WordPress.org

Make WordPress Core

Opened 6 months ago

Last modified 2 weeks ago

#53352 new defect (bug)

Twenty Twenty-One: PHP warning: Illegal string offset 'custom_css_post_id'

Reported by: karenaug Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 5.7.2
Component: Bundled Theme Keywords:
Focuses: template Cc:

Description (last modified by sabernhardt)

Hello,

When I open my blog, I get the following error message:

Warning: Illegal string offset 'custom_css_post_id' in /.../wp-includes/theme.php on line 1063

In the dashboard I see the following message:

...ng offset 'nav_menu_locations' in /.../wp-includes/theme.php on line 1063


Warning: Cannot modify header information - headers already sent by (output started at /.../wp-includes/theme.php:1063) in /.../wp-includes/functions.php on line 6362

Line 1063 is $mods[ $name ] = apply_filters( "pre_set_theme_mod_{$name}", $value, $old_value );

I have tried: uploading wordpress again with ftp, clearing caches, reinstalling the twenty twenty one theme, deactivated plugins, uploading the theme.php file again.
I don't see this bug when I activate other themes.

The forum thread is: https://wordpress.org/support/topic/theme-down/page/2/#post-14525964

Is there anything else I can do?

Kind regards,

Karen

Change History (3)

#1 @audrasjb
6 months ago

  • Summary changed from Bug in theme Twenty One to PHP Warning in Twenty Twenty-One

#2 @SergeyBiryukov
6 months ago

  • Summary changed from PHP Warning in Twenty Twenty-One to Twenty Twenty-One: PHP warning: Illegal string offset 'custom_css_post_id'

#3 @sabernhardt
2 weeks ago

  • Description modified (diff)

@karenaug Hi and welcome to Trac!

Your site still uses Twenty Twenty-One, and the custom CSS is included properly now. Were you able to fix it somehow?

I received similar errors with Twenty Twenty (and possibly Twenty Nineteen as well) around the time you opened the support topic and this ticket. I think the errors occurred immediately after activating a plugin, though you said that was not the case when you had trouble. (Because my site was a local development site, on WP5.8-alpha, I replaced it entirely.)

Note: See TracTickets for help on using tickets.