YOUR HELP PLEASE: Unknown database issue to do with layouts

Permalink 1 user found helpful
I am devving on localhost with C5.7 and a custom theme. I have been working on a variety of things and out of nowhere some bizarre critical error has occurred within my site causing two pages not to load at all.

I think this is a problem to do with installing a duplicate theme with same custom layout area names in it in page_theme.php and then removing that theme.

SYMPTOMS are 2 pages do not load fully, the CSS fails and the load does not complete. It stalls in both cases where custom layouts should be within block areas. (in different templates), This lead me to think it must be layout related and possibly within the database?

I note in a clean page the whole CMS stalls when I try and "ADD LAYOUT" to a block area.

I have tried changing page templates, and these page templates work fine with other pages. So the issue I believe is when the blocks are called that call upon these two custom layouts.

The layouts themselves are named in the page_theme.php, 'six_block_grid' and 'two_columns'

I have tried removing entries from various MYSQL tables to do with Layout Presets but I seem unable to edit the MYSQL file as it keeps saying:

"SELECT * FROM `jazzitupkids_C52`.`AreaLayoutPresets` WHERE ;"

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1

I have attached my MYSQL file and my page_theme.php

ANy ideas would be a huge help otherwise the live site is screwed!

1 Attachment

 
tallacman replied on at Permalink Reply
tallacman
can you try putting the theme back in and see what happens?
tobyme replied on at Permalink Reply
Thanks very much for the reply.

Sadly no luck I have:
- Reinstalled the removed theme (it was simply a clone of my main theme with an alternate title) and activated, also tried assigning it throughout. then uninstalled
- Assigned Elemetal throughout, unistalled all other themes and then reinstalled my themes. No progress.

It does defo seem to be something to do with the custom layout templates.

When I revert to an early dev database, I can easily edit container layout and select my presets from the menu. With the active database if I click the Container Layout button on a blank page within any template it freezes the whole CMS.

Would removing the presets in the MYSQL table work? It is what I was going to try but then got this stupid warning to do with MySql 1064, which comes on every databse in my localhost now?

Maybe that is to do with something else in MAMP PRO. It is not something I have come across before with MAMP. Although I am fairly new to MAMP PRO 4.

I am running Coda, Codekit, MAMP PRO on a mac.
tobyme replied on at Permalink Reply
I should maybe add - I have been using Block Designer and made a few custom blocks, that was the only other thing going on at the same time, may than have added something oncporrect to the MySQL file?

The site itself is very small so fart with only 6/7 real pages so trawling the MySql isnt that tough yet.
tobyme replied on at Permalink Reply
And I should also say - when I try and load the 2 pages in question they take absoluitely ages to render.

I have tracked down which bkock the content is loaded in in my Our Courses page? So I am guessing the easiest would be to remove the ayout from the databse? Where would I do this?

I would have enclosed files here but it wont let me.
tobyme replied on at Permalink Reply
Righto - just in case someone is reading this I have managed to get the pages to reload by editing the SQL in Coda and removing the AreaLayoutPresets and AreaLayoutsUsingPresets data from the MySQL?

I wonder what on earth happened.....
nigelcooper66 replied on at Permalink Reply
I had similar problem. Had tried to "save layout as preset" from edit mode BUT probably used the same name as a layout in my page_theme.php.

It made the affected page not load correctly, edit bar missing. Other pages loaded edit bar but site was very unresponsive.

As burbleweb described I solved this by deleting the only entry I had in AreaLayoutPresets.

Took an age to figure out. All back to normal..I think