Page 1 of 1

One ticket gives white screen, then redirects

Posted: 25 Jun 2024, 05:03
by gurksallad
Hi

We had this very strange error during the morning. One particular ticket, that's been open for three months and last edited yesterday, now shows a blank screen when opening and redirects back to the bug view page. All other tickets are fine and opens as they should, but this one - number 3186 - is dead.

Reading the manual to setup error reporting and such, I have added this to the config:
$g_stop_on_errors = ON;
$g_show_detailed_errors = ON;
$g_display_errors = DISPLAY_ERROR_HALT;
$g_log_level = LOG_ALL;
$g_log_destination = '/tmp/foo';
However, we see no information, no log file, no nothing anywhere. We click ticket, white screen, back to bug view.

What's going on?



MantisBT Version 2.25.5
Schema Version 211
PHP Version 8.0.30
Database Driver mysqli
Database Version, Description 10.6.18, 10.6.18-MariaDB-ubu2204

Re: One ticket gives white screen, then redirects

Posted: 25 Jun 2024, 05:13
by gurksallad
I see now that the syntax for my log_destination was wrong, so now I got some logging.

BUT; I do not get anything for 3186. For any ticket, the log is flooded with great text, following everything that happens, but when opening 3186; _zero_. Not even one line of activity, prior going back to bug view.

Re: One ticket gives white screen, then redirects

Posted: 25 Jun 2024, 05:18
by gurksallad
Data is still in the database, all seems intact, so I have really no clue what's going on here 8O

Re: One ticket gives white screen, then redirects

Posted: 25 Jun 2024, 05:28
by gurksallad
I did one more test using the Email Importer plugin. I sent a testmail to the ticket and it got imported properly:
Start checking all mailboxes: Tuesday 25th of June 2024 07:26:49

Mailbox: Primary
Message: Reporter: 3 - some@email.add --> Issue ID: #3186




Done checking all mail

But I still can't open the ticket in Mantis.

Re: One ticket gives white screen, then redirects

Posted: 25 Jun 2024, 19:31
by atrol
I would upgrade in a first step to latest stable version (2.26.2 at the moment), or at least to 2.25.8.
In best case, this fixes your issue, e. g. some PHP 8.x related issues were fixed after 2.25.5.
If not, this is a better state to start more investigations as there will be no official fixes for 2.25.x.