• Odd Menu Behavior

    From Phil Kimble@1:128/2 to All on Mon May 14 01:05:14 2018
    Hi Guys,

    I am setting up custom menus in mystic -cfg in Slackware 14.4 64bit.

    I have 2 ansi text files, main.ans and mail.ans with exact same permissions. mail.ans is a copy (cp main.ans mail.ans).

    In the Menu Settings, I have tried several differemt approaches, but mail.ans will not display. main.ans displays no issues.

    In Menu Settings -> Display File = main
    No problems, displays as expected.

    In Menu Settings -> Display File = mail
    Does not display file.

    And adding it into |DFmail doesnt work either.

    I deleted the menu altogether, recreated, and still no luck. I delete the mail.ans file & recreate it from main.ans, edit it in & save using the Mystic Ansi Editor, still no luck. Lastly, I created, from scratch, a very simplistic text file using Mystic Ansi editor and it still doesnt show. I am baffled...

    Any advice/recommendations??

    Thx
    Phil


    --- Msged/LNX 6.1.2
    * Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)
  • From Paul Hayton@3:770/100 to Phil Kimble on Mon May 14 20:03:18 2018
    On 05/14/18, Phil Kimble pondered and said...

    I have 2 ansi text files, main.ans and mail.ans with exact same permissions. mail.ans is a copy (cp main.ans mail.ans).

    both are in the text directory and have the same permissions right?

    In the Menu Settings, I have tried several differemt approaches, but mail.ans will not display. main.ans displays no issues.

    Are you trying to display mail.ans in a different menu or just change out the main.ans for mail.ans in the main menu you're editing?

    And adding it into |DFmail doesnt work either.

    Adding it where?

    I deleted the menu altogether, recreated, and still no luck. I delete the mail.ans file & recreate it from main.ans, edit it in & save using the Mystic Ansi Editor, still no luck. Lastly, I created, from scratch, a
    very simplistic text file using Mystic Ansi editor and it still doesnt show. I am baffled...

    Deleted which menu?

    Does the mail.ans display OK in the ansi editor?

    Best, Paul

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Phil Kimble@1:128/2 to Paul Hayton on Mon May 14 22:30:30 2018
    Hi Paul,

    Lets redefine what I am doing for clarity - creating a second theme. I have the
    default theme & creating a second theme with customized menus & display files (ansis).
    My directory structure is
    /opt/mystic/themes/default
    /opt/mystic/themes/newtheme
    both have thier own text,script, & menus subdirectories.

    I have 2 ansi text files, main.ans and mail.ans with exact same
    permissions. mail.ans is a copy (cp main.ans mail.ans).
    These are located in the newtheme/text/ directory

    both are in the text directory and have the same permissions right?
    Yes

    In the Menu Settings, I have tried several differemt approaches, but
    mail.ans will not display. main.ans displays no issues.
    What I doscovered is that mystic is looking for the mail.ans file in the /default/text directory MOT the /newtheme/text.

    Are you trying to display mail.ans in a different menu or just change
    out the
    main.ans for mail.ans in the main menu you're editing?
    Customizing for a new theme

    And adding it into |DFmail doesnt work either.
    Adding it where?
    Editor->Menu->Settings

    I deleted the menu altogether, recreated, and still no luck. I delete
    the mail.ans file & recreate it from main.ans, edit it in & save using
    the Mystic Ansi Editor, still no luck. Lastly, I created, from
    scratch, a very simplistic text file using Mystic Ansi editor and it
    still doesnt show. I am baffled...

    Deleted which menu?
    It doesnt matter if the ansis are in the /newtheme/text directory as long as they are in the /default/text.
    Does the mail.ans display OK in the ansi editor?
    Nope.

    I validated this by renaming the /default/ directory to BogusDef & no screens would display under the newtheme theme. As soon as Mystic located the ansis in default/text, it displayed. Both default & newtheme paths are correct in the themes editor. Even with /opt/mystic/text directory, Mystic is looking for the default theme when displaying text files (ansis) that belong to a different theme.

    Best, Paul

    -+- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    + Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz
    (3:770/100)
    Thanks for the help!!
    Phil

    --- Msged/LNX 6.1.2
    * Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)
  • From Paul Hayton@3:770/100 to Phil Kimble on Tue May 15 20:20:44 2018
    On 05/14/18, Phil Kimble pondered and said...

    Lets redefine what I am doing for clarity - creating a second theme. I have the default theme & creating a second theme with customized menus & display files (ansis).
    My directory structure is
    /opt/mystic/themes/default
    /opt/mystic/themes/newtheme
    both have thier own text,script, & menus subdirectories.

    OK thanks :)

    I have 2 ansi text files, main.ans and mail.ans with exact same
    permissions. mail.ans is a copy (cp main.ans mail.ans).
    These are located in the newtheme/text/ directory

    OK

    What I doscovered is that mystic is looking for the mail.ans file in the /default/text directory MOT the /newtheme/text.

    Yep and if you want to see your new menus / ansis etc. you need to change the theme you are using when you are logged in.

    Do this by heading to the 'account settings' menu (usually option A from the default main menu) and then select option K 'language' this is actually the option to change the active theme the user is setting.

    Another option is while not logged in head to mystic -cfg > editors > user editor > choose your user name > then press page down key to to get second screen 'SETTINGS 1' then alter the field called 'Theme' to use the new theme you want your user to now use upon login.

    I think this is the root of your issue... I hope :)

    Best, Paul

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Phil Kimble@1:128/2 to Paul Hayton on Tue May 15 21:32:40 2018
    On 05/14/18, Phil Kimble pondered and said...

    Lets redefine what I am doing for clarity - creating a second theme.
    I have the default theme & creating a second theme with customized
    menus & display files (ansis).
    My directory structure is
    /opt/mystic/themes/default
    /opt/mystic/themes/newtheme
    both have thier own text,script, & menus subdirectories.

    OK thanks :)

    I have 2 ansi text files, main.ans and mail.ans with exact same
    permissions. mail.ans is a copy (cp main.ans mail.ans).
    These are located in the newtheme/text/ directory

    OK

    What I doscovered is that mystic is looking for the mail.ans file in
    the /default/text directory MOT the /newtheme/text.

    Yep and if you want to see your new menus / ansis etc. you need to
    change the
    theme you are using when you are logged in.
    But I am editing from mystic -cfg >Editors >Theme >Menu >/S >View

    Not logged in at all

    Do this by heading to the 'account settings' menu (usually option A
    from the
    default main menu) and then select option K 'language' this is
    actually the
    option to change the active theme the user is setting.

    I will give this a try
    Another option is while not logged in head to mystic -cfg > editors > user
    editor >> choose your user name > then press page down key to to get
    editor >> second
    screen 'SETTINGS 1' then alter the field called 'Theme' to use the
    new theme
    you want your user to now use upon login.

    I think this is the root of your issue... I hope :)
    This would only make sense if I was logged on. But I am in mystic -cfg > Editors > Menus

    Best, Paul
    Thanks for the help. I will gve these a try...
    -+- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    + Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz
    (3:770/100)

    --- Msged/LNX 6.1.2
    * Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)
  • From Paul Hayton@3:770/100 to Phil Kimble on Fri May 18 19:55:41 2018
    On 05/15/18, Phil Kimble pondered and said...

    What I doscovered is that mystic is looking for the mail.ans file in
    the /default/text directory MOT the /newtheme/text.

    Yep and if you want to see your new menus / ansis etc. you need to change the
    theme you are using when you are logged in.
    But I am editing from mystic -cfg >Editors >Theme >Menu >/S >View

    Not logged in at all

    Do this by heading to the 'account settings' menu (usually option A from the
    default main menu) and then select option K 'language' this is actually the
    option to change the active theme the user is setting.

    I will give this a try

    Phil, how did you get on?

    Best, Paul

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Phil Kimble@1:128/2 to Paul Hayton on Sun May 20 00:10:08 2018
    On 05/15/18, Phil Kimble pondered and said...

    What I doscovered is that mystic is looking for the mail.ans
    file in the /default/text directory MOT the /newtheme/text.

    Yep and if you want to see your new menus / ansis etc. you need
    to change the
    theme you are using when you are logged in.
    But I am editing from mystic -cfg >Editors >Theme >Menu >/S >View

    Not logged in at all

    Do this by heading to the 'account settings' menu (usually
    option A from the
    default main menu) and then select option K 'language' this is
    actually the
    option to change the active theme the user is setting.

    I will give this a try

    Phil, how did you get on?
    It finally clicked. I removed all reference in mystic -cfg of the default theme & renamed default directory to defBAK. NewUser has only one choice & does not sk for theme. I basically forced the bbs to use the newTheme.

    Mystic complained very loudly about not being able to locate the default theme in the error log. Then it complained it couldnt locate the newTheme theme. A very stubborn personality.

    Then logging in locally took a few attempts before mystic finally picked it up.
    I am not 100% convinced that it is mystic causing the issues, may be the OS injecting some issues. But it is a clean installation of Slackware 14_64.

    My next challenge is trying to solve the "Unable to find mystic.dat".

    Best, Paul

    -+- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    + Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz
    (3:770/100)

    --- Msged/LNX 6.1.2
    * Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)
  • From Paul Hayton@3:770/100 to Phil Kimble on Sun May 20 21:13:28 2018
    On 05/20/18, Phil Kimble pondered and said...

    Then logging in locally took a few attempts before mystic finally picked it up. I am not 100% convinced that it is mystic causing the issues, may be the OS injecting some issues. But it is a clean installation of Slackware 14_64.

    I'm glad you got the problem sorted :)

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From Phil Kimble@1:128/2 to Paul Hayton on Sun May 20 21:20:34 2018
    On 05/20/18, Phil Kimble pondered and said...

    Then logging in locally took a few attempts before mystic finally
    picked it up. I am not 100% convinced that it is mystic causing the
    issues, may be the OS injecting some issues. But it is a clean
    installation of Slackware 14_64.

    I'm glad you got the problem sorted :)
    I am thinking it is more of an ESXi/Slackware/MysticBBS issue than just a MysticBBS error. I was editing menus last night & getting odd delays. Thinking
    it is a memory/terminal window problem. I rebooted the VM, allocated more RAM to it & another processor...

    -+- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    + Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz
    (3:770/100)

    Thx,
    Phil

    --- Msged/LNX 6.1.2
    * Origin: Bayhaus.net - Colorado Springs - Serving the FrontRange (1:128/2)
  • From Stephen Walsh@3:633/280 to Phil Kimble on Mon May 21 21:01:40 2018
    Hello Phil!

    20 May 18 21:20, you wrote to Paul Hayton:

    I am thinking it is more of an ESXi/Slackware/MysticBBS issue than
    just a MysticBBS error. I was editing menus last night & getting odd delays. Thinking it is a memory/terminal window problem. I rebooted
    the VM, allocated more RAM to it & another processor...

    I run my setup under EsXi 5.5, with 1gb of ram, 1 cpu, centos 6.9 and don't have any issues with editing
    things via a ssh session from my linux mint 18.3 pc.




    Stephen


    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Dragon's Lair ---:- dragon.vk3heg.net -:--- (3:633/280)