Upgrade to 5.3-Exit Edit mode hangs

Permalink
After the upgrade from 5.2 rc (or thereabouts) to 5.3 I cannot exit out of edit mode anymore. It just hangs and spins forever.

* Clearing the cache doesn't help.
* Deleting the cache directory manually doesn't help.
* Restarting apache and mysql doesn't help.
* Turning off the cache in debug settings doesn't help (in fact with this off I still notice cache file do get created).

I am running on windowsxp using xammp, which has worked fine till the 5.3 upgrade. E.g. here is the page I am accessinghttp://localhost/concrete5/index.php/contact/... and there are the cache files C:\xampp\htdocs\concrete5\files\cache The reason I mention cache files is that there have been others with this problem in the forums and some have resolved their issues by clearing the cache e.g.http://www.concrete5.org/index.php?cID=4952... No such luck for me.

Help! I can't edit anymore.

abulka
 
frz replied on at Permalink Reply
frz
did this end up working for you again?
abulka replied on at Permalink Reply
abulka
No change in my situation. Don't know what to try next. Scanning the forums, it seems that I am not the only one with exit edit mode problems - perhaps there is a subtle bug somewhere?
Remo replied on at Permalink Reply
Remo
Does it work if you set up a new site?
Would probably helpful to know if it is caused by the upgrade or not..

I guess there are no javascript errors?

I've seen that the exit mode doesn't work with some themes. Mind trying to change the theme?
Jotun replied on at Permalink Reply
I just ran into the same problem with a new installation, first time I see it after editing pages all day. Tested it with many browsers, even tried re-logging..nothing works. Says Edit Page instead of Exit Edit Page, when I click it it spins forever. I don't get any errors or anything. I tried clicking approve this version link in a different browser but nothing happens there either. Some help with this would be great.
frz replied on at Permalink Reply
frz
goto your dashboard > settings >debug and clear the site cache. Clear your browser cache as well, try again.
Jotun replied on at Permalink Reply
Thanks Franz that fixed it.
abulka replied on at Permalink Reply
abulka
Wow - upgrading to concrete 5.3.1 seems to have fixed the problem.

I had the default theme that came with concrete by the way. Clearing caches never worked for me. I didn't try a reinstall / new website - I was going to - but the new concrete 5.3.1 fixed the exit edit mode problem.

P.S. When I accessed the page after the upgrade (from 5.3.0 to concrete 5.3.1) I finally got the prompt about saving the edits. Its like its been waiting weeks to get out of edit mode!
ringo replied on at Permalink Reply
In version 5.3.1? My edit bar now is totally invisible since upgrading. Very annoying as i cannot get anything done!
katz515 replied on at Permalink Reply
katz515
Did you clear your browser cache?
ringo replied on at Permalink Reply
cleared the application cache as well as browser cache. There is extra whitespace where the edit bar should be but it contains no buttons! Very very weird. I have no idea how to fix this now.
ringo replied on at Permalink Reply
from my page source when i look at it. The javascript files are all added ok but there are no divs to contain the ccm type area e.g.

<div id="ccm-dashboard-page">

there are no tags at all with ccm related classes or ids! Why would this be happening? I call the 'header_required' element in my page header but this always worked as expected. I really have no idea what is going on here. please help!
frz replied on at Permalink Reply
frz
is it possible you didn't get all the files up there for your upgrade ringo?

your issues sound super rare and pretty deep so I wonder if something large is perhaps missing?
katz515 replied on at Permalink Reply
katz515
One thing that I can think of it... is...

If your server is running additional caching such as eAccelarator, you may have to restart your Apache...

I don't recall if you are non-English user.... but if so... sometime I had to restart Apache because gettext cache the .mo file and it corrupted my Meny before.

Pretty much... next thing I would suggest is to restart Apache... but I don't know if you are using shared hosting or VPS/Deficated...