Several months after handing over a client site, I have been asked to do a few more things.

Somewhere along the way, the page defaults editor has stopped working. In every case, it crashes with a memory error:



This is happening on every page type configured including a new (test) one on both their live site as well as a test setup I built from their site data on a separate (proven) server. Allocating more memory does not help and seems like a red herring... something is spinning off out of control. Since it is also not working on the fresh development server install (with their data), it makes me think something is wrong in their DB.

I am still at the wild guessing stage, but I see some evidence of blocks being created and deleted over the last few months as well as stacks (from global areas). Is it possible that some orphaned block or stack is still embedded in a page type default? Or is there some way of completely resetting the defaults for one or more page types and recreating them? The key is being able to get back into the defaults editor by whatever means possible. Naturally, composer is not working until the page type defaults can be properly set which means nobody can do anything and they are just a little anxious ;-)