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 gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...