Download & Extend

No javascript or CSS calls are being added to the head

Project:jCarousel
Version:6.x-1.1
Component:Documentation
Category:bug report
Priority:critical
Assigned:Unassigned
Status:closed (won't fix)

Issue Summary

Hi,

I installed this module and added the example code to a page (using a completely hands-off input format, in order that no PHP be stripped out), but the javascript and CSS links are not being added to the document head. The page is just displaying the sample photos as an unordered list.

I am certain it's not a problem with my Drupal install or theme because the examples at /admin/help/jcarousel all work fine. And I'm doing all this as user-1, so it can't be a permissions problem.

Am I missing something?

Thanks,
Andrea

Comments

#1

Exactly the same here

what ARE we missing?

Im starting to agree with what chroni said here.

#2

I'm having the same issue. I thought it was a jcarousel views module issue, but maybe it's a jcarousel modules issue. Can I give any more information that might help fix this problem?

#3

Same here. Sometimes it includes the javascript in the header, sometimes not. Including for the same page with no changes whatsoever in the content.

#4

Priority:normal» critical

There is something wrong with the logic that determines whether or not to add the headers, though it is not obvious what exactly the issue is. As a workaround, I replaced this line in jcarousel_add:

$jcarousel_added['plugin'] = TRUE;

with

$jcarousel_added['plugin'] = FALSE;

and the problem disappeared. The drupal_add_css and drupal_add_js functions deal with not adding the same lines twice in the header, so the result is acceptable.

I've changed the priority to critical, as this appears to affect many people and it entirely stops jCarousel from working and can thus have a severe effect on both site functionality and appearance.

If you have not yet made the choice of which module to use for this functionality, I'd check out Views Slideshow.

#5

Status:active» closed (won't fix)

The 1.x version probably won't be receiving further updates, but this problem has been resolved in the 2.x version. I'm going to go ahead and close this due to the age of the issue, please open a new issue if this problem exists in the 2.x version.