Jump to content
justb3a

Module: Image Extra

Recommended Posts

hey, I didn't forget about these issues, just had to finish a client project first. sorry  :mellow: I added the fix for the missing javascript, please pull the develop branch. 

  • Like 3

Share this post


Link to post
Share on other sites

Thanks both works great now. Such a useful module! 

Share this post


Link to post
Share on other sites

Thanks a lot for this modules. I used it in several projects and it always worked fine for me.

Today I ran into a strange bug. The Image Extra fields don't seem to be created in the database.

When I check the orientation field, or any other extra field it says:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_backgroundImages.orientation' in 'field list'

during page creation.

I looked up the the corresponding mysql table and yes, there is no field created.

could this be connected with the multilingual support? I set up a multilingual site on which english is not the default lang.

Thanks for your help.

Share this post


Link to post
Share on other sites

@pmichaelis: I don't think that it has to do with the multilingual site, this always works fine for me. And it doesn't matter whether english is the default language. `english` is just a label. Could you please try to rename the field so that it doesn't contain camelCase (capital letters)? For example field_backgroundImages to field_background_images. Have a look at the description: "Any combination of ASCII letters [a-z], numbers [0-9], or underscores (no dashes or spaces)." I don't  know whether this is the reason but I would like to give it a try. 

Edit: Tested it using a camelCaseField without any problems. Using two languages "default" and "english". But my system is case insensitive  ;). Which PW version do you use?

  • Like 1

Share this post


Link to post
Share on other sites

Could you please try to rename the field so that it doesn't contain camelCase (capital letters)?

Thank you! Your were right about the field renaming. Using PW 2.7.2. by the way.

Works like charm.

Share this post


Link to post
Share on other sites

Thank you justb3a for a wonderfull module of yours! It is indeed a nice tool to use instead of a Repeater or PageTable when they are an overkill.

I got similar issue as this. I understand your answer below, but I wish I could not use multilangual fields, even if I have Language Support and 2 languages installed. Is it possible?

My sites are often unilingual, but I do create additional language for admin to be able to work in default English admin interface, as all support you can get is in English (or should I say American to honor the creator of PW). I found no other way to do this (is there any?)

Share this post


Link to post
Share on other sites

I wish I could not use multilangual fields, even if I have Language Support and 2 languages installed. Is it possible?

My sites are often unilingual, but I do create additional language for admin to be able to work in default English admin interface, as all support you can get is in English (or should I say American to honor the creator of PW). I found no other way to do this (is there any?)

I added an option to disable multi-language fields. In field settings for Image Extra Fields there is a new checkbox "Disable multi-language fields?". Please pull branch develop to get this new feature.

btw: branch develop is ProcessWire 3.x ready but it needs a  bit more testing before I'll  create a new release.

  • Like 2

Share this post


Link to post
Share on other sites
It took some time but now it's possible to use a textformatter e.g. markdown parser. This is only available in branch develop for PW3.x.

There is a little issue due to focus textareas, I created a PR to solve this.

How to use it: go to field settings, enter some other fields, save. Reopen ImageExtra tab, now you can see a table below in which you can define one textformatter for each extra field. All installed text formatters will be listet in this dropdown.

post-2759-0-92009200-1464860053_thumb.pn

  • Like 4

Share this post


Link to post
Share on other sites

Is ImageExtra working in repeaters? I can't save the description and caption fields and also not delete the image. (see screenshot)

I use ImageExtra with an image slider on the same website and it is working fine. :)  But in this repeater it's not ...

So it seems I can't use an image in a repeater in this website?

(This would spoil the plan  :( )

Any ideas?

Thanks!

post-3713-0-84386400-1465725415_thumb.jp

Update:

Not sure if this has to do with ImageExtra at all. The whole repeater doesn't seem to work. If I put text in a text-field and save: the text is gone after saving. Don't know what is wrong here ...

Update: 

The problem is that these field dependencies don't work in repeaters. 

Sorry for blaming the Module  :rolleyes:

Thanks for the great work!

Share this post


Link to post
Share on other sites

hi @Henrik, glad you figured out yourself what caused the problem. I just wanted to test images in repeaters again. But I've got a lot of pages out there which are using images containing image extra fields inside repeaters!

  • Like 1

Share this post


Link to post
Share on other sites

I don't know if this is a known issue, but the orientation dropdown isn't working with the new image field from PW 3.0 and 2.8.
I tried the develop branch, but had no luck.

Anyway thx for this great module!

Edit: I just found out, that the dropdown is working in grid view, but not in list view
Edit2: none of the extra fields is working in list view

Share this post


Link to post
Share on other sites
On 11/12/2015 at 1:00 PM, adrian said:

Sorry for the delay in getting back to you regarding the error - I still need to look at this again, but for now I have a new problem for you :)

It looks like the Page Link option isn't working properly - it just shows a text input with "0" as the value.

Screen Shot 2015-11-12 at 9.59.43 PM.png

If I load "InputfieldPageListSelect.min.js" in the module, then it works as expected.

Screen Shot 2015-11-12 at 9.59.56 PM.png

Hello, would you mind to point how to do this, I get this very same error.

Thanks.

Share this post


Link to post
Share on other sites

My first time using this module - very cool. :)

For custom "additional" fields it would be nice to be able to set a field label as well as the field name, so field labels in the page editor can have spaces instead of underscores, etc. Maybe the field labels could be defined in the same table that is used for selecting TextFormatters?

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, Robin S said:

My first time using this module - very cool. :)

For custom "additional" fields it would be nice to be able to set a field label as well as the field name, so field labels in the page editor can have spaces instead of underscores, etc. Maybe the field labels could be defined in the same table that is used for selecting TextFormatters?

Big +1 for this - sometimes it can be very hard to explain what should go in a field without a label.

  • Like 2

Share this post


Link to post
Share on other sites

I thought about this feature as well from time to time :). There is a new version 1.0.1 which fixes some PHP7 issues and adds the possibility to set custom labels for each extra field. It also supports multi-language usage. Furthermore I changed the way the extra fields (form) are rendered. Now you can click a tab and briefly hold (aka long-click) it and all extra fields will switch to that language. And I removed the checkbox for the caption field. If it was set, it will be added as first item in the `other fields` input field.

Screen Shot 2016-10-05 at 17.07.25.png

 

Screen Shot 2016-10-05 at 17.07.09.png

 

  • Like 6

Share this post


Link to post
Share on other sites

This looks awesome @justb3a - thank you!

While you're on a roll, I don't suppose you'd like to add the ability to define the width of custom fields so we can float them on one line?

The other thing that would really help would be an options type field with select/radios/checkbox options.

Sorry, I know that's a lot - just a wishlist :)

  • Like 1

Share this post


Link to post
Share on other sites
5 minutes ago, adrian said:

While you're on a roll, I don't suppose you'd like to add the ability to define the width of custom fields so we can float them on one line?

haha, I tried this today but $field->columnWidth = 50; has been ignored. So I guess I need to change the whole markup, wrap the fields inside a list or something like that. Today I just wanted to finish the other feature and didn't investigate further. But I keep it in mind. Furthermore I won't add another column for the widths of a field, I would prefer to set it to 50. Otherwise I've to add one more column to define the number of rows the textarea should be – for each field.

 

13 minutes ago, adrian said:

The other thing that would really help would be an options type field with select/radios/checkbox options.

I know... There is a github issue for this as well. For now I got no good idea how the interface / structure could look like – it has to be as easy as possible for the user to add / remove / manipulate the fields. Maybe a simple input field where the user is able to add all option fields (comma-separated). Once the module settings has been saved one more table could appear. In this table the user could be able to set a type (select, radio, checkbox) and the options (comma-separated input). But what about multi-language labels and options? ??? This would blow up the whole settings a lot... If you have a good idea, just let me know!

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for your thoughts on those.

I have a couple of weird things for you.

Now even with description field rows set to 0 I still get a label for the Description field.

Also, the input>text fields are now textarea fields - I think it looks kinda weird when you only want simple setting entries.

Screen Shot 2016-10-05 at 10.02.49 AM.png

Share this post


Link to post
Share on other sites

Thanks @justb3a for the updates, it's getting better and better!

There's a PHP notice in the new release:

PHP Notice: Undefined index: otherField in .../site/modules/ImageExtra/ImageExtra.module:992

If you use Tracy Debugger it's easy to spot.

Share this post


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

I have a couple of weird things for you.
Now even with description field rows set to 0 I still get a label for the Description field.
Also, the input>text fields are now textarea fields - I think it looks kinda weird when you only want simple setting entries.

You're right. The check whether to show the description label or not missed a condition. Since adding the opportunity to add textformatters I changed InputfieldText to InputfieldTextarea. Textformatters like Newlines to Unordered List doesn't make that much sense if you aren't able to add line breaks. I added a condition: all fields default to InputfieldText except the fields which got a textformatter assigned. I'm not that happy with the layout/styles right now. I need to invest some more time optimizing the layout.

3 hours ago, tpr said:

There's a PHP notice in the new release:

You're right, too. I missed the following scenario: checked captionField but added no otherField.

The fixes are merged into the master branch :)

  • Like 3

Share this post


Link to post
Share on other sites
5 minutes ago, justb3a said:

Since adding the opportunity to add textformatters I changed InputfieldText to InputfieldTextarea. Textformatters like Newlines to Unordered List doesn't make that much sense if you aren't able to add line breaks.

I understand the thinking here, but agree with @adrian that often you want a single line input rather than multi-line. I know you want to avoid an overly-complicated interface but perhaps there could a "Rows" input for additional fields like for the Description field?

Share this post


Link to post
Share on other sites
1 minute ago, Robin S said:

I understand the thinking here, but agree with @adrian that often you want a single line input rather than multi-line. I know you want to avoid an overly-complicated interface but perhaps there could a "Rows" input for additional fields like for the Description field?

But:

9 minutes ago, justb3a said:

all fields default to InputfieldText except the fields which got a textformatter assigned

I am pretty happy with this solution - works for me anyways!

Share this post


Link to post
Share on other sites
Just now, adrian said:

 

10 minutes ago, justb3a said:

all fields default to InputfieldText except the fields which got a textformatter assigned

I am pretty happy with this solution - works for me anyways!

Myself, I add SmartyPants and HTML Entity Encoder textformatters to all text fields.

  • Like 1

Share this post


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 bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...