Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hi all,
First bug reported, so please bear with me.
The user of the system reported that when you download the CSV roster : ?q=node/6/signups/print/html or /csv ... there are three instances of each person who signed up. Eeach person shows up three times with the exact same information.
In the Signups list (?q=node/xx/signups), the people only show up once.
Now, if I got to a users "Current Signups" : ?q=user/xx/signups .. the same event shows up three times!
There is only one "Event" in the database table "event" .. also, there is only a single entry in "node" as well.
Correcting this is quite an urgent situation for me, so any help would be appreciated!
Thanks,
dg
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | three.png | 20.02 KB | dropgear |
| #1 | Screenshot-1.png | 11.93 KB | dropgear |
| #1 | modules.txt | 4.43 KB | dropgear |
Comments
Comment #1
dropgear CreditAttribution: dropgear commentedHi all,
Still need help here. On the advice of a drupal savvy friend, I've tried some debugging steps:
1. The following is a list of modules I have installed related to signup:
Signup 5.x-2.4
Signup Scheduler 5.x-1.0
Signup Status 5.x-1.x-dev
Signup Status Certificates 5.x-1.x-dev
Signup Status Log 5.x-1.x-dev
Signup Status Mailer 5.x-1.x-dev
Token 5.x-1.10
Event 5.x-2.x-dev
Event All Day 5.x-2.x-dev
Event Views 5.x-2.x-dev
I've disabled, and re-enabled every one of these, and the problem persists as long as I can see a list of signups.
Also No, none of the users have clicked the submit button 3 times :) They were all single signups until ... something happened. To my understanding, people started being marked as "Paid" (Signup Status), and from that point forward, there are 3 entries for each user.
Attached are two PNG files that illustrate the problem.
Also, a list of all of the modules in my system .. maybe someone can point me to what else I should be enabling or disabling.
Hopefully this will help!!
Thanks,
dg
Comment #2
dww- Do you have a test site? (If not, you need one). ;)
- On your test site, can you reproduce the problem with just signup.module enabled? If so, there's a bug here.
- If not, turn on the other signup-related add-ons (signup_status, etc, etc) 1 by one, and see if/when you start seeing the problem. That'll help narrow down the source of the bug.
?q=node/6/signups/print/html isn't a path that this module even provides. I'm not sure where that's coming from: which add-on module is providing it, if it's a view, etc, etc. Probably, it's a view, and there's some bug in the view definition. But, I can't really help you much unless I know where that list is being generated. It's certainly not my code. ;) The best I can do is probably help you re-classify this issue into the right queue so the appropriate person looks at it.
Comment #3
dropgear CreditAttribution: dropgear commentedHi dww,
On the advice of one of my friends I created a local test copy to try to reproduce the problem.
The problem persists with only SignUp enabled, BUT it's because SignUp Status has had three entries for each person at some point ("Registered", "Not Paid", "Paid"), which matches the business process the people using it are employing.
Anyways, I did a "SELECT * FROM signup_log ORDER BY form_data" and sure enough there are three identical entries for each person that has been registered.
uid nid anon_mail signup_time form_data Ascending status completion_time cert_id
26 6 1212147522 a:15:{s:10:"First Name";s:11:"xxxx";s:9:"La... 4 1212765615 2
26 6 1212147522 a:15:{s:10:"First Name";s:11:"xxxx";s:9:"La... 4 1212765615 2
26 6 1212147522 a:15:{s:10:"First Name";s:11:"xxxx";s:9:"La... 4 1212765615 2
34 6 1212170882 a:15:{s:10:"First Name";s:12:"yyyy";s:9:"L... 4 1216230361 28
34 6 1212170882 a:15:{s:10:"First Name";s:12:"yyyy";s:9:"L... 4 1216230361 28
34 6 1212170882 a:15:{s:10:"First Name";s:12:"yyyy";s:9:"L... 4 1216230361 28
.. so that's where the three entries are coming from. I'm going to clean up the database manually, and see where that takes me :)
Anyways, this is probably a SignUp-Status issue. If someone would like to re-classify .. that'd be great.
dg
Comment #4
dwwComment #5
jrbeemanComment #6
dwwThis bug doesn't exist in the (re-written) D6 version of signup_status. If it's broken in D5, it's probably going to stay broken, since I don't think any of the signup_status maintainers still care about the D5 version.