Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Sun Mon Tue Wed Thu Fri Sat
- 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 12:00 – 14:00 -
- 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 17:00 – 21:00 -

Supporter timezone: Europe/Vienna (GMT+01:00)

Tagged: 

This topic contains 3 replies, has 0 voices.

Last updated by Bigul 6 days, 3 hours ago.

Assisted by: Bigul.

Author Posts
November 21, 2024 at 5:35 am #16427279

draganF

I think the problem with database is solved. But now I got PHP Warning.
You can see everything on screenshot attached.

16426662-Screenshot_21.png
November 21, 2024 at 11:02 am #16428579

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

Welcome to the WPML support forum. I will do my best to help you to resolve the issue.

Are you getting this warning in all the pages? Please share with us the WordPress debug.log(not WPML debug information) for collecting more details on this. Refer to the following pages for instructions

https://wpml.org/documentation/support/debugging-wpml/

https://wordpress.org/documentation/article/debugging-in-wordpress/

To enable WordPress Debug log, open your wp-config.php file of site root and look for define('WP_DEBUG', false);. Change it to:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
 
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
 
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

In this case, the errors will be saved to a debug.log log file inside the */wp-content/* directory. Please do the steps to reproduce the bug and check you are getting any errors or warnings related to WPML in the log file.

If you can paste your debug.log to http://pastebin.com/index.php and provide me that link it would be great! (This is the cleanest way because sometimes the logs are long and create a complete mess of discussion).

--
Thanks!

Bigul

November 21, 2024 at 1:29 pm #16429252

draganF

Here is link.
https://pastebin.com/CLpQezRr

I noticed so far that I got this error only when go to Properties (to list properties and Edit...) or Add new property.
I did not noticed it anywhere else.

November 21, 2024 at 5:24 pm #16430488

Bigul
Supporter

Languages: English (English )

Timezone: Europe/Vienna (GMT+01:00)

Hello,

Thank you for the updates and Debug log details. However, the Debug log shows no warnings or errors related to the WPML. So please make sure any WPML warning or error is tracked in the Debug log while doing the following steps.

I noticed so far that I got this error only when go to 
Properties (to list properties and Edit...) or Add new property.

Maybe you are facing this issue because of compatibility conflicts. So to make sure if possible, please do the following steps.

a) Backup your site first[Mandatory]
b) Deactivate all the plugins that are not related to WPML and Houzez theme
c) Then check the issue is existing or not
d) If the issue is gone, activate the plugins as a group of three or four to find which one has an interaction issue

--
Thanks!

Bigul