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.

Client Updated to 1.7.1 and Advanced Conditionals No Longer Work

April 13, 2011 2:40pm

Subscribe [2]
  • #1 / Apr 13, 2011 2:40pm

    Justin Long

    196 posts

    I have a large client site that we recently updated from 1.6.8 with the core hacked, we are now running a clean unhackec version of 1.7.1. Since the update all of the advanced conditionals no longer work, this includes if:else and if with statements AND or OR. Simple conditionals work just fine as do PHP conditionals. The site in question is fairly large (400 or so templates) so I do not fancy going through every template and changing all the conditionals.

    Any ideas?

    I can provide site access via PM.

  • #2 / Apr 13, 2011 2:56pm

    Lisa Wess

    20502 posts

    Hi, Justin,

    Do you know when you downloaded EE 1? There was a problem in the initial build, but it was fixed quickly.

    There are details in this thread.

  • #3 / Apr 13, 2011 3:10pm

    Justin Long

    196 posts

    Actually Lisa that might be it, I downloaded it shortly after release because the first time I tried to download I couldn’t because it was being update. I will redownload and report back.

    - Just updated and it does not appear to be fixing anything.

  • #4 / Apr 13, 2011 5:05pm

    Sue Crocker

    26054 posts

    Justin, when you say advanced conditionals - could you give a simplified example? I’ll try to replicate it from a fresh build of EE 1.7.1.

  • #5 / Apr 13, 2011 5:09pm

    Justin Long

    196 posts

    Sure for example the homepage currently has

    {if segment_2}
        {embed="utils/_standard_content"
                livelook_cachebust="{embed:livelook_cachebust}"
                livelook_statuses="{embed:livelook_statuses}" 
                livelook_show_future="{embed:livelook_show_future}" 
                livelook_show_expired="{embed:livelook_show_expired}"
            } 
    {if:else}
        {embed="utils/_homepage"
                livelook_cachebust="{embed:livelook_cachebust}"
                livelook_statuses="{embed:livelook_statuses}" 
                livelook_show_future="{embed:livelook_show_future}" 
                livelook_show_expired="{embed:livelook_show_expired}"
            } 
    {/if}
  • #6 / Apr 14, 2011 3:49pm

    Sue Crocker

    26054 posts

    Justin, can you test with a similar template in a template group called testme:

    {if segment_2 ==""}
    Some segment
    
    {if:else}
    In the else
    
    {/if}

    Does that work as expected?

  • #7 / Apr 15, 2011 2:27pm

    OutofControl

    164 posts

    I had this same issue which was fixed in the most recent 1.7.1 update. If you are using caching, be sure to clear the cache after upgrading to the “fixed” 1.7.1 to clear the conditional errors.

  • #8 / Apr 15, 2011 3:13pm

    Sue Crocker

    26054 posts

    Thanks for the assist, James.

    Justin?

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

ExpressionEngine News!

#eecms, #events, #releases