Hi Danilo,
Apologies in advance for the repetition, but I will walk through the normal steps we recommend to resolve this issue below in order, just to double-check that you have completed all the suggested steps in the correct sequence. Based on the commands that you shared in your post, I am assuming you have a 2.7 installation - if not, be sure to check the correct version of the user manual for your current AtoM version, as some instructions (like how to restart PHP-FPM) may be different.
If I am understanding correctly, you are saying you have already made the recommended change in the Ghostscript policy.xml file described in this thread?
And you have double-checked the SQL modes applied, per these instructions?
In AtoM 2.7, the only SQLmodes that should be set are: ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION. If they are not, then the link above should tell you how to change them.
If yes - did you remember to restart MySQL after making SQL mode changes?
- sudo systemctl restart mysql
Let's also make sure that the filesystem permissions are set properly as AtoM expects:
If you have checked and confirmed that both of the files above are updated correctly and that the permissions are properly set, then now you could try regenerating derivatives. We can run it more quickly by limiting it to just text files (i.e. PDFs), like so:
After that and BEFORE testing would be the time to clear the application cache and restart PHP-FPM - it's possible if you test before doing this that you are still seeing an older cached version of the page:
- php symfony cc
- sudo systemctl restart php7.4-fpm
Remember as well that
your web browser also has its own cache, so you might want to clear this before re-testing, or test in a private / incognito browser window, where the cache is typically disabled by default.
If that still doesn't work, then now would be a good time for us to gather additional information.
- What is the full version number shown in Admin > Settings?
- Have you upgraded recently? If yes, did you follow Option 1 (download the tarball from our website) or Option 2 (install from our GitHub code repository)?
- Does your site have any local customizations or code changes in place, including a custom theme plugin?
- Is this affecting ALL PDFs, or just some of them?
- Do you have any PREMIS rights applied to the affected descriptions?
- Anything else we should know about your installation?
Hopefully with more information, we can provide further suggestions.
Cheers,