![]() ![]() Switching to "text" discovered some elementor code. WPML also copied some elementor code in the translation which wasn't visible when editing in "visual"mode. The private box looks like this: hidden link If you do not, please ask me to enable the private box. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. Please make a backup of the site files and database before providing us access. We have strict policies regarding privacy and access to your information. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site. ![]() Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. I will be checking various settings in the backend to see if the issue can be resolved. The information you will enter is private which means only you and I can see and have access to it. You will find the needed fields for this below the comment area when you log in to leave your next reply. I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. The option you listed probably work if it's a wordpress page.īut as I'm using an Elementor template (productpage) I do not have to options you presented. Sadly, both options do not work because the page is a template in elementor and not a page in wordpress. ![]() Please let me know how that goes and if that resolves the styling issues for you. The issue should be fixed by using one of the 2 methods I presented above. ![]() Some store the styling in a custom field (the custom field usually contains the "style" or "css" or "layout" or "styling" wording) and that custom field might need to first be set to "copy" in order to have the styling being carried over to the translated page.Īfter doing this, you should first make a small change on the default language, then save the page, then go to the translation of that page and re-save it - and the CSS should be copied over. Option B - setting the custom fields to "copy"Īnother reason why this might happen is due to the way the content builder or the theme stores the styling for the content. Now switch the language at the top of the backend, go to Pages and click "Edit" on the newly duplicated page (it should open it in the same editor that you created the initial page in, so it should take the layout and instead of using any of the WPML editors, you can manually translate by using the initial editor that you used for the initial default-language page) Select the page that you want to duplicate, select the language that you want to duplicate the page in, and click duplicateĦ. Switch the language back to the original/default language, from the top of the backendĥ. Delete the current translation by switching the flag at the top, go to pages, click "delete" on the page translation, then go to trash and remove it from there, tooģ. Option A: by using the Duplication methodĢ. In that situation, there are 2 options that we have: Sometimes, with content builders, there can appear issues like this for multiple reasons (sometimes some of the modules from the visual builder that are used are not compatible with WPML yet, some updated that have been recently launched with that page builder are not still 100% compatible with WPML, etc.). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |