courtneycj
Member
Posted 9 months ago #
Hello. I have a wordpress theme on a website run through 1&1 web hosting that I have been struggling to update for a week. I'm not a programmer, so please keep that in mind.
Originally, I couldn't make changes through wordpress because it said my blog wasn't running the right version of php. I fixed that according to the directions 1&1 gave me (changing the .htaccess file in my root menu), and now I can't log in to my dashboard or my blog at all. On both sites, I get a blank page with an error message that says, "Your server is running PHP version 4.4.9 but WordPress 3.2.1 requires at least 5.2.4." I checked with 1&1, and they said everything is running fine from their end.
I don't know what to do. Please help!
The server your website is hosted on does not meet the minimum software requirements needed to run WordPress.
PHP software version on the server: 4.4.9
PHP software version needed to run WordPress 5.2.4
You will need to contact 1&1 and ask them to update the software, or move you over to a different server with PHP 5.2.4 installed. If they cannot do this, you will need to move to a different host that will.
courtneycj
Member
Posted 9 months ago #
Hi, I followed the instructions 1&1 gave me to be able to run PHP 5.2.4 but this is still happening, and the WordPress dashboard (http://mysite.com/wp-admin) is now unavailable to me, whereas it wasn't unavailable when I first started having issues.
What error are you getting?
courtneycj
Member
Posted 9 months ago #
When I type in the URL and go to the dashboard page, it's just a blank web page that says "Your server is running PHP version 4.4.9 but WordPress 3.2.1 requires at least 5.2.4." at the top, just like when I try to go to my website. --> http://www.courtneycjohnson.com
But I followed the directions, so PHP 5.2.4 should be enabled now.
The server might need a reboot before PHP 5.2.4 takes effect. This is an issue for you to sort out with your host.
courtneycj
Member
Posted 9 months ago #
Apparently the htaccess file was no longer saved as .htaccess, and that was causing the problem. Thank you for your help, though!