Melançon Enterprises • a multidivision multinational since 1980

Get a client e-mail about a Drupal node clone bug and a basic question about where to look up registration data of people submitting forms on the web site (we'd made them with ubercart free order, so admin/store/ etc.), look for errors about this in the dblog, note again all the hits the site is getting for images that are no longer in that location from stupid people on forums who hotlinked them on the old site, realize this time that stopping these many hits to the Drupal 404 not found page, which even worse is redirected to a node in their setup, is making boost create a cache for each one, and just 404ing these fools at the Apache level would be far better, and might have really helped the site not struggle so much when it was on a too-weak server a week ago, and think this is just the sort of thing that should be on a checklist, web development needs checklists, knew this even before hearing about the checklist manifesto, and then thinking it would be a really good idea to have an online checklist, and even better let people share and rate checklist items in various categories, post an issue to the Drupal checklist module and register drupalchecklists.com, and plan to work this into the Drupal 7 book.

Get a text from my business partner but messages in the phone full because Verizon or Samsung imposes an arbitrary limit that has nothing to do with storage space on text messages and spend 7 minutes typing old messages to save them because i have psychological problems.

Then write this blog post.

Wonder how many distractions weren't recorded. Note that the client was responded to, but no time logged. What's the work time in all that first paragraph, 10 minutes i think and 15 messing with the Drupal Checklist idea, and trying to change my user info at the registrar, still have to submit the support request since it isn't saving that form...

Oh yeah the checklist item here is to put common 404s that are not your site's responsibility -- legacy non-page (file/image) content like this which should not be redirected, and probably common attack vectors like wp-login.php or such that certainly doesn't apply to your Drupal site -- these things should just give 404 from the web server before Drupal ever has to get involved.

Going to check Harvest for putting in time and this invoice and then walk the dog.

Meta will end now.