• Resolved ccn225

    (@ccn225)


    Hi Lazy Blocks Team,

    First of all, thank you for creating such a great plugin; it’s been incredibly helpful for my work!

    I recently encountered the following error message:

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

    This might be related to my theme, but just in case, could you please confirm if this error might stem from the Lazy Blocks plugin?

    Thank you for your time and assistance!

Viewing 3 replies - 1 through 3 (of 3 total)
  • I am facing the same problem, the update to WordPress 6.7 generated this error.

    Anyone found a solution?

    EDIT: Turns out that I had ‘WP_DEBUG’ turned on in the wp-config.php file of WordPress. If you want to get rid of the error message, go in the wp-config.php file in your WordPress root folder and check the ‘WP_DEBUG’, if it is turned on and in case change it:

    define( 'WP_DEBUG', false );

    It was frustrating because the error was logged in the front-end and this workaround will hide the text, but the error still remains…

    • This reply was modified 5 days, 18 hours ago by lucalarcher.
    Thread Starter ccn225

    (@ccn225)

    Hello everyone,

    As a Japanese user, I often run into issues related to double-byte languages, so my first thought was, “Here we go again.” However, I’m relieved to see that this isn’t just happening to me, which confirms it’s not an issue with my custom WordPress theme.

    I shared the problem with ChatGPT and got this response:
    https://chatgpt.com/share/673dead4-58bc-8000-88b9-be1c31c52929

    The issue seems to stem from the timing of translation file loading. While it might be possible for users to implement a temporary fix, there’s a risk it could cause other problems. I hope the development team can address the root cause as soon as possible.

    Plugin Author nK

    (@nko)

    Hi,

    We are currently working on the plugin update and fix this issue. Please wait for the update to be released.

    I’m marking this topic as resolved. For further discussion, please continue the conversation here: https://github.com/nk-crew/lazy-blocks/issues/325

    Regards,
    Nikita.

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