View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003241 | mantisbt | other | public | 2003-07-25 16:43 | 2008-08-11 09:41 |
Reporter | khuypen | Assigned To | vboctor | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.2.0a2 | ||||
Summary | 0003241: On Excel, no column headings display. | ||||
Description | The excel report displays the details of the bugs selected but no column headings so that you understand what you are looking at. | ||||
Tags | No tags attached. | ||||
Confirming for the latest CVS version. With 0.18.0a4, however, it does not show any data. Mantis version |
|
I have seen this issues with Apache 2.046 on Win2000 with IE 6, PHP 4.3.3, MySQL (Latest version) with 0.18.rc1. Although if you update your printing preferences they do show up. |
|
I removed a line in print_all_bug_page_excel.php, as following, <?php html_head_end() ?> <div id="Classeur1_16681" align=center x:publishsource="Excel"> <tr> titles desactivated for html pages
<?php |
|
I can't analyze the excel file which reported by mantis. edited on: 11-17-03 09:30 |
|
I have the same problem and it is related to the fact that the code tries to extract the user printing preferences but does not find any and therefore no headers are returned. This is simply resolved by removing a comment marker on line 171 of the file print_all_bug_page.php so that a new menu item will appear at the top of the page allowing you to set the printing options (i.e. choosing the fields that will be included in the report). Once a selection is made the Field Names appear in the first row of the resulting spreadsheet. |
|
Tried to followi in the note 0011624. But this change caused errors:
SYSTEM WARNING: Invalid argument supplied for foreach() |
|
This is a pretty serious bug - should I try one of the excel plugins instead? |
|
Has anyone verified this on 1.1.2 / 1.1.1 / 1.2.0a1? If I remember correctly, I've added this when I re-wrote Excel export code. |
|
I've confirmed that this is fixed in the latest trunk code. I believe the fix is available in 1.2.0a1. |
|