Subj : Re: Small bug
To   : Mike Fenton
From : g00r00
Date : Wed Jan 04 2023 03:03 pm

 MF> 2023.01.04 13:33:16 Setting time left to 60
 MF> 2023.01.04 13:33:16 Setting menu to "" (Security start menu)
 MF> 2023.01.04 13:33:16 Error loading menu:

 MF> You can also just go into the user and do a CTRL+U select the security
 MF> level and it never changes the start menu for the user.

I was able to find the issue with that logging, thank you!  I am uploading a new build now which will include the fix.

As far as it not updating the user field when you upgrade the user security level, thats expected behavior.  Older versions would copy the start menu from the security into the user record, but now it just pulls the menu name directly from the security record.

The reason for the change is because if you wanted to change the start menu for a security level in the past you'd have to then go into each user's record and update their start menu field.  Now you can blank out all of the user's start menu fields and let it pull the menu from the system default or their security profile.  You'd only set the start menu directly on the user's record if you really wanted them to have their own custom start menu.

Hope I was able to explain that in a way that made sense lol.

On login:

If user record has a start menu defined, Mystic will use it.  If not, it will check their security level profile and use the start menu defined there.  If that is also blank, it will then use the default start menu defined in System Configuration > General settings.

.... My reality check just bounced

--- Mystic BBS v1.12 A48 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.