Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
From some point of time, the dialog which was shown when choosing custom permissions in field settings, does not appear anymore! Help!
Comments
Comment #1
bluewallmedia CreditAttribution: bluewallmedia commentedI can confirm I'm having this same issue running 7.15.
EDIT: For what its worth, debug tests show this test fails for block functionality. I'm not sure this is related, but may be helpful in debugging this issue.
BlockTestCase->testBlockVisibilityPerUser()
thanks for the module and community support, its much appreciated!
Comment #2
bluewallmedia CreditAttribution: bluewallmedia commentedHas anyone come across a fix or a patch for this yet ? Thanks!
Comment #3
NenadP CreditAttribution: NenadP commentedI am in great need to overcome this bug, if someone found a source of this bug, please help!
Comment #4
NenadP CreditAttribution: NenadP commentedStrange enough, falling back to previous version did not solve the problem. Could be this related to other module or Drupal core update (7.15). I see the form when inspecting with firebug, but nothing appears on screen. I am trying to find way to set file permissions directly in database, cant find entry in database for the field permissions for now.
Comment #5
yogaf CreditAttribution: yogaf commented@HoverFusion Try to Aggregate JavaScript files.
It worked for me.
Comment #6
NenadP CreditAttribution: NenadP commentedThanks but in my case that did nothing :( you only aggregated javascript fles and dropdown was avail again ? Thanks anyway!
Comment #7
wOOge CreditAttribution: wOOge commentedSame here — running D7.15 and FieldPermissions 7.x-1.0-beta2 (Jan 25)
Using FireBug — you can see the permissions matrix is there but it is css hidden regardless of what level access one selects.
Comment #8
NenadP CreditAttribution: NenadP commentedTried: downgrade drupal to 7.14
Downgrade field permissions to 7.x-1.0-beta1
messed with jQuery update
Tried various combinations of those
Nothing helps, problem persists.
Comment #9
Jeff Veit CreditAttribution: Jeff Veit commentedGot the same. The set of fields have visiblity: hidden. Changing visiblity to visible, in Chrome css debugger does not make a difference.
It may be some combination of modules: I have two sites built from the same base, one of them has many modules turned off, and the other has them on. The one with them on has the problem. This isn't a certain diagnosis - it's just a shadow of a hint.
Comment #10
Jeff Veit CreditAttribution: Jeff Veit commentedHappens in Chrome & FF.
Comment #11
NenadP CreditAttribution: NenadP commented#9 i suspect this also, as it stopped to work with site update, including 7.14->7.15 update, and about 5-10 modules update. But i do not know now which modules are those. For me this is life and death issue, i need to go to production level with my site and i depend heavily on this matter...
Does anyone know how those values (field permission values that are set in that dialog that is failing to show now) can be set manually ? I cannot find in database info about those values.
Anyone knows any workaround ?
Comment #12
Jeff Veit CreditAttribution: Jeff Veit commentedFor me LoginToboggan is the culprit. And there's an issue and a patch. After applying the patch, you may need to rebuild your javascript cache for the change to take effect. Go to Configure, Performance, and clear all caches.
I'm leaving this issue as active: if this issue has affected you, would you check and leave a note that it's solved for you. If there are a few, then it's safe to assume this is fixed.
Comment #13
NenadP CreditAttribution: NenadP commented#12 Jeff Veit Thanks very much for this life-saviour info!
Patch works, dialog is back again!
I again believe in social outsourcing and community spirit! :D
Thanks!
Comment #14
wOOge CreditAttribution: wOOge commentedConfirmed, patch mentioned in #12, works for me.
Comment #15
MrPaulDriver CreditAttribution: MrPaulDriver commentedConfirmed, patch mentioned in #12, works for me.
Comment #16
davey_b CreditAttribution: davey_b commentedI have this problem but applying the patch didn't sort it. I cleared all caches etc. but still no joy. I may be missing something obvious.
Comment #17
akalata CreditAttribution: akalata commentedThanks for the pointer Jeff!
Comment #18
plinto CreditAttribution: plinto commentedI am having the same problem but I do not use the LoginToboggan module.
Comment #19
dflitner CreditAttribution: dflitner commentedI'm also seeing this problem. I don't use LoginToboggan but I've narrowed it down to a conflict with the Field Conditional State module. I'm going to open an issue in that queue and point to this thread.
Comment #20
richardj CreditAttribution: richardj commented#12 confirmed, works when logintoboggan is installed, fixes the JS conflict.
Comment #21
philipjohn CreditAttribution: philipjohn commentedI concur with #16 and I don't use the module mentioned by #19
The patch supplied here doesn't work for me, and looking at the HTML I do NOT see the table hidden - it simply isn't there.
Any thoughts?
Comment #22
Joe_Smith CreditAttribution: Joe_Smith commentedI am getting the same thing. I'm using the Field Conditional State module too but have not confirmed it is the cause. I am not using the LoginToboggan module.
This html:
has this CSS:
Changing or removing this CSS in the browser exposes the options.
Comment #23
rviner CreditAttribution: rviner commentedI can also confirm there is an issue with the custom permissions displaying when the Field Conditional State module is installed.
Comment #24
rviner CreditAttribution: rviner commentedI can confirm this is now fixed with the latest version of Field Conditional State.
Comment #25
rollingnet CreditAttribution: rollingnet commentedThis issue is due, at least for me, by LoginToboggan but, as others noted above
See Adding logintoboggan.permissions.js causes error if Drupal.settings.LoginToboggan not set issue (especially the latest patch #23), for resolution.
Comment #26
Leeteq CreditAttribution: Leeteq commented@rviner: which module are you referring to as not giving this problem?
- the old, original 7.x-1.x-dev branch, last update in January:
https://www.drupal.org/project/field-conditional-state
- or the brand new successor module with its 7.x-2.x-dev branch last updated in June:
https://www.drupal.org/project/field_conditional_state
(notice: 2 different modules, dashes vs. underscores as their only visible url difference...)
Comment #27
wOOge CreditAttribution: wOOge commentedFolks — if you have LoginToboggan installed — apply the patch in #23 of this issue to LoginToboggan:
https://www.drupal.org/node/1365764#comment-8579719
Comment #28
mjgruta CreditAttribution: mjgruta commentedI can confirm that applying the patch #23 from LoginToboggan (https://www.drupal.org/node/1365764#comment-8579719) fixed the checkboxes not showing for custom permissions.
Comment #29
Alan D. CreditAttribution: Alan D. commentedComment #30
Jeff Veit CreditAttribution: Jeff Veit commentedAnd I want to thank myself too: 3 years ago I left a note here, and today I needed this again. God, I love open source! Drupal.org you are wonderful: if it weren't for you, I'd be debugging again. Internet hug for everyone who has contributed to Drupal.org, but special thanks to Neil Drumm who is responsible for so much of it.
Comment #31
cthshabel CreditAttribution: cthshabel commentedThe patch mentioned in #27 for the patch in login toboggan was the fix for me! Thanks everyone.
LOL @JeffVeit that is exactly how I feel about Drupal. <3
Comment #32
rwilson0429 CreditAttribution: rwilson0429 commentedThe patch in #52 at https://www.drupal.org/node/1365764#comment-10286257 fixed the problem for me. If you are using logintoboggan this patch may be better for you.
Comment #34
mariacha1 CreditAttribution: mariacha1 at ThinkShout commentedGiven that this sounds like a LoginToboggan known issue, I'm closing this as a duplicate. I've added an error message to the form with a link to the new documentation, which covers this issue: https://www.drupal.org/node/2802067#known-issues
Protocol here is to apply the patch at https://www.drupal.org/node/1365764#comment-10286257 to LoginToboggan until that issues is committed.