View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014721 | mantisbt | printing | public | 2012-09-19 20:05 | 2014-12-08 02:08 |
Reporter | phyllisl | Assigned To | dregad | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | closed | Resolution | fixed | ||
OS | SLES | OS Version | SLES11_64bit_SP2 | ||
Product Version | 1.3.0dev | ||||
Target Version | 1.3.0-beta.1 | ||||
Summary | 0014721: Error page when generate summary in HTML format | ||||
Description | This is actually from testing the nightly build 1.3 Mantis. After finishing the installation and created the first ever bug report(logged in as administrator), if user clicks summary->print reports->Internet Explore icon, it gives a page with following error: XML Parsing Error: XML or text declaration not at start of entity | ||||
Steps To Reproduce | click summary->print reports->Internet Explore icon | ||||
Additional Information | Mantis Version: The installation was done by following the guide online at: Also, attached is the config_inc.php of this server. The page content is copy pasted from the installation result without modification. | ||||
Tags | No tags attached. | ||||
Attached Files | config_inc.php (9,744 bytes)
<?php $g_hostname = 'localhost'; $g_db_type = 'mysql'; $g_database_name = 'bugtracker'; $g_db_username = 'root'; $g_db_password = 'mAntis'; $g_crypto_master_salt = 't3rJRrII0IjPfo+66SgQpo2YMZ/IOHpNUnSCpftNa7w='; ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | ||||
related to | 0014744 | closed | dregad | Unicode characters in text field prevent bug display |
related to | 0015721 | closed | grangeway | Functionality to consider porting to master-2.0.x |
related to | 0014748 | closed | dregad | XML Parse Error when having jpg image as attachment in summary report in HTML |
related to | 0014811 | closed | dregad | Summary page doesn't generate properly because of special characters |
It now gives a new error after updating the file. |
|
I cannot replicate this. |
|
Sorry to confuse you. Actually I made a mistake while applying the patch. Now the error should be: |
|
Looks like the error is caused by data in one of the issues being exported, causing incorrect html to be generated. Would you be able to
|
|
I tried to remove the lines that caused the problems from source file, and the report was finally printed, but apparently, all the special characters that should be printed out just like other text (see:Should Successfully print out like this) are causing trouble in 1.3 |
|
That's not what I asked. I'm looking for a sample of data (the special chars you mention) that breaks so I can reproduce the problem locally and hopefully fix it. Your screenshot does not help. |
|
Oct 31 04:33:51 sn2-b-1 ADE: |12020111 28657 000003 THRD TMSM 2008-10-31T04:33:51.559966| NOTICE 0674 THRD: xÆ·xÆ· Sorry about that, would this help? |
|
OK, I can confirm there's an issue. I fact, in 1.3 I'm not even able to add a note with the data you provided in 0014721:0032939. I have opened a new issue 0014744 to track this. Please follow-up there. |
|
Additional issue identified by atrol (see 0014811:0033158). |
|
Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch |
|
MantisBT: master 8ae62f36 2012-09-21 00:03 Details Diff |
Fix 0014721: XML Parsing Error in print_all_bug_page_word.php Revised code so that generated page complies with xhtml 1.0 strict DTD. |
Affected Issues 0014721 |
|
mod - print_all_bug_page_word.php | Diff File | ||
MantisBT: master 63548c7a 2012-09-21 00:03 Details Diff |
Additional XML Parsing Error in print_all_bug_page_word.php Error is triggered when Custom Fields contain html special characters. Fix 0014721 |
Affected Issues 0014721 |
|
mod - print_all_bug_page_word.php | Diff File |