You are here

INSTALL.txt in Signup 6.2

Same filename and directory in other branches
  1. 5.2 INSTALL.txt
  2. 5 INSTALL.txt
  3. 6 INSTALL.txt
  4. 7 INSTALL.txt
It is assumed that you have Drupal up and running.  Be sure to check
the http://drupal.org web site if you need assistance.  If you run
into problems, you should always read the INSTALL.txt that comes with
the Drupal package and read the online documentation.


0. Always backup your database before you enable a new contributed module!


1. Place the signup package into your Drupal modules/ directory.


2. (Optional) Customize the form presented to users when signing up
   for content on your site.  Unfortuantely, there is not yet a way to
   do this from within your site, you must implement hook_signup_pane_info in
   a module to register a callback that returns form elements.


3. Enable the signup module by navigating to:
   Administer > Site building > Modules

   Note: if you want support for automatic closing of events and
   reminder emails you must also install and enable either the Event
   module (http://drupal.org/project/event) or use the Date module
   (http://drupal.org/project/date) and add at least one date field.

   Click the 'Save configuration' button at the bottom to commit your
   changes.


4. For the final configuration of the module, navigate to:
   Administer > Site configuration > Signup

   Here you can configure the options for the module.


5. Enable the node types that you wish to allow signups for under:
   Administer > Content management > Content types

   You may wish to create a new content type specifically for event
   signups (which you can customize via the Content Construction Kit
   from http://drupal.org/project/cck), or install the Event module
   (http://drupal.org/project/event).


6. Grant the proper access to user accounts under:
   Administer > User management > Access control

   'sign up for content':
     Allows users to sign up for any content types that are signup-enabled.
     NOTE: Enabling 'sign up for content' for the anonymous user will
     allow anonymous users to sign up by entering an email address.

   'cancel own signups':
     Allows users to cancel their own signups. Without this permission,
     only users with 'administer all signups' or 'administer signups for
     own content' permission are allowed to cancel signups.
     NOTE: Anonymous users aren't allowed cancel their signups even if
     this permission is granted to the role 'anonymous user'.

   'edit own signups':
     Allows users to edit their own signups.  When viewing their own
     signup information, users will be able to update the values.
     NOTE: Anonymous users aren't allowed edit their signups even if
     this permission is granted to the role 'anonymous user'.

   'view all signups':
     Allows users to view all of the users who have signed up for any
     signup-enabled content on the site.

   'email all signed up users':
     Allows users to send an email to everyone who has signed up for
     any signup-enabled content on the site.

   'email users signed up for own content':
     Allows a user to send an email to everyone who has signed up for
     content owned by the user.

   'admininister all signups':
     Implies 'view all signups' and 'cancel own signups' permissions.
     Allows users to view who has signed up for nodes, to cancel
     signups of other users, to close signups for specific nodes, and
     to configure system-wide settings related to this module.

   'administer signups for own content':
     Allows users to view who has signed up, to cancel signups of
     other users, and to close signups for any nodes that the user owns.

   'cancel signups':
     Allows users that can administer signups for a given node to
     cancel the signups of other users from the node/N/signups page. 

   Viewing the signup report (Administer > Content management > Signup),
   and configuring the module (Administer > Site configuration > Signup)
   are restricted to users who have the 'access administration pages'
   privilege.


7. (Optional) If you have enabled the Views module on your site
   (http://drupal.org/project/views), be sure you are running Views
   version 5.x-1.6 or later.  Once you have everything installed and
   working, you should consider customizing any of the signup-related
   views to better suit the needs of your site.  For example, if you
   are using the event module, you might want to add a filter to the
   'current signups' view to restrict it to events that have not
   started yet.

8. (Optional) Configure if and how you want a list of users signed up
   for each node to appear.  Under the 'Advanced settings' at
   admin/settings/signup, if the signup form and related information
   is being displayed on the node itself or on a separate tab, you
   will find a setting to control how you want the list of signed up
   users to appear.  You can either use the built-in listing, no
   listing at all, or if you have enabled the Views module on your
   site (see step #7 above), you can also embed a view for this.

   There is a default view included called 'signup_user_list' which is
   disabled by default.  If you enable this view to customize it at
   all, you should be careful about two things:

   A) Be sure to restrict access to this view to roles that have the
      'view all signups' permission to avoid information disclosure.

   B) If you continue to embed the view on the signup nodes, be sure
      to disable the menu items for the view, so that you don't get a
      duplicate tab with the same information.

   Note that if you just use it in its default (disabled) form, it
   will still work as an embedded view under the signup form, and you
   do not need to worry about these two things.

   Of course, instead of embedding the view under the signup form, you
   can also disable the setting entirely, then enable the default
   'signup_user_list' view to provide the information on a separate
   tab or in a block.


9. Start signing up!

File

INSTALL.txt
View source
  1. It is assumed that you have Drupal up and running. Be sure to check
  2. the http://drupal.org web site if you need assistance. If you run
  3. into problems, you should always read the INSTALL.txt that comes with
  4. the Drupal package and read the online documentation.
  5. 0. Always backup your database before you enable a new contributed module!
  6. 1. Place the signup package into your Drupal modules/ directory.
  7. 2. (Optional) Customize the form presented to users when signing up
  8. for content on your site. Unfortuantely, there is not yet a way to
  9. do this from within your site, you must implement hook_signup_pane_info in
  10. a module to register a callback that returns form elements.
  11. 3. Enable the signup module by navigating to:
  12. Administer > Site building > Modules
  13. Note: if you want support for automatic closing of events and
  14. reminder emails you must also install and enable either the Event
  15. module (http://drupal.org/project/event) or use the Date module
  16. (http://drupal.org/project/date) and add at least one date field.
  17. Click the 'Save configuration' button at the bottom to commit your
  18. changes.
  19. 4. For the final configuration of the module, navigate to:
  20. Administer > Site configuration > Signup
  21. Here you can configure the options for the module.
  22. 5. Enable the node types that you wish to allow signups for under:
  23. Administer > Content management > Content types
  24. You may wish to create a new content type specifically for event
  25. signups (which you can customize via the Content Construction Kit
  26. from http://drupal.org/project/cck), or install the Event module
  27. (http://drupal.org/project/event).
  28. 6. Grant the proper access to user accounts under:
  29. Administer > User management > Access control
  30. 'sign up for content':
  31. Allows users to sign up for any content types that are signup-enabled.
  32. NOTE: Enabling 'sign up for content' for the anonymous user will
  33. allow anonymous users to sign up by entering an email address.
  34. 'cancel own signups':
  35. Allows users to cancel their own signups. Without this permission,
  36. only users with 'administer all signups' or 'administer signups for
  37. own content' permission are allowed to cancel signups.
  38. NOTE: Anonymous users aren't allowed cancel their signups even if
  39. this permission is granted to the role 'anonymous user'.
  40. 'edit own signups':
  41. Allows users to edit their own signups. When viewing their own
  42. signup information, users will be able to update the values.
  43. NOTE: Anonymous users aren't allowed edit their signups even if
  44. this permission is granted to the role 'anonymous user'.
  45. 'view all signups':
  46. Allows users to view all of the users who have signed up for any
  47. signup-enabled content on the site.
  48. 'email all signed up users':
  49. Allows users to send an email to everyone who has signed up for
  50. any signup-enabled content on the site.
  51. 'email users signed up for own content':
  52. Allows a user to send an email to everyone who has signed up for
  53. content owned by the user.
  54. 'admininister all signups':
  55. Implies 'view all signups' and 'cancel own signups' permissions.
  56. Allows users to view who has signed up for nodes, to cancel
  57. signups of other users, to close signups for specific nodes, and
  58. to configure system-wide settings related to this module.
  59. 'administer signups for own content':
  60. Allows users to view who has signed up, to cancel signups of
  61. other users, and to close signups for any nodes that the user owns.
  62. 'cancel signups':
  63. Allows users that can administer signups for a given node to
  64. cancel the signups of other users from the node/N/signups page.
  65. Viewing the signup report (Administer > Content management > Signup),
  66. and configuring the module (Administer > Site configuration > Signup)
  67. are restricted to users who have the 'access administration pages'
  68. privilege.
  69. 7. (Optional) If you have enabled the Views module on your site
  70. (http://drupal.org/project/views), be sure you are running Views
  71. version 5.x-1.6 or later. Once you have everything installed and
  72. working, you should consider customizing any of the signup-related
  73. views to better suit the needs of your site. For example, if you
  74. are using the event module, you might want to add a filter to the
  75. 'current signups' view to restrict it to events that have not
  76. started yet.
  77. 8. (Optional) Configure if and how you want a list of users signed up
  78. for each node to appear. Under the 'Advanced settings' at
  79. admin/settings/signup, if the signup form and related information
  80. is being displayed on the node itself or on a separate tab, you
  81. will find a setting to control how you want the list of signed up
  82. users to appear. You can either use the built-in listing, no
  83. listing at all, or if you have enabled the Views module on your
  84. site (see step #7 above), you can also embed a view for this.
  85. There is a default view included called 'signup_user_list' which is
  86. disabled by default. If you enable this view to customize it at
  87. all, you should be careful about two things:
  88. A) Be sure to restrict access to this view to roles that have the
  89. 'view all signups' permission to avoid information disclosure.
  90. B) If you continue to embed the view on the signup nodes, be sure
  91. to disable the menu items for the view, so that you don't get a
  92. duplicate tab with the same information.
  93. Note that if you just use it in its default (disabled) form, it
  94. will still work as an embedded view under the signup form, and you
  95. do not need to worry about these two things.
  96. Of course, instead of embedding the view under the signup form, you
  97. can also disable the setting entirely, then enable the default
  98. 'signup_user_list' view to provide the information on a separate
  99. tab or in a block.
  100. 9. Start signing up!