update issues from 5.5.2.1 to 5.6.0

Permalink
I am currently running 5.5.2.1 and am trying to update to 5.6.0. However, when I click the update button I get this error:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 79 bytes) in /home2/messiah4/public_html/updates/concrete5.6.0/concrete/libraries/3rdparty/adodb/adodb.inc.php on line 2896

when I should get a confirmation message. Anyone else know how to fix this?

pakigreenl
 
TorstenKelsch replied on at Permalink Reply
TorstenKelsch
If I remember correctly, Andrew Embler said in another discussion that the PHP memory size has to be at least 64 MB (concrete5 runs with less, but it is needed for the upgrade process).
pakigreenl replied on at Permalink Reply
pakigreenl
Thanks for the reply. Do you have the link to that thread so I can see what the solution is to get the memory and what to do once I have enough?
TorstenKelsch replied on at Permalink Reply
TorstenKelsch
http://www.concrete5.org/developers/bugs/5.6.0.1/fatal-error-allowed-memory-size-of-16777216-bytes-exhausted-afte/

You have to ask your web hoster. Some hosters allow their customers to change the settings in a range from some low to some high value. That can be done in the Confixx panel, per example. In my case, there are a few levels from 32 MB up to 128 MB (webhoster.de AG).
pakigreenl replied on at Permalink Reply
pakigreenl
Well I went into my Cpanel. I went to the php config and changed my php version from 5.2 to 5.3. I could not find anywhere to update the php memory. I refreshed the site and all was well. Or, so I thought. everything is in working order with the exception of blog pages on one of my blogs is missing the content block and vimeo block on each page. they aren't just not showing the block. When I enter edit mode they are not there. They were set up in composer and they are still there to be set up. I even created a test page to see if the other ones were stripped. They didn't show in the test page either. Is there something that would be blocking those from the page?

Also, even when logged out the edit bar image remains at the top of the screen:
TorstenKelsch replied on at Permalink Reply
TorstenKelsch
Oh, that’s odd. When I added /dashboard to your web site, I found myself in the backend. That means, everybody could manipulate your system. So, PLEASE DELETE THE LINK IN YOUR POST INSTANTLY!

Please delete the cache – from the dashboard or via FTP (/files/cache, but leave the empty file index.html alone, if there is one; that will keep users from listing the directory).

I don’t have a solution, I’m sorry. I can only say, I had a similar problem some time ago, but in my case the dashboard bar had disappeared. The failure was, there was a line missing in the footer.php of my theme. Look if there is a line at the bottom of your footer file:
<?php Loader::element('footer_required'); ?>
.

And in the
<head>
section of the theme’s header.php file, there has to be a line
<?php Loader::element('header_required'); ?>


/themes/your-theme/elements/header.php or …footer.php
TorstenKelsch replied on at Permalink Best Answer Reply
TorstenKelsch
My guess is that it has something to do with the advanced permission system.

The developers had written somewhere that 5.6.0 is suitable for testing, but a productive web site should only be upgraded to 5.6.0.1. Maybe it had to do with bugs in the permission system.

You could try updating to 5.6.0.1, but I can’t garantee that this will solve the problem.
pakigreenl replied on at Permalink Reply
pakigreenl
That did it. The update to 5.6.0.1 rectified all my issues!

Update = Spoke too soon the top edit bar image remains on log out.

Post update Update = I had to reset many permissions I had previously set correctly. Once that was done only Admins could reach the backend on login and that removed the edit bar. Thank you everyone who helped!
TorstenKelsch replied on at Permalink Reply
TorstenKelsch
I’m glad I could help. And thanks for giving me a Best Answer, much appreciated!