Bug Illegal mix of collations/Custom Character Filter is not working

[ar2]

This comes instead of http://www.hdtv.com.pl/forum/members/rafankaminsk.html

Invalid query: Illegal mix of collations (latin2_general_ci,IMPLICIT) and (latin1_swedish_ci,COERCIBLE) for operation 'regexp'126

I think it may be consequence that Custom Character Filter is not working

'ą'=>'a'
'Ą'=>'a'
'ę'=>'e'
'Ę'=>'e'
'ó'=>'o'
'Ó'=>'o'
'ś'=>'s'
'Ś'=>'s'
'ł'=>'l'
'Ł'=>'l'
'ż'=>'z'
'Ż'=>'z'
'ź'=>'z'
'Ź'=>'z'
'ć'=>'c'
'Ć'=>'c'
'ń'=>'n'
'Ń'=>'n'

http://www.hdtv.com.pl/forum/members/rafankaminsk.html original name of acc is rafałkamińsk

 

[Fillip H.]

This means your database is using several different character sets, which is not supported. You need to manually edit all your database tables and all columns within each database to make sure they are all using the same character set. You'll need to contact your host if you don't know how to do this.

It's quite likely this is indeed the cause of your filter not working.

 

[ar2]

hmm but it was working correctly before instal dbseo with vbseo

 

[Fillip H.]

That's irrelevant. vBSEO stored its settings in a different format than DBSEO does. You can't compare the two products.

 

[ar2]

manually changed all character sets in dbseo tabels, nothing changed. Same error.

 

[Fillip H.]

You need to change all character sets for all tables in your entire database, and then set the correct default character set on a database level. Just changing DBSEO tables will not fix the root cause of the problem.

 

[ar2]

all vb relevant tables are in same char set, besides, this problem in my opinion is rather syntax error than char set because before dbeseo it was working fine. Or can you send me example of your httaccessss?

 

[ar2]

UP. Still not working.

 

[Fillip H.]

This has nothing to do with your .htaccess file, but it is related to your database. If you have access to phpMyAdmin, then please PM me with login information for the phpMyAdmin page and let me know what the correct character set is, and I will fix it for you

 

[Fillip H.]

I've upgraded DBSEO on your site to v1.2.9 and this issue appears to have been resolved