HTML loop
Permalink
I'm new to Concrete5 and while testing out version 5.7 in preparation for possibly converting a Drupal site to Concrete5 I erroneously created an HTML snippet which invoked the location.reload() method on the Home page. Of course this caused the Home page to render in an endless loop. After not finding the "location.reload()" in any file under the site's directory it became clear Concrete5 stores added html in the database. I dumped the database to a SQL file to find the code. After locating the references in the dumped SQL file. I found 3 tables containing the errant code: btContentLocal, btCachedBlockRecord and CollectionVersionBlocksOutputCache. I went back to the database and fired up phpMyAdmin to make the corrections. The only table I could access from phpMyAdmin was btContentLocal (probably because I had already deleted the cache files on disk) so I edited out the errant "location.reload()" method invocation from there.
Cutting to the chase, the site continues in this reload loop even after re-starting the site from scratch and clearing the browser cache.
Can anyone aid me in finding and applying a proper solution to this dilemma?
Many thanks!
Cutting to the chase, the site continues in this reload loop even after re-starting the site from scratch and clearing the browser cache.
Can anyone aid me in finding and applying a proper solution to this dilemma?
Many thanks!
Thank you for your prompt response to my post. Because the home page is in this relentless loop I am unable to do anything using the Concrete5 screen interface. Is there some way to accomplish this reversion from the command line?
Thank you again.
Thank you again.
Go to site.com/index.php/dashboard
On Sep 14, 2014 1:47 PM, "concrete5 Community" <discussions@concretecms.com>
wrote:
On Sep 14, 2014 1:47 PM, "concrete5 Community" <discussions@concretecms.com>
wrote:
There is no shortage of great information on that page and the pages contained therein but I was unable to find anything dealing with "reverting" to a previous version.
Thanking you in advance for your continued assistance.
Thanking you in advance for your continued assistance.
Hi,
what Mnkras is suggesting is that once you are logged into the dashboard go to 'Full Sitemap'
Click on your homepage
click versions from the resulting menu
select a previous version by checking the box to the left
approve this version by clicking approve (the thumbs up icon at the top)
That version will now show in the front-end of the site to the non-logged in users however the most recent one with your looping html will still be there and be seen by deafult by editors so you might just want to remove that version.
what Mnkras is suggesting is that once you are logged into the dashboard go to 'Full Sitemap'
Click on your homepage
click versions from the resulting menu
select a previous version by checking the box to the left
approve this version by clicking approve (the thumbs up icon at the top)
That version will now show in the front-end of the site to the non-logged in users however the most recent one with your looping html will still be there and be seen by deafult by editors so you might just want to remove that version.
apologies - I just realised this is version 5.7 - it will look different from how I described (I also have not tested it yet)
To both Andy and Mike,
After getting over my Homer Simpson moment I found the "Versions" option under the handy Site Map. I attempted to revert to the first instance of the page created when I installed Concrete5 followed by "Approving" the reversion. The Home page remained in the page reload loop. My method to verify that indeed the page reverted was to go back to the Site Map page, select "Versions" again and attempt to "re-revert" the page but the "Approve" option did not display so I assumed the reversion was successful. I even rebooted my Linux box trying to "sledgehammer" it into compliance.
THE SOLUTION: I deleted the tables in the database and reloaded the previously exported Concrete5 SQL file WITHOUT the call to the "location.reload()" method. Everything came back OK.
Concrete5 certainly appears to be superior to Drupal in terms of offering a low-tech person the ability to perform light maintenance on a Web site as long as they don't have to add/modify any HTML. Since I'll be unable to maintain their relatively simple Drupal site going forward I wanted to convert it to a CMS easier for the average user to maintain in terms of adding photos and manipulating blocks of text information. Concrete5 looks like a winner in this regard. Still, having the code in the database is quite unwieldy for those needing to access it. ESPECIALLY when it goes south! If I can verify that the people who will use this tool do not intend to play with HTML to any great extent then I will most likely forge ahead with my plans to convert their site from Drupal to Concrete5.
Thanks again for your assistance in this matter.
-Paul
After getting over my Homer Simpson moment I found the "Versions" option under the handy Site Map. I attempted to revert to the first instance of the page created when I installed Concrete5 followed by "Approving" the reversion. The Home page remained in the page reload loop. My method to verify that indeed the page reverted was to go back to the Site Map page, select "Versions" again and attempt to "re-revert" the page but the "Approve" option did not display so I assumed the reversion was successful. I even rebooted my Linux box trying to "sledgehammer" it into compliance.
THE SOLUTION: I deleted the tables in the database and reloaded the previously exported Concrete5 SQL file WITHOUT the call to the "location.reload()" method. Everything came back OK.
Concrete5 certainly appears to be superior to Drupal in terms of offering a low-tech person the ability to perform light maintenance on a Web site as long as they don't have to add/modify any HTML. Since I'll be unable to maintain their relatively simple Drupal site going forward I wanted to convert it to a CMS easier for the average user to maintain in terms of adding photos and manipulating blocks of text information. Concrete5 looks like a winner in this regard. Still, having the code in the database is quite unwieldy for those needing to access it. ESPECIALLY when it goes south! If I can verify that the people who will use this tool do not intend to play with HTML to any great extent then I will most likely forge ahead with my plans to convert their site from Drupal to Concrete5.
Thanks again for your assistance in this matter.
-Paul
For your current issue, I would still recommend doing that.
If that does not resolve the issue, ensure that all caches (site cache included are cleared)
Mike