Issue 1404: Resizing the DIV and caledar row that holds the events and not an event resize
Status:  Invalid
Owner: ----
Closed:  Aug 2013
Reported by afindley...@gmail.com, May 14, 2012
Quick Background:
*I am making a Paid Time Off (PTO) calendar for several regions in the US.
*I am using Zend framework, jquery, fullcalendar, Expand/All by www.adipalaz.com, and a custom "more..." link 
*I have 3 different jquery tabs with a new instance of a calendar on each tab (level 1)
*Each tab has a different topic related to the PTO, with 3 accordion sections
*One accordion section per tab has a filter to filter the results on the calendar
*One accordion section per tab has a calendar on it (level 2)
*The first calendar pulls from two different Event sources through a JSON call/feed
*This calendar pulls PTO according to region
*The regions are displayed as an all day event
*Each "event" is an Expand/Collapse using www.adipalaz.com (level 3)
*When each "event" is expanded or collapsed using the www.adipalaz.com an AJAX call pulls all the PTO related to that region 
*Each expanded AJAX call hides details about the extra info unless the custom "more..." link is clicked (level 4)
*Each custom more link also has some actions (level 5)

Now, all of the above works.  

I have a .click function which handles "level 3" and above.  Part of this .click function is the AJAX call and another part gets and sets the z-index so that my "level 4" data pops above all the other non-expanded "level 3" data.  
So far, that functionality is fine.  The problem is all my underlying data still needs to be visible.

My multi-tiered problem
1. rerender all the events on the calendar so that the week and events are all visible regardless of the clicked "level 3"
2. once rerendered not losing the "level 3" .click action which disappears if I use the $('#calendar1').fullCalendar( 'rerenderEvents'); and not losing the "level 3" data that was displayed prior to trying to rerender the event.

I have images for a visual explanation of what I am trying to do and how it isn't working but haven't figured out how to upload yet.

May 31, 2012
#1 afindley...@gmail.com
This is what I came up with after a lot of help.  I added it to the calendar initialization:

eventClick: function(event, element) {
     if (typeof event.originalTitle == 'undefined') {
	event.originalTitle = event.title;        
     }
	
     if (event.loaded) {
	event.title = event.originalTitle;
	event.loaded = false;
	$('#calendar1').fullCalendar('updateEvent',event);
     } else {
	$.ajax({
	  url: regionNamesUrl + getFilterUrlPart(event.segmentDate,event.region),
	  dataType: 'html',
	  cache: false,
	  success: function(data){		                        
		event.title = event.originalTitle + '<br/><br/>' +data;
		event.loaded = true;
											
		$('#calendar1').fullCalendar('updateEvent',event);

		clicker(event,'approved');
		clicker(event,'cancelled');
	  },
	  error: function(data){
	    alert('An error has occurred retrieving data from the server.  Try reloading the page.');
	  }
     });
   }				
}    
Aug 18, 2013
Project Member #2 adamrs...@gmail.com
(No comment was entered for this change.)
Status: ReproTemp
Aug 25, 2013
Project Member #3 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-Bug