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.

[Solved] Upgrade issue

November 02, 2010 12:29pm

Subscribe [4]
  • #1 / Nov 02, 2010 12:29pm

    Net Resources

    26 posts

    Hi

    Upgrading EE from version 2.1.0 to 2.1.1 (20101020) on a development server.
    Have gone through the stages outlined at http://ellislab.com/expressionengine/user-guide/installation/update.html

    Since upgrading, the front-end and majority of the back-end/control panel work fine.
    However, when I try to add or edit an entry I get a blank page with “The page you requested was not found.” message returned.

    Is this something anyone else has experienced with the recent upgrade?

    Cole

  • #2 / Nov 02, 2010 1:36pm

    Net Resources

    26 posts

    To add some further info the same problem happens when I try to access Tools > Utilities > PHP Info

  • #3 / Nov 02, 2010 2:29pm

    Net Resources

    26 posts

    Additionally, if I go the CP Home I get a blue Notice panel with the following message:

    new_version_notice_high_priority

  • #4 / Nov 02, 2010 2:41pm

    Net Resources

    26 posts

    Apologies - one further (though likely unrelated) symptom of the upgrade is that the Javascript interactions with the CP aren’t working, eg show ExpressionEngine Info panel in the footer doesn’t slide up/down (just hidden) and likewise with the sidebar.

    Looking at the source code all the requisite JS files are being loaded - just their implementation in the pgae isn’t kicking in.

    Ta,

    Cole

  • #5 / Nov 03, 2010 6:00am

    John Henry Donovan

    12339 posts

    Cole,

    Can I confirm you also updated your themes folder when you upgraded?
    Do you have any add-ons installed.

  • #6 / Nov 03, 2010 8:30am

    Net Resources

    26 posts

    Hi John

    Problem resolved and hands up I’m afraid that the problem seems to have been between the User and Keyboard in this instance. It turns out the javascript issue was related. I dug a little deeper and found out that there was no global.js in the upgraded version.

    On further investigation it turns out that there had been around 19 files missing from our copy of the EE211 download. Replaced the errant files and all seems to be working now.

    One question - I assume upgrading the version of EE from 210 to 211 negates the need to upgrade to the latest build? CP is saying 20101020

    Thanks,

    Cole

  • #7 / Nov 03, 2010 8:50am

    Net Resources

    26 posts

    Right, alas the issues is not resolved.

    Adding a new page am confronted with the following error message:

    An Error Was Encountered
    You have tried to access a channel that does not exist.

    If I go into Content > Edit I can see that entry has saved just fine and it is also shown in the site front-end.

    However, if I now try and edit/access the file in the CP I get the same error message.

    Any thoughts?

    Cole

  • #8 / Nov 03, 2010 9:00am

    Net Resources

    26 posts

    John

    Sorry, in answer to your earlier question there are a number of add-ons installed on the site:

    Modules:

    AWGrab
    Playa
    SEO Lite
    Structure

    Extensions:

    Drifter
    Freebie
    Last Segment
    Matrix
    Playa
    WYMEditor

    Fieldtypes:

    Matrix
    Playa
    WYMeditor

    Plus a range of plugins (although these shouldn’t affect the CP, right?)

    Cheers

    Cole

  • #9 / Nov 03, 2010 11:14am

    Net Resources

    26 posts

    Noticed that despite the upgrade the footer is reporting version 2.1.0 (but with build 20102010).
    Similar issue reported at http://ellislab.com/forums/viewthread/172225/ although in this instance definitely following the instructions for upgrading versions (rather than builds).

    Cole

  • #10 / Nov 03, 2010 4:52pm

    Ingmar

    29245 posts

    You have run the upgrade, I suppose? What does it say in your config.php file? Also, in your case I would recommend to replace all files with a fresh copy. Make sure that all files are uploaded to the server, correctly, including themes etc. files.

  • #11 / Nov 04, 2010 9:03am

    Net Resources

    26 posts

    Hi Ingmar

    Okay, run the version upgrade again.
    Javascript is working fine and now reporting that is on 2.1.1 (20102010).

    However, when trying to add a new entry I still get the error message:

    An Error Was Encountered
    You have tried to access a channel that does not exist.

    As before, the entry is added and shows up in the front-end just fine but can’t access from the back-end. If I try to edit an existing entry (Content > Edit) I get the same error message:

    An Error Was Encountered
    You have tried to access a channel that does not exist.

    Screenshot attached (Standard CI error message/display?).

    Cheers

    Cole

  • #12 / Nov 04, 2010 4:37pm

    Ingmar

    29245 posts

    When you look at the data in the MySQL db directly, what channel_id does it have?

  • #13 / Nov 04, 2010 5:48pm

    Net Resources

    26 posts

    Hi Ingmar

    All seems fine in the DB - all the channel ids correlate as expected (added two entries to two separate channels).
    However a dig around MySQL reveals another problem which might be the cause of the reported issue.
    There is no associated information for the added entries in the `exp_channel_data` table.

    Could this be caused by a conflict with one of the fieldtypes (see response http://ellislab.com/forums/viewthread/172236/#819664 above) or a more general issue with saving entries?

    Cheers

    Cole

  • #14 / Nov 05, 2010 10:14am

    Ingmar

    29245 posts

    It sounds like a possibly corrupted database. Do you have a pre-upgrade backup? Does it suffer from the same symptoms?

  • #15 / Nov 05, 2010 11:57am

    Net Resources

    26 posts

    Hi Ingmar

    Reverted back to pre-update version and all is hunky dorey.
    Rolled out an update (for about the sixth time this week) and systematically deleted all the Add-ons. The one that seemed to be causing the problems was the Drifter Accessory.

    Will roll out another upgrade to double test and report back.

    Cole

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

ExpressionEngine News!

#eecms, #events, #releases