Jump to content
Soma

Images Manager (beta)

Recommended Posts

Great work Soma, thanks for the effort.

Wouldn't it be more consistent to use the widely known Wordpress short code syntax (http://codex.wordpress.org/Shortcode_API)?

[image='/path/imagename/' width='100' class='align_left']

And since there's also already a short code module for PW ... or is there a reason why choosing your syntax over the other?

Keep it up!

Share this post


Link to post
Share on other sites

Hi Soma, only want to drop a short note:

when working with the ImagesManager in a MultiLanguageSite and the current AdminUser has another Language than the default one

when creating new CategoryPages the PageTitle is only set for the current UserLanguage, default-LanguageTitle is left empty!

With PageName, you populate all LanguageFields with the CategoryName. With the TitleField I think the defaultLanguage should be filled too, because it is the fallback for other empty TitleFields.

PS: it's really fun to work with the ImagesManager! :)

Share this post


Link to post
Share on other sites

Great work Soma, thanks for the effort.

Wouldn't it be more consistent to use the widely known Wordpress short code syntax (http://codex.wordpress.org/Shortcode_API)?

[image='/path/imagename/' width='100' class='align_left']

And since there's also already a short code module for PW ... or is there a reason why choosing your syntax over the other?

Keep it up!

I don't know shortcodes and WP anyway and don't know if it's a good idea.

Shortcode module is something different.

I've chosen PW selectors because it works well and is easy to use.

Hi Soma, only want to drop a short note:

when working with the ImagesManager in a MultiLanguageSite and the current AdminUser has another Language than the default one

when creating new CategoryPages the PageTitle is only set for the current UserLanguage, default-LanguageTitle is left empty!

With PageName, you populate all LanguageFields with the CategoryName. With the TitleField I think the defaultLanguage should be filled too, because it is the fallback for other empty TitleFields.

PS: it's really fun to work with the ImagesManager! :)

Yeah I noticed this too and couldn't made up my mind to how it should behave with multilanguage. I will have a try soon, thanks.

Share this post


Link to post
Share on other sites
Great Job, Soma! An image management tool was at the top of my personal wish list. Your module comes close to this desired. It is a promising alpha version ...

However, I have a problem with uploading images. Error message: Class 'PageImage' not found (line 526 of /../site/modules/ImagesManager/ImagesManager.module) In the ImagesManager is a new line with title, category, imagetag, modified and a broken image icon. The file is uploaded to the directory tmp_uploads, the corresponding page in the selected category created. But the picture file does not move in the new asset subdirectory. Did I forget something during installation?

In addition, only the administrator can use the ImagesManager. Other users will only see the button on textarea fields. But has no function.

In the module-config I have entered two special fields under "Textfields used for searching images on pages". However, the button ImagesManager will appear above each textarea field.

Can you help me to make better use the module? 

Thanks.

Share this post


Link to post
Share on other sites

Thanks enibas94 for the feedback and using my module.

There's a permission for the module "images-manager". You can create a new permission with that name and give it to roles that should see ImagesManager page.

There's currently no permission or access handling for the button added to all textarea fields. The "Textfields used for searching images on pages" is originally meant for the module to search for if there's images in the text. But kinda would be the same fields as where to add the ImagesManager button. So while already there, I changed the config to say "Textarea fields you want to use the ImagesManager on."

So it is now used to define what textarea fields you want to use ImagesManager. This is now working for editor users.

As for your error.  Error message: Class 'PageImage' not found (line 526 of /../site/modules/ImagesManager/ImagesManager.module)

Not sure but since the class name is "Pageimage" I guess it has to do with PHP version, because it works for me, but maybe the capital "I" in PageImage is making it not find the class on your environment. 

I changed it to "Pageimage" and committed an update.

Can you let us know if it's working for you now?

Share this post


Link to post
Share on other sites

Hi Soma, thank you for the quick help. Now the upload works for me! Small cause, large effect.

I have also added the permission. Now the editors can feed the ImagesManager. But the button ImagesManager above the text boxes still does not work for these users. The other with the text boxes "used for searching images on pages" I still do not quite understand it. But it will come ... I'm sure.

Share this post


Link to post
Share on other sites

It is working fine, make sure you updated the module with all its files correctly. 

The setting in the ModulesManager you talk about is now called:

Textarea fields you want to use the ImagesManager. A button will appear above those fields.

Add one or more fields separated by a pipe body|sidebar.

Share this post


Link to post
Share on other sites

I just made another update to replace the fields settings with a AsmMultipleSelect for convenience. If you update, you want to select the textarea fields you want to use IM on. You also have to save the module setting at least once to make it work. And maybe reinstall the module to get rid of unnused settings, but not necessary.

post-100-0-42784600-1372755454_thumb.png

  • Like 4

Share this post


Link to post
Share on other sites

Soma, since you pointed me to it specifically, I just wanted to let you know that I was able to use ImagesManager for my project and it fit the bill completely. Thanks for taking the time to work on image gallery management for PW!

  • Like 4

Share this post


Link to post
Share on other sites

Hello,

I just tried your module in a fresh PW install following the steps you outlined in the first post. 

Everytime I try to upload a image I get these two errors:

  • pme_power_foto.jpg - Invalid file extension, please use one of:

  • Missing required value (ImagesUpload)

Any idea what's wrong?

Share this post


Link to post
Share on other sites

No sorry, I have no idea currently. Any more hints to how you set up or reproduce?

Where do you get these errors? 

Invalid file extension, please use one of: ....  (one of what?)

Are the file extensions set correctly for the image field?

Missing required value, means there's no image sent... ?

Share this post


Link to post
Share on other sites

There is one thing I did not mention... I'm using a fresh install but with the Bootstrap profile.

I tried this setup again with the default site and everything is working fine.

Thanks for your help.

Share this post


Link to post
Share on other sites

Hi Soma,

THANKS for this module! ^_^

Is this still true?:

Use at your own risk and it's not recommended to use in production yet.

I have a site about to go into production (I'm about to upgrade it from 2.3 to 2.4 too before it goes live). Would you recommend I not use ImagesManager due to it's Alpha status?

I know if I use it it is at my own risk no matter if you say yes or no :)

Share this post


Link to post
Share on other sites

To be honest, I'm not sure. Yes it's alpha/proof of concept but seems pretty stable and some use it already. But it also means it didn't get any love since then.

I don't think there can happen much as it just creates pages with a image on it. So even you could go and do it without/remove ImagesManager. The parsing part for image tags could also be replaced or handled differently. It's all not things that can break easily or go competly wrong you wouldn't be able to fix somehow.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Soma, I understand completely, it's a 'nice' Module that is not invasive and as you note should it break for some reason I would be able to work-around that with normal PW code and small changes.

Thanks for your fast and helpful comment :)

Share this post


Link to post
Share on other sites

Images Manager is a fantastic and very useful module that I install on every ProcessWire site.  I have a couple of sites on 2.4 and haven't experienced any problems.

  • Like 2

Share this post


Link to post
Share on other sites

FAB! Thanks for the experience and advice cstevensjr :)

Share this post


Link to post
Share on other sites

Hey Soma. Very useful module and it has promise to be just what I need for something I'm working on right now but I have a couple of questions:

First, I need to upload images of a higher resolution but when I upload through the module interface I get an error that the file exceeds the maxFilesize set in the php.ini. The php.ini maxFilesize is set to 10mb and the pics, so far, have been well below that. When I use the standard pw image upload the files go up no problem but error out using the module. I notice you set a maxFilesize => 32 default but when I change that it doesn't make any difference. Can you give me some guidance how to set it to match the limit in the server php.ini? Also it might be worth considering adding an option in the module settings to set the maxFilesize.

Second, I sometimes forget to set the category before clicking upload and I found that rather than throw an error immediately, the module goes through the process of uploading the file first, then throws the error that no category was set. Since the file's already uploaded, it get's left orphaned in the temp directory. I went into the assets > files > .tmp_uploads and found several pics from days earlier still in there. I can't be the only one that sometimes forgets to set a category which means the server could get clogged with orphaned files pretty quickly. Maybe an onsubmit check for the category before upload begins would fix that.

Share this post


Link to post
Share on other sites

Have a read of this: https://processwire.com/talk/topic/2194-flie-upload-max-file-size/

It should help you with your php.ini settings.

Thanks Adrian but if the server php.ini was the problem then any image I upload whether using the images manager module or using the images field that exceeds the limit would fail. Wouldn't it? If I go to a page and use the images field to select and upload a 2mb or 3mb image is succeeds but not through this module.

I'm making the assumption it's not the server's php.ini.

Share this post


Link to post
Share on other sites

I had a similar problem early this morning.  I was trying to upload an image to Images Manager and it would not work.  

post-756-0-09568100-1399312886_thumb.png

This was using the latest version of PW Dev.  I struggled with this for a few hours and then reverted my /wire directory to 2.3.12 and then everything worked again (I could upload images).  A few minutes ago I uploaded version 2.4.1 and it also worked.

I opened an issue on this occurrence in Github.  

Edited by cstevensjr
  • Like 1

Share this post


Link to post
Share on other sites

I had a similar problem early this morning.  I was trying to upload an image to Images Manager and it would not work.  

attachicon.gifpw-latest-dev.png

This was using the latest version of PW Dev.  I struggled with this for a few hours and then reverted my /wire directory to 2.3.12 and then everything worked again (I could upload images).  A few minutes ago I uploaded version 2.4.1 and it also worked.

Where did you get 2.4.1? The latest version I can find is 2.4.0.

Share this post


Link to post
Share on other sites

@digitex, ImagesManager doesn't set a maxFilesize, where do you see this? It uses PW InputfieldFile.module that does set it from the php.ini. I'm not sure in what regard it is different to when uploading on a page, because it should be the same. Though the upload form in ImagesManager is a normal form file input that uploads on submit, while page upload you may using ajax async upload. Anyway it shouldn't make a difference.

Thanks for the suggestion with the missing category parent. Yes, that surely would be possible. While it all works somehow, there's a lot left to be desired. It's still an proof of concept pretty much.

@cstevenjr, are getting this on a new install? I haven't tried yet on latest PW though. Strange. 

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 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-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 Process refunds and send customer notifications 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 (alpha version only available via GitHub) 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 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 Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...