I have created a bunch of views for a website that I am creating, and all are working fine.
I have one view that consists of a page, a data-export (.iif), and pdf view. I am currently configuring the pdf view, and found that I needed to remove the labels. Unfortunately it was towards the end of my work day (or so I thought), and I made the mistake of removing the labels for each field for 'All displays'. When I went to the page and the data export to try and re-enable the 'Create a label' checkbox for each field, it would not save.
Am I doing something wrong?
Comments
Comment #1
stefan.kornI can confirm this issue. Same applies for me. I cleared the checkbox for 'Create a label' first and afterwards wanted to re-enable it for some fields. But this does not work. The checkbox is still cleared after saving. Only way to get rid of this is to remove the field and put it back in.
Comment #2
stefan.kornOk, I found that not only the re-enabling does not work but also the text field for the custom label text is not shown. This let me think about Jquery. I have Jquery Update module enabled and use Jquery 1.7.x. It seems that this is the cause. If I put Jquery back to 1.5.x everything works as expected.
.
Comment #3
stefan.kornUsed this to get Jquery 1.5 in backend and Jquery 1.7 in frontend. Seems to work so far.
Comment #4
liquidcms commentedthis is still an issue for me. latest drupal core, and latest -dev of jqupdate i am not able to enable Label for Views fields.
i am using Seven as admin theme and no version of jquery for Seven fixes this issue; even 1.4; but, disabling the jqupdate module fixes this.
is it not possible to simply have jqupdate do nothing for admin theme?
Comment #5
liquidcms commentedhmm.. surprised this isn't a more commented issue yet or maybe it is covered elsewhere.. so will change title to better match the issue.
from looking at code for -dev rel of this module i don't see how this can work at all for admin themes (and it isn't)"
this code looks for setting for admin_version yet this is no longer stored as a jq update variable it is stored on a per theme basis. so this code is all wrong. code needs to look up theme then pull variable for that theme and assign accordingly.
i'll submit a patch in a bit..
Comment #6
liquidcms commentedhmm.. ok.later down in that function there is this:
which is correct for pulling out version for theme (the earlier line is still wrong as it does nothing since that variable no longer exists)
but, it seems as though my issue is that when i go to Views UI i hit this function numerous times.. and the first time (and others), the theme is not known; therefore default jq update theme is used.
Not sure if this is a bug in core or some other module causing issues here or possibly just a bug in how jq update determines the theme (maybe it can't reliably determine theme at this time). So for now; i guess i iwll need to hack jqupdate to do the "right thing" here and look up theme based on path as opposed to global $theme variable.
Comment #7
liquidcms commentedi added this:
and this fixes my problem although this is not correct way to do this.. bigger issue is why when i enter Views UI does this function not know the theme.
Comment #8
odizle commentedI'm having the same issue using version 2.7 on drupal 7.41.
Tried @stefan.korn suggestion to use the patch in this issue but it did not work for me.
Only thing fixing it for my right now is to disable jquery update.
@liquidcms can you guide where should one put your code?
Comment #9
odizle commentedInstalling the latest 7.x-3.x-dev fixed the issue.
Comment #10
capysara commentedI was having the same issue. I changed "Alternate jQuery version for administration pages to "Default (provided by Drupal)" and it seems to be working again. (admin/config/development/jquery_update)
Comment #11
blanca.esqueda commentedSame here..... Same as #10, I had to change the 'Default jQuery version' to 'Default (Provided by Drupal)' to have it working again.
Comment #12
abarpetia commentedI am using 7.x-2.7 with Drupal 7.50 version and having this same issue. #10 changes worked for me but then other functionality which needed Jquery update on administrative pages will stop working.
For ex: On one of my website I have dragdropfile module enabled which needed this module and setting Administrative pages setting to 'Default (Provided by Drupal)' will break this module.
At this point am not sure what's causing this issue but will try to provide patch.
Thanks
Comment #13
kthullThanks @capysara! #10 did it for me.
Comment #14
markhalliwellThis is a jQuery version/API deprecation issue and can resolved in the 7.x-3.x branch by either: