How safe is a 5.5.2.1 upgrade?

Permalink
Hi,

My background is that I started with an old version of C5 about 2 months ago. 5.4.x I think. Helping a friend and took a chance on this unknown CMS to me at the time.

I learned the ropes, updated that version to 5.5.1 I think, then, after I got the hang of it, and something quirky happened. Thought to start fresh.

I backed up what I could and then downloaded and installed a clean version of 5.5.0 (the most stable version at the time).

Then, I ran into some bugs where I couldn't delete a page attribute, so, I took a chance and upgraded to 5.5.2.

I had a few quirky things happen. Header looked off, font issues and some other things. With help I got it corrected.


After so many version changes, I forgot what version I was running, so I went to --> the Dashboard, "Update concrete5" (that's the only way I know how to find the version #).

And there I see there is even a NEWer version: 5.5.2.1.

So, I have a few questions:


1. how safe is that to upgrade to from an upgraded version as mentioned above? I don't want chase around new problems with a new version.

2. Can I go back (painlessly) if there is a quirky thing or set of quirky things that I don't like?

3. When I log in, I see a "checking for updates" - why am I not notified of that 5.5.2.1 update there?

 
Ekko replied on at Permalink Reply
Ekko
Before I would consider upgrading I would make sure the update offered something new, and useful to your site. If your site is doing fine now, and there is no difference than upgrading may be an entirely pointless effort. I have a few 5.4.1 floating around, and I have no intention of upgrading them until it becomes necessary in a future redesign, which for the forseeable future is not the case, as they are working fine as is, and still look modern.

As for safety it should be fairly straight forward, but I would still read a few threads on possible problems, and I would make sure to have a backup just in case. I am fairly certain you can roll back just as easily as rolling forward, and have read several threads of people doing exactly that with no issues.
frz replied on at Permalink Reply
frz
1) 5.5.2.1 just fixes a few of the annoying bugs in 5.5.2. Thus the
point release (the dot one). Upgrading from 5.5.2 should be easy and
painless.

2) You should always backup your database and any custom files before
running any concrete5 install. There's no magic undo button but
everything is undoable if you prepare first.

3) These update checks sometimes take a couple days to trip, its
possible yours just hasn't - depends on where/how you're hosting, etc.

If you've already made it through the dramatic interface changes from
5.4 to 5.5 - you should go ahead and get to the latest 5.5.2.1. We
don't expect to release another new version for months and it will be
a dramatic rethink of advanced permissions, which will likely mean a
few close releases ending in a point release like this one.

best wishes

Franz Maruna
CEO - concrete5.org
http://about.me/frz
PineCreativeLabs replied on at Permalink Reply
PineCreativeLabs
I just tried upgrading a client's site from 5.5.1 straight to 5.5.2.1 - epic fail! They are hosted with GoDaddy (which sucks) and afer trying to download the newest version (which showed as 5.5.2.1), it crashed and showed errors. I figured it was because of GoDaddy's limitations, it didn't download everything.

Not all folders from the concrete folder in 5.5.2.1 was there when I checked, so I uploaded the rest. It then showed a different error:

Warning: require_once(/home/content/53/7934353/html/updates/concrete5.5.2.1/concrete/config/../libraries/loader.php) [function.require-once]: failed to open stream: No such file or directory in /home/content/53/7934353/html/updates/concrete5.5.2.1/concrete/config/base.php on line 532
Fatal error: require_once() [function.require]: Failed opening required '/home/content/53/7934353/html/updates/concrete5.5.2.1/concrete/config/../libraries/loader.php' (include_path='/var/chroot/home/content/53/7934353/html/libraries/3rdparty:/home/content/53/7934353/html/updates/concrete5.5.2.1/concrete/config/../libraries/3rdparty:.:/usr/local/php5/lib/php') in /home/content/53/7934353/html/updates/concrete5.5.2.1/concrete/config/base.php on line 532


What I'm now wondering, is it possible simply to replace the ROOT concrete folder with the one in 5.5.2.1? Will that work?

Yes, I did backup the site first before all this.
PineCreativeLabs replied on at Permalink Reply
PineCreativeLabs
Nevermind - I got it. I simply replace the root concrete folder with the latest one, as well as the root config folder. Then I did a fresh install on a new database, and was able to restore everything from the backed up database.

Must say - very impressed with the backup tools and how fast it restores stuff!
MattWaters replied on at Permalink Reply
MattWaters
Here's a newly minted documentation page on what version numbers mean:

http://www.concrete5.org/documentation/general-topics/version-numbe...