Why we have stopped using CMSMS
Posted: Mon Oct 16, 2017 7:28 am
We love building websites with CMSMS, but there are a few things that has forced us to the change content management system we use. Why I wrote this message? Because we would like to use CMSMS, ‘cause it used to be the best option and the template system is still just great. So what’s wrong?
Update process is really a slow process and you have to do it manually which easily leads to mistakes. This should be automatic nowadays. Period.
Quality of the updates. Especially version 2 and it updates are really buggy. We have problems at least one of our sites EVERY update sequence. Sometimes it’s a module but mostly it’s the core. We have the same amount of Wordpress sites and we use automatic updates. No problems. It isn’t fair to compare to Wordpress, but maybe it is. Our customers don’t understand why they should pay more for upgrading CMSMS. And we wouldn’t like to use Wordpress ‘cause it’s just evil
We are web developers and we don’t won’t to use our time solving technical server issues, but with CMSMS we are forced to do so.
And if you add a quite high frequency of the updates… well. We try to make business. It’s not a hobby for us.
A quite minor, but still… Support from the dev. Mostly we (I mean the whole community) get good support, but some of the devs are not polite. Most are and thanks for that! For example posts get locked/moved/deleted without warning/notice or information. Some of the posts/bug reports are closed and ingored just by saying “Not enough information” or “Works for me”. Excuse me?
I think that you should listen your clients more. The web developers who actually build sites for customers. For example no image roller when 2.0 was released, GCBs where deleted, Design manager is/was a mess from UI/UX point of view, everything seems to go more technical when the trend is to go more simplier.
Yes – I’m frustrated and this message maybe a bit harsh, but the main point really is to help building a better CMS and not just leave. Thanks for the good work and hopefully you have the power to make CMSMS even better, more competitive and simple again.
BR
Tommi (CMSMS user from the 2009)
Update process is really a slow process and you have to do it manually which easily leads to mistakes. This should be automatic nowadays. Period.
Quality of the updates. Especially version 2 and it updates are really buggy. We have problems at least one of our sites EVERY update sequence. Sometimes it’s a module but mostly it’s the core. We have the same amount of Wordpress sites and we use automatic updates. No problems. It isn’t fair to compare to Wordpress, but maybe it is. Our customers don’t understand why they should pay more for upgrading CMSMS. And we wouldn’t like to use Wordpress ‘cause it’s just evil
We are web developers and we don’t won’t to use our time solving technical server issues, but with CMSMS we are forced to do so.
And if you add a quite high frequency of the updates… well. We try to make business. It’s not a hobby for us.
A quite minor, but still… Support from the dev. Mostly we (I mean the whole community) get good support, but some of the devs are not polite. Most are and thanks for that! For example posts get locked/moved/deleted without warning/notice or information. Some of the posts/bug reports are closed and ingored just by saying “Not enough information” or “Works for me”. Excuse me?
I think that you should listen your clients more. The web developers who actually build sites for customers. For example no image roller when 2.0 was released, GCBs where deleted, Design manager is/was a mess from UI/UX point of view, everything seems to go more technical when the trend is to go more simplier.
Yes – I’m frustrated and this message maybe a bit harsh, but the main point really is to help building a better CMS and not just leave. Thanks for the good work and hopefully you have the power to make CMSMS even better, more competitive and simple again.
BR
Tommi (CMSMS user from the 2009)