Greatly appreciate the great service this module provides!

When a content type is set to allow subscriptions for that content type, AND the content type has comments enabled, an empty Notifications fieldset (expanded) shows up underneath the "Add new comment" box. I noticed this with an existing content type after upgrading to 6.x-2.0, so I tried creating a new content type and got the same results.

I'm going to add in some jquery for now to hide it from users. It doesn't do anything at all, but it may be misleading for some users.

Thanks!

Comments

mshaver’s picture

Status: Active » Needs review
StatusFileSize
new895 bytes

This is actually the fieldset for the "skip notifications" functionality. I just noticed this as well and it appears because the fieldset doesn't have the access permission on it as well. Here is a patched version.

swellbow’s picture

Status: Needs review » Reviewed & tested by the community

Worked perfectly. Thanks so much!

michaelfavia’s picture

I ran into the same issue and created a similar patch. Is this fieldset used by any other modules at this time?

If SO then this access check is overly specific and will fail them. We might need some sort of FAPI "#after_build" function to determine if it is empty and prune it instead.

Alternatively we can just have each add to it in the same way that this one did. Using #attribute specific variables so as not to reset the fieldset contents that another might create.

If NOT then lets remove the fieldset in the firstplace and make the form easier to understand.

Ill submit a modified patch that conditionally adds the notifications fieldset "carefully" if they have the necessary permission to skip notifications. This is at least extensible until we hear from Jose.

michaelfavia’s picture

Status: Reviewed & tested by the community » Needs review
StatusFileSize
new2.77 KB

Here you go.

pathfinderelite’s picture

same issue, subscribing

aharown07’s picture

I'm going to apply the patch and test a bit. Will post results.

Yup. Works.

askibinski’s picture

Also applied this patch.

Looks OK to me. Empty fieldset is gone.

Everything else seems to work fine.

jose reyero’s picture

Status: Needs review » Fixed

Thanks for the patches, done a simple fix though same idea.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.