[Resolved] Menu sync time out issue - workaround or Patch?
This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing timeouts with Cloudflare when using WPML to synchronize and translate menus due to high resource usage and extensive database queries. This issue is exacerbated by the n+1 query problem with a large number of menu options and languages. Solution: We recommend the following workarounds to address the timeout issue: 1. Manually translate the menu to avoid triggering the resource-intensive synchronization process. 2. Temporarily disable Cloudflare while running the menu synchronization or translation process, which will prevent Cloudflare from stopping the request. 3. Consider upgrading to Cloudflare Pro, which allows for a higher timeout limit (up to 100 seconds), potentially preventing these interruptions.
If these solutions do not resolve your issue or seem outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
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.
I created a video showing that it works on our side: hidden link but I recommend developing the site outside Kinsta because their cache memory is too aggressive, and you will get false positives all the time. Once the site is finished, you can restore it in Kinsta and continue from there.
1.- Could you tell me what you mean by " developing the site option is not an option for us"?
2.- Yes, we have been working on the staging site to avoid running tests on the production site. This is done for security reasons, and it is a good practice.
3.- I have set your next message private so you can share the credentials to the new staging site, where we will continue running any tests necessary.
The problem with Kinsta is that the cache is very aggressive, and sometimes the changes made to the site are not reflected, including the ones to the menus.
Regarding the suggestion I made earlier, because of the aggressive Kinsta cache memory, taking a copy of the production site outside Kinsta, making the changes, and the restore it in Kinsta is not difficult to do and will save you time.
