[Resolved] 404 when creating translations using Divi Builder
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're trying to translate a page using the Divi Builder instead of the WPML Advanced Translation Editor and you encounter a 404 error page when attempting to start translating, we understand your frustration.
Solution: Here's a workaround that we've found to be effective: 1. Navigate to the
After applying this change, try editing the page using the Divi Builder without first saving or updating the page.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please 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.
I'm trying to translate a page using the WordPress editor (in this case, Div Builder) instead of the WPML Advanced translation editor.
Link to a page where the issue can be seen:
hidden link
I expected to see:
The English translation of the page in the Divi Builder.
Instead, I got:
404 error page when was about to start translating the page using the Divi Builder.
Here's a screen recording of the error (with sound): hidden link
There is no caching active. I've resaved permalinks and tried the buttons under WPML » Troubleshooting but that did not help. The default WPML Advanced Translation Editor works fine.
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
Upon reviewing your debug information, I have observed that the PHP limit for your "WP Memory Limit" is lower than the recommended 256MB or the required 128MB, as mentioned in the documentation found at: https://wpml.org/home/minimum-requirements/. To resolve this, I kindly request that you contact your hosting provider and request an increase in the PHP value for you.
The WPML Translation Editor has always worked fine. The problem occurs when using the Divi Builder. Here are two use cases where the 404 problem occurs:
1. I go to "Pages" and Switch to English (the flag in the wp admin top bar). Then I try to create a new (English page) with the Divi Builder and publish. Result: 404 error page.
2. I create a new Swedish page with the Divi Builder and publish. Then I choose "Edit page" and click "Translate this document with WordPress editor" using Divi Builder. Result: 404 error.
Please see if you can reproduce the error in the attached screen recording: hidden link
I've tested it on my end following the method you shared to replicate the issue but it worked fine on my end here. hidden link . Could you try deactivating the remaining plugins and leave only WPML activated and see if you're able to make this work correctly?
Could you also try to create a new English page from scratch? See video: hidden link
Wordpress editor translations works with Gutenberg but not with Divi Builder. A workaround could be to first create and publish the page using Gutenberg, and after that edit the page with Divi, but that's a workaround and quite time consuming. WPML must be compatible with Divi, right?
I can see the issue now. Yes, you're right, if we publish the page first, then we'll be able to edit it using DIVI builder. If not, it will show page not found.
Please allow me to escalate this and I will come back to you once I've feedback.
I'm reaching out to update you on your request. It's worth mentioning that due to the presence of a workaround solution, it diverges from our typical workflow, resulting in a lower priority. However, I want to assure you that our compatibility team has been notified, and they will investigate this promptly.
Thanks a lot for your thorough research! The solution seems to work, but I'm a bit hesitant to modify the Divi theme core files. It will be overwritten the next time I update Divi, and I don't want to override the Divi core.php file in my child theme since it might create conflicts with future Divi updates.
Is it likely that it will come an WPML update that fixes this compatibility issue with Divi in the future?
The resolution for this issue might not have been implemented in Divi yet, as it currently holds a lower priority. However, if additional reports are received regarding this matter, it will prompt further escalation.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.