I have added some file areas to my Mystic BBS and set the access correctly
but they do not show up. Restarted MIS to see if the BBS needed a restart to see them, but the areas still do not show up.

Is there a trick to it that I am not seeing? I added them in the File Base editor like the others.

Thanks,


SHIFT838
FuSiON BBS
fusion.zapto.org:9900

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: FuSiON BBS (21:4/164)

I have added some file areas to my Mystic BBS and set the access
correctly but they do not show up. Restarted MIS to see if the BBS

Speaking from my own experience where, if memory serves, I set access to 255 rather than s255 and message groups didn't work, could you tell us what you have the access set to?

Personally, for my fsxNet areas, my List ACS is set to "s10z1".

That "1" puts it into my fsxnet group, which I have set up in the File Group Editor.

Likely you already have/knew all that, but I figured I'd ask anyway. And could you share more setup details?

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
* Origin: Storm BBS (21:2/108)

Hello SHIFT838!

On 03 Nov 2019, SHIFT838 said the following...

I have added some file areas to my Mystic BBS and set the access
correctly but they do not show up. Restarted MIS to see if the BBS
needed a restart to see them, but the areas still do not show up.

Try clearing the List ACS field of the file areas to see if they show up
then, just to rule out that possibility.

If you e.g. set the List ACS to "z2" you have to switch to (join) the corresponding file group from the Files menu before they'll show up in the
file area listing (for that group). As the List ACS determines whether an area will be listed and possible to switch to, but nothing else -- it does not regulate access in any other way.

Perhaps I'm stating the obvious here, though. :-)

Best regards
Zip

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

On 03 Nov 2019 at 08:53a, SHIFT838 pondered and said...

I have added some file areas to my Mystic BBS and set the access
correctly but they do not show up. Restarted MIS to see if the BBS
needed a restart to see them, but the areas still do not show up.

check you are using z ACS codes for file groups and not g ACS codes used with message groups, would be my first thought.

Also check ACS settings applied for the file group you are referencing

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I have the access set to s10g1 to List, s20g1 to read/post and s255 for admin
I have tried s10 and s20 but still the new area does not show up.

All the others work fine.


SHIFT838
FuSiON BBS
fusion.zapto.org:9900

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: FuSiON BBS (21:4/164)

these are local file areas so i'm using the g1 for group.


SHIFT838
FuSiON BBS
fusion.zapto.org:9900

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: FuSiON BBS (21:4/164)

I have the access set to s10g1 to List, s20g1 to read/post and s255 for admin I have tried s10 and s20 but still the new area does not show up.

Yeah, as Avon said, it's probably that it should be s20z1 with a 'z' rather than s20g1.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/64)
* Origin: Storm BBS (21:2/108)

Bingo.. i was not using the z for file groups!


SHIFT838
FuSiON BBS
fusion.zapto.org:9900

--- Mystic BBS v1.12 A43 2019/03/03 (Raspberry Pi/32)
* Origin: FuSiON BBS (21:4/164)

On 04 Nov 2019 at 07:44p, SHIFT838 pondered and said...

Bingo.. i was not using the z for file groups!

Yep had a feeling it was that, good you got it sorted and that others here
were able to help too - thanks guys!

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Bingo.. i was not using the z for file groups!

I did the exact same thing when getting Mystic configured the first time :)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Stellar Darkness BBS (21:4/162)