• Skip to main content
  • Skip to forum navigation

StudioPress

  • Shop for Themes
  • My StudioPress

Forum navigation

  • Home
  • General Genesis Discussions
  • StudioPress Themes
  • Genesis Blocks
    • Genesis Blocks
    • Genesis Custom Blocks
  • Retired Themes
  • FAQs
  • Forum Rules
  • Internationalization and Translations
  • Forum Bugs and Suggestions
  • Forum Log In

Are You Using The WordPress Block Editor?

Genesis now offers plugins that help you build better sites faster with the WordPress block editor (Gutenberg). Try the feature-rich free versions of each plugin for yourself!

Genesis Blocks Genesis Custom Blocks

WordPress 6.7 update triggered genesis warning

Welcome!

These forums are for general discussion on WordPress and Genesis. Official support for StudioPress themes is offered exclusively at My StudioPress. Responses in this forum are not guaranteed. Please note that this forum will require a new username, separate from the one used for My.StudioPress.

Log In
Register Lost Password

Community Forums › Forums › General Genesis Framework Discussions › WordPress 6.7 update triggered genesis warning

This topic is: not resolved
  • This topic has 16 replies, 8 voices, and was last updated 2 months, 2 weeks ago by brycejune.
Viewing 17 posts - 1 through 17 (of 17 total)
  • Author
    Posts
  • November 19, 2024 at 4:03 pm #508555
    blancy
    Participant

    After updating to WordPress 6.7 on my genesis-based sites I see a warning that was apparently introduced in this release which has been named a 'Doing it wrong' warning and reads as follows:

    "Translation loading for the genesis 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."

    I also had this warning for a couple of plugins but they have since provided updates which correct the issue and the warning is now gone for those. Will there be an update for genesis framework theme to address it?

    thanks

    November 19, 2024 at 9:08 pm #508556
    AnitaC
    Keymaster

    It sounds like you may have found this warning having Debug mode turned on. While I do not know right now if they'll have a fix for this, the site should function normally.

    As a temporary solution, you can suppress the warnings using WP_DEBUG_DISPLAY in your wp-config.php file. Set:

    
    define( 'WP_DEBUG_DISPLAY', false );
    

    Need help with customization or troubleshooting? Reach out to me.

    November 20, 2024 at 5:14 am #508561
    blancy
    Participant

    Thanks.

    Yes I have debug mode turned on on my local development and staging sites. I realise that the warning won't show on the live site where debug mode is set to false but it would be good to have it fixed so that I can continue to have it enabled on my staging sites and also to keep my debug log less clogged up as it generates a lot of lines in the debug log for every page visit.

    I was just wondering if there was a plan to address it as all other plugins themes I use have already addressed the issue.

    November 20, 2024 at 10:23 am #508564
    AnitaC
    Keymaster

    @blancy I have some feedback. I was told this is a bug in WordPress Core and they are aware of it - https://core.trac.wordpress.org/ticket/62337. And, it should possibly be resolved in the next WordPress update (in 6.7.1) that is scheduled to release tomorrow. So Genesis doesn't need to be updated as it's an issue with Core.


    Need help with customization or troubleshooting? Reach out to me.

    November 20, 2024 at 1:52 pm #508568
    blancy
    Participant

    @AnitaC Ah, interesting. Hopefully that will sort it.

    Many thanks for providing this info.

    November 21, 2024 at 3:39 pm #508581
    blancy
    Participant

    It seems 6.7.1 has not fixed this for my site sadly.

    "Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the genesis 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."

    November 21, 2024 at 6:47 pm #508582
    AnitaC
    Keymaster

    @blancy looks like WordPress didn't push that fix. I mean on that trac someone said it's fixed for them, but I see it on Ninja Forms too so I really don't think 6.7.1 fixed it for "every" instance unfortunately.


    Need help with customization or troubleshooting? Reach out to me.

    November 26, 2024 at 2:45 pm #508623
    blancy
    Participant

    From the latest on that trac it sounds like it's the responsibility of the theme / plugin developers to address the issue. Most have acted fairly quickly. I hope genesis will at some point also.

    November 26, 2024 at 2:57 pm #508624
    blancy
    Participant

    I'm using the following in functions.php to suppress it for now:

    add_filter( 'doing_it_wrong_trigger_error', '__return_false' );

    January 21, 2025 at 2:39 pm #508991
    webdev
    Participant

    Any update on this?
    Is there another way to contact them?

    February 8, 2025 at 7:38 am #509115
    pixelloop
    Participant

    It's annoying that we still don't seem to have an update on how to resolve this properly.


    I write articles about blogging, WordPress and building a business online at Mazepress.

    February 10, 2025 at 7:24 pm #509128
    AnitaC
    Keymaster

    They're working on it. Not sure when the update will happen, but I know they're working on it like many of the other themes and plugins who also need to resolve it.


    Need help with customization or troubleshooting? Reach out to me.

    February 22, 2025 at 11:53 am #509174
    thartl
    Participant

    Thank you, Anita. That is good to know.
    This prevents me from displaying debug output in local and clutters server logs quite a bit.
    It will be a welcome relief to have it fixed.

    February 25, 2025 at 2:54 pm #509175
    bloom
    Participant

    I am getting now getting this warning as well. Any updates to a solution?

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the genesis 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 /var/www/wp-includes/functions.php on line 6114

    March 13, 2025 at 11:06 am #509188
    Steck Insights
    Participant

    Still seeing the same here running WP 6.7.2 and PHP 8.1.

    I'm concerned that this notice will become a warning and an error over time as PHP versions increase and restrictions get tighter.

    March 13, 2025 at 7:27 pm #509190
    AnitaC
    Keymaster

    @steck-insights They are still working on this from what I understand.


    Need help with customization or troubleshooting? Reach out to me.

    April 23, 2025 at 5:02 am #509196
    brycejune
    Participant

    Hi,
    The warning you’re seeing is related to WordPress 6.7's stricter handling of when translation functions are called. It indicates that Genesis is loading translations too early in the process. Since other plugins have already released fixes, it’s likely that the Genesis Framework team is aware and working on a similar update. Keep an eye on upcoming Genesis theme updates or reach out to their support directly for a timeline.

  • Author
    Posts
Viewing 17 posts - 1 through 17 (of 17 total)
  • You must be logged in to reply to this topic.
Log In

CTA

Ready to get started? Create a site or shop for themes.

Create a site with WP EngineShop for Themes

Footer

StudioPress

© 2025 WPEngine, Inc.

Products
  • Create a Site with WP Engine
  • Shop for Themes
  • Theme Features
  • Get Started
  • Showcase
Company
  • Brand Assets
  • Terms of Service
  • Accptable Usse Policy
  • Privacy Policy
  • Refund Policy
  • Contact Us
Community
  • Find Developers
  • Forums
  • Facebook Group
  • #GenesisWP
  • Showcase
Resources
  • StudioPress Blog
  • Help & Documentation
  • FAQs
  • Code Snippets
  • Affiliates
Connect
  • StudioPress Live
  • StudioPress FM
  • Facebook
  • Twitter
  • Dribbble