View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0024189||mantisbt||bugtracker||public||2018-03-30 03:50||2019-05-13 14:16|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0024189: Some statusses become 'Black'|
Some statusses become 'Black',
I saw some issue here before which were closed, however I find this is still actual.
In my config_inc.php I have $g_status_enum_string defined with all possible statusses in all projects. ( Added some constants into custom_constants_inc.php ).
|Steps To Reproduce|
Change between projects with different statusses.
Ctrl-F5 is retrieving status colors.
I guess it has something to do with 'caching' in css/status_config.php?
|Tags||No tags attached.|
|related to||0020079||new||Custom status colors not working when displaying issues from another project|
|related to||0023324||closed||cproensa||Generated css, js code should be cached by browser|
|related to||0024563||closed||atrol||Status button always black|
|related to||0025755||resolved||atrol||Status icons change to black|
Which version do you use?
Some discussion related to different stats enums in different projects 0023324:0057633
For the record, I saw a similar behavior (all squares black on `My View" page) on www.mantisbt.org/bugs some days ago.
My impression was, that I got it just when using anonymous access.
@cproensa do you think we should add
Sorry @atrol: Version 2.12.0
I don't know. Someone configured this before I started to contribute to Mantis.
I have no time to reproduce/fix at the moment
fixes the issue?
Hi @atrol, would like to try, but the line
'cache_key=' . helper_generate_cache_key( array( 'user' ) )
is not available in source code css/status_config.php?
I checked in freshly downloaded source MantisBT 2.12.0
Sorry for the quick comment.
I found out hat to change line 224 of core/html_api.php
And YES, this seems to fix the issue!
Sorry, it's in core/html_api.php
Edit: Crossed post.
I have experienced that too, after anonymous access, but in my system the status enum is unique for global config, so this may not be the same issue as reported here.
Let's clarify if status enum can be changed per project.
|2018-03-30 03:50||TomR||New Issue|
|2018-03-30 04:25||atrol||Relationship added||related to 0020079|
|2018-03-30 04:25||atrol||Status||new => feedback|
|2018-03-30 04:25||atrol||Note Added: 0059357|
|2018-03-30 05:32||atrol||Relationship added||related to 0023324|
|2018-03-30 05:35||atrol||Note Added: 0059358|
|2018-03-30 05:45||atrol||Note Added: 0059359|
|2018-03-30 06:09||TomR||Note Added: 0059361|
|2018-03-30 06:09||TomR||Status||feedback => new|
|2018-03-30 06:43||atrol||Status||new => feedback|
|2018-03-30 06:43||atrol||Note Added: 0059364|
|2018-03-30 06:43||atrol||Product Version||=> 2.12.0|
|2018-03-30 06:52||TomR||Note Added: 0059365|
|2018-03-30 06:52||TomR||Status||feedback => new|
|2018-03-30 06:57||TomR||Note Added: 0059366|
|2018-03-30 06:57||atrol||Note Added: 0059367|
|2018-03-30 06:57||atrol||Status||new => feedback|
|2018-03-30 06:58||atrol||Note Edited: 0059367||View Revisions|
|2018-03-30 06:58||atrol||Status||feedback => acknowledged|
|2018-03-30 06:59||cproensa||Note Added: 0059368|
|2018-06-25 03:28||atrol||Relationship added||related to 0024563|
|2018-06-25 03:30||atrol||Note Edited: 0059364||View Revisions|
|2019-05-13 14:16||atrol||Relationship added||related to 0025755|