First, I would like to say that I’ve only had my WP Engine experience because I’m working on somebody else’s website, and that website is hosted at WP Engine. There may be some great advantages to using WP Engine, but I’m not in love.
My WP Engine experience is related to a job I’ve been working on for the last week. I wanted to use wkhtmltopdf to generate some PDFs via PHP. Since wkhtmltopdf is an executable file, it would need to allow executable permissions for www-data (or whatever WP Engine’s user name is for apache). I tried to change permissions via FileZilla, but it couldn’t be done.
Quick note. If you’re having problems generating PDFs with wkhtmltopdf and it’s giving you an error that says it has failed without an error message, make sure you have a good copy of wkhtmltopdf on your server. In my case I had uploaded the file with FTP, and used Filezilla’s auto mode.
Every year I find myself going through my open source projects and changing the copyright notices. This year I’m doing it via the terminal, and it only takes two commands.
First, little background on why I’m writing this blog post… I have a client that has a “semi-dedicated” hosting account. In most respects, this account is just a fancy shared hosting account, but they say there are less accounts on the server. The client’s website is on that hosting account. The client also has a server at another location. I have root access to that server, and the client wants to be able to have that server do direct MySQL queries on the website’s database.
If you are using DOMPDF on a server environment that has a self-signed security certificate, or perhaps the certificate name doesn’t match what it should, DOMPDF will not load images or other assets without specifically creating a stream context that allows it to do so.