Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support tonysupport

    (@tonysupport)

    Hi tom,

    Thanks for contacting us.

    Could you let me know which version of WordPress you’re using?

    Also, could you please enable WordPress’s debug mode and logging by following this guide: Debugging in WordPress. Once enabled, please reproduce the issue and check if any descriptive error messages appear, especially ones that reference a specific file in the plugin.

    Additionally, could you check the debug log for any entries around the time the error occurred and share that section with us? This might give us more insight into what’s going wrong.

    You can keep WP_DEBUG_DISPLAY set to false so the log entries do not display on your website, if that would help.

    Thread Starter tomtom3000

    (@tomtom3000)

    Hello, ok i did what you said and i get the error message below.

    Also i use the newest WordPress Version 6.7.

    I googled a bit and it seems to be a common issue with the new wordpress version. Can you pleaes fix this?

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the restaurant-reservations 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/pizzeriagaiser.webfromtom.it/public_html/wp-includes/functions.php on line 6114

    Plugin Support tonysupport

    (@tonysupport)

    Hi Tom,

    Thanks for sharing that information.

    We’re looking into this issue, as it appears related to a change in WordPress 6.7. In the meantime, you can roll back to WP 6.6 to avoid the error.

    We’re hoping to release an update when we figure out exactly what the issue is within the plugin, as we use the ‘init’ hook to load our translations currently.

    Thread Starter tomtom3000

    (@tomtom3000)

    Hello, i just saw that now it seems to work now and i changed nothing. Pretty strange as the error still shows up once i change the WP_DEBUG to “true”. My case is resolved but you should probably fix that error anyway. Thank you very very much for the awesome support. And please let me know once an update is availible.

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