Skip to content Skip to sidebar

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.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+02:00)

Tagged: 

This topic contains 7 replies, has 2 voices.

Last updated by Dražen 2 years, 9 months ago.

Assisted by: Dražen.

Author Posts
January 15, 2023 at 1:23 pm #12821471

mendixW

I am trying to: access my site normally but all of the pages in each language were not setup correctly.

Link to a page where the issue can be seen: Fixed already but this is the 2nd time this happened. The first time was December 17 which is similar timing but just a month ago. On the admin side, it said "Lets setup WPML". Luckily there was only one step that needed to happen when I went through that process and then everything started working properly. It did add a language switcher in the footer that I had to turn off. And it did reset the settings for Post Type Translation.

I expected to see: my pages organized by language

Instead, I got: none of my pages setup properly. All of my settings restarted.

January 16, 2023 at 7:11 am #12823949

Dražen
Supporter

Languages: English (English )

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

Hello,

thanks for contacting us.

Can you please check and make sure your hosting doesn't have set to clear larger autoload tables? We do have a similar issue when hosting automatically clears some larger keys, one of them WPML configuration settings, and that reset config and you need to set it up again.

Please check:
- https://wpml.org/forums/topic/wp-engine-clears-wpml-settings/#post-9617177

Regards,
Drazen

January 16, 2023 at 7:46 pm #12829417

mendixW

Thank you. Our vendor is also WPEngine.

They said we do not have Object Caching enabled.

And that they cannot disable clearing larger autoload tables: "We don't have a fix for this though. It's a platform setting we need to maintain performance. WPML may wish to optimize how their plugin saves and stores data in the database to avoid this issue on hosts like WP Engine and any others that use this same setting."

January 17, 2023 at 6:40 am #12831053

Dražen
Supporter

Languages: English (English )

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

Hello,

thanks for getting back.

I am afraid for now, there is not much we can do from our side, we have a developer ticket to optimize these keys, but this will take some time before it is done.

When I have more info I will update you via this ticket.

Hope you understand.

Regards,
Drazen

January 29, 2023 at 1:05 pm #12912299

mendixW

For reference, this happened again this morning.

January 30, 2023 at 6:31 am #12918511

Dražen
Supporter

Languages: English (English )

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

Hello,

yes, it will happen each time they key in DB goes over the limited size and then WPEngine deletes it.

I am afraid there is not much we can do from our side but we are working on improving and lowering the size. Once I have some new I will update you.

Regards,
Drazen

March 16, 2023 at 2:43 pm #13260829

mendixW

We've done some basic poking at the problem.

The issue is when our wp_option icl_sitepress_settings goes over a threshold size, WPEngine deletes it.

The icl_sitepress_settings value seems to get bloated because all the translatable ACF fields are being added there as well. On our site, we built out a limited page-builder using ACF's flexible content. Here's an example: we have a flexible content element called "Cards", that adds a repeater group to the page where each repeater element is a card with it's own heading, image, and body text.

When the page is published or "updated" (same button), WPML fills the icl_sitepress_settings with new field names for translation, something that looks like (this is a rough example)

i:1;s:xx:"flexible_content_1_card_heading";
i:1;s:xx:"flexible_content_1_card_image";
i:1;s:xx:"flexible_content_1_card_body"
i:1;s:xx:"flexible_content_2_card_heading";
...

We currently have 303 pages utliziing this page builder. So, after some time, when enough new pages have been created or updated, we get a db value over the 1 MB and the entire row gets deleted.

This completely resets WPML, causing us to have to go back and reset all our options, like which custom post types (13) and taxonomies (4) are translatable, which is a pain and requires us to keep a reference doc to ensure we set them correctly again.

We also have to turn off the WPML language footer.

Our thinking/question is: why are all these fields in the same wp_option table as the WPML sitewide settings?

March 17, 2023 at 7:06 am #13266557

Dražen
Supporter

Languages: English (English )

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

Hello,

thanks for getting back.

The reason why is because that key contains all settings needed for the WPML plugin, one of it being the translation settings of your custom fields.

I currently see the plan for optimizing this key is scheduled for WPML 4.7, so I hope soon we will some improvements here.

Thanks for your patience.

Kind regards,
Drazen