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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...