I'm coding in a date of birth for registered users on a new archive, and I've made it check to see if the user is over thirteen or not. If they are, then all is well, but if they're not, then they get a permission denying them registration. This is all fine and well, but I don't want it to be okay for them to simply hit back, change the year, and voilΓ : registered.
I'm toying with cookies at the moment -- not the greatest barrier, I know -- but because the header is already sent, it won't create the cookie.
How can I get around it?
ETA: I'm using sessions at the moment, but I think I'd rather try cookies. :3
archive:
site:
Available for skin/mod commission! π
Have it save their email in a permission denied table would be more permanent.
Ah yeah, that would probably be better. We were planning on having a "possible problem" table to log people who might register again with fake details. Thanks, Tammy!
archive:
site:
Available for skin/mod commission! π
I've been thinking of trying to do something that in my head I've been calling "User Control" because of the huge number of duplicate accounts at my site. Perfect Imagination has something really cool, where they look at similar usernames, emails, passwords, and DOB and find people who've signed up more than once. (They also have an alert system for when people change their DOB, which is maybe more relevant to this particular post.) Anyway, does that sound like what you're talking about for the "possible problem" table, Jenny? If so, sweet. Need any help?
Not yet! Although I'll let you know if I do. I'm still messing around with it, to be honest, and yep at the possible problem table. π I was originally thinking of signing them up to the authors table (with a dummy password/email) so then if they tried registering again, it would block them via eFic's controls, but it seemed rather silly and excessive. So the problem table would contain all you said (and even though IPs are sort of 'sketchy' to use for logs, probably that) and then it will log it, and, well, we'll use it to compare the data.
I've actually got it set so they only input their DOB in at registration, and it's not editable at a later date. I figured that if it was accurate, then the DOB wouldn't need to be changed at all. So, I've set it up so it's only "modifiable" at registration.
I'm not sure if I'm going to release it as a public mod at the moment; not sure on how many people want it, and Tammy has it planned in the next version already. I think it probably needs a lot of testing... This is what I did:
- added "dob" to the authors table
- added a date of birth field to editbio.php (set as an <input> field for registration)
- set up some if/else to determine whether the field was entered correctly, and the important bit: whether they're over a certain age
- changed the reg. query to add dob in
... and yep. It's also for the ratings, too. At the new archive, we're trying to keep out under-16s to view certain ratings, so we're trying to configure how the ratings/warnings work and all that jazz. π Fun stuff. It's the only way we can figure out how to keep a "restricted section" though without too much modding. I don't want to be another eFic deviant. π
archive:
site:
Available for skin/mod commission! π
For the user's security, I would just ask for Month and Year. I absolutely HATE it when sites ask for the whole thing.
*snip*
We would love you forever at the JoBros archive if you released it. We've been cracking down on under 13 users because we've kinda reached that critical mass point (closing in on 20k memebers) and we're trying to be as legally compliant as we possibly can.
(We also wait awhile to convert to new eFiction releases because any bugs result in 15k+ whiny e-mails)
Skins made by Kali are no longer supported!
For the user's security, I would just ask for Month and Year. I absolutely HATE it when sites ask for the whole thing.
Is that what the v4 will be like?
I'll think about it. I can see it from a user perspective, but also from the admin perspective. =/
Also, is there any logical way to try and make a 'restricted' section with warnings? I can hard-code the warnings in, I just want to do something like blocking no age-consented people from SEEING that a story is there. I guess that's the extreme version though. π
Is it possible to change the age consent digit anywhere else from "Edit Preferences", by the way? We're using it in conjunction with Registered Users Only, but I don't want it to be bypassed with ?ageconsent=ok or something. =/
kali, I'll let you know. It still needs a lot of testing. π
archive:
site:
Available for skin/mod commission! π
v4 is just going to ask whether or not they're over 13 and it'll do it before the register form is displayed. They can still go back and lie, but they can do that no matter what you do.
There is a javascript ?ageconsent=ok option. You'd have to take that out of viewstory.php and the function in corefunctions.php that builds the title links.
Oh right!
Thanks. π
archive:
site:
Available for skin/mod commission! π
I have a general theoretical run-down of this mod if anyone wants to try? Please let me know. I need some testers with time. π
archive:
site:
Available for skin/mod commission! π
I can test it.
Question: how does it handle people who have already signed up? Ignores them? Or does it make them enter a DOB at some point?
I've made it so if its empty, the person can edit it in the edit bio. I'm not sure about it though. D: I'll e-mail you all relevant info. π Thank you!
archive:
site:
Available for skin/mod commission! π
I can test it on my test archive(s) if you like.
Skins made by Kali are no longer supported!
That would be awesome -- thanks. π
archive:
site:
Available for skin/mod commission! π
