Relation Reverse field problem after upgrade

Hello

The pages in the example that you sent me are 2 different items
please look at the IDs

item-id: 8515
item-id: 257

Yes they are translations.  So it has nothing to do with the category view.  It's the language that is playing me tricks.  The filed was set to non-translatable so I guess that it would only apear in the relation reverse field in the language it was last saved.  Does that make sense?

Anyway, I've unchecked it, re-entered the data for the relation field and it's now showinng as it should in reverse relation filed.

Maybe the non-translatable option should be removed from the relation field?  Or can that be fixed so it gets the language association also?

Thanks for your help.

Hello

non "untranslatable" is for fields that store a field in DB
and works like this:
- when you click save on the item, then all other associated items will be saved with same value

Relation-reverse does not store values values in DB
so that setting has no-effect at all
i think we need a flag in the XML file of field to mark if a property such as "untranslatable"  is applicable / meaningful and disable it otherwise