This issue was created in response to a discussion on: http://drupal.org/node/1531916.

For some companies' Drupal websites, protocols need to be kept as the user creates/updates their newsletter status.

Proposed is the following:
- Adding an option in the Admin API Pages to enable/disable protocolling
- Add a table "simplenews_protocol" in the Database that mimics the watchdog table.
- Add code to simplenews_subscriber_save and calling functions so that a protocol entry is created when a user changes the value of any subscription.

Either the protocolling can appear as a feature in the base module, as a sub-module packaged with the base module, or as a separate module (like simplenews_statistic) is now.

Please send feedback.

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Need to think about this.

Another possibility might be to rely on http://drupal.org/project/message and provide integration with that, possibly through the existing rules integration. Would be very flexible and customizable, so admins could configure what kind of messages are logged how.

Then we'd need to find a way to display these messages on the subscriber page, though. So maybe that's more something for the upcoming 7.x-2.x branch where the plan is to convert our custom data structures to entities.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

- Let's start with this as a feature in the main module
- Then provide a API function to add a protocol message and one to get messages of a given subscriber. Something like:

simplenews_protocol_add($snid, $message, $variables, $timestamp = REQUEST_TIME);
simplenews_protocol_list($snid); // Returns an array of the entries

Then we can start to use this in the subscribe/unsubscribe functions and maybe add more usages. We can use the list function to display a list of messages on the admin subscriber form.