Widget Activities in Inactive Widgets area
desaiuditd opened this issue · comments
It seems that Stream is not able to log widget activities/changes from the Inactive Widgets area. Following two use cases are not being tracked down:
- Widgets are sorted
- A widget is updated
"Widget is deleted from Inactive Area" is already handled in #282
@desaiuditd Nice catch! We definitely need to track updates to widgets wherever they may be.
However i'm not sure if we really need to track sorting of inactive widgets, doesn't make much sense to me. @fjarrett Thoughts ?
Yeah, probably no need to track sorting of inactive widgets. It's really just a trash area for widget instances.
@shadyvb @westonruter Why not? I mean, it's a WordPress change so shouldn't Stream be tracking every single thing that is changed, be it big or small? With the changes coming in #251 people can easily opt-out of tracking whatever they think is unnecessary in their opinion.
Inactive widget order is not a user-specific order (like reordering metaboxes or something) it is an order that affects all users on that screen. Correct me if I'm wrong about this.
Maybe some more deep thought/discussion should be done about where exactly we draw the line for Stream, what it should track, and what it should not track.
Correct. Inactive widget order is not user-specific. All users would see the same.
@fjarrett I do not think a user would be able to ignore this type of action, since he'd need to disable all Widgets::Order actions and lose updates to order operations in other sidebars as well.
My POV is that while we do strive to track almost everything, admins would have so little benefit knowing of such actions, so it'd just clutter the Stream list.
@shadyvb Yes, that's certainly the counter-argument here, and it's definitely a valid one. But to answer your question, they could just by excluding the "Inactive Sidebar" context.
Yea! didn't think of that. If they can filter/exclude it, then it'd only be natural to track everything and have users filter out what they do not want.
/five for the global exclusion settings idea!
👍 to @fjarrett
Though even I think a concrete scope for the plugin needs to be defined, as the plugin will grow it is prone to face issues like this on a front and not just specific to any individual module.
@desaiuditd You are clear to go ahead and proceed with this issue! And thanks for reporting it. /five