I have a view context that is using an image field formatted as a juicebox gallery. When I try adding options under "Pro / Manual Configuraton Options", nothing seems to get saved. The next time I try adding or editing my juicebox config options I see a blank text area where my options should have been saved.

I'm currently using Drupal 7.23 with the latest Juicebox dev version, and latest juicebox library.

Comments

rjacobs’s picture

rjacobs commented

Hi rp121,

I believe that this is actually a duplicate of #2006830: Support for views row field formatter (Views Not saving Juicebox Configuration and reverting to default when saved) in which a couple people reported something similar but I was unable to reproduce the problem. Unfortunately the previous reporters did not respond to my requests for additional information, and I eventually needed to close that issue for lack of activity. From what I can gather so far this appears to be a problem that's only triggered in isolated cases.

So the bottom line is that I'd love to get to the bottom of this, but I'll need some help to understand what is going on. Below are the (unanswered) questions that I posed to the people in issue #2006830, if you are willing to reply to these and help me reproduce this locally that would be great.

  1. When editing the view are you using the standard views UI (the URL for the edit page would be something like /admin/structure/views/view/viewname/edit)?
  2. Is it possible to correctly save changes to the Juicebox view configuration options that are not in the expandable/collapsible fieldsets? For example, is it possible to correctly save changes to the "Main Image Field" or "Main Image Field Style" options?
  3. Do you have any other modules installed that are related to either views or form customization in Drupal? This could prove useful as such modules may influence form conf processing in case-specific ways.
  4. Within the same Drupal installation, does this same problem arise when working with the settings for a gallery that's based on a field formatter (not a view)? Setting up the field formatter is quite easy, just see the notes under the heading "Using the Juicebox field formatter (nodes/entities are galleries)" in the documentation. Once a field formatter is in place you would just want to then check if it's possible to correctly save the width/height values for it.
robdubparker’s picture

robdubparker commented

Thanks, rjacops

Due to timeline I had to find other modules/plugins to help achieve the photo gallery reqs.

However, to help you investigate here are some answers to your questions:

  • I am editing the view using the standard views UI.
  • Also, upon further investigation, this problem seemed to occur within CTOOLS contexts, not just views.
  • When using the standard field formatters the functionality seems to work correctly. Issue is isolated to views/contexts juicebox config options.
  • Lastly, the options for views "title source", "caption source" save successfully. Problem is specific to the "lite config", and "pro/manual config" options.

Hope this helps.

rjacobs’s picture

rjacobs commented
Status: Active » Closed (duplicate)

Ahhhh, ok, ok, I think I finally see what is going on here.

Your points above ruled-out a couple things (thanks for that) and so I tried to experiment a bit more based on your initial report and follow-up. Initially it didn't fully register that you were using a view context, but your second point about ctools contexts made this more clear. Then, when I experimented to see if that, or panels, might be conflicting somehow, I realize that views context doesn't have the ability to use the Juicebox display formatter. This made me wonder how the heck you were even using Juicebox within you view. Then I had an ah-ha moment a realized that you, and presumably the others who reported something like this, were using the field formatter inside of a view. This is, quite frankly, a configuration that I had never really thought of, and sure enough, is one that displays this problem.

So indirectly I think we've sorted out the cause here... and I can now reproduce this.

Now I'll just have to see what can be done about this... but seriously, being able to get it replicated was probably 90% of the battle. Thanks so much for following up!

I'm going to re-open #2006830: Support for views row field formatter (Views Not saving Juicebox Configuration and reverting to default when saved) and continue looking at this problem there given that it's the older thread on this topic. rp121, please feel free to follow-along there should you decide to re-visit this module.

Thanks again!