Documentation

This has not been edited for human consumption: it's just a dump of every browser tab open for research into doing some more advanced work with the version control system CVS, which is the default for the Drupal project. Even some SVN stuff may have snuck in here. These notes are very much for Agaric's internal use!

Would agaric design consider taking on a job for web development (say, setting up a personal website) and doing the work alongside the client, teaching them along the way, for a higher fee than normal?

Q: For the record, what's the difference between a plain vanilla Event and an Event-enabled CCK content type?

A: Event can (more or less) work with any node type. A reason for using a CCK node (say, content_event) instead of the event module's default node type would be the ease of adding fields--

Mac OSX's graphical enhancement of the unix diff command, opendiff (part of the optional free add-on developer tools) can be accessed through terminal like so:

Ebony-697:~/Web Sites Data/LinkLocus/Power2Exchange/css ben$ opendiff style_old.css style_new.css

(You can also grab the files through a graphical interface through [volume]/Developer/Applications/Utilities/FileMerge)

Key, poorly documented commands:

Two little extras to make a new Drupal installation that extra little bit better (it's the Agaric way):

• Put a robots.txt in root.
• Put favicon.ico in root, even if it's already somewhere else or called something else.

And some contributed (third-party, non-Drupal-core) modules:

(Drupal 4.7) Sometimes moving the menu entry for a category, page (I think), or other node will fail when done from the "edit" tab on that node.

Don't panic.  Just go to administer/menu and edit the menu item from there.

It's worked every time for us so far, but we rather hope this bug will be fixed in Drupal 5.0.

Planet Photoshop Effects Tutorials

A good, simple module for Drupal called Nice Menus has an annoying bug (supposedly not on all themes, but certainly on most of them): It frequently loses the focus when the mouse moves from the top-level menu to a child menu, causing the drop-down menu to disappear as the user goes to click on it.

Very annoying. (If you click and hold and move the mouse down, the second-level menu stays and you can then click on it. Not exactly a solution you can ask your users to do.)