So you're editing a Story node in Drupal, and... Wait, was it a Story? Or was it a Page node? Or is the node you're editing actually a Blog Entry?

When you create a node, Drupal gives you a big-letter reminder of what you're making: "Create Story" (or whatever the node type is) appears at the top of the creation form. Yet when you later edit the node, there's no easy reminder of what the node type. Clues in the path, the visible fields, or elsewhere may give it away to the experienced site builder, but not to a newcomer admin to the site. And to be sure, you won't often care what the node type is when making some small edits, but then again you might find yourself scratching your head as you stare at the edit form for a node someone else made, thinking that you'd like to make this change if it's a Story but that change if it's a Page...

There's a nice and very simple tip at the Josiah Ritchie blog to aid future editors (including yourself) on this small point.

Here's a checklist I used when quickly setting up a new sites in Drupal 6. It's appeared on this site earlier, but buried away in an obscure older page (Checking out Drupal 6: Dipping into new site creation); I'm moving it here so it'll have its own page that I'll remember (?) to update more frequently.

I hope this'll be helpful to Drupal beginners who are unsure what key tasks they should consider after installing Drupal. Bt don't dive into the list just yet! Some pretty important disclaimers come first:

Read these first!

1. My checklist is for sites built upon a copy of my existing Drupal "sandbox" installation. That's covered in the first few items of the list; Drupal installation from scratch isn't covered. Chances are you might need to replace items 1-4 with the standard procedure for setting up a new site.
2. My sandbox database already includes lots of things set up that I almost always want for a new site: can't-do-without-'em modules already enabled, input formats created, key content types configured, and so on. To better aid readers, I'll add those into the list over time.
3. The checklist represents just the basics to build the framework for a "generic" new site (to the extent that such a thing exists). After that comes the real work of web site creation: customizing and building all the features specific to the new site! That, of course, can't be covered here.
4. The list makes sense for the sites I typically make; it may be all wrong for you. Treat as reference and entertainment. (And parts may be all wrong for me; let me know if I'm doing something dumb and need to stop!)

The checklist

Here we go:

1. Create directory for the new site within Drupal installation (per general Drupal installation procedures)
2. Create empty database for the new site (via my ISP's online tools)
3. Import a copy of my sandbox site's database into the new database (via phpMyAdmin)
4. Make sure new site directory's settings.php file uses correct domain and database info
5. Log in to new site (Unasked-for tangent, and admonishment to writers everywhere: Note that that's "log in to site", not "login to site". Major pet peeve. Grrr.) 
6. Change ID 1 user info (which is still the same as sandbox site) to new info appropriate for new site
7. Put site in maintenance mode at admin/settings/site-maintenance
8. Enable or disable key modules at admin/build/modules
9. Handle any pressing warnings/notices tossed up by Drupal
10. Change site info at admin/settings/site-information
11. Enable and select theme. If an existing theme will be modified into a new unique theme, first create and rename a copy of the theme within the new site's themes directory. 
12. Make sure file system at admin/settings/file-system is set to sites/<domain>/files
13. Set site's meta tags at admin/content/nodewords, including Description under Front Page tab (requires Meta Tags module)
14. Set site's contact info at /admin/build/contact
15. Change sandbox site info at admin/settings/forward (requires Forward module)
16. Get Google Analytics ID via Analytics account, add at admin/settings/googleanalytics (requires Google Analytics module)
17. Set XML Sitemap, submit to Google (requires XML Sitemaps module)
18. Remove unneeded menu items (left over from sandbox setup) at admin/build/menu
19. Make sure email for site works
20. Once all is working, turn of error logging to screen at admin/settings/error-reporting

Steps after that start getting pretty site-specific, so the list ends there. The important thing is that the above takes me to a functioning beginning, without my having to think hard.

What's your (probably better) site setup checklist?

As described in How's that Ubercart review coming along?, my work on a Drupal ecommerce site using Ubercart came to a halt when Node Import refused to import my spreadsheet. I found and fixed the problem: Node Import was choking on a column that held paths for my nodes' images. (It was choking silently and demurely, which didn't help at all; a spittle-flinging "ack.. hack... image paths... hurk... killing me..." would have made my troubleshooting a lot faster.)

It seems Node Import wanted slashes in front of my paths (like this: /images/picture.jpg), whereas the book example I'm following shows paths without (like this: images/picture.jpg). I'll add more on that in the final review, but let me note that I can't say for sure it's an error in the book; perhaps the slash-less paths are correct under some setups, such as a different file system setting. (My sample site is using the Public, not Private, download method. Not that I know that that matters.)

In any case, for anyone having trouble getting Node Import to work, one basic troubleshooting step should be obvious: try importing versions of the spreadsheet with columns removed, one batch after another, until you can track down the column(s) with data responsible for the trouble. (You know, remove half the columns, so you test the remaining half; then reverse things so you test the other half... If one of those two variants causes trouble, then test that with first one half of its columns removed, then the other half... There's a name for this sort of thing, but I'm blanking on it. Computer-y people, anybody know?)

All right, back to the Ubercarting...

I'm working through Packt Publishing's Ubercart 2x book to create a spiffy Drupal e-commerce site. So far, I'm finding the book itself worthwhile; it's been quite a help in installing and setting up Ubercart, and creating some basic products. All fine and good, and I look forward to showing off a sample site and writing up the book review.

What's taking me so long is getting Drupal/Ubercart to work right. First I had a problem with certain Ubercart admin forms making themselves unavailable – a problem which, like an earlier unrelated problem with image paths, mysteriously hiccuped itself into resolved status. (Oh, Drupal, stop toying with me.)

Now it's problems with importing nodes from a spreadsheet. This is a part of the book I could just skip, creating all my sample products one node at a time. But I've been wanting to play with node importing for some time now; I have plans for a future site that'll require mass import of music-related data. Any e-commerce site I build in the future, too, is almost certain to require import of product data, so I definitely want to take this chance to learn the importing ropes.

The import process calls upon the good offices of the Node Import module, a welcome tool which, although used in the Packt book, isn't entirely up to full production snuff in Drupal 6. My first bug upon trying to import product data took the form of an ugly error message:

Fatal error: Call to undefined function uc_product_node_is_product()...

Bleah. One solution, as noted in module issues threads, is to forego the latest release candidate, 6.x-1.0-rc4, and use the newer 6.x-1.x-dev instead. That worked! But then comes the second bug:

Once the spreadsheet file and other assets (such as images) are all ready, Node Import takes you through an eight-screen process to start the import. Click "Start Import" on that last screen, and something magical is supposed to happen with (I'm told) a progress screen and, finally, magically-created nodes. Alas, I'm getting the Drupal equivalent of that Millennium Falcon hyperspace scene, where the engines rev up and... sputter out, keeping the ship right where it is. My site just jumps back to the start of the import process, with no progress bars, nothing imported, no new nodes. I add a little detail in an issues thread where a couple other Drupalers have reported the same trouble.

(ADDITION: The above problem holds true using both a tab-separated format or a comma-separated format, whether I output from Numbers or from Excel. Actually, using comma-separated (CSV) format, it holds true using general Latin encodings – but what Node Import asks for is UTF8 encoding. When I try that, I don't even get as far as the end of the eight screens; after just four or so, I get this lovely error message:

Fatal error: Unsupported operand types in /<my web site path>/sites/all/modules/node_import/node_import.admin.inc on line 371

Sigh.)

So that's where I am today. I expect I'll get past it eventually... maybe even really quickly, if a kind soul reading this can suggest what's going wrong. Anyone?? (Banging on the monitor isn't helping at all.) 

In the meantime, looking ahead through the Packt book, I see all kinds of exciting Ubercart features waiting to be tapped. Sure hope I can get there soon!

EDIT: I think my problem's solved. See end.

I'm working on an Ubercart store using the documentation at Ubercart.org and Packt Publishing's Ubercart 2x book. According to that book and to Ubercart.org documentation, the form at Administer › Store administration › Configuration › Cart settings should have three tabs: Cart settings, Cart panes, and Cart block. However, on the new site I created, I see no tabs at all; there are the various settings expected for the Cart settings tab (General cart settings, Anonymous cart duration, Continue shopping element, and Cart breadcrumb), but there are no actual tabs, and thus no way to reach the settings for Cart panes and Cart block.

Any ideas on why this might be? I'm on Drupal 6.15 and Ubercart 6.x-2.2. I tried enabling all core and optional Ubercart modules, to no avail. The Theme is the default Garland. No funny cacheing- or optimization-related features are enabled. What could cause these tabs to be missing?

(I've asked the question at the Ubercart.org forums and the Drupal.org forums, and am still looking for an answer. Thanks to anyone who can help!)

EDIT: I'm going to sheepishly – if tentatively – retract my question. I've been unable to find any other folks with the same problem, suggesting that it's truly a bizarre quirk of my own setup, and not a Drupal or Ubercart problem per se, with a clean answer floating about out there. In the end, I tried "joggling" things: clearing cached data in admin/settings/performance (even though I have cache disabled); and, disabling and then re-enabling Ubercart modules. Somehow, those actions did the trick: I now get the missing tabs. 

As happens with Drupal problems now and then, it's a welcome but unsatisfying resolution; it's the equivalent of smacking a TV to make the picture come in, without revealing anything about the source of the problem, how to prevent it happening again, and what to do if a future recurrence proves more stubborn. Sigh. In any case, things do look to be working again. 

For anyone running across the same problem and this post in the future: You may be facing a "gremlins" issue and not a clear problem to be reasoned out. Try purging with any and all caches, disabling and re-enabling modules, and just general fiddling with things. Heck, try giving the monitor a few knocks; that just may do it. : /