Available Solutions

Problem:
The client was experiencing a conflict when enabling WPML String Translation and Elementor Pro simultaneously, leading to a 500 error on their website.
Solution:
We recommended the following steps:
1. Verify that the server meets all WPML minimum requirements.
2. Consult our FAQ on 500 errors for potential solutions.
3. Enable WordPress debug to identify the specific error by following our debugging guide.
4. Perform a compatibility check by:
- Creating a full website backup.
- Disabling all plugins except for WPML and its add-ons.
- Switching to a default WordPress theme like TwentySeventeen.
- Reactivating plugins one by one to identify the conflicting plugin.
5. If the issue persists, it may be related to server/hosting settings, particularly the 'allowed memory size exhausted' error. We provided a custom search URL to explore existing tickets with similar issues and solutions.
6. We also suggested updating to the WPML 4.6.10 beta version after creating a full website backup and removing the current WPML version.

If these steps do not resolve the issue or if the solution is outdated or not applicable, we recommend opening a new support ticket. We also advise checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.

For further assistance, please contact our support team.

Problem:
The client was experiencing issues with the layout of the home page when switching to the French language, and sometimes pages would disappear after modifications. The problem seemed to be primarily with the navigation menu.
Solution:
1) We permanently deleted the menu items that were in the trash and re-translated the pages. Then, we deleted the French menu and synced the menu again, which resolved the menu issue.
2) For the home page layout issue, we suggested that the client re-create the affected section in the default language and then update the translation to see if the issue persists.

If you're experiencing similar issues, we recommend you try the following steps:
- Permanently delete any menu items in the trash and re-translate your pages.
- Delete the problematic menu and sync it again.
- Re-create any sections of your home page that are not displaying correctly in the default language, and then update the translation.

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If these steps do not resolve your issue, we highly recommend checking the 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.

Problem:
The client re-installed WPML on their blog and set Dutch as the default language and English as the secondary language. They wanted a language dropdown in the menu and footer. However, the website only displayed in English, and no language selector was shown. The client's attempts to remove the "/en" from the URL were unsuccessful, and the only solution seemed to be deactivating the WPML plugin. The issue persisted even though the client had set the website not to follow the browser's language settings.
Solution:
First, we asked the client to enable the WordPress debug log to identify any potential errors. We provided instructions and the necessary code to add to the wp-config.php file:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

We also requested that the client increase the WP Memory Limit to 256 MB and the MaxInputVars to 10000 for better performance, providing links to relevant documentation:

• WPML minimum requirements,
• Increasing memory allocated to PHP,
• Setting the MaxInputVars directive in an .htaccess file

Upon further investigation, we found that the homepage had not been translated into Dutch. We advised the client to complete the translation of the homepage and check if the language switcher appears and works correctly on other pages, providing examples where the language switcher was functioning properly.

If this solution does not seem relevant to your situation, please open a new support ticket with us.