Page 1 of 1

[mod_issue] Upgrade experience

Posted: Wed May 28, 2014 1:56 am
by paulbaker
I upgraded from a 1.11.10 site.

Here is what I started from:

----------------------------------------------
Cms Version: 1.11.10
Installed Modules:
CMSMailer: 5.2.2
CMSPrinting: 1.0.5
FileManager: 1.4.4
MenuManager: 1.8.6
MicroTiny: 1.2.6
ModuleManager: 1.5.5
News: 2.14.2
Search: 1.7.11
ThemeManager: 1.1.8
Quotes2: 1.0.2
CGExtensions: 1.38.8
CGSimpleSmarty: 1.7.2
JQueryTools: 1.2.6
Products: 2.20.2
Showtime: 3.4
Archiver: 0.2.6
FormBuilder: 0.7.4
SEOTools2: 1.2.1
UsersGuide: 1.8.1

Config Information:
php_memory_limit:
process_whole_template:
max_upload_size: 32000000
url_rewriting: none
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true

Php Information:
phpversion: 5.4.21
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
memory_limit: 128M
max_execution_time: 120
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 8M
upload_max_filesize: 32M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)

Server Information:
Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.1.73
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No filesystem time difference found

----------------------------------------------

In Step 8 I got:
Upgrading database for CMSMS 1.99-alpha0

updating structure of content tabless

add index to the module plugins table

updating structure of the permissions table

add index to user groups table

deleting old events

creating new events

create table layout_tpl_type

create table layout_tpl_categories

create table layout_templates

create table layout_stylesheets

create table layout_tpl_addusers

create table layout_designs

create table layout_design_tplassoc

create table layout_design_cssassoc

create table locks

create initial template types

convert global content blocks to generic templates

dropping gcb related tables...

converting stylesheets

converting page templates

created design NCleanBlue

created template NCleanBlue

associated 3 stylesheets with the design

created design CTW

created template CTW

associated 1 stylesheets with the design

created design CTWHome

created template CTWHome

associated 1 stylesheets with the design

adjusting pages
Upgrade itself seemed to go OK. But front end gave white screen. I cured that with a clear CMSMS cache.

Then I got an Oops screen:

Code: Select all

ERROR: at line 127 in file /home/cthuk/public_html/betaupgrade/lib/smarty/sysplugins/smarty_internal_templatebase.php:

Message:

Unable to load template tpl_top '24'
Close Full Trace ?
#0 /home/cthuk/public_html/betaupgrade/lib/classes/internal/class.Smarty_CMS.php(306): Smarty_Internal_TemplateBase->fetch('tpl_top:24', 'p15', NULL, NULL, false, false, false)
#1 /home/cthuk/public_html/betaupgrade/index.php(169): Smarty_CMS->fetch('tpl_top:24')
#2 {main}

The site uses 4 GCBs.

Now, according to
http://forum.cmsmadesimple.org/viewtopi ... 82&t=70192
GCBs should still work OK.

There is 1 GCB on the home page which is the page erroring. It is called like this:
{global_content name='Footer'}
in the old non-upgraded version of the site and unchanged in the new beta upgraded version.

When I try to edit the home page template (using DesignManager) I get a white screen when I save.

Here's what it upgraded to:

----------------------------------------------
Cms Version: 2.0-beta1
Installed Modules:
CMSMailer: 5.2.2
CMSPrinting: 1.0.5
FileManager: 1.4.4
MenuManager: 1.8.6
MicroTiny: 1.2.6
ModuleManager: 1.5.5
News: 2.14.2
Search: 1.7.11
ThemeManager: 1.1.8
Quotes2: 1.0.2
CGExtensions: 1.38.8
CGSimpleSmarty: 1.7.2
JQueryTools: 1.2.6
Products: 2.20.2
Showtime: 3.4
Archiver: 0.2.6
FormBuilder: 0.7.4
SEOTools2: 1.2.1
UsersGuide: 1.8.1
AdminSearch: 1.0
CMSContentManager: 1.0
DesignManager: 1.0
Navigator: 1.0

Config Information:
php_memory_limit:
max_upload_size: 32000000
url_rewriting: none
page_extension:
query_var: page
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true
timezone: Europe/London

Php Information:
phpversion: 5.4.21
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
E_DEPRECATED: 0
test_file_timedifference:
test_db_timedifference:
memory_limit: 128M
max_execution_time: 120
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 8M
upload_max_filesize: 32M
session_save_path: /tmp (1777)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)

Server Information:
Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.1.73
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No file system time difference found

----------------------------------------------

Other points:

Content Manager shows all pages but with a "** ERROR **" under the Template column for all pages. The Page titles show but they are not clickable so I can't edit Pages.

Site Users Guide: clicks to a white page with just "Main Page".

Archiver doesn't even show properly in the menu - just shows as "-" and this gives blank white screen when clicked.

Product Manager clicks to white page with "Items, Field Definitions ...etc." on left.

Quotes2 clicks to white page with "Quotes, Groups..." on left.

SEOTools2 appears to work OK.

Showtime Slideshow appears to work OK.

Form Builder clicks to white screen.

Happy to try some things on this upgrade if someone can point me in the right direction.

Re: Upgrade experience

Posted: Fri May 30, 2014 2:29 pm
by calguy1000
I tested this last night. It is because of the use of smarty by module developers in the constructor of their modules without checking if smarty exists.

Smarty (or rather the CMSMS smarty) does not exist during the upgrade process, so the module(s) generate a fatal error.

I had to correct a bunch of my modules too.