[Resolved] Change translation mode for existing page
This thread is resolved. Here is a description of the problem and solution.
Problem: The client needed to disable automatic translation for a specific page because it was preventing visibility of custom translatable fields in the Advanced Editor. Solution: We recommended setting the field
mfn-page-items
to Translate and then re-translating the page. We provided a step-by-step guide through our documentation:
If the provided solution is irrelevant due to being outdated or not applicable to your case, 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 issue persists, please open a new support ticket with us.
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 afraid that there isn't an option to reset the custom field preference. You can edit the file wpml-config.xml in the theme folder and get the reference of the default custom field preference of the theme.
Also, please follow the documentation to translate the page content https://wpml.org/errata/betheme-bebuilder-content-not-available-in-translation-editor/
OK; this is quite interesting. Here is the wpml-config.xml. I marked by an "x" after </custom-field> all the fields that are set in the config file but DO NOT APPEAR in WPML panel. As you can see, there are a lot of them. On the other hand, there are fields in the WPML panel that do not exist in the config file.
It is normal behavior. WPML will recognize the field in WPML > Settings > Custom Fields Translation if the field has a value in the database. Some fields in the config file .xml do not have a value so it they won't be available there.
OK, but what's about the fields that are dinamically created in DOM by JavaScript? And why there are wfm_* fields in your panel that ARE NOT in wpml_config.xml of BeTheme? That's strange.
what's about the fields that are dynamically created in DOM by JavaScript?
As I mentioned above, only the field that has the value in the database will be recognized and displayed in WPML > Settings > Custom Fields Translation.
why there are wfm_* fields in your panel that ARE NOT in wpml_config.xml of BeTheme?
Because the theme author doesn't add the field configuration to the file as the default. They can add anything on their end. The same for other themes and plugins.
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.