• Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fullwidth-templates domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Shea Bunge

    (@bungeshea)

    I don’t think that error message is coming from this plugin – the fullwidth-templates domain isn’t one Code Snippets uses at all.

    Thread Starter Insect Trojan

    (@insecttrojan)

    sorry I didn’t paste it all because the next is in greek for the code snippets

    PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>fullwidth-templates</code> 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 <code>init</code> action or later. Please see <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/insect.gr/httpdocs/wp-includes/functions.php on line 6114[19-Nov-2024 14:36:14 UTC] PHP Notice: Η συν?ρτηση _load_textdomain_just_in_time κλ?θηκε <strong>εσφαλμ?να</strong>. Η φ?ρτωση τη? μετ?φραση? για τον τομ?α <code>code-snippets</code> ενεργοποι?θηκε πολ? νωρ??. Αυτ? ε?ναι συν?θω? ?νδειξη για κ?ποιο κ?δικα στο πρ?σθετο ? το θ?μα που εκτελε?ται πολ? νωρ??. Οι μεταφρ?σει? θα πρ?πει να φορτ?νονται στην εν?ργεια <code>init</code> ? αργ?τερα. Παρακαλ? δε?τε τη σελ?δα <a href=”https://developer.www.ads-software.com/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> για περισσ?τερε? πληροφορ?ε?. (Το μ?νυμα αυτ? προστ?θηκε στην ?κδ. 6.7.0.) in /var/www/vhosts/insect.gr/httpdocs/wp-includes/functions.php on line 6114

    Plugin Author Shea Bunge

    (@bungeshea)

    Ah I see, makes sense! I’m not seeing this error myself, but I think I’ve identified where it might be occurring. I’ll see about releasing a patch shortly to fix it up.

    Thank you for reporting it!

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