1

(495 replies, posted in Juicebox-Pro Support)

Wrestling with a photographers website and juicebox, I found myself to have some more wishes for future versions of Juicebox for WordPress:
[*]setting to have JB display WPs scaled-down "large" images while embedded, and full-sized original images in fullscreen mode, therewith optimizing both loading speed and visual quality in the coming generation of HiDPI displays[/*]
[*]setting to change formatting of captions: no separate CSS font definition, no drop-shadow, no hard-coded inline padding (all of which tend to look horrible with captionPosition=Bottom)[/*]

2

(495 replies, posted in Juicebox-Pro Support)

Things I'd like to see in Juicebox (for WordPress):

  • dynamic creation of the config XML via some PHP when simply a post's or pages attachments are being used. If the user adds a new photo to a page/post, or changes some existing photos data like a title, there would be no need to save the post, go to Juicebox, find the gallery, edit the gallery, save without doing anything just to get the new data into the otherwise static XML

  • If a page/post already has a juicebox gallery shortcode, clicking on the JB button should edit this existing gallery (see above), not add a new emtpy one by default

  • And the most important one: while the full-screen gallery view is very nice indeed, on iOS devices opening a new, separate JS URL for it means that the underlying, originating page will be reloaded from scratch when closing the full-screen gallery view. Others like photoswipe do this much more elegantly.

  • Support for HiDPI (Retina) Images

Hi Steven,
I added your code into wp-juicebox.php (not .js), and it does what it should: write https into the javascript snippet when called from a secured page.
Thanks for your help, Phil

Hi,

just found out why Juicybox (WP Plugin with Pro addon) stubbornly displayed "XML not found" in two of my browsers: they were using https://, while the Juicybox javascript looks for the config XML in http://.

You may want to change this behaviour at some point, I think, as it practically means I can't use Juicybox for any sites that have members areas, or where the backend work in the CMS is done over https. Or is there a setting I've missed somewhere?

Thanks, Phil