Title: Update causing a new bug&#8230;
Last modified: December 19, 2024

---

# Update causing a new bug…

 *  [mjkentish](https://wordpress.org/support/users/mjkentish/)
 * (@mjkentish)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/update-causing-a-new-bug/)
 * I’ve started getting this error message on most of the pages on my website following
   a recent automatic update…
 * **Notice**: Function _load_textdomain_just_in_time was called **incorrectly**.
   Translation loading for the `post-smtp` 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](https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/)
   for more information. (This message was added in version 6.7.0.) in **/var/www/
   wp-includes/functions.php** on line **6114**
 * A few similar ones also appear.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fupdate-causing-a-new-bug%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  [Lina Asenova](https://wordpress.org/support/users/linaasenova/)
 * (@linaasenova)
 * [1 year, 5 months ago](https://wordpress.org/support/topic/update-causing-a-new-bug/#post-18208416)
 * WordPress 6.7.x has introduced changes that are causing PHP notices (not critical
   errors) to appear when using certain incompatible plugins. Here are your options
   to resolve this:
    1. **Check for Plugin Updates:** Many developers have likely released compatibility
       fixes already, so start by **ensuring your plugins are up to date.** In your
       case the error is from the **Post SMTP** plugin, so you can also reach to their
       support team: [https://wordpress.org/support/plugin/post-smtp/](https://wordpress.org/support/plugin/post-smtp/)
    2. **Adjust Error Reporting Settings:** If the notices persist, it’s likely because
       your site is in debug mode or your host displays PHP notifications. To prevent
       these notices from showing up, disable Debug mode by editing your `wp-config.
       php` file. Replace this line:
       `define( 'WP_DEBUG', true );`with: `define( 'WP_DEBUG',
       false );`
    3. **Other Options:**
    4.  - Temporarily roll back to WordPress 6.2.2 and upgrade again once plugin developers
          catch up.
        - Alternatively, maintain your current version and wait for plugin updates.

Viewing 1 replies (of 1 total)

The topic ‘Update causing a new bug…’ is closed to new replies.

## Tags

 * [init](https://wordpress.org/support/topic-tag/init/)
 * [triggered](https://wordpress.org/support/topic-tag/triggered/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 1 reply
 * 2 participants
 * Last reply from: [Lina Asenova](https://wordpress.org/support/users/linaasenova/)
 * Last activity: [1 year, 5 months ago](https://wordpress.org/support/topic/update-causing-a-new-bug/#post-18208416)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
