-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log changes to patterns #57
Comments
Planning to use the Stream plugin for logging changes, so this is pending the merge of one of these PRs:
For the "adding a reason part" work is in progress on an "Internal Notes" plugin. Logging changes isn't critical for the initial launch, so I changed the milestone on this one to Pattern Creation instead. |
Development on the Stream plugin seems stalled, I haven't gotten any further responses on my PRs. I suspect we will need to write our own connector for post changes if we still want to use the plugin. |
The xwp/stream#1264 pull request has been merged and will be included in the next version of Stream. |
This enables the new logging feature in the Internal Notes plugin for the Pattern post type, and adds some custom logging for when a pattern gets flagged and when flags are managed by moderators. Fixes #57
There are probably several reasons why we'd want to be able to audit changes made to a pattern. One is so we can see who removed a pattern from the directory, when they did it, and why, if they include a reason.
A log entry should have a date, user name, type of change, and an optional comment. It might look something like this:
Log entries could be added both by automated processes (by "patternbot" or something) or by user-driven actions. In some cases the comment field could get populated automatically with pre-determined values. In other cases, like when a moderator is manually changing the status of a pattern, a textarea field should be available to add a reason, which would then get added to the log's comment field.
The text was updated successfully, but these errors were encountered: