Function _load_textdomain_just_in_time was called incorrectly.

  • Resolved apsuhos

    (@apsuhos)


    1 year, 1 month ago

    PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. I had no issues with this notice until I changed the answer to “Does your website use third-party services?” from Yes to No, because my site doesn’t use marketing cookies and I didn’t want the marketing section to appear on the cookie policy page or banner. As soon as I selected No, the _load_textdomain_just_in_time notice popped up and the cookie banner stopped displaying. On the cookie policy page I got this under 7.1 section.

    You have loaded the Cookie Policy without JavaScript enabled. On AMP (Accelerated Mobile Pages) pages, you can use the consent management button located at the bottom of the page.

    JavaScript was enabled and it was not an AMP.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    1 year, 1 month ago

    Hello @apsuhos ,

    Thank you for reaching out.

    Regarding the PHP notice about _load_textdomain_just_in_time, this issue was addressed in our updates some time ago. If you’re still seeing it, it’s likely being triggered by a third-party plugin that’s forcing translation loading too early. Could you let us know which other plugins are currently active on the site?

    As for the Section 7.1 message (“You have loaded the Cookie Policy without JavaScript enabled”), that typically points to a REST API issue. Would you be able to share the URL of your website so we can take a closer look?

    Thanks in advance.
    Best regards,
    Antonio

    Thread Starter apsuhos

    (@apsuhos)

    1 year, 1 month ago

    Hello!

    I’m aware that the issue has been addressed, I’ve read about it. Unfortunately, the site is not publicly accessible yet.

    There were several plugins installed, but I went ahead and deactivated all of them except Query Monitor. The problem still persisted. So, I spun up a clean local instance using the TT5 theme and installed only Complianz and Query Monitor. I went through the wizard and managed to get the banner working.

    However, as soon as I went back and changed the setting “Does your website use third-party services?” from “Yes” to “No”, I received the PHP notice again.

    Edit: Just tried it on the WordPress playground and got the same notice.

    • This reply was modified 1 year, 1 month ago by apsuhos.
    Plugin Support Antonio Candela

    (@antoiub)

    1 year, 1 month ago

    Hello @apsuhos ,

    Thank you very much for the detailed feedback and for taking the time to test this.

    I’ve tried to replicate the behavior both in the WordPress Playground and in a Local environment, but I wasn’t able to trigger the PHP notice, even after changing “Does your website use third-party services?” to “No”.
    I tested it using:

    • WordPress 6.8.2
    • PHP 8.3 / 8.0.16
    • Complianz 7.4.2
    • Query Monitor 3.19.0
    • Theme TT5

    Were you perhaps using a different WordPress / PHP / Plugins version, or was everything up to date on your end?
    If possible, a short video showing how you reproduce the issue would be very helpful.

    Thanks again for your support and detailed input!

    Best regards,
    Antonio

    Thread Starter apsuhos

    (@apsuhos)

    1 year, 1 month ago

    Hello!

    I recorded a video in WordPress Playground

    • WordPress 6.8.2
    • PHP 8.3.23
    • Complianz 7.4.2
    • QM 3.19.0
    • TT5

    Let me know if you need anything else.

    Plugin Support Antonio Candela

    (@antoiub)

    1 year, 1 month ago

    Hello @apsuhos ,

    Thank you. I was implementing a statistics category, which is why I wasn’t able to replicate the issue at first. It seems the error is triggered when only Functional is available in the cookie categories.

    I’ve created an internal task, which is currently pending review.
    I’ll update the thread as soon as I hear back from the team.

    Best regards,
    Antonio

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

The topic ‘Function _load_textdomain_just_in_time was called incorrectly.’ is closed to new replies.