[Elgg 1.5-1.12 & 2.X - 4.X: Tidypics] v2.0.2
Release Notes
- Support for animated gif thumbnail creation when using Imagick php extension as image library,
- New setting for thumbnail sizes to allow for creation of square-cut / non-square-cut thumbnails images: NOTICE: the CSS of Tidypics is for usage of the default thumbnail size settings, i.e. if you make any changes in the thumbnail settings you will very, very likely need to make also modifications is Tidypics' CSS or the layout will look faulty,
- New option to allow for client-side image size reduction before upload (EXPERIMENTAL! Only for HTML5 uploader),
- New option to allow for client-side removal of exif data (EXPERIMENTAL! Only for HTML5 uploader AND with image size reduction option enabled),
- Check for valid subtype of the entities processed in Tidypics pagehandler views,
- On re-creation of image thumbnails also check if image is included in album image order array and add guid if not,
- Check previous and next image links are valid before displaying navigation elements in image full view,
- Re-work of permission check that evaluates if a user is allowed to upload photos (both in and out of group context) and determines if the "Upload photos" button is shown or not,
- On retrieval of exif data don't expect all sections exists in an image file: check first to avoid php warnings,
- Updated Plupload HTML5/HTML4 uploader to version 2.1.9,
- Improved caching of JS and CSS (and other files) of 3rd party scripts used by Tidypics,
- When using the Widget Manager plugin display/not display Tidypics group widgets according to each groups' settings.
Thanks also to Ismayil Khayredinov for his contributions.
Project Info
Stats
- Category: Photos and Images
- License: GNU General Public License (GPL) version 2
- Updated: 2022-10-10
- Downloads: 146268
- Recommendations: 221
Other Projects
View iionly's plugins
thanks for sharing!
I can't test any Cloudflare issues. Have you updated only Tidypics to 2.0.2 and it stopped working or have you also updated Elgg at the same time? In the latter case it might not be an issue in Tidypics at all. In any case try it with Elgg version 2.2.2 and not with an older version (version 2.1.3 - 2.2.1 don't play well with the html5 uploader due to a backward incomplatible version of jqueryui that has been replaced with the older but BC version again on Elgg 2.2.2).
Version 2.0.2 of Tidpics caches its JS libs differently (actually using the "Elgg 2 way"). I don't know if this could cause a problem with Cloudflare. Or it might be necessary to refresh the Cloudflare cache after the update of Tidypics (or in whatever way Cloudflare works). Or it might be an issue of http vs https usage on your site on the one hand and Cloudflare on the other - though I don't know why this should start to show on Tidypics 2.0.2 and not already with older versions.
@Michele Do you refer to the "Upload photos" button in the title section where you get a popup for selecting the album to upload the images to? I thought you were referring to the html5 uploader form.
How is the usage of CDN configured? Is it done with a plugin or by some other means? Are you sure that the way it is done works on Elgg 2? Are the correct versions of the cached files used matching the versions used in Elgg 2 and what files are cached in the first place?
I think the problem is with the lightbox JS lib of Elgg that is necessary for the album select popup to open in an lightbox popup. The menu item is registed in the usual way with the elgg-lightbox class listed in the link_class attribute. If this results in an error due to the lib not yet loaded even with the button already visible (due to the asyncronous loading of JS code) it's kind of an Elgg core bug - as the same issue would occur also with any other clickable link that used the elgg-lightbox class in the same way to open a lightbox.
It might be necessary to open a discussion topic to allow for a more general discussion of this issue as it would be unnecessary to add a specific fix in Tidypics if the issue needs to be fixed in Elgg core anyway. Nevertheless, it would help to know how exactly you use CDN (and if only to be able to reproduce the issue).