• Resolved juliankauai

    (@juliankauai)


    Hi, I was experimenting with moving up to PHP 8.3 and when I did that, I got this error below. I moved back to 8.2 for now. But I hope you all take a look at it. I don’t know if it has to do with you, but you have the only translation plug-in on our site. Let me know if I can help in any way. Thanks

    PS If anyone else has seen this or knows how to fix it, please let me know. I’d like to move the site to php 8.3

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the plumamazing 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 /mnt/customers/customers-bh-1b8fk4/6bd1350e-a12e-4a44-ab17-c40db8595417/wp-content/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-software-add-on 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 /mnt/customers/customers-bh-1b8fk4/6bd1350e-a12e-4a44-ab17-c40db8595417/wp-content/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the elementor 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 /mnt/customers/customers-bh-1b8fk4/6bd1350e-a12e-4a44-ab17-c40db8595417/wp-content/wp-includes/functions.php on line 6121 Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-gateway-stripe 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 /mnt/customers/customers-bh-1b8fk4/6bd1350e-a12e-4a44-ab17-c40db8595417/wp-content/wp-includes/functions.php on line 6121 Notice: Function WP_Block_Patterns_Registry::register was called incorrectly. Pattern content must be a string. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /mnt/customers/customers-bh-1b8fk4/6bd1350e-a12e-4a44-ab17-c40db8595417/wp-content/wp-includes/functions.php on line 6121

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author edo888

    (@edo888)

    Hi,

    There is no connection to GTranslate plugin.

    Thanks! 🙂

    The problem:  Changing from *PHP 7.4 to PHP 8.3 results in a critical error on my WordPress Website <heilbronn.ac.uk>.  After upgrading to PHP 8.3 my site went offline (blank).  I switched back to PHP 7.4 and my site works fine with PHP 7.4 so far.

    The Cause:  I’ve learnt from our web hosting service company that the theme (Passage) is causing the issue.  I’m not sure if they are right.

    Questions: How can I check what part of the theme is causing the issue and how to fix it?  I’m currently running WordPress 6.8.2 and PHP 7.4.

    Problems with changing the theme (passage):  Changing the theme (Passage) can significantly change how my website looks and functions. It might cause problems with layout of the page and post content, widgets, sliders etc.. 

    Dashboard message:  Your site has a critical issue that should be addressed as soon as possible to improve its performance and security. Your site is running on an outdated version of PHP (7.4.33), which does not receive security updates. It should be updated.

    I hope someone can help me with this issue. Thank you.

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

The topic ‘changing to php 8.3 produced this error’ is closed to new replies.