Edit box blank due to special characters in post

[richtv]

vBulletin 3.8.7 Patch Level 2
PHP 5.4

After searching around [google] I found it was due to special characters. The posts which cause that blank box, after clicking the Edit button, for my situation had the € euro symbol.

I read in the following post a possible fix but that case was for vB4

http://www.vbulletin.com/forum/forum/vbulletin-sales-and-feedback/licensed-customer-feedback/407073-php-5-4-support-released-march-1st-2012?p=3623114#post3623114

Can you offer a possible solution for me? thanks.

[Renate]

vBulletin 3.8.7 Patch Level 2
PHP 5.4

After searching around [google] I found it was due to special characters. The posts which cause that blank box, after clicking the Edit button, for my situation had the € euro symbol.

I read in the following post a possible fix but that case was for vB4
http://www.vbulletin.com/forum/forum...14#post3623114

Can you offer a possible solution for me? thanks.

I do have vBulletin 3.8.9 and the same problem with special caracters not apearing in a quote (for example written privé and posted the reply you only see priv) or installation after installing a German de_DE language applinet everything written after priv has been lost. I have looked everywhere on the internet and no answer has to be found. Seemingly there are very few people having this problem and thats why no solution can be found.The database collatie has Utf8_general_ci everywhere. Languagemanager of vB says 'The locale 'de_DE' could not be located on this server'. So after that I found 'Although Synology uses the UTF-8 character encoding for the file system their Linux does not have internationalization support built in. Because of that the JavaVM running CrashPlan is not able to handle non US-ASCII characters. As a result CrashPlan will not be able to back up files and directories with non US-ASCII characters in their names.' but there was a way to fix this although I was not intending to use CrashPlan I did not menage to do so. I am not that familiar with Linux.

Still, when I ask 'locale -a' it shows de_DE as one of the used languages. Aperently it seemed to be an Synology/Server/Linux issue I could not solve, but after searching for days finaly intending to give up and do everything in english and without special caracters.

[Wayne Luke]

Open your includes/config.php file and find this line: // $config['Mysqli']['charset'] = 'utf8';

Uncomment it by removing the //, save the file and reupload it to your server. Does this solve the issue?

[Renate]

Open your includes/config.php file and find this line: // $config['Mysqli']['charset'] = 'utf8';

Uncomment it by removing the //, save the file and reupload it to your server. Does this solve the issue?

Thank you for the reply but I tried this and it did not work out.

[Wayne Luke]

Please upgrade to 3.8.9.

[Renate]

Please upgrade to 3.8.9.

As you can see in the beginning of my quote I use 3.8.9.

[Wayne Luke]

Sorry was looking at the first post. This is one reason why we ask customers to create their own threads even if they think they have the same issue as another.

What version of PHP and MySQL are you using? What is the character set and collation of your MySQL database? Are these applied to all fields so that they are the same as well? What encoding is your language set to in the AdminCP?

[Renate]

Sorry was looking at the first post. This is one reason why we ask customers to create their own threads even if they think they have the same issue as another.

What version of PHP and MySQL are you using? What is the character set and collation of your MySQL database? Are these applied to all fields so that they are the same as well? What encoding is your language set to in the AdminCP?

Hello Wayne.Thank you for the reply. As I said, there is nothing to be found on the internet abouth this problem and I was suprised to find someone here who expirienced the same kind of problem. I did all the research I could and as I wrote the collation fields are all the same (everywhere) as you can see here above.

Databankserver
Server: Localhost via UNIX socket
Servertype: MariaDB
Serverversie: 5.5.43-MariaDB - Source distribution
Protocolversie: 10
Karakterset van server: UTF-8 Unicode (utf8)

Webserver
Apache
Client-versie van databank: libmysql - mysqlnd 5.0.11-dev
PHP-uitbreiding: mysqli Documentatie

phpMyAdmin
Versie-informatie: 4.3.0


Synology Nas seems to have his own kind of PHP as they call it MariaDB. I think the caracter problem is best subscribed above whith a not functionable CrashPlan because of the caracters. It looks like vBulletin is not able to write in the database because of those strange caracters and therefore don't show them.

[Wayne Luke]

Well the problem is that vBulletin 3 was never designed to support UTF-8. UTF-8 characters are stored in 2 or 3 bytes. Sometimes those additional bytes signify an end of string value so the string is ended. Since no real change or bug fixes have been applied to the software for this issue since 2007-2008, that can cause problems on modern systems. We don't interact with Crash Plan which is a backup service so it has no relevance here.

Try removing the values at vBulletin Options -> vBulletin Options -> Censorship Options -> Blank Character Stripper. Then repost some of the content that is causing the problems. Old content won't be fixed, it would have to be edited.

[Renate]

Well the problem is that vBulletin 3 was never designed to support UTF-8. UTF-8 characters are stored in 2 or 3 bytes. Sometimes those additional bytes signify an end of string value so the string is ended. Since no real change or bug fixes have been applied to the software for this issue since 2007-2008, that can cause problems on modern systems. We don't interact with Crash Plan which is a backup service so it has no relevance here.

Try removing the values at vBulletin Options -> vBulletin Options -> Censorship Options -> Blank Character Stripper. Then repost some of the content that is causing the problems. Old content won't be fixed, it would have to be edited.

CrashPlan indicates just the problem I am experiencing, the database does not accept strange caracters so there will be no registration of them (see attachment).

Your suggestion removing the values there did not help.

Editing will be a hell of a job and I did some changes (changed k in können) by hand with no result on the behavior (still showing k instead of können).

[kh99]

Can you post a link to your forum?

[Renate]

Can you post a link to your forum?

My forum is not in public yet, it is on a Synology Nas to configure everything to my liking. Yesterday evening I tried a german language.xml and from that point even the regular text in English is now in German and not readable anymore because all the forumtext stops after every ö/ü/é/á. I deleted everything and start all over.

[Wayne Luke]

Can I ask why you're trying to use vBulletin 3.8.X?

[Renate]

Can I ask why you're trying to use vBulletin 3.8.X?

I pushed the wrong buton so I lost the reply and have to do it again. So in short now I was a member of a vBulletin forum version 3.8.5. the guy wanted to quit so I took ik over from him. I heard that although I took it over I had to buy a license, which I did. However I was alowed now to download and use the latest version, which was 4.2.3., I still use the first layout I have and which I like very much. For the purpose of getting familiar with another vBulletin forums I downloaded version 3.8.9 which has the same layout on my NAS and which is not working because of the caracters. Now I am trying version 4.3.2. but I already can say, I don't like.