Seems like this ought to be working… I know that generally you wrap the allow_eecode tags around a single field, but this is being used in concert with Pages and the field I need to display is the Body field, which contains several entries loops as shown below:
{exp:weblog:entries weblog="snippets" url_title="news_events_intro_text" disable="categories|category_fields|member_data|trackbacks" rdf="off"}
{content}
{/exp:weblog:entries}
<h2>Our Next Trade Show</h2>
{exp:weblog:entries weblog="events" disable="categories|category_fields|member_data|pagination|trackbacks" rdf="off" show_future_entries="yes" limit="1" sort="asc"}
<a href="http://{cf_events_url}" target="_blank" rel="noopener">{title}</a>
{entry_date format="%m %d %Y"}
{cf_events_city}, {cf_events_state}
{/exp:weblog:entries}
<h2>Press Releases</h2>
{exp:weblog:entries weblog="pressreleases" disable="categories|category_fields|member_data|pagination|trackbacks" rdf="off"}
<a href="http://{url_title_path=news_events/press_release}">{title}</a>
{entry_date format="%m %d %Y"}
{/exp:weblog:entries}
<h2>Customer Success Stories</h2>
{exp:weblog:entries weblog="csstories" disable="categories|category_fields|member_data|pagination|trackbacks" rdf="off"}
<a href="http://{url_title_path=news_events/customer_success_story}">{title}</a>
{entry_date format="%m %d %Y"}
{/exp:weblog:entries}
And my template then looks like this:
{exp:weblog:entries weblog="pages" rdf="off"}
{embed="includes/header_top" title="{title}"}
<!-- Insert additional JS and CSS references here -->
{embed="includes/header_bottom" loc="news"}
<div id="content-left">
{embed="includes/submenu_news" locs="{cf_pages_submenu_loc}"}
</div>
<div id="content-center">
{exp:allow_eecode}
{cf_pages_body_{country_code}}
{/exp:allow_eecode}
</div>
<div id="content-right">
Right
</div>
{embed="includes/footer" loc="news"}
{/exp:weblog:entries}
I’m guessing that this just isn’t going to work to display all this different data. And since this is a Pages template that needs to serve 5-6 different pages its needs to stay very generic.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.