Alrighty, then!

Welcome, finally, to the new (and soon to be improved) Universal Hub. Fire away with comments, complaints, etc.

A couple of changes:

If you have an OpenID account somewhere, you can now use it to register/log in here (click on the login/register link in the upper right).

If you post an article, you'll notice a new "Split" button on the posting form. Put your cursor where you want your article to be "split" - the top part will show up on index pages as a teaser to the entire article.

More to come.

And what was it that kept blowing up?

Grr, I feel so stupid about this, but here goes: The new version of Drupal in use here uses a lot of caching to reduce database loading - basically, if you're the first person to look at a page, the database makes a copy so the next person who comes along gets that instead of a freshly made page assembled out of lots of database queries (yes, Drupaloids, I realize I'm simplifying that a bit).

Turns out there was one field in one of the caching tables in the database that never got built when I upgraded the software for some reason. So every time every single page on the site was called up, not only wasn't the caching going on, but there were all sort of errors getting built as the system tried to access that field. It didn't affect the test server because I had caching turned off so I could play with changes in templates and stylesheets and modules. What was first thing I did when I installed the software on the live site? Turn on caching. What was the second thing I did when I installed the software on the live site? Watch the entire server crash as the database went berserk trying to write to and read that field. Grr. It made me appreciate why the favorite saying of one of the IT guys at my old job was "You're killin' me!"