Andy Babic

@robnardo I think using flat menus is a common way around this problem, although it's not great for developers to have to assemble the correct handles every time. It would...

I think wagtail is close to figuring out what it wants to do natively for translations/localisation, so it's probably worth holding out for that.

Hey @calbear47. That isn't really something wagtailmenus caters for out-of-the-box. I think main menus could work, but you'd need a custom menu model (with relationships/unique criteria overridden, and certain methods...

@calbear47 Whatever native solution we come up with for `wagtailmenus` will almost certainly now be inspired by the native localisation models/features coming in [Wagtail 2.11](https://docs.wagtail.io/en/latest/releases/2.11.html)

Thanks for sharing @perepicornell! That's superb :)

My only concern there would what happens when you edit and resave the menu. Don't the stored pk values change depending on what language is active? Does that have any...

Overriding [`get_pages_for_display()`](https://github.com/rkhleics/wagtailmenus/blob/master/wagtailmenus/models/menus.py#L981) might be a safer bet, but would take a bit more custom code.

Hey @perepicornell. I'm sure this will be really helpful for others... thanks for doing such a great job of explaining the problem and your solution.

@Redjam I would have a scan at the code suggestions further up, specifically [this one](https://github.com/jazzband/wagtailmenus/issues/242#issuecomment-795138779). Wagtailmenus does some pre-fetching of page data to use for rendering, so ideally you need...

Hi @rcmurphy. Apologies for the delay in getting to this. Your help is much appreciated - I am just spread very thinly! Am totally happy with this change, but would...