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.

Upgrade Errors

February 12, 2012 10:20pm

Subscribe [4]
  • #1 / Feb 12, 2012 10:20pm

    Tad Ward

    41 posts

    I upgraded a site from EE 1.6.8 to EE 2.4.
    The EE 1 site had numerous add-ons, a few of course didnt have EE2 equivilents.
    Upgrade went smooth except, I am receiving two errors.  Only see them when logged in as Super Admin (errors for Super Admin turned on of course), but the site when viewed logged out or other browsers seems to work fine.

    The errors are in the attached image.
    The first error, I have no idea what would be causing it.  I have tried reuploading the Template.php file thinking it was corrupted during upgrade, but that did nothing.

    The second error, I have come to find out it has to do with the Generate HTTP Page Headers under Output and Debugging being turned on.  I turn it off and it disappears.  But in all ee installs I have done this is always on.
    Also in Output and Debugging both Enable GZIP Output and Force URL query strings are on as well.

    I turn off Force URL query strings, nothing is fixed.  But if I turn off Enable GZIP Output, the site becomes viewable but that error is still at top of the site.

    What could be causing the issue?
    Previous add-on, something the database?

    Thanks much in advance!

  • #2 / Feb 13, 2012 11:28am

    I would guess that the first error (the one about $end) is from a missing add-on.

    The rest of the errors are caused from the first error being shown, it messes with the template parser output and thus gets a bit angry.

  • #3 / Feb 13, 2012 11:34am

    Tad Ward

    41 posts

    Hey Jeremy, thanks for the tip.  I was thinking it was an add-on of some sort.
    Could this error be popping up if that add-on was disable/uninstalled in ee1 before the upgrade?

  • #4 / Feb 13, 2012 7:24pm

    Sean C. Smith

    3818 posts

    Tad,

    The error should not be there if the add-on was disabled or uninstalled before the upgrade. Did you uninstall all incompatible add-ons before the upgrade to 2.4? Do these errors occur on all pages in the CP or only on specific ones?

    Sean

  • #5 / Feb 13, 2012 7:27pm

    Tad Ward

    41 posts

    Hey Sean,

    The error isn’t in the CP, its when you view the website while logged in as Super Admin.
    Yes I uninstalled all incompatible add-ons before the upgrade.

    Tad

  • #6 / Feb 14, 2012 10:06pm

    Robin Sowell

    13255 posts

    Odd one- it looks like it’s related to a segment conditional.  Can you try this- just to get a better feel for what’s going on.

    Open up system/expressionengine/libraries/Template.php and around line 3245 let’s put in some debug:

    eval("\$result = (".$cond.");");
            
    if ($result)
    {

    change to:

    eval("\$result = (".$cond.");");
            
    if (! isset($result))
    {
    var_dump($cond);
    }
    elseif ($result)
    {

    What that will do- show us how it's seeing that conditional when the error occurs. It's not a fix- but it should help us discover what's going wrong. It's not like an {if segment_x something…} for some reason.

     

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

ExpressionEngine News!

#eecms, #events, #releases