[drupal-devel] Let's accept more interim solutions

Gabor Hojtsy gabor at hojtsy.hu
Wed Apr 27 20:13:04 UTC 2005

>>>> I don't have a clear idea of how to fix this, but I'm suggesting that
>>>> we think about ways of pulling Drupal's cooler features up to the
>>>> surface where making hacks are more accessible... one way to do this
>>>> *might* be to offer module and theme editors in the admin section...
>>>> making it possible to work on and improve modules without having to
>>>> interact with a server... while many in the Drupal community might not
>>>> be directly interested in this feature, I think it would do a great
>>>> deal for bubbling up the ability to hack on do cool things with
>>>> Drupal.
>>> And break the whole thing outright quite easily. If a single module is
>>> broken, then all you receive is a blank page, or even worse an error
>>> message.
>      Perhaps one could enable a 'test mode' in which settings would be
> checkpointed, and automatically rolled back by cron if changes are
> not manually committed?    This might offer some protection.  This
> approach might help new users recover from a bad attempt to
> enable  'clean URLs', also.

Cron will include all Drupal anyway, so if you have a broken edited 
module, then cron will be broken.


More information about the drupal-devel mailing list