This thread is resolved. Here is a description of the problem and solution.
Problem:
The client couldn't see the main menu on secondary languages
Solution:
The client recently started to translate his site and pages that were included in this menu weren't translated yet!
- Translate the pages
- Go to "WPML > WP Menus Sync" to create menu translation and synchronize menus
- If you have any custom links in your menu, then go to "WPML > String translation" to translate them
I am now working out the steps we will need to take in order to manually translate pages one at a time, using the dev site as a staging area. However, my first issue is that on the dev site you'll now see that the menu is not the same across the different languages (I've only "translated" the homepage for now as a test) and in trying to synchronise the menu across in the back end "appearances > menus" area, it's somehow actually lost the menu on the main original language entirely, even though it's still present on the front end. The only menus now available to choose from are three duplicated US versions that only have two menu items (I have no idea why the US version only has these random entries!). I've provided some screenshots for you to look at for these menu issues.
I have also gone through the process of translating the Divi footer as per your previous instructions, but for some reason on the translated page its severely misaligned.
I feel like I'm missing something obvious! Any help appreciated
I went to "WPML > WP Menus Sync" and saw that none of your pages are translated. That's why WPML couldn't synchronize the pages with their translations.
I have attached a screenshot and will explain each color code
- I duplicated the page "Who" in Australian to get an example
- The green color means that the element will be added: we have the page "Who" in Australian (as mentioned above) + Travel alerts and webinars which are custom links that you will need to translated manually in "WPML > String translation".
- That's why the label is in red and the URLs is in orange (string and url needs to be translated)
At the bottom of the screenshot, you have a link to go directly to String translation and translate them.
WPML is not able to translate custom links because as the name suggest they are custom and can be anything (external pages, links to documents ...)
Now, if you look at the homepage for Australia you'll see those 3 elements ("Who" being translated + 2 custom links not translated yet).
PS: note that the title/label is "Who" not "WHO". You have all your titles uppercased in the original menu by customizing the label.
- You can go to "Appearance > Menus" select the "Main Menu" and edit the Australian translation to do the same operation and get the same result.
Another way to do it, would be to create a CSS rule that uppercase your menu items automatically. It should be something like this:
Last note, you have duplicated your homepage in the other languages like we talked about previously. Now don't forget to click the buton "Translate independently" if you want to make changes on those secondary languages. I know they are all based on English but you might need to make few adjustments (color vs colour or different currencies, contact info etc...). If you don't click "Translate independently", the translation will remain as a duplicate and every time you will save your original language it will overwrite any changes you made on the secondary language.
Thanks for the support Nico. I have started to slowly add the plugin back to the live site. One thing I still can't figure out, which is true on both the dev and live site, is that in duplicating the homepage and then the custom Divi library footer, one - the AU version is displaying perfectly, the other, the US version seems to be missing some styling code or other as its gotten all squashed up plus other style problems - font sizes, colours etc. Any ideas what has happened here? I've made no changes to either translated page at all yet
I just visited hidden link and the footer seems to be identical to the original one. Did you solve the issue by yourself? Maybe it was only a temporary caching issue? Purging the cache may have solved this.
If you need more assistance let me know, and give me all the details to reproduce/find the issue. Else could you please mark this ticket as solved.
Hi Nico - no the AU version has always been fine, it's the US version that is the issue which is even stranger since they are both identical copies of the original version, and I've not made any changes to either of them.
Weirdly, the footer seems to have righted itself. So strange. I'll work through your comments as best I can and hopefully will be fine now. Just trying to make sure we get all the setting sorted in the best possible way to make it as smooth as possible
