Drupal 7

Update: Issue posted. http://drupal.org/node/1028214

The goal is to use the book-variable.tpl.php (exactly like the book-variable.tpl.php is used, including how it gets overridden by themes) but without its preprocess function. Here's one fallback approach that should work, but doesn't, due to seeming weirdness in Drupal:

Notes from the Lullabot Drupal Overview video (which is free until Wed. Jan 12).

minimal has no optional modules enabled nor any content types. Nor is the administrator role set up for you.

DBTNG

master-slave replication

any database that PHP can support, which includes Oracle and MSSQL (Microsoft)

built on top of PDO which comes with PHP 5.2+.

Drupal requires PHP 5.2.4 or later
PHP 4 is dead.

User 1 is still special

Short story: Turn the navigation menu off on any site for which you are customizing the user experience, it is only going to cause you pain.

Seeing "You have not created any content types yet. Go to the content type creation page to add a new content type." when you know darn well you have content? And node/add/page, say, still works?

Is it a bug, a feature, or 'gee. huh' that moving a content add form out from under "Add content" in the navigation menu will also remove it from the node/add page?

After much thought, and not being sure if it needs a hook_theme and a template_preprocess or what

Decided that it is not something we should be doing anyway. Overriding block.tpl.php or node.tpl.php from a module just messes up themes! We can have our own templates for the content we print if we want.

Please leave a comment if you think this conclusion is incorrect!

When fields are used for configuration-like stuff (this is for AJAX form messages) it would make sense to be able to export field instances to code (as opposed to, say, node or comment fields).

asked, to no avail:

11:37 benjamin-agaric: is there a standard / anything anyone's tried for giving programatically-created field instances a machine name type thing

By using field storage, we get access to translation.

We've defined the info files, made them dependent on the core module. That was fun!

Caching is fun to implement, but try to hold off until you have all your functionality in place. As someone somewhere surely said (OK, it was Donald Knuth), "Premature optimization is the root of all evil."

We could define our form messages as a nested array analogous to menu definitions— a form ID,

Fields offer the advantage of understanding translation for user-entered data. Therefore, using fields, there's a potential

the $conf variable --

http://api.drupal.org/api/drupal/developer--globals.php/global/conf/7

Drupal 7 Module Development, as expected from knowing the authors, is an excellent book. As an author on another Drupal book, i can't give a Planet-posted review, but it's very good, it should be bought, and the things i think are incorrect i'm noting here until i can find the Packt errata submission form.

http://packtlib.packtpub.com/drupal-7-module-development/book

Slides and code:
http://www.angrydonuts.com/drupal-7-advanced-ajax-tips-and-tricks

Drupal 7 combined the existing system with one Earl wrote for CTools.

Not covering form today (#ajax). Earl doesn't like

How you build an AJAX request and what that means.

How do you respond to an AJAX request: server-side, PHP code. 'delivery callback'

Page Rendering in Drupal 7, presentation by Moshe Weitzman at DrupalCon Paris 2009. Transcript.

Changes you can make with this rendering system that was hard with D6 but trivial in D7.