WPML has a major conflict with let latest version of Pro and Cornerstone

[Lobsterass]

I have the exact same issue as all the people in this thread. My English version of one of most important pages is gone. This is the 3rd major bug I’ve encountered since the update and the other 2 are not solved yet either. I can’t believe how the latest update of Pro was ever approved with all these bugs.

I have tried to edit the translation within WPML, like you wrote but Cornerstone still believes there is no English version of that page. I’m so frustrated!

I have updated the theme and I still can’t make this work. I’ve spent all day going crazy over this. PLEASE HELP!

Please DO NOT give the automated response of how to check conflicts between plugins! Please SOLVE THIS!

Grafisk design Stockholm • OM OSS • MONROE DESIGN AB

[charlie]

So for all of this release Cornerstone hasn’t been able to see the English version of that page? Is there any other pages that cornerstone can’t find that I may see? When I’m in your admin I can see the english version of that page however it’s language is not set to English. Was there any other type of upgrade in this time? We don’t really have any sort of migration running on WPML for this so I’m curious how the language could change. See note.

[Lobsterass]

Hi!

No, the existing English translations of pages were still working after the update of Pro. The issue happened when I edited the content of that page.

WHAT I DID:

1. I redid the Swedish content of that page.
2. I did what I normally do in Cornerstone, which is clicking on the English flag and then in the pop-up select “copy Swedish content to English page”. (I wanted the old ENG version of the page to be replaced by a SWE copy that I could translate manually back-end in WPML later).
3. Error message saying the English page was not created.
4. I then tried to create a completely new page OM OSS 2 just to test things out. Don’t mind that page.
5. I have then been able in Cornerstone to click on the ENG flag and copy over SWE content. But the page created is incorrectly treated by WP as a SWE page. WP calls this incorrect copy page OM OSS (Engeska).
6. I have done the ENG translations under OM OSS > edit page > translate (using WPML translation manager). The translations made don’t show up front-end because WP seems to think that there’s no ENG version of that Swedish OM OSS page.

Please see images below. I want to remove adjusted fields in the WPML editor btw. That suddenly just showed up.

SOLUTION: I’m happy if you can create a copy of the Swedish OM OSS page that shows up PUBLISHED front-end as an English version of that page. I can translate it myself again (texts are saved on my computer) if I just get the English page published. It’s OK if both SWE and ENG versions are in Swedish language temporarily. Please tell me what you did if you succeed because I really don’t want to go through this hell again.

[Lobsterass]

@charlie it’s been 3 days. Could you please login (please see secure note above) and publish an English version of the Swedish OM OSS https://monroedesign.se/om-oss/? I can’t get it to work so I see it as a conflict between Cornerstone/Pro and WPML.

Btw, I have the same issue on that page on my dev copy site http://dev.monroedesign.se/en/about-us/. I can’t edit the English translation.

[charlie]

I apologies for the slow response on this matter.

I think for that page in particular it was in a weird in between state of being translated, but not completed or it got into that state at some point. I noticed it was also in the translation queue. I saw the issue where it was creating a new page, but it was not the right translation. And I think this related because when I created a new page and duplicated content and it’s working (keeping in mind the bug where default language pages will overwrite translated pages). See secure note. I’ll try to add an error message when a page is in the queue as this was very confusing for the both of us.

For the fields, the SF ones are SystemFields. In the settings they are being translated. Was this just some debugging you were doing or did these show up in V6?

Let me know info helps and if you have any other questions. Tag me anytime in the forum.

Do you usually use the buttons on the page list? See below screenshot.

In WPML > Settings

[Lobsterass]

Hi @charlie

1. So you’re suggesting doing a workaround in which I translate the English OM OSS 2 in Cornerstone (because you believe there’s something wrong with this specific page only)?

2. Is this really how my WPML translations must be done in the future? If not, do you have a guide on how translations must be done nowadays?

3. How do I go about when I have translated this workaround page to English and want to keep my URL without a number two added? Is it going to work to change it to just OM OSS without a 2 once I have deleted the original OM OSS and emptied the trash?

4. How do I translate the SEO fields to English back-end with this Cornerstone-translated page?

5. The System Fields were suddenly just there without me touching anything. I haven’t dared to unclick any of those in settings because I’m afraid of deleting important translations somewhere. Which ones should I select “to not translate”?

6. No, that WPML button is nothing I’m used to. I see it as a Pro/WPML bug(?) that appeared after the Pro update.

It would be much better if you could just create an English page for the original Swedish OM OSS without a 2 in the URL. Is that not possible because of some Pro bug?

[charlie]

1-4
If you’re creating from directly in the dashboard that’s fine, most topics have been around the translations inside cornerstone so that’s where my head was at. If you’re doing that i think the problem might be that you need either accept the new translation for english, or change your WPML settings for translations (IE set all translations as accepted). See secure note I would try the former first.

5. I would leave them alone then and I’ve never seen them. I’ll take a look at the WPML docs for that one.

6. Okay and this only showed up after you saved the original page?

We can remove the 2 if we want to go this route, it’s just a draft to get you some information and I think if we can get your changes through the translation queue you’ll be fine.

[Lobsterass]

No, you’re missing my point. I’ve TRIED to save and publish the WPML editor’s English translations many times. This is perhaps the 20th site I translate with WPML so I’m not completely new at this. Please do whatever you need to do to publish this English version of that page. I CAN’T DO IT. I click save and publish and NOTHING HAPPENS. And please tell me what you did if you succeed.

5. I would leave them alone then and I’ve never seen them. I’ll take a look at the WPML docs for that one.
Well, are the not translated system fields why this page doesn’t get published?

6. Okay and this only showed up after you saved the original page?
Yes. I have no clue why I get this extremely irritating cog symbol there now. Nothing works the way it normally does!

[charlie]

Okay now I’m on the same page. Very new to WPML and my knowledge is primarily just around how we integrate with it. Are there any other sites you have that have this issue?

5. Possibly. I would start here and finish the fields and remove any fields you don’t need from that in WPML Settings. The other pages didn’t have these values though, including my test page. Do you assign those via WPML?
6. Okay, understood.

Another solution we can try if 5 didn’t work and WPML sent me this when I was going through our integration. It recommends making a backup before trying this and I would probably run this in a staging server. In the trouble shooting page there is a number of actions. I’d start with the WPML Cache one, the syncronize ones, Ghost entries, and the Element Type one. It seems like a possible job syncing issue or #5. I’d also contact WPML and see if they have insight. They are looking at our integration this week so if they find anything I’ll be sure to swing it your way.

See secure note for URL. Thank you for your patience

[charlie]

How are we doing here?

[Lobsterass]

Hi!

Thanx for not giving up on my site <3. I did start a support thread at WPML.org but they haven’t given me anything new yet. However, I have done a successful workaround for this page specifically. I did what you did and created a separate cornerstone English page, About us.

I changed the WPML settings to “advanced editor” for all new pages and I tried to make a new SV test page and I translated it with the advanced editor to EN. That worked exactly how it’s supposed to work, so I’ll just have to live with that the OM OSS/ABOUT US page has a different WPML setting compared to all other pages. At least it works.

So, in other words, I still don’t understand why this specific page can’t be translated with the classic WPML editor but I have worked around it so the problem is finally solved!

Thank you for doing your best to help me out. <3

[charlie]

Music to my ears that at least you’ve got something working. Let us know if there’s anything we can do to have a smoother WPML integration as well. The classic editor part clears some things up with me as the other UIs I were seeing for WPML were much different then that site. Always happy to help let us know if you have any other questions!