I recently moved my site to a new hosting company. I was unable to transfer the Cache directory because my previous host had a 20mb limitation on compressing a directory. So I have been refreshing the image cache for all sizes used by zpArdoise. I have checked the cache and all the thumb sizes exist yet when you load the pages the behavior is that the thumbs are being created for the first time.
Also is Imagick supposed to be enabled? On my installation it says Imagick unavailable.
Comments
Note that the requirements in the latest version have been updated:
ImageMagick 6.3.8+
Imagick 3.0.0+
I am not familiar with the zpArdoise theme, does it register cache sizes with the cacheManager? Maybe those are not correct.
At any case, if you look at the cacheManager options it does explain how to pick caching requestst to match the files you have already in your cache folder.
I can see the correct images are being created in the cache "only" when I load a page.
The problem is when I tell Admin to cache the images, it reports that all images have already been cached (which is not true). If I select any specific size in admin it reports all images already cached. The only image size that has "actually" been created is the 40 x 40 for admin pages.
I just reinstalled ZP, had no effect.
The only way for this to "go wrong" is for your filesystem to say a file is present when it is not.
I am looking at the cach via FTP client and the files are clearly not there. zpAdmin for some reason thinks thay are ther and they are not.
When I moved I restored database from previous installation which worked fine. Maybe this ies where the issue was introduced, since the cache was empty.
I have selected empty cache when i first started rebuilding the gallery.
For some reason ZP thinks the images are in the cache but when I look in the cache they are NOT there. How do I resolve this???
I am testing with a stock installation of ZP photo and a stock version of zpArdoise, no modifications. I have cleared the cache for testing to witness exactly what is generated when a page is loaded vs a pre-caching request.
Pre-caching with a ZP official theme works fine. Pre-caching with zpArdoise has many issues. zpArdoise had a new release on January 5, 2013. I'm wondering if I had a previous installation all images would have already been cached, and I would never experience these caching issues. Since I moved severs, I witness what happens when pre-caching entire gallery.
First off, if you select any zpArdoise size for pre-cacheing available in the selections, the only size that will be generated is the 40 x 40 pixel size, for admin. I have witnessed this by watching my FTP client.
Secondly, if you select an individual zpArdoise image size, but do not select the admin size box, and then click the "cache the images", the zpArdoise selection will be deselected, and "all admin sizes" will be selected and then nothing will happen.
Also, zpArdoise is registering a slideshow size of 450 but the actual cache size generated when used by viewer is 525. I am using Galleriffic option, so image caching needs to be aligned with gallerific sizes.
I am not positive this is distinctly zpArdoise problem, but I can't duplicate it on a ZP approved theme.
All testing on FF W7, no time to test other browser yet.
The settings in my cachmanager must have existed prior to the new version of zpArdoise, and then were brought to my new database when I installed the backup database from old server.
At some time & version in the past zpArdoise must have registered with cachemanager, but the new version is not. Thats why I think I'm getting the weird behavior when pre-cacheing.
Sorry....my regular job is interfering with all this testing. ;-)
Thats why on other thread I posted I am installing old ZP & old zpArdoise, to see if cachemanager registration was correctly set.
I do no know if zpArdoise will automatically restore the options with the new versions, though. The theme's author will have to address that.
with zpArdoise 1.4.4, I did some improvement on displaying protected image (use getFullImageURL() rather than getUnprotectedImageURL()).
zpArdoise implements galleriffic script which use at least 2 pictures :
- a thumbail of 85*85 (the name in cache is like img_xxxx_85_cw85_ch85_thumb.jpg
- a picture of 525px (img_xxxx_525.jpg)
I don't know anything about cachemanager (I don't use this plugin for my own business) : I don't know how it should be configured for third party theme and how it should be used to generate the cache image.
However, I tried to use the plugin with 2 sizes of pictures to generate :
- zpArdoise : Size 85, Crop width 85, Crop height 85, thumbnail
- zpArdoise : Size 525
(be careful with the Upper letter)
I went to an album, reseted the cache and generated the cache : cache image has been well generated.
so I don't understand where is your problem.
btw : something curious : cachemanager don't check if theme name is correct or not, so I can add a theme wich not exists and it generates cache image for nothing...
Themes have the ability to register the sizes of images they use with the cacheManager. See any of the distributed themes for examples.
Now on my new install with restored database, these old entries in cachemanager do not work. I assume if I delete old zpArdoise entries and enter new ones it will work fine.
I did not see that the bottom row was for new custom entries & assumed that the existing zpArdoise entries were registered by the theme (forgetting that I must have entered them myself months ago).
I am so sorry Vincent to get your attention over an issue that is of my own creation. This gallery is only one project of many websites & I have started to document any changes I make, as it is just too much to remember.
I won't have time to test this for 6 hours or so but I'm pretty sure my assumptions will prove correct.
I had spaces & hyphens in names for new sizes. This should cause an error or be documented in help info for cachemanager, as the "apply" will be accepted as currently coded.
I don't think pre-caching of the images I needed foe zpArdoise were ever being created by pre-caching, They had all been generated by page loads. Inspect the cache with FTP, while pre-caching or page loading to see exactly what is being generated.