I enabled ModuleInfo. It's very simple and very cool. Now each enabled module on my site has an information link that tells me all about the module and where it's being used.

I enabled the Admin Role module today. This module is supposed to allow the user to assign all permissions to a specified role.

Unfortunately, the module had some issues with 6.5, such as assigning all permissions to the wrong role, or not assigning them at all. As you can probably imagine, it was pretty frustrating and disturbing.

I have an issue posted on drupal.org, so we'll see what happens. I have disabled the module until the issue is resolved.

UPDATE:

I enabled the admin_menu module. It was very easy to configure. I removed the Administration menu items off of the Navigation menu so they weren't in two places, which would have defeated the purpose of installing the module in the first place.

One thing I'll need to remember: Re-enable the Administration menu items in the Navigation menu when the time comes to do a Drupal version upgrade. Otherwise, after I disable all contrib modules I'll be left without an admin menu at all. That would suck. Five bucks says I'll forget to do that...

Drupal Chix has a thread going right now about Labor Saving Modules & Tips. MiriamNZ posted a comment about the modules she finds useful. Included were:

• admin_menu
• adminrole
• moduleinfo

Upgrading from 6.4 to 6.5 was pretty easy. Just follow the Upgrade.txt instructions and use SimpleScripts to perform the upgrade and Voila!

Nothing seems to have broken.

From what I can tell, I can't make a content type created in CCK a menu item.

For example: I created a content type called Book Reviews that I wanted to link to in the right nav menu. From what I can tell from the Drupal documentation I can't do this (well maybe using Views?).

But if you look to the right you'll see a "Reviews" section there. How did I do this?

1. Create a vocabulary in taxonomy called Reviews with "Book Reviews" and "Movie Reviews" listed as terms.
2. Assign these new vocabularies to each book and movie review.

As you can probably tell, I have switched from the default theme (Garland) to one of my own creation. More accurately, I took the Garland theme and made it my own. I know it's not that pretty, but it's a work in progress.

Neat things I learned:

• .info pages are FSM's gift to Drupal
• modules/system/page.tpl.php is also FSM's gift to Drupal
• To change the style of an area of your website, open the page.tpl.php file in your theme and find the corresponding id or class of the area. Then open style.css and find that id or class and change it.
• Fun.

I've just learned something potentially annoying about Taxonomy and CCK. It seems that if you create a new content type using CCK, you need to go into Taxonomy and manually assign the content type to the corresponding vocabularies in order to use Taxonomy in the new content type.

I can see why this would be the case, but if I have new content type that I want all my vocabularies to access, it gets quite tedious. A 'select all' function would be nice.

Maybe the point here is to create specific vocabularies for specific content types. I'll have to continue to think this through.

I'm trying to grasp Taxonomy as it applies to Drupal. I'm using this entry to test faceted tagging.

According to Drupal 6, by David Mercer,

Facted tagging uses a bottom up system of classification, where facets or properties of the content are described by the terms.

I suspect establishing a solid Taxonomy for ppld.org will be quite a challenge. I hope that this is the sort of thing that can be altered as the redesign progresses. I fear that I'll need to have a set Taxonomy ready from the beginning and I'm not sure if I can do that.

I'm also not sure exactly how Taxonomies work yet. I mean, I see I can add Vocabularies to this entry, but I really want this entry to fall into the Taxonomy category, not the list items for Taxonomy.

Wish me luck!