Plugin: Tied Entries

Yes this works, but doesn’t work in my situation where that particular field will always have content.

I have one weblog named amenities, and another weblog named promo.

I’m using reverse related entries to display all promo entries when viewing an amenities entry. My issue is that I have 2 custom Playa fields. One Playa field designates which amenities page it appears on and the Second Playa field designates the page the Promo links to.

My problem is that because I need to use reverse related entries, I have no way of specifying which Playa field to use, so my promo entries are appearing on the wrong page because it’s grabbing my Second Playa field that designates the promo link. So my promo ad is appearing on the same page it links to.

I hope this makes sense.

Bransin, just to clarify, when you say pages, do you mean entries? If it’s pages, any way to filter the content by using the segments in the URL? If it’s entries (hard trying to imagine someone else’s setup without seeing it), can’t the two types of content be filtered by their being in different weblogs?

When I say pages, sorry I forgot to mention that I’m using Structure. So an entry within a specific weblog like amenities, will create a static page. Works just like the pages module.

I thought this plugin would accomplish what I need to accomplish with reverse related entries. It would be great to select which relationship field to filter by when using reverse related entries. Right now I have a weblog that has 2 relationship fields that perform different tasks but relate to the same weblog. How do I tell ExpressionEngine to find all reverse related entries by custom field?

Bransin, this now works. As of Tied Entries v1.3 you can select which relationship field to filter by when using reverse related entries. Right now it’s limited to either all fields or just one field.

Hi Adam,

Do you think your plugin might be able to accomplish this in a more efficient way -

http://ellislab.com/forums/viewthread/156766/#758297

?

Hi Adam, Do you think your plugin might be able to accomplish this in a more efficient way - http://ellislab.com/forums/viewthread/156766/#758297 ?

Yes, it’s useful for that sort of thing. But it doesn’t yet have recursion (another feature request), which would let you set the folder level for each doc at any arbitrarily deep level and the plugin would follow.

Sorry I actually meant the concept from my own comment in that thread rather than the original poster’s issue (which I shamelessly hijacked!).

example: http://www.jamessmith.co.uk/JS/touchpoints

Sorry I actually meant the concept from my own comment in that thread rather than the original poster’s issue (which I shamelessly hijacked!). example: http://www.jamessmith.co.uk/JS/touchpoints

Without climbing inside and understanding fully, it looks like the new feature of the plugin may help with what you wrote as follows:

The hardest part is distinguishing between two relationship fields, since they are all bundled together in the relationships table it’s hard to get EE to recognise which relationship comes from which custom field.