On a session timeout, the login theme is displayed using default theme instead of selected theme

Bug #1006308 reported by Don Schoeman on 2012-05-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When the current login session is timed out and the user attempts to enter a menu, PHPDevshell displays the login screen as it should. However, the login screen uses the default theme instead of the theme selected for the Log In|Out menu. The only way to re-produce this bug is to let the session expire, deleting the session file does not produce the same problematic result.

Changed in phpdevshell:
status: New → Confirmed
assignee: nobody → TitanKing (titan-phpdevshell)
TitanKing (titan-phpdevshell) wrote :

I have tried this and could not replicate the problem as such. I have noted this to be confusing settings rather. In this case I think you have forgotten to set the Default Theme in the "General Settings" ui. To resolve this I have improved the Theme Manager to better handle theme assignment and set default themes also for general settings preventing confusion.

As a note, remember to update the include path for your custom theme.

TitanKing (titan-phpdevshell) wrote :

Would you please be so kind as to state wether this issue is now resolved either by means of using the information given or using the new feature in Theme Admin.

Changed in phpdevshell:
status: Confirmed → In Progress
Don Schoeman (don.sch) wrote :

The Default Theme was set to our custom theme when this problem occured so that wasn't the problem. I can unfortunately only test the new changes once we've reintegrated the latest PHPDS changes into our own project. Will let you know as soon as possible whether the changes made a difference or not.

TitanKing (titan-phpdevshell) wrote :

Ok Good, I have tested the following with an alternative theme.

1. Custom login theme, for normal permission requests and session timeouts.
2. Tested all other pages too (404.php, 403.php) etc.

In my tests it did work and I could not replicate the problem. This could have been a recent fix that repaired this problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers