Hi Patabugen,
Unfortunately not. This is a slippery slope. Categories are one thing, but what if Stream tracked every change that was made when you edited a post! That’s a lot of data.
Stream focuses on tracking the where / when / who of admin updates, but not the specific details of what. This would be far too much information to store in your local database.
Hey Luke,
Thanks for your reply. I wanted to use Stream to be able to track down when something was broken (and ideally by who).
The current problem I’m learning I can’t use Stream for us somebody has (hopefully) unchecked a box from a category which should be checked – I say hopefully because I’d rather know that it was a user than a faulty plugin.
So Stream has my vote for being able to track a little bit more, without it I’m actually not sure how useful Stream is at all – though it clearly is to so many users so I’d be interested in some use-cases (perhaps on your website).
—
Sami
Hi Sami,
Suppose you noticed that a category description had changed, and you weren’t sure when and how, you could log into Stream and filter the results to just the Category taxonomy, drilling down to figure out who could have changed it.
In terms of other use cases, although we can’t track specifics for taxonomies and post types, we do track specifics for other settings. So you would be able to see when particular settings where changed.
The reason we don’t track all the changes to posts (besides the fact that it’s a lot of data to store) is because WordPress already keeps Post revisions, so you can easily drill down through the revisions to find a particular change. Categories are a bit different, since there is really only category name, description and parent, I’m not sure how useful it would be to track those individual items.
If you had custom meta for your category, that becomes more difficult again. For a start, Stream only knows that a term has been updated, you would have to tell it to look for a particular piece of information if that information isn’t already built into WordPress. Secondly, there are scalability issues – should Stream automatically check hundreds of different meta keys every time a term is updated, and log the before and after values if there is a change?
