SMF 1.1.14 Database Error.

[ssdevious]

Greetings,

I recently updated to 1.1.14, but now on name-change, I'm getting a Database error.

It says that Database is @ 1.1.11, but forum @ 1.1.14, how do I get rid of this / update the database?

Best Regards,
~tEh'Pâr4d0x

[Illori]

the version in the database is usually not worth changing, what is the exact error you are getting?

[ssdevious]

Database Error

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Pâr4d0x' OR memberName LIKE '~tEh'Pâr4d0x')
LIMIT 1' at line 4
File: /home/x10jac/public_html/main/forum/Sources/Subs-Members.php
Line: 935

Note: It appears that your database may require an upgrade. Your forum's files are currently at version SMF 1.1.14, while your database is at version 1.1.11. The above error might possibly go away if you execute the latest version of upgrade.php.

This is it.

Thanks for any help,
~tEh'Pâr4d0x

[Illori]

looks like you have a user that registered with a name that is causing issues. you might need to get access to phpmyadmin and find the user and give it a new name or delete it.

[Taglar Dreskk]

I'm curious about this error message as well.  We have been using SMF for 3 years now and have allowed our members to use apostrophes in their names.  But it seems like after updating to 1.1.14 anyone who changes their displayname to one with an apostrophe in it gets the same error as above.

In previous versions, this was not an issue.

[Taglar Dreskk]

Can anyone confirm if something was changed not allowing apostrophes in display names for 1.1.14?  Because, like I said, we had been using them before, now all of a sudden I'm getting errors.

[Rich N-O]

I'm curious about this error message as well.  We have been using SMF for 3 years now and have allowed our members to use apostrophes in their names.  But it seems like after updating to 1.1.14 anyone who changes their displayname to one with an apostrophe in it gets the same error as above.

In previous versions, this was not an issue.

We are experiencing exactly the same problem. Any help would be appreciated.

[Taglar Dreskk]

Glad to hear others have the same problem.

So far the only resolution I have found is that the new stable 2.0 version of the forum does not have this issue.  We had already planned to migrate to this version in January...but this means we are stuck with the "problem" until then.