Hello, thank you so much for this module. By and large it is working fantastic -- however, there is a little glitch in the system, as far as I can tell (assuming that I have set everything up appropriately :-)).

Here it is: I cannot seem to "disable" the signups option for particular nodes, e.g., forum topics, personal blog items.

I do not want content creators to be able to "enable signups" for their blog entries, or their forum postings. I only want them to be able to enable signup for content-type "events".

However, when I go to the administer > content > configure > content types and I un-click the "Allow Signups" checkbox for the "forum" and "blog" content-types -- in spite of this, authors of "forum" and "blog" postings, still are given an option to "enable signups for this node" whenever they are posting their new content.

That is to say -- the "Allow Signups" checkbox does not seem to work. (Even when the checkbox is unchecked, signups are still allowed. .)

Thank you for your attention. And assistance, and hard work.

Albert
www.ithou.org

Comments

hunmonk’s picture

hunmonk commented
Assigned: Unassigned » hunmonk
Status: Active » Fixed

this is by design--node types can either be enabled as signup nodes by default, or any node not enabled by default can be made a signup node 'on the fly'. however, only people with the 'admin signups' permission should be able to make a node a signup node on the fly, so i have added this check to the code in 4.6 and HEAD

venkat-rk’s picture

venkat-rk commented

Like the original poster, I am finding this module very valuable. Thank you for all your effort.

However, I would like to again bring up the issue of signup permissions on nodes (for those with admin signup permissions) overriding the global signup configuration for the content type. I really feel this should be thought out again as it can create a peculiar situation in some use cases.

For example, on my web site for a non-profit community network, I created a flexinode content type called 'Other event' using which non-profits and companies could share information about events not related directly to the network but which they deem to be useful to the community. Since the members have admin signup permissions, they of course have the overriding permission on the node.

As the site admin, it would be one less hassle if external organisations did not have some kind of a backdoor for running event signups through my site. Sure, I can explain this to my users, but it would be better if it wasn't there in the first place.

The only way I can turn this off would be to turn off their admin signup permission, which would hurt their ability to use signups for other event types.

hunmonk’s picture

hunmonk commented
Status: Fixed » Active

ramdak: what would be your suggested solution?

jsimonis’s picture

jsimonis commented

Mayve have it work similar to the other options-- where you can set which roles can even see the ability to override the default setting?

venkat-rk’s picture

venkat-rk commented

Oops! Hunmonk, I really don't know how I missed your reply. Sorry.

I don't have the time right now, but I would second jsimonis' suggestion. If I can think of another way, I will get back soon.

hunmonk’s picture

hunmonk commented

so you're suggesting a seperate permission for this one operation?

hunmonk’s picture

hunmonk commented
Category: bug » feature
Status: Active » Postponed

postponing for now--i won't make any feature changes in the module until we've mapped out how it's going to change based on the direction of the event module.

dww’s picture

dww
we/he/they
commented
Version: 4.6.x-1.x-dev » 4.7.x-1.x-dev
Assigned: hunmonk » dww
Status: Postponed » Closed (duplicate)

this will all be solved by my patch in http://drupal.org/node/49007