CMS Made Simple Forums

Hello all,

I'd like to upgrade my 1.1 installation to the latest 1.1.2.
I would like to know if it is possible to upgrade by juste uploading the diff files, or should I redo a complete installation?
Is it necessary to call ./cmsms/install/upgrade.php  to alter database?

Thanks.

1) Yes, there is a diff from 1.1 to 1.1.2 directly
2) If there was a database schema upgrade, you'd be directed to the upgrade routine each time
    you attempted to access the site.... until such time as the upgrade is done.

But...
with 1.1 to 1.1.2, there's no schema change.

Thanks for your quick answer

C U soon

Hey,
just want to let you know I've already installed it and am already reverting it... 
After the first refresh, all my menu styles were messed up, there is no continuity in the styles generated by the menu manager and that's really too bad because it is very very time-consuming (at least for me) to setup a perfect CSS.
I really don't want to get into that again...

You tell me I could only revert the menu manager, but since I see the lack of continuity in that module, I don't want to take the risk to have other unexpected issues.

I think this goes along with ted's frustration.
I cannot really understand why improvements on the core or modules impacts the generated pages and I hope the I/O of core and modules will be set up once and for all so that users don't have to do debug/development after upgrading their installation.

That's really strange.... The menu manager wasn't touched from version 1.1 to version 1.1.2.... infact, probably (without looking) the only one that was touched was News).

I upgraded from a virgin site from 1.1 to 1.1.2 Friday without any difficulty.
I can't see what would cause the problem when upgrading from 1.1.1 to 1.1.2

As another point.

With any upgrading comes risk.  Risk that bugs may be introduced, Risk that bugs you relied on may be fixed... .Risks that new functionality may break old functionality, and 'gasp' require you to do something.  All kinds of risks.

We do take the effort to try to make things somewhat backward compatible, and we try to make things so that they'll upgrade well.  But errors do happen.

[edit]
Not upgrading also has risks.... Risks that you're sitting there with security flaws that you haven't fixed yet.  Risk that the version X fixes problems you have.  Risk that you may not be able to get support any more for your old version of the product.  All kinds of risks.

It's a catch 22 situation.  To upgrade, or not to upgrade.  The only real solution is to become part of the team, to join the group, express your concerns, test fixes on a development site, contribute suggestions, and put in the same amount of effort that alot of other people do for free.

This situation exists wether the software is commerical or GPL.  I've regularly seen instances where hundreds of hours worth of work were generated just because Microsoft released a new version of SQL server, or some other package.  There is no avoiding it.  With CMS Made Simple, Linux, apache, and PHP, at lest you get the software for free.  No matter which way you look at it, it still costs time.
[/edit]

Are you on the testing team? or the Support Team?  Did you spend hours of your free evenings or weekends trying the best that you can to make everything work?  did you test this release on a staging site before uploading to a production site?  If your answer to any of the questions in this paragraph is 'No'.... then you probably have more responsibility than  the rest of us do, if an upgrade fails.

Are you on the testing team? or the Support Team?

No

Did you spend hours of your free evenings or weekends trying the best that you can to make everything work?

Not for the CMS itself but trying to understand CMSMS and building my new site, oh yes... I'm working on the new site for months and the wapcam project is not my regular job.

did you test this release on a staging site before uploading to a production site?

Of course I did, and I'm glad I did because reverting got into a nightmare as the News wouldn't work (amongst others). and I finally dumped the whole site and db back.

I hope you didn't take my remark for a personnal attack or even an attack, it's far from being my point. My point was more about relating my experience and let you do the best of it. I have questions and I'm just trying to understand what is going on.
i totally agree that not upgrading as well as upgrading is a risk. I just thought that, seen the versioning number, 1.1.2 would be more about correcting issues and stabilizing the CMS than adding features and breaking backward compatibility.

The only real solution is to become part of the team, to join the group, express your concerns, test fixes on a development site, contribute suggestions, and put in the same amount of effort that alot of other people do for free.

I'd like to because I really like the CMSMS project. However, I'm already putting all my free time on another project that gives me little time to contribute elsewhere.
As you may have noticed, I'm trying to bring contribution where I can (such as the 20cts-worth UDT I posted for changing language with flags) but again I'm not a php dev.
I could also hack the CMSMS code for my own purpose without letting anyone know. I prefer to write my remarks as I consider they are constructive ones and would only benefit the project. I apologize if sometimes, my english let you think I'm criticizing your work without any regard to it.

If CMSMS ever needed mobile software (my competence field), I would contribute much more actively. Unfortunatly, this has little to see with a CMS. Now all I can offer (for now) is my skills in development to relate and analyze issues I encounter.

Now I want to make sth clear: I know (probably more than many) how much time the team is giving for the project. I thank you all for that and wish you keep up the good work.