Skip to content Skip to sidebar

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing an issue with database bloat that was supposed to be resolved in WPML version 4.8, but the problem persists and seems to have worsened. The client is also concerned about the focus on new features over resolving existing issues.
Solution:
We advised the client to refer back to the original ticket where this issue was escalated, as it is still open and monitored by our second-tier support and developers. The resolution of the database bloat issue was postponed to a later version (4.9) due to its complexity and the need for further work and testing. We encouraged the client to continue the discussion in the existing ticket to keep all relevant information in one place and ensure proper tracking.

If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket.

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 3 replies, has 1 voice.

Last updated by Dražen 2 months, 3 weeks ago.

Assisted by: Dražen.

Author Posts
August 28, 2025 at 9:36 am #17354127

sanderv-27

Background of the issue:
Hello,

we have been talking about database bloat for a while (months).
It was promised that in 4.8 it would be resolved, but as of now the database seems even bigger.
A cache was added, and existing items have grown over time.

Am I misreading this, or was this promise not fulfilled?

Symptoms:
The database appears to be larger than expected, despite promises of resolution in version 4.8.

Questions:
Am I misreading the situation regarding the database bloat?
Was the promise to resolve database bloat in version 4.8 not fulfilled?

September 1, 2025 at 9:44 am #17361933

Dražen
Supporter

Languages: English (English )

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

Hello,

I am not sure to which escalated issue are you referring to.

Do you mean the one you reported in this ticket: https://wpml.org/forums/topic/wp_installer_settingsis-autoload-and-large/?paged=3

As I can see, ticket is still opened so you can always post a reply there and 2nd tier can follow up or forward your reply to 2nd tier / developer.

Just to answer your question, seems this was not included in current release due to complexity of the issue, and it needs further work and testing.

If you still have doubts about same problem, please post reply in related ticket, as we do not allow same duplicate tickets, and that one is already escalated.

Hope this helps.

Regards,
Drazen

September 1, 2025 at 12:50 pm #17362566

sanderv-27

Hello Drazen,

is there an easy to find my previous tickets? I cannot seem to find my previous (resolved) tickets.
However, there was one created where was promised this issue would be resolved in the upcoming 4.8 version.

It is a big disappointment to here that instead of living up to that promise, you did not only postpone a solution, the issue has only gotten worse.

I understand it is appealing to focus on AI and generate revenue by your new translation service, but in the meantime the underlying quality of your plugin is degrading.

So now that the promise is not fulfilled, when is this scheduled to be resolved?
--
Update: i see it was promised to be resolved in 4.9

September 1, 2025 at 1:10 pm #17362684

Dražen
Supporter

Languages: English (English )

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

Hello,

thanks for getting back.

You can find all of your tickets under your profile URL: https://wpml.org/forums/users/sanderv-27/

As I can see from your last reply, you mention it was promised for 4.9, not 4.8.

I would appreciate it if you have any other question on this issue and topic to post them in the related ticket, since all the information are there and that ticket is connected to escalated developer ticket and is monitored for any replies.

Regards,
Drazen