gyakuzuki

Excuse me? I certainly wish you had some manners when asking someone for help. This was months and months ago, I’m not going to able to provide you a step by step solution here.

The debug logs, from my memory, indicate that one of the entries in the database is broken. In my case, it was entirely null, when it should have had some array of content. Repairing the content wasn’t necessary, if I could get past the null error, I could just reinstall the theme to repopulate the database correctly. In my case, I believe I added an empty array {} into the null field, which, whilst obviously not fixing the theme, left it at least in a state that could be repaired by a removal and reinstall of the theme.

I decided to just resolve this by relocating the blog to the root directory.

OK, I resolved this by adding a junk array from a “theme_mods_***” option in the database to the “sidebars_widgets” option, which was for some reason totally blank and this seemed to be what the debug logs were indicating.

Ok, I tried all of that and still no help. Can anyone help me with what’s gone wrong? Something must be persisting somewhere to cause this, surely? Since I’ve gone through a reinstall and everything? Is this something database related?

Sure, I’ll try these, but the issue didn’t happen right away when I upgraded. As I mentioned, things were fine, then Jetpack started being weird with widgets, then widgets and customise became broken.

I will reply again once I’m through the list; note that I won’t try the ‘permalink structure’ one because I already tried and it causes a separate issue with htaccess that I have a separate post about.