Hello, guest. We have noticed that you are not registered at this bug tracker. Your experience will be greatly enhanced if you log in. To do so, you first must register by clicking on the Register tab at the top. If you are already registered, you can login at the Login tab.
Syndicate Syndicate Listing Display Search Login/Register
Bug Id ?
Reporter ?
Dalai-Lama
Product/Version ?
Bugdar / 1.2.1
Status ?
Closed
Severity ?
Moderate
Duplicate Of ?
- none -
Fixed in Revision ?
Mstone ?
Summary ?
XML Error while updating or creating a bug
Report Time ?
September 22, 2007 02:11 AM
Assignment ?
Resolution ?
Fixed
Priority ?
Normal
Dependencies ?
- none -
Mstone (old) ?


Votes
For: 0 (0%)
Against: 0 (0%)
Total: 0

September 22, 2007 02:11 AM Dalai-Lama
This is the error i get approx 90% of the times when i update or create a bug on my bugdar
XML Error: Invalid character at line 17 colunn 39 in /framework/xml.php on line 151

This happen on any browser.

My bugdar if you wanna test :
http://www.starshine-online.com/bugdar/

PHP: 5.2.0-8
MySQL 5.0.32

September 22, 2007 04:01 PM Robert
Are you using a language other than the default (en_US)? If so, make sure you copy locale/en_US/emails/ to your locale directory. If you're not, have you changed any of the XML files?

September 22, 2007 05:43 PM Dalai-Lama
I'm using the default en_US language and i never touch to any files :)
Maybe it's a problem with UTF8 / ISO ? Or things like that ?

September 23, 2007 12:04 AM Dalai-Lama
With more tests, we find that the problem come from accents and special characters.
The Apache default encoding is ISO-8859-1
(AddDefaultCharset ISO-8859-1)

We think that it come from there, but is there a way to bypass it, 'cause we can't change our server to UTF-8

September 23, 2007 03:05 PM Robert
Have you changed any of the language settings in the Admin CP? Also, what version of Bugdar did you initially install -- did you start at 1.2.1 or did you upgrade to it?

September 23, 2007 05:11 PM Dalai-Lama
I don't think we have changed any of the languages settings in admin CP
I can give you admin access to my bugdar if you need some testing ?
We first install the 1.2 then upgrade to 1.2.1, but the bug was also there in the 1.2

September 26, 2007 03:04 PM Robert
Can you check two things for me: first, what collation are you using for your MySQL database? Second, can you add this line to includes/config.php:

$debug = 1;

Then reproduce the error and copy the output for me. This will allow me to see exactly what is failing and where. After you do this, you should remove the line you added.

Sorry I'm a little slow to respond.

September 27, 2007 12:45 AM Dalai-Lama
My MySQL Database collation are all "latin1_swedish_ci"

This is what i have show with the debug line :

Error: Fatal
XML Error: Invalid character at line 2 colunn 98 in /framework/xml.php on line 151
Debug Stack:

#0 trigger_error(XML Error: Invalid character at line 2 colunn 98, 256) called at [/home/starshine/public_html/bugdar/framework/xml.php:151]
#1 XML::parse(
Starshine-Online Bug Tracker Bug Notification - potentiels toucher complètement dingues
Hi Fafhrd,

You are receiving this email because you have opted to get notifications for the Starshine-Online Bug Tracker bug tracker.

The bug is "potentiels toucher complètement dingues" (id: 86) located at http://www.starshine-online.com/bugdar/showreport.php?bugid=86

Here are the notices:
###################################################################

The status of the bug is now "Confirmé", from "Non confirmé".

###################################################################
If you no longer want to receive email from us, please log into your account and click the "My Controls" tab at the top of the screen to change email preferences.

http://www.starshine-online.com/bugdar
, 1) called at [/home/starshine/public_html/bugdar/includes/class_notification.php:594]
#2 NotificationCenter::finalize() called at [/home/starshine/public_html/bugdar/editreport.php:227]

October 6, 2007 05:15 PM Markus Staab
to override the default charset from the webserver, you can send a php header

header('Content-Type: text/html; charset=utf-8');

October 10, 2007 11:51 AM Markus Staab
on our bugdar this problem also occurs

October 10, 2007 12:51 PM Robert
Markus, can you give me your collation as well? I think this bug is MySQL related, but I'm not sure.

October 10, 2007 01:34 PM Markus Staab
our hoster uses a very old mysql version, without collation support (3.23.58)

October 10, 2007 04:15 PM Robert
Are you using a language other than English that has accented characters?

October 10, 2007 04:28 PM Markus Staab
no, we use default en_US.

see
http://bugs.bmodul.de/

October 10, 2007 04:38 PM Robert
Does the problem happen every time or only on certain occasions?

October 10, 2007 07:20 PM Markus Staab
only rare in certain situations

October 12, 2007 07:04 PM Robert
I have a feeling this is related to encodings. Are you using PHP5?

April 30, 2008 03:23 PM whatrevolution
Error: Fatal
XML Error: not well-formed (invalid token) at line 16 colunn 113 in /framework/xml.php on line 151


Identical error, occurs on http://bugs.movsq.net

April 30, 2008 03:27 PM whatrevolution
Response headers from the server on which I found this bug:

Date: Wed, 30 Apr 2008 15:31:24 GMT
Server: Apache/1.3.33 (Unix) mod_ssl/2.8.22 OpenSSL/0.9.7d SE/0.5.2
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Pragma: no-cache
X-Powered-By: PHP/4.4.0
Set-Cookie: btuserid=5; expires=Thursday, 30-Apr-09 15:31:24 GMT; path=/
Last-Modified: Wed, 30 Apr 2008 15:31:24 GMT
Content-Encoding: gzip
Content-Length: 1922
Keep-Alive: timeout=3, max=32
Connection: Keep-Alive
Content-Type: text/html; charset="utf8"

200 OK

October 14, 2008 02:22 PM Robert
This is fixed in 2.0 because email text has gone back translatable strings rather than XML files.