Several problems when trying to upgrade to 1.11.7 [SOLVED]

[cmsforchurch]

I currently have CMS Version 1.9.4.2 "Faanui" and want to upgrade to 1.11.7.

I'm trying to follow the instructions on the upgrade page:
http://docs.cmsmadesimple.org/upgrading

Problem 1:
The upgrade instructions say I must first upgrade to 1.10 before I upgrade to 1.11. Where is 1.10? The download page only lists 1.11.7 and 1.11.6. I can't find 1.10 or any other versions earlier than 1.11.6.

Because I couldn't find 1.10, I tried installing 1.11.7.

Problem 2:
The upgrade instructions say I must first upgrade all 3rd party addons before I upgrade CMS. I went to Extensions >> Module Manager. It didn't list any modules. Does that mean all my modules are up to date? So I didn't upgrade any modules before I tried installing 1.11.7.

Problem 3:
The install process flagged my version of PHP with a warning. It said it should work with mine, version 5.2.17, but it recommends 5.3. I switched my web server to 5.3. But when I clicked the button it to try it again, it gave an error that "Session not working, you have problem with some modules and functionality! Ask your provider, exiting!" Not sure what "provider" it means or what I must ask my provider. So, since it said it should still work with 5.2, I switched it back to 5.2 and clicked the button to continue.

It then upgraded config.php OK, cleared the cache OK. But it stopped in the middle of the next step and wouldn't continue.

Problem 4:
Step 5 only does these steps:
Adding module_smarty_plugins table...[done]

Enhancing the adminlog table...[done]

Enhancing the css table table... [done]

Creating routes table... [done]

Adding an index to the content table.... [done]

Building static route database...

Thanks in advance for any help anyone can give me.

[Jo Morg]

One step at the time...

Problem 1:The upgrade instructions say I must first upgrade to 1.10 before I upgrade to 1.11. Where is 1.10? The download page only lists 1.11.7 and 1.11.6. I can't find 1.10 or any other versions earlier than 1.11.6.Because I couldn't find 1.10, I tried installing 1.11.7.

Hopefully you made a backup...
The full list of downloads is here. Revert to the backup and try the recommended procedure.
HTH.

[paulbaker]

[Jo types quicker than me, but much of what I say is relevant]

1: About half way down the downloads page you'll see "All releases are available in the file release system" with a link to a page listing all versions back to the dawn of time. The link is not particularly obvious.

Because I couldn't find 1.10, I tried installing 1.11.7.

Hmm, if you went straight from 1.9.4.2 that's why you'll be having most of the trouble you specify.

2. If under the "Available Upgrades" tab is empty then, yes, there are no modules requiring upgrade (actually I think it only checks those modules clever enough to know and interact with the forge, but unless you use really old/quirky modules you should be OK).

3. Probably related to your version jump. Switching to 5.3 is pretty much a requirement these days with CMSMS.

4. Again probably related to your version jump.

Try again now you can get to the in-between versions (you kept a back up of your 1.9.4.2, didn't you?)

Good luck...

[cmsforchurch]

Hey, thanks for the quick response from both of you!

Yes, I had a backup.

I returned to my prior version, and got most of the way through the upgrade to 1.10.3. In step 6 I got this error:
Fatal error: Cannot override final method CMSModule::GetModulePath() in /hermes/waloraweb092/b1559/pow.zumbro/htdocs/modules/Captcha/lib/classes/module/class.captcha.php on line 1048.

Any thoughts on what to do about that?

[Dr.CSS]

Most times if the module doesn't show any newer version in extensions > module manager but give errors etc. during CMSMS upgrade you can rename the modules folder, Capcha~, then upgrade CMSMS then rename the module back to original...

After every CMSMS upgrade check module manager again to see if any need upgrading if so upgrade them, then upgrade CMSMS, rinse, repeat...

[cmsforchurch]

Thanks Dr.CSS! That got version 1.10.3 to complete the install.

I'm back to trying to get version 1.11.7 to install and only get to step 2. When checking permissions and PHP settings, it recommends I switch to php 5.3. But as stated in my initial post, when I switch to php 5.3 and click Try Again in this step, I get:

"Session not working, you have problem with some modules and functionality! Ask your provider, exiting!"

I'm not sure what to do about that error. Or should I go back to php 5.2.17?

[paulbaker]

If you're switching between PHP versions half way through an install I bet the server resets various things and restarts PHP, losing all sessions etc. That's why you get the message.

I would set it to 5.3 (highest version you can) and then restart the upgrade to 1.11.7.

[Jo Morg]

Also, it wouldn't hurt to post the list of modules you are using: there's the possibility of one or more being too old and not working with PHP 5.3.

---

However a word of caution: if you are using any of the modules released by Calguy1000, you will have to make a decision between upgrading PHP (all latest releases of CG modules need 5.3 as a minimum), or using PHP 5.2.x with versions of CG modules still supporting this version (ergo not the latest).

---

I, personally, would upgrade to the latest always, even if I had to drop or replace a few older modules.

[cmsforchurch]

paulbaker, I set my server tp php 5.3. I'm not exactly sure what you meant by restarting the upgrade, so I tried restarting running upgrade.php after swtiching to php 5.3 but still got the same error. So I then tried restarting the upgrade by recopying the CMS Made Simple files over the top of the files on the server then started the upgrade.php process again. Still I got the same error.

So then I thought I would try Jo Morg's suggestion. But first I had to set my installation back to 1.10.3 so I could get my list of modules and system information. I was able to get that running again. Here is my system information after moving it all back to 1.10.3:



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

Cms Version: 1.10.3

Installed Modules:

CMSMailer: 5.2.1
FileManager: 1.4.3
MenuManager: 1.7.7
ModuleManager: 1.5.3
News: 2.12.3
Printing: 1.1.2
Search: 1.7
ThemeManager: 1.1.4
TinyMCE: 2.9.12
FormBuilder: 0.7.3
Captcha: 0.4.6
Gallery: 1.4.4
CGExtensions: 1.31
FrontEndUsers: 1.18.1
CustomContent: 1.8.3
MysqlDump: 1.2.4
CMSPrinting: 1.0
MicroTiny: 1.1.1


Config Information:

php_memory_limit:
process_whole_template: false
output_compression: false
max_upload_size: 1000000
default_upload_permission: 664
url_rewriting: mod_rewrite
page_extension: .html
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.2.17
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 0
memory_limit: 24M
max_execution_time: 300
output_buffering: On
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 10M
upload_max_filesize: 10M
session_save_path: /home/users/web/b1559/pow.zumbro/htdocs/cgi-bin/tmp (0755)
session_use_cookies: On (True)
xml_function: On (True)


Server Information:

Server Api: cgi
Server Db Type: MySQL (mysql)
Server Db Version: 5.0.91


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

I see several of them were developed in part by CalGuy: CG Extensions, CustomContent, FrontEndUsers, MenuManager, MicroTiny NuSoap, and ThemeManager. Any suggestions?

Thanks for looking at this for me.

[paulbaker]

I'm not exactly sure what you meant by restarting the upgrade

Well it sounds like you can upgrade to 1.10.3 OK. So I just meant upgrade from 1.10.3 in the normal way, but after switching to the higher PHP version.

[Jo Morg]

CG Extensions, CustomContent, FrontEndUsers are the ones needing 5.3, if you want the latest versions of these. All the others are core modules (Calguy1000 being part of the core Developer Team ).
Now, I would bet that the site would work with 1.10.3 already on PHP 5.3.
If it does, try (after set to 5.3) upgrading all modules (non core) to the latest versions, taking care to upgrade according with dependencies (dependents later, as obvious), and upgrading CMSMS next.

[cmsforchurch]

Jo Morg, you are right, my 1.10.3 now works with php 5.3.

You suggest I upgrade all my non core modules. How do I do that? When I use upgrade manage, it says there are no newer modules available in the repository. So does that mean I already have the latest versions?

[Jo Morg]

When I use upgrade manage, it says there are no newer modules available in the repository. So does that mean I already have the latest versions?

If on Module Manager there are no upgrades listed, and assuming that it can reach the repository server, then you probably have all modules up to date.

So, being this a checkpoint on the upgrade process, clear cache and backup at this point.
As long as there are no pendent issues (like the use of deprecated tags, {stylesheet} being one; not too good Smarty syntax; UDT's that may not be PHP 5.3 ready;) you should be clear to upgrade to the latest CMSMS version. At least, if something goes wrong, it has to do with this final step, and easier to debug.

[cmsforchurch]

I cleared the cache, did a backup, then tried the install. As soon as I start the install, I get:

Session not working, you have problem with some modules and functionality! Ask your provider, exiting!

[cmsforchurch]

OK, now I see where I had a {stylesheet} tag in one of my templates. It took me awhile to find where the documentation is for the tags. I'll go through my templates and see what other tags I have that I need to replace.