Search results

EDIT: This is actually completely wrong and I apologize. Turns out this issue is actually caused by some who miss a step in the upgrade process, of which happened with me and a few others. Follow the instructions properly and you shouldn't have this problem!!! This is a problem I ran into...

Nevermind my other post. I figured out that this is actually generated from the PHP and hosting settings of the Domain in Plesk. On domains with PHP 5.3 and earlier, there's a safe_mode option. This is removed with 5.4 and after, however. This is likely actually a bug that it's still inserting...

According to the docs, safe mode isn't even available for 5.5, nor 5.4 in my case. What exactly did you do to change it? I tried a 'sed -i.old -e 's/^safe/\;safe/'' which commented out all the lines that start with 'safe' (all of which were removed) but now all I get is a blank page. Can you...

With PHP 5.4 still set on the site, run a phpinfo() page and there will be a large section on what was used previously for ./configure. For the most part, you can almost copy-paste that into the new ./config, except with some changes (e.g. 5.3 had --with-fastcgi instead of --with-cgi as in 5.4)...

I'm having this exact same problem. The solution saying to run as an Apache module makes no sense nor can I even set it to that (I can only php_handler it to either cgi or fastcgi) and I've ruled out that building from source isn't my issue but rather most likely Plesk not playing very nicely...