Having developed sites with both WordPress and Drupal, I have to say that this one area where Drupal falls behind. I prefer Drupal as a flexible, extensible CMS that has more power out-of-the-box than anything else available. However, when I develop Drupal sites for a client, there are always two key complaints:
Site users and administrators who are not experienced with Drupal find it difficult to use.
Upgrading modules is a hassle for site admins who are not experienced with Drupal.
Both of these serve as significant barriers to organizations choosing Drupal for their CMS needs.
Problem one is something that needs to be addressed through usability testing and a renewed focus on the end-user experience. This requires something of a cultural change in terms of how Drupal developers approach a problem. That change is starting to happen, but it will take a long time before Drupal is as intuitive to use as something like WordPress (granted that part of the reason Drupal is more difficult to use is because it has more options, more power, more features, and more flexibility.)
Problem two is much easier to address because it can be fixed by writing some code. If the Drupal community can find a way to simplify the upgrade process securely then Drupal becomes a much more viable choice for a lot of organizations looking for a CMS that is powerful but easy to use.
I completely agree with this. This would make the process very seamless. Once the security side of it is thought through then it will be a great addition to Drupal. Bring on Drupal 7.
This is going to be written during the Summer of Code for Drupal. In a secure fashion, of course... because if your Apache can write your PHP files that's a security weakness we want to avoid.
Hi again chris,
Just wanted to update the situation. Google maps for thailand now has eng labels along with thai http://www.sajalkayan.com/google-maps-for-thailand-now-speaks-english.html
I just started work on my portal last month after discovering Drupal lets hope now with Google map support I can make it into a useful resource for confused tourists.
I am not trashing nor complaining. I was pointing out the feeling that this release is being push through with more haste than in the past, and I feel uncomfortable about it. This worry might be unfound as there are many peoples working full time on Drupal now, but it is new and untested to me.
I suggest you stop complaining about every and all negative comments being published. I have blog about Drupal since 2004, mostly good things. If you can't take negative comments, or feel that the general users might be too dumb to find out for themselves and got scared away from adopting Drupal, don't waste your time here.
@Chris - We are dealing with release candidates right now. I wouldn't recommend taking your site to drupal 6 unless you know what you are doing or want to do some testing. There won't be a final release until it's ready.
But, I would really recommend not trashing on or complaining about a system that hasn't had a final release because of critical issues. The next time you post people will think twice about what you say because of what you wrote before. Sometimes it's better to bite your tongue when you get frustrated.
"working full time job and taking care of a few live sites not relating to the job"
Me too. But I'd rather spend my time fixing the bugs than blogging about them.
My stance stems from my unfortunate situation, working full time job and taking care of a few live sites not relating to the job. I’m scared of things going wrong, especially when it happens at 10am on a Monday.
Pasqualle,
Thanks for pointing that out. “Release when it’s ready” has served Drupal well in the almost 4 years I’ve been using the platform. I just feel RC4 is not quite ready enough when so many issues were still found in the 9 days since RC3. This might not prevents D6 release after RC4, but it will certainly keeps me away for the reason I mentioned above in reply to greggles.
You are making a wrong conclusion. There is a difference between 2 critical bugs exist and 2 critical bug added to the list. There is only 1 new critical, and as I see it isn’t a new bug. So nothing prevents us to release D6 final after RC4.
In fact, every version of Drupal has “critical” issues. While the two you point out are bad, there are always bad ones lurking deep in the code. Holding back for fear of critical issues means no software would ever be released.
Having developed sites with both WordPress and Drupal, I have to say that this one area where Drupal falls behind. I prefer Drupal as a flexible, extensible CMS that has more power out-of-the-box than anything else available. However, when I develop Drupal sites for a client, there are always two key complaints:
Both of these serve as significant barriers to organizations choosing Drupal for their CMS needs.
Problem one is something that needs to be addressed through usability testing and a renewed focus on the end-user experience. This requires something of a cultural change in terms of how Drupal developers approach a problem. That change is starting to happen, but it will take a long time before Drupal is as intuitive to use as something like WordPress (granted that part of the reason Drupal is more difficult to use is because it has more options, more power, more features, and more flexibility.)
Problem two is much easier to address because it can be fixed by writing some code. If the Drupal community can find a way to simplify the upgrade process securely then Drupal becomes a much more viable choice for a lot of organizations looking for a CMS that is powerful but easy to use.
I completely agree with this. This would make the process very seamless. Once the security side of it is thought through then it will be a great addition to Drupal. Bring on Drupal 7.
There is the drush module (http://drupal.org/project/drush) and drush module manager (http://drupal.org/project/drush_mm). Those are command line oriented but I don't think it would be much work to slap an interface on them.
I think they will use ftp among other file access systems. This way you have control of file access , ownership and execution of code.
Totally agree with
... if your Apache can write your PHP files that's a security weakness ...
Think that is the main reason for not doing such thing.
This is going to be written during the Summer of Code for Drupal. In a secure fashion, of course... because if your Apache can write your PHP files that's a security weakness we want to avoid.
nice littly pussy.. i meant kitten..
come to think of it, there's a 5-year-old cat running around in my house and i have no idea where its toilet is.. this is rather worrying.
stupid show!
ขอบคุณครับ ผมชอบใจ MapJack จริงๆ
พึ่งได้ยินชื่อ INSEAD มาเร็วๆ นี้ที่ presentation ของ Bain
ดูเหมือนบริษัท management consulting พวกนี้จะกลืนกินโลกเขาไปเสียแล้ว
มันกลายเป็น institute มากกว่าที่จะเป็น company ไปแล้ว
ขายฝันให้ CEO แล้วยังขายฝันให้คนทำงานในบริษัทเองด้วย
วาดภาพชีวิตได้ซะสวยหรู คือถ้าเองเข้าได้ ทางชีวิตของเองก็เตรียมไว้ให้เรียบร้อยแล้ว
คนธรรมดาที่ไม่ได้ยอดมนุษย์อย่างเราก็ฝันนนนนน~~~~
You job title looks fantastic.
new theme!
I'm one of them.
Btw, what is consulting?
Shit. That's all the answer I did in interview.
ผมกำลังเริ่มศึกษา้ LaTeX เพื่อเขียนวิทยาพนธ์ครับ อ่าน web นี้แล้วเข้าใจเกี่ยวกับ LaTex เพิ่มขึ้นเยอะมาก
เหมาะสำหรับมือใหม่อย่างผม ขอบคุณมากครับกับความรู้ที่สะสมและเผยแผ่ให้
Hi again chris,
Just wanted to update the situation. Google maps for thailand now has eng labels along with thai http://www.sajalkayan.com/google-maps-for-thailand-now-speaks-english.html
I just started work on my portal last month after discovering Drupal lets hope now with Google map support I can make it into a useful resource for confused tourists.
Truly fantastic and oh-so-thai.
You have to wonder what was going through their head as they posted the flyer. Nothing, one must assume.
wow, this "child of the nature" is awsome!
I am not trashing nor complaining. I was pointing out the feeling that this release is being push through with more haste than in the past, and I feel uncomfortable about it. This worry might be unfound as there are many peoples working full time on Drupal now, but it is new and untested to me.
I suggest you stop complaining about every and all negative comments being published. I have blog about Drupal since 2004, mostly good things. If you can't take negative comments, or feel that the general users might be too dumb to find out for themselves and got scared away from adopting Drupal, don't waste your time here.
@Chris - We are dealing with release candidates right now. I wouldn't recommend taking your site to drupal 6 unless you know what you are doing or want to do some testing. There won't be a final release until it's ready.
But, I would really recommend not trashing on or complaining about a system that hasn't had a final release because of critical issues. The next time you post people will think twice about what you say because of what you wrote before. Sometimes it's better to bite your tongue when you get frustrated.
"working full time job and taking care of a few live sites not relating to the job"
Me too. But I'd rather spend my time fixing the bugs than blogging about them.
Hi greggles,
My stance stems from my unfortunate situation, working full time job and taking care of a few live sites not relating to the job. I’m scared of things going wrong, especially when it happens at 10am on a Monday.
Pasqualle,
Thanks for pointing that out. “Release when it’s ready” has served Drupal well in the almost 4 years I’ve been using the platform. I just feel RC4 is not quite ready enough when so many issues were still found in the 9 days since RC3. This might not prevents D6 release after RC4, but it will certainly keeps me away for the reason I mentioned above in reply to greggles.
I’m quite surprised everytime when reading drupal planet and see your name.
You are making a wrong conclusion. There is a difference between 2 critical bugs exist and 2 critical bug added to the list. There is only 1 new critical, and as I see it isn’t a new bug. So nothing prevents us to release D6 final after RC4.
In fact, every version of Drupal has “critical” issues. While the two you point out are bad, there are always bad ones lurking deep in the code. Holding back for fear of critical issues means no software would ever be released.
Note well the message from Bugzilla when your query returns no bugs… http://en.wikipedia.org/wiki/Zarro_boogs