Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello there!
I'll continue checking out this issue and I'll follow up when you have an answer here.
For now, I just want to tell you that while you should be able to see the fallback taxonomy elements in the archive ("blog" for example), you can't use it at all while editing the page because in there you need to have content so you can select it. you can't select content from the original language (no matter the type of taxonomy) on a translated language since the fallback feature is a front-end feature only.
Also know that if you have filters in place, the elements that are using the fallback feature will not show either, because when you use filters, one of the filters is the language itself; the content won't be present in the translated language, so of course it won't appear.
Let me know how ti goes so we can understand how to continue.
Thank you very much for the information. Your remark that I can’t select content from the original language on a translated language since the fallback feature is a front-end feature only appears to answer my question, as this is the very thing I was trying to achieve: being able to select fallback taxonomies while editing the page.
There is however one other thing that I noticed: In the sandbox page that Bruno provided to me (hidden link), I was able to access fallback taxonomies in the Post edit site as long as I used the Gutenberg editor. When I installed and activated the Classic Editor, the problem of not being able to access the fallback taxonomies reappeared. So maybe there’s a compatibility issue with the Classic Editor…?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
As I thought, the possible bug is in the fact that you can see the fallback category in Gutenberg.
I can theorize it happens because most of the things are handled with REST and AJAX in Gutenberg so there might be something that is actually loading the content incorrectly.
I'm escalating the case to our developers to see if we can clarify this correctly and try to fix the bug if there's one, and of course, we will be able to let you know if there's a way to achieve what you want (although i think it won't be possible).