CMS Made Simple Forums

this may seem like a stupid question, but should I just ftp the files to the server and overwrite the existing ones, then run the installer?

Hello,

please have a look at the "doc" folder of the package you have downloaded. There are interesting files inside : README, INSTALL, UPGRADE, htaccess...
The online documentation may help too.
Backup (database and folders) is your friend. Clearing the cache before upgrading is an idea too.

Pierre M.

I had the same questions and although I -did- read the docs, I still had some issues.

I did not have any luck ftp'ing over my existing installation. My ftp client kept complaining that directories could not be renamed which means it was using mv command instead of cp command I guess. I'm no Unix brainiac so this was baffling to me.

Ultimately I figured out how to use the terminal and issued a couple Unix command which recursively copied and overwrote the files in my cmsms installation that needed to be upgraded. See this thread for the detials...
http://forum.cmsmadesimple.org/index.ph ... 567.0.html

I do not think this upgrade process is very easy for non-techies. It would be much easier if you could upgrade from within the admin somehow. It is frustrating to have to continually ask for assistance for something that is so "easy" for the developers and more expert types to understand.

Michael

thanks.

It's not very hard once you get used to it, and it does force you to think about backups.

That being said, I wonder if something could/should be built along the lines of the current module manager, where you could upgrade from within the admin section by having an upgrade link trigger the overwriting and upgrading of the core in a method similar to how various modules are updated.

cnymike wrote: I do not think this upgrade process is very easy for non-techies. It would be much easier if you could upgrade from within the admin somehow. It is frustrating to have to continually ask for assistance for something that is so "easy" for the developers and more expert types to understand.

Michael

Michael has a point.
And if not integrated in the admin panel, the upgrade process could at least be "redocumented for non-techies", couldn't it ?
One more FR for 2.0

Pierre M.

Concerning redocumentation, it wouldn't be too hard to present several different scenarios in which a person could initiate an upgrade. We've nearly documented one way just in this thread. right?

Admittedly there are many ways in which users install this cms. Some run their own servers, others used shared servers, etc. But certainly the vast majority of installations could be covered by several well-documented methods I think.

For me, the best solution would be a Module-like install process.

documentation is free for everybody to update (its wiki afterall) if the README files have some strange stuff, please file a bug or even better, a patch.

for the admin upgrade stuff, its not as easy as it sounds. it wont work with most isps (safemode, php running as nobody and so on)