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

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 eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild. 
      EDIT: You can now install it directly from the Modules directory: http://modules.processwire.com/modules/inputfield-float-range/
       
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Features
      Min/max values Precision (number of decimals) Optional step value (Read more) Optional manual override of the selected value (will still adhere to the rules above) Configurable rounding of manually entered values (floor, round, ceil, disable) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

       
      Todo
      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant  
      Changelog
      004 (current version)
      - Make rounding of manually entered values configurable (floor, round, ceil or disable)
      - Fix small JS bug when the value-display field was not displayed
      - Update README
      003
      - Code cleanup, add some ModuleInfo data & LICENSE
      - Submit to PW Modules directory (http://modules.processwire.com/modules/inputfield-float-range/)
      002
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional
      001
      - Initial release
       
      Thanks!
       
       
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-10-18
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
×
×
  • Create New...