Hello,
Since updating X there is a major problem with the WPML-plugin. Translating the original page with content is not possible anymore (Cornerstone is not working). This problem was already in the update before 7.01 but is not not resolved yet.
also the paralax image is not working anymore.
Can you help to solve this?
Hi lumijans,
When you described in your message that “Cornerstone is not working” do you mean it’s not loading when trying to translate the page? If so, does it not load at all on whatever language or just the secondary language?
Also, When updating to X 7.0.1 did you also update Cornerstone to 4.0.1? If not, try updating Cornerstone as well and see if that solves the problem.
Can you clarify what problem you said was already there before the update to 7.0.1?
Regarding the parallax issue, I think it would help if you can send us a link to your website, specifically the page that has a non-working parallax.
Thanks.
Hello,
If the original page (in Dutch) is duplicated in Wplm cornerstone is not loading, there are just plain code in the box and when seeing the result see page (English) is empty (this was already a problem before updating to 7.0.1, so in the earlier version of X). Cornerstone is indeed updated to 4.0.1. It seems that there is nothing wrong in WPML itself.
The picture https://huisartsrivierenbuurt.nl/ used to be parallax (also on https://huisartsrivierenbuurt.nl/patienten-informatie/)
regards, Astrid
Hi @lumijans,
There is an issue with parallax and will be fixed in next release, but it’s not related to WPML at all.
And when translating a page, please do it within the builder by clicking the flag icons. Please check this related thread https://theme.co/apex/forum/t/translating-website-pro-with-wpml/41383/7 as it sounds you were not using the builder when you translated it, perhaps advanced string translations? If that’s a yes then you probably upgraded from the old version where string translation is not an issue yet (pre-v2). I’m afraid with the latest versions, you’ll have to use the correct translation (in-builder translation) which also means you’ll have to re-do the translations.
And this https://theme.co/apex/forum/t/wpml-issue/48740/2 for proper setting.
Thanks!
The parallax works again, thanks for solving. But some lay-out are messed up now.
Concerning WPML, also translated pages which were working fine are not showing up anymore, i loaded the last versions of X and Cornerstone.
I also asked WPML-support desk for advice but the problem seems to come from the theme.
Is there improvement expected?
Hi.
Sure we can take a look at it on your dashboard. Can you provide us with your login details on a Secure Note?
Thanks.
Hey @lumijans,
This looks like an issue with caching. Even though I deactivated W3 Total Cache though, the translated page won’t update.
Would you mind completely uninstalling W3 Total Cache and check if the issue persists?
If it does, it’s best that you copy your site to a staging server so we could troubleshoot without the risk of breaking something in your site.
Please then give us Staging WordPess Admin and Staging FTP access.
Thanks.
Hello @lumijans,
Cornerstone 4.0.2 is now available in automatic updates! This release contains fixes for several issues, like you have mentioned above, so be sure to check out the changelog (https://theme.co/changelog/). Please do update to the latest version.
Please also make sure that your WPML plugin is up to date.
After doing the updates, always remember to clear all caches when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.
Please let us know how it goes.
Hello,
Theme and plug-ins are all up to date, also cache cleared (In the main website). But the translated pages are still not matching. Posts in blog (news) are doing wel. What’s wrong?
Your colleague Christian asked me to set up a staging site (also last versions), which i did, see last secure note.
Hey @lumijans,
Your method of creating a staging site seems incorrect, so Cornerstone doesn’t load there. Would you mind trying other ways of copying your site to a staging server?
Please also give us FTP access to both the live site and the staging site. If you’re not familiar with FTP, please ask your web host to give you the details.
Thanks.
Hello,
I sent the log-in info of he staging site in an secure note (second one, first was incomplete).
Hope you can help to find out what went wrong in the last updates. (WPML-cornerstone)
thx, Astrid
Hi Astrid,
Thank you for the information. I checked the staging website and used the recommended method, which is to create the page with Cornerstone and use the Flag icon at the bottom right section of the Cornerstone while editing the page to copy the existing page for the second language and it worked correctly.
Please kindly check the secure note for the links.
I am afraid that you might need to change the way you translated the previous pages. I suggest that you install the Duplicate Post plugin and duplicate the pages in question. Duplication will remove the WPML translation link. Now go to the duplicated page using the Cornerstone and use the flag icon there to copy the page and do the translation inside the Cornerstone itself.
Thank you.
Hello Chistopher,
Thanks for testing and giving the explanation. Unfortunately my client needs to set up everything again. I also asked the developer of the WPML-plugin for advice. I’m waiting for this answer.
Since there will be other users with the same problems.
rerards, Astrid
Hey Astrid,
I’d just like to add that in pages Christopher created, if you’re going to use Classic Elements like the Classic Headline, the issue will still persist.
Your environment is among the environments where this issue happens. In my test site, both Classic and V2 elements work. Also, caching is no longer a factor in your staging.
Regretfully, you’d need to convert the text elements in your pages to V2 Elements.
We’re sorry for the inconvenience but this change was not taken into account because WPML just recently released their new version also and it comes with some changes.
Thank you for understanding.
Hello Christian,
I set up a new page (name of the page = voorbeeld) in Cornerstone (no container/header/footer), I translated it the way you recommand (name = example) in english.
I also put in the menu and synchronised the menu. But it still not working. All the pages are build in Cornerstone with no container. Can you have a look in the staging site?
Hello @lumijans,
When you create a page in Cornerstone and would like to translate it, do the translation within Cornerstone. You can switched back and forth using the translation flags at the lower right corner of the preview editor.
After creating the Dutch page within Cornerstone, click the British flag to start translating the page into English. You must select copy from existing page so that you will have the same structure for you to start translating the texts.
(All of the images were tested and taken from your staging site.)
Hope this helps.
Thank you for the explanation. I followed all the steps. Strange enough the translated page is not loading when i click on the english flag.
Step 1
I copied the existing homepage and called it welkomthuis
step2
I opened it in cornerstone and clicked the english flag in the bottom right, i changed the header in welcomehome and loaded the english version of the globol blocks content (further down in the page). Ans saved it.
step 3
I added the pages to the menu in english (changed the menu item in welcomehome) and dutch and synchronised the menus
When I load the english version it still shows the dutch text, but it does show the english global block (ut if i open the english page direct in cornerstone it seems ok)
nb these pages are all set up in 'no container/header/footer
I also cleared caches
What’s wrong?
Hello @lumijans,
It appears that there is a conflict with WPML and the classic elements used in the page. This has been confirmed by one of our developers already. They also provided this workaround:
1) Disable all cache feature and plugin (I didn't get immediate results due to this), not permanent but while you're fixing it then it should be inactive
2) Downgrade to these versions
WPML Multilingual CMS - 4.2.6
WPML String Translation - 2.10.4
WPML Translation Management - 2.8.5
3) If you wish to use Yoast SEO plugin then please downgrade your WPML to these, else, you can still use the above versions.
WPML Multilingual CMS - 4.0.6
WPML String Translation - 2.8.6
WPML Translation Management - 2.6.7
If downgrading is not an option for you, I would recommend that you recreate your homepage using the new section, row, column, and other elements and then you do the translation.
Hope this explains your issue briefly.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.