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.

Update 2.0.1pb01 to 2.1.3 Template Manager not loading

May 03, 2011 2:28pm

Subscribe [4]
  • #1 / May 03, 2011 2:28pm

    lebisol

    2234 posts

    Hi there,
    I just did an update from 2.0.1 to latest 2.1.3 (Build:20110411) and noticed two issues while I did not get errors on update.

    Now, Template Manager is not loading right for main site 1 (MSM)
    - regardless from theme being used either ‘default’ or ‘corporate’. I re-uploaded themes folder a few times…cleared cache, different browsers…etc. While in Template Manager none of the drop down menus work other than home button. If I used the flyout menu to edit single template then the editor loads fine, preference manager, snippets all work fine.

    -If I create a new site or use the template manager on 2nd site no issues at all.

    What gives?


    Thanks.

  • #2 / May 04, 2011 12:42am

    lebisol

    2234 posts

    After looking more at it the update did not work as smooth as installer made it seem.
    I am now getting a Notice of:

    Security Update Release
    An ExpressionEngine version 2.1.1, build 20101018 has been released as a security release. The latest version is: 2.1.3, and the latest build is: 20101220.

    Please download here and follow the update docs to ensure you are running on the most up-to-date version.

    while the footer in CP reads - current build but wrong version:

    ExpressionEngine v2.0.1pb01 - © Copyright 2003 - 2010 EllisLab, Inc.
    Script executed in 0.2032 seconds - 29 SQL queries used - Build:  20110411

    the problem with Template manager still persists; after stripping css I found an error in CP and not sure if it is related:

    Fatal error: Allowed memory size of 100663296 bytes exhausted (tried to allocate 24 bytes) in /home/user/public_html/themes/cp_themes/default/design/manager.php on line 215

    I am not in position to roll back the DB since the backup was corrupt so…any ideas what went wrong? File or database level? I could use a pointer.

    Thank you.

  • #3 / May 04, 2011 5:56am

    John Henry Donovan

    12339 posts

    lebisol,

    Can I just confirm that you did a version update as opposed to a build update?
    Did you completely replace your themes folder?

    How much PHP memory do you have?
    You can find this under your PHP Info under Tools under the variable name memory_limit

    Are you running any add-ons?

    What is your build and version for MSM?

  • #4 / May 04, 2011 12:19pm

    lebisol

    2234 posts

    Hi John,
    I did a full update with renaming of system folder trick and no issues came about, it failed at creating trackbacks archive but not a big deal. At this point I noticed the template manager issue and nothing else. In the meantime and out of desperation, I re-ran update (I know I know) during which I had some errors of creating tables as they have been created during first pass (installer/u202.php etc). I did not finish this second round of update due to having to hunt and comment out all the sql and what to comment out was not as obvious as a first few screens/errors.

    Yes, the templates have been deleted, new uploaded and then custom theme placed back. Forum module and themes updated just fine.

    1]———————
    memory_limit   96M
    post_max_size   15M

    2]———————
    Non-native running:
    JOA Captivate
    Facebook_comments
    Sitemap

    3]———————
    MSM = Version: 2.0 Build: 20101215


    Thanks again.

  • #5 / May 06, 2011 12:20pm

    Kevin Smith

    4784 posts

    Hey lebisol—

    Can you confirm for me that your permissions are set correctly? I don’t think it’s a filesystem issue, but let’s make sure we don’t miss the low hanging fruit here.

    Reviewing your MySQL tables and comparing them to the update files located in system/installer/updates, can you determine where the update failed?

    And just to be clear, was this update performed on a live site or a local development version? If it was on a live site, check with your host to see if they might have a backup of your site. Let’s keep working on it, but in case it turns out that this upgrade irreversibly failed, a rollback may be the only rescue possible.

    Kevin

  • #6 / May 06, 2011 12:53pm

    lebisol

    2234 posts

    Hi Kevin,
    It is a live site.
    Yeah a clean install and then database sync of existing tables data seems like the best path at this point. I was just trying to avoid this but might be the best option.
    Thanks for listing.

  • #7 / May 06, 2011 2:31pm

    lebisol

    2234 posts

    So after a clean install and then a db dump the EE version info in footer/notice is good.
    BUT my original problem is there with the template manger not loading. I don’t think this is file-system issue since cp_themes and entire folder structure for that matter is fresh and worked on a clean install.

    After the DB import something related to templates and coming from the db is doing this.
    Still getting an error in CP:

    Allowed memory size of 100663296 bytes exhausted (tried to allocate 71 bytes) in
    /home/user/public_html/themes/cp_themes/default/design/manager.php

    and it makes no sense as you look at the php settings above.
    Looking at the table I found ...TON of templates/revisions I assume.

    SELECT *
    FROM `exp_templates`
    WHERE `site_id` =1
    LIMIT 0 , 1000

    Showing rows 0 - 999 (8,286 total, Query took 0.0167 sec)

    How it grew so Big I don’t know since revision count is set to 10.
    After trunking the table ‘ee_templates’ the manager loaded fine so question is how to import template files back into the db as entries?

  • #8 / May 06, 2011 6:10pm

    Brandon Jones

    5500 posts

    lebisol,

    I’m assuming there are a lot of duplicates in there? Not sure what in the upgrade process would cause that, but I think you could try manually moving your 2.1.0 templates table into 2.1.3’s database and see if that works.

  • #9 / May 06, 2011 6:39pm

    lebisol

    2234 posts

    Must have been the update that multiplied the templates and could have been the root of all here.
    What I should have done after the upgrade…and did now is just ended up trashing the content of the tables exp_templates and template_groups and copy-paste manually recreated groups/templates from files. Odd, usually I get CP issues with files missing etc. never the DB but go figure.

    All is well now….man, what a pain of an upgrade.
    Thanks guys.

  • #10 / May 07, 2011 1:55pm

    Greg Salt

    3988 posts

    Hi lebisol,

    Thanks for the update and glad that you finally got this sorted out. I’ll go ahead and close this out now.

    Cheers

    Greg

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

ExpressionEngine News!

#eecms, #events, #releases