The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
![]()
Really confused at what I need to do. utf-8 with language 'character set' as utf-8.
Everything worked fine until server switch. Any advice would be greatly helpful... I'm stumped (and having a panic attack) and my users are now forced to see a black box with a question mark in it instead of foreign characters. Please, any ideas? Thanks |
#2
|
||||
|
||||
![]()
what did you set exactly as utf-8? Your database tables? Your site? vBulletin Settings?
|
#3
|
|||
|
|||
![]()
i didn't change anything after the move. That's just the database encoding, and the language parameter in vbulletin setting... thought that would help.
I'm guessing the new database doesn't have the same encoding as the last one. I don't know why this would be. I also don't know how in the world to change that.. |
#4
|
||||
|
||||
![]()
If you're using phpmyadmin, there's an option to change the collation for individual tables and fields.
I only have the newest pma version right now, but it should look something like this: |
#5
|
|||
|
|||
![]()
What would I switch it to?
|
#6
|
||||
|
||||
![]()
utf8_general_ci or utf8_bin
|
#7
|
||||
|
||||
![]()
You need to make sure that your new database is using the same collation and charset as your old database.
|
#8
|
|||
|
|||
![]()
Finally found it out.
Used this guide https://www.vbulletin.com/forum/show...hings-To-Check It was actually un-commenting the line within config.php thus manually setting the default connection for utf-8. Thanks for everyone's help. |
![]() |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|