• Resolved Thomas

    (@thomhsb)


    Hello,

    I have this error with your plugin:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fluentform 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 /home/xxxxx/website.com/wp-includes/functions.php on line 6114

    Why just your plugin? Because I’ve run several tests and yours is the only one with this problem.
    Thanks

    • This topic was modified 10 months, 3 weeks ago by Thomas.
Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    Hello @thomhsb,

    Thanks for reaching out! Unfortunately, we couldn’t recreate the issue on our end. We’d love to understand more so we can find a solution. Could you share a screen recording showing the issue? This will help us see what’s happening and work on a fix.

    Thank you

    Same issue @amimulihsanmahdi

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fluentform 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 /home/sites/sitename/web/wp/wp-includes/functions.php on line 6114

    This is triggered in the front- and backend when debug mode is active. This bug was introduced in the 6.0 update.

    Edit:

    Traced it to the action

    add_action('plugins_loaded', function () {

    in the app.php file. This is called too early and should be at least on the init hook.

    • This reply was modified 10 months, 3 weeks ago by Levdbas.
    • This reply was modified 10 months, 3 weeks ago by Levdbas.
    • This reply was modified 10 months, 3 weeks ago by Levdbas.
    Thread Starter Thomas

    (@thomhsb)

    Thank you Levdbas!
    After Amimul Ihsan’s response, I was eagerly waiting for someone else to talk about it. @amimulihsanmahdi : In debug mode, it’s both frontend and backend. Query Monitor displays it too.

    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    Hello @thomhsb,

    We are working on this issue and we will release an update once the issue got fixed.

    Thank you

    Any updates on this issue? I have this error on my website for 2 weeks, is there any option to keep using fluent forms until you fix it?

    Thank you

    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    Hi there,

    The issue is fixed and we are planning to release an update soon.

    Thank you

    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    Hello again,

    We have released an update that fixes the issue.

    Thank you 

    Thread Starter Thomas

    (@thomhsb)

    Super, it’s perfect! Thanks a lot!

    Hi @amimulihsanmahdi , I updated to version 6.0.2 and still running into the same issue. The code is still called too early on the plugins_loaded hook.

    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    Hello @levdbas,

    Are you using any multilingual plugins? The issue might be happening due to compatibility with multilingual plugins. If you could share the details then we could take a deeper look.

    Thank you

    Hi @amimulihsanmahdi, no I also have this on standard themes without any plugins active. WP_DEBUG needs to be enabled though.

    I still see that the file ‘web/app/plugins/fluentform/boot/app.php’ is hooked to the plugins_loaded action, which is incorrect and should be the ‘init’ hook at the earliest.

    Thread Starter Thomas

    (@thomhsb)

    Finally, I agree with Levdbas
    Both in visitor and connected mode 🙁

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

    • This reply was modified 10 months ago by Thomas.
    • This reply was modified 10 months ago by Thomas.
    • This reply was modified 10 months ago by Thomas.
    • This reply was modified 10 months ago by Thomas.
    Plugin Support Amimul Ihsan

    (@amimulihsanmahdi)

    Hello @all,

    Thank you for the information. We have identified issue by following the information you provided and we have added the fix to our dev branch. The fix will be released in the upcoming update.

    Thank you again for the cooperation.

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Translation loading for the fluentform domain was triggered too early.’ is closed to new replies.