I like this idea -- to a degree. Quicksilver on the Mac (blacktree.com) offers you three modes: Stable, Beta and Development, meaning that you can run at the bleeding edge if you're feeling brave or you can simply use the most stable code. Drupal could offer an administrative setting (perhaps in conf.php) that would enable experimental code for testing... I dunno, that does seem a bit out there, but it's a novel idea to address the concerns raised so far. Chris On 4/26/05, puregin <puregin@puregin.org> wrote:
On 26 Apr 2005, at 1:22 PM, Chris Messina wrote:
I'm terribly confused by what you mean... are you against this feature because it's "dangerous"?
Perhaps we could provide better safeguards to prevent again "breaking the whole thing outright".
I mean, if you don't like this idea, what kind of alternatives might you suggest?
Chris
On 4/26/05, Gabor Hojtsy <gabor@hojtsy.hu> wrote:
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.
Goba
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.
Djun