Hi all,
I updated my 1.1.1 to 1.2.0a1 last night, and there is a page display issue that I haven't yet figured out. I thought it might be related to some changes in the CSS file, but I have confirmed I'm using the same file that the live tracker on this site is using, and the pages here display fine.
The site in question: http://www.blueninjasoftware.com/tracke ... g_page.php
As you can see, the filter settings are displayed fully, and are not collapsible. Both the expanded and collapsed versions are shown. Also, the table frames around the issue list are not visible. The table frame issue affects the bug view pages also, making them difficult to read.
Is there something else I need to do, or some file not in the 1.2.0a1 download package?
Thanks!
P.S. - this seems to affect any areas where collapsible items are used, such as the relationships section on the bug view page, etc. I have tried this not only in Firefox (without any script blocking or anything), as well as IE7 - so I don't think it's a browser/add-on issue.
1.2.0a1 page display issue.
Moderators: Developer, Contributor
-
Blue Ninja
- Posts: 16
- Joined: 23 Dec 2006, 20:57
- Location: CT, USA
- Contact:
-
Blue Ninja
- Posts: 16
- Joined: 23 Dec 2006, 20:57
- Location: CT, USA
- Contact:
Re: 1.2.0a1 page display issue.
Hmm, copntinued poking around found the likely cause - my config_inc.php had the line:
# CSS file
$g_css_include_file = '%path%css/default.css';
This conflicted with the value in the config_defaults_inc.php file, where %path% was not included. Oddly, this has worked since I originally installed Mantis, so I'm not sure why it didn't manifest itself until 1.2.0a1, but in any case, removing the duplicate value from the custom config file seems to have done the trick.
Looking forward to poking around with all the new goodies in this version!
# CSS file
$g_css_include_file = '%path%css/default.css';
This conflicted with the value in the config_defaults_inc.php file, where %path% was not included. Oddly, this has worked since I originally installed Mantis, so I'm not sure why it didn't manifest itself until 1.2.0a1, but in any case, removing the duplicate value from the custom config file seems to have done the trick.
Looking forward to poking around with all the new goodies in this version!