Jump to content

Module: Image Extra


Recommended Posts

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.

  • Thanks 1
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

  • Like 1
Link to post
Share on other sites
  • 3 months later...
  • 2 weeks later...

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 \\\\\$

Link to post
Share on other sites
  • 2 weeks later...

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

Link to post
Share on other sites
  • 2 weeks later...
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

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
Link to post
Share on other sites
  • 2 months later...
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.

Link to post
Share on other sites
  • 5 weeks later...
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!

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. 😅

Link to post
Share on other sites
  • 3 weeks later...
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:

 

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.

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!

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?

Link to post
Share on other sites
  • 4 weeks later...

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

Link to post
Share on other sites
  • 4 weeks later...

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;?>

 

Link to post
Share on other sites
  • 2 months later...
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;
}
Link to post
Share on other sites
  • 1 month later...

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
Link to post
Share on other sites
  • 2 months later...

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.

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 😞

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!

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.

 

Link to post
Share on other sites
  • 2 months later...
On 3/20/2019 at 6:39 PM, MateThemes said:

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.

 

This issue is solved, because the PR I submitted has now been accepted by @justb3a.

Link to post
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 FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
×
×
  • Create New...