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.
We don't have different status values per project.

My impression was, that I got it just when using anonymous access.

@cproensa do you think we should add project to the cache key?

        if( $t_stylesheet_path == 'status_config.php' ) {
            $t_stylesheet_path = helper_url_combine(
                helper_mantis_url( 'css/status_config.php' ),
                'cache_key=' . helper_generate_cache_key( array( 'user' ) )
            );
        }

Sorry @atrol: Version 2.12.0
Forgot with reporting bug. ( Why is it not possible to edit your own report bug / and or comments/activities on mantisbt butracker? )

Why is it not possible to edit your own report bug / and or comments/activities on mantisbt butracker?

I don't know. Someone configured this before I started to contribute to Mantis.
I assume there have been reporters that changed/deleted information, so that it became hard to understand the whole history of the issue after the changes.

I have no time to reproduce/fix at the moment
@TomR could you please try if changing core/html_api.php from

'cache_key=' . helper_generate_cache_key( array( 'user' ) )

to

'cache_key=' . helper_generate_cache_key( array( 'user', 'project' ) )

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

Hi @atrol,

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.

My impression was, that I got it just when using anonymous access.

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.

@cproensa do you think we should add project to the cache key?

Let's clarify if status enum can be changed per project.
I fear it may create a problem with filters.

I also noticed a long time ago that sometimes there is a situation with a black status.
I managed to achieve a stable reproduction of this situation.
Here is a sequence of actions that will lead to a black status:

1. Wait until the TOKEN_AUTHENTICATED expires under your user;
2. Go to account settings;
3. On the password entry page (login_password_page.php) of the current user, you need to completely update the page in any way (in google chrome it is Shift + F5);
4. Enter the password of the current user.

After that, all statuses will be displayed as black squares.

It is also possible that this behavior will be reproduced if the user for some reason remains on the login_password_page.php page during the reauthorization process until the page cache lifetime expires.
But so far I have not tried to reproduce this script.

I created a related issue in which I presented my solution. ( https://mantisbt.org/bugs/view.php?id=25892 )