Brinkster updated their mysql server and I have an error.

I have the same problem still looking for a fix, I can still use my blog if I turn off all my plugins (which I cant turn back on now anyway).

my post:
https://www.ads-software.com/support/topic/75929?replies=8

is this what yours is doing?

same problem here
not much help from brinkster live support
ill post if i can figure anything on it
ppppppppeeeeeeeaaaaaaaaccccccceeeeeeeeeeeeeeeeee

I will not touch the plugins until I have the mysql problem fixed.

Have you seen https://software.newsforge.com/article.pl?sid=06/06/01/213223&from=rss , the link given by brinkster support?

Do you get something out of it in relation to our problem?

Juan

When I call they emailed me the link and told me to look for a patch (from wordpress) and that wordpress should have been built to run with the new back slash workin.

So what version of WP are you all running, at the least, upgrade to 2.0.3 and see if it works.

If not, then put a bug against WP in https://trac.www.ads-software.com.

Regards

2.0.3 for me, (did update last night hoping to fix the problem) but had alot of the same problems with 2.0.1 but with it I could turn on my plugins only for them to deactivate themself about 5 min later.

I took a look at the MySQL 4.1.20 Changelog and as far as I can tell this fixes a issue within MySQL. Therefore it looks like it doesn’t require changes in the calling (for instance WordPress) programs.

And I would expect more people to experience this issue if it was a WordPress related issue.

Try asking them which version they were running before the upgrade. Maybe it’s something else that was changed that’s causing this issue.

I have this problem too.

I think the bit at the end of that article is what the problem is. I’d say since my phpMyAdmin is telling me that the MySQL version running is 5.0.15-nt that Brinkster has taken the second option.

Rather than upgrading to 5.0.22, they have taken the
sql-mode=NO_BACKSLASH_ESCAPES approach. *cough* slack *cough*

I’m guessing that the backslash escaping for apostrophes is tightly built in to WordPress?

Just posted ticket #2820 at https://trac.www.ads-software.com/report/1
about this matter.

Juan

I don’t think it’s WordPress’ fault. Slash escaping is a documented part of MySQL.

I asked Brinkster if they had a 5.0.22 install they could move me to and got my hopes high when they said ‘yes’. It turned out to just be 5.0.19 and they don’t actually have anything higher. Go Brinkster support!

i reupped all wordpress files to my host
didn’t change anything………..

I reuploaded wordpress no help here either, I was using Gallery2 it wacked out also ??

All I can think of is to try a code I used when I was younger: up, up, down, down, left, right, left, right, b, a, select start I will try this and let you know if it helps ??

thanks for cheering me up

I got this from Ryan at https://trac.www.ads-software.com/report/1 ticket 2820

Wed Jun 14 00:21:29 2006: Modified by ryan
NO_BACKSLASH_ESCAPES will break WP. Backslash becomes a normal character rather than an escape character when that flag is set. This will cause queries to fail, as you have found out.

Good, now I know what the problem is. So, what does it means, no more blogs? no more WordPress? no more Brinkster?

I have two blog applications with problems and don’t know what way to go.

Complain to Brinkster that they should upgrade their MySQL to a version which fixes the security issue instead of relying on workarounds which break a lot of software out there.

From the MySQL page I linked above:
If you are unable to upgrade MySQL to a version that includes the fix for the bug in mysql_real_escape_string() parsing, but run MySQL 5.0.1 or higher, you can use the NO_BACKSLASH_ESCAPES SQL mode as a workaround. (This mode was introduced in MySQL 5.0.1.) NO_BACKSLASH_ESCAPES enables an SQL standard compatibility mode, where backslash is not considered a special character. The result will be that queries will fail.