The Slide-Box module works fine for the Administrative accounts.
For all other accounts authenticated or not, the Slider Box will generally display initially but then
on subsequent refreshes the 5 stories will appear listed vertically consuming the whole page. No refreshes no outer box. Just as though the contents that would have been in the box are all thrown
out.
I have observed this with IE 8, Safari, Firefox, and Chrome as Unauthenticated and Authenticated regular user. On some occasions, the box does not even work the first time for these users and the
displays goes directly to a vertical list of what would have been in the Feature Box.
I have allowed the Slider Box permissions for Unauthenticated and Authenticated users but because of these errors I have edited the BLOCK containing the feature to restrict to Slider Box to Administrator only since it works fine for that account.
I would very much like to utilize this module since it looks very nice but I cannot unless I can resolve this issue and searching through the Permissions area, I don't know what is relevant.
ANY IDEAS?
Also, hopefully is newer versions the weighting engine for the stories can be used to dynamically modify those stories or perhaps a MANUAL method of doing same. I found myself editing stories for no reason other than to make them appear as I wanted in the sliders. I saw a reference to your plans of incorporating that into future modules and look forward to that.
Hopefully you have ideas on my issues.
Thanks.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | content_slider-363470-5.patch | 3.01 KB | fuerst |
Comments
Comment #1
dreflexia commentedI have the same issue. Any progress?
Comment #2
Panther256 commentedI am struggling with a similar problem with the "Featured Content Slider"... My problem is related to Drupal adding an HTML comment
<!--after a javascript tag and then transposing it to an<!--which then renders a javascript error when loading the page. Drupal also strips out my CSS line ( I should probably add it to a proper location and not the "page" itself).I have found that under certain circumstances I can re-add my CSS link and delete the comment to get everything to work but you have to do this everytime you edit the page.
Same/similar problem, maybe?
Comment #3
dreflexia commentedI believe that I found a solution. Disable block cacheing. This appears to work. Page cacheing is ok, but block cacheing is not. When the init function doesn't fire, the pages show stacked. And the init function wasn't firing some of the time with block cacheing. I have no idea why it works consistently as an administrator (although I agree with "mdphdjhu" that it does).
Hopefully this will help with a fix.
Comment #4
sudeepg commentedI closing this issue now.
Comment #5
fuerst commentedIt seems that contentslider.js get not loaded from
hook_block()when using block caching. Because I think disabling block caching isn't a permanent fix I added an implementation oftemplate_preprocess_block()to content_slider.module to get contentslider.js loaded (only) when needed. Same for the CSS. Usingtemplate_preprocess_block()hopefully is a good place for it because that way JS/CSS only get added when necessary. See the attached patch please.BTW: If javascript is missing you can at least avoid vertically stacked nodes by adding that CSS to your theme: