Make WordPress Core

Opened 11 months ago

Last modified 11 months ago

#59845 new enhancement

kritischen Fehler seit Update auf WordPress 6.4

Reported by: mdamerius's profile mdamerius Owned by:
Milestone: Awaiting Review Priority: normal
Severity: critical Version: 6.4
Component: Upgrade/Install Keywords: needs-testing
Focuses: administration Cc:

Description

Hallo seit dem Update heute auf die Version WordPress 6.4. bekomme ich bei der mobile Version meiner Homepage nur noch die Meldung "Es gab ein kritisches Problem" In der Desktop Version sieht alles gut aus. Brauche dringend Hife.

Change History (8)

#1 @rajinsharwar
11 months ago

Hey @mdamerius, sorry to hear that, and thanks for your ticket. For us to point out, can you please enable the WP DEBUG LOG, and try to share the contents of the /debug.log found under your wp-content folder here?

You can enable the WP DEBUG LOG by adding this snippet in your wp-config.php

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

After that, please try to reload your website again, and then attach the debug.log file here found under your /wp-content folder.

Last edited 11 months ago by rajinsharwar (previous) (diff)

#2 @flixos90
11 months ago

Hi @mdamerius, und vielen Dank für das Ticket!

Ich persönlich kann dir zwar auf Deutsch antworten, aber die Entwicklung und Diskussion auf Trac ist typischerweise komplett in Englisch, damit es international zugänglich ist. Falls du mir also auf Englisch hier antworten könntest, wäre das super. :)

Are you using a separate WordPress installation for the mobile website? Otherwise I'm a bit confused why the critical error only happens on the mobile version.

Other than that, I would echo the advice from @rajinsharwar. If you could do that and then share some additional information about the error here, that would be very helpful.

This ticket was mentioned in Slack in #core by jorbin. View the logs.


11 months ago

#4 @JeffPaul
11 months ago

Lacking a response from @mdamerius I did a quick lookup of the website on their dotorg profile (noting profile created today, so taking their website as likely the site with the error noted in this Trac ticket) and seeing that whatcms.org reports that they're using WP 6.4, PHP 8.1.25, Apache, MySQL, cdnjs and Cloudflare for CDN for anyone trying to replicate.

#5 @mdamerius
11 months ago

Hello and thanks for the help. DEBUG LOG is enabled. The following message appears for me.

PHP Fatal error: Uncaught Error: Failed opening required '/homepages/7/d889104224/htdocs/clickandbuilds/HIMNews/wp-content/themes/Newspaper/legacy/common/wp_booster/td_css_res_compiler.php' (include_path='.:/usr/lib/php8.1') in /homepages/7/d889104224/htdocs/clickandbuilds/HIMNews/wp-includes/template.php:790

#6 follow-up: @flixos90
11 months ago

@mdamerius Thank you for providing additional details.

@joemcgill This looks like it could potentially be caused by the caching of the theme directories too (for which you already prepared a PR)? Just an assumption, maybe there's some additional "magic" at play on the site which leads to the expected value of the directories to change after the relevant function is first called (but that now would no longer work due to the caching in a global).

Last edited 11 months ago by flixos90 (previous) (diff)

#7 in reply to: ↑ 6 @joemcgill
11 months ago

Replying to flixos90:

@joemcgill This looks like it could potentially be caused by the caching of the theme directories too (for which you already prepared a PR)? Just an assumption, maybe there's some additional "magic" at play on the site which leads to the expected value of the directories to change after the relevant function is first called (but that now would no longer work due to the caching in a global).

Very likely the same root cause as #59847.

#8 @mdamerius
11 months ago

What options do I have to solve the problem? @flixos90 I use the plugin for mobile display. By the way, I use the plugin included in the theme. Does it make sense to deactivate this and replace it with another one?

Note: See TracTickets for help on using tickets.