Jump to content
justb3a

Module: Image Extra

Recommended Posts

Hey @justb3a

I'm using your module together with matrix some repeaters fields at the moment and get the following notice:

Notice: Undefined index: title in C:\xampp\htdocs\intern\oneslider\site\modules\ImageExtra\ImageExtra.module on line 523

PW: 3.0.62 / ImageExtra: 1.0.6

Share this post


Link to post
Share on other sites
6 hours ago, mauricemoss said:

Hey @justb3a

I'm using your module together with matrix some repeaters fields at the moment and get the following notice:

Notice: Undefined index: title in C:\xampp\htdocs\intern\oneslider\site\modules\ImageExtra\ImageExtra.module on line 523

PW: 3.0.62 / ImageExtra: 1.0.6

Hi @mauricemoss, there's already a PR for this issue here: https://github.com/justb3a/processwire-imageextra/pull/30

I hope @justb3a takes it into account for her next release.

Share this post


Link to post
Share on other sites

I have a sudden problem with this module. The "Image extra fields" don't show up any more. Not on the Edit Page template, nor on the published page itself. There is the caption field enabled and two extra TextInputs. (see the attached image_extra_field_details.png) but they are not visible.

I have done this page for a library more than a year ago and they used it without a problem since then.

On the Page > Home -> Content ->  Edit (an item) which uses this module: there is only the image and a description field (like a normal image field) the other TextInputs are simply gone. (see the image_extra_field_page_edit.png).

Nobody has changed anything what so ever, I have checked the logs to be sure.

The page uses the Image Extra Module 1.0.0 and ProcessWire version 3.0.27

Any idea what the reason could be?

Thanks for any feedback.

P.S.

When I enable debug mode the only notice I get is :

Undefined index: vitrineimages in /home/bla/public_html/wire/modules/ImageExtra.module on line 826

but no error

The Admin->Modules->ImageExtra->Module information page shows:

Title Image Extra
Class ImageExtra
File /wire /modules /ImageExtra.module
Version 1.0.0
Installed 1 year ago
Summary Adds custom fields to image fields (including multi-language support)
Hooks To after.InputfieldImage::getConfigInputfields(), after.InputfieldImage::renderItem(), before.ProcessField::executeSave()
More Information https://github.com/justonestep/processwire-imageextra

 

image_extra_field_details.png

image_extra_field_page_edit.png

Share this post


Link to post
Share on other sites

I have added an additional field called price, which starts with a $ symbol. Every time the page is saved, whether or not there is an output formatter set, an additional \ is added in front of the $ symbol, so if you save say five times you end up with \\\\\$

Share this post


Link to post
Share on other sites

After I installed this, I couldn't upload anything, all images failed to upload and the console output 

Failed to load resource: net::ERR_CONNECTION_RESET

for each. After uninstalling, image uploads work again

ProcessWire ver 3.0.89

Share this post


Link to post
Share on other sites
On 30.10.2017 at 9:35 PM, titanium said:

Hi @mauricemoss, there's already a PR for this issue here: https://github.com/justb3a/processwire-imageextra/pull/30

I hope @justb3a takes it into account for her next release.

@justb3a

Same problem here with an image field in a repeater:

ErrorException: Undefined index: title in C:\laragon\www\XXX\site\modules\ImageExtra\ImageExtra.module:523

PW 3.0.95

Share this post


Link to post
Share on other sites

Hi.
I have a problem with the "link field" and PW 3.0.96 .
When I try to select a page (page tree) the "Choose" button disappears. Unfortunately it is no longer possible to make a selection.

Does anyone have the same problem or a quick solution for it?

I think the error is not the module, but the file "ProcessPageList.js"

Thanks,
Robert

  • Like 2

Share this post


Link to post
Share on other sites
On 3/24/2018 at 4:15 AM, ro-bo said:

Hi.
I have a problem with the "link field" and PW 3.0.96 .
When I try to select a page (page tree) the "Choose" button disappears. Unfortunately it is no longer possible to make a selection.

Does anyone have the same problem or a quick solution for it?

I think the error is not the module, but the file "ProcessPageList.js"

Thanks,
Robert

I'm on PW 3.0.104 and having the same problem.

Share this post


Link to post
Share on other sites
On 8/4/2017 at 1:50 PM, mr-fan said:

just tested with 3.0.65 and it seems that the pagelink field is not working?

imageextra.thumb.jpg.9ee7b8bd45060a8c970cea78bb8f1388.jpg

Best regards mr-fan

 

On 8/7/2017 at 5:22 PM, justb3a said:

Thanks @mr-fan: there was a little bug figuring out, whether the user is working in the backend or not (differentiate between int(0) und false :D ). The belonging JavaScript file wasn't loaded.

Hello, i am experiencing this problem as well. Unfortunately i have to consider myself an absolute beginner so i would be more than happy if someone could explain this solution in more detail. Thanks in advance!

Share this post


Link to post
Share on other sites

Sorry for spaming this thread but i am kinda stuck. As far as i understand this issue has fixed at some point. I only need a solution to apply image-links in pw and from what i read ImageExtra seems the way to go. It will work properly with image-fields but not within repeater-fields. I am using module version 1.0.6 with processwire 3.0.98. Any advise is highly appriciated. 😅

Share this post


Link to post
Share on other sites

Hello,

I'm having the Select button disappearing, so I can't select anything. Is there a fix for this issue?

I'm using last version of the module.

Thanks!

Share this post


Link to post
Share on other sites
14 hours ago, alejandro said:

Hello,

I'm having the Select button disappearing, so I can't select anything. Is there a fix for this issue?

I'm using last version of the module.

Thanks!

Are you by chance using the master instead of develop branch again?

Remember this was fixed on the develop branch:

 

Share this post


Link to post
Share on other sites
9 hours ago, adrian said:

Are you by chance using the master instead of develop branch again?

 

Yes, I upgraded to the latest version. Anyway, I've changed it to repeater field with image + page reference fields, so problem solved.

Share this post


Link to post
Share on other sites

Hey there,

I create all my fields with the Migrations module, so I create all my fields with the core functions.
Sadly, I'm having trouble creating "otherField" information with ImageExtra.

If I try this, the whole field is broken:

$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = "{\"cf_textformatter\":{\"copyright\":\"\"},\"cf_label\":{\"cf_label__copyright\":\"Copyright\"}}";
$myField->save();

Or with an array:

$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = [
	'cf_textformatter' => [
		'copyright' => ''
	],
	'cf_label' => [
		'cf_label__copyright' => ''
	]
];
$myField->save();

I always get this error:

ProcessWire: ProcessPageEdit: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_test_field.copyright' in 'field list'

 

Has anyone made any experience with this? Suggestions? 🙂

Thanks in advance!

Share this post


Link to post
Share on other sites
17 minutes ago, noodles said:

Hey there,

I create all my fields with the Migrations module, so I create all my fields with the core functions.
Sadly, I'm having trouble creating "otherField" information with ImageExtra.

If I try this, the whole field is broken:


$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = "{\"cf_textformatter\":{\"copyright\":\"\"},\"cf_label\":{\"cf_label__copyright\":\"Copyright\"}}";
$myField->save();

Or with an array:


$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = [
	'cf_textformatter' => [
		'copyright' => ''
	],
	'cf_label' => [
		'cf_label__copyright' => ''
	]
];
$myField->save();

I always get this error:


ProcessWire: ProcessPageEdit: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_test_field.copyright' in 'field list'

 

Has anyone made any experience with this? Suggestions? 🙂

Thanks in advance!

 

If I see it correctly, the "other field columns" will be added on a save hook via the $input->post data - which I don't have in my case.
In line 1213 it looks like I will have to alter the table in my script. 😞

Damn! 🙂 

Any sweeter way known by someone?

Share this post


Link to post
Share on other sites

I just pulled from the dev branch and still get the same error as before (right after new image upload)

$title = $language->title->getLanguageValue($language); // line 398

Call to a member function getLanguageValue() on string

And also: line 229-231: PHP Warning: stripos() expects parameter 1 to be string, array given

latest PW dev installed, PHP 7.2

Share this post


Link to post
Share on other sites

Hi there,

I set up the Image Extra Fields + multilang support. 

UNF the second language is not showing when switching to the other page language.
It always displays the default language.

Custom field name is "img_title";

Trying to output the field like this:

<?=$page->images->first()->img_title;?>

 

Share this post


Link to post
Share on other sites
On 7/19/2018 at 10:46 AM, alejandro said:

Hello,

I'm having the Select button disappearing, so I can't select anything. Is there a fix for this issue?

I'm using last version of the module.

Thanks!

 

Here is a little fix:

In your templates/admin.php add a custom css file:

$config->styles->add($config->urls->templates . "styles/admin.css");
require($config->paths->adminTemplates . 'controller.php'); 

in templates/styles/admin.css

.PageList .PageListItem:hover .PageListActions {
    display: inline-block !important;
}

Share this post


Link to post
Share on other sites

I really like this module. It's much cleaner for managing different alt-Text and caption than everything I tried before (extra fields, repeater, complex Hanna Code) but I ran into an issue on the second site I installed.

The image field I wanted to enhance was named Bilder (with uppercase). After adding extra field imgcaption the site stopped working and in debug mode it read something like field Bilder.imgcaption doesn't exist. After changing the field name to bilder (lowercase) and correcting my templates and Hanna Code everything worked again. Might be worth some warning in the documentation

  • Like 1

Share this post


Link to post
Share on other sites

I ran into an issue with multilanguage support.

Most sites I'm working need only one language, but for a german user interface I need the module Languages Support which automatically adds a description field for every language to an image field. I used to disable these extra language fields in the admin interface by setting disable multilanguage support in the input settings of the definition for my images-fields. After installing the Image Extra Module I added a caption field, which seemed to work fine: I could edit and process content of this new caption field.

Now I noticed that it is  possible to insert a new caption, but not to alter an existent one. I get a notice that the field was changed, but nothing happens. After checking the database I saw that there was a connection to multi-language support. Instead of a simple entry for new captions like "["Schloss Rheinsberg (Photo: xyz)"] an edited entry is like '{"0":"Das Refektorium","1019":"Das Refektorium"}'
When I enable multi language support for the image field I can see, that only changes in the field for the custom language (in my case german) are processed but do also change the value of the field in the default language (english) This is very confusing for authors.

As a workaround When changing the language of the admin to default instead of german everything works as expected.

Share this post


Link to post
Share on other sites
On 3/14/2019 at 3:18 PM, sujag said:

I ran into an issue with multilanguage support.

Most sites I'm working need only one language, but for a german user interface I need the module Languages Support which automatically adds a description field for every language to an image field. I used to disable these extra language fields in the admin interface by setting disable multilanguage support in the input settings of the definition for my images-fields. After installing the Image Extra Module I added a caption field, which seemed to work fine: I could edit and process content of this new caption field.

Now I noticed that it is  possible to insert a new caption, but not to alter an existent one. I get a notice that the field was changed, but nothing happens. After checking the database I saw that there was a connection to multi-language support. Instead of a simple entry for new captions like "["Schloss Rheinsberg (Photo: xyz)"] an edited entry is like '{"0":"Das Refektorium","1019":"Das Refektorium"}'
When I enable multi language support for the image field I can see, that only changes in the field for the custom language (in my case german) are processed but do also change the value of the field in the default language (english) This is very confusing for authors.

As a workaround When changing the language of the admin to default instead of german everything works as expected.

Yes we have also this problem. only solution is the workaround to set the users language to the default language 😞

Share this post


Link to post
Share on other sites
On 10/30/2017 at 9:35 PM, titanium said:

Hi @mauricemoss, there's already a PR for this issue here: https://github.com/justb3a/processwire-imageextra/pull/30

I hope @justb3a takes it into account for her next release.

I've got the same error here. I use the Image in a Repeater.

Is there any workaround at this time? Although the module works fine, to have an error is annoying.

Thanks for your help!

Share this post


Link to post
Share on other sites
On 3/16/2019 at 5:13 AM, MateThemes said:

I've got the same error here. I use the Image in a Repeater.

Is there any workaround at this time? Although the module works fine, to have an error is annoying.

Thanks for your help!

I have found a solution, that worked for me.

I just put in the module file at line 523 a isset statement:

/**
   * Hook format extra fields
   *
   * @param HookEvent $event
   */
  public function formatExtraValue(HookEvent $event) {
    $page = $event->arguments(0);

    if (!isset ($page->data['title'])) {
      $field = $event->arguments(1);
      $value = $event->arguments(2);
      $settings = $this->getOtherFieldSettings($field);

      if ($settings && $formatters = $settings->cf_textformatter) {
        foreach ($value as $v) {
          foreach ($this->additionalFields['other'][$field->name] as $otherField) {
            if (!array_key_exists($otherField, $formatters)) continue;
            $formatter = $formatters->$otherField;
            $currentValue = $v->$otherField;
            if ($formatter) $this->modules->get($formatter)->formatValue($page, $field, $currentValue);
            $v->$otherField = $currentValue;
          }
        }
      }
    }
  }

And this works for me.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...