Ok, I corrected one issue. In Debian plugins are installed in /usr/share/wordpress/wp-content/plugins but loaded from /var/lib/wordpress/wp-content/plugins so all plugins are symlinked from /var/lib/wordpress/wp-content/plugins/xyz to /usr/share/wordpress/wp-content/plugins/xyz. This caused SLB to incorrectly figure out it’s own path. For example it would try to load /wp-content/plugins/controller.php/client/css/app.css instead of /wp-content/plugins/simple-lightbox/client/css/app.css
Removing the symlink to /usr/share/wordpress/wp-content/plugins/simple-lightbox and actually installing it in /var/lib/wordpress/wp-content/plugins/simple-lightbox fixed that problem.
So I did another default theme/disable all other plugins round, but still no joy. 🙁
Hi, it looks like you may not have cURL installed and/or configured for local PHP requests.
See here for more information on SLB’s requirements, including cURL support.
Thanks for looking into this. cURL is installed and working fine. Package php5-curl is also installed and the curl.so is loaded in /etc/php5/apache2/conf.d/20-curl.ini and my php.ini has “allow_url_fopen = On”.
I had read the requirements but I don’t know what the statement “cURL must be enabled for local requests” means. Google doesn’t turn up much either. What configuration is needed to enable this? From a bash shell the curl command can download files from my wordpress site just fine.
Ok, I got everything working. It turns out that on Debian simple-lightbox needs to be installed in /var/lib/wordpress/wp-content/plugins/simple-lightbox (as I noticed before) but a symbolic link is also needed from /usr/share/wordpress/wp-content/plugins/simple-lightbox to /var/lib/wordpress/wp-content/plugins/simple-lightbox
This is the other way around of all the other plugins. It seems the apache config uses /usr/share/wordpress/wp-content/plugins (so presence there is needed otherwise apache can’t find the files and returns 404) but the Debian wordpress php code uses /var/lib/wordpress/wp-content/plugins. So a presence there is needed for the php part to work. I guess there is some php code in SLB that doesn’t handle symbolic links well. So for SLB the real files need to be placed in /var and a link in /usr instead of the Debian standard way of placing the real files in /usr and a link in /var.
PS: it seems SLB does not call cURL directly or even through the HTTP API functions. I still don’t understand the “cURL must be enabled for local requests” requirement which was really confusing me.
