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.

Allow EE Code issue

December 16, 2010 1:55pm

Subscribe [5]
  • #1 / Dec 16, 2010 1:55pm

    123454329

    144 posts

    Allow EE Code issue seems to have stopped working with 2.1.2

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

    **

    Also, I can’t see “Default Text Formatting” override options anymore…

    Show Formatting Buttons is set to “yes” but they don’t show up.

    **

    Pls advise!

  • #2 / Dec 17, 2010 3:08am

    John Henry Donovan

    12339 posts

    Thomas,

    Did you follow the version or build upgrade documentation?

    Can you provide a screenshot of that custom field page with the issues you describe

    Can you confirm you updated your themes folder when upgrading?

    Does you Allow EE Code plugin still exist in your third-party folder?

  • #3 / Dec 17, 2010 11:59am

    123454329

    144 posts

    Did you follow the version or build upgrade documentation?

    yes.

    Can you provide a screenshot of that custom field page with the issues you describe

    Screenshots removed

    btw, clicking on “glossary” does nothing!

    Can you confirm you updated your themes folder when upgrading?

    yes

    Does you Allow EE Code plugin still exist in your third-party folder?

    yes.

    **

    i believe this is a caching issue. try this:

    write

    {current_time format="%m / %Y"}

    to any entry and save. look at the webpage and it will display just the code. now, reload the webpage. and it will display what you really want to see.

    can you confirm?

  • #4 / Dec 18, 2010 3:24pm

    Greg Salt

    3988 posts

    Hi Thomas,

    I can replicate the “Allow override” not being shown on the Publish page so I have submitted a bug report. I cannot replicate the Glossary not working. Are you seeing any errors in Firefox Firebug, Chrome or Safari’s inspector?

    Cheers

    Greg

  • #5 / Dec 19, 2010 4:34am

    123454329

    144 posts

    hey greg,

    as i said “clicking glossary” does nothing for me. this is what i get in safari when i inspect the element:

    index.phpResource interpreted as stylesheet but transferred with MIME type text/php.
    index.phpResource interpreted as script but transferred with MIME type text/php.
    index.phpResource interpreted as script but transferred with MIME type text/php.
    index.phpResource interpreted as script but transferred with MIME type text/php.
    index.phpResource interpreted as script but transferred with MIME type text/php.
    index.phpResource interpreted as stylesheet but transferred with MIME type text/php.

    can’t say if this is related.

    **

    i am still concerned about the issue i described when i started this thread and what i believe is “caching” related:

    please grab the add-on here:
    http://expressionengine.com/downloads/details/allow_ee_code/

    make this code a snippet…

    {current_time format="%m / %Y"}

    …and throw it in an entry.

    when you first look at the webpage the code gets displayed as code but when you reload the page the code becomes the information you want it to be.

    as submitting an entry clears all caches this is odd.

    can you replicate that?
    thanks!

  • #6 / Dec 20, 2010 9:36am

    Sue Crocker

    26054 posts

    I’m not even getting the value to be processed then. Can I get you to log this as a defect? The link is in my signature.

  • #7 / Dec 20, 2010 11:14am

    123454329

    144 posts

    Tks, Susan!
    If there’s anything you wish to add…

    https://support.ellislab.com/bugs/detail/14828/

  • #8 / Dec 21, 2010 2:17am

    John Henry Donovan

    12339 posts

    Thomas,

    Thanks for your report. Keep an eye on the actual report as that is where the status will change

  • #9 / Dec 27, 2010 4:49pm

    Derek Jones

    7561 posts

    I commented in the bug thread, but to close the loop here, that variable will not be processed by that plugin, as {current_time} is parsed very early, long before any tags.  This is not new behavior, incidentally, just a limitation of what that plugin has access to.

  • #10 / Dec 27, 2010 5:32pm

    123454329

    144 posts

    is there a feasable way to display current_time within an entry then?

  • #11 / Dec 28, 2010 2:51am

    John Henry Donovan

    12339 posts

    Thomas,

    is there a feasable way to display current_time within an entry then?

    You could add {current_time format="%m / %Y"}  to an embed. Then use the embed parameter for the Allow EE Code tag.

    {exp:allow_eecode embed="y"}
  • #12 / Dec 28, 2010 3:07am

    123454329

    144 posts

    Tks, John.

  • #13 / Dec 28, 2010 10:30am

    Sue Crocker

    26054 posts

    Glad Derek was able to help.. Don’t hesitate to post again as needed.

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

ExpressionEngine News!

#eecms, #events, #releases