17

I'm using EE v2.7.0 and the syntax actually appears to be: {grid_fields} {grid_fields:relationship}{grid_fields:relationship:title}{/grid_fields:relationship} {/grid_fields}


17

The solution turns out to be fairly simple and the logic can pretty much work the same. EE relationship fields let you pull the count separately from the tag pair like this: {relationship-field:count} So, the solution is to use that in our conditional logic: {if "{relationship-field:count}" == ""} do stuff {if:else} do relationship stuff {/if}


11

In this case, I think building your own settings table is the way to go for sure. Using the settings column should really only be for very minor yes/no types of settings, not storing actual data. Especially when you get into supporting MSM, where you need settings for each site, it can get hairy fast. Plus, then your data is more easily searchable and ...


10

Long time to add to this but... {relationship-field} do relationship stuff {if relationship-field:no_results} Empty stuuf {/if} {/relationship-field}


9

Did you try this tag: {relationship_field:total_results} Example: {exp:channel:entries channel="xyz"} {relationship_field} {relationship_field:total_results} {/relationship_field} {/exp:channel:entries}


7

Looks like you were missing the relationship tag pair for your person field. Try this: <Videos> {exp:channel:entries channel="videos"} {person} <Video> <Subject>{person:title}</Subject> <Facts> {person:facts} <Fact>{person:facts:fact}</Fact> {/person:facts} ...


6

The "limit entries by status" setting for the Relationship field controls what entries are available to select in the control panel - not what entries will display in your templates. So if you have the field set to "any status", and you've selected child entries with both "open" and "featured" statuses, then your tag will need an explicit status parameter: ...


6

My decision to use playa over Ellis' new relationships, is based on: 1) When you buy an addon from a top-notch developer like Brandon Kelly, it comes with developer support, which can include timely addition of future features that you request v. paying for a support plan from Ellis if you don't have one already. 2} Playa has been vetted for many years ...


6

I believe you need to have your categories tags set within the relationship tag pair like: {exp:channel:entries channel="parent"} <h1>{title}</h1> {relationship_field} <p>{relationship_field:categories backspace="2"}{category_name}, {/relationship_field:categories}</p> {/relationship_field} {/exp:channel:entries}


5

If you do not specify orderby and sort parameters on the playa tags, the order in which they are displayed is the one in which they are displayed in the drop panes interface in the CP. Code {exp:channel:entries channel="mainchannel" limit="1"} ... entry stuff ... {exp:playa:children channel="relatedchannel" status="open"} {!-- Capture ...


5

Not with the native relationship field but you can with Playa.


5

I know you sorted this out, but for others who may wind up here looking for details: Say you have an entry with an entry_id of 10. That entry's channel has a Relationship field with a field_id of 20. While editing that entry, you choose a child entry from your Relationship field, which has an entry_id of 50. You'll end up with these values in your ...


5

The documentation is confusing on the EL site. If you prefix the single tags variables count & total_results with the custom field name, you will have access to control your markup with conditionals. This should work: {cf_article_related} {if cf_article_related:count == 1} <aside> <h2>Further Reading</h2> &...


5

Have you tried labeling the statuses without the initial caps? I believe the default categories are open and closed not Open and Closed, is it possible that that is causing the issue for you? Additionally if you are trying to show all entries except a certain one consider using not. For example I have a status like status="not closed|open|...


5

It's a pretty simple operation, since they are stored very similarly. First, backup your database. Then, run this code in a PHP-enabled template: <?php $playa = ee()->db->query("SELECT * FROM exp_playa_relationships"); foreach($playa->result_array() as $rel) { $data = array( 'parent_id' => $rel['parent_entry_id'], '...


5

Always read the manual Steven!!! http://docs.pixelandtonic.com/playa/using/converting/relationships.html


4

Playa from Pixel & Tonic has sibling relationships that might work the way you want them to.


4

From what I can gather, I would simply get the field_id from the exp_channel_fields for the relevant relationship channel field that has been created inside EE CP. I would then insert both the pieces of content (the main piece of content and the relating content) into exp_channel_data as usual, then get the entry_id's for both pieces of content. Since EE 2 ...


4

Since your project area is determined by the URL, you can just query the URL to get the entry_id of your project, and add that to a hidden field: {exp:query sql="SELECT entry_id AS project_entry_id FROM exp_channel_titles WHERE url_title = '{segment_3}' AND channel_id = 1"} <input type="hidden" name="update_project[selections][]" value="{...


4

Unless this is a really simple site I would highly recommend switching to Playa relationships - you'll have lots more flexibility as the site grows. However, if you want to stick with native relationships, try using the unique parameter offered by Stash's get_list. Something like this works, whilst having the added benefit of keeping your markup cleanly ...


4

Sean, you may need to add a status parameter to your playa tag like so: {exp:playa:parents channel="zoo_visitor" status="not closed"}. Zoo Visitor uses a custom status per member group and the playa tag will only pull in those with an Open status by default.


4

Do you mean that a single entry could have a single entry relating itself to over 2,000 other entries, or just that there are 2,000+ other entries to choose from? If the latter, the answer is Yes, Playa is quite capable of dealing with large numbers of entries. Simply set a Limit on the Playa field to something like 100 entries, and then use the Search bar ...


4

I’ve found the solution: {switch='odd|even'} needs to be namespaced so that it switches within the context of the relationship field, like so: {staff_member_groups:staff_group_members:switch='odd|even'} Otherwise, {switch='odd|even'} is going by the larger context of the entries tag that surrounds this template. For clarity, my final block of code looks ...


4

The short answer is that entries don't have URIs in EE. Content is completely separated from URL routing - it will appear wherever you decide to call it in your templates (which are essentially analogous to routing in EE). (The exception is when you set a Pages URI, or use an add-on like Structure which subverts this fundamental tenet of EE.) So, as Siebird ...


4

You need to prefix the categories loop with the related field name like this: {exp:channel:entries dynamic="no"} {parks}{parks:categories}{category_name}{/parks:categories}{/parks} {/exp:channel:entries} This is to allow you flexibility to display the parent entry's categories too, so it's quite handy.


4

Make sure that in the settings for your Relationship custom field that you have checked the box for "Include in selection Future entries?"


4

This works in my tests when accessing a child relationship: {relationship_field} <p>Child entry title: {relationship_field:title}</p> {relationship_field:grid_field} Column 1: {relationship_field:grid_field:grid_column_1} <br> Column 2: {relationship_field:grid_field:grid_column_2} <br> {!-- etc... ...


4

Try using the count and total results variables, but namespaced with the name of your relationship field: {relationship_field} {if relationship_field:count ==1} <ol> {/if} <li>{relationship_field:title}</li> {if relationship_field:count == relationship_field:total_results} </ol> {/if} {/...


3

There are a couple of ways to approach this if you are just wanting to have price you would want do something along the following (as referenced here) Most variables can also be used outside of the product form, inside a standard {exp:channel:entries} loop. For example, if your Store products custom field is named “product_details”, then the price is ...


3

I would just pass the entry_id to an embed. {exp:weblog:entries ...} {reverse_related_entries limit="1"} {embed="some/template" entry_id="{entry_id}"} {/reverse_related_entries} {/exp:weblog:entries} Embed: {exp:weblog:entries entry_id="{embed:entry_id}" ...} <h2>{title}</h2> {a_matrix_field} <p>{...


Only top voted, non community-wiki answers of a minimum length are eligible