|
bpoux
|
January 7, 2015 at 7:52 pm
Hi,
I upgraded a custom build of EE from version 4.2.8.p to version 4.4.7.p
Initially it requested that I upgrade to PHP 5.4 which I have done. I then did the requested migration with no issues.
I cannot access the Events, Registration and a few other EE admin pages and I am getting a message telling me to upgrade to PHP 5.4.33 because I am running PHP 5.2.17. But I’m not, I’m running PHP 5.4.
Go Daddy hosting does not have anything higher than 5.4 available. I’m not sure how to proceed from here.
Thanks for your time, Rayna
the-tma.org
|
|
Seth Shoultes
|
January 8, 2015 at 12:27 am
Hello Rayna,
It kind of sounds like you are running out of memory on the server. Any idea what your current memory limit is set to?
You might try turning on debugging in your wp-config.php in the WordPress root directory. Can you check your server error logs at all? There may be some tell-tale signs of what’s happening in the error logs. Otherwise see if Godaddy can track down what’s happening when the admin pages are loaded.
|
|
Tony
|
January 8, 2015 at 5:57 am
Just a note on the PHP version notice.
It is a persistent notice meaning it will remain until you dismiss it. If you look on the bottom right of the message there should be a ‘Dismiss’ link. Once you click that the message should be removed and no longer display.
As @seth mentions if you enable WP_Debug within wp-config.php we can see what errors are being thrown.
Also, when you updated, did you do so using FTP and replacing the files or did you delete the current version and upload the newer? (The latter being the correct way to do so without causing errors)
|
|
bpoux
|
January 8, 2015 at 11:41 am
Thank you both – I did overwrite, not upload anew and can see my screens.
I am still getting the PHP error and it is dismissible just wondering why it’s not registering that I have PHP 5.4 running. I changed it specifically for this plugin.
I will look into the memory issue though I don’t think we’re using anywhere near our memory limit.
Thank ya!
|
|
bpoux
|
January 8, 2015 at 11:42 am
**I did overwrite, not upload anew. I just deleted and re-uploaded anew and can now see my screens. (the original sentence made NO sense above)
|
|
Lorenzo Orlando Caum
|
January 8, 2015 at 12:20 pm
Hello again, we do not recommend overwriting when upgrading and there are some changes between the major releases of Event Espresso 4:
4.1.x –> 4.2.x –> 4.3.x –> 4.4.x
Did you follow an update guide for upgrading?
Thanks
—
Lorenzo
|
|
bpoux
|
January 8, 2015 at 1:37 pm
Hi Lorenzo, No, didn’t follow a guide. I received the zip file via email and there were no instructions to do that. but I have since deleted all the files and then uploaded the new copy and other than the PHP error, all seems to be working. Thanks!
|
|
Tony
|
January 8, 2015 at 2:27 pm
I am still getting the PHP error and it is dismissible just wondering why it’s not registering that I have PHP 5.4 running. I changed it specifically for this plugin.
To explain a little more, rather than adding a check on each page load, EE4 checks the PHP version, then (if needed) creates a notice and saves that notice to be displayed. So when you upgrade, it still just displays the saved notice, until dismissed (which deletes the notice).
If you go to Event Espresso -> Maintenance -> System information.
You can check the PHP_Version that EE4 currently detects.
One problem with using FTP and overriding files, happens if we move functions around within different files so say you have 2 files in your version, FileA and FileB.
We move the function from FileB into FileA and clean up the code a little (removing FileB completely), if you then update by overwriting, the new version only has FileA and so overwrites it on your server, leaving FileB as is, the function that was removed, is now still within FileB on your server.
2 functions can not have the same name.
That’s not the only reason, but its an important one. Its not just with EE but any plugin. When manually updating always (after creating a backup just in case) Delete the current version, then Upload the latest.
I know your up and running now, just wanted to at least let you know why this likely happened.
|
