ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Trouble with AllowEE plugin

August 04, 2011 11:30pm

Subscribe [2]
  • #1 / Aug 04, 2011 11:30pm

    Aesa

    4 posts

    I have followed the instructions found here http://digitalformula.net/articles/Allow-ee-code-in-expression-engine-with-allow-ee-code to set all the parameters within the EE control panel and added the 2 required tags as directed in the AllowEE plugin instructions as follows

    {exp:channel:entries channel="packages_section_page"}
    {exp:allow_eecode}
    {page_content}
    {/exp:allow_eecode}
    {/exp:channel:entries}

    When building a page with this template I have entered a snippet tag ... {advanced_reservations} ... in the {page_content} field but EE is not parsing the snippet. When I view the page I see {advanced_reservations} instead of the text contained within the snippet.

    Does anyone have any idea what I have done wrong?

  • #2 / Aug 05, 2011 8:39am

    the3mus1can

    426 posts

    This is going to be a parse order issue.  Snippets are parsed earlier than the modules and plugins so that they can be used inside of them.  I am pretty sure you will not be able to get a Snippet to work in this scenario.

  • #3 / Aug 05, 2011 10:54am

    Aesa

    4 posts

    After reading this I created shared templates containing the text that is in each of the snippets and replaced the the snippet code with {embed="shared/templatename"} with the same results.

    When the page is viewed {embed="shared/templatename"} is displayed on the page instead of the text contained in the shared template.

    Any other suggestions?

  • #4 / Aug 05, 2011 11:07am

    the3mus1can

    426 posts

    This is the correct syntax for an embed:

    {embed="shared/templatename"}
  • #5 / Aug 05, 2011 11:23am

    Aesa

    4 posts

    I am using that syntax. the colons were a typo in that post and have been corrected

  • #6 / Aug 05, 2011 11:27am

    the3mus1can

    426 posts

    Try adding parse=“inward”:

    {exp:allow_eecode parse="inward"}
        {page_content}
    {/exp:allow_eecode}
  • #7 / Aug 05, 2011 11:35am

    Aesa

    4 posts

    Still doesn’t work. I also tried

    {exp:allow_eecode parse="inward" embed="y"}
        {page_content}
    {/exp:allow_eecode}


    and

    {exp:allow_eecode embed="y"}
        {page_content}
    {/exp:allow_eecode}

    with the same negative results.

    I have verified with the hosting company that the allow query and allow embed parameters were set to yes when the plugin was installed.

  • #8 / Aug 05, 2011 1:49pm

    the3mus1can

    426 posts

    Sorry, forgot about that param for the embed=“y” on the allow_eecode.  Unfortunately, I am also out of ideas at the moment.

  • #9 / Aug 05, 2011 3:37pm

    Aesa

    4 posts

    the3mus1can,

    Thanks for trying.

    Anyone else using this plugin that may have a solution?

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases