Background of the issue:
I am trying to use page lists in content and navigation menus, either directly in footers or in submenus in the header. All involved pages have been translated. The issue can be seen at: hidden link. I expected to see the translated content of hidden link, including a menu with a submenu and a page list of the 'parent' page with one 'child'.
Symptoms:
The translated page lists return empty. In contents, this is just an empty block, and in navigation menus, the menus are missing. Instead of the expected submenu and page list, I got no submenu and no page list, with the page list framed by two paragraphs.
Questions:
Why are the translated page lists empty?
How can I fix the missing menus in the translated navigation?
thanks for the patience, I will take over and help further.
Please note we 2 issues here, so we might need to split tickets.
1) Menu items - Can you check now? I see pages were not added as parent/child from Pages > All, so I have added them and re-translated your templates from WPML > Translation management, and it seems to work fine.
2) I will open a new ticket for this, as this seems to be a bug with the Page list block inside a content template, I will update further on this topic in the new ticket:
I still think these are the same issue - the translated pagelist returns an empty array which any block making use of them, be it in content, header, footer, navigation etc. will base its rendering on this empty array.
Fixing the bug in the most simple case, e.g. just pasting a pagelist into content, could automatically fix all other use cases.
sure, but until I can confirm and check further, please let's keep it separate, as it looks to me like they can be different.
Can you please revert back to my last reply, check the issue with navigation, and let me know if something is wrong, since as I said it works fine now after re-translating the pages / template.
I already wrote about the navigation - as you see the original and translated one have very different structure with the latter even having one root menu point extra. This seems to be a different bug where the translation is an old one - the menu structure I added was not really translated, otherwise the deleted menu (Sample) would not exit in the translation.
In short - yes, there are two distinct bugs, one with the empty-translated-pagelist and one with old content not being replace with new translations.
I understand that you wrote before, but let's try to make it more clear here for the navigation issue so I can confirm and check and escalate further.
I am checking the navigation issue on: hidden link, and I see the same structure in both languages and no issue, but maybe I am misunderstanding something here. Image attached.
Can you please recheck and share with me what is different, exact example, or try to reproduce it again on that website and share with me step by step guide so I can check and confirm it also?
I am not as I do not even yet understand this issue with navigation or what happens. I have taken this ticket not sure if it was like this or if someone changed this later.
That is why I am trying to share with you that I do not understand or see the issue and need further information from your side.
If you can please reproduce it and share step by step guide with me so I can further help you on this.
"Easiest way to verify is very simple:
1. create a blank navigation block (anywhere even in content, so no need to use the side editor on templates)
2. just add one page list (the default "all pages" will do)."
our 2nd tier checked further and it seems it is related to the navigation template after all, if you check the code of blocks there is a wp_navigation cpt that is with ID 10 and translated to ID 41
It has a different structure than the original. If you re-translate them and make them the same it works fine.
