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.

CP problem when upgrading from 2.1.2 to 2.1.3

January 18, 2011 1:09pm

Subscribe [5]
  • #1 / Jan 18, 2011 1:09pm

    moogaloo

    200 posts

    Ive upgraded from EE 2.1.1 to 2.1.2 OK now (having had problems as detailed hand fixed here - http://ellislab.com/forums/viewthread/176081/#835515 )

    I then went about upgrading to 2.1.3 and hit a problem when I uploaded the backed up /themes folder, getting the following error o the CP pages:

    A PHP Error was encountered
    
    Severity: Notice
    
    Message: Undefined variable: theme_css_mtime
    
    Filename: _shared/header.php
    
    Line Number: 9
    index.php?S=dfeec82a25d6f33b3ceee01090c21c8f6bca1db0&D=cp&C=css&theme=default&v=" type="text/css" media="screen" title="Global Styles" charset="utf-8" >

    with the page all messed up having no styling attached to it.
    I then went back and replaced the themes folder with the default ee2.1.3 base install /themes folder and the css was working (altho some of the JS wasn’t working such as the accessories windows and the CP navigation dropdowns)
    When I tried to re-upload the backed up /themes folder the same error occurred.

    I’m aware that this may therefore be to do with some 3rd party addons that have messed things up, but any pointers would be greatly appreciated right now!!

  • #2 / Jan 18, 2011 2:25pm

    McCoy IT

    41 posts

    I’m having the same issue as you are having with the control panel. 2.1.1 upgraded to 2.1.3
    Plugins: Solspace Freeform 3.0.5, Pixel & Tonic Matrix 2.1.2, Wygwam 2.1.7, Fieldpack and Dive Bar addons.

  • #3 / Jan 18, 2011 5:25pm

    moogaloo

    200 posts

    I’m having the same issue as you are having with the control panel. 2.1.1 upgraded to 2.1.3
    Plugins: Solspace Freeform 3.0.5, Pixel & Tonic Matrix 2.1.2, Wygwam 2.1.7, Fieldpack and Dive Bar addons.

    Ok.
    I’m using all of them too - think I’ll update each theme pack in term to find the culprit.
    I’ve got a lot more than those, so that’s a good head start!

  • #4 / Jan 18, 2011 5:30pm

    moogaloo

    200 posts

    I know 2.1.3 changed the way the cp handled styling, so I guess its to do with that

  • #5 / Jan 18, 2011 8:43pm

    moogaloo

    200 posts

    OK - I’ve narrowed it down to the following file: /themes/cp_themes/default/_shared/header.php

    If I avoid uploading that file, the main CP seems to load fine… but…

    When I now go into a publish page it’s all errors - see attached.

    I really hope this can get fixed soon - I’ve wasted over day of time now trying to get this site working, which it was doing fine as EE2.1.1, and has been problem after problem after problem since updating to 2.1.3

  • #6 / Jan 19, 2011 8:35am

    moogaloo

    200 posts

    bump - really need some help on this - the backend is completely screwed up due to updating I think - I cant work on this site as it is.

  • #7 / Jan 19, 2011 6:07pm

    Ingmar

    29245 posts

    When I tried to re-upload the backed up /themes folder the same error occurred.

    Yes, there were some changes to the 2.1.3 themes, you need to download a fresh set as well.

  • #8 / Jan 19, 2011 7:25pm

    moogaloo

    200 posts

    ok - i think that covers the initial problem, with the shared/header.php file being different in 2.1.3, but the publish pages are still a mess… any idea?

    I really dont want to have to go thru the process of trying to roll back to 2.1.1 and start again.

  • #9 / Jan 20, 2011 8:42am

    Sue Crocker

    26054 posts

    Are you using a stock theme?

  • #10 / Jan 20, 2011 9:41am

    moogaloo

    200 posts

    not quite sure i know what you mean… the CP is using the NSM Morphine accessory (which I’ve usd in every EE2 site since it came out).
    I’ve tried turning Morphine off and the problem is exactly the same.

  • #11 / Jan 20, 2011 9:57am

    the themes folder has completely changed in version 2.1.3. try using the newer version and only restore your backed up third-party folder.

  • #12 / Jan 20, 2011 10:16am

    moogaloo

    200 posts

    OK - will give that a go - thanks

  • #13 / Jan 20, 2011 11:02am

    moogaloo

    200 posts

    Yep - that appears to have resolved teh problems.

    This, I think, is the 6th site I’ve upgraded / installed to 2.1.3 this week, all with local and live setups, most of which not going exactly smoothly - my head isn’t used to this much intensive thinking!!

  • #14 / Jan 20, 2011 3:15pm

    Ingmar

    29245 posts

    Glad to see you’re all set. Please post again as needed.

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

ExpressionEngine News!

#eecms, #events, #releases