Tidypics supports 3 image libraries: default is GD php extension (which is required to be available by Elgg core). And then there's the Imagick php extension (which you would have to make sure it's installed in your XAMPP environment). Lastly, there's the ImageMagick command line option which makes use of the convert command available within the ImageMagick package. The path to the convert command would only be necessary to provide if you want to use the ImageMagick command line tools.

I have to admit that I can't tell for sure if the ImageMagick option works on XAMPP/Windows. I never tried it and as I have no Windows I couldn't even try it. If you provide the full path to the directory where the convert command, i.e. where you installed ImageMagick to - try also with a slash at the end of the path - it either works or it might be the confirmation that it does not work on Windows. You can also try the path on the ImageMagick tab where you would get some version information provided by the convert command if it's found at the path and can be executed.

If the ImageMagick command line tools option doesn't work on XAMPP, you might try to get the Imagick php extension option to work as it's at least better than the default GD php extension because the latter has quite high memory consumption for resizing images with a high resolution. The other two image libary options don't have these memory issue.

Thank you, iionly, for your detailed response.

I installed the ImageMagick PHP extension and everything appears to be working fine.
The TidyPics Server Information tab displays:
             imagick    Enabled    
             exec()    Enabled    Required for ImageMagick command line

My site's production server is Linux, so the ImageMagick path will probably resolve correctly. If I do manage to get the ImageMagick command line tools working without the PHP extension, I'll post the results.

Thanks again.

Use this PR.

In the future, ask questions to the author of the plugin on the plugin's page ;)

I deleted the line 

'filter_id' => 'izap_videos_tabs',

and it is working now. Thank you so much, sorry for posting in the wrong spot!

Thanks for reporting the bug. And thanks for providing the PR already. I'll add the fix in the next release (due to the easy way to correct the problem I won't make a new release immediatelly though).

Don't worry about location you opened the discussion. It's the "Tidypics" group after all. And I got the info about the bug from the posting here, too.

Are you reallly asking about DOWNloading or is it about UPloading?

I don't know of any download size restrictions.

I guess you refer to the default memory limit set by Elgg of 64 megabyte. If you need to increase this value, you can modify the value set for memory_limit in Elgg's .htaccess file in the root folder of your Elgg installation. If you need to increase the value for Tidypics thumbnail creation to work, you might also want to check if the values for upload_max_filesize and post_max_size in .htaccess suit your requirements (upload_max_filesize = maximum filesize of uploaded images; post_max_size >= upload_max_filesize x number of images you allow to be uploaded with Tidypics in one batch).

Suggestion: if you have either the Imagick php extension or the Image Magick package installed on your server, you can select either of these options in the Tidypics plugin settings to be used as image library as both have much lower memory requirements (and provide better resize quality results, too).

iionly - I just found a link with advice (including yours) for changing server timezone in Elgg. https://elgg.org/discussion/view/2412154/how-do-i-change-the-time-zone-settings

Am wondering, if I make this script change will it effect the one album created successfilly since the server change (UTC)? Also, am I right in thinking it will not affect entries made prior to server change  (UTC -  ?

To be honest, I can say for sure if the images of the newly created album will show or not after changing the timezone. My guess is, yes, as I think the real cause of the images not showing (actually any kind of files of the affected users not found) is the <day> part in the path to the users' data:

/path/to/datadirectory/<year>/<month>/<day>/<user_guid>image/<album_guid>

These (sub)directories are created with the timestamp of the account creation taken into account. And the <day> can be different due to the timeshift of different timezones. Afterwards on accessing any files again Elgg again takes the timezone / timeshift currently used into account when determine the path the files are to be found. This part can fail when the timezone has changed.

My suggestion: just try setting the timezone to the timezone used on the old server either in Elgg's .htaccess or in engine/settings.php as soon as possible. The crucial point isn't necessarily the one new album but rather the old albums and profile pictures: will these show up again? If yes, you might lose one new album. But I think it's much easier to fix that (upload again) as compared to trying to get all the old stuff showing up again with different users involved. Also, trying as soon as possible is important as you might get a problem with any newly created accounts now with the new timezone in effect once you return to the old timezone.

Just ask the support of your webhoster about the name of the timezone used on the old server and the add either a line in the <IfModule mod_php5.c> block in .htaccess like

php_value date.timezone 'UTC'

with the timezone name you were told instead of UTC. Or add a line like

date_default_timezone_set('UTC');

in engine/settings.php before the line

global $CONFIG;

Again, enter the timezone name actually been used on your old server.

Eureka - it worked! I entered: date_default_timezone_set('America/Montreal'); in engine/settings.php and the missing images now display correctly. Also, the album created post server move and its comments and the two new user registrations have not been disturbed.

Once again I'm most grateful to you for getting my site working again.  I'll doubtless be upgrading later this year and hope you guys hang together (have been reading some of the debate!). Although complex for a non coder like me, I have found Elgg to be consistently highly stable, flexible and secure and look forward to installing version 2.3.