Closed (fixed)
Project:
Juicebox HTML5 Responsive Image Galleries
Version:
7.x-2.1
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Oct 2015 at 19:48 UTC
Updated:
17 Nov 2015 at 18:54 UTC
Jump to comment: Most recent
Comments
Comment #2
rjacobs commentedHi,
I think you need to leverage the following (pro) config option:
showThumbsOnLoad="FALSE"That should ensure that the thumbs are not loaded at all. If you also have the "Show Thumbs Button" option disabled then the user will not even be able to toggle them back on manually, which essentially eliminates the thumbnail feature altogether.
See the Juicebox javascript library config options for more info.
Comment #3
justkristin commentedOh, thank you! I have implemented the showThumbsOnLoad="FALSE" option in the Pro settings window, and have tried it both with and without the "Show Thumbs Button" checked, but it still seems to want to come up with thumbs active. Is there anything else I can check? I am so grateful for your help...
http://devanimals.sandiegozoo.org/animals/reindeer
Comment #4
justkristin commentedShoot. I have taken the thumbnail button off (deactivated it/unchecked the setting) as well, and it still shows up. I am not sure what I am doing wrong...
Comment #5
rjacobs commentedIt looks like the
showThumbsOnLoad="FALSE"option is not actually getting set in your example gallery XML:http://devanimals.sandiegozoo.org/juicebox/xml/field/node/182/field_anim...
Can you confirm that you have set this option in the "Pro / Manual Configuraton Options" for your gallery configuration? I just did a quick confirmation on a test gallery and that setting appears to work as expected within the Juicebox javascript library.
It sounds like some of your setting values are not getting saved or something like that. Are you sure that you are configuring the correct gallery field and that there are no validation errors when you save?
Comment #6
justkristin commentedI have been able to save the following, and gone through the save process with no clearing or disruption of settings:
http://devanimals.sandiegozoo.org/sites/all/libraries/juicebox/juicebox_...
I have also confirmed that the library being called is the Pro version:
OK Juicebox Javascript Library Pro 1.4.3.1
Any other tips would be so gratefully accepted. Thank you so much!
Comment #7
justkristin commentedSir -
The gentleman over at Juicebox gave me a final piece of advice to try, and so I have checked all the permissions:
I will admit that I am not entirely clear on where the gallery xml files are - I had assumed that all would be in the DB, but I am remedial and shouldn't be assuming. :) I have made sure that all my module and library files, as well as the files and dirs in the sites/default (files, etc) have the correct permissions... Might I be missing files somewhere else?
Thank you again so much for all your help.
Comment #8
justkristin commentedHere is a public acknowledgement of my idiocy as well as my solution:
Make sure that when you are putting your settings into Drupal, your dev isn't using something other than the Default display settings. I was entering the Pro settings in the wrong display tab.
*bows head in shame*
Thank you for your help and patience, and for a great plugin!
Comment #9
rjacobs commentedIt had just occurred to me that something like this could be going on. The XML path showed that you are using a custom view mode (cck_blocks) on your field which may not be inheriting the default display formatter settings. Anyway, I'm glad you were able to sort that out. The different view mode distinctions are not always obvious via the Drupal admin interface.
Just for reference the XML "files" are not actually files when you use this module. The XML is dynamically generated by Drupal (via the module) on demand just like any other Drupal page. So you won't have to worry about any file-level permissions when it comes to any XML. This was of course not related to your issue, but I just wanted to mention it for anyone else who may end up reading this thread.