A metadata field to show history of a page

(Steve Brown) #1

Hi all,

 

The Logs functionality in matrix seems a bit light on when it comes to tracking what has happened to an asset over time.  

 

Examples: If one of my Sys Admins makes an edit to a live page, where can I see a record of that action?  If one of our publishers put something in Safe Edit and then three different publishers make edits to it before it goes back live, where can I see this in the logs?

 

Assuming that the logs cannot provide this sort of valuable info, I assume the only way we can capture this is by appending content to a (non-user-editable) metadata field using triggers.

 

Has anyone done something like this, or are there any other ideas for capturing a more readable, accessible, complete asset history?

 

We are on v4.18.2 and do not have rollback turned on (were warned against it due to the size of our DB - 500,000 assets and counting...)

 

Thanks,

 

Steve.

#2

Hey Steve!
We have rollback enabled and have over 800,000 assets on the system. The trick is truncating the rollback table often. We hadn’t done it in a while and it does slow down the backend when rolling back.

(Bart Banda) #3

If you are after logs on the content, you need to navigate down to the WYSIWYG (or raw) Content Type asset of a Bodycopy asset and view the logs screen on that asset, as that's where the content data is stored and logged. 

(Steve Brown) #4

If you are after logs on the content, you need to navigate down to the WYSIWYG (or raw) Content Type asset of a Bodycopy asset and view the logs screen on that asset, as that's where the content data is stored and logged. 

 

Thanks for the reply Bart,

 

But from what I can see I still dont know when that div has been edited.  I can see status changes and publish date changes...but what if the item is edited live?

(Steve Brown) #5

Hey Steve! We have rollback enabled and have over 800,000 assets on the system. The trick is truncating the rollback table often. We hadn't done it in a while and it does slow down the backend when rolling back.

 

Thanks for the reply.  Will have to look into rollback again by the looks - it was a fair few years ago now that I got that initial advice.  Dont think it is a solution for the immediate problem - even if we can get update info out of the rollback table, the truncation of it means that we will lose that info again at some time.

 

Not often I get to talk to someone with a larger implementation than us!  Im sure we have a lot of similar war stories to tell....

#6

  Thanks for the reply.  Will have to look into rollback again by the looks - it was a fair few years ago now that I got that initial advice.  Dont think it is a solution for the immediate problem - even if we can get update info out of the rollback table, the truncation of it means that we will lose that info again at some time.
 
Not often I get to talk to someone with a larger implementation than us!  Im sure we have a lot of similar war stories to tell....

#7

Ello there! Not a worry. We had found that we were only requiring rolling back very early and out of our 100 plus coordinators in admin we could see that only a few were using the function. Google analytics was good with extracting that too! Truncating the rollback table though with the entries we had over those assets took a few hours.

(Bart Banda) #8

 

Thanks for the reply Bart,

 

But from what I can see I still dont know when that div has been edited.  I can see status changes and publish date changes...but what if the item is edited live?

 

You should be able to get that info from the asset full log scalar log. See attached screenshot for where I'm looking. You don't get any info from that on your end? 

logs.jpg (42.4 KB)
#9

Ahhh didn’t know about the full log scalar!!!
Bart what would we do without you!


The logs have always been hit and miss. Will try that next week