windows-1252 Encoding Error

[Cheater912]

When I installed vB 5, I got errors saying "Unsupported encoding" (from module.php).

It was reading XML files that had encoding="windows-1252" in the document header. So I changed them all to UTF-8 and it installed fine.

How can I fix this?

Thanks

[Wilamowski]

In Beta 15 it's the same problem???? WTF

- - - Updated - - -

Unexpected Text:
<?xml version="1.0" encoding="windows-1252"?>


Fatal error: Uncaught exception 'Exception' with message 'xml error Unsupported encoding, on line 1' in /volume1/web/vb5/core/vb/xml/import.php:161
Stack trace:
#0 /volume1/web/vb5/core/vb/xml/import/widget.php(18): vB_Xml_Import:arseFile('/volume1/web/vb...')
#1 /volume1/web/vb5/core/install/includes/class_upgrade_final.php(55): vB_Xml_Import_Widget->import('/volume1/web/vb...')
#2 /volume1/web/vb5/core/install/includes/class_upgrade.php(1571): vB_Upgrade_final->step_1(Array)
#3 /volume1/web/vb5/core/install/includes/class_upgrade_ajax.php(610): vB_Upgrade_Version->execute_step(1, 1, Array)
#4 /volume1/web/vb5/core/install/includes/class_upgrade_ajax.php(401): vB_Upgrade_Ajax->execute_step(1, 0, Object(vB_Upgrade_final), Object(vB_XML_Builder_Ajax), 1, NULL, 0, Array)
#5 /volume1/web/vb5/core/install/includes/class_upgrade_ajax.php(148): vB_Upgrade_Ajax->process_step('final', 1, 0, 1, NULL, 0, 0, 0, Array)
#6 /volume1/web/vb5/core/install/includes/class_upgrade.php(431): vB_Upgrade_Ajax->init(NULL)
#7 /volume1/web/vb5/ in /volume1/web/vb5/core/vb/xml/import.php on line 161

- - - Updated - - -

Hello, Vbulettin we pay for this, where it's help.
Helpdek say i'dont now what is this? maybe bug.
Great marketing

[Cheater912]

Finally a post!

[Wayne Luke]

We ship the files with encoding ISO-8859-1. This should work for all installation and upgrade purposes.

If you redownload the software are the XML files still encoded Windows-1252? What version did this occur in?

[Cheater912]

I'm on Beta 15. The XML files in the installer directory that still use Windows-1252 encoding are:
vbulletin-channels.xml
vbulletin-pages.xml
vbulletin-pagetemplates.xml
vbulletin-routes.xml
vbulletin-widgets.xml

<?xml version="1.0" encoding="windows-1252"?>

[Hartmut]

You are correct, i just reported this in JIRA: http://tracker.vbulletin.com/browse/VBV-5700

[Cheater912]

Thank you!

[Wilamowski]

OK, problem it's with this file:

core/install/vbulletin-widgets.xml
-routes.xml
-pagetemplates.xml
-pages
-channels.xml

You must changing kod inside file for <?xml version="1.0" encoding="ISO-8859-1"?> and save as ISO not windows latin

Congratulations to the team vbulletin, and we pay for them to fix bugs, and enough to "programmer" looked into the files and fix the mess in their ruling.
Shame

[Wilamowski]

Bravo for "programmers" from Vbulletin !!!!
In v16 the same bug!!!

[Wayne Luke]

Bravo for "programmers" from Vbulletin !!!!
In v16 the same bug!!!

Only the bugs listed in the announcement would have been fixed. Not every bug will be fixed between betas. If you want to track the issue then watch it in JIRA and you will receive an email when it is fixed.

http://tracker.vbulletin.com/browse/VBV-5700

[Wilamowski]

You are correct, i just reported this in JIRA: http://tracker.vbulletin.com/browse/VBV-5700

Bravo for "programmers" from Vbulletin !!!!
In v17 the same bug!!!

Maybe in paying beta nr 348 it's ok. Shame!!

[Wayne Luke]

Bravo for "programmers" from Vbulletin !!!!
In v17 the same bug!!!

Maybe in paying beta nr 348 it's ok. Shame!!

You're right. It will continue to exist until the issue is marked as fixed.

[Yves R.]

Bravo for "programmers" from Vbulletin !!!!
In v17 the same bug!!!

Maybe in paying beta nr 348 it's ok. Shame!!

I invite you to see the fixed release version in the given issue: