I understand the following topic is very old and didn’t want to bump it as it appears the preference is for new topics to be started.
May I make the suggestion that the above is added to the wiki page here? It took me about 40 minutes of searching to figure out why, despite following all of the necessary steps, my instance kept telling me snappdf was not installed or enabled.
Thanks for the reply. I figured it out and that matters more to me.
There is nowhere on that page in the documentation, nor in the installation docs, that tell admins that after the .env file is updated on an existing instance, to run php artisan optimise for the change to snappdf to take effect.
Interesting. It wouldn’t work for me until I ran that command. I’d even rebooted the VM and it didn’t do anything until after doing that. Now PDFs are fine on my install.
Yes, that is correct. I ran it on my initial installation (about 15 months ago) and then also whenever I do an update via CLI, I need to run that. Otherwise the update won’t take.
One way to test this would be to temporarily change the mailer to log in the .env file (without running optimize) and then use the health check in the app to check the current setting.
So I set email back to smtp and tested by changing PDF generator to hosted_ninja without running php artisan optimize and as before, there were no changes within the Health Check.
For further testing, I did run php artisan optimize and the changes were enabled and Health Check said that snappdf was not enabled, as expected. I then repeated the steps in reverse. First without optimize and no changes were made. Then followed by optimize and changes were made and then visible in the Health Check.