Auto Update to 6.7 now Warnings

The messages are only warnings and not errors. They inform you that 3 of the plugins you are using are not yet compatible with WordPress 6.7. You only see the messages because you have activated WordPress debug mode or the output of PHP messages.

To solve this, I would recommend the following steps:

Log in via FTP and edit the wp-config.php file. You should deactivate debugging there, i.e. the reverse of the procedure described here: https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/ – if you need help with this, contact your host’s support team.

If the first tip is not enough, you can also rename the plugin directory via FTP. So /wp-content/plugins/ e.g. to /wp-content/plugins.bak/. WordPress will then no longer load them and you should be able to access the backend again. However, you will then have to reinstall all the plugins you use individually.

If you then have a working website again, you should also follow up on the warnings you have seen. You should definitely update the plugins that are causing the problem to the latest version – so it is best to install all pending updates. If this does not finally solve the problem, contact the developers of the plugins causing the problem so that they can make their plugin compatible with WordPress 6.7.

Hey @threadi ,

thank you very much for the very fast reply. Deactivating the debig was the way to go. i was able to login again and updated all themes and plugins.

The problem is, that some Notices and Warnings remain also after the updates.

In the frontend i get following errors:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at/wp-includes/functions.php:6114) in /wp-content/plugins/borlabs-cookie/classes/Cookie/Frontend/CookieBlocker.php on line 81

In the backend i get:

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the thegem-elements-elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /wp-includes/functions.php:6114) in /wp-admin/includes/misc.php on line 1438

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

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

Additional ALL umlauts like ?, ?, ü are now broken. How to fix that?
What was that for a crappy update?

EDIT: The umlauts problem ist just with debug status active, so that is no real problem because after the warnings etc. are fixed it should be fine

• This reply was modified 3 months, 4 weeks ago by firehold. Reason: The umlauts problem ist just with debug status active, so that is no real problem because after the warnings etc. are fixed it should be fine

@leesvillelake: please create your own topic for your own issue: https://www.ads-software.com/support/forum/wp-advanced/#new-topic-0

@firehold: Have you already installed all pending plugin updates as I recommended? If not, you would have to contact the plugin developers concerned to resolve the latest messages so that they can update their plugin.

@leesvillelake — as threadi has alluded to, tagging onto other member’s topics is considered rude in these forums. I’m sure that was not your intention, but now you know better. Please always start your own topic anew. While existing topics may seem like the exact same issue as yours, the resolution is very rarely the same. Having various members attempting to resolve multiple issues in a single thread just causes more confusion. By tagging onto someone else’s topic, you are diverting attention away from their issue they want resolved. When you start your own topic, members can focus attention solely on your issue.

To avoid further confusion your reply in this thread has been removed from view.