HELP: Site inaccessible after upgrade from 5.4.2.2 to 5.5.0
Permalink
Hello,
I tried upgrading my site "http://www.inmobiliarioaldia.com/" from 5.4.2.2 to 5.5.2.1 but the upgrade failed. I had to revert back and restore a backup to have the site operational again. However, I need to upgrade. The site running in 5.4.2.2 is too slow and I don't like the Dashboard.
I then followed the instructions athttp://www.concrete5.org/documentation/how-tos/developers/manually-... to manually upgrade the site. I managed to manually upgrade the site to 5.5.0. The Dashboard works, everything works and I can access all the pages. However, as soon as I close the browser the site becomes inaccessible. I get a blank page. From IE I get HTTP 500 error. So, I did the process again. Again, I get the site upgraded to 5.5.0 and everything working. I can open many other tabs in the same browser to access the site. However, if I use another browser I can't access the site. It is like the site is private or in maintenance mode, but I checked those settings already and the site is public and maintenance mode is off. Once I close the browser. Everything is gone again and I can't access the site or the dashboard, so I need to repeat the upgrade process.
The upgrade to 5.5.2.1 from 5.4.2.2 hasn't worked at all. At least, I want to be able to stay in 5.5.0 for the moment. Please HELP.
I tried upgrading my site "http://www.inmobiliarioaldia.com/" from 5.4.2.2 to 5.5.2.1 but the upgrade failed. I had to revert back and restore a backup to have the site operational again. However, I need to upgrade. The site running in 5.4.2.2 is too slow and I don't like the Dashboard.
I then followed the instructions athttp://www.concrete5.org/documentation/how-tos/developers/manually-... to manually upgrade the site. I managed to manually upgrade the site to 5.5.0. The Dashboard works, everything works and I can access all the pages. However, as soon as I close the browser the site becomes inaccessible. I get a blank page. From IE I get HTTP 500 error. So, I did the process again. Again, I get the site upgraded to 5.5.0 and everything working. I can open many other tabs in the same browser to access the site. However, if I use another browser I can't access the site. It is like the site is private or in maintenance mode, but I checked those settings already and the site is public and maintenance mode is off. Once I close the browser. Everything is gone again and I can't access the site or the dashboard, so I need to repeat the upgrade process.
The upgrade to 5.5.2.1 from 5.4.2.2 hasn't worked at all. At least, I want to be able to stay in 5.5.0 for the moment. Please HELP.
Hi Andy,
I have access to the server via SSH. What logs should I look for? I may have override some core files in the past but I want to stay away of it. Isn't the new code supposed to replace them? My new 5.5.0 code is in the /public_html/updates folder and site.php has a line to point to concrete5.5.0.
I have access to the server via SSH. What logs should I look for? I may have override some core files in the past but I want to stay away of it. Isn't the new code supposed to replace them? My new 5.5.0 code is in the /public_html/updates folder and site.php has a line to point to concrete5.5.0.
your php error log and apache error log. Where they are will depend on the Linux distribution you are using.
By overrides - I mean do you have any files in folders such as /root/elements/ or any other of the root folders to override core files. For example if you look in /root/elements is there a header_required.php in there (this is a wild stab in the dark)?
By overrides - I mean do you have any files in folders such as /root/elements/ or any other of the root folders to override core files. For example if you look in /root/elements is there a header_required.php in there (this is a wild stab in the dark)?
there are not files under /public_html/elements. header_required.php and other files are under the /public_html/concrete/elements folder. I found the following errors in the server's error log:
[13-Sep-2014 11:37:26] PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
[13-Sep-2014 11:37:26] PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
[13-Sep-2014 11:37:40] PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
Any ideas?
Thanks,
Alejandro.
[13-Sep-2014 11:37:26] PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
[13-Sep-2014 11:37:26] PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
[13-Sep-2014 11:37:40] PHP Fatal error: Exception thrown without a stack frame in Unknown on line 0
Any ideas?
Thanks,
Alejandro.
ouch! I've never seen that message before. But I had a quick search and I did find a thread which mentions it:
http://www.concrete5.org/community/forums/installation/solved-excep...
Some of he comments imply that it may be a custom template - which is kind of along the lines of what I was thinking - some incompatibility with the new version somewhere in some added code.
If it were me and I needed the site back up I'd roll back to 5.4.2.2 - then I'd download and run in a dev environment - remove any custom templates and run the upgrade locally until I found the problem.
You might get lucky and someone else might see the thread who has acutally seen and resolved this error.
http://www.concrete5.org/community/forums/installation/solved-excep...
Some of he comments imply that it may be a custom template - which is kind of along the lines of what I was thinking - some incompatibility with the new version somewhere in some added code.
If it were me and I needed the site back up I'd roll back to 5.4.2.2 - then I'd download and run in a dev environment - remove any custom templates and run the upgrade locally until I found the problem.
You might get lucky and someone else might see the thread who has acutally seen and resolved this error.
Thanks Andy, I had to restore the backup and the site is accessible again and I'm back using concrete 5.4.2.2. I have to figure a way to upgrade though. Now, there are certain sections of the Dashboard that don't work, like "System & Settings" and "Extend Concrete5". That means I can't install new plugins, etc, but at least the site can be accessed now by the end users.
There's something odd with my old code that is causing issues with the upgrade, even when doing manual upgrade. Do you know if instead running an upgrade, it is possible to perform a fresh install of concrete 5.5.2.1 or 5.6.X to another URL and then migrate the data and switch back the URL?
Please let me know if you have any ideas. Thanks again for all your help.
Alejandro.
There's something odd with my old code that is causing issues with the upgrade, even when doing manual upgrade. Do you know if instead running an upgrade, it is possible to perform a fresh install of concrete 5.5.2.1 or 5.6.X to another URL and then migrate the data and switch back the URL?
Please let me know if you have any ideas. Thanks again for all your help.
Alejandro.
Hi Alejandro,
I'm a little worried when you say certain sections of the dashboard don't work.
Is it more than one section or is it just the extend concrete5 page?
The reason I ask is - if it is multiple sections in your dashboard that would imply you may have some broken core code and we cannot easily verify the integrity of your installation.
If it is just the extend page then it might only be a broken/rogue add-on that is causing your problem - and is likely causing your upgrade issue as well.
If it is only the extend page then we need to know what the error is.
Go to logging and turn on the setting to display errors in the page and then go to extend concrete5.
If you don't get an error in the page then you'll need to check your server log again to track down the error message - this should give us a clue why that page is not working and if it is a problem with a plugin work out which one it is.
If you have multiple broken pages in the dashboard then that's a different matter.
Does that make sense?
I think if you want to migrate all of the site pages into a fresh instance of 5.6.3.1 you'd pretty much have to recreate everything manually.
I'd check and see if your problem just comes from a broken plugin first.
I'm a little worried when you say certain sections of the dashboard don't work.
Is it more than one section or is it just the extend concrete5 page?
The reason I ask is - if it is multiple sections in your dashboard that would imply you may have some broken core code and we cannot easily verify the integrity of your installation.
If it is just the extend page then it might only be a broken/rogue add-on that is causing your problem - and is likely causing your upgrade issue as well.
If it is only the extend page then we need to know what the error is.
Go to logging and turn on the setting to display errors in the page and then go to extend concrete5.
If you don't get an error in the page then you'll need to check your server log again to track down the error message - this should give us a clue why that page is not working and if it is a problem with a plugin work out which one it is.
If you have multiple broken pages in the dashboard then that's a different matter.
Does that make sense?
I think if you want to migrate all of the site pages into a fresh instance of 5.6.3.1 you'd pretty much have to recreate everything manually.
I'd check and see if your problem just comes from a broken plugin first.
Hi Andy,
The sections that do not work from the Dashboard are: "Extend concrete5" and "System & Settings". When I click "System & Settings" gives me a Page not found error. The click in "Extend concrete5" simply doesn't bring any content.
Additionally I noticed there are other sections that used not to be there before that do not bring any data either, like "Scrapbook", "Stacks & Blocks", "Welcome to concrete5", "Customize Dashboard Home". Also, I used to configure new site members with "User and Settings" but now it is called "Members". It looks to me that it may be using some mixed code between 5.4.2.2 and 5.5.0, the version I attempted to go to.
The following error is coming up in the server everytime I click one of the above pages that do not work:
[14-Sep-2014 20:32:37] PHP Fatal error: Call to a member function getCollectionID() on a non-object in /home1/inmobim4/public_html/concrete/blocks/autonav/controller.php on line 256
Regards,
Alejandro.
The sections that do not work from the Dashboard are: "Extend concrete5" and "System & Settings". When I click "System & Settings" gives me a Page not found error. The click in "Extend concrete5" simply doesn't bring any content.
Additionally I noticed there are other sections that used not to be there before that do not bring any data either, like "Scrapbook", "Stacks & Blocks", "Welcome to concrete5", "Customize Dashboard Home". Also, I used to configure new site members with "User and Settings" but now it is called "Members". It looks to me that it may be using some mixed code between 5.4.2.2 and 5.5.0, the version I attempted to go to.
The following error is coming up in the server everytime I click one of the above pages that do not work:
[14-Sep-2014 20:32:37] PHP Fatal error: Call to a member function getCollectionID() on a non-object in /home1/inmobim4/public_html/concrete/blocks/autonav/controller.php on line 256
Regards,
Alejandro.
also Andy, how can I install a brand new instance of 5.6.3.1 to a new folder and then make it point to the same domain when everything has been recreated? Appreciate any pointers. You have been a great help. Thanks for your time.
Hi Alejandro,
it all sounds pretty messed up. You've restored the 5.4.2.2 database but you're seeing (at least) parts of the 5.5 or 5.6 codebase in the backend.
When you rolled back did you change the config/site.php to remove the pointer from the updates directory?
That is likely the last thing I'd check before moving on to a fresh install of 5.6.3.1.
To do this you'd need to create a new blank db
create a subfolder you want to run it in and add your 5.6.3 code in there
Run the install as you would do normally
When happy with the installation and you have everything setup you'd need to alter your root .htaccess to rewrite the new folder.
There will be a how to somewhere on the site on how to accomplish this - I can't remember the specifics off the top of my head.
it all sounds pretty messed up. You've restored the 5.4.2.2 database but you're seeing (at least) parts of the 5.5 or 5.6 codebase in the backend.
When you rolled back did you change the config/site.php to remove the pointer from the updates directory?
That is likely the last thing I'd check before moving on to a fresh install of 5.6.3.1.
To do this you'd need to create a new blank db
create a subfolder you want to run it in and add your 5.6.3 code in there
Run the install as you would do normally
When happy with the installation and you have everything setup you'd need to alter your root .htaccess to rewrite the new folder.
There will be a how to somewhere on the site on how to accomplish this - I can't remember the specifics off the top of my head.
Hi Andy,
I did modified the config/site.php and removed the line that pointed to the updates directory. I don't really know what is going on. The other idea I had before doing everything over and starting fresh is to download 5.4.2.2 code and replace my current concrete folder completely to see if that works with the restored backup.
Anyway, I'll let you know how that goes.
Regards,
Alejandro.
I did modified the config/site.php and removed the line that pointed to the updates directory. I don't really know what is going on. The other idea I had before doing everything over and starting fresh is to download 5.4.2.2 code and replace my current concrete folder completely to see if that works with the restored backup.
Anyway, I'll let you know how that goes.
Regards,
Alejandro.
Hi Andy,
I reinstalled a clean concrete instance with 5.6.3.1 and copied everything to the new site. Thanks for all your assistance.
Regards,
Alejandro.
I reinstalled a clean concrete instance with 5.6.3.1 and copied everything to the new site. Thanks for all your assistance.
Regards,
Alejandro.
glad you sorted it out - sorry we couldn't find a way to shortcut having to do the whole thing again.
are you able to look in n your server error logs: this would be helpful as you could narrow things down if you can see more info about where the problem is occurring?
Are you using any overrides? Specifically have you overriden any core files such as /concrete/elements/header_required.php - or any other files?