You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The admin monitoring logs nearly every save and delete call in the backend.
4
+
The admin monitoring allows an shop owner to log almost every activity in the backend.
5
5
6
6
Facts
7
7
-----
@@ -15,53 +15,65 @@ Builds
15
15
16
16
Description
17
17
-----------
18
-
The admin monitoring logs nearly every save and delete call in the backend. The idea is to generate an overview of the changes in the backend to know who changed certain things.
18
+
The admin monitoring allows an shop owner to log almost every activity in the backend. The goal is to monitor all changes in the backend and show them in a nice view so that
19
+
a shop owner can monitor who changed what, e.g. logged in to the admin account, saved a product, deleted a customer, e.g.
19
20
20
21
### BE CAREFUL
21
22
This extension writes a lot of data into the database and we exclude only a few core classes. If you have many writes in the backend, please have a look into this to avoid a full hard disk!
22
23
23
-
To exclude a class, add it into the node `config/default/firegento_adminmonitoring_config/exclude/object_types`
24
+
There are currently several ways if you can exclude e.g. specific models, admin routes, field names from logging data to the database:
25
+
- Exclude all changes from a specific object (e.g. Mage_Index_Model_Event)
26
+
- Exclude all changes from a specific admin route (e.g. admin_sales_order_create_loadBlock)
27
+
- Exclude specific objects from specific admin routes (e.g. Mage_CatalogRule_Model_Flag from admin_promo_catalog_save)
28
+
- Exclude specific field names from every object (e.g. created_at, updated_at)
24
29
25
-
```xml
26
-
<config>
27
-
<default>
28
-
<firegento_adminmonitoring_config>
29
-
<exclude>
30
-
<object_types>
31
-
<Mage_Index_Model_Event />
32
-
<!-- omit infinite loops -->
33
-
<Firegento_AdminMonitoring_Model_History />
34
-
</object_types>
35
-
</exclude>
36
-
</firegento_adminmonitoring_config>
37
-
</default>
38
-
</config>
39
-
```
40
-
41
-
You can also exclude fields like updated_at ...
30
+
There is a basic *adminmonitoring.xml* file located in the "etc" folder of this extension with the following default excludes:
42
31
43
32
```xml
33
+
<?xml version="1.0"?>
44
34
<config>
45
-
<default>
46
-
<firegento_adminmonitoring_config>
47
-
<exclude>
48
-
<fields>
49
-
<updated_at />
50
-
<update_time />
51
-
</fields>
52
-
</exclude>
53
-
</firegento_adminmonitoring_config>
54
-
</default>
35
+
<adminmonitoring>
36
+
<excludes>
37
+
<object_types>
38
+
<Mage_Index_Model_Event/>
39
+
<Mage_Admin_Model_User/>
40
+
<Enterprise_Logging_Model_Event_Changes/>
41
+
<Enterprise_Logging_Model_Event/>
42
+
<!-- omit infinite loops -->
43
+
<FireGento_AdminMonitoring_Model_History/>
44
+
</object_types>
45
+
<fields>
46
+
<created_at/>
47
+
<updated_at/>
48
+
<create_time/>
49
+
<update_time/>
50
+
<low_stock_date/>
51
+
</fields>
52
+
<admin_routes>
53
+
<admin_sales_order_create_index/>
54
+
<admin_sales_order_create_loadBlock/>
55
+
<admin_sales_order_create_save/>
56
+
<admin_sales_order_invoice_save/>
57
+
<admin_sales_order_shipment_save/>
58
+
<admin_sales_order_creditmemo_save/>
59
+
<admin_sales_order_create_reorder/>
60
+
<admin_promo_catalog_save>
61
+
<Mage_CatalogRule_Model_Flag/>
62
+
</admin_promo_catalog_save>
63
+
</admin_routes>
64
+
</excludes>
65
+
</adminmonitoring>
55
66
</config>
56
67
```
57
68
69
+
58
70
### Third party integration
59
71
60
72
Events for model_save_after and model_delete_after are observed and changes automatically logged, if not excluded as described above.
61
73
So even third party models will be logged and can be even better integrated by link to their adminhtml edit form.
62
-
To do this observe the firegento_AdminMonitoring_rowurl event and see Firegento_AdminMonitoring_Model_RowUrl_Product for an catalog_product implementation which can be adapted.
74
+
To do this observe the event **firegento_adminmonitoring_rowurl**and see **Firegento_AdminMonitoring_Model_RowUrl_Product** for an catalog_product implementation which can be adapted for your custom models.
63
75
64
-
If you want to log your own events just dispatch the firegento_AdminMonitoring_log event:
76
+
If you want to log your own events just dispatch the event**firegento_adminmonitoring_log** and pass your custom data:
65
77
66
78
```php
67
79
Mage::dispatchEvent(
@@ -76,9 +88,14 @@ Mage::dispatchEvent(
76
88
);
77
89
```
78
90
91
+
If you want to exclude some more fields, admin routes, object types just create a custom *adminmonitoring.xml* file
92
+
in your custom module and add the necessary values in the same structure like in the default *adminmonitoring.xml* file of this extension.
93
+
94
+
79
95
Requirements
80
96
------------
81
97
- PHP >= 5.3.0 (or even 5.0 as long as [spl](http://www.php.net/manual/en/book.spl.php) is activated)
98
+
- PHP >= 5.5.0: json extension
82
99
83
100
Compatibility
84
101
-------------
@@ -90,6 +107,7 @@ Installation Instructions
90
107
1. Install the extension by copying all the extension files into your document root.
91
108
2. Clear the cache, logout from the admin panel and then login again.
92
109
3. You can now configure the extenion via *System -> Configuration -> Advanced -> Admin -> Admin Monitoring*
110
+
4. You can view all logging entries in *System -> Configuration -> Admin Monitoring*
93
111
94
112
Uninstallation
95
113
--------------
@@ -100,6 +118,8 @@ Uninstallation
100
118
DROPTABLE'firegento_adminmonitoring_history';
101
119
```
102
120
121
+
3. Please remove all integration for the admin monitoring in your custom modules.
122
+
103
123
Support
104
124
-------
105
125
If you have any issues with this extension, open an issue on [GitHub](https://github.com/firegento/firegento-customer/issues).
0 commit comments