PHP notice after core update

  • Resolved numero7

    (@numero7)


    2 months, 2 weeks ago

    I received the following notice after upgrade to WP 6.7.1 :
    Notice: Function _load_textdomain_just_in_time was called?incorrectly. Translation loading for the?wp-asset-clean-up?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.

    Can you check if code should be updated on your end ? thanks in advance for this great plugin.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @numero7 in what particular page have you noticed this problem? I’ve done everything I could to debug this, and I couldn’t get this error. This notice was showing up from other plugins while I was doing tests, but never from Asset CleanUp. Some print screens would be good if you can provide some!

    You can use a service such as https://imgbb.com/

    Plugin Author Gabe Livan

    (@gabelivan)

    @numero7 just so you know, I managed to locate the errors! So, thank you for pointing them out. This will be fixed in the next release for sure. However, if you want benefit from the next release sooner (that is in testing at the moment), without having these notices, you can download the development version which, in essence, is the next version of the plugin (e.g. in case minor issues will be found during testing, they will be fixed).

    Here’s how you can do that: https://www.assetcleanup.com/docs/how-to-get-the-development-version-of-asset-cleanup/

    Thread Starter numero7

    (@numero7)

    Hey, thank you very much for having checked.. no worries I can wait next release ??
    Thank you again

    • This reply was modified 1 month, 2 weeks ago by numero7.
    Plugin Author Gabe Livan

    (@gabelivan)

    @numero7 this has been fixed in the latest version that was just released: v1.4.0.1. If you will notice this problem again in the plugin, let me know and I will check it out!

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