The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Currently, the all day checkbox is weighted so that it's at the very top of the event entry form and the actual date setting is down near the bottom. So for one, it would be nice if they were together. In addition, I'd like to see an option in settings to move the whole thing as a unit to whatever weight you want. This is the way the locations module does it and it's a nice way to get around the locked weight from module added things.
Thanks,
Michelle
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | event.module_54.patch | 3.88 KB | Anonymous (not verified) |
| #4 | event.module_53.patch | 3.94 KB | Anonymous (not verified) |
| #3 | event.module_52.patch | 3.94 KB | Anonymous (not verified) |
| #1 | event.module_51.patch | 5.83 KB | Anonymous (not verified) |
Comments
Comment #1
Anonymous (not verified) commentedHere's a patch that does a few things:
1) groups the start date, end date, and all day fields into one field group
2) allows you to specify the weight for that fieldgroup on the event settings page
if you're using eventrepeat, see this http://drupal.org/node/131854 for a way to keep the repeat field together with the rest of the weighted event stuff.
Comment #2
michelleEvent All Day is gone, now, so that part isn't needed. Being able to move all the event controls is still needed,though. Can you re-roll this patch against 2.x? I don't believe 1.x is getting any new features.
Thanks,
Michelle
Comment #3
Anonymous (not verified) commentedTHanks, I didn't realize there was a 5.x.2.x version. Here's the weight patch for it.
Comment #4
Anonymous (not verified) commentedjust kidding! Here's the patch revised for a bug that causes an empty "Date/TIme" fieldset to display on every form.
Comment #5
Anonymous (not verified) commentedwhoops, wrong one. This is the fixed patch, i promise.
Sorry!
Comment #6
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.