Drupal

Because the calendar/event system thinks that seven days after a Tuesday is a Monday, I'm simply scrapping the event system on the site before I get any angrier. I'm already feeling a whole lot of RAAAAGE!!!! right now at it, and I'm seriously considering just trashing Drupal and creating myself a new site from scratch. At least that would work right.

Tomorrow morning, I think I'm going to delete all my events on the site, and start over from scratch. It seems that the Event Repeat module for Drupal enjoys completely messing up my event nodes every time I make any kind of change that should be propagated through a series of repeated events, and not only in the nodes in the series being changed. Oh no — if it doesn't screw up other event nodes as well, it's a waste of effort or something. It really pisses me off.

DrupliBacon™
by chrys

Not mine, but hilarious. Rob, you should get a kick out of it for sure!

I'm moving over to Disqus for site comments, thanks to my friend Rob Loach's work on a Disqus module for Drupal. There's some issues to be ironed out, mainly with Drupal core, as I can't turn off the Comments module (it's required by Project issues) but disabling the ability of users to comment doesn't prevent it from spewing at hook_link.

This week, I'm looking forward to tackling one of the issues that so far has kept me from moving Toast IT Toastmasters from the current (lame) website to a new one I'm building in Drupal. The problem has been that while there is a module for signing up for nodes, there is no module that does the same thing for CCK user reference fields. (Well, that's the one I'm tackling, anyway. There are others, but not as important.)

After downgrading Apache, installing Xdebug for PHP, clearing the in-database Drupal cache for each test site repeatedly, and dancing in the rain with a dead chicken in nothing but my underwear, I've finally gotten the test sites on the laptop up and running.

I've been having a lot of trouble lately, getting Drupal to play nice on my local setup. Both when I was using the old P2, and now with the laptop, whenever I tried to make use of the local Drupal setup (using a copy of the live database) the child process of Apache would crash, with nothing logged by either Apache or PHP.

For some reason, Drupal hates me. And I don't know why.

This time, the problem was with Links Package – without cause or reason it decided to change a number of the links on my links page to different URLs already on the page. It did this to more than half of them. I've since changed the URLs back to what they should be, but it's just bizarre that this would happen in the first place!

Hello internet, what's happening... I finally got around to updating the various Drupal modules that had fallen out of date on here, and patched up Token with some event-based, well, tokens. I'll pass them upstream some point today, and perhaps they'll even be committed by someone.

If you've been paying way too much attention to my website lately (and I'm sure you haven't) you might have noticed that I've been fooling around with different themes, looking for one to replace the current Garamond theme that currently defines the look and feel of coldacid.net. The thing is, while Garamond was okay when I first started using it, it's lately started to feel somewhat of an albatross. (And it doesn't help that almost every LCD monitor I've ever dealt with more or less washes out any of the theme details, either!)