Posted by penguininja on March 8, 2012 at 1:31am
4 followers
Jump to:
| Project: | Julio |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | jgraham |
| Status: | closed (fixed) |
Issue Summary
FullCalendar is not using the correct path for the FullCalendar library located in /profiles/julio/libraries/fullcalendar. There is a "Path to FullCalendar" setting that can be set at /admin/config/user-interface/fullcalendar to temporarily resolve this. In addition, the fullcalendar library is in a nested folder, similar to #1465816: nivo slider js library packaging/build issues. Addressing these issues in the FullCalendar queue at #1472436: Allow "Path to FullCalendar" Setting to use Libraries API.
Comments
#1
related #1481158: how to deal with problem third party libraries?
#2
See: #1472436: Allow "Path to FullCalendar" Setting to use Libraries API
#3
#919224: Allow use of subtrees or individual file from archives instead of the whole archive
Once that goes through this should start building properly.
#4
Linking to the remaining blocker on this
#1482888: Support 'subtree' download attribute for libraries
#5
Temporary workaround after installing (similar to #1465816: nivo slider js library packaging/build issues)
cd TO-YOUR-WEBROOTcd profiles/julio/libraries/fullcalendar/
rm -r changelog.txt demos/ GPL-LICENSE.txt MIT-LICENSE.txt jquery/
mv fullcalendar/* .
rmdir fullcalendar/
drush cc all
#6
I think this may be okay to close, the libraries are getting packaged properly, but I didn't see the drupal.org drush issue closed out. Followed up for clarification to ensure this isn't a transient success.
#7
Fixed in d.o packager
#8
Automatically closed -- issue fixed for 2 weeks with no activity.
#9
Latest builds are exhibiting this issue again.
#10
Latest builds are proper.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.