Upgrade gone awry--HELP!

[lalldrin]

Just upgraded from 0.31 (I think) to 1.4.1 on Linux/Apache and am having problems. I'm getting a blop of junk at the top of all admin pages, and at the end of the site output.

From the top of every admin page:

--------------------------------------------
e for the full disclaimer.

Copyright and License
Copyright © 2005, Robert Campbell . All Rights Are Reserved.
This module has been released under the GNU Public License. You must agree to this license before using the module.
'; ?> e for the full disclaimer.

Copyright and License
Copyright © 2005, Robert Campbell ....
--------------------------------------------

The copyright disclaimer repeats five times.


From the bottom of the main site output (www.calstateteach.net):

--------------------------------------------
modules[$key]; if ($gCms->modules[$key]['installed'] == true && $gCms->modules[$key]['active'] == true) { $gCms->modules[$key]['object']->ContentPostRender($html); } } Events::SendEvent('Core', 'ContentPostRender', array('content' => &$html)); header("Content-Type: " . $gCms->variables['content-type'] . "; charset=" . (isset($pageinfo->template_encoding) && $pageinfo->template_encoding != ''?$pageinfo->template_encoding:get_encoding())); echo $html; @ob_flush(); $endtime = microtime(); $db =& $gCms->GetDb(); $memory = (function_exists('memory_get_usage')?memory_get_usage():0); $memory = $memory - $orig_memory; $memory_peak = (function_exists('memory_get_peak_usage')?memory_get_peak_usage():0); if ($config["debug"] == true) { echo "

Generated in ".microtime_diff($starttime,$endtime)." seconds by CMS Made Simple using ".(isset($db->query_count)?$db->query_count:'')." SQL queries and {$memory} bytes of memory (peak memory usage was {$memory_peak}
"; } else if( !isset($config['hide_performance_info']) ) { echo "\n"; } if (get_site_preference('enablesitedownmessage') == "1" || $config['debug'] == true) { $smarty->clear_compiled_tpl(); #$smarty->clear_all_cache(); } if ($config["debug"] == true) { #$db->LogSQL(false); // turn off logging # output summary of SQL logging results #$perf = NewPerfMonitor($db); #echo $perf->SuspiciousSQL(); #echo $perf->ExpensiveSQL(); #echo $sql_queries; foreach ($gCms->errors as $error) { echo $error; } } # vim:ts=4 sw=4 noet ?>
--------------------------------------------

This is PHP code being output at the bottom of every page. Clearly not good!

Any ideas?

Thanks,

Loren

[Pierre M.]

Hello Loren,

Just upgraded from 0.31 (I think) to 1.4.1

This is an adventure. I even wonder if it is a joke. For some release the release notes tell only about versions after 0.5. Prior releases are prior stone age.
Around the 1.1 or 1.2 era CMSms (modules) API has changed a lot.
You should try to upgrade step by step : 0.3 -> 0.5 -> 1.0 -> 1.1 -> 1.2 -> 1.3 -> 1.4.1 and soon -> 1.5.
Beware modules upgrades and tweaks at each stage.
Keeping current is much less pain.

Pierre M.

[lalldrin]

Nope, it's not a joke. And I've learned my lesson about staying current! I'm planning to just do a fresh install and move the (now converted) database over. Hopefully that does it.

I was unaware that CMSms upgrades had to be incremental. If that's the case, I'm feeling blessed that I have a functioning site at all.

Thanks for the truth, even if it didn't bring an easy fix.

Loren

[alby]

I was unaware that CMSms upgrades had to be incremental. If that's the case, I'm feeling blessed that I have a functioning site at all.

I did many upgrades from 1.1.X to 1.4.1 but 0.3 ....

Alby