cancel
Showing results for 
Search instead for 
Did you mean: 
Go to solution

Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

I Enabled PHP 5.6 from my dashboard but after that my wordpress site shows version 5.2.17. Some applications not working, especially my feed not working after changing it to 5.6 from 5.3. What to do ?

6 REPLIES 6
Helper II

Re: Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

Once you change PHP versions, you also have to restart Apache.

 

Unsure how to do this in GoDaddy's system.

 

Likely you'll find an option to do this in the Control Panel.

 

To ensure a restart actually works...

 

First stop Apache + verify your site content no longer serves.

 

Then restart Apache + hopefully you'll see PHP-5.6 show up.

 

Keep in mind, PHP-5.6 is nearing end of life, so best to go to PHP-7.1 instead.

Re: Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

i am using shared deluxe hosting plan and i don't have access to restart option for apache. anybody from godaddy can help me do this to refresh my site?

New
Solution

Re: Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

Go to System Processes (near bottom), another window will show. Click "End Web". This will automatically restart the web system and PHP 5.6 will now be active. Hope this helps.

Re: Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

The same thing happened to me, updated from PHP 5.3 to PHP 5.6. Have restarted service by clicing "End Web" for now 10 times but PHP version is still PHP 5.2.17.

Is it possible that this happens because it is SUNDAY ?

New

Re: Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

Same here. Did it ever get moved to the new version?

Solution

Re: Enabled PHP 5.6 but My Wordpress Site Still Showing PHP Version 5.2.17

After 3 days and 10-20 times of doing Click "End Web", I initiated a Chat through the GoDaddy Hosting panel and one member of support team solved the problem.

I think the problem was in some configuration files of my hosting maybe .htaccess but I am not sure.

Anyway the support guy solved the problem in 2 min.