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.
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)
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,024 |
Nodes: | 17 (0 / 17) |
Uptime: | 08:27:12 |
Calls: | 503,208 |
Calls today: | 3 |
Files: | 224,779 |
D/L today: |
327 files (35,733K bytes) |
Messages: | 440,263 |