emergency weblog; or: epersonae; or: elaine nelson

in which I write about stuff

DrupalCamp: CCK

the Content Creation Kit, one of the basic Drupal modules, explained. (very well explained, too.)

Categories: conference notes, drupalcamp seattle 2008, Professional

weird screen problems!

Basically, this & the Views session after lunch are one session.

Hey, she’s using an example. Excellent, I always learn better from examples. An art organization that offers art classes.

Planning, writing out ahead of time what you’ll need. Connecting instructor & course to create a scheduled class. (Some of what I was trying to do with rates?)

Each piece of information should only be entered one time. (Ala normalizing databases.) Linking to those pieces. (Yep, she just said the same thing re: database design.)

Now the how-to. “Content” in the CCK section. (for downloading)

When you start, all that’s there is Page & Story. After CCK is installed “Add content type” tab/link is available.

Machine-readable name is usually same as human-readable, but w/out spaces, etc. (node template teacher.node.tpl?)

Descriptions matter most when you have lots & lots of content types.

Every node has a title & a body. Full stop. But may not make sense in context of node. (In this instance, what about alphabetizing? Oh, she’s renaming it as “Displayed name of this teacher” — so presumably you could add first & last names separately? Although that seems annoying.) “Your main goal is not to get phone calls…support calls from the users of your site.”

Usually leaves minimum at 0, because users often have partial information. (I like how much she’s thinking about the needs of the data entry person.)

More thoughts about workflow in re: published by default — is that what you want?

Discussion of whether to use Body for something like Bio, because of conflicts with creating Views and/or Templates. (Looks like she learned something new! Fun.)

Create fields once the content type has been created.

Borrow a field from another content type. (Borrow a feeling? ๐Ÿ™‚ Also, can’t have 2 different fields with the same name.

She probably should’ve left offย  one of her content types before the presentation?

Node reference comes bundled, btw, but has to be enabled.

Ah, now I can see that you can use a text field w/validation for dates. (And does ANYBODY use datestamp?)

On Node Reference, Use select list when only a few, use autocomplete text field when lots & lots.

Hundreds of other CCK content type modules. (Although not so many for D6. Oh, had good chat over the break with Greg (heyrocker guy) and ??? (tall guy, maroon t-shirt) about whether to go D6 or D5. Sounds like for a new site, D6 is the better way to go, even though some modules are still missing, buggy, etc. That’s just where the energy is.)

Covering some particular issues in the image type, including checkbox. (Oh, can put name of person in alt attribute via theme!) If resizing pic, don’t worry about max file size?

If stuff isn’t required, make sure the theme doesn’t break down. Definite focus on making it work easy for data entry, make the Drupal developer do all the work. ๐Ÿ™‚ You can also have a default image. Audience member had problem with default image, conflicts with “required.”

Discussion of weight and D5 vs D6. (Hiding weight & using drag/drop? teh HAWESOME.) But…she’s missing some key modules. Grr. This is the basic issue with deciding on a version: D6 is just a better user/admin experience while D5 has more stuff.

“Mrs. Jane Q Smith III”?! heh. Ah, she has done just what I was thinking. First/Last name are fields for sorting & searching, but hidden on the display page.

Can use a single date field for start and end date, and a single date field for times.

CCK field “Date” — viewable via Calendar, Date API? (missed some of that.)

More detail on the Node Reference type; checkbox for which node type(s), and then also advanced that uses Views for selecting.

Now for Taxonomy…mismash of wording references (as mentioned in Drupal 101) “kinda schizophrenic” — and apparently another thing that got better in D6.

[so what’s the deal with lunch?]

Back to the planning list. How did we want to organize this stuff? 2 sets of terms: one set for subject area, one for age level. Better explanation of when to use taxonomy! Things that cut across multiple content types. A class has subject area & age level; an instructor has subject area(s), and a scheduled class draws both from class & instructor, so doesn’t need either.

(She did a bike trail site? Fun.)

Chewing on how to

Question about how/whether to use synonyms; she hasn’t used them, not sure how they work in practice.

Are there performance penalties for using CCK vs writing your own module? Might be faster, but harder to maintain. At what size site does it matter? Audience member answer, would have to be something damn huge (my words) for it to matter at all. Drupal.org uses CCK, handles the server load on the server end. Another audience member suggests that with shared hosting it might actually matter. Jennifer mentions caching, “turning off Views UI gives huge performance boost” and same with other unused modules. NWSource guy said their bottleneck was the database, everything is in CCK. And “so much easier”

CCK & custom modules can interact in weird ways, too.

[note for the gender-sensitive…I’m impressed at the balance here in attendees. I think Jennifer is the only woman presenting, but she is fantastic.]

Comment feed

Comments are closed.