Watched 1 video

Watched 1 Video from start to finish

Subscribed for 1 month

Learning and showing your support for 1 Month

Spread the word 1 time

Referred 1 Member to Drifting Ruby

10

10 times Chatter Box

Make 10 comments to videos or replies to other comments
2/10

Share the love 1 time

Liked 1 episode

3

Welcome back 3 times

You've visited Drifting Ruby on 3 different days

Suggested 1 episode

Helped the community by suggesting 1 episode

Vote Suggestion 1 time

Helped the community by voting on suggestions 1 time

1 time Chatter Box

Make 1 comment to videos or replies to other comments

Earned on 3/4/2019

# Name
Jack Chang said over 2 years ago on FullCalendar Events and Scheduling :

I  just downloaded  and installed your example from https://github.com/driftingruby/042-fullcalendar and seems it has the same issue I have encountered.

To reproduce the issue:

1.  create an new event or update (either edit or drag&drop) an existing event. (everything is good so far)

2 . click on next month button, then click to go back to current month

3. you will see two duplicate events you just created/updated

Any clue?

Jack Chang said over 2 years ago on FullCalendar Events and Scheduling :

NVM, I found the problem in  https://github.com/driftingruby/042-fullcalendar.

In app/views/events/create.js.erb and  app/views/events/update.js.erb

$('.calendar').fullCalendar(

 'renderEvent',

  $.parseJSON("<%=j render(@event, format: :json).html_safe %>"),

  true   //  <-----

);

the 'stick' atttibute for  'renderEvent'  method  should be set to false