February 28, 2016 at 8:20 pm #25912
I am on the Diagnostic Tool page. I am able to successfully handle JPG, PNG and EPS.
However, the metadata pages comes back with nothing after 30 minutes. I have run the test several times, just to see if I was missing anything, including after getting some permissions set up based on another support topic.
I have ImageMagick running. I do not have show_exec disabled in php.ini.
I did not see this in the forums, but based on the “Force alternate metadata reading” checkbox on the settings page, I just installed ExifTool on my server. Apparently the path to ExifTool was set, because I can run it from the root.
The metadata test page is still not working, though. I am out of ideas. 🙂
(Edit: I haven’t tried the alternate reading option, yet. I’d rather not if it’s not the best way and unless I have to.)March 3, 2016 at 1:18 pm #25936
Metadata reading is done via shell_exec, not show_exec, as is writing. If shell_exec does not work, it then tries to use a built in PHP function that is inferior, but may still work. However, without shell_exec, you cannot write metadata.
If this is taking 30 minutes, there is something wrong with your setup. The metadata writing/writing has no reason to hang, and should either fail or succeed and that’s it. Diagnosing this myself would take time so you’d have to submit a support request or try to test stuff yourself and I’ll provide you feedback when I can here.March 3, 2016 at 1:19 pm #25937March 3, 2016 at 1:43 pm #25938
I actually meant I waited at least 30 minutes before giving up, not that it took that long.
I’ll take a look at shell_exec first, then at the alternative.
Edit: Oh yes, I did have a typo above. I meant shell_exec. And it shows as enabled on the Symbiostock settings page.March 3, 2016 at 1:50 pm #25939
The force alternative does immediately come back with the ability to read metadata.
I don’t really have a need to write metadata to the image itself, so that should be just fine. As long as updates to the gallery/product will be written to the database for use in the site itself.March 3, 2016 at 2:01 pm #25940
Okay, so the one thing you might want to check is the permissions on the actual exiftool command and perhaps even its directory. It needs to be executable. This is something Symbiostock checks for, but your install has already demonstrated having issues with setting permissions, so you may manually have to do this.
This may also pose a problem when you update Symbiostock as exiftool will get overridden and you may have to re-set the permissions, if that is indeed the issue, which I’m pretty sure it is.March 3, 2016 at 4:00 pm #25941
I set ownership of the Symbiostock plugin folder to the WordPress user, so now turning <i>off</i> the force alternate (which means I guess I’m using ExifTool now) still comes back with read but not write.
I had actually installed exiftool and put it in the path on the server because I didn’t realize Symbiostock came with it. I uninstalled it from the server, but same results.
But, that’s fine. As long as I can read the EXIF, then all is good.
Thanks again, Robin. I know we all appreciate the time you take to help 🙂March 3, 2016 at 5:18 pm #25942March 4, 2016 at 4:52 pm #25952
Based on the ownership command I gave, here are the rights to Symbiostock’s exiftool:
As I was saying, before this ownership change, the exif reading/writing did nothing. After the above change, it reads exif. Which is good enough.
Honestly, my next question about handling Sony RAW (.arw) files will hopefully garner more of your attention in the next couple of days.
Robin, your patience and enthusiasm is very much appreciated!! I can’t say it enough. 😉
You must be logged in to reply to this topic.