v5.6.3.3 installed. Is there a compelling reason to upgrade?
Permalink
I have v5.6.3.3 installed after a big effort in January.
It was really a kind of upgrade horror (user error and upgrade path not clear)
Through repetition I believe my routine is improved, but I don't wish to get into that same problem this time.
Is there a compelling reason to upgrade to v5.7?
What would the advantages and disadvantages be?
If I should upgrade, which version should I go to?
Will any essential features be missing?
Can I do this in one step or what specific versions should I step through?
Also what are the likely problems I will face during the upgrade?
It is a pretty simple CMS website with about 4 plugins.
I am sorry, I have not been following all the developments, however many thanks to the team.
It was really a kind of upgrade horror (user error and upgrade path not clear)
Through repetition I believe my routine is improved, but I don't wish to get into that same problem this time.
Is there a compelling reason to upgrade to v5.7?
What would the advantages and disadvantages be?
If I should upgrade, which version should I go to?
Will any essential features be missing?
Can I do this in one step or what specific versions should I step through?
Also what are the likely problems I will face during the upgrade?
It is a pretty simple CMS website with about 4 plugins.
I am sorry, I have not been following all the developments, however many thanks to the team.
I did upgrade! Via a weird route admittedly (installing Wordpress on the site then Concrete 5.7).
now I am locked out and cannot get into my site
error message :
Call to undefined method Concrete\Core\Page\View\PageView::disableEditing()
I tried the emergency permission disable function as seen on
http://www.concrete5.org/documentation/developers/5.7/installation/... and that just gave me the text of the concrete.php file created - several times repeated on the browser.
Any other suggestions please?
now I am locked out and cannot get into my site
error message :
Call to undefined method Concrete\Core\Page\View\PageView::disableEditing()
I tried the emergency permission disable function as seen on
http://www.concrete5.org/documentation/developers/5.7/installation/... and that just gave me the text of the concrete.php file created - several times repeated on the browser.
Any other suggestions please?
What version are you updating from and what version are you updating to?
thank you for your reply : 5.6.3 to 5.7.4.2
There is no way to upgrade a 5.6.x (version 6) site to 5.7.x (version 7) https://www.concrete5.org/index.php?cID=710973...
If you wish to use 5.7.x you will need to create a new site from scratch.
I hope you made a backup of your 5.6.x files you can restore, or just download 5.6.3.3 again and restore the 'concrete' folder from that.
If you wish to use 5.7.x you will need to create a new site from scratch.
I hope you made a backup of your 5.6.x files you can restore, or just download 5.6.3.3 again and restore the 'concrete' folder from that.
Honestly, I would not recommend an upgrade to 5.7.x. In my test area, it appears to be full of bugs. I also had installed it on a customer’s website at a different web hoster, and I could not even edit blocks without failures. I had to delete it and reinstall 5.6.
There is still no database backup (version 5.7.4.2) like in 5.6, so you’d have to find another way to backup your database.
There is still no database backup (version 5.7.4.2) like in 5.6, so you’d have to find another way to backup your database.
Perhaps you'd like to report those bugs in the bug tracker as 5.7 installs just great everywhere i've seen it, including the budget host installers softaculous and mojo marketplace.
I cannot remember those issues I ran into, but in the meantime (concrete5.7.5.x) I am happy again with concrete5.
So, today I would recommend upgrading to 5.7, if the website is not too extensive. In my opinion, the new concrete5 has become more user friendly. The Composer has become more intuitive, so that blogging is more fun than before.
So, today I would recommend upgrading to 5.7, if the website is not too extensive. In my opinion, the new concrete5 has become more user friendly. The Composer has become more intuitive, so that blogging is more fun than before.
I don't think statements like this are helpful, let alone accurate. What the heck does "In my test area" mean? The core team has done a fantastic job of squashing bugs, and the latest release is solid, with another big update almost ready for release (v. 5.7.5 )
You mention version 7.4.2 later after your vague "In my test area" reference, but look at all the releases and release notes since...
5.7.5 Release Notes
5.7.4.2 Release Notes
5.7.4.1 Release Notes
5.7.4 Release Notes
5.7.3.1 Release Notes
5.7.3 Release Notes
5.7.2.1 Release Notes
While in this particular case I too might suggest to the original poster that he not upgrade (there is no upgrade), your reasoning seems clearly outdated.
You mention version 7.4.2 later after your vague "In my test area" reference, but look at all the releases and release notes since...
5.7.5 Release Notes
5.7.4.2 Release Notes
5.7.4.1 Release Notes
5.7.4 Release Notes
5.7.3.1 Release Notes
5.7.3 Release Notes
5.7.2.1 Release Notes
While in this particular case I too might suggest to the original poster that he not upgrade (there is no upgrade), your reasoning seems clearly outdated.
+ 1
5.7.4 is a stable version if you ask me. Been following development ever since the first .7 version, and build quite a few websites on 5.7.4 since it's release (upgraded to 5.7.4.2). I never look back (5.6) anymore, nor should others when they have switched. It's a big step to take perhaps for some who don't know what to expect, but codewise it's a mile ahead. It's up to coding standards and you get to use composer, yey!
Just my 2 cents.
5.7.4 is a stable version if you ask me. Been following development ever since the first .7 version, and build quite a few websites on 5.7.4 since it's release (upgraded to 5.7.4.2). I never look back (5.6) anymore, nor should others when they have switched. It's a big step to take perhaps for some who don't know what to expect, but codewise it's a mile ahead. It's up to coding standards and you get to use composer, yey!
Just my 2 cents.
In my test area means that I had installed concrete5 on a web hoster’s server which I test content management systems on.
I agree with you that I should have been more specific, but anyway, in the meantime the issues I ran into have disappeared. And yes, the developers are doing a good work of course. I have been a concrete5 fan since years.
I agree with you that I should have been more specific, but anyway, in the meantime the issues I ran into have disappeared. And yes, the developers are doing a good work of course. I have been a concrete5 fan since years.
Thanks for posting the update and clarification.
I think anyone who has benefited from Concrete5 at any point and wants an even better Concrete5 moving forward should remember when they are posting that others who have never used Concrete5 before come here evaluating, and it's easy for them to take negative posts "out of context" so-to-speak if we're not careful.
Of course becoming more of the solution by contributing in whatever way you can, rather than just complaining, would be a good thing too.
I think anyone who has benefited from Concrete5 at any point and wants an even better Concrete5 moving forward should remember when they are posting that others who have never used Concrete5 before come here evaluating, and it's easy for them to take negative posts "out of context" so-to-speak if we're not careful.
Of course becoming more of the solution by contributing in whatever way you can, rather than just complaining, would be a good thing too.
Absolutely, yes. In the five years of being a community member, not only have I found useful solutions, but could help some other users (take a look at my profile). Anyway, you are right, sometimes I appear a bit negative. I am sorry for that.
No problem. I wasn't even "speaking" directly to you in most of my last response. It can happen to the best of us, especially when we're in the midst of dealing with something frustrating (which we call know comes with the territory).
It depends what those 4 plugins are and how reliant your site is on them. It also depends on what theme you are using; whether the creator has made a 5.7 version, or if you made it yourself you will have to port it over (very easy to do generally).
There is (currently) no way to press a button and upgrade a concrete5 v5.6 site to concrete5 5.7 like in previous versions, you would have to start a new 5.7 site (use the latest release).
Due to the way Concrete5 versions are named, 5.6 is actually version 6 and 5.7 is version 7. You may have known that already but it never hurts to explain for future readers.