Problem/Motivation

The calendar is rendered with javascript and hence all html rendered in the calendar is not reachable by Drupal's behaviors.

Steps to reproduce

Try for example to click an ajax link rendered in the calendar events using the element class "use-ajax".

Proposed resolution

Add Drupal.attachBehaviors after the .render() function in fullcalendar_view.js.

CommentFileSizeAuthor
#8 fullcalendar_view-3214419-8-trigger-drupal-behaviors.patch998 bytesjessehs
#7 fullcalendar_view-3214419-7-trigger-drupal-behaviors.patch3.63 KBjessehs

Issue fork fullcalendar_view-3214419

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

Agogo created an issue. See original summary.

Mingsong made their first commit to this issue’s fork.

mingsong’s picture

mingsong
Location 🇦🇺
commented

Thanks Oscar for raising this issue.

I tried to add following lines after calendarObj.render();

         calendarObj.render();
        // Inform other Drupal modules about the change of DOM.
        Drupal.attachBehaviors(this);

While I drag and drop an even, I got an error said:

Uncaught TypeError: e.querySelector(...) is null

I am assuming that other modules remove the DOM created by Fullcalendar.js. It is why the 'null' is return.

I agree with that we need to work out a way to inform other modules about the changes made by Fullcalendar.js.

agogo’s picture

agogo commented

Thanks for the response! I also tried that exact approach and noticed that this only makes the on screen rendered html affected. Switch view and were back to square one.

The reason I found the problem is that I need to be able to render content with ajax on onclick since the calendar view becomes unloadable with too many calendar events.

I'll post a way to make this work if/when I find it.

agogo’s picture

agogo commented

Troubleshooting this, the way I got it working was from running the datesRender callback and then running the attach on the rendered dates:
Drupal.attachBehaviors(info.el)

I also went and removed the behaviors with the datesDestroy callback:
Drupal.detachBehaviors(info.el);

For some reason I couldn't get the correct HTML within the eventRender callback and don't have time to troubleshoot further at the moment, but at least this is a step forward.

  function datesRender (info) {
    Drupal.attachBehaviors(info.el);
  }
  function datesDestroy (info) {
    Drupal.detachBehaviors(info.el);
  }

      calendarOptions.datesRender = datesRender;
      calendarOptions.datesDestroy = datesDestroy;

PS. I'm not receiving any errors with this implementation but that is probably due to the enviroment I'm working in and the events rendered.

kazah’s picture

kazah commented

Same problem.

If I try to log calendar in custom behavior I got undefined.

But if I add settimeout for 1 second I get calendar object without problem.

jessehs’s picture

jessehs
he/him
Primary language English
Location Taos, New Mexico
commented
StatusFileSize
new fullcalendar_view-3214419-7-trigger-drupal-behaviors.patch3.63 KB

The technique mentioned in comment #5 appears to be working for me. It allows me to target and change bits of the calendar each time it is updated using a separate module's Drupal JS code. I've attached a patch that shows the changes. (Sorry for the extra noise, but my editor is configured to fix whitespace errors.)

jessehs’s picture

jessehs
he/him
Primary language English
Location Taos, New Mexico
commented
StatusFileSize
new fullcalendar_view-3214419-8-trigger-drupal-behaviors.patch998 bytes

Oops. I left in console logging messages. This new patch also does not attempt to fix all the whitespace errors.

  • jessehs authored 810e1bc on 5.x 
    Issue #3214419 by jessehs, Agogo: Drupal.attachBehaviors should be ran...
mingsong’s picture

mingsong
Location 🇦🇺
commented
Status: Active » Fixed

Beautiful!

Thanks Jesse and Oscar for your work on it.

Released with 5.1.7

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.