Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
After I enabled the fullcalendar modules, I received a complete site crash with a fatal error.
I created a discussion item for this in the support forum: http://drupal.org/node/1666026
Comments
Comment #1
aspilicious CreditAttribution: aspilicious commentedI think something is wro,ng with your drupal installation. That is not caused by fullcalendar. We don't even touch the aggregator module.
Comment #2
travelingcoley CreditAttribution: travelingcoley commentedMy drupal install was working correctly and the site was displaying correctly prior enabling fullcalendar. I had feeds working previously and didn't change any other modules during the enabling of fullcalendar. All I did was enable fullcalendar and then my whole site crashed with the aggregator module fatal error (Fatal error: Call to undefined function aggregator_category_load() in public_html/includes/menu.inc on line 592). Could enabling fullcalendar corrupt the drupal install?
Comment #3
travelingcoley CreditAttribution: travelingcoley commentedIt seems that trying to enable FullCalendar caused quite a few of my modules to become disabled. This caused the crash.
I was able to manually re-enable the aggregator module through the DB (since I couldn't get into the admin console with the crash) and then clear the cache through the DB. After this, I was able to finally get into my site. However, more errors were occurring, so with access back to the site, I went to the modules page and I found that a lot more modules had become disabled. I then re-enabled them. After this, my site was working again.
I don't know why enabling FullCalendar caused all sorts of modules to change from enabled to disabled. As I noted in the discussion thread (http://drupal.org/node/1666026), I did initially receive a message at enabling FullCalendar regarding the Color module needing to be enabled. Not sure if this caused the trouble, but it was strange that non-relevant modules were then disabled by the system automatically which caused the whole site to fail.
Comment #4
tim.plunkettThis actually sounds like a duplicate of #494096: Using Chrome ConfirmForms do not double click prevention causing problems. Closing for now.