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.
I am working with a site that will use many volunteers at all times of the day. When we test it out by setting up time slots for volunteers over several hours or days, we get only one time slot, 5-6 p.m visible (the entered as event started at 4 p.m)
Comment | File | Size | Author |
---|---|---|---|
#12 | weight-readme.patch | 1.12 KB | pwolanin |
Comments
Comment #1
SanDiego CreditAttribution: SanDiego commentedI am having exactly the same problem. No matter what time the event starts or how many volunteers can be chosen for each timeslot only one time slot is created and it starts at 5pm. If the duration is chosen 2 hours then 5-7pm, if one hour then 5-6pm. Does anybody know any workaround?
Comment #2
cmillet1 CreditAttribution: cmillet1 commentedI am having this problem as well. I have used this module before and it worked fine, but removed it and recently installed again to test. The only change since I lasted tested is that we upgraded from Drupal 5.2 to 5.3..
Comment #3
bRight2 CreditAttribution: bRight2 commentedYep same thing here. Only one timeslot, and always same hour... Drupal 5.3
It's a pity, was exactly what I was looking for to organize the shifts in a bar.
Greetz
Comment #4
pwolanin CreditAttribution: pwolanin commentedhmm - sounds bad - I'll take a look tonight.
Comment #5
pwolanin CreditAttribution: pwolanin commentedI'm just testing with the current version of event and this module - I don't see the problem. Are you sure you set the end time of the event later than the start time?
Comment #6
bRight2 CreditAttribution: bRight2 commentedYour right,
I did a clean install with event and volunteer module and it did worked...
I'll check my mainsite and try to find the conflicting module/theme (??) one of these days
I'm no programmer dough, I did used a correct (later) end-time :)
sorry for the fuzz;
b
Comment #7
pwolanin CreditAttribution: pwolanin commentedComment #8
SomebodySysop CreditAttribution: SomebodySysop commentedI've got the same exact problem, although the time slot that comes up is always 4:00 pm - 5:00 pm
no matter what I enter as start and end dates.
I know it's a configuration issue because the same module works on another site with the same version of event.
So, there is either a conflict with the theme or another module. Can you give me a bit of input about what the section that creates the slots is doing so I can try to figure out what other module/theme is causing this?
I did try re-installing volunteer module and updating event module, and at least 3 different themes with no better luck. Looks like there's some module conflict somewhere. I guess.
Thanks!
p.s. Got more info!
I have DBA module running on both sites (the one where event_volunteer works and the one where it doesn't). I created an identical event_volunteer node on each site:
Start date: 30 December 2007 1:00pm
End date: 30 December 2007 10:00pm
Timeslot length: 2 hours.
1 volunteer.
I submitted the node on both sites. I then went looked at the volunteer_timeslots table for each node record. In the timeslot_data field, the following appears:
So, it would appear that the timeslot_data field info being returned on the first site is NOT correct.
The other fields in each table from both sites are correct: timeslot_length num_volunteers timeslots_organizers
Hopefully this additional info can help someone point me in the right direction.
Comment #9
SomebodySysop CreditAttribution: SomebodySysop commentedWell, for anyone who might run into this problem, I fixed it in my case. How? I loaded the module weight module (http://drupal.org/project/moduleweight) and observed that the volunteer_timeslots module was weighted lower than the event module. Weighted the two the same, and bingo, it worked.
Comment #10
pwolanin CreditAttribution: pwolanin commentedAh - that would indeed be a problem. Did you change the weight of the event module at some point? Maybe I should add that to the README.
Comment #11
SomebodySysop CreditAttribution: SomebodySysop commentedI'm not sure what happened (perhaps during some upgrade), but all of my module weights seemed to have changed to "1" at some point. When I loaded volunteer_timeslots, it defaulted to "0". On the site where I didn't have a problem, all my modules were weighted at "0". Why the weights changed on the one site, I don't know. But, it would be good for someone having this problem that this is something they might want to take a look at.
Comment #12
pwolanin CreditAttribution: pwolanin commentedcommiting the attached patch text to the README file.
Comment #13
(not verified) CreditAttribution: commentedAutomatically closed -- issue fixed for two weeks with no activity.