It'd be nice if users with the privilege to create events could click a date in the calendar and get the event creation form, with that date preselected.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

killes@www.drop.org’s picture

Hmm, does this make sense usability wise? Wouldn't you expect to get a list of events on that day? I think I should mark this as "undesirable" or "won't fix".

asimmonds’s picture

FileSize
27.29 KB

Maybe something like the SunONE calendar, with a '+' symbol on each day for event addition. Screenshot attached.

skip’s picture

Done as shown in the screenshot, I think this would be a great benefit.

+1.

killes@www.drop.org’s picture

The feature looks interesting. I'll accept patches for it. :)

darrian’s picture

Included in the reoccuring event patch I submitted is this feature. See http://drupal.org/node/view/4122

-Darrian

darrian’s picture

Attached is a small patch for just this feature.

You will also need to modify event.css:

remove:
.event-calendar div.day {}
add:
.event-calendar div.day span.this {} /* for the number */
.event-calendar div.day span.addevent {} /* for the + sign to add events */

ricabrantes’s picture

Version: » 5.x-2.x-dev
Status: Active » Closed (fixed)

This topic this closed because of the time without answers

dww’s picture

Status: Closed (fixed) » Needs review

This shouldn't have been closed. There was a patch, it just needs review. I doubt it still applies, but it's still a good idea. ;)

flickerfly’s picture

A patch at #145205: Add 'all day' flag to dates that claims to fix this while adding an All Day Event feature as well.

--- Sorry, I was bouncing from Date Issue Queue to here and neglected to notice the project change. This is not applicable to the Event module.

urbanlegend’s picture

Issue summary: View changes
Status: Needs review » Closed (outdated)

Given that this issue has not been updated in 7 years or more, I am closing this ticket as outdated (no longer needed and/or relevant). However, if anyone feels this represents an issue that is still being encountered in the current version of Drupal, please reopen and/or provide additional comments.