There are several portions of my site that rely upon self referencing relationships, that are (or rather were) gathered through the reverse_related_entries tag pair.
I have a channel for press releases. One of the attributes of that channel is a relationship called translations, which points to its own channel, press releases.
When a PR is entered it is usually in English only. Often though, there will be other translations of that same PR, so when they go into the system, the relationship attribute is used to “point” to the origin press release. Then in a template where the origin press release is being shown, I used a reverse_related_entries pair to loop through and show me all the other language press releases that pointed to “this” one.
Well, I’ve just upgraded to 2.6.x from 2.5.x and all my templates which used relationships in any way are now broken, because there is no backwards compatibility here. Sucks big time, but what can ya do…
The problem is, as sexy as the re-designed relationship functionality looks to be at first glance, I cannot for the life of me figure out how to reproduce what I was doing before. Everything seems to rely on being inside of a exp:channel:entries call where the channel in question has clear relationships downward to children. It’s a bit confusing.
Given the scenario I’ve described above, is there anybody alive who can tell me how to duplicate the reverse_related_entries functionality in the new format?
I’m truly desperate here and any help is hugely appreciated.