A mysterious message and a theme that doesn’t work well

  • Resolved cadrago21

    (@cadrago21)


    7 months, 2 weeks ago

    Good morning I have a site updated to the latest version of wordpress with the enfol theme, as soon as I install in your plugin in the free version it completely messes up my whole theme and I get this error message:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uncanny-automator 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/customer/www/christianbardus.it/public_html/wp-includes/functions.php on line 6121

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Ken Young

    (@uncannyken)

    7 months, 2 weeks ago

    Hi @cadrago21,

    Sorry you’re experiencing this issue! There are a couple of things at work here:

    1. We need to update the loading of translations for compatibility with WordPress 6.7.0, which will happen with the next release, due out next week.
    2. The notice is breaking your theme because it’s being output in places that cause the layout to break.

    #2 could be fixed immediately if you disable debug output on your WordPress site. You’d want to set WP_DEBUG to “false” in your wp-config.php file. There’s some additional info on this here: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/, but you could also ask your webhost’s support for help if you’re not comfortable making that change yourself. Alternatively, you could wait until the next release and update Automator, and that would also fix the issue.

    Please let us know if you run into any other issues.

    Thanks,
    Ken

    submon

    (@submon)

    4 months, 2 weeks ago

    Not sure if you have resolved this yet but I also am seeing this error in my logs. I seem to be up to date. This notice is filling up my logs so I’d love to see it resolved though I no it’s not necessarily breaking anything at the moment.

    Plugin Support Ken Young

    (@uncannyken)

    4 months, 2 weeks ago

    Hi @submon, thanks for following up.

    You’ll see in our changelog that we did release a fix for this in version 6.5.0. However, we identified an issue with that fix that was causing some triggers to not fire, so we had to revert that fix in version 6.5.0.2. Unfortunately, due to the way Uncanny Automator works by hooking into other plugins, it’s a more challenging problem that we had originally anticipated.

    We do have another fix in the works though, so we’re hoping we can get that resolved in the near future.

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

You must be logged in to reply to this topic.