Closed (outdated)
Project:
FullCalendar
Version:
7.x-2.0
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
17 Feb 2012 at 13:16 UTC
Updated:
4 Jun 2025 at 19:58 UTC
Jump to comment: Most recent
Comments
Comment #1
simon georges commentedI just closed #1488656: Drag&Drop doesn't update the date field as a duplicate of this one.
Comment #2
awesini commentedSounds like the same problem for me. There seems to be an issue with Firefox. (I'm using 19.0.2 - Have also reset to factory default settings)
Actions:
1) Drag existing event to "new day".
2) Nothing updates (no messages) and I'm taken to page of the node.
3) Hit F5 to refresh and I can see the date in the node update with the "new day".
Same actions above but in Chrome, IE, Opera, Safari:
1) Event is changed/updated.
2) Messaged displays "The new event time has been saved."
I've tried 7.x-2.0, 7.x-2.x-dev.
What's even more bizarre is that we have another test environment and there are no problems in Firefox! I even exported/imported the same view and I still get the problem described above.
Please help!
Comment #3
awesini commentedFYI, solved my issue by using older fc libraries. "fullcalendar-1.4.10.zip"
Get them here: http://arshaw.com/fullcalendar/download/
Comment #4
parasolx commentedI don't know if this solution could be related to this issues.
Updating date field need two values, which is start date and end date. In certain condition, the date field only consist of start (or one date enter) only. This could make the error to thrown out since the second value is not found.
So, just try to apply a simple patch in fullcalendar.module (line 170)
to:
So, if second value didn't exist, it will take first value.
Comment #5
dcam commentedI've volunteered to help clean up the FullCalendar issue queue. As part of that effort I'm closing issues open for unsupported versions of the module as "Closed (outdated)". That includes any Drupal 7-compatible versions because no active maintainer is supporting them.
If this issue is still relevant for version 3.x of FullCalendar, then feel free to re-open it and update the issue version number.