Support for views row field formatter (Views Not saving Juicebox Configuration and reverting to default when saved)

Hi Julian,

I've not personally encountered any problems with Juicebox views settings failing to "stick" after saving changes, and have not (yet) heard of anyone else having this issue. Anyway, I think we first just need to isolate the problem you're encountering and see if it's in fact related to the Juicebox module or something else.

First, just to confirm, have you gone though all the steps in the documentation under the heading "Using the Juicebox views style plugin (nodes/entities are images)"? It sounds like you have, but I just want to make sure that you have not missed a step.

Also, is it only the Juicebox related views settings that fail to save (and always revert back to the defaults) or is it all the views page settings that fail to save? For example, if you use a different formatter for your view page (such as "Grid") and then alter some of it's formatting settings, do they persist after a save?

Just let me know and we'll go from there.

Julian, were you able to have a look at some of my comments above? I just wanted to check in on this as we'll need some additional info in order to help out.

Also, if you already resolved this please let us know what the problem/solution was. Having that kind of information documented here will be useful for any others who may encounter this kind of problem.

Cheers

As I haven't heard anything new on this one (and therefore don't have any info to replicate it), and given that no other users have reported this, I'm going to go ahead and close it. If anyone experiences any problems like this with the most recent release please re-open this or file a new issue.

Same problem. Cannot save settings such as gallery width and height.

Thanks for reporting this fedExpress.

I'd very much like to investigate more and see if we can isolate/fix this. At the moment however it's not something that I can replicate on any of my test environments, so I'm going to need some help and additional info from the people experiencing this problem in order to be of use. The following details will be especially useful:

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) or some other tool?
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. 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.

It would also be interesting to know if anyone seeing this problem has any other modules installed that are related to either views or form customization in Drupal, as these may influence things in case-specific ways.

Please just let me know the answers to the questions above and I'll be happy to investigate further.

wrong issue post

Hi kclarkson. Just to confirm, are you saying that the image settings are not being saved when you change them (i.e. you make a change to the "Main Image Field Style" setting, click save, and then re-visit the setting screen and the "Main Image Field Style" setting is not changed)? Or are you saying that these settings are in fact being saved but they are not being applied.

If the latter is true then it's most likely unrelated to this specific issue. One thing that you would want to try is forcibly clearing your browser cache between configuration changes like this. The Juicebox XML, which is how this module passes all its settings to the Juicebox javascript, may be getting cached within your browser. It's even possible that your ISP or hosting company has some caching or reverse proxy systems in place which could be sending cached versions of the XML that don't represent your recent configuration changes. There are lots of levels where caching can come in, and it can be a pretty tricky thing to diagnose in some cases.

wrong issue post

@kclarkson, it does sound like your situation is different from the one this thread is discussing, and may have something to do with caching that's specific to the systems between your public server and your users. In any case it will be better to address this in a separate support/issue request. Would you be willing to open-up another issue thread and just past-in your text from comment #6 there? That will make it much easier to give your unique situation attention.

Sorry everyone but without any additional participation from others I can't replicate this problem and therefore can't do anything to help. Marking as postponed until someone can provide more info.

Once again, here are the questions I'm hoping someone who's seeing this problem can answer:

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. 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.

It would also be interesting to know if anyone seeing this problem has any other modules installed that are related to either views or form customization in Drupal, as these may influence things in case-specific ways.

I'm going to close this now due to inactivity. I'm still interested to look into this if someone can help replicate it. If so please re-open and reference the questions in comment #10.

Ok, I'm going to re-open this as I can now, finally, replicate this issue. Thanks to some follow-up comments by rp121 in the (now duplicate) issue #2102617: Views Pro / Manual Config options not saving I was able to realize that this is a problem for a specific configuration where the field formatter is used inside of a view. This is a configuration that I had not tested or explored in detail because the module's views support was only targeted toward views display formatters (i.e. formatters for a whole view display as opposed to individual views rows).

Anyway, this should be something that module's architecture is generally capable of supporting, it just looks like there is an issue related to the hierarchy (fieldset) handling in the conf form that's causing problems.

Adjusting status values....

Alright, I discovered (and implemented) a much better way to handle fieldsets within the configuration form. This allows changes to "stick" in all contexts. However, the specific case of using the field formatter within individual views rows poses additional problems. Due to the way this module must generate gallery XML data independent of the actual view page request, it is not currently possible to use configuration settings that apply to each view row. When building the XML we simply do not have a good method to fetch the gallery display configuration independently from the actual gallery image data. Because of this I have set a warning message to appear in place of the Juicebox configuration options when selecting "Juicebox Gallery" as the view field formatter.

The relevant commit is: http://drupalcode.org/project/juicebox.git/commit/c658771

All this said, my guess is that there are very few cases where users would actually want to use the Juicebox field formatter within individual view rows. It could be that the people hitting this problem were actually wanting to achieve the results that are already available via the (working) Juicebox display style formatter. I could be wrong, and if there is actually a demand for styling individual view rows as Juicebox galleries (as opposed to styling a whole view display as a gallery) I suggest somone open up a separate feature request thread for that.

Note that experimental support for this kind of field-based gallery (galleries embedded into individual views rows) is now available in a sandbox extension module. See:

https://www.drupal.org/sandbox/rjacobs/2302609

Update: A fix for this has been implemented in #2401389: Consider alternate ways to store and generate gallery XML. The sandbox project noted above in no longer needed or relevant.

Marking this (old) issue as "fixed" in 7.x-2.x. As noted above the fix was implemented as part of another issue, but given that people are still referencing this one it seems appropriate to update the status and track the fact that a solution is available.