Thanks to @mortendk for finding this. I'm going to post i up here, because eventually I'm sure it would get removed for the original poster's awesome use of profanity. Someday I want to use this kind of a reply to someone, but I can never find the appropriate time.

The original post can be found at bugs.php.net.

From bugs.php.net

[3 May 9:23pm UTC] SOMERANDOMDOUCHE at gmail dot com
Description:
------------
Yeah, I would firstly like to mention how absolutely pissed off at PHP I
am. Your program must be the absolute worst programmed piece of software
in all of the net. You compete with Bill Gates in that regard.

Now that I have that off my chest, let me explain why your program
sucks. I have spent over 12 hours researching, reinstalling, etc etc etc
etc etc etc ETCETERA... All trying to get mysql into php. It won't load
the goddamn dll. Nothing in Event Log. Nothing anywhere, regardless of
errors=E_ALL, or "REPORT_STARTUP_ERRORS". I have fucking done it all.

ITS IMPOSSIBLE TO INTEGRATE PHP WITH MYSQL. THIS IS BECAUSE YOUR PROGRAM
SUCKS, AND YOU SHOULD ADD SOME GODDAMN ERROR REPORTING SO WE CAN AT
LEAST FIGURE OUT WHAT THE FUCK ____YOUR___ PROGRAM IS DOING WRONG.
FIX YOUR SHIT. just fucking fix it.

Thanks. And fuck you sincerely, for making my life, and everyone else's
life, an utter atrocity. I'm going to Cold Fusion 8; Fuck you.

Expected result:
----------------
Nothing. Your blasted PHP program doesn't even report error messages
like it should.

Actual result:
--------------
Yay! PHP Works. Oh wait... no it doesn't. It isn't loading .dll's, and
it isn't reporting why not - maybe this is because PHP sucks? yup, i
think so.

[3 May 9:26pm UTC] SOMEGUY1@php.net

.

[3 May 11:02pm UTC] SOMEGUY2@php.net

I wanted to send you a unicorn and a rainbow by way of apology, but
realized you wouldn't be able to sign for it since your head is stuck
so far up inside your ass.

OMG. Let the awesomeness ensue.

As we all know, or at least those of us that at any point ever have had to deal with browser compliance across multiple browsers, platforms and versions, it can always be a HUGE pain to get new fangled features to work properly in every browser. Who is the usual culprit we are used to getting pissed about? You guessed it Internet Exlporer, or as I like to call it, "Internet Exploder", or "That suck ass browser".

The new theme I have here uses almost 100% transparent PNG images for all the regions, and relies on the transparency and the background gradient to give the site the overall color theme. Of course Internet Explorer 6 (IE6) does not know what to do about this. It never has, and never will. This is only one of the obvious many things wrong with IE at any level of it's awesome ability to make up it's own web standards, and think they are cool or something. Forget floating issues, and padding issues. But I wont go on and on about the issues, because I'd just be preaching to the choir here.

The 960 Gridder module utilizes the code developed by Andrée Hansson, and is intended for use with the ninesixty theme created by dvessel. The 960gs CSS Framework system was originally created, and is maintained by Nathan Smith.

Using the 960 Gridder module allows you to enable the 960 Gridder by default without using the bookmarklet provided at the author's website. It also provides an administrative interface, allowing you to configure ALL of the options available with 960 Gridder and additional features including:

You can save these settings as the default settings for when 960 Gridder loads, so that you don't have to configure it every time it loads as well.

I just recieved a link from @sethcohn regarding a post from Acquia floating around the twitterverse.

The post by Jacob Singh highlights a new process for installing those pesky updates to your Drupal site in Drupal 7. The process is looking VERY nice, and makes it so that a non-techie client could complete updates without any issue.

The Permission Select module I created a month or so ago now was the only one I have so far that I ported to Drupal 7 at the same time I made the Drupal 6 version. It was quite an honor to see my module up there bein used and tested with. Granted, it's only because there is an active Drupal 7 version, along with a small handful of the crucial developer modules like Admin Menu and Devel.

After some initial feedback on my Save & Edit module for Drupal 6, I've decided to push forward with attempting to get support for the feature to be included in Drupal 7 as a core item. I've recently figured out an issue with a bug that was preventing me from feeling it was complete, and now with that done, I'm ready to push to get it accepted as a desired feature, and move forward with creating a patch that will put it in core.

How to help get this in D7 core...

Please visit drupal.org/node/500890 to show your support for the module, and post feedback related to getting it in core.

Here is the original post on drupal.org regarding the issue.

I would like to start off a "paper trail" of my efforts to get Save & Edit functionality in Drupal 7 core. This will be my first time proposing a feature or discussing a feature that I actually plan to implement myself, and provide patch(es) for, so keep that in mind.

Well, this has been a long and unproductive weekend with major frustration in trying to accomplish what "should" be a simple task in Drupal 6.

I posted a couple of issues over the weekend related to the problem as it evolved from Friday night to Saturday, even ending up on Sunday spending some time in the IRC channel searching for the answer.

The related issues on drupal.org are 497636 and 497530. The issue itself was not easily apparent in my initial work on the Taxonomy Rockstar module. What I'm trying to accomplish at this point is only laying down code for the backend interface, and the API that will allow developers to extend the modules using an easy API to create new layout types and search filters for taxonomy presentation.

The Real Problem

At first the problem seemed to be related to my hook_theme function and somehow it not sending the appropraite $element to the function I created for theme_checkboxes.