Jump to content
justb3a

Module: Image Extra

Recommended Posts

@tekno: Like any other value: $image->orientation
 
For example:

$sidebar = "<img src='$image->url' alt='$image->description' class='$image->orientation' />";

outputs:

<img src="/site/assets/files/1/bigger-terminal.400x0.jpg" alt="We're gonna need a bigger terminal." class="left">

Share this post


Link to post
Share on other sites

i tried ->orientation , ->orientationField , ->orientationValues but it did not print. i try it again

thanks for your reply

Share this post


Link to post
Share on other sites

i tried it again and it works after i added second image.

thank you!

Share this post


Link to post
Share on other sites

It also works for just one image. If you allow more than one image in field settings you have to get the first image, iterate over or get one randomly. 

// $image = $page->images->getRandom();
// foreach ($page->images as $image) { ... }
$image = $page->images->first();

$sidebar = "<img src='$image->url' alt='$image->description' class='$image->orientation' />";
  • Like 1

Share this post


Link to post
Share on other sites

thank you it works great

how can i translate image standart fields (orientation, description, caption)? i look ImageExtra.module but i can not dare to change anything :)

Share this post


Link to post
Share on other sites

There is already an issue on github. I'll get back to this as soon as I've resolved some other issues...

Share this post


Link to post
Share on other sites

Thanks very much @justb3a for this module, a valuable addition to PW and looks ideal for solving a usability + presentation requirement I have :)

I can see from your blog page how to access the additional attributes via the API and have that working AOK in a template but for an image inserted in a textarea field that uses CkEditor do you know how I can get CkEditor or PW to output the extra attribute I have added? Thanks in advance for any pointers or help :)

Share this post


Link to post
Share on other sites

This is just what I was looking for! 

I have a question, though: How might I go about changing one of the custom fields to a textarea, or even enabling CKEditor?

Share this post


Link to post
Share on other sites

@alan: Sorry I never want to output extra attributes in CkEditor or similar. If you find a solution, please let me know.  :)

@statestreet: This is not possible at the moment, but I've planned to allow markdown in the fields.

Share this post


Link to post
Share on other sites

@justb3a

Sorry I never want to output extra attributes in CkEditor or similar. If you find a solution, please let me know.   :)

Thanks, I'm glad to know this facility is not something I missed :)

I will certainly let you know if I find a solution.

Share this post


Link to post
Share on other sites

Great module, worked fine for me! But since a couple of days, for any reason, it doubles my costum image fields. Updated it to Version 0.0.3 but still the same problem. I dont know what happened. Maybe i did anything wrong? I didn't install any other module in the past days, as far as I know :D.

Here are some screenshots to show you what I mean:

http://www.directupload.net/file/d/4071/vtafnu3t_jpg.htm
http://www.directupload.net/file/d/4071/n592lj7s_jpg.htm  

        

Any ideas what could be wrong?

Thank you!

  • Like 1

Share this post


Link to post
Share on other sites

Great module, worked fine for me! But since a couple of days, for any reason, it doubles my costum image fields. Updated it to Version 0.0.3 but still the same problem. I dont know what happened. Maybe i did anything wrong? I didn't install any other module in the past days, as far as I know :D.

Here are some screenshots to show you what I mean:

http://www.directupload.net/file/d/4071/vtafnu3t_jpg.htm

http://www.directupload.net/file/d/4071/n592lj7s_jpg.htm  

        

Any ideas what could be wrong?

Thank you!

Okay, somehow there seems to be a problem with LanguageSupport and the german package, I uninstalled it and its working perfectly now. Could be a bug or I did anything wrong.

Share this post


Link to post
Share on other sites

This is just a JavaScript/CSS issue. Go to Modules > Core and install the Languages Support - Tabs module.  ;) 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @justb3a,

Just noticed a bit of a critical bug. If you remove one of the "Add other text input fields" the field/column is not removed from the DB. This results in a fatal error and the images uploaded to the field are lost. You have to manually edit the DB table to remove the fields to get things working again.

As a wishlist item, I'd love to see the ability to add select, radio, and checkbox fields as well as plain text :)

Share this post


Link to post
Share on other sites

Hi @adrian,

initially I decided to keep the fields/columns after removing so if you need them again your data/entries are still available. I tested it again right now without any problems. 

Scenario: image field containing 4 image extra text fields, adding some images, removing one text field, editing/adding/deleting images... everything works as expected. Any ideas? (ProcessWire 2.6.22, PHP 5.6.14)

Share this post


Link to post
Share on other sites

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.

post-985-0-74699000-1447329625_thumb.png

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

post-985-0-28869900-1447329642_thumb.png

Share this post


Link to post
Share on other sites

Another critical issue - when using an image extra field within a PageTable, the extra fields show up under the image and appear to be editable. You can make changes to the content of these fields, but of course they don't get saved when saving the main page which is very confusing for the user.

post-985-0-68439200-1447627272_thumb.png

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian,

initially I decided to keep the fields/columns after removing so if you need them again your data/entries are still available. I tested it again right now without any problems. 

Scenario: image field containing 4 image extra text fields, adding some images, removing one text field, editing/adding/deleting images... everything works as expected. Any ideas? (ProcessWire 2.6.22, PHP 5.6.14)

Some more info on that error:

post-985-0-72466900-1447628132_thumb.png

The error is coming from PW itself because it looks like every DB field needs a value for the entry to be successfully saved. You should be able to replicate by removing one of the fields from the comma separated list of extra fields, or by simply uninstalling image extra and then trying to upload an image.

Share this post


Link to post
Share on other sites

Some more info on that error:

attachicon.gifScreen Shot 2015-11-16 at 8.54.52 AM.png

The error is coming from PW itself because it looks like every DB field needs a value for the entry to be successfully saved. You should be able to replicate by removing one of the fields from the comma separated list of extra fields, or by simply uninstalling image extra and then trying to upload an image.

I'm not able to reproduce this behaviour, I'll let the pictures speak for themselves:

  1. added 5 Image Extra fields, added images, filled content, saved
  2. removed 2 Image Extra fields
  3. added one more image
  4. saved page
  5. deinstalled module Image Extra
  6. edit page
  7. added another image, fill description
  8. save page

post-2759-0-64981300-1448018514_thumb.pn

Share this post


Link to post
Share on other sites

:) But I'm able to reproduce the PageLink issue:

post-2759-0-97446400-1448019794_thumb.pn

I'll fix that.

Regarding the PageTable issue: I never used an image field containing extra fields inside a PageTable. I'll test this later.

Share this post


Link to post
Share on other sites

I don't know what to say about the issue with removing extra fields - I am continuing to get that error on different PW installs.
 
But now I have another issue for you. With ImageExtra installed and Maximum Files Allowed set to "1" when I go to upload a second image, the editor actually shows both images. After save, the first one disappears, but without ImageExtra, the second one instantly overwrites the first one. This has been confusing for our users - they think a second image has been uploaded rather than overwriting the first one. I hope you can reproduce at your end.
 
I wonder if it's a simple matter of incorporating some of the new code in: 
https://github.com/ryancramerdesign/ProcessWire/blob/980ce4f0be2054dfbad4a7b334d35bdca42da7da/wire/modules/Inputfield/InputfieldFile/InputfieldFile.module#L438

into your module at:

https://github.com/justonestep/processwire-imageextra/blob/master/ImageExtra.module#L540

 
Thanks!

Share this post


Link to post
Share on other sites

Sorry, I am on a bit of a roll - I really do love this module :)

I don't really understand the "Select the inputfields where the extra fields should be attached." option in the config settings. It lists all the different inputfield types, but the module only works with image field types. I actually tried to see if it works with InputfieldFile, but it didn't even work there. Am I missing something about this setting?

I think a more useful setting would be to control which image fields (the actual fields, not field types) that imageextra is attached to. At the moment the "Image Extra Fields" fieldset is added to the Input tab of all image fields, which I expect most developers don't need - they probably only want them for certain image fields. Does that make sense and sound like a good idea?

Thanks again :)

Share this post


Link to post
Share on other sites

@adrian: Could you please open an issue for each topic on Github?

The select field in module settings allows you to add these extra fields to other ImageFields (for example CroppableImage). I've never tested it with InputfieldFile but I think this should be supported as well.

There could be an additional select list to choose the fields (only list the fields with FieldTypes selected above) but I don't know if this is really necessary. Imagine you add another image field where you want to add extra fields, you had to go to module settings again and select the newly added field. If you don't need it for an image field, just don't touch the settings.  

  • Like 1

Share this post


Link to post
Share on other sites

Hello,

How do you add "InputfieldPageListSelect.min.js" to the module to fix the 0 issue with the link field? 

Ive tried hooking into the "InputfieldPageListSelect::render" but couldnt get it to work.

  • Like 1

Share this post


Link to post
Share on other sites

Hello,

How do you add "InputfieldPageListSelect.min.js" to the module to fix the 0 issue with the link field? 

Ive tried hooking into the "InputfieldPageListSelect::render" but couldnt get it to work.

I think I just modified the ImageExtra module to add it there. Have a go and if you are still having trouble I'll take a closer look.

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