Problems upgrading from 1.5.2 to 1.6.3 Build:  20080421
Posted: 30 May 2008 12:58 PM   [ Ignore ]  
Grad Student
Rank
Total Posts:  60
Joined  04-19-2005

I’ve run into some problems upgrading from 1.5.2 to 1.6.3 (Build: 20080421), similar to those found here:

http://expressionengine.com/forums/viewthread/72291/ (and a number of similar threads)

I was able to complete the software update successfully based on Lisa’s suggestions found in the forums but I’m now getting the following error on the home page of the site:

Parse error: syntax error, unexpected T_ENDIF in /www/pmh4652/public_html/eesys/core/core.functions.php(637) : eval()'d code on line 12

I’m not sure where/how to begin troubleshooting at this point. Any help would be appreciated.

Profile
 
 
Posted: 30 May 2008 01:17 PM   [ Ignore ]   [ # 1 ]  
Moderator
Avatar
RankRankRankRankRankRankRank
Total Posts:  15368
Joined  05-15-2004

Can you access other pages fine? Your control panel, too? Looks like there might be a problem with your template, could you put it in a text file and attach it here?

 Signature 

Everything will be good in the end. If it’s not good, it’s not the end.

Profile
MSG
 
 
Posted: 30 May 2008 01:30 PM   [ Ignore ]   [ # 2 ]  
Grad Student
Rank
Total Posts:  60
Joined  04-19-2005

Yes I can access the CP and other pages on the site - article page

(Bear with me. I didn’t build the site so I’m having to pick my way through the code.)

The contents of the index page are as follows:

{embed=brick/header-super page_title="Brick Reloaded"}
{assign_variable
:my_weblog="brick"}
{assign_variable
:my_template_group="brick"}

{embed
=brick/index_featured}

Which leads us to the “brick/index_featured” template.


I’ve cut all of the EE code (with the exception of an embed=“brick/footer” tag which works fine) from that page.

I can get index_featured to load on its own but not when called through the embed process from the index template.

The pared down index_featured template is attached as a text file.

hmm - attempted to upload a .txt file and got this error:
Error Message:  The file you are attempting to upload has invalid content for its MIME type.

Let’s just do this:

<table border="0" cellspacing="0" cellpadding="8">
    <
tr>
        <
td valign="top" width="300" style="border-right:#CCCCCC 1px solid">
            <
div style="margin-left:5px; padding-top:5px">
                <
span class="section">NEW STUFF</span><br />
<!--
removed new stuff weblog entries -->
            </
div>

            <
div align="center" style="margin-bottom:10px; margin-top:10px">
<!--
removed OAS code -->            
            </
div>
        </
td>
        
        <
td valign="top" width="300">
<!--
removed calendar code -->
            <
div style="margin:18px 5px 2px 10px" align="left"><span class="indexHeader"><a href="http://twitter.com" target="_blank">TWITTER</a></span></div>
<!--
removed flash twitter badge -->
            <
div style="margin-left:5px; padding-top:10px">
<!--
removed hotFresh weblog entries -->
            </
div>
        </
td>
    </
tr>
    <
tr>
        <
td colspan="2">{embed="brick/footer"}</td>
    </
tr>
</
table>

Profile
 
 
Posted: 30 May 2008 01:50 PM   [ Ignore ]   [ # 3 ]  
Grad Student
Rank
Total Posts:  60
Joined  04-19-2005

I think I may have narrowed the issue down to a specific weblog entries query in the original index_featured template.

Reviewing now.

Profile
 
 
Posted: 30 May 2008 02:02 PM   [ Ignore ]   [ # 4 ]  
Grad Student
Rank
Total Posts:  60
Joined  04-19-2005

[pulls hair out]

I found it. They had the following as a conditional:

{if:byline}

Replacing that with the following resolved the problem:

{if byline}

Questions:

Was the colon ever a part of the conditional formatting syntax?
Do I need to have them do a review on their templates for similar issues?
This code worked in 1.5.2. Was that version more lenient in terms of conditionals?

Thanks for pointing me in the direction of a problem with a specific template, Ingmar.

Profile
 
 
Posted: 30 May 2008 02:11 PM   [ Ignore ]   [ # 5 ]  
Moderator
Avatar
RankRankRankRankRankRankRank
Total Posts:  15368
Joined  05-15-2004

Glad you found it. No, the colon is a typo, and always has been. I am not aware of an alternate syntax that would have worked in older versions, but I have no version old enough to test. Note that with advanced conditionals, the preferred form is now:

{if byline != ""}

although the old version will still work for simpe conditionals (ie not involving elseif/else clauses).

 Signature 

Everything will be good in the end. If it’s not good, it’s not the end.

Profile
MSG
 
 
Posted: 30 May 2008 02:13 PM   [ Ignore ]   [ # 6 ]  
Grad Student
Rank
Total Posts:  60
Joined  04-19-2005

I’ll see that they’re aware of the preferred method for conditional syntax. Thanks again.

Profile
 
 
Posted: 30 May 2008 02:15 PM   [ Ignore ]   [ # 7 ]  
Moderator
Avatar
RankRankRankRankRankRankRank
Total Posts:  15368
Joined  05-15-2004

Very good. Closing that one out for now, if there’s anything else, related or not, kindly start a new thread in the appropriate forum, thanks.

 Signature 

Everything will be good in the end. If it’s not good, it’s not the end.

Profile
MSG
 
 
   
 
 
Post Marker Legend
New Topic New posts Hot Topic Hot Topic with new posts New Poll New Poll Moved Topic Moved Topic Sticky Topic Sticky topic
Old Topic No new posts Hot Old Topic Hot Topic with no new posts Old Poll Old Poll Closed Topic Closed Topic Announcement Announcements
Theme
Change Theme
Visitor Statistics
The most visitors ever was 1149, on July 16, 2007 09:33 AM
Total Registered Members: 64908 Total Logged-in Users: 38
Total Topics: 81852 Total Anonymous Users: 24
Total Replies: 440060 Total Guests: 224
Total Posts: 521912    
Members ( View Memberlist )