WordPress.org

Make WordPress Core

Opened 3 days ago

Closed 3 days ago

Last modified 3 days ago

#53379 closed defect (bug) (invalid)

PHP-Warnung: Invalid String-Offset 'custom_css_post_id"

Reported by: kreativstattandrea Owned by:
Milestone: Priority: normal
Severity: critical Version: 5.7.2
Component: Bundled Theme Keywords:
Focuses: template Cc:

Description

Hallo,
ich kann im Customizer keine Änderungen im Header mehr vornehmen.
Dieser Fehler steht in meiner Server-Error-Logfile:

10.06.2021 19:38:01 kreativstattandrea.de [client 157.55.39.0] AH01215: PHP Warning: Illegal string offset 'custom_css_post_id' in /mnt/web222/d0/62/5549962/htdocs/WordPress_03/wp-includes/theme.php on line 1063: /home/strato/http/premium/rid/99/62/5549962/htdocs/WordPress_03/index.php

Ich habe auch schon WordPress 5.7.2 neu installiert und vor dem Arbeiten im Customizer den Cache geleert. Seit dem 04.06.2021 geht leider nix und mein Blog sieht nicht gut aus.

Was ist hier zu tun? Danke

Sonnige Grüße
Andrea Kutsch

Change History (1)

#1 @desrosj
3 days ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed
  • Summary changed from PHP-Warnung: Ungültiger String-Offset 'custom_css_post_id" to PHP-Warnung: Invalid String-Offset 'custom_css_post_id"

Hi @kreativstattandrea,

Welcome to Trac! I apologize in advance if I'm misunderstanding your report. I've had to rely on Google Translate.

I'm sorry to hear that you're experiencing issues with your WordPress site. It seems this is not reporting a specific issue in the WordPress Core code, but rather an issue with your specific site. It's possible that there is a bug in WordPress, but without reliable steps to reproduce on a fresh install, this is more of a support request.

Those are better handled over on the WordPress.org support forums. There is a localized version, so you'll be able to communicate in German with volunteers that are looking to help site owners with problems like this: https://de.wordpress.org/support/.

I'm going to close this out as invalid, which is Trac's default ticket resolution. I'm not saying your issue is invalid, there are just no actions to be taken currently here in Trac.

Last edited 3 days ago by sabernhardt (previous) (diff)
Note: See TracTickets for help on using tickets.