Comments on: Drupal. PITA. Avoid.

By: Juzar

Juzar — Thu, 20 Aug 2009 05:32:46 +0000

Any one worked (or trying to work) with “Drupal E-commerce ” ?

http://www.drupalecommerce.org

By: Chris

Chris — Wed, 18 Mar 2009 05:44:07 +0000

Sorry to hear you were to lazy to read the documentation properly. Also Drupal isn’t a CMS it’s a framework.

By: shyam

shyam — Wed, 18 Mar 2009 03:59:58 +0000

I can understand Drupal being difficult for you. It has a very very steep learning curve and the admin interface is something only geeks can love. Dries & the community will get that fixed by the time Drupal 7 is out as the stable release, but as far as the current state of affairs go, it is a hard beast to master.

WYSIWYG is also a major drawback, it should not be that difficult to work, but you can use the TinyTinyMce module, which works pretty much out of the box. Though you have to keep in mind, the future for the feature is through the WYSIWYG API. But this works currently and does not require any jumping around hoops.

Drupal has its own way of doing things, including the messy way of upgrading it and the modules. But there is a reason why it works that way, because it is a framework and not a CMS. You can use it to build a CMS, but it is not a CMS out of the box. Once you are comfortable with it (wait till you start hacking page.tpl.php), it can do a lot of things that other products really struggle to do. But it is crucial that you spend time learning and understanding it, else it will lead to experiences like this.

By: Vimal George

Vimal George — Mon, 09 Mar 2009 04:45:47 +0000

*yawn*
the author seems to think CMS=wordpress. (this is not an ad-hominem attack. Just a nagging sensation of bad taste.)

Drupal is the King of hackability as far as CMSes go. You can integrate it with anything including the Kitchen sink. And the community is rock-solid. I can hardly agree with any of the points listed above in the post other than the arcane terminology in the admin page that seems like something a druid would use; the first few times you work with it.

And why bitch about a particular blogging tool’s integration? XMLrpc works the same everywhere. http://www.google.com/search?hl=en&rls=en&hs=RaX&q=drupal+windows+live+writer&btnG=Search
DISCLAIMER: I run multiple Drupal installations on production for a living. So God help me…

By: Sathya

Sathya — Thu, 05 Mar 2009 21:34:14 +0000

Nice detailed post by Manan

By: Rod G

Rod G — Tue, 03 Mar 2009 19:20:42 +0000

I know what you mean about it being a tough idiom to adjust to. However, the comment on unhelpful community surprises me– I’ve found just the opposite and have received help from basic installs to advanced configuration and also on graphic design (themeing) and how to price services.

Here in NYC (not known as a friendly town, eh?) we have an awesome Drupal community that meets monthly at Mansueto Ventures (http://groups.drupal.org/nyc).

Why Drupal and not WordPress though? For me it’s because Drupal does more than just blogging. This may be an unfair characterization, I switched in 2005 and WP has surely advanced since then. But personally, I see really creative stuff happening in Drupal, recovery.gov and myplay.com being two good examples.

By: ankita

ankita — Tue, 03 Mar 2009 13:59:55 +0000

i m neutral
find both of them complicated

By: Peter

Peter — Mon, 02 Mar 2009 18:45:16 +0000

It sounds like you have used WordPress a lot, and are new to Drupal? Well, I’m sure I’d be frustrated with WordPress trying to configure it to do what Drupal does.

As someone in the Drupal community, we all know there are usability issues around administration and upgrades. And Drupal is a as much a framework as a CMS, so out of the box it’s not really well-configured for blogging. But in return you get a ton of power and a great ability to customize.

To one point, but using local blogging software – the Drupal blog API can be used to post different content types – but this has to be enabled on the Drupal side.

By: Jeff

Jeff — Mon, 02 Mar 2009 17:28:14 +0000

Sorry to hear about your issues. There is a solid solution though, get a subscription with Acquia. They’ll support your drupal site, answer your questions, and help through upgrading. Something you cannot get with WordPress.