Concrete5.7 broke design area by inserting 'content' block on sitewide footer
Permalink
I'm editing a website, and I tried inserting a content block into a design area on the site
wide footer (so it seems outside restoring a previous version).
Its broken the design area so I can't just remove the content block since it no longer shows up, I think the design area is still there but its now showing up empty and off placement,
thats set in the theme css isn't it?
adding content should not be able to broke or mess anything set in the theme css (currently Elemental) should it?
Is there any way to version control restore previous versions of the site wide footer?
wide footer (so it seems outside restoring a previous version).
Its broken the design area so I can't just remove the content block since it no longer shows up, I think the design area is still there but its now showing up empty and off placement,
thats set in the theme css isn't it?
adding content should not be able to broke or mess anything set in the theme css (currently Elemental) should it?
Is there any way to version control restore previous versions of the site wide footer?
Or manually delete a content block attached to a element outside the concrete5 cms interface (site editor doesn't pick it up anymore)?
Nevermind solved it, I did find a way to delete the offending content block, and the element returned to position after it was removed.
Thanks anyway.
Thanks anyway.
Great managed to do it again in a different way, the footer is very dangerous
because the layouts aren't delete-able if bad code screws over the ability to remove blocks,
is it really over then?
And the footer is non-versioned so that won't work either.
Is there a outside the concrete5 interface method for removing a block when the
editing interface has broken?
Is the phpmyadmin surgery hard?
because the layouts aren't delete-able if bad code screws over the ability to remove blocks,
is it really over then?
And the footer is non-versioned so that won't work either.
Is there a outside the concrete5 interface method for removing a block when the
editing interface has broken?
Is the phpmyadmin surgery hard?
Personally have had to do a lot of PHPMyadmin work to resurrect completely hosed sites before. My advice is to do a site backup before you start doing lots and lots of editing, since every once in a while something really blows up.
I once had a case where a block added to the footer messed something up, and could no longer login and could not get to dashboard. That sick feeling when you have a page-full or cryptic PHP error messages.
Once you figure out the database schema for C5 you see it's very logical, but the time to learn that is not when you're looking at losing a whole week of site editing due to one bad block messing up the database.
I do maintain two test C5 servers (5.6 and 5.7) those are handy for two reasons. First I can try stuff and not worry about crashing my prod sites, and second, if I do hose a prod site, I can go back and compare what code and/or database content is different--this is priceless if one particular field or php line is borked. Not to digress, but my test servers run on VMware server, and that has a snapshot capbility--this lets you undo even the most terrible error to site or database.
I once had a case where a block added to the footer messed something up, and could no longer login and could not get to dashboard. That sick feeling when you have a page-full or cryptic PHP error messages.
Once you figure out the database schema for C5 you see it's very logical, but the time to learn that is not when you're looking at losing a whole week of site editing due to one bad block messing up the database.
I do maintain two test C5 servers (5.6 and 5.7) those are handy for two reasons. First I can try stuff and not worry about crashing my prod sites, and second, if I do hose a prod site, I can go back and compare what code and/or database content is different--this is priceless if one particular field or php line is borked. Not to digress, but my test servers run on VMware server, and that has a snapshot capbility--this lets you undo even the most terrible error to site or database.
Yeah that is what I ended having to do, restore from phpmyadmin backup, it was I little older then I would have liked, but I did have the for thought to have taken a backup occasionally.
It was good practice forced me to learn some new things, and yeah I completely toasted
the cms editor. xD
It was good practice forced me to learn some new things, and yeah I completely toasted
the cms editor. xD
