Problem: You are working on a site under development and facing issues with displaying variations and menus in Arabic. The variations and menus are not displaying correctly in Arabic. Solution: We have identified that the Max Mega Menu plugin used on your site is not fully compatible with WPML. To address this, you can follow the workaround provided in the Max Mega Menu documentation to make the menu translatable. Here is the guide: https://www.megamenu.com/documentation/wpml-setup/ If you encounter any issues during this process, we recommend contacting the plugin author and informing them of the compatibility issues. We are also willing to collaborate with them to enhance WPML compatibility.
Please note that this solution might be outdated or not applicable to your specific 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 problem persists, please open a new support ticket.
Problem: You are experiencing issues with automatic translation not working on your site using WPML. Solution: We recommend you try the following steps: 1. Navigate to Plugins → Add New and select the Commercial tab. Click on 'Unregister WPML from this site'. 2. Once the page reloads, click on 'Register WPML'. 3. Register the site using the new key. 4. Check if the automatic translation is now functioning. If the problem continues, please follow these additional steps: 1. Go to Plugins → Add New, select the Commercial tab, and click 'Unregister WPML from this site'. 2. After the page loads, click on 'Register WPML'. You will see a prompt to enter the site key. Click on 'Get a key for this site'. 3. In your WPML account, complete the site key wizard and set it to 'Production site'. 4. Copy your new key and paste it in the Commercial tab. Afterwards, you can delete your old site key in the WPML account. 5. Reassign the credits to the newly registered site. 6. Attempt to translate again.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You are experiencing issues with the automatic translation feature in WPML not functioning properly.
Solution: We recommend creating a new sitekey by adding your site to your WPML account manually. Here are the steps to follow: 1. Navigate to Plugins -> Add New -> Commercial in your website. 2. Click on the register link to start the site registration process in your WPML account, ensuring you use the exact Site URL. 3. During registration, specify whether this site is for production or development, decide the number of credits to assign, and create the new site key. 4. Return to Plugins -> Add New -> Commercial on your website. 5. Use the newly created site key to register by clicking the register link again.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Solution:
The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.
First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.
To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:
define('WP_DEBUG', true);
To enable the error logging to a file on the server, you need to add yet one more similar line:
define( 'WP_DEBUG_LOG', true );
The errors will be saved to a debug.log file inside the /wp-content/directory.
Solution:
The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.
First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.
To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:
define('WP_DEBUG', true);
To enable the error logging to a file on the server, you need to add yet one more similar line:
define( 'WP_DEBUG_LOG', true );
The errors will be saved to a debug.log file inside the /wp-content/directory.
Solution:
The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.
First, you need to see what the errors are. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.
To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:
define('WP_DEBUG', true);
To enable the error logging to a file on the server, you need to add yet one more similar line:
define( 'WP_DEBUG_LOG', true );
The errors will be saved to a debug.log file inside the /wp-content/directory.
