• Resolved simbian

    (@simbian)


    Using Query Monitor plugin i can see this:

    Translation loading for the content-control 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.

    Caller:
    _load_textdomain_just_in_time()
    wp-includes/l10n.php:1370

    1. get_translations_for_domain()
      wp-includes/l10n.php:1408
    2. translate()
      wp-includes/l10n.php:194
    3. __()
      wp-includes/l10n.php:306
    4. ContentControl\get_plugin_config()
      wp-content/plugins/content-control/content-control.php:31
    5. ContentControl\config()
      wp-content/plugins/content-control/content-control.php:56

    Im using WordPress 6.7.2.
    Can you fix this?
    Thanks.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Kim L

    (@kimmyx)

    Hi @simbian,

    Thanks for the post!

    We’ve forwarded this to our dev team so they can take a closer look.

    We’ll let you know once we receive feedback from them.

    We appreciate your patience! ??

    Let us know if you have other questions.

    Plugin Support Sarai Acevedo

    (@sarai1)

    Hi @simbian,

    While we’re testing this on our end, could you try removing the translation from lines 31 and 38 in wp-content/plugins/content-control/content-control.php to see if that resolves it for you?

    Thread Starter simbian

    (@simbian)

    Hello @sarai1 unfortunately did not solved, now the errors are:

    1. _load_textdomain_just_in_time()
      wp-includes/l10n.php:1370
    2. get_translations_for_domain()
      wp-includes/l10n.php:1408
    3. translate()
      wp-includes/l10n.php:194
    4. __()
      wp-includes/l10n.php:306
    5. ContentControl\Controllers\TrustedLogin->init()
      wp-content/plugins/content-control/classes/Controllers/TrustedLogin.php:48
    6. ContentControl\Plugin\Core->register_controllers()
      wp-content/plugins/content-control/classes/Plugin/Core.php:306
    7. ContentControl\Plugin\Core->initiate_controllers()
      wp-content/plugins/content-control/classes/Plugin/Core.php:293
    8. ContentControl\Plugin\Core->__construct()
      wp-content/plugins/content-control/classes/Plugin/Core.php:54
    9. ContentControl\plugin_instance()
      wp-content/plugins/content-control/content-control.php:131
    10. ContentControl\{closure}()
      wp-content/plugins/content-control/content-control.php:111
    11. do_action('plugins_loaded')
      wp-includes/plugin.php:517
    Plugin Author Daniel Iser

    (@danieliser)

    @simbian For the record I run Query Monitor while developing, and have not once seen these or they would have been cleaned up. I run full WP_DEBUG, SCRIPT_DEBUG enabled. I was only able to replicate this on the WP 6.8-beta.

    Not seeing any more after this one was fixed.

    • This reply was modified 2 weeks, 2 days ago by Daniel Iser.
    Thread Starter simbian

    (@simbian)

    Hello @danieliser thanks for your answer, uhm i continue noticing it, as you can see.
    I confirm im using WP 6.7.2.

    Hi everyone. I hope to be in the right forum.

    After update to WordPress 6.8-RC1, I have the same message. This happend for many themes and plugins.

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf 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 C:\MAMP\htdocs\my-site\wp-includes\functions.php on line 6121

    The previous message is about acf, but there’s many other affected textdomains.

    Affected textdomains: js_composer, acf, gp-limit-submissions, happy-elementor-addons and others, including my own custom theme.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.