3 ms·
Handing a Drupal website over to a client was always hard. No wysiwyg, no automatic updating, built-in dependency hell (that the client can see in /modules), _c
by saltcod 15y ago
Handing a Drupal website over to a client was always hard. No wysiwyg, no automatic updating, built-in dependency hell (that the client can see in /modules), _constant_ warnings about module updates and security updates and core updates and updates of every other kind, make Drupal an extremely tough sell.
- krondor 15y agoJust a few nitpicks; Drupal does have wysiwyg implemented as a module http://drupal.org/project/wysiwyg http://drupal.org/project/wysiwyg (actually several competing editors are possible), Drupal also can do automated updates, though I wouldn't advise it. Drush works for it, http://drupal.org/project/drush http://drupal.org/project/drush and a lot of people use it with great success. You would want a carefully vetted rollback plan though. The better road is to forgo updates other than security until scheduled maintenance or a MUST have feature is present. The GUI /update process is actually quite nice if you've set everything up properly. The thing about Drupal is doing everything doesn't have to be painful, but if you've approached it in a "non-Drupal" way it can get bad quickly. Drupal is complex and the hand off to a customer is never easy with complex software. Have you tried the same with Plone?