Problem: The client set a new homepage using SiteOrigin Premium and configured it as a static page in WordPress settings. However, the new homepage does not display the layout built with SiteOrigin, showing instead the layout of the old homepage without a sidebar. Solution: We determined that the issue is not related to WPML. Here are the steps we took to diagnose the problem: 1. Temporarily deactivated WPML to ensure the issue was not related to the translation plugin. 2. Set the new homepage as a static page in the original language under Settings → Reading. 3. Found that the homepage still did not display the SiteOrigin layout, even with WPML deactivated. Since the problem persists without WPML, it suggests that the issue is related to either the theme or SiteOrigin itself. We recommend contacting SiteOrigin support for further assistance.
If this solution does not resolve your issue or seems irrelevant, 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 the problem persists, please open a new support ticket with us.
Problem: The client is trying to create custom translations for each post using the WPML Advanced Translation Editor (ATE), skip translation fields, avoid adding HTML, and manage non-WPML plugin translations separately.
Solution: 1. Custom translations with different designs or content amounts cannot be created using ATE; instead, use the WordPress editor. For more details, see this guide. 2. There is no persistent 'undo' button in ATE. To undo automatic translations within the same session, use the available 'Undo translation' button. To redo translations, consider deleting them or resending them via the Translation Management Dashboard. 3. All translation fields must be completed in ATE; to add text not present in the original, or to skip HTML, use the WordPress editor. 4. To exclude WPML ATE from translating content managed by other plugins like WP Recipe Maker, use the WordPress editor.
If this solution does not resolve your issue or seems outdated, 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.
