As mentioned in this thread.. https://xoops.org/modules/newbb/viewtopic.php?viewmode=flat&type=&topic_id=61462&forum=14 I’ve gone ahead and re-coded the imagemanager.

I’ve done this for my own use so while I’ve tried to keep it xoopified as much as possible I have taken some shortcuts to get it running. Mostly this is hard coded text rather than language variables.

I’m not a born coder so this is at your own risk. I’ve tried to make it as secure as possible.

If anyone wants to help with this, take it over or absorb some of it into the core than that would be fantastic.

Basic concepts:
Uploaded files are stored as they are originally uploaded. Resized images are generated as required from the original uploads.
Users have their own upload directory that they use to manage their own images.

Improvements over original imagemanager:
Higher quality images produced when using Imagemagick
Quicker access to a user’s commonly used images
Images only need to be uploaded once for use at different sizes
More intuitive and attractive to use

Things missing from the original imagemanager:
Database storage of images
‘Friendly’ image names
Mime type data

Possible Further features:
Resize and crop images in the imagemanager


Download files here.. http://www.mediafire.com/?9fbt2d4ttwx

You can test it here .. http://xoopsforever.x10hosting.com
With username and pass combos: test1111/test1111 test2222/test2222 test3333/test3333

Screenshots and code extracts follow….

After clicking the imagemanager button the user would see their own images. Other users cannot see these images unless they are used somewhere on the site:




If they click the 'Site Images' tab they then see the images all users have access to:




This is the 'user image detail' screen where the user can choose the image size to use or delete the image:




Same screen but for site images (no delete button):


Finally the user can add the image to their post etc..



I've realised the above might be confusing as some images appear in both the user and site wide screens. The user's images wouldn't show in the site images unless they'd uploaded them to both areas

I'll try and explain how some of the code works - if anyone spots improvements or problems let me know!

The new image manager creates directories on the server to store the images. This code creates either a directory matching one of the sections added in the images part of XOOPS admin or a directory for the user.

It also adds an .htaccess file to secure the directory

I won't paste all the code here but the function...

function im_manager_createThumbnail($source,$thisActiveDir)

creates thumbnails in the cache folder. The new imagemagick command makes much better quality thumbnails than the previous code.

I think rather than droning on through the code it's probably better if I go through how the system works. There's lots of commenting in the code to explain it anyway.

In the old imagemanager all the images are stored in a single directory.

In this system each of the sections from the XOOPS image admin has a directory on the file system. In addition each user can have their own directory. These are created the first time the imagemanager is started by a user for a user's own directory or a section from the admin area is selected in the imagemanager.

When an image is uploaded it is stored in one of these directories as an exact copy of the file on the user's PC.

If a user views their own images or the site's images a thumbnail is created of the relevant files and stored in the /cache folder. The user is shown these thumbnails on the screen.

Selecting a thumbnail shows a preview of the image (again generated and then stored in the /cache folder). The user can choose the size of image required and the alignment. If the user is viewing their own images they have the option of removing the image from their area (this only removes the original uploaded file).

Finally the file they've selected is created at the size chosen and moved to the upload folder. They can then press a button to add the image display code to the page.

Short Version!: Images are uploaded to a specific directory for storage. All the images shown on the site are created from this original. Thumbnails and previews shown while using the imagemanager are stored in the cache folder. If an image is selected to be shown on the site a copy is made of the original and this copy is stored in the /uploads directory.

This is very nice!!!! Congratulations!

cool....thank you xgarb...

this should be improved and included in XOOPS 2.3

i heard 2.3 beta will be release soon..maybe the core team can include it in 2.3 rc

Excellent improvements.
Let's see how to adopt into our next release. Or to modularize image management functionality.

Feel free to use it however you like. My code will need some work to integrate it properly into the core.

I've always thought a user and site file manager would work well in XOOPS with areas for storing images, mp3s, video etc.

I usually favour features being 'modulalized' but in the case of a file manager I wonder if it would be better in the core so all modules would use the same system.

Maybe a core module so it's a module but always comes with the core?

Woah !!
It's like a dream... but it's true

Thanks xgarb x1000 !!!