Closed (duplicate)
Project:
LoginToboggan
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Jan 2012 at 06:59 UTC
Updated:
22 Sep 2014 at 17:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
nadavoid commentedMoving this into the LoginToboggan queue.
The problem is in logintoboggan.permissions.js. I think it may have to do with the specificity of the jquery selector, but I'm not sure.
Comment #2
nadavoid commentedThis small patch should resolve the problem for 7.x-1.3.
Comment #3
halmsx commentedthanks for the patch. is there any side effect on logintoboggan's features?
Comment #4
daveparrish commented#2 worked for me. I haven't seen any issues it causes with logintoboggan and looking at the code, I don't see why it would cause any issues.
Comment #5
jeff veit commented#2 works for me too.
Comment #6
NenadP commented#2 working ! Thanks 100 x 100 times :)
Comment #7
Taxoman commentedPlease commit this to -dev "asap".
Comment #8
wOOge commentedConfirmed — patch in #2 fixes the problem for me.
Comment #9
mrpauldriver commentedConfirmed — patch in #2 fixes the problem for me.
Comment #10
Taxoman commentedPlease commit to -dev.
Comment #11
bartezz commentedTested and working!
Comment #12
j0rd commentedI believe most people who run into this bug, is because they have field_permissions (Field Permissions) module installed. Going through and tagging issues and adding keywords into issues, so people can find them.
#1407402: Field permissions reset to default (no access) after updating the field
#1365764: Adding logintoboggan.permissions.js causes error if Drupal.settings.LoginToboggan not set.
Also I'd like to say that patch #2 works for me as well.
Comment #13
md2 commentedI think this issue was caused by a JavaScript error and not the JQuery selector. There is a patch for over at issue #1365764, please test and see if it fixes this issue also.
Cheers,
Mark
Comment #14
Anonymous (not verified) commentedFYI: this problem also manifests as turning the settings fieldset in a rules component non-clickable.
I can confirm that the patch in #1365764 also solves this issue.
Please roll a new version of LoginToboggan incorporating this patch.
Comment #15
nadavoid commentedI just tested this scenario again, and I'm not seeing the problem any more.
I installed field_permissions 7.x-1.0-beta2 and logintoboggan 7.x-1.3. After that,
/admin/structure/types/manage/page/fields/bodystill has the Custom permissions fieldset, and/admin/people/permissionsstill lists the two "Field permissions" permissions. This is without applying any patches.So, I'm not sure if either of these patches are needed any longer. Or am I missing something? It's been a while since I first opened the issue.
Comment #16
ptmkenny commented@nadavoid (#15) I still have the issue with field_permissions 7.x-1.0-beta2 and logintoboggan 7.x-1.3 on Drupal 7.18 unless I apply the patch.
As noted in #14, I was able to use the patch in #1365764 to fix this issue.
Comment #17
phiscock commentedThat patch worked for me both to fix the problem with Field Permissions but also with Faster Permissions.
Comment #18
thirdender commentedI just ran into this problem as well. Initially I had no problems running LoginToboggan and Field Permissions. The problems started when I changed the LoginToboggan settings allow immediate login and added a pre-auth user role. Patch #1365764 fixed my issue straight away.
Comment #19
wOOge commentedPatch in OP works to fix the issue — can we roll this into the module?
Comment #20
david_garcia commentedBoth this and #1365764 are the same issue. Closing this as a duplicate as the other issue has better follow up on what the real cause of the problem is.
Comment #21
wOOge commentedApply the patch in #23 of this issue:
https://www.drupal.org/node/1365764#comment-8579719