| Language Name | syntax "Type" |
|---|---|
| Bash | bash |
| C | c |
| C++ | cpp |
| CSS | css |
| Drupal 5 | drupal5 |
| Drupal 6 | drupal6 |
| HTML | html4strict |
Various code tricks, techniques, snippets, puzzles, bugs, inconsistencies, patterns and other such stuff.
A guide to the one of the best open sources databases in the world!
After registering an account with the site, you may decide you want to go with a brighter theme than the default. So the site has been populated with about a dozen alternative themes that you can set from your user account.
To do this:
Your default theme is now changed whenever you log in.
NOTE: You may have trouble viewing all of the "extra" content with a non-standard theme.
This book covers how to use some of the sophisticated features of the site.
A collection of Bourne Again SHell tips and tricks.
So it's important to understand early on that Drupal strives for a 'secure' and 'reliable' architecture and does so by separating the core code from user generated and contributed code. All the editable code is kept in the /sites folder of a Drupal installation. In a single site installation all this modular code is kept in /sites/all/modules or /sites/all/themes. One of the most common beginner mistakes is to look inside the new Drupal directory and use the /modules or /themesdirectory for storing downloaded modules and custom code.
The root /modules directory holds the modules that have been incorporated in the core Drupal release, this directory and all directories outside of /sites should be left alone. Drupal provides ample ways to override the behavior of the core code, and using the API's is vastly more secure and reliable than altering core code.