web-based, open-source
collections management software for museums and more
If you have installed and enabled the mail_edit module then you can go to admin/build/mail_edit to edit the mail templates.
You will find that the subscriptions module is providing a range of templates. Which template is used for a particular notification depends on the kind of subscription that is triggering it. So for example a notification that is sent because the user has subscribed to a taxonomy term will use the subscriptions_taxonomy_node-tid template. Notifications that are sent because the user has subscribed to a content type will use the content type specific template, for example subscriptions_content_node-type-blog for a subscription to all blogs. Similarly, a notification that is sent because the user has subscribed to a specific node will usually use the subscriptions_content_node-nid template.
However, there is an exception to the above rule: notifications of updated nodes that are sent because of a node subscription will nevertheless use the content-type-specific template, but only for those content types that the user could subscribe to. Note that this exception is only used for subscriptions to individual nodes, NOT to any other subscription type. So, for example, if a notification is sent out about an updated book page because the user has subscribed to a particular taxonomy term that the book page is tagged with, then the notification will NOT use the book page template subscriptions_content_node-type-book but the generic subscriptions_content_node-nid template.
If the user has chosen to get the notifications in digest form then always the template subscriptions_mail_digest will be used.
A long list of available variables that you can use in your templates are listed on the template editing pages when you expand the "Replacement patterns" fieldsets. Some of the variables are only available after you have saved the template once. If you enable the subscriptions CCK field module then, in the content type specific templates, you will get extra variables for each CCK field that exists for the content type.
If you have installed and enabled the mail_edit module then you can go to admin/build/mail_edit to edit the mail templates.
You will find that the subscriptions module is providing a range of templates. Which template is used for a particular notification depends on the kind of subscription that is triggering it. So for example a notification that is sent because the user has subscribed to a taxonomy term will use the subscriptions_taxonomy_node-tid template. Notifications that are sent because the user has subscribed to a content type will use the content type specific template, for example subscriptions_content_node-type-blog for a subscription to all blogs. Similarly, a notification that is sent because the user has subscribed to a specific node will usually use the subscriptions_content_node-nid template.
However, there is an exception to the above rule: notifications of updated nodes that are sent because of a node subscription will nevertheless use the content-type-specific template, but only for those content types that the user could subscribe to. Note that this exception is only used for subscriptions to individual nodes, NOT to any other subscription type. So, for example, if a notification is sent out about an updated book page because the user has subscribed to a particular taxonomy term that the book page is tagged with, then the notification will NOT use the book page template subscriptions_content_node-type-book but the generic subscriptions_content_node-nid template.
If the user has chosen to get the notifications in digest form then always the template subscriptions_mail_digest will be used.
A long list of available variables that you can use in your templates are listed on the template editing pages when you expand the "Replacement patterns" fieldsets. Some of the variables are only available after you have saved the template once. If you enable the subscriptions CCK field module then, in the content type specific templates, you will get extra variables for each CCK field that exists for the content type.
If you have installed and enabled the mail_edit module then you can go to admin/build/mail_edit to edit the mail templates.
You will find that the subscriptions module is providing a range of templates. Which template is used for a particular notification depends on the kind of subscription that is triggering it. So for example a notification that is sent because the user has subscribed to a taxonomy term will use the subscriptions_taxonomy_node-tid template. Notifications that are sent because the user has subscribed to a content type will use the content type specific template, for example subscriptions_content_node-type-blog for a subscription to all blogs. Similarly, a notification that is sent because the user has subscribed to a specific node will usually use the subscriptions_content_node-nid template.
However, there is an exception to the above rule: notifications of updated nodes that are sent because of a node subscription will nevertheless use the content-type-specific template, but only for those content types that the user could subscribe to. Note that this exception is only used for subscriptions to individual nodes, NOT to any other subscription type. So, for example, if a notification is sent out about an updated book page because the user has subscribed to a particular taxonomy term that the book page is tagged with, then the notification will NOT use the book page template subscriptions_content_node-type-book but the generic subscriptions_content_node-nid template.
If the user has chosen to get the notifications in digest form then always the template subscriptions_mail_digest will be used.
A long list of available variables that you can use in your templates are listed on the template editing pages when you expand the "Replacement patterns" fieldsets. Some of the variables are only available after you have saved the template once. If you enable the subscriptions CCK field module then, in the content type specific templates, you will get extra variables for each CCK field that exists for the content type.
test topic
The subscriptions module enables users to subscribe to be notified of new or updated nodes or of comments. Users can subscribe to individual nodes, all nodes of a particular content type or all nodes tagged with a particular taxonomy term, for example all topics in a particular forum or entries in a particular blog.
The subscriptions module provides a flexible framework that allows other modules to provide additional subscription types, for example by author or organic group.
Once enabled, all nodes can have an additional link that allows the user to change their subscriptions. In addition, users have a tab on their user screen from where they can manage all of their subscriptions. Users can also set an auto subscribe function which notifies them if anyone comments on or updates posts they have made. Admins can set this on by default.
Users can choose the frequency of notification emails and can also choose to have them delivered in digest form. The admin can customise the notification emails using mail templates.
For each subscription the user can choose whether to be notified only of new nodes, or also of updates, or also of comments. The admin has fine control of which of the many subscription options to make available to the user. The subscription user interface can hence be as simple or as complex as the admin likes.
The subscription module is similar to the notifications module. Both are rewrites of the old 5.x-1 subscriptions module. Both modules provide extensible frameworks. However the two modules differ in the details of the types of options and functionality they provide.
This page is work in progress. Please contribute.