Jump to content
Soma

Images Manager (beta)

Recommended Posts

PW Images Manager (beta)

Just a weird little screencast trying to show how it works. (out of date a little, tags now use a textfield for easy copy/paste)

This module allows you to manage images from one central repository. You create a root page "/images/" where you can then add categories and images as pages. From there the new admin page created "ImagesManager" will show categories and images added in a ajax data table, from where you can see and search/filter all images, upload and create new categories and edit images too.

Every image will also show an image tag generated to copy into a textarea. This tag looks like this:

{image=/path/to/image/imagename/, width=200}
The width=100 is the thumbnail size used to output the image.

You can also have additional segment to contain classes:

{image=/path/to/image/imagename/, width=100, class=align_left}
Or you can enter the id directly:
{image=1033, width=100}
Once inserted into a textarea field it will get parsed when saved and loaded automaticly. It will store an abstract id tag in Database and convert it back to the image HTML tag. So after first save you'll see the image inserted in a Wysiwyg and be able to resize and place it as usual. Once it's inserted somewhere Images Manager will show a search link with the pages containing the image (you can configure the fields int the module setting). You can change the image or move it to a different category, it will still work and show the correct image. This also works with multi-language fields.

You can still also use the regular insert image dialog in TinyMCE and chose image from those pages. And it will start keeping track of those as well (they're the same after all).

You can use those central images pages also with page fields to reference them single or even whole categories, search them with API and do what you like.

Images Manager will also parse the page render on front-end and replace any found image tags with the HTML code. It will also look for a description on the image and output it as alt tag. If you want to have multi-language description you can add a `image_description` TextLanguage field to the image page template and have images parser use them.

Along with this module, you can also install the `PageListImageLabel` module to add thumbnails to the image pages in the tree.

To get it working you need to have the basic setup:

1. Create new `image` field with input setting to 1 max image

2. Create new `image` template and add `title` and the `image` field created before

3. Create a 'image-category' template with only title and allow the `image` template and `image-category` as child pages under family settings.

4. Create a `image-root` template with only the title field for the root of the images tree. Allow only `image-category` as child page under family settings.

5. Create the root page with the `image-root` under the home page as "/images/"

6. Done.

The structure of the image repository looks like this

/images/

/cagetory1/

/imagesxy/

/category2/

/image2/

/image3/

Now you can use the ImagesManager to add categories and images. But you can also still use the page tree to add new stuff as usual.

The root path, template names and fields are configurable in the module settings.

How to install the module:

- Download the contents of this repository and put the folder renamed as "ImagesManager" into your site/modules/ folder

- Login in to ProcessWire and got to Modules page and click "Check for new modules". You should see a note that the two new module were found. Install the "ImagesManager" module.

- A new admin page "ImagesManager" should appear in the top menu.

- You may configure the option on the module screen to suit your needs.

Download at github

https://github.com/somatonic/ImagesManager

Thanks and enjoy.

  • Like 31

Share this post


Link to post
Share on other sites

This looks really awesome, Soma! Thanks so much for this (and also for helping me in regards to my image management concerns post). I will definitely be giving this a run... er, once I break through this wall of trouble I'm having with learning PW. In any case, this looks like quite the thing that could help me.

Questions:

How many images can this manager handle comfortably, would you say? And is this something that's server intensive?

Also, is this something that you'd recommend for the general handling of all images, or just the ones that would be reused?

Share this post


Link to post
Share on other sites

Soma, this is awesome!

One minor suggestion: Instead of copying the image code by hand perhaps it is possible to copy it on click with Javascript?

One major improvement: Somehow connect the image manager to a standard image field, so you can also insert existing images to it and / or mix it with single ones. Like I suggested here: http://processwire.com/talk/topic/1188-image-inputfield-like-in-tinymce/#entry10701 I know that we would need a way of symlinking to other images than the ones in the assets/files folder. But you are creative ;-)

Great work!

  • Like 3

Share this post


Link to post
Share on other sites

Bravo! This'll open the flood gates to folk who expect this functionality in whatever CMS they use.

"Somehow connect the image manager to a standard image field" <- An uber image field

I rarely stick images into a wysiwyg editor and I have dreams where the standard image field can either accept an upload or link to another image on another page.

  • Like 4

Share this post


Link to post
Share on other sites

Marty, that is good dream to have (it would be superb feature).

Soma: you are a machine.

  • Like 4

Share this post


Link to post
Share on other sites

Thanks guys!

Yes there I see some room for improvements to select the tag and also show some infos of the image size.

It's impossible to have image field select from those images. It would require a new image fueldtype. But that's not something that has to be connected to ImagesManager but just a field you can select an image page. Thats the great thing about this approach.

But you can do it with a page field easily. I'm doing it. If you use PageListSelect you'll even see the image thumb. And it would also be possible to select multiple or even just categories. This is even better than a dedicated fieldtype.

  • Like 1

Share this post


Link to post
Share on other sites

This looks really awesome, Soma! Thanks so much for this (and also for helping me in regards to my image management concerns post). I will definitely be giving this a run... er, once I break through this wall of trouble I'm having with learning PW. In any case, this looks like quite the thing that could help me.

Questions:

How many images can this manager handle comfortably, would you say? And is this something that's server intensive?

Also, is this something that you'd recommend for the general handling of all images, or just the ones that would be reused?

PW can handle x thousands of pages easily. Image Manager is using ajax based data table to list and search/filter those pages, so it scales infinitely. Also the abstraction of the images in texts uses page ID's searches, and this is pretty fast. So you could go as far as your server limit. It's not more intensive than PW itself. ImagesManager doesn't add a noticeable overhead.

You could use this for all images, but still also use the on page image field where it makes sense. However when sharing images and inserting those in Textareas, I think ImagesManager approach and its abstract feature is a big plus in handling those.

It's still alpha and it's possible some things may change on the way to a first RC. So it's not for use in production yet. 

  • Like 1

Share this post


Link to post
Share on other sites

Nice job Soma! Lots of good thinking here, and I like where you are going with the scalability. I look forward to seeing this in the modules directory. 

Share this post


Link to post
Share on other sites

I just pushed an update to 0.0.2 to github.

Some refactoring and some changes

- changed image tag syntax to use selector string syntax. This is easier to handle and I can use the PW selector class to read key=value easily.

Now supports:

{image=/path/, width=200, height=200, class=someclass, id=myimage, rel=album}
- improved image upload to use the image field settings for max size settings, also improved error handling there

- added some translations string

- changed data table some and added a input for the tag where when you click it will select the tag text automatic for easy copying.

- added modified date (sortable), also fixed some stuff with sortable of other cols

- added size col

- improved data table live search to search for also image description or image description field and title

Planned

- improve upload even more if/where possible

- add easy image delete function

- (Done) add textarea fields setting, to only insert "ImageManager" button to those specified

Any testing or help appreciated.

Thanks

  • Like 5

Share this post


Link to post
Share on other sites

Hey Soma, very cool Manager!
(it's not the first time I say this, but it can't be said to often :) )
 
I want to ask if it is possible and if you find it useful, to include an optional userdefined callback-function that gets invoked in the public function executeUpload() method at line 517. After successful upload and the new ImagePage is saved calling it for example like this:
 

if( ! empty($this->options['userCallbackUpload']) && function_exists($this->options['userCallbackUpload']) ) {
  ${$this->options['userCallbackUpload']}( $imagepage );
}

 
With this, users may have a simple way to extend imagesPageTemplate with some more fields (e.g. for Exif-data). Yes, actually they allready have this option to extend the template or provide an own, but it would only allow to do a manually populating of fields. With a userCallbackFunction it could be done automatically.
 
Is this not of interest for the ImagesManager himself?
You may read Exif-description and IPTC-description fields and populate automatically the ImageDescriptionField. (IPTC has higher priority as EXIF).
 
So, if a user uses IPTC-description the field is allready filled, if not, and Exif-Description is available, this is used.
Downside: If there is unwanted text populated, the user has to change it manually. But with nothing populated automatically the user allways has to do it all manually.
 
Maybe it could be an boolean option: 'Yes, do autopopulate the image description' or 'NO'  ?
 
 
EDIT: approved code for reading this I can provide, - as you've said elsewhere: i'm the 'metadata-man' :P

  • Like 1

Share this post


Link to post
Share on other sites

Hey Mr MetaData!

Yeah sure why not. Since it does add value and it's only optional I think this is good idea to add.

I just went ahead and added support for MetaData in my last commit. You could now add a field "image_exif" and get the EXIF data stored when uploading images. I made the method setMetaData(), which adds the meta data on page/image creation, hookable so you can do a hook on it to store additional data. Not sure if this a good idea but maybe nice to have.

v 0.0.3

  • fixed issue with images getting added twice to the assets folder (hope this is now ok)
  • removed the performance intense pages search for image tags (In my testinstall with 120k pages this result in many second waiting to load the data table.
  • and just output a link on all images to a PW search that will run a search.
  • added EXIF data support.

Let me know if that EXIF data reading is ok, or if it need a more sophisticated method.

You can hook the Meta Data method like this from a autoload module:

$this->addHookAfter("ImagesManager::setMetaData", $this, "hookMetaData");

public function hookMetaData(HookEvent $event){
    $page = $event->arguments[0]; // page that the image will be added
    $file = $event->arguments[1]; // path of file in temp upload folder
    // do whatever you like
    $page->yourfield = "I'm the Meta Man!"; // will be saved to page
}
  • Like 3

Share this post


Link to post
Share on other sites

...

Let me know if that EXIF data reading is ok, or if it need a more sophisticated method.

...

Exif reading is perfect!  :)

We can retrieve the data with

$myExifArray = wireDecodeJSON( $myImagePage->image_exif ); 

EDIT:  Your solution is very elegant. The user who wants to get Exifdata may only add a TextareaField to his image-Template!

---

But there is something with the Textfield not allright: post-1041-0-90412700-1366564393_thumb.jp

I use Firefox on Windows

Edited by horst

Share this post


Link to post
Share on other sites

Hi, it's me again.
 
It would be really nice if we can have a field for IPTC as well:

'imagesIPTCField' => 'image_iptc',

and if you can provide their fieldnames within the hookable method:

$this->setMetaData($imagepage, $this->upload_path . $file, $this->options['imagesEXIFField'], $this->options['imagesIPTCField']);
public function ___setMetaData(Page $page, $file, $fieldnameExif, $fieldnameIPTC) {

If you want to populate IPTC data too:

		// write iptc data if field exists on page
		if($page->template->fieldgroup->hasField($this->options['imagesIPTCField'])) {
			$tmp = getimagesize($file, $info);
			if(isset($info['APP13'])) {
				$iptc = iptcparse($info['APP13']);
				if($iptc) {
					$page->set($this->options['imagesIPTCField'], json_encode($iptc));
				}
			}
		}

Share this post


Link to post
Share on other sites

The hook does already allow you to do any additional custom field saving... Just add field you wish and populate it in the hook.

Thx I'll have a look. Forgot FF isnt consistent across OS. I think I know what it is.

Share this post


Link to post
Share on other sites

The hook does already allow you to do any additional custom field saving... Just add field you wish and populate it in the hook.

Thx I'll have a look. Forgot FF isnt consistent across OS. I think I know what it is.

Allright ^-^ , - but getting the ExifFieldname would be of great help if the user changes the default name: function ___setMetaData(Page $page, $file, $fieldnameExif)

Many thanks!

Share this post


Link to post
Share on other sites

You can already get the settings via the module options.

Share this post


Link to post
Share on other sites

You can already get the settings via the module options.

Yep (ich habs)  :) : $options = wire('modules')->getModuleConfigData(wire('modules')->get('ImagesManager'));

Share this post


Link to post
Share on other sites

Hmm, wire("modules")->get("ImagesManger")->options[key] should be enough :) The module sets the options array in the init.

But you can also get it when you hook setMetaData() with 

$event->object->options['imagesEXIFField']; 
  • Like 1

Share this post


Link to post
Share on other sites

willyc, nope. it's not in modules directory yet!

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 Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      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 BitPoet
      As threatened in Ryan's announcement for 3.0.139, I built a little module for sliding toggles as a replacement for checkboxes. Styling of the input is CSS3 only (with all the usual caveats about older browsers), no JS necessary, and may still be a bit "rough around the edges", so to speak, since I didn't have much time for testing on different devices or brushing things up enough so I'd feel comfortable pushing it to the module directory. But here's the link to the GitHub repo for now:
      InputfieldSlideToggle
      Fieldtype and Inputfield that implements smartphone-style toggles as replacement for checkbox inputs. The visualization is CSS-only, no additional JS necessary.
      Status
      Still very alpha, use with caution!
      Features / Field Settings
      Size
      You can render the toggles in four different sizes: small, medium, large and extra large.
      Off Color
      Currently, "unchecked" toggles can be displayed either in grey (default) or red.
      On Color
      "Checked" toggles can be rendered in one of these colors: blue (default), black, green, grey, orange or red.
      Screenshots

      Some examples with checkbox label


      View all Size and Color Combinations
      Small toggles Medium toggles Big toggles Extra big toggles  









    • By Orkun
      Hi Guys
      I needed to add extended functionalities for the InputfieldDatetime Module (module is from processwire version 2.7.3) because of a Request of Customer.
      So I duplicated the module and placed it under /site/modules/.
      I have added 3 new Settings to the InputfieldDatetime Module.
      1. Day Restriction - Restrict different days based on weekdays selection (e.g. saturday, sunday) - WORKING

       
      2. Time Slots - Define Time slots based on custom Integer Value (max is 60 for 1 hour) - WORKING

       
      3. Time Range Rules per Weekday - Define a minTime and MaxTime per Weekday (e.g. Opening Hours of a Restaurant) - NOT WORKING PROPERLY

       
      The Problem
      Time Slots and Day Restriction working fine so far. But the Time Range Rules per Weekday doesn't work right.
      What should happen is, that when you click on a date, it should update the minTime and maxTime of the Time Select.
      But the change on the select only happens if you select a date 2 times or when you select a date 1 time and then close the datepicker and reopen it again.
      The time select doesn't get change when you select a date 1 time and don't close the picker.
      Here is the whole extended InputfieldDatetime Module.
      The Files that I have changed:
      InputfieldDatetime.module InputfieldDatetime.js jquery-ui-timepicker-addon.js (https://trentrichardson.com/examples/timepicker/) - updated it to the newest version, because minTime and maxTime Option was only available in the new version  
      Thats the Part of the JS that is not working correctly:
      if(datetimerules && datetimerules.length){ options.onSelect = function(date, inst) { var day = $(this).datetimepicker("getDate").getDay(); day = day.toString(); var mintime = $(this).attr('data-weekday'+day+'-mintime'); var maxtime = $(this).attr('data-weekday'+day+'-maxtime'); console.log("weekday: "+day); console.log("minTime: "+mintime); console.log("maxTime: "+maxtime); var optionsAll = $(this).datetimepicker( "option", "all" ); optionsAll.minTime = mintime; optionsAll.maxTime = maxtime; $(this).datetimepicker('destroy'); $(this).datetimepicker(optionsAll); $(this).datetimepicker('refresh'); //$.datepicker._selectDate($(this).attr("id"),date); //$.datepicker._base_getDateDatepicker(); // var inst = $.datepicker._getInst($(this)); // $.datepicker._updateDatepicker(inst); /*$(this).datetimepicker('destroy'); InputfieldDatetimeDatepicker($(this), mintime, maxtime); $(this).datetimepicker('refresh'); */ // $(this).datetimepicker('option', {minTime: mintime, maxTime: maxtime}); } } Can you have a look and find out what the Problem is?
      InputfieldDatetime.zip
       
      Kind Regards
      Orkun
    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      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)
       




×
×
  • Create New...