As a BO admin I want to be able to track changes done from the Back Office

[matks]

Is your feature request related to a problem?

As a BO admin I want to be able to track changes done from the Back Office. I want to know when a product properties has been updated, when a product has been deleted, when a category was renamed... because sometimes my shop settings are wrong and I want to understand how it ended up in this situation.

Describe the solution you'd like

A way to track changes related to an item of PrestaShop (a product, a category, an order...)

Log entries seem a good way to achieve this.

Additional context

User need reported by @ldeprestashop . @ldeprestashop can you elaborate?

[PululuK]

Hi @matks @ldeprestashop

IMHO I think we need :

• Improve logs controllers : (started here Improve admin logs  #21075)
• Add missing log datas in some controllers and classes : (Started here Missing log datas in some controllers and classes #18519)

I can take this issue 😉

Thanks

[matks]

• Missing log datas in some controllers and classes #18519

Hi @PululuK indeed your contributions very well match this need 😉 . I think we can think of other items we can add to the list.

One thing I had in mind was to add a logger middleware to our Command and Query Buses: by implementing this, everytime a Command or Query would be dispatched in the software we would get one log.

[PululuK]

Yeah ! I like the idea @matks
The problem of the logs that they fill up very quickly, I'm afraid that the log table will explode. Should we perhaps analyze the relevance of the actions to be logged?

[Hlavtox]

Hi everyone, my 5 cents to this topic. THIS IS EXTREMELY GOOD IDEA AND IMPORTANT THING. 👍 👍 👍

Even with only few employees, as a boss, you need to know who did this or who screwed up that. In our ERP, every single action on every single object is logged - date and time, employee, what data changed, previous state and final state. Can't imagine living without it in those "how the hell this happened" cases.

I think that the current Prestashop log system can be used for that (except for precise previous/current states - can be limited to "product->description changed"), but it needs to be configurable and a regular cleaning system should be made. We grew our ERP DB to 10 GB in first year and a half, mainly because of logs. 😄

[micka-fdz]

+1 for this good idea ! Very useful for agencies like us to know if errors come from us or merchants 😂

[ldeprestashop]

@matks Ye I can make a specification.

Just wait 2 week, I must focus on Product days and finish strategics plan before ;)

[jolelievre]

Log entries might be a bit simple for this feature, I guess the ideal would be a true Event sourcing feature that would be saved in DB with dates, associated action/customer/employee/...

[matks]

Log entries might be a bit simple for this feature, I guess the ideal would be a true Event sourcing feature that would be saved in DB with dates, associated action/customer/employee/...

PrestaShop logs is a SQL table which contain all that. I should have been clearer 😅 I was thinking about this kind of logs not text file logs.