Jump to content

Module ImageReference - Pick images from various sources


gebeer

Recommended Posts

Hi @gebeer, I tested the update this morning and oops...

I don't know what happened this time, but it no longer works at all either inside or outside of a repeater. it just loads a clone of the page currently being edited.

It's hard to explain, so this GIF should illustrate what's happening (this is a test outside of a repeater):

Animated GIF showing module bug

The above demonstrates the "choose an image from page" and "choose any page" options.

  • The field settings are correct - they are same ones that worked (outside of a repeater) previously.
  • There are images available!
  • I tried the other options (from a folder etc) and exactly the same thing happens.
  • I uninstalled all other modules in case there was a JS conflict and still the same thing happens.

In case it helps, here is the console log:

Console log for the module

I'm using ProcessWire version 3.0.147 and PHP 7.2.

Happy New Year! (?)

Link to comment
Share on other sites

@all

I just discovered that v2.0.1 is not working correctly when not logged in as superuser. The ajax calls to get the thumbnails are not working.

You can either revert back to v2.0.0 and deactivate the option to get thumbnails or wait for a fix to the master version.

Sorry for the inconvenience!

I have my logic for the ajax calls in the init() method of InputfieldImageReference.module. Until just now I didn't realize that this is not getting called correctly. I read up on how to implement ajax calls to an inputfield module and one of the proposed ways was to do this in init(). Will have to investigate further. If anyone can give me pointers on how to make this work, this would be great.

Link to comment
Share on other sites

4 minutes ago, LMD said:

I don't know what happened this time, but it no longer works at all either inside or outside of a repeater

Are you logged in as non superuser when this happens? I just discovered a few minutes before you posted that there is a problem with non superusers. See my last post above. Try to fix this asap.

Link to comment
Share on other sites

20 minutes ago, gebeer said:

Are you logged in as non superuser when this happens? I just discovered a few minutes before you posted that there is a problem with non superusers. See my last post above. Try to fix this asap.

No, it's in my dev environment and I'm the only user (superuser).

While I think of it, I also ensured the pages were 'published' and not 'hidden', in case that was the problem (it wasn't).

Edited by LMD
Last minute though
  • Like 1
Link to comment
Share on other sites

Just now, LMD said:

No, it's in my dev environment and I'm the only user (superuser).

Thank you for clarifying. I'm currently looking into it. But won't be able to fix this until hopefully tomorrow.

Link to comment
Share on other sites

Hi @gebeer,

I think it would be better to name the title of the fieldtype "Image Reference" instead of "Image Reference Fieldtype":

s0WVwtz.png

https://github.com/gebeer/FieldtypeImageReference/blob/2df486396ae58a5ff1687d30434cbfce6f913602/FieldtypeImageReference.module#L32

I guess this was due to a wrong field setup, but I also got these errors:

jyFaXaY.png

 

Regarding your AJAX:

I found it easier and safer to handle my ajax calls via hooking into ProcessPageView::pageNotFound: https://github.com/BernhardBaumrock/RockTabulator/blob/6670f2647fcbbb1f5ad4c5237ea9fd03b8899315/RockTabulator.module.php#L73

https://github.com/BernhardBaumrock/RockTabulator/blob/6670f2647fcbbb1f5ad4c5237ea9fd03b8899315/RockTabulator.module.php#L159-L188

I've taken a similar approch to yours on RockGrid and had some problems with it, because of scripts not being available when the field is collapsed and loaded via ajax or the like...

  • Like 1
Link to comment
Share on other sites

8 minutes ago, bernhard said:

I think it would be better to name the title of the fieldtype "Image Reference" instead of "Image Reference Fieldtype":

Yep, will change it.

8 minutes ago, bernhard said:

found it easier and safer to handle my ajax calls via hooking into ProcessPageView::pageNotFound

Thanks for that hint. Will give it a try.

  • Like 1
Link to comment
Share on other sites

New version v2.0.2 is available from github.

This version fixes the problems with getting thumbnails displayed via ajax. At least in my extensive testing everything was working. @LMD can you please give it a try now?

While trying to fix the ajax issue, I was running in circles for hours on end. Tried various methods I found in the forum and @bernhard's hook. I always got it working as superuser but got very strange results when logged in as an editor user with page edit permissions. Until I discovered that the problems were due to my module not always loading for ajax requests. I added 'autoload' => 'template=admin' to my module info and suddenly all was working as expected. Still scratching my head why a module's init() method would get called when logged in as superuser but not when logged in as editor. Any ideas here?

New in this version is the feature for uploading files to the predefined folder from within the inputfield. Here's a short preview of that feature.

Now that this is working, I'm thinking about adding the ability to delete them from within the inputfield, too.

As always, I shall be happy to receive your comments and issue reports 🙂

 

 

  • Like 4
Link to comment
Share on other sites

3 minutes ago, LMD said:

Works like a charm for me, both outside and inside repeaters

Today I discovered that it doesn't work inside RepeaterMatrix fields, yet. If you have a chance to test this, please report. Thank you.

Link to comment
Share on other sites

New version v2.1.0 is available on github.

New features:

Images in folders can now be uploaded and deleted from within the input. I am pretty excited about this feature. It gives you an image field that holds images independent of a page where images can be edited (upload/delete) and outputs PageImage objects in the frontend that can be cropped and resized.

EDIT: forgot to mention that the module install 2 permissions imagereference-folder-upload and imagereference-folder-delte. Any non-superuser role needs those.

Short preview

Also now you can have the folder under either site/templates/ or site/assets/. The module will find it in both locations. If you have folders with same name in both locations, it will pick the one in site/templates/

The module is almost ready to go. One major thing, I need to fix, though, is getting it to work inside RepeaterMatrix fields. It is working fine inside normal repeaters. But eventually I will get there.

Feel free to grab a copy and do some tests. Your feedback is much appreciated.

Edited by gebeer
forgot to mention
  • Like 7
Link to comment
Share on other sites

New minor version v2.1.1 with fix for error when using field inside RepeaterMatrix is on github.

This was a strange error and, honestly, I still don't quite understand the root cause. When trying to add a new repeatermatrix item with this field inside, I got the error

Field [fieldname] is not saveable because it is in a specific context

Google brought me to this closed issue in the processwire-issues repo. The issue was related to FieldTypeFile. I just applied the fix for it to my fieldtype module and it worked.

But I'd like to understand the underlying problem. So if anybody has any clue, please let me know. Thank you.

  • Like 1
Link to comment
Share on other sites

On 1/5/2020 at 10:10 AM, gebeer said:

Today I discovered that it doesn't work inside RepeaterMatrix fields, yet. If you have a chance to test this, please report. Thank you.

Oh, sorry, I don't have a RepeaterMatrix field in operation anywhere at the current time.

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

New version v2.1.2 is out on github.

This version fixes a problem with images inside a folder that have names not conform with file naming conventions.

When the module loads images from a folder, it converts them to Pageimage objects. When images are added to a Pageimages object file names get sanitized automatically by PW. In my case this resulted in different file names inside the Pageimage object and on disk. Consequently, thumbnails and previews for those images could not be loaded. I fixed this by automatically renaming all folder images to match the sanitized name versions inside a Pagimage object. 

This version also adds the ability to set values to this field via API. You can now do something like this to set a Pageimage object as new value to this fieldtype via API

$p = $pages->get(1001);
$image = $p->image; // returns a Pageimage object
$p->of(false);
$p->set('imagereference', $image); // sets the Pageimage object to the ImageReference field. This gets converted to a JSON string internally for storage
$p->save();

 

  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...

@gebeer I've installed your module today for the first time. I was mostly interested in the feature "select from folder". But sadly, that just didn't work. I cleared site/cache several times, refreshed modules etc., but the field always would state that no such folder exists.

I have added that folder after creating the field. Does that matter? Does the folder have to be there before you create an image reference field? Nothing suspicious in the logs, btw (debug mode on).

ProcessWire: 3.0.149
PHP: 7.3.13
Webserver: Apache/2.4.35 (Win64) OpenSSL/1.1.1d
MySQL: 5.7.24

Link to comment
Share on other sites

11 hours ago, dragan said:

I have added that folder after creating the field. Does that matter? Does the folder have to be there before you create an image reference field?

It doesn't matter whether you create the folder before or after. The module will pick it up once it is there. If it is not there yet, you will get a warning. Once it is there, the warning normally goes away. If it is empty, you will get a warning to upload images.

Can't reproduce your problem here on PW 3.0.145 PHP 7.2 But versions really shouldn't matter in that case. Did you install latest master?

EDIT: just tested this on PW 3.0.149 and PHP 7.3.2 without problems.

Where did you create the folder? It needs to be either in /site/assets/ or /site/templates/.

Please try and comment out line 680 in FieldtypeImagereference.module and see if the warning message persists. I attached the error to both the field and globally so it is shown at the top of the page when you save the settings. Maybe this is the culprit in your case?

Edited by gebeer
Link to comment
Share on other sites

  • 7 months later...

Hi @gebeer I'm trying to use your module within the settingfactory module but I' having some issue initializing it, what are the mandatory parameters to make it work? I tried this config but it shows just the placeholder image. Thanks
 

[
        'name' => 'logotest',
        'label' => __('Logo & Favicon'),
        'type' => 'InputfieldImageReference',
        'width' => '100',
        'fromfolder ' => true,
        'folderpath' => '/site/templates/',
        'description' => __('description'),
        'collapsed' => 0,
    ],
Link to comment
Share on other sites

@Sevarf2 you need to specify the folderpath correctly.

When the files are located in /site/templates/images/icons/, the value is 'images/icons/ '

When the files are located in /site/assets/icons/, the value is 'icons/'

Hope that helps

 

Link to comment
Share on other sites

40 minutes ago, gebeer said:

@Sevarf2 you need to specify the folderpath correctly.

When the files are located in /site/templates/images/icons/, the value is 'images/icons/ '

When the files are located in /site/assets/icons/, the value is 'icons/'

Hope that helps

 

still not working, I can only see the default image and nothing more
image.png.d6c9eece9e6aaa9ba0784d3941a37d70.png

Link to comment
Share on other sites

I just installed tracy and I got this error
image.png.b729d656968f234013386aa669001a5e.png

I'm using php settings not json

[
        'name' => 'logotest',
        'label' => __('Logo & Favicon'),
        'type' => 'InputfieldImageReference',
        'width' => '100',
        'fromfolder ' => true,
        'folderpath' => 'assets/imgs/',
        'description' => __('image upload'),
        'collapsed' => 0,
    ],

Link to comment
Share on other sites

@gebeer Are there plans to allow for multiple images to be used with this module / field-type? Or is there something I've been missing? I don't see anything in the module or field configs. (not that I would need it right now for a real-live project, I'm just curious)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By Robin S
      Select Images
      An inputfield that allows the visual selection and sorting of images, intended for use with the FieldtypeDynamicOptions module. Together these modules can be used to create a kind of "image reference" field.

      Integration with FieldtypeDynamicOptions
      InputfieldSelectImages was developed to be used together with FieldtypeDynamicOptions (v0.1.3 or newer):
      Create a Dynamic Options field. Choose "Select Images" as the "Inputfield type". Select Images appears in the "Multiple item selection" category but you can set "Maximum number of items" to 1 if you want to use Select Images for single image selections. Define selectable options for the field via a FieldtypeDynamicOptions::getSelectableOptions hook. See some examples below. FieldtypeDynamicOptions is recommended but is not a strict requirement for installing InputfieldSelectImages in case you want to use an alternative way to store the field data.
      Selection of Pageimages
      In this example the field allows selection of Pageimages that are in the "images" field of the home page.
      The field will store URLs to the Pageimages so it works as a kind of "image reference" field. You can use the "Format as Pagefile/Pageimage object(s)" option for the Dynamic Options field to have the formatted value of the field be automatically converted from the stored Pageimage URLs to Pageimage objects.
      $wire->addHookAfter('FieldtypeDynamicOptions::getSelectableOptions', function(HookEvent $event) { // The page being edited $page = $event->arguments(0); // The Dynamic Options field $field = $event->arguments(1); // For a field named "select_images" if($field->name === 'select_images') { $options = []; // Get Pageimages within the "images" field on the home page foreach($event->wire()->pages(1)->images as $image) { // Add an option for each Pageimage // When the key is a Pageimage URL the inputfield will automatically create a thumbnail // In this example the label includes the basename and the filesize /** @var Pageimage $image */ $options[$image->url] = "{$image->basename}<br>{$image->filesizeStr}"; } $event->return = $options; } }); Selection of image files not associated with a Page
      When not working with Pageimages you must add a "data-thumb" attribute for each selectable option which contains a URL to a thumbnail/image.
      In this example the field allows selection of image files in a "/pics/" folder which is in the site root.
      $wire->addHookAfter('FieldtypeDynamicOptions::getSelectableOptions', function(HookEvent $event) { // The page being edited $page = $event->arguments(0); // The Dynamic Options field $field = $event->arguments(1); // For a field named "select_images" if($field->name === 'select_images') { $options = []; // Get files that are in the /pics/ folder $root = $event->wire()->config->paths->root; $path = $root . 'pics/'; $files = $event->wire()->files->find($path); // Add an option for each file foreach($files as $file) { $basename = str_replace($path, '', $file); $url = str_replace($root, '/', $file); // The value must be an array with the following structure... $options[$url] = [ // The label for the image 'label' => $basename, 'attributes' => [ // An image URL in the "data-thumb" attribute 'data-thumb' => $url, ], ]; } $event->return = $options; } }); The field values don't have to be image URLs
      The values stored by the Dynamic Options field don't have to be image URLs. For example, you could use the images to represent different layout options for a page, or to represent widgets that will be inserted on the page.
      Also, you can use external URLs for the thumbnails. In the example below the options "calm" and "crazy" are represented by thumbnails from placecage.com.
      $wire->addHookAfter('FieldtypeDynamicOptions::getSelectableOptions', function(HookEvent $event) { // The page being edited $page = $event->arguments(0); // The Dynamic Options field $field = $event->arguments(1); // For a field named "calm_or_crazy" if($field->name === 'calm_or_crazy') { $options = []; // Add options that are illustrated with thumbnails from placecage.com $options['calm'] = [ // The label for the option 'label' => 'Nicolas Cage is a calm man', 'attributes' => [ // An image URL in the "data-thumb" attribute 'data-thumb' => 'https://www.placecage.com/260/260', ] ]; $options['crazy'] = [ // The label for the option 'label' => 'Nicolas Cage is a crazy man', 'attributes' => [ // An image URL in the "data-thumb" attribute 'data-thumb' => 'https://www.placecage.com/c/260/260', ] ]; $event->return = $options; } }); Field configuration
      You can define labels for the button, notices, etc, that are used within the inputfield if the defaults don't suit.

       
      https://github.com/Toutouwai/InputfieldSelectImages
      https://processwire.com/modules/inputfield-select-images/
×
×
  • Create New...