• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

PHP5 index.php in root directory issues

Y

yowzer

Guest
index.php in root directories not parsing after PHP5 upgrade

I tried searching, but I didn't quite find this specific problem described anywhere. I used one of the PHP5 walk-throughs for upgrading PHP to version 5 in Plesk 7.5.x. It works perfectly except for one thing.

Instead of index.php in the root directory, it is being sent as plain text with content-type application/x-httpd-php. It's a very strange thing because PHP is working fine in most places.

In a sample directory tree, all of these work fine:
/blort.php
/pics/
/pics/index.php
/index.php

The strangest thing is that while http://www.mydomain.com/ returns the PHP file as plain text without compiling it, http://mydomain.com/ compiles the PHP and sends the HTML properly.

I am on Plesk 7.5.3 with PHP 5.1.4.
 
This is the one I used:
http://forums.serverbeach.com/showthread.php?t=6125

Even more strange in this whole situation is that when I was going to start some more troubleshooting, everything was working fine. While I hate not knowing what the issue was (I suspect Apache was caching), it's at least resolved now.

I still need to upgrade some PEAR packages for Horde to work, but it looks like things went fine.
 
Back
Top