Home›Support›English Support›[Assigned] "Custom Link" and "Post Type Archive" items in menus aren't being translated properly
[Assigned] "Custom Link" and "Post Type Archive" items in menus aren't being translated properly
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Elementor users - please update WPML to the latest version to maintain compatibility. More details here - https://wpml.org/changelog/2024/12/wpml-4-6-15-critical-update-for-elementor-sites/
Background of the issue:
I am trying to fix an issue with a few untranslated items in the footer template. The issue can be seen on this page: hidden link. I expected to see all menu items in the footer translated, except for brand names.
Symptoms:
A handful of links are not being translated properly. Specifically, 'Resources' and 'Products' within the 'Quick Links' menu are untranslated. Additionally, 'Privacy Policy', 'Sitemap', and 'Cookie Settings' links are experiencing the same issue. 'Resources' and 'Products' are 'Post Type Archive' items, while the other links are 'Custom Link' items.
Questions:
Is this a bug, or have I missed some additional configuration/setup to ensure these are translated?
The pages are translated and published. I tried the WP Menus Sync option, but that showed no changes, and syncing didn't resolve it. Actually, having read that document you sent... it now appears that running the menu sync manually will disable the automatic WP menu creation. I did NOT want to disable that, but it appears I have done so by running that manually. How do I revert this back to fully automatic so WPML may create WP menus?
I increased the memory limit (to 256 instead of 128) before doing any of that, but that seems to have made no difference.
So it doesn't appear that the manual WP Menu Sync is the solution, and it has no disabled part of my automatic translations. Where do we go from here?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Thank you for the clarification!
The automatic menu translaiton can only automatically translate menus that contain nothing else but pages or other dynamic links.
This automatic translation will not do the job if you use custom menu items or additional plugin that add further options to the menus.
The same counts for WP Menus Sync.
If you are using custom menu items you will need to translate those with WPML > String Translation or direclty inside each menu - the menus will need to be actually translated in this case.
Also, in case you use a plugins that add options to each menu, then you need to translate the menus manually and create one menu per language, while setting the options manually in each language.
---
If you are looking to revert WP Menus Sync you will need to go to Appearance > Menus, switch the language and delete any translated menu manually.
So what about the items that are "Post Type Archive" types? These are built-in (WordPress default) dynamic pages that are created for any registered post types that have "archives" enabled, so these ones should work just fine, right? It's just the custom links that require a manual "prod" via the string translation feature.
I did spend some time explicitly telling WPML to translate those custom link strings. I was able to find them when searching via the String Translation menu, and queued them all up for translation. However they still don't seem to be getting translated. They will show as "Translation in progress to [language]" in the String Translation page right after queueing them up, but if I view the "Translation Management" page and filter to in-progress items, I don't see any of those ones appearing there. In fact, I see a handful of items here that appear to be old content that's stuck. These items are all mostly translated, but they all have at least one language untranslated that's reporting "[language]: Waiting for translator" even though all of the translations are set to be automatic. Why would it be waiting for a human translator for just a random single language, while it translates all of the others just fine? It's set up to perform translations automatically so I have literally no clue why it would be holding up translations for content for random languages.
I think there might be multiple issues going on here, so if I could just hop on a quick call to walk through config settings, I think that would be beneficial to rule out any bugs. I have only used WMPL on a few sites so far so I'm still learning how to navigate these more complex issues, but it's sometimes hard to tell what is a bug vs what is officially supported for automatic translations vs what I need to do manually to accommodate the limitations.
