Member
I am seeing on some images (seems like the same ones all the time)a black screen with {{ERROR} printed instead of the image.
There seems to be a few posts on this in this forum but if all the images are cached I thought it would be ok.
It seems that the ones that fail are always symlinks but not all symlinks fail.
An earlier post mentioned server space , unfortunately I have no tool to administer that nor am I in theory limited by the hosting service.
I will backup all my earlier test versions and delete them to see if this helps, there will surely be no space limitation then but in the meantime I am open to other causes to check.
Thanks
There seems to be a few posts on this in this forum but if all the images are cached I thought it would be ok.
It seems that the ones that fail are always symlinks but not all symlinks fail.
An earlier post mentioned server space , unfortunately I have no tool to administer that nor am I in theory limited by the hosting service.
I will backup all my earlier test versions and delete them to see if this helps, there will surely be no space limitation then but in the meantime I am open to other causes to check.
Thanks
Administrator
Such errors come form server not being able to process the images. Common reasons memory and server power. It can also be corrupt metadata.
If you host allows try Imagick instead of GD for processing. If available you can switch that on the Options > Image right at the beginning.
If you host allows try Imagick instead of GD for processing. If available you can switch that on the Options > Image right at the beginning.
Member
Can you elaborate a bit on "process the image"?
As far as I know I have a cache image for the sizes required including full size (though it might be a symlink to the actual image).
It seems to only be an issue for the full size image display. I am not asking for anything but the photo to be displayed (no exif data) and only the filename below the image.
Options > Theme > Exif is disabled
As far as I know I have a cache image for the sizes required including full size (though it might be a symlink to the actual image).
It seems to only be an issue for the full size image display. I am not asking for anything but the photo to be displayed (no exif data) and only the filename below the image.
Options > Theme > Exif is disabled
Administrator
> Can you elaborate a bit on "process the image"?
As said before processing means resizing or cropping.
> It seems to only be an issue for the full size image display
Maybe you have set it to be protected. Check your image options.
> Options > Theme > Exif is disabled
That is importing. But if metadata is corrupt it can break image processing even if GD does not preserve it in the resized images (unless that changed unknown to me).
As said before processing means resizing or cropping.
> It seems to only be an issue for the full size image display
Maybe you have set it to be protected. Check your image options.
> Options > Theme > Exif is disabled
That is importing. But if metadata is corrupt it can break image processing even if GD does not preserve it in the resized images (unless that changed unknown to me).
Member
>As said before processing means resizing or cropping.
I believe that I have all the needed images cached. Options > Theme > Crop thumbnails is indeed enabled but I believe that I have all the needed thumbnails cropped.
I don't know what zp will do to "process" a request for the full size image ...
>Maybe you have set it to be protected. Check your image options.
I have
Options > Image > Full image protection
Disable hotlinking is unchecked
cache the full image is checked
I understand this to mean that images are unprotected. A request for an image URL is directly served the image without "processing" ?
Pointing a browser at the URL of the image that is displayed as ERROR get the same result as if I had gone to the album then clicked on the image or clicked on a different image and scrolled right or left to the offending image.
>That is importing. But if metadata is corrupt it can break image >processing even if GD does not preserve it in the resized images >(unless that changed unknown to me).
I can look at the metadata on the file on my mac with preview and it doesn't complain about anything but maybe it is more tolerant
I believe that I have all the needed images cached. Options > Theme > Crop thumbnails is indeed enabled but I believe that I have all the needed thumbnails cropped.
I don't know what zp will do to "process" a request for the full size image ...
>Maybe you have set it to be protected. Check your image options.
I have
Options > Image > Full image protection
Disable hotlinking is unchecked
cache the full image is checked
I understand this to mean that images are unprotected. A request for an image URL is directly served the image without "processing" ?
Pointing a browser at the URL of the image that is displayed as ERROR get the same result as if I had gone to the album then clicked on the image or clicked on a different image and scrolled right or left to the offending image.
>That is importing. But if metadata is corrupt it can break image >processing even if GD does not preserve it in the resized images >(unless that changed unknown to me).
I can look at the metadata on the file on my mac with preview and it doesn't complain about anything but maybe it is more tolerant
Administrator
> I don't know what zp will do to "process" a request for the full size image ...
This explains you questions:
> Options > Image > Full image protection
Zenphoto will not serve the full image directly but via a page. Disable that to get the image directly.
> I can look at the metadata on the file on my mac with preview and it doesn't complain about anything but maybe it is more tolerant
Maybe. Maybe it is not the metadata and your serer is just not powerful enough. You maybe see time outs in logs or memory errors possible.
This explains you questions:
> Options > Image > Full image protection
Zenphoto will not serve the full image directly but via a page. Disable that to get the image directly.
> I can look at the metadata on the file on my mac with preview and it doesn't complain about anything but maybe it is more tolerant
Maybe. Maybe it is not the metadata and your serer is just not powerful enough. You maybe see time outs in logs or memory errors possible.
Member
Administrator
Also check the color mode/profile maybe. It should all be RGB and the color profile sRGB. If color profiles are embedded in the images they also could cause trouble like exif metadata.
Sorry that I cannot help more unless there are specific error log entries.
Sorry that I cannot help more unless there are specific error log entries.
Administrator
> a space in the filename
That should not really cause trouble but not only for SEO I would recommend to avoid spaces and any special chars in file names. Zenphoto would try to clear on upload but the seo_zenphoto plugin must be enabled for that. FTP upload bypasses that naturally but the seo_cleanup plugin can clear file/folder names afterwards.
Another common issue is wrong file/folder permissions the can cause all sorts of issues.
That should not really cause trouble but not only for SEO I would recommend to avoid spaces and any special chars in file names. Zenphoto would try to clear on upload but the seo_zenphoto plugin must be enabled for that. FTP upload bypasses that naturally but the seo_cleanup plugin can clear file/folder names afterwards.
Another common issue is wrong file/folder permissions the can cause all sorts of issues.
Member
Thanks for the tips
I checked a small sample of the files that result in {{ERROR}} and they have Color space RGB and Color profile uRGB and Alfa channel No but so do many of the other photos that present just fine.
There is nothing in the Debug log - in fact it is not even created on the new installs (which I understand is normal if there is nothing to log).
Is there a Debug plugin to manage the various debug flags or is there somewhere to enable them manually?
If so where and which do you suggest?
I have copied the zp install to MAMP and that file is always displayed correctly there.
I have copied the file to another directory on the same shared hosting server and the image displayed correctly the first time I displayed it. (I note that the action of displaying it caused a symlink to be generated and it always displays {{ERROR}} afterwards.
I checked a small sample of the files that result in {{ERROR}} and they have Color space RGB and Color profile uRGB and Alfa channel No but so do many of the other photos that present just fine.
There is nothing in the Debug log - in fact it is not even created on the new installs (which I understand is normal if there is nothing to log).
Is there a Debug plugin to manage the various debug flags or is there somewhere to enable them manually?
If so where and which do you suggest?
I have copied the zp install to MAMP and that file is always displayed correctly there.
I have copied the file to another directory on the same shared hosting server and the image displayed correctly the first time I displayed it. (I note that the action of displaying it caused a symlink to be generated and it always displays {{ERROR}} afterwards.
Administrator
You don't need to enable the debug log. If there is anything to log it will appear in the debug log.
Early/deep PHP server related errors will only be in the server side PHP error log as they happen before anything of ours gets executed. You have to ask your host if you can enable and/or where review that (a good idea to know in any case).
You can also enable several debug modes for extra info for ZP related things via the config file:
https://www.zenphoto.org/news/debugging/
I can only assume that symlinks may not be working correctly on your server although it say they do. Check the permissions of the files maybe.
Early/deep PHP server related errors will only be in the server side PHP error log as they happen before anything of ours gets executed. You have to ask your host if you can enable and/or where review that (a good idea to know in any case).
You can also enable several debug modes for extra info for ZP related things via the config file:
https://www.zenphoto.org/news/debugging/
I can only assume that symlinks may not be working correctly on your server although it say they do. Check the permissions of the files maybe.
Member
For sure something on my host server symlinks is not working as expected.
I copied the directory that had image files that were giving me grief.
I copied the files that were a problem and renamed them without spaces or '(' or ')' (by default my mac renamed images that had the same sequence number with a space and (sequence number) e.g. photo (2).jpg. And I left the "badly" names files there.
After uploading that album and cache to my test copy on the host server I can see that the "poorly" named files still fail while the well named files, use - and not space, underscore or ( or ) then all seems to work for those files.
>I can only assume that symlinks may not be working correctly on >your server although it say they do. Check the permissions of the >files maybe.
Once again - You are correct!
It is enough to know the rules not so important to me to know why it doesn't work (though I think it is clearly a difference caused by the host server implementation or configuration of symlinks).
Let me try renaming all the image files giving me grief and see if the {{ERROR}} problem goes away for good.
FYI the permissions of the files
thumbs - 644
symlink - 777
album directory - 755
I also tried all combinations of the 2 settings for Options > Image > Full image protection and none appeared to make a difference.
I copied the directory that had image files that were giving me grief.
I copied the files that were a problem and renamed them without spaces or '(' or ')' (by default my mac renamed images that had the same sequence number with a space and (sequence number) e.g. photo (2).jpg. And I left the "badly" names files there.
After uploading that album and cache to my test copy on the host server I can see that the "poorly" named files still fail while the well named files, use - and not space, underscore or ( or ) then all seems to work for those files.
>I can only assume that symlinks may not be working correctly on >your server although it say they do. Check the permissions of the >files maybe.
Once again - You are correct!
It is enough to know the rules not so important to me to know why it doesn't work (though I think it is clearly a difference caused by the host server implementation or configuration of symlinks).
Let me try renaming all the image files giving me grief and see if the {{ERROR}} problem goes away for good.
FYI the permissions of the files
thumbs - 644
symlink - 777
album directory - 755
I also tried all combinations of the 2 settings for Options > Image > Full image protection and none appeared to make a difference.