_load_textdomain_just_in_time was called incorrectly

  • Resolved Nick Papazetis

    (@papazetis)


    3 months, 3 weeks ago

    I am getting this warning on Query Monitor

    Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf-font-awesome 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. (This message was added in version 6.7.0.)+

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Matt Keys

    (@mattkeys)

    I saw this reported by another user and I wasn’t able to reproduce it in my environment. If a call to get_field or similar happens before ACF initializes itself it will initialize early and maybe that is causing this notice to appear?

    Thread Starter Nick Papazetis

    (@papazetis)

    I have both acf and acf fontawesome plugins as must-use-plugins

    I ll double check my set up

    Thread Starter Nick Papazetis

    (@papazetis)

    Hi @mattkeys ,

    I think I found the issue.
    The load_plugin_textdomain( 'acf-font-awesome', false, plugin_basename( dirname( __FILE__ ) ) . '/lang' ); is loading in acf/include_field_types action and that is causing the warning.

    I add it on initaction and it doesn’t return an error

    Hope this helps

    Having the same issue, it’s fairly common for most plugins after the 6.7.1 update. The easiest way to reproduce it is to log in as an admin and then change your user account’s language to anything other than the default. Nick’s suggestion above also solves the issue for me.

    • This reply was modified 1 month, 3 weeks ago by plaidpowered.
    • This reply was modified 1 month, 3 weeks ago by plaidpowered.
    Plugin Author Matt Keys

    (@mattkeys)

    I just released v4.1.2 which should help address this issue. This was only showing up on sites which call ACF fields/functions before ‘init’ which is why I was not able to reproduce the problem initially.

    However moving this to ‘init’ seems to be more correct anyways and will resolve this issue for those sites which may be forcing ACF to load itself early.

    Thread Starter Nick Papazetis

    (@papazetis)

    Thank you @mattkeys!

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