Good Monday Morning

[Toni KatVixen]

Originally Posted by docholly

Morning..
I'm in a piss-foul mood myself. One of the blogs we maintain was upgraded but the articles are now in reverse order and the T-Girl is nowhere to be found. I have the client buzzing me every 3 minutes on googletalk to get it fixed. I'm sure there is a button somewhere in the dashboard but phuck if i can find it.

That happened to one of my blogs yesterday....gggrrrr.......and it was not upgraded.

I even checked my settings that I haven't messed with in years. The only settings that I could find that would effect it is under Options<Reading

I am not too pleased to say the least.

[docholly]

Originally Posted by Toni KatVixen

That happened to one of my blogs yesterday....gggrrrr.......and it was not upgraded.

I even checked my settings that I haven't messed with in years. The only settings that I could find that would effect it is under Options<Reading

I am not too pleased to say the least.

Apparently it has to do with our host upgrading their php whatever scripts and making my current copy of wordpress obsolete. It would have be nice to be notified.. but WTF do I know..

sorry it happened to you.. and apparently on the version that i was using there is not a 'button' fix but has to do with the actual script.

[cd34]

Originally Posted by docholly

Morning..
I'm in a piss-foul mood myself. One of the blogs we maintain was upgraded but the articles are now in reverse order and the T-Girl is nowhere to be found. I have the client buzzing me every 3 minutes on

Originally Posted by Toni KatVixen

That happened to one of my blogs yesterday....gggrrrr.......and it was not upgraded.

This was my fault. Mysql released a security advisory, that particular machine showed that the exploit had been attempted unsuccessfully (along with two other machines) and we upgraded it to the suggested 'secure' release of mysql. However, the release that was suggested contains the following bug:

http://bugs.mysql.com/bug.php?id=32202

A regression bug like this shouldn't occur in mysql -- and it wasnt expected, and I apologize. Machines are upgraded quite frequently due to security patches and while I did do quite a bit of internal testing on mysql on two of our test machines, neither would have hit that particular bug. We've downgraded mysql and applied a workaround for now.

Normally for security updates, we don't really make announcements because each machine probably gets 3-4 security patches a week applied. However, we will include a blog of sorts that lists updates made to machines to at least make diagnosing things like this go a little quicker.

Again, I do apologize.

[docholly]

Originally Posted by cd34

This was my fault. Mysql released a security advisory, that particular machine showed that the exploit had been attempted unsuccessfully (along with two other machines) and we upgraded it to the suggested 'secure' release of mysql. However, the release that was suggested contains the following bug:

http://bugs.mysql.com/bug.php?id=32202

A regression bug like this shouldn't occur in mysql -- and it wasnt expected, and I apologize. Machines are upgraded quite frequently due to security patches and while I did do quite a bit of internal testing on mysql on two of our test machines, neither would have hit that particular bug. We've downgraded mysql and applied a workaround for now.

Normally for security updates, we don't really make announcements because each machine probably gets 3-4 security patches a week applied. However, we will include a blog of sorts that lists updates made to machines to at least make diagnosing things like this go a little quicker.

Again, I do apologize.

My concern was not with you but the fact that my personal slave and tech support guru wasn't available. Coupled with the fact that almost none of what you said means anything to me, makes me think I really need to read "Web terms for Dummys" but thanks for the apology, our client is a MAJOR chore..

Sparky threw himself >>> |bus|