Overriding Drupal database variables
Tucked away at the bottom of settings.php is the following comment.
Technical information on this site may be out of date : no updates since 2015
Tucked away at the bottom of settings.php is the following comment.
For most of 2008 I’ve been working on a large Drupal installation (around 10 developers, something like 100 custom modules, 17 languages, split over 2 sites).
This all adds up to a lot of updates, and schema changes.
OK - so I’m a heretic.
This is absolutely against the accepted Drupal Dogma.
What’s great about Drupal is that you can achieve most things without hacking the core codebase; this means that every Drupal installation has the same base and any good developer who knows Drupal can take over the site.
The selected file could not be uploaded, because the destination is not properly configured
This “feature” has bitten me before. It’s one of those annoying Drupal things which would be fine if the error message wasn’t so misleading.
What’s happening is that file_copy()
calls file_create_path()
Drupal allows you to create multiple sites sharing some or all of the same code and optionally sharing some database tables.
The documentation for the Drupal settings file http://api.drupal.org/api/file/sites/default/settings.php/5/source
includes the following
One of the things that is confusing about Drupal is the use of the word node.
Going to the dictionary doesn’t help much:
In my opinion “node” is just the wrong word.
PracticalWeb Ltd today joined the Drupal Association
The membership fee helps support the drupal.org infrastructure and marketing costs.
Unit testing Drupal can be pretty challenging as it’s hard to isolate parts of the code.
One of the surprising things about Drupal is that it doesn’t use object oriented coding.
There’s a good page in the Drupal documentation about this
http://api.drupal.org/api/file/developer/topics/oop.html
It makes a good case for the design of Drupal, and goes a long way to explain why Drupal feels more OO than the code looks at first glance.
Drupal 6 has been out for a while now, Drupal 7 is in the works, and yet most sites still seem to be using Drupal 5. Is it time to upgrade yet?
If it was just the core features the answer would be simple, Drupal 6 is better and is fully stable.
The problem is that many (maybe most) of the features of a Drupal website are powered by contributed modules, and modules written for Drupal 5 don’t work with Drupal 6.