- Download
- Rename folder to
nsm_entry_select - Copy to your
/system/expressionengine/thrid_party/directory - Install fieldtype
- Create a new field.
Let's say your custom field name is my_entry_relationship_field. In your templates you have one tag: {my_entry_relationship_field}
By default this tag returns a pipe delimited string of the related entry ids - great to use as tag parameters.
Example: Rendering related entries using the {exp:channel:entries} tag and a collection embed template.
This technique requires a parent templates and a "collection" embed.
The parent template: site/index:
{!-- The entry with NSM Entry Select custom field value --}
{exp:channel:entries weblog="my_weblog" limit="1"}
<h1>Title</h1>
{embed="site/related_entries" related_ids="{my_entry_relationship_field}"}
{/exp:channel:entries}
The collection embed template: site/related_entries:
{!--
Pass the related entry ids into a second weblog entries tag
The passed custom field value will look something like: 1|2|3
The tag below *will* render the related entries
--}
<h2>Related Entries</h2>
<ul>
{exp:channel:entries weblog="my_related_weblog" entry_id="{embed:related_ids}"}
<li>{title}</li>
{/exp:channel:entries}
</ul>
{!--
You could also show all but the related entries
The tag below *will not* render the related entries
--}
<h2>Un-related Entries</h2>
<ul>
{exp:channel:entries weblog="my_related_weblog" entry_id="not {embed:related_ids}"}
<li>{title}</li>
{/exp:channel:entries}
</ul>
{exp:channel:entries channel="parent_weblog"}
<p>{title}</p>
<ul>
<li>{nsm_entry_select_field}</li>
<li>{nsm_entry_select_field value="title"}</li>
<li>{nsm_entry_select_field value="field_id_33"}</li>
<li>{nsm_entry_select_field value="field_id_33" multi_field="yes"}</li>
<li>{nsm_entry_select_field value="field_id_33" multi_field="yes" multi_field_glue="*" }</li>
</ul>
{/exp:channel:entries}
This tag accepts the following parameters:
The entry value to return. By default this is the entry id but it can be any of the standard entry attributes:
entry_idsite_idchannel_idauthor_idforum_topic_idtitleurl_titlestatusview_count_oneview_count_twoview_count_threeview_count_fourallow_commentsstickycomment_total
Example:
{my_entry_relationship_field value="title"} or {my_entry_relationship_field value="url_title"}
Custom field values can also be retrieved but for now you'll need to know the custom field id. Example:
{my_entry_relationship_field value="field_id_12"}
Note: Pulling custom data will require one or more small DB calls.
The glue for the returned entry values. Default glue is a pipe "|".
Example: Output the selected entry id's concatenated with a "," ie: 1,2,3. Use this in {exp:query} tag WHERE entry_id IN() conditional like so:
<ul>
{exp:query sql="
SELECT *
FROM `exp_channel_titles`
WHERE `entry_id`
IN({my_entry_relationship_field glue=","});
"}
<li>{title}</li>
{/exp:query}
</ul>
Related entries may have custom fields such as multi-select and checkboxes that store selected values in a pipe delimited string. In some cases you may want to replace the pipe with a human readable value such as a comma.
Example:
The related entry has a multi select box with 3 possible values: apples, oranges and lemons. The field id is "20". If the related entry has apples and oranges selected the value of the custom field will be apples|oranges.
Outputs: apples|oranges
{my_entry_relationship_field value="field_id_20"}
Outputs: apples, oranges
{my_entry_relationship_field value="field_id_20" multi_field="yes"}
The example above assumes that there is only one related entry.
Multi-select custom fields are glued with ", " by default. The glue string can be overridden with the multi_field_glue='' parameter.
Example:
Outputs: apples|oranges
{my_entry_relationship_field value="field_id_20"}
Outputs: apples, oranges
{my_entry_relationship_field value="field_id_20" multi_field="yes"}
Outputs: apples * oranges
{my_entry_relationship_field value="field_id_20" multi_field="yes" multi_field_glue=" * "}