Ok, thank you everyone. Right now hired programmer trying to catch these glitches and to find solution against em.
Printable View
Ok, thank you everyone. Right now hired programmer trying to catch these glitches and to find solution against em.
What has this got to do with You-Know-What? Don't understand what you guys are babbling about.
Apostrophes??? WTF?
"The Bitch of Hua Hin"
Come on, it can't be that difficult. It's quite obviously a bug in the DB library / ORM to protect against SQL injection attacks.
vBulletien taking over a year to come up with a fix is beyond ridiculous. Do you have any idea what would happen if I told my clients it's going to be a one year wait for me to come up with a fix like this? I'm pretty confident that in no time I'd besleeping on the street corner with the cockroaches.
Again, if you're unable to take care of it, and are unable to find developers to take care of it, then just via me root access via SSH, and I'll take care of it myself. It can't possibly be that difficult. Again, looks at the part of the code that checks against SQL injection, and I'm sure you will find your problem.
Sorry FRM, I couldn't see any mistakes there. Care to point them out?
Obviously, I don't actually think you're going to provide me with root access to the SGT server. Actually, I did have root for a while there, while the board was under Surfcrest's control.
Nonetheless, don't tell me this is a difficult problem to resolve. That's just stupid. You could contract this problem out to a $5/hour guy in India, and we would have it solved in an hour.
Don't be stupid.
Again, what do you think would happen if I tried pawning off these bullshit excuses on my own clients? I'd be immediately fired, and out of work, and rightfully so. Don't sit here and say this is a really complex technical issue that takes time to resolve, because we both know that's simply not true.
Ok, fine, up to you. This is a really complex technical issue that's out of your control, your hands are tied, and you're stuck waiting over a year for the devel team over at Infopop to come up with a solution.
Okie dokie. Got it.
You've previously confirmed to me the database tables are a UTF-8 charset, correct? So that can't be it. That means it's more than likely the DB layer of the software, so just take a look at the function(s) that protect against SQL injection attacks, and you will more than likely see your problem in there. This forum is PHP based, meaning you have the full plain text codebase sitting on your server, and PHP is an easy language.
Up to you. Don't sit here and say the problem is out of your control, and you're stuck waiting for over one year for the devel team at Infopop to release a patch. That's stupid. Again, if I tried something like that, I'd be homeless right now.
Offer is on the table for you though, if you want it. PM me, I'll give you my actual e-mail address, you can e-mail me the DB library file(s), and I'll take care of it. Christ, I'm blind, and I'll have this fixed in 30 mins.