When logintoboggan is enabled, the fieldset for "Custom Permissions" never appears on the page. When inspecting using a debugger, I can see that the HTML of the custom permissions form is present, but it does not display on screen. I'm guessing it is some sort of CSS conflict.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

nadavoid’s picture

Project: Field Permissions » LoginToboggan
Version: 7.x-1.0-beta1 » 7.x-1.3

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

nadavoid’s picture

Status: Active » Needs review
FileSize
669 bytes

This small patch should resolve the problem for 7.x-1.3.

halmsx’s picture

thanks for the patch. is there any side effect on logintoboggan's features?

daveparrish’s picture

Status: Needs review » Reviewed & tested by the community

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

Jeff Veit’s picture

#2 works for me too.

NenadP’s picture

#2 working ! Thanks 100 x 100 times :)

Taxoman’s picture

Priority: Normal » Major

Please commit this to -dev "asap".

wOOge’s picture

Confirmed — patch in #2 fixes the problem for me.

MrPaulDriver’s picture

Confirmed — patch in #2 fixes the problem for me.

Taxoman’s picture

Version: 7.x-1.3 » 7.x-1.x-dev

Please commit to -dev.

Bartezz’s picture

Tested and working!

j0rd’s picture

Title: CSS conflict with logintoboggan, prevents using Custom Permissions. » CSS conflict with logintoboggan, prevents using Custom Permissions (field_permissions module)
Issue tags: +Field Permissions

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

md2’s picture

I 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

Anonymous’s picture

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

nadavoid’s picture

I 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/body still has the Custom permissions fieldset, and /admin/people/permissions still 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.

ptmkenny’s picture

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

phiscock’s picture

That patch worked for me both to fix the problem with Field Permissions but also with Faster Permissions.

thirdender’s picture

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

wOOge’s picture

Issue summary: View changes

Patch in OP works to fix the issue — can we roll this into the module?

david_garcia’s picture

Status: Reviewed & tested by the community » Closed (duplicate)

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

wOOge’s picture

Apply the patch in #23 of this issue:
https://www.drupal.org/node/1365764#comment-8579719