• Renegade voting permissions

    From Stettin Palver@1:229/426 to All on Wed Aug 14 20:16:51 2019
    I recently resurrected my old Renegade BBS going from 10.05 to v05-19.4. I have just about everything working but I have some odd behavior on the voting booth. I'm being forced to give s150+ access to vote, which includes being
    able to track votes and view user votes. I've tried editing the VOTING.MNU file to fiddle with permissions and it looks like even s50 should be able to vote, but when I create a user with that permission, hitting L to list topics doesn't show any topics. I have tried matching the s### on (t)rack vote and (u)ser votes moving the permission level lower, but that doesn't seem to keep the permission to view the list of votes. Something seems hard coded to the secuirty level to actually display the list. Any idea where I could change that level to something reasonable like s50? It looks like you must have
    s151 or greater to list, despite any VOTING.MNU access level settings.

    Actually just now after having a user modified to 151 and able to list, I set the new user access to 151 and created one. That user had a blank list of topics, so I tried the original user I tested with, and now that user doesn't have any topics when I list. This is really weird. Any ideas on where to dig in would be appreciated.

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Nick Andre@1:229/426 to Stettin Palver on Wed Aug 14 21:18:15 2019
    On 14 Aug 19 20:16, Stettin Palver said the following to All:

    Actually just now after having a user modified to 151 and able to list, I s the new user access to 151 and created one. That user had a blank list of topics, so I tried the original user I tested with, and now that user doesn have any topics when I list. This is really weird. Any ideas on where to di in would be appreciated.

    Backup the VOTING.DAT file. Nuke it. Then create a zero-byte VOTING.DAT and try this again. Check the voting permissions in Config - ACS Settings (C)

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Stettin Palver@1:229/426 to Nick Andre on Wed Aug 14 21:52:27 2019
    Actually just now after having a user modified to 151 and able to list, I s the new user access to 151 and created one. That user had a blank list of topics, so I tried the original user I tested with, and now that user doesn have any topics when I list. This is really weird. Any ideas on where to di in would be appreciated.

    Backup the VOTING.DAT file. Nuke it. Then create a zero-byte VOTING.DAT and try this again. Check the voting permissions in Config - ACS Settings (C)

    I will try that tonight, but I wanted to reply back here with another odd piece of information. My main goal was to provide a new user password to old users and have them log in and have everything work, including viewing voting. However it seems that after I verify the access works on a test user, then set the (A) New User access to s##, I must always edit the new user to be s##+1. For example I had it working with s201 on Testuser4. I changed new user access to s201, then magically Testuser4 couldn't see topics. I bumped Testuser4 to 202 and the topics returned. So I went back to new users being s50, then set Testuser to 50, no topics. Set to 51 and can list topics.

    E. Change a Vote: s150
    F. Add voting choice: s50

    Those seem to not affect the ability to _list_ topics

    Hopefully starting with a fresh .DAT resolves the oddity :)

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Stettin Palver@1:229/426 to Stettin Palver on Thu Aug 15 00:17:12 2019
    Backup the VOTING.DAT file. Nuke it. Then create a zero-byte VOTING.DAT and try this again. Check the voting permissions in Config - ACS Settings (C)

    I will try that tonight, but I wanted to reply back here with another odd piece of information. My main goal was to provide a new user password to ol users and have them log in and have everything work, including viewing voti However it seems that after I verify the access works on a test user, then the (A) New User access to s##, I must always edit the new user to be s##+1 For example I had it working with s201 on Testuser4. I changed new user acc to s201, then magically Testuser4 couldn't see topics. I bumped Testuser4 t 202 and the topics returned. So I went back to new users being s50, then se Testuser to 50, no topics. Set to 51 and can list topics.

    OK, I backed up the VOTING.DAT and created a new blank empty file. I added one test poll and confirmed it showed up ok on the test user. If I change the "new user" default permission to that of the working Testuser4, that user loses the ability to list polls until I add 1 to the security level. This is a bit frustrating, but at least I know how to work around it.

    I think I'll just start everyone out with s50 and manually bump them to 51 so they can see the voting topics.

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)