Issue 1220: Event rendering event on Google Chrome
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by romain.b...@gmail.com, Dec 22, 2011
I stumbled open an event rendering issue on Google Chrome (work on Firefox and IE, all latest versions).

I use paralelle jQuery ajax requests to register the event in the database (if successful, then  render event).

I use latest version of jQuery (7) and jQuery UI, and latest version of fullcalendar (1.5). Here is the part of my code :

/*
*	Modification d'un évènement
*	Envoie les modifications à apporter à un évènément en fonction de son ID et render le nouvel event
* 	edit mode : soit par le formulaire, soit en drag and drop
*/
function calenderRegisterEditedEvent(eventId, eventObject, editMode) {
	
	var theData;
	if(editMode === 'undefined') {editMode = "normal";}
	
	// Prépare les paramètres à envoyer à la page d'enregistrement dans la base de donnée "action.saveEvent.php"
	if(editMode == "drag") {
		
		theData = {
			eventId: eventObject.id,
			title: eventObject.title,
			start: eventObject.start + "",
			end: eventObject.end + "",
			allDay: false,
			notes: eventObject.notes,
			modifiable: true
		}
		
	} else if(editMode == "normal") {
		
		theData = {
		eventId: eventId,
		title:  $("#eventLabel").val(),
		start: $("#startDateDate").val() + " " + $("#startDateTime").val(),
		end: $("#endDateDate").val() + " " + $("#endDateTime").val(),
		allDay: false,
		notes : $("#eventNotes").val(),
		modifiable: true
		};
	}
	
	// Enregistre l'event dans la base de donnée (encode JSON du formulaire et sauve dans la base de donnée)
	$.ajax({
		type: "post",
		url: "ajax/action.updateEvent.php",
		data: $.param(theData),
		success: function(html) {
			
				// MOdifie l'évènement avec les memes infos qu'envoyées en base de donnée..
				if(editMode == "normal") {
					// eventObject.id = eventId,
					eventObject.title = $("#eventLabel").val();
					eventObject.start = $("#startDateDate").val() + " " + $("#startDateTime").val() + "";
					eventObject.end = $("#endDateDate").val() + " " + $("#endDateTime").val() + "";
					eventObject.notes =  $("#eventNotes").val();
					eventObject.allDay = false;
					eventObject.modifiable = true;
					
					$("#calendar").fullCalendar('updateEvent', eventObject);
				} // If mode == "drag", we have aldready moved the javascript event item so no update is necessayr. On update juste la base de donnée.
				
			// Affiche le message de succès
			helperMessage(html);
			
		},
		error: function(x, t, e) {
			// Do nothing for now
			helperMessage(e);
		}
	});
}

Dec 22, 2011
#1 romain.b...@gmail.com
Sorry, this is actually the add event function

/*
*	Ajout d'un évènement
*	Après la PopUp, enregistre la valeur de l'evt dans la base de donnée, renderEvent si succès
*/
function calendarRegisterEvent(startDate, endDate, allDay) {
	
	$("#message").html(startDate + endDate + allDay + " Test");
	
	// Régle le petit bug des allDay yes/no
	if(allDay == "no") {allDay = false;} else {allDay = true;}
	
	// Prépare les paramètres à envoyer à la page d'enregistrement dans la base de donnée "action.saveEvent.php"
	var theData = {
		title:  $("#eventLabel").val(),
		start: $("#startDateDate").val() + " " + $("#startDateTime").val(),
		end: $("#endDateDate").val() + " " + $("#endDateTime").val(),
		allDay: allDay,
		notes: $("#eventNotes").val(),
		modifiable: true
	};
	
	// alert($("#eventNotes").html());
	
	// Enregistre l'event dans la base de donnée (encode JSON du formulaire et sauve dans la base de donnée)
	$.ajax({
		type: "post",
		url: "ajax/action.saveEvent.php",
		data: $.param(theData),
		success: function(html) {
			
			// Dsiplays success message. Doit etre AVANT le render, sinon on ne peut pas récupérer l'ID !!
			helperMessage(html);
				
				// Ajoute l'évènement visuellement (seulement si l'ajax a répondu "succes" à l'enregistrement).
				// On doit reformatter les date en objet, puisqu'on récupère les modifs du formulaire d'ajout d'évènement
				$("#calendar").fullCalendar('renderEvent',
					{
						id: parseInt($("#thisevtid").attr("value")),
						title: theData["title"],
						start: $.fullCalendar.parseISO8601(theData["start"]),
						end: $.fullCalendar.parseISO8601(theData["end"]),
						notes: $("#eventNotes").val(),
						allDay: false,
						modifiable: true
					},
					true // Make the event "stick"
				);
				
				// Ajoute l'event à la source !
				// theData["id"] = parseInt($("#thisevtid").attr("value"));
			
				// Ajoute le nouvel event à la source
				// $("#calendar").fullCalendar().eventSource.push(theData);
				// var Test = $("#calendar").fullCalendar();
				// alert(dockydocsCalendar['firstHour']);
			// $("#calendar").fullCalendar('unselect');
			
		},
		error: function(x, t, e) {
			// Do nothing for now
			helperMessage(e);
		}
	});
	
}
Dec 22, 2011
#2 romain.b...@gmail.com
Here is where it come from (so its not really a fullcalendar issue). In Chrome, the text string format returned by the browser seems to be different from the one returned by Firefox. I used to format that text in PHP before inserting into the database to separate hours and minutes... (screenshots bellow)


Sans titre 6.jpg
39.6 KB   View   Download
Aug 14, 2013
Project Member #3 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #4 adamrs...@gmail.com
This message is being bulk-sent to a number of issues, both [very] old and new.

I have been working on taming this issue tracker, which has gotten out of control after months of neglect. You are receiving this message because I could not successfully reproduce the bug you were reporting with a reasonable amount of effort. I have written some new bug-report guidelines to be used by all bug reports going forward:

    http://arshaw.com/fullcalendar/wiki/Report-a-Bug/

Its salient point is that all bug reports should have an isolated demonstration, viewable online with a tool like JSFiddle.

If the bug you originally reported is still important to you, could you please first try the latest version of FullCalendar and see if it is fixed? If not, could you please file a NEW bug report that follows the new guidelines? This issue will not be monitored for further comments.

I'm sorry I have taken so long to respond to many of your request, and I'm sorry if this new procedure causes extra work for you. Going forward, the issue tracker will be much more of a well-oiled machine.

Again, if you must, PLEASE SUBMIT A *NEW* BUG REPORT (following the new guidelines) INSTEAD OF COMMENTING ON THIS ONE. Further comments on this report will be ignored. Thanks.
Status: Invalid
Labels: -Type-Defect Type-Bug