something has broken

I deactivated Jetpack and now this is at the top, above my header

Warning: Illegal string offset 'custom_css_post_id' in /home/customer/www/wendyg.com/public_html/wp-includes/theme.php on line 1063

I deactivated Yoast but only deactivating Jetpack did the message at top changed.
TY

before updating those 3 plugins, I saw 3 messages via my contact page under "Feedback". each was someone offering me some SEO or other service. Now I don't see those messages either.

Hi there,

Not sure if I understand but I don't believe this is a theme issue.

Do you get the error with all plugins disabled except Yoast and GP Premium?

Thanks but I just deactivated all plugins except GP Premium and yoast. It's still not fixing it.

I hadn't deactivate everything since only yoast and jetpack had just been updated.

There seems to be something wrong with a line of code b/c this is the warning at the top of my site

Warning: Illegal string offset 'custom_css_post_id' in /home/customer/www/wendyg.com/public_html/wp-includes/theme.php on line 1063

WendyG.com

That message is actually pointing to a WordPress core file and not a GP file.

Do you get the same issue with a Twenty series default theme?

I just activated the 2020 theme and don't see that warning message.

Soooo, since the 2020 and 2021 WP Themes don't show this Warning message, would that indicate that it's related to GP?

I reactivated GP and GP Premium and reactivated my plugins and this is the displayed warning

Warning: Illegal string offset 'custom_css_post_id' in /home/customer/www/wendyg.com/public_html/wp-includes/theme.php on line 1063

Hi there,

I am not seeing the error on the front end of the site ... but the menu still looks a little wonky. Can you go to Customizer > Menus and make sure your menu has its location set to the Primary Navigation.

Not sure what caused this problem - it may have been a cached file, or just a glitch when those plugins were updated.

Let me know if the error reshows - and i can take another look.

Thanks David, I made my menu Primary Navigation, but it still reverts to this broken one. I'm not sure how to fix that.

And about the warning mssg, I eventually contacted someone in CS @ my host SiteGround. He said the plugin updates caused some conflicts with parts of my website. He removed the warning and suggested I not update plugins, etc simultaneously.

So Siteground were on the right track that some 'things' got corrupted on update - and that looks to be the case with the Menu - see Tom's response here ( SG should be able to help repair that if you ask them nicely ):

https://generatepress.com/forums/topic/wordpress-custom-menu-is-not-working-with-gp-theme/#post-1800913

Sorry for the original delay between responses - we try to cover 24hrs with West Coast US, Europe and Asia support teams but occasionally we have gaps and these topics had to be re-assigned as we looked into the issue.

Thanks David,
I got back in touch w/ CS at SiteGround and restored a prior version of my blog from last week. I'd completely forgotten that they create a back up every day. I still don't understand what happened but at least it's been restored.

Glad to hear you got a solution.