OK, that was a little messy because in Drupal 5, the default and settings.php is part of the Drupal code. I think in Drupal 6 it is created as needed. In this case we wanted our site to truly be the default, but not have any risk of overwriting it by svn updating drupal core. That would be bad.

(Note that Agaric doesn't pretend to understand why the checkouts we've checked out into the larger drupal core checkout don't get overridden. We're just happy that they don't. (Note further that the deleted default directory didn't get restored either. But we're paranoid. (In fact, more paranoid than ever. What if we do change any little thing in Drupal core, would everything get overwritten on the next svn update? (And finally, note that nested parenthesis in text is kind of fun.))))

Oh yeah, the how-to ended two paragraphs ago. You can get your time back by going and hugging someone you love.

Comments

Post new comment

Your name: *

E-mail: *

The content of this field is kept private and will not be shown publicly.

Search

Search this site:

Agaric?

Agaric makes powerful web sites for people who do things. As a collective of skilled workers, Agaric collaborates with you and open source free software communities to develop tools and build platforms that meet your needs.
How we can help you? Please ask Agaric!