Problem: You created and published a page and its translation using WPML, but the translated page shows a 'not found' error despite having purged caches and updated permalinks. Solution: We recommend running several troubleshooting options in WPML. First, navigate to WPML → Support and click on "Troubleshooting". Here, you should: 1. Clear the cache in WPML. 2. Remove any ghost entries from the translation tables. 3. Set the language information. 4. Fix post type assignments for translations. Additionally, check the .htaccess file for rules that might cause incorrect redirects. Rename the current .htaccess file in the root folder of your WordPress installation, then go to Settings → Permalinks and save the permalinks to create a new .htaccess file. Remember to back up your database before making any changes.
If this solution does not resolve the issue or seems 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.
Problem: You are using WPML to translate your WordPress site and have noticed that the custom field boxes do not appear in the block editor for translated versions. Solution: 1. Ensure that the ACF Field Groups are set to "Different fields across languages" when editing the groups in ACF. 2. Set WPML > Settings > Post Type Translation > ACF Field Groups to "Not translatable". 3. If using the WordPress Editor for translating content, you must manually edit the custom fields on the translated content. 4. For using the "Expert" mode for your ACF Groups, set the custom fields to "Copy once", which will copy them only once, allowing them to be edited on the translated post or page. 5. Increase the WordPress memory limit to at least 256 MB as WPML requires a minimum of 128M. You can do this by adding the following code to your wp-config.php file:
define ('WP_MEMORY_LIMIT', '256M');
Add this just before the comment:
// That's all, stop editing! Happy blogging.
6. Check the current server values under WPML > Support > WordPress and contact your hosting provider if changes are not applied.
If these steps do not resolve your issue or the solution seems outdated, we 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.
