• menu groups

    From Edmund Wong@1:153/7083 to All on Thursday, December 09, 2021 11:17:45
    Hi,

    Does anyone know if it's possible to create a menu system such that I can have separate areas dependent on groups? Like in the main menu, instead of
    a general Message area and a File area which can access every message/file area, I have two separate areas, 1 for local the other for fidonet.

    In each area, I can only select that area's message bases and file bases.

    For instance, I enter the Fidonet area, and I can access the
    Fidonet message bases and file bases only. When I select "Area change",
    it only lists Fidonet-only areas.

    Ditto with the local areas.

    Thanks

    Edmund

    ... What was the best thing before sliced bread?

    --- Mystic BBS v1.12 A47 2021/12/01 (Linux/32)
    * Origin: Eagle's BBS (1:153/7083)
  • From g00r00@1:129/215 to Edmund Wong on Thursday, December 09, 2021 11:05:50
    For instance, I enter the Fidonet area, and I can access the
    Fidonet message bases and file bases only. When I select "Area change", it only lists Fidonet-only areas.

    You can do what you want in many different ways, but the easiest would be to use the message group system. You will need to create a message group in the Message Group Editor called "FidoNet".

    After you have created the FidoNet group in the group editor, note the "ID" number associated to the group. For this example lets say your FidoNet group is ID 1 it will look like this in the list of groups within the editor:

    Message Group Name ID ---------------------------------------------------------
    FidoNet 1

    With the group created, you must now go into your Message Base Editor and set up the message bases that you want to show up in that group. Lets say you
    have a FidoNet base called "MYSTIC", and you open it up for editing. You will see a "List ACS" in the settings. This is what tells Mystic what the user must have to see that message base. Yours by default might look like "s20" which means the user must have a security level of 20 or higher to see it.

    If you add "g1" to the List ACS it will tell Mystic that the user must also be in group 1 in order to see the base in the list. So if you changed "s20" to "s20g1" and save the base, it will now only show up when the user has a security level of 20 AND has joined group 1 (which is your FidoNet group).

    As another example here is what my MYSTIC echo looks like in my message base configuration:

    Name | MYSTIC
    Base Type | Networked
    Echo Tag | MYSTIC
    List ACS | s10(g1|g5)
    Read ACS | s10(g1|g5)
    Post ACS | s20(g1|g5)
    Sysop ACS | s255(g1|g5)
    Net Address | 1:129/215 (FidoNet)

    My BBS uses a little more complex variation which allows the base to show up in two groups at the same time. My List ACS is "s10(g1|g5)" which means that the user must have a security level of 10 or higher, and be in either group 1 (my FidoNet group) or group 5 (All Message Bases group) to see the MYSTIC base.

    Now on my BBS when a user is logged in they must change to either the FidoNet or All Message Bases group using the Change Group option before they will see the MYSTIC echo.

    Hope this helps.
    --- Mystic BBS v1.12 A47 2021/12/06 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)