| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Renegade voting permissions |
SP> Actually just now after having a user modified to 151 and able to list, I s SP> the new user access to 151 and created one. That user had a blank list of SP> topics, so I tried the original user I tested with, and now that user doesn SP> have any topics when I list. This is really weird. Any ideas on where to di SP> in would be appreciated. NA> NA> Backup the VOTING.DAT file. Nuke it. Then create a zero-byte VOTING.DAT and NA> 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) SEEN-BY: 57/0 153/250 220/70 226/100 250/3 267/800 317/3 633/267 280 640/1384 SEEN-BY: 712/620 848 886 770/0 1 100 330 340 772/0 1 210 500 @PATH: 229/426 317/3 770/1 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.