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 1 reply, has 2 voices.

Last updated by Mihai Apetrei 1 year, 10 months ago.

Assisted by: Mihai Apetrei.

Author Posts
July 27, 2023 at 1:54 pm #14111273

celiaS-2

Hello. We use WPML and ACF Pro on our sites hidden link and hidden link. At the end of last week, we tested the new functionality on our staging hidden link. We were adding new repeater fields in one of the existing ACF blocks (hidden link). And if we added all new fields (6) at once, we got a white screen and an error message, when saving fields. Error logs had a message, that the memory limit was exceeded (hidden link). So we only saved 1–2 fields at a time.
Here are the resources of our server (hidden link) (256 MB allocated within the current tariff plan). WordPress version - 6.2.2.
Here are the plugins, that we use (hidden link):
Advanced Custom Fields PRO - v 6.1.6.
Advanced Custom Fields Multilingual - v 2.0.5
WPML Multilingual CMS - 4.6.3
WPML String Translation - 3.2.5
WPML Media - 2.7.2
We made an appeal to our hosting provider (Kinsta) to increase the RAM limit to 512 MB, but unfortunately, this is only available in premium tariffs. But we were offered to choose a tariff with a large number of PHP Workers (4 instead of 2 that we have now). They also suggested cleaning up the database of revisions (the wp_post_meta table has about 2,000,000 on stage and 3,000,000 on production). Can it help?
Perhaps you can provide additional suggestions. Or maybe you know about the problem and the next plugin update might fix the problem.

July 27, 2023 at 4:02 pm #14112435

Mihai Apetrei
WPML Supporter since 03/2018

Languages: English (English )

Timezone: Europe/Bucharest (GMT+03:00)

Hi there.

Based on the information provided, the issue seems to be related to memory limit and server resources when using WPML and ACF Pro on the staging site.

Here are some suggestions to address the problem:

1. Database Cleanup:
As suggested by your hosting provider, cleaning up the database of revisions can help reduce the size of the database and potentially free up some memory. The large number of entries in the wp_post_meta table might be contributing to the memory limit issue. You can use a plugin like WP-Sweep to clean up unnecessary data, including revisions, transient options, etc. However, before performing any database cleanup, always make sure to have a full backup of the site in case of any unexpected issues.

2. PHP Workers:
Increasing the number of PHP Workers from 2 to 4 can potentially help improve performance, especially if you have a high traffic website or resource-intensive processes. More PHP Workers allow concurrent PHP requests to be processed simultaneously, which might prevent timeouts and memory issues.

3. Memory Limit:
While you couldn't get the memory limit increased to 512 MB, you can still optimize your site to work within the available 256 MB limit. One way to achieve this is by optimizing the theme and plugins, reducing the usage of heavy scripts, and avoiding excessive use of memory-intensive plugins.

4. ACF Pro and WPML Updates:
Ensure that you are using the latest versions of both ACF Pro and WPML plugins. Developers often release updates to fix bugs and improve performance, so keeping them up-to-date might resolve the issue if it's a known problem.

5. Repeater Field Optimization:
If the issue is specifically related to adding new repeater fields, you can try optimizing how you add the fields. Instead of adding all 6 new fields at once, try adding them one or two at a time, as you mentioned you were doing before. This could help you avoid hitting the memory limit.

6. Debugging:
Enable WP_DEBUG in your WordPress configuration to see if there are any specific error messages or warnings related to the issue. These messages can provide more insights into what might be causing the problem.

7. Server Cache:
If your site has caching enabled, try clearing the cache after making changes to the site. Sometimes, outdated cached data can cause unexpected issues.

Before making any significant changes to your site, it's essential to create a backup so that you can revert to a working state in case something goes wrong.

If you're unsure about how to proceed, consider seeking assistance from a developer with experience in WordPress, WPML, and ACF Pro to help you troubleshoot and implement these suggestions effectively.

I hope that you will find all this information helpful.

Mihai Apetrei