(2015-04-21, 22:56:33)shawn_a Wrote: Yeah i thought the width and height were for auto thumbnails, not manual cropping, since every item had a thumbnail field in output.
so here is my list now that I understand how it works.
* Auto thumbnails would be a nice feature
* Move name/ID as the primary field on edit and column list instead of the second field, would be better UI and less confusing.
* If manual thumbs and no thumb exists, do not output a partial path in "thumbnail" output as it does now
PHP Code:// blank thumbnail, should be null, or not exist
'thumb-0' → array•3 {
'filename' → str•20 'ExtraGallery/thumbs/'
* thumbnails are not publicly accessible
/data/ExtraGallery/thumbs is a private store, and not public
GSTHUMBNAILPATH would be a better place for thumbs, and use your own prefix for the filenames as is standard, gsgallery.name.ext
* regenerate any auto thumbs if settings change, or offer the manual ability to do so.
* add fancybox to images
shawn_a,
From your list I'm planing only to fix bug with partial path when no thumb generated.
Auto generating thumbnails is already implemented, please see ExtraGallery settings and my previous reply.
/data/ExtraGallery/thumbs location is public accessible, it works, I'm using it on many web pages. I've prefer this location for better control of unused thumbnails and to prevent some misleading when user uploads image and GS generates automatically it's own thumb in GSTHUMBNAILPATH (name of thumb may be name that ExtraGallery will false positive recognize as it's thumb).
Plugin updated, v.1.02
http://flexphperia.net - my portfolio