CMS Made Simple Forums

How can I find out, that the module isn't update to 1.10?

You can't actually, but a good reference is when a module produced a new file after 22-10-2011 it's probably updated to work with 1.10.x.

you can also take a look at the changelog or at the release notes for the module in the forge... This is a good place to store that information by developers... But unfortunately not all the devs use to do this good practice!
The solution is: test, test, and test again in local and production server too.

Thanks to developer team for TinyMCE-2.9.4 working fine on 1.10.1 new installation !

My main reason for wanting to upgrade is that some modules won't upgrade in 1.9.4.3 (e.g. formbuilder 0.6.4 -> 0.7) I assume that this is a memory problem and that it might work better with the new module manager. How badly are things likely to break if I do the upgrade without the "upgrade all modules" step?

Most probably (read: for sure) the upgrade process will fail at step 6, because of the modules incompatibility (most common situation, as far as I could see from these questions).

But you can try on a "dummy" website - that is, make a working copy of your website and test everything on it. If it goes well, then go live.

okay - is there any alternative way to upgrade modules (e.g. via FTP or a TGZ file - or do most modules also have an install script which needs to be run?)

I do it via FTP (don't like to use Module Manager).

Usually I just overwrite existing module files. Than I go to Extensions -> Modules and if the script running is necessary, it is indicated in the 'Status' column. It says something like 'Needs upgrade', or something similar. Just click on that link and everything is done automatically.

seregarem wrote:How can I find out, that the module isn't update to 1.10?

I made a list of 1.10+ tested modules in the Dutch announcement board: http://forum.cmsmadesimple.org/viewtopi ... 35#p265635

Hi I'm wondering if you can help, i have copied across the files to our webserver to CMSMS to version 1.10.1 after some Hosting issues. Since the copy i cant run the install/upgrade.php or access my home page nor can i access the admin page.

I was on a realy old version, 1.2.2, upgraded to 1.5.4 to 1.9.1 to 1.9.4.3 then to 1.10.1

Any ideas any one?

AdamOwen123, please stick to your own topic at http://forum.cmsmadesimple.org/viewtopi ... =7&t=58024

It's not easy to help people if they spam their issues all over this forum

I upgraded from 1.9.4.3 to 1.10.1, upgrade.php deleted some modules from the modules directory, including Printing. But it did not delete Printing row from the modules table, other deleted modules were deleted from there too. Can I safely delete that row or is there references to it in other tables?

help: after upgrading all modules (except TinyMCE) I upgraded from 1.9.4.3 to 1.10.2 via shell, fixed ownership and permissions, but now everything on the site is giving a 500 error.
I haven't been able to find anything in error logs, however.

[update] I'm pleased to say that restoring from backup brought the site back online as 1.9.4.3 (FTP of 5000 small files wasn't the smartest way to do that though!)
I wasn't able to verify against a corrupted download via checksums, since I couldn't run the installer.

As a general word of advice, the latest versions of some modules (FEUsers and Formbuilder that I know of) do not work with versions prior to 1.10.0.
So, leave them to last when upgrading modules, take your final backup, then upgrade them and upgrade CMSMS. That way, if you have to revert to your backup, forms and FE logins will still work.

If people know of other modules which are not backward-compatible, please list them

aateck wrote:Upgrading from 1.9.4.3 to 1.10.2 te Upgrade HALT on step 6 and write this message:

Code: Select all

atal error: Cannot override final method CMSModule::Lang() in /homez.40/capviepa/www/modules/ConfigGUI/ConfigGUI.module.php on line 216

My language if French from France!
How terminate the Upgrade?

If I remember, ConfigGUI is an old module used in very old versions and no longer needed/compatible.
Looking at your error message you could try to manually remove module files via ftp and then rerun the upgrade process, but that may not work properly.
Your best chance is to restore your backups, remove the ConfigGui module, backup files again, then upgrade.