[Resolved] WP Dashboard has gotten really slow since using WPML

Hello,

I have now also installed the latest versions of our plugins, which are solving a performance issue between WPML String Translation and the latest version of WordPress.

When activating WPML there appear various database errors regarding duplicated entries that refer to post attachment in the Dutch language.

I went to WPML > Support > Troubleshooting and ran the option to synchronize post taxonomies for "Media" (4573 posts were processed for "attachment").

Now, when deactivating and then activating WPML again I can no longer confirm those errors.

The only errors I currently can confirm on the site are PHP Deprecated Notices coming from our Sticky Links plugin - those should not harm the site, they only refer to the fact that a specific function used in PHP inside this plugin will work in a different way in the upcoming version of PHP and our developers by then should adapt the code.

At the moment I can not confirm any performance issue on the site caused by WPML.

Could you please revise this on the test site now and let me know if further assistance is needed?

Best regards
Andreas

Hello,

Yes, this is what I ask you to do and I would appreciate it of you could point me toward a page where you see an unexpectedly high loading time with the amount in seconds, as I can not confirm any unexpectedly high load time on the test site by now.

Best regards
Andreas

Hello,

I actually only wanted you to revise the test site in its current state to let me know if you still see performance issues there.

Also, if you decide to delete the test site, take note again that I had to take this step:

When activating WPML there appear various database errors regarding duplicated entries that refer to post attachment in the Dutch language.

I went to WPML > Support > Troubleshooting and ran the option to synchronize post taxonomies for "Media" (4573 posts were processed for "attachment").

Best regards
Andreas

Hello,

I am glad to hear that we made advancements on this matter.

These Deprecated Notices should not harm your site at the moment - they are only showing up because WP DEBUG is enabled on this site.

Those notices do refer to the fact, that there might occur issues on the site if the code for active plugins will not be adapted for the future version of PHP.

Some of these notices refer to WordPress Core itself, which means you first should make sure to use WordPress 6.3.1 or wait until a future version of WordPress will solve these issues.

Other errors of this kind might refer to PHP functions used in plugins, like in this case our "Sticky Links" plugin.

I tested this on a local test site with WPML and Sticky Links on PHP 8.2 and I can replicate this Notice there which is why I have escalated this issue now including a suggestion about how to solve this issue internally.

This request will have to be reviewed by our developers and tested to be implemented into a future version of the Stocky Links plugin, but please take note again, that this will not impact the site while using the current latest version of PHP.

If you need any assistance to apply changes to the live site, please let me know.

Best regards
Andreas

Hello,

1) Those errors will only show up with WP DEBUG is enabled.

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

Also take note, that this issue has already been escalated internally and will be handled before the upcoming PHP version will be available.

2) and 3) Yes, there are also two Notices for WordPress itself on the site such issues are handled by the WordPress Core Team.

Imagine it like this:

PHP uses integrated functions, like for example strlen() which is a function that will let you determine the length of a string.

It is a simple example, as you pass here only one argument, a string, and it will count the characters.

Other functions are way more complex.

Those functions sometimes change the way they work in different versions of PHP and then WordPress-, Theme- and Plugin developers will need to update their code in order to keep it working with the upcoming version of PHP, which in this case might be 8.3.0.

This is what a Deprecated Notice refers to and there is nothing you can or need to do about it from your side, but reporting such issues and waiting for them to be fixed.

4) The private reply form is enabled. Please make sure to take a backup of your site and database before providing access.

5) Yes, you can delete the test site.

Best regards
Andreas