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.
The documentation on the module page says that:
drush fullcalendar-plugin
will install the fullcalendar plugin.
First, the command would have to be drush dl fullcalendar-plugin. Second, drush returns an error that there is no release history for fullcalendar-plugin.
Comment | File | Size | Author |
---|---|---|---|
#3 | agriturlameta.com Status Report.png | 173.78 KB | romeof1980 |
Comments
Comment #1
tim.plunkettNo,
drush fullcalendar-plugin
is a custom command I included in the module. fullcalendar-plugin is not the name of a module, which is why dl wouldn't work.Comment #3
romeof1980 CreditAttribution: romeof1980 commentedHI guys!
anyway the cmd "drush fullcalendar-plugin" does not seems to work with Drupal 7.42
here is the error I got (I fired it after successfully downloading and enabling the module via drush):
Drush was unable to download the FullCalendar plugin to [error]
sites/all/libraries
furthermore I got the following warning when accessing the Rooms module (after moving the 1.6.7 plugin's fullcalendar folder's content to sites/all/libraries/fullcalendar):
Warning: file_get_contents(sites/all/libraries/fullcalendar/lib/moment.min.js): failed to open stream: No such file or directory in _locale_parse_js_file() (line 1488 of /home/agriturlameta/public_html/includes/locale.inc).
on the other hand, in the status report all seems installed as expected (see attachment)
any tips/hints will be highly appreciated..
thanks!
Comment #4
romeof1980 CreditAttribution: romeof1980 commentedComment #5
romeof1980 CreditAttribution: romeof1980 commentedHI guy,
by the way,
the plugin works fine (v. 1.6.7) in Drupal 7.42
it's just the Drush cmd that does not work
have a great day,
romeo
Comment #6
gislePossible duplicate of #2731873: Wrong path for FullCalendar JS plugin?
The reason the "drush fullcalendar-plugin" doesn't work is because the current code is outdated. Basically, it tries to download a file that no longer is on-line. The patch attached to the related issue fixes that.
I haven't seen the warning mentioned in #3, so that may be another (and unrelated) problem.