Pushing Save after Edit causes C5 to get stuck in wait mode or keep trying.
Permalink
Summary of what is used and possible needed info:
C5: 5.5.1.
Browser: Firefox.
Hosting Provider: WebHostingWholesale (WHW1).
Installation fine, no problems.
Server speed excellent.
Site comes up fine.
No problem logging in.
I have cleared caches.
I have restarted computer.
Problem reproducible upon demand.
Problem: Pushing Save during editing of a block causes getting stuck in wait state. Waiting to save never stops.
Process: Login as Admin>>Go into Edit mode>>Try to edit any block.>>Click Save>> Watch swirling graphics indicating to wait>>Swirling graphics continues, and waiting never stops.
Eventually, I need to close that edit window and reload the page, since the swirling graphics does not go away. The editing that was done does not get saved.
I recently found out that clicking multiple times on the Save while the swirling graphics is showing helps on occasion to save the edits. Not sure if waiting between the clicks makes difference or not, but I think maybe waiting and clicking save again works better than clicking fast; don't really know without more testing.
I also posted about the above problem herehttp://www.concrete5.org/index.php?cID=144422&editmode=...
----------
Update 3/11/12:
Based on response from WebHostingWholesale and another post here that made me think (even though not related), I now found that the problem does not exist when I make use of IE. My Firefox is currently 3.5, and so it may be a browser compatibility with Concrete 5, since it works with IE. It is hopeful seeing it work on IE, and WOW, Concrete 5 is FAST. Works very well. Got to say, NJ. But need it working with Firefox. Of course I'll check on updates for Firefox.
C5: 5.5.1.
Browser: Firefox.
Hosting Provider: WebHostingWholesale (WHW1).
Installation fine, no problems.
Server speed excellent.
Site comes up fine.
No problem logging in.
I have cleared caches.
I have restarted computer.
Problem reproducible upon demand.
Problem: Pushing Save during editing of a block causes getting stuck in wait state. Waiting to save never stops.
Process: Login as Admin>>Go into Edit mode>>Try to edit any block.>>Click Save>> Watch swirling graphics indicating to wait>>Swirling graphics continues, and waiting never stops.
Eventually, I need to close that edit window and reload the page, since the swirling graphics does not go away. The editing that was done does not get saved.
I recently found out that clicking multiple times on the Save while the swirling graphics is showing helps on occasion to save the edits. Not sure if waiting between the clicks makes difference or not, but I think maybe waiting and clicking save again works better than clicking fast; don't really know without more testing.
I also posted about the above problem herehttp://www.concrete5.org/index.php?cID=144422&editmode=...
----------
Update 3/11/12:
Based on response from WebHostingWholesale and another post here that made me think (even though not related), I now found that the problem does not exist when I make use of IE. My Firefox is currently 3.5, and so it may be a browser compatibility with Concrete 5, since it works with IE. It is hopeful seeing it work on IE, and WOW, Concrete 5 is FAST. Works very well. Got to say, NJ. But need it working with Firefox. Of course I'll check on updates for Firefox.
Okay, C5 has gotten our attention, and we are darn impressed!
So impressed, we are thinking of showcasing it on our sites. Clients have mentioned it a good amount during the last two years more than prior years.
U1C1, you most likely got the email communication by now and are hopefully upgrading your browser.
This got my personal curiosity, and I was able to reproduce the problem by making use of Firefox 3.5.1. Don't know if it is a compatibility problem from the browser side or C5. The fastest solution really seems to be to upgrade your browser.
I have confirmed the C5 editing/saving function works fine with Firefox 3.6.27, and 10.0.2, and also Internet Explorer 7.0.5730.xx, and so chances are the problem is limited to a tiny group of browser versions that are also old.