Finally... my Read More link woes fixed? In Tweaking the Read More Tweak, I noted that I used the Read More Tweak module to make Drupal's strangely-invisible Read More links more prominent. But that module opened up another problem: the Read More link was appearing even when there was no more content, i.e., when the teaser showed the whole of the node. 

The issues queue for the module discusses the matter, ending with confirmation that the latest version fixes things. Yet I kept getting that link after every teaser, whether for new posts or edits of old posts. Recent testing revealed something else: Somewhere along the line of upgrades and experiments, that module had stopped being at fault; I was now getting that persistent link in every teaser even with Read More Tweak disabled.

Things are fixed now. It's all so simple as to be embarrassing:

I set up a FeedBurner account for this site a few short months ago, with the help of the FeedBurner module. Things seemed to work: I saw a modest but crunchy number of subscribers, and looked forward to tracking that number.

Then things stopped working: FeedBurner shows 0 subscribers (et tu, Mom?), and attempts to sign up for posts via email didn't work. 

I think I fixed the problem, but first this test post. If it works, I'll post a few notes on the troubleshooting experience.

I posted a new page titled Drupal for Beginners. It's a broad "What's Drupal" overview, with answers to some of the most basic beginner questions I see on the Drupal.org forums, and pointers to important resources that beginners should check out.

Please take a look and let me know whether this is of use. Thank you!

In Drupal 6 and browsers make nice-nice!, I got all happy over the Safari 4 beta abolishing several bugs that had kept me from using Safari as my Drupal site admin tool.

However, I failed to post a crucial follow-up to that: it wasn't long before a new oddity forced me to toss Safari out the door once more. The problem was in buttons, such as those for opening a "Choose file..." dialogue when uploading an image. Sometimes – not in any way I could predict – buttons would be dead in the Safari 4 beta, doing nothing when clicked. That's an annoyance during general web use (such as when trying to submit a comment somewhere), but a show-stopper for admin work. 

The problem persisted even after the official Safari 4 launch, so it wasn't a beta problem alone. Yet a search on the Apple support forums and elsewhere didn't turn up people with a similar problem, so clearly it wasn't a real Safari problem at all. That's where I lapsed out of my usual vegetative state just long enough to remember that I had a couple of old third-party Safari plug-ins installed, Inquisitor and Safari Stand. They're both nifty tools, and perhaps later I'll play with Safari 4-tested versions, but at least one was gumming up the works; removing both has fixed the problem.

It's only been a few days, but so far I haven't found any problems remaining when using Safari for admin work on Drupal 6. Great! And there's a big bonus, as well: Apple's playing up blazing JavaScript speed as Safari 4's forte, and it's really making a difference on my iMac. Dialogues for images, links, and so on in TinyMCE pop up so much faster now than they do in Firefox. (And as a small bonus, the Top Sites feature is handy for quickly getting at any number of sites in progress.)   

I may want to head back to Firefox at times to use some specific web developer plug-in, but for general admin work, Safari 4's speed alone is making me happy all over again. Until the next show-stopping bug, that is...

In the EDAM manual page Taxonomy Suggestions, I outlined one of the ways I like to set up taxonomy for a generic site: one Vocabulary to tag what a piece of content is (a news article, a general info page, a review, etc.), and one Vocabulary to tag what the piece of content is about (Drupal, politics, clown attacks, whatever).

For this site, I use a short list of Terms for the first Vocabulary, but free tagging (i.e., free-form input of Terms) for the second – I had no idea how many Terms I'd want for tagging posts, and individually adding each desired new Term to a list seems a pain. (Incidentally, to enable free tagging, go to the target Vocabulary's "Edit vocabulary" form, and check the "Tags" box in the "Settings" group.)

Free tagging is handy stuff, with one drawback: free input makes it hard to keep consistent with your Terms.