Download & Extend

COPPA module - strange behavior

Project:COPPA
Version:6.x-2.x-dev
Component:Code
Category:bug report
Priority:critical
Assigned:Unassigned
Status:needs review

Issue Summary

Hi there - I am trying to test out the COPPA module and have set things up according to the COPPA page. I have downloaded and installed a brand new instance of Drupal 6.10 and have just put COPPA on there. I have noticed the following:

1) When I sign up a new user, it doesn't ask for my parent's email address. Then, when I submit the form, it creates the new user, and then comes back with the new user form with the parent's email address. But when I try to create a new record from that, I get a whole bunch of code at the top of my screen.
2) The current site that I would like to put this on uses a text field for the birth date (it was set up incorrectly, but now we have a number of users and I don't want to have them all reset their birthdates for this.) Is there a way to have the module work on a string instead of a date field?
3) I cannot for the life of me figure out the proper setup so that the role that you create as the COPPA role is the default for a user who was born less than 13 years ago. The use case is this:
a) I am 33 years old and sign up. COPPA checking should not be enforced for me.
b) My 3 year old son wants to sign up. I have a "Child" role that is very restrictive and is the role specified in the COPPA settings. I would like the site to automatically assign him to the Child role based on his birth date.
c) When I log in and click the Sign Coppa Compliance, it says I have no children. I thought that when my child signed up, he would have been able to specify my email address or user name to automatically link us together, but the only way I see that we can do this is through the administration section. This would be tedious.

Please let me know if I need to develop this functionality on my own or if I am just not doing things correctly.

Thanks,

Scott

Comments

#1

Component:Code» Documentation
Category:bug report» support request

Scott,

1. can you provide the code returned?
2. not currently, and I don't foresee this as likely being developed in the future.
3. a. COPPA checking will see that you are 33 and not apply (assuming that the birth date field is setup properly)
b. You can instead apply coppa to the authenticated role or some other user role that all users are put into. Careful though as this will require the DOB field to be set properly or you may lock users out.
c. Currently relationships are managed through the admin UI only.

To explain better for 3 a/b. If you have a user who potentially should have COPPA apply to then they should be a member of the COPPA role whatever you determine that to be. The important distinction is that users in this role are expected to have a properly populated DOB field or they will potentially be locked out of the system. If the user is over 13 then COPPA status does not matter as the checking is skipped if they are 13 or under then they must pass the proper COPPA checks.

#2

Jeff,

Thanks for the help so far. It's been a busy month, so I only have returned to this now. I've tried a new drupal installation (v6.12), and the only thing I've added to it is the COPPA for Drupal 6 dev module, then autoassignrole module, and the James Andres patch. I think it's working well now - except for this:

When the user signs up, they can put in their birthdate, but the issue is that it creates the account, then presents a new user signup screen with the parent's email address there. So, it will create the account, send the login information to the email address, but the parent's email address hasn't been filled in yet. Therefore, we would never know who is the parent of who. A solution to this could be that when the birth date is checked, a page is returned to explain that they need their parent's permission, and then they could enter their parent's email address.

Let me know what the feasibility of something like this would be. I do not have any php experience, but could probably learn pretty quickly....but is there any way to check the age prior to creating the account in the User hook?

Thanks,

Scott

#3

Hi,

I am going through the same problem.
If i add the hook_validate to validate the profile_dob field, will that help?
I greatly appreciate your help.

#4

Status:active» postponed (maintainer needs more info)

Please try the 6.x-2.0-beta1 release and report back.

#5

Hi,

I have encountered the exact same issue as Scromie. I have a required birthdate field on my registration page. When it is filled out the form submitted, the page is refreshed to the registration page, except this time with the addition of the parent email field that should have been there when the birthdate was shown as being under 13.

Basically, there is no way for the user to fill out a parent email when they register. I am not really sure how to approach this issue.

Ideally, the user would enter their birthdate, and upon submission would be shown a screen that asks them to enter their parent's email so that they can be informed and give consent.

Also, where is the code for the email that the parent receives?

Thanks,

Dave

#6

Thanks for the module!

Working on a series of patches to get the COPPA module working with Drupal 6 and Content Profile integration.

Quick overview of patches:
coppa.admin.inc --

  • Made a few changes to check type and field for content profile integration.
  • Correct date of birth and user link.

coppa.module --

  • Made a few changes to help support a more automated process (link parent and student during registration).
  • Added case 'delete' to hook_user to keep the coppa database tables clean.
  • Updated coppa_get_dob to work with content profile (cck fields).
  • Updated profile form dob.
  • Updated the coppa_age function to calculate and return user age.

coppa_email.install --

  • Updated schema coppa_email to store cid instead of pid.

coppa_email.module --

  • Added a submit function to clear form storage upon submit.
  • Added code to the form_alter hook that attempts to retain form data when rebuilding with request for parent email.
  • Added code to the validate function to properly validate and support the changes in the form_alter function.
  • Added a function to return child id if parent email is in the coppa_email database table. (Used in coppa.module).
AttachmentSize
coppa.admin_.inc-443982-6.patch 2.53 KB
coppa.module-443982-6.patch 4.83 KB
coppa_email.install-443982-6.patch 960 bytes
coppa_email.module-443982-6.patch 2.86 KB

#7

Component:Documentation» Code
Category:support request» bug report
Priority:normal» critical
Status:postponed (maintainer needs more info)» needs review
nobody click here