• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Plesk 8.0.1 and FC4 not compatible with PHP5?

S

Spazholio@

Guest
Ok, short and sweet:

Last week, we purchased another server to replace our old one which was running 7.5.4, PHP4 and FC2. We set up the new server, migrate all our domains, only to discover that most of our Gallery and WordPress installs are b0rked, giving us safe mode-like errors, even though safe mode is turned off for those particular domains. The kicker here is that when we tried to re-set up WordPress from the App Vault, it claims that it needs PHP4.x.x, and we have PHP5.x.x and it therefore can't continue. What the heck have we done wrong, and what can we do to resolve it?

ANY information shedding light on this would be appreciated.
 
I don't know if it will help in your situation but to get the appl vault to install with PHP5, edit the following file for each appl in the vault:

/usr/local/psa/var/cgitory/$appname$/info
*info.xml*
<APACHE_VHOST name="PHP" value="on" />
<DATABASE type="mysql" name="" username="" passwd="" host="localhost" />
<VERSION name="PHP" value="4.1.0" rel="ge" />
 
While that is completely do-able, and may be a temporary kludge to get it to work, what I want to know, essentially, is where we screwed up. It's pretty obvious we have, I just need to know where. =)

Once we know that, I may be able to correct the oversight, or just get another server, and do it properly (with CentOS this time).

I've been googling for others having the same issue, and I just haven't seen anyone else.
 
Back
Top