Skip to content

Commit 408c8a6

Browse files
committed
Merge remote-tracking branch 'origin/patch-31' into Pro-Variables-doc-cleanup
2 parents b7f37b3 + f6647dd commit 408c8a6

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/add-ons/pro-variables/fieldtype.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,9 @@ The value of the field will be the _variable name_, for example: `my_var`. To ou
2727

2828
## Examples
2929

30-
Say you have 5 different testimonial quotes stored as variables in the variable group Quotes, named `lv_quote_1` to `lv_quote_5`. To each News entry, you want to add one of those quotes. Then add a Pro Variables field to your News field group, eg. `news_quote`. Then select the Quotes group in the field settings. To output the quote, you’d need code like this:
30+
Say you have 5 different testimonial quotes stored as variables in the variable group Quotes, named `pv_quote_1` to `pv_quote_5`. (Remember, you can create these in one pass using the (suffix option)[/add-ons/pro-variables/manage.md#variable-creation-options].)
31+
32+
To each News entry, you want to add one of those quotes. Then add a Pro Variables field to your News field group, eg. `news_quote`. Then select the Quotes group in the field settings. To output the quote, you’d need code like this:
3133

3234
{exp:channel:entries channel="news"}
3335
<h2>{title}</h2>
@@ -54,4 +56,4 @@ If you’re allowing for multiple selections, you can use the channel field as a
5456
{news_quotes}
5557
<blockquote><p>{{var}}</p></blockquote>
5658
{/news_quotes}
57-
{/exp:channel:entries}
59+
{/exp:channel:entries}

0 commit comments

Comments
 (0)