rhisflow

Hi Marc, thanks so much!

So it turns out the cause for this error notification was that some posts contained a pattern / reusable block, which no longer existed.

So when editing those posts, the block showed “this block has been deleted or is unavailable”.

Somehow, this caused your plugin to trip over it.

Just letting you know in case that helps or if that is expected behavior.

Best wishes!

Thanks for your super quick reply, Marc!

Great tip, thank you – to deactivate such notices, is this a setting within wordpress or on the server? If you could give me a hint as to where to deactivate this, I’d appreciate it!

I’m looking into the details as to what’s different and will get back to you as soon as I found something!

Also, I’ve already noticed that it’s unrelated to the theme update, so it must be something about the posts – I’ll investigate!

Thanks for letting me know that multi-lingual support will come to the WordPress Core at some point, that’s great news!

Also, thanks for clarifying that full multilingual support is currently not possible with core features only.

Our of curiosity: so for your bilingual site, did you accept the current core limitations then, i.e. having the pages I mentioned (author, search, archives,etc) not be bilingual?

Hi @zoonini ,

I think you just confused @akopacsi and his original post with my recent post where I mentioned 404, search pages, archives, etc ??

Hi @tracyrosen ,

I think you’re still talking about your Translatepress approach, which I had already acknowledged and pointed out its limitations, which is why it’s not an option for me.

My quote you were using in your reply referred specifically to @zoonini ‘s previous suggestion to assign specific headers to different page templates.

In that scenario, your statement:

The header is translated across the board…

is definitively not true.

Since in her suggested approach one menu navigation language is assigned to one header template, that, and only that, menu will be shown whenever its template is used.

Example: the French header menu will always be shown on French page templates.

And since templates cannot be changed (to my knowledge anyway) for the pages I had mentioned, only one header menu will ever be shown on those pages, making it somewhat unsuitable for a fully multilingual site.

So let’s maybe wait to hear back from @zoonini first before we confuse different things here :).

• This reply was modified 1 year, 9 months ago by rhisflow.

Thanks for following up on this, @zoonini ??

Your suggested process only works partially, at least as far as I know and ever got when trying to implement it.

The main problem I find is that it’s not possible to apply custom templates to all pages, only to some (and to all posts).

Specifically, it’s not possible to apply a different template to the following pages:

• 404
• search
• author
• archive

Maybe I’m even missing some others, but with those, it doesn’t seem to be possible to assign a different template.

So as far as I can see it, the same should be true on your bilingual website, it should have the same problems:

Whenever a French reader enters a search term, looks at an author’s page, browses categories or runs into a 404 page, they’ll be looking at a foreign language header all of a sudden.

Since this makes a website seem broken and unprofessional in my opinion, I’d rather have a complete solution instead of one which only works on some parts of the website.

But maybe (hopefully) I just don’t know how to do it and you can tell me ?? !

Thanks!

• This reply was modified 1 year, 9 months ago by rhisflow.

Hi @zoonini ??

Right. You’d have to assign the right template to each page or post manually, which you can do in the editor

Yes, I understand and am using this approach to assign different templates to different posts or pages.

However, this template approach does not work for the issue I was describing, which is concerning the header navigation menu.

Since that same menu is on all pages and posts (or rather, the same header menu is used in all page and post templates), it is irrelevant which templates the posts or pages use.

Thanks for mentioning the block visibility plugin, I had actually found that earlier along with at least one other “conditional blocks” plugin.

However, while they would be able to solve this problem, those plugins all require an ongoing paid subscription to do so, because the required condition is “URL path”, which is not available in their free versions.

Hi @thelmachido , thanks for your suggestion!

However, I don’t think that actually works, at least I never got it working, which is why I was looking for a solution.

With the new FSE, it seems you can only select one nav menu per header per template, and even if you create a different header in a different template, there’s no way you can implement a conditional logic to determine when the other template should be used (which would require a logic based on the URL path like “if it contains “/en/”, then use this template, etc).

@tracyrosen , I also went down that path with Translatepress to try it and while it can indeed work if you only need to literally translate a single navigation menu, it does not work if you need different menu items in the other languages, which is what I needed.

In other words, you can’t add or remove menu items that way for other languages.

@domainsupport , thanks so much for your recommendation and pointing me in the right direction ?? !

I ended up using the Max Mega Menu and after a few hours of setting everything up, it works quite nicely, so I consider this a good solution, thank you ?? !

• This reply was modified 1 year, 9 months ago by rhisflow.

Thanks for replying so quickly, guys, much appreciated!

@akopacsi : yes, I was actually also considering switching back to 2021.

However, this would cause other problems and lots of work as some functionality currently provided by the full site editing would be lost (like different post templates with specific layout and content blocks).

@domainsupport using the legacy menu sounds like an interesting option to pursue!

Would you be able to name a few of the plugins you know that might do the job?

You said there were plenty, but when looking for “legacy menu plugin”, I’m not actually finding anything?

Thanks a lot!

Hi @akopacsi and @greentreefrog ,

I was wondering if you’ve found a solution for this?

I am using the twenty twenty-two theme and trying to display a different header (including a navigation menu in a different language), based on the URL path.

This is because on my site, all languages are distinguishable by subdirectories, like so:

https://www.domain.com/de/postname
https://www.domain.com/es/postname

So I want to display a site header with a German nav menu if the URL contains “/de/”

I was not able to find any free solutions for this, could you maybe point me in the right direction how to solve this?

Thank you!

Hi Stéphane,

thanks for your quick reply!

Ok great, thank you for working on a solution, I’m looking forward to it ?? !

Please reply here in this thread so that I get an e-mail notification.

Best wishes!

Just like @mahype , @mpknol , @rtm-communications and @derrida have been pointing out in this thread:

The free version of Polylang has become completely useless and pointless since the introduction of Full Site Editing themes.

Not sure if the plugin team honestly expects website visitors to put up with menus and navigations in foreign languages??

What’s even more discouraging and disappointing is that the Polylang team is completely unresponsive regarding this issue – or, more likely, they simply don’t care about their free users.

Case in point: I’ve pointed out almost 6 months ago already in this thread here that changing to a WordPress theme with FSE basically breaks the site if it had the free Polylang version installed, because the translation of menu navigation worked fine on the free version of older themes (pre FSE), but it no longer works with FSE themes.

I guess nobody in this support forum will be surprised that I never received any reply to the concerns and questions I raised, at least not beyond their standard canned “it’s a pro feature” response.

Too bad that Polylang has dropped the ball on this, along with their customer service.

I’ll be moving to the competition, along with many other disgruntled users I’m sure.

Hi @chouby ,

thanks for your answer.

That’s a real bummer as it effectively paywalls the same functionality depending on the Theme we use.

In other words, menus in the header and footer have been perfectly translatable in the free version.

By simply updating one’s Theme, this functionality is suddenly lost – was that a deliberate business decision you made, or accidental?

Is there any chance you’d reconsider?

After all, it’s not anything new your free users would get, but simply maintaining the free functionality when changing themes.

I appreciate your support!

Hi guys,

does anyone know how to solve the issue?

Thank you!

Hi @zoonini ,

thanks for your detailed response.

I’ve just tried it again and this error no longer occurs!

Seems like since the latest update (6.0.1) it has been solved ??

Best wishes
Florian