Give another user the ability to create Events with Signups

See point #5 in the INSTALL.txt file.

Go to admin/content/types/event on your site.
Scroll to the bottom and look for the "Signup options:" setting
Select the "Enabled (on by default)" radio button.

I have the same exact problem. My content type has enable signup on too. It would be create to set the signup settings when creating the node/event.

Well, seems like this isn't "fixed" then. Perhaps it's a bug. Perhaps some will have time/ability to debug it. ;)

#254192: Signup settings not shown when creating signed up enabled content marked duplicate.

I just looked at the code, and it's definitely a bug. Here's the problem:

function signup_alter_node_form($form_id, &$form) {
  ...
  // If the current user has the global 'administer all signups' permission
  // and signups are not explicitly disallowed, or if this node-type is
  // signup-enabled and the user has permission to administer signups for
  // their own content, add a fieldset for signup-related settings.
  if ( (($signup_type_default != 'disabled' || (!empty($node) && !empty($node->signup))) && user_access('administer all signups'))
       || (!empty($node) && $signup_type_default == 'enabled_on' && $node->uid == $user->uid && user_access('administer signups for own content')) ) {
    $form['signup'] = array(
      '#type' => 'fieldset',
      '#title' => t('Signup settings'),
      ...
    );
    ...
  }
}

If you read that (admittedly convoluted) if clause, you'll see that we never add the Signup settings fieldset to the node form if $node is empty (which is what happens at node/add/...) unless the current user has 'administer all signups'. So, someone just has to fix that logic to correctly handle the node/add case.

Can someone help and fix this?
Thanks advance...

Hello?

Is there anyone there who knows how to fix this? I am hopeless with code, but am happy to test :)

tracking

I have the same probleme. The user can't have the "helper" on creation but they have the option when they edit his node already created.

Ok... i'm not sure is the good way... Now i just test if the node is empty... i'm not sure is completely safe, but it's work. Can we test if the node is in "added state"?
Sorry i can't create a patch because i'm not on my machine and i would like go to sleep so.. perhaps tomorow :)

// If the current user has the global 'administer all signups' permission
  // and signups are not explicitly disallowed, or if this node-type is
  // signup-enabled and the user has permission to administer signups for
  // their own content, add a fieldset for signup-related settings.
  if ( (($signup_type_default != 'disabled' || (!empty($node) && !empty($node->signup))) && user_access('administer all signups'))
       || (!empty($node) && $signup_type_default == 'enabled_on' && $node->uid == $user->uid && user_access('administer signups for own content')) || (empty($node) && user_access('administer signups for own content')) ) {
    $form['signup'] = array(
      '#type' => 'fieldset',
      '#title' => t('Signup settings'),
      '#collapsible' => TRUE,
      '#collapsed' => TRUE,
      '#weight' => 30,
    );

It works fine with the above code change, but I think it kinda overrides the Signup disable settings for all the content types. Which means, you can't disable the signup for the content types you want....

I noticed this problem as well and would like to track any solutions than come up.

How about just adding the following check to the original code?

      (empty($node) && $signup_enabled && 
       user_access('administer signups for own content'))

So you have:

  if (user_access('administer all signups') ||
      (!empty($node) && $signup_enabled && $node->uid == $user->uid &&
       user_access('administer signups for own content')) ||
      (empty($node) && $signup_enabled && 
       user_access('administer signups for own content'))  ) {

I think the ($signup_type_default != 'disabled') check in comment 10 doesn't check that signup is enabled for the type and doesn't check that user has the privilege.

Ok, sorry, everyone's confused in here, and it's all my fault. That if clause is way too complicated in the first place, which is why everyone's having so much trouble with this. Furthermore, it occurs to me and starbow (sitting right next to me), that the logic was wrong for another reason: whether or not you have administer all vs. administer own perms shouldn't change the behavior in terms of node types that allow signups. If the site admin says that a given node type (foo) should allow signups (but doesn't have them enabled by default), and I can administer signups for my own content, and I can create foo nodes, I should still get the fieldset to signup-enable any particular foo node I create...

So, here's a patch that should hopefully make all the logic much more clear by splitting apart the giant if into some separate, easier-to-grok variables, and then the logic becomes very simple:

  if ($signups_possible && ($admin_all || $admin_own)) {

See attached patch. I tested this a bunch and I think it's good, but other eyes are welcome before I commit. ;)

Starbow tested this and couldn't break it, so I just committed to HEAD. Yay. ;)