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.

Tagged: 

This topic contains 0 reply, has 1 voice.

Last updated by Alejandro 5 months, 1 week ago.

Assisted by: Alejandro.

Author Posts
December 19, 2024 at 12:32 pm #16530126

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

I meant in the entire database. when I check there via a plugin, I could see the main database had UTFMB3 as a collation instead of UTFMB4 which is the usual standard for WordPress sites.

About plesk, Could you try to initially disable all of them and let me know so I can test if everything's ok? if it is, then you can start enabling some of them while testing with different pages.

Would that be ok with you?

December 22, 2024 at 10:31 am #16537394

eddyD-5

Hi,

OK

I changes database to utf8mb4_general_ci and removed the security.

December 24, 2024 at 2:38 pm #16544040

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Ok we're getting somewhere now.

The problem with the translations is happening because something fails on the site (And we knew that). Before, we never got any sort of error or particular clue, but after you fixed the database collation and removed something else, I can start seeing the issues.

We get a very weird issue now:

PHP Warning: file_get_contents(/wp-content/plugins/wpml-translation-management/plugin.php): Failed to open stream: No such file or directory in /wp-includes/functions.php on line 6864

[24-Dec-2024 14:07:23 UTC] PHP Warning: file_get_contents(/wp-content/plugins/woocustomizer/woocustomizer.php): Failed to open stream: No such file or directory in /wp-includes/functions.php on line 6864

[24-Dec-2024 14:07:27 UTC] PHP Warning: file_get_contents(/wp-content/plugins/yith-infinite-scrolling/init.php): Failed to open stream: No such file or directory in /wp-includes/functions.php on line 6864

These say things like the site can't find files from plugins. it's showing a LOT of those, some of plugins that do not exist anymore like Translation Management!

Now, this usually means that either there's something in the DB with that info or there's something else, like a file or something with that configuration. does that ring a bell to you?

At the same time, did you update WPML from a really old version where translation management was indeed a separate plugin straight into this version?

I'll ask our devs to help me find something in the DB in the meantime so i can understand what to do next, because the error is super weird! I also saw another one where a WC language file was being called somewhere but was never really in existance. that usually happens with verion 6.7.X of WordPress yet you don't have it anymore!

Do you know if you have a server-side cache? if you do could you flush it and let me know which one? your hosting might need to let you know about this.

December 26, 2024 at 12:35 pm #16546879

eddyD-5

For below one i found some existing code and removed it.

This one i found [24-Dec-2024 14:07:27 UTC] PHP Warning: file_get_contents(/wp-content/plugins/yith-infinite-scrolling/init.php): Failed to open stream: No such file or directory in /wp-includes/functions.php on line 6864

I did not update from an old WPML version. But when the problem started i reinstalled wpml but this didn't fix the problem.

I cleared all litespeed cache settings and data.

December 30, 2024 at 9:50 am #16552684

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Can you please tell me how did you remove the problem you found? You have the same issue for at least 6 other similar plugins or files which is quite weird and could be the reason.

The main problem I found is that when I last checked you didn't even have some of the plugins that threw such warnings which meant that your site was trying to look for stuff that actually didn't exist and that didn't even need to be looked at. So something either has custom coding and is asking for content or you have some sort of cache somewhere that needs to be flushed.

Please let me know.

December 30, 2024 at 11:09 am #16552965

eddyD-5

For the pugin called yith-infinite-scrolling i remember i needed to add some code. I used the plugin code-snippets to do this.

When i removed the code snippets plugin this code was not removed.

On 26 Dec i re-installed the plugin code-snippets and then removed the yith-infinite-scrolling code and then removed the plugin code-snippets again.

The last days i was working on the taxonomy terms. I found out the default language for the taxonomies was english and not nl (dutch) so i changed this. I was updating and translating the taxonomies again. In the debug file i see alot of errors class-wpml-term-actions

But now i also see the taxonomy is not synchronizing with the other languages anymore.

January 3, 2025 at 5:07 pm #16562126

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Hi there,

I haven't forgotten about you. i have created a staging site inside your website to try to locate the source of the problem.

The problem is coming because of a code, likely from a plugin that is basically making WPML work incompletely (it lacks information other content should pass) and as a result, it ends up blocking everything. I'm trying to figure out which is it, because i sometimes get errors from things that do not exist on the site, which tells me that there's a code somewhere that is calling plugins or something from a plugin that is no longer being used.

I'll update you as soon as I know more and I apologize in advance if it's taking too much, the holiday traffic and some end-of-the-year vacations made things slower than usual.

I'll let you know as soon as I have more information 🙂

January 7, 2025 at 4:17 pm #16570750

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Hello there!

After a really really long and in-depth database check, i could see the problem stems from the fact that something prevented a page to be written in the native WordPress posts table, that created a series of problems that basically prevented you from translating anything else.

See, the content IS actually translated, but as soon as it's sent to the site, something on the site blocks the creation of the actual post so you can see it.

In fact there are many pages that seem translated in the past BUT that can't be translated anymore.

While I wait on our devs for further information about a solution, could you please let me know if you had previously translated content in the past with the advanced translation editor or only with the classic translation editor?

I hope we'll have a solution for you soon because I know it's been a long time. this is indeed a very particular case and you had a lot of plugins and variables on your site which made the process even longer but I'm confident we'll get to the bottom of it soon!

Thanks in advance.

January 8, 2025 at 10:49 am #16572927

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

The problem should be solved now. we cleaned out some corrupt entries among your tables and the problem disappeared.

I have also added some extra credits on your account since this problem took way longer than expected.

Regards.

January 8, 2025 at 6:17 pm #16574934

eddyD-5

Looks ok now. Thanks for the support !

January 9, 2025 at 10:20 am #16576993

Alejandro
WPML Supporter since 02/2018

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+02:00)

Awesome! I'm glad everything is better now.

This ticket will be open for another week in case something comes up, you can reply any time to extend the life of the ticket.

If the issue you encounter is different than this one, then I will split the ticket and close this one, then continue on the other one.

Regards.