Definitive Guide to Drupal 7

• Project-izing Handbook maintenance

Karoly Negyesi (chx) mentioned in IRC "one thing people (like rszrama) is using entities is basically multigroup functionality." "Say, you have something like a line item in an invoice, needs a lot of fields, that becomes an entity. And it's not a node because a node has stuff like promote and sticky which does not apply."

Fields

borrowing from Barry Jaspan, http://www.archive.org/details/DrupalconDC2009-FieldAPIDrupal7

texas-bronius: What's the best way to provide css for non-js-enabled browsers that differs for css for js-enabled?
17:13 texas-bronius: hi benjamin-agaric welcome back
17:15 benjamin-agaric: texas-bronius: hi. Assign the classes themselves with JavaScript?
17:15 texas-bronius: benjamin-agaric: duh. Yes, good idea thanks. Class name could be "hasjs" or something.

The nodeapi ops were turned into hook_node_[operation] functions, such as:

These are notes for what will be an Appendix in the Definitive Guide to Drupal 7.

Before we do anything to try to upgrade a site, we back it up. We also never upgrade the live, production instance of a site, but a copy. (At least the first time.

[gotcha] If copying over the entire code of a site, make absolutely certain that we have changed the database connection settings in settings.php. Especially if we are (and we shouldn't be, but if we are) on the same server as our live site. [/gotcha]