Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

Tagged: 

This topic contains 13 replies, has 0 voices.

Last updated by Dražen 42 minutes ago.

Assisted by: Dražen.

Author Posts
January 7, 2025 at 9:38 am #16568685

axelT-5

Page list block not working on translated page.

January 7, 2025 at 9:49 am #16568723

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

I am trying to reproduce the issue from scratch with the page list in content, but I was not able as it seems to work fine for me.

What I have done:

- Created 2 new pages, set them as parent > child, translated. Made sure they are like that in both languages
- Edited page templates and added page list block, translated the template

it seems to work fine: hidden link

Can you please check it out on the next test site and let me know if I am missing any steps here?

- hidden link

Thanks,
Drazen

January 7, 2025 at 12:03 pm #16569375

axelT-5

Hello,

I added a pagelist in content and in navigation.

- you see that the pagelist in content vanishes
- in navigation the bug is now much stranger: it looks like it opens a submenu into the page list, but it is not the current translated navigation, but a previous one.

So there is another bug mixing revisions of translations that currently hides the pagelist in navigation bug. But you can still see the pagelist-in-content bug which is very likely the same bug. If the pagelist-in-content is fixed I strongly assume that navigation menus will work correctly.

Screenshot 2025-01-07 135957.png
Screenshot 2025-01-07 135854.png
January 7, 2025 at 12:46 pm #16569514

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

thanks for getting back, as I advised let's please keep this ticket topic on the content page list issue, if you think they are the same we can just continue on this or you can get back to me in another ticket, to keep things and conversations clean and simple.

So, as I said, I tried to reproduce the issue, but following the shared steps in my last reply I do not get the same issue, can you please share a full step-by-step guide on how can I reproduce the same issue with the page list block in the content part? If it is easier you can record a video of your steps from scratch, using the LOOM tool.

Thanks,
Drazen

January 8, 2025 at 1:02 pm #16573521

axelT-5

Hello,

1. install WPML
2. create a hierarchy of pages (a parent and a child are enough)
3. add the pagelist block to a third page (sample, home etc.) rooting at the parent page of the created hierarchy
4. have it translated
5. inspect the translated page to see the pagelist is not translated, but empty

You have two labs where this can be seen. 🙂

January 8, 2025 at 1:31 pm #16573658

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

Thank you very much, that makes it a lot clearer now.

I have escalated this to our 2nd tier to further check and escalate to our developers for a permanent fix. In the meantime, as a quick workaround, you can edit 2nd language page manually and select the correct translated parent page and it should work fine.

Regards,
Drazen

January 8, 2025 at 1:48 pm #16573770

axelT-5

Hello,

there is no workaround applicable - the real hierarchy is dynamic (as intended for pagelists) and contains several dozens of pages.

As this breaks every hierarchically based setup (like every mega menu etc.) out there I think this blocks many customers from adoption. Please escalate accordingly to engineering right away. For us it is a breaking point, and we would have to look for a different solution if this is not solved asap.

January 8, 2025 at 1:58 pm #16573811

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

thanks for reply.

Sure I will note this and I have escalated it, as mentioned, and will update you here when I have some news or a workaround on this. Note it may take a day or two before I have any feedback.

Regards,
Drazen

January 8, 2025 at 1:59 pm #16573812

axelT-5

Also note:
The issue is not new, just not recognized as such.

https://wpml.org/forums/topic/translating-a-template-part-containing-auto-generated-navigation-from-the-navigation-block/
https://wpml.org/forums/topic/newly-created-pages-are-not-visible-in-the-page-list/
https://wpml.org/forums/topic/translating-a-template-part-containing-auto-generated-navigation-from-the-navigation-block/

January 8, 2025 at 2:53 pm #16574001

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

our 2nd tier checked and provided a solution. Please go to WPML > Settings > Custom XML Configuration and add the next code:

<wpml-config>
  <gutenberg-blocks>
    <gutenberg-block type="core/page-list" translate="0">
      <key name="parentPageID" type="post-ids" sub-type="page">
      </key>
    </gutenberg-block>
  </gutenberg-blocks>
</wpml-config>

- Save.
- Go to your default language page and make a small change, save, and re-translate. It should work fine and show the correct pages in the page list block in the translated page.

We will also be including this code from our side, so it is permanently solved.

Regards,
Drazen

January 8, 2025 at 4:07 pm #16574435

axelT-5

Thanks, that fixes the content page list.

Unfortunately the navigation issue still seems to be a problem. 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).

You will see the page list populate the menu in the original language, but the translated will be empty.

If you create an explicit menu item and then inject the page list as a submenu then this seems to have started to work. So the submenuing seems to be OK (not fully checked as the remaining issue breaks the user workflow)

Quite strange that the fix does not fix everything. But maybe engineering will have a smallish add to fix this as well.

Thanks for the fast turnaround with engineering!

January 9, 2025 at 7:30 am #16576194

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

Thanks for the feedback, Let's continue on this in another ticket, I need to keep it separated as this is another block, and not the same case and might need another escalation.

If the fix for the current case helps, I think it is safe to close this one ticket now.

Regards,
Drazen

January 9, 2025 at 6:20 pm #16579357

axelT-5

Hello,

personally I do not think it is wise to split up the ticket for a third time, we already saw that there is confusion about what ticket serves what already - especially when the subjects remain the same. Engineering will have to collect the fragments of information from different places.

Anyway if you feel a separate ticket will serve this purpose be my guest and create a new one or use the other half of this ticket. AFAIAC it still runs under "Page list block is empty in translation".

January 10, 2025 at 7:53 am #16580452

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+01:00)

Hello,

I was talking about the original ticket with the navigation issue. This kind of putting all in one ticket causes problems with communication and the clarity of the topic and issues, as you can see from our conversation.

1) So please keep this ticket about page list block inside content, for which we have provided solution and this ticket can be closed now.

2) The issue for navigation block/templates is checked in this ticket: https://wpml.org/forums/topic/page-lists-are-empty-in-translation/ and is waiting for your feedback and let's continue there on that topic.

Thanks,
Drazen