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
Copy file name to clipboardExpand all lines: 16/umbraco-cms/fundamentals/backoffice/logviewer.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -143,11 +143,11 @@ public class AzureTableLogsRepository : LogViewerRepositoryBase
143
143
}
144
144
```
145
145
146
-
Azure Table Storage requires entities to implement the `ITableEntity` interface. Since Umbraco’s default log entity does not implement this, a custom entity (`AzureTableLogEntity`) must be created to ensure logs are correctly fetched.
146
+
Azure Table Storage requires entities to implement the `ITableEntity` interface. Since Umbraco's default log entity does not implement this, a custom entity (`AzureTableLogEntity`) must be created to ensure logs are correctly fetched.
147
147
148
148
### Creating a custom log viewer service
149
149
150
-
The next thing we need to do is create a new service that amongs other things is responsible to figure out whether a certain log query is allowed.
150
+
The next thing we need to do is create a new service that amongst other things is responsible for figuring out whether a provided log query is allowed.
@@ -187,7 +187,7 @@ public class AzureTableLogsService : LogViewerServiceBase
187
187
188
188
### Register implementation
189
189
190
-
Umbraco needs to be made aware that there is a new implementation of an `ILogViewerRepository` to register. We also need to replace the default JSON LogViewer that is shipped in the core of Umbraco.
190
+
Umbraco needs to be made aware that there is a new implementation of an `ILogViewerRepository`and an `ILogViewerService`to register. These need to replace the default ones that are shipped with Umbraco.
0 commit comments