Antti Alasvuo
OMVP
May 20, 2023
visibility 2038
star star star star star
(1 votes)

Swapcode.Optimizely.AuditLog updated to v1.4.1

If you are using my audit log add-on Swapcode.Optimizely.AuditLog then I suggest that you update it in your solution.

I've been waiting now for few years for Optimizely to fix the styles used in the Change Log tool in admin view, but seems like they don't have time to fix the styles for the table.

In the past the log messages have not been visible without using browser developer tools to see the HTML source..

In this new version I've changed the structure of the activity log entry, and now you can see usually most of the relevant information.

There is still issue with the Change Log styling, you need to scroll the table to right, and the last column size depends on your browser window size, but there is nothing I can do about it ;-D

Another change I did was I added a new extension method for IServiceCollection, AddAuditLog(), which you should start using instead of the old way.

// replace old code
services.AddEmbeddedLocalization<AuditLogInitializationModule>();

// with the new extension method, which should be done after call to .AddCms()
.AddAuditLog();

The add-on is still using the initialization module to register the event handlers but this is preparation to change the implementation in a following update, so the AddAuditLog method actually just currently registers the embedded resources ;-)

The updated NuGet package should show up to the Optimizely NuGet feed shortly, but in the meantime you can manually get the updated NuGet package from my GitHub repository releases.

May 20, 2023

Comments

error Please login to comment.
Latest blogs
cms13-scan: A Deterministic CMS 13 Readiness Scanner

Every CMS 12 to CMS 13 upgrade I have looked at starts the same way. Someone opens the solution and starts hunting. A text search for the APIs

Adnan Zameer | Oct 12, 2026 |

Setting Up an Optimizely CMS 13 MCP Server Locally with Codex

Optimizely CMS 13 supports Model Context Protocol (MCP) , allowing AI tools such as Claude and Codex to interact with CMS content and metadata...

Mardy | Oct 12, 2026

Handling SixLabors.ImageSharp vulnerability warnings in Optimizely CMS 12 (unofficial)

UPDATED: Optimizely is officially working with SixLabors to find a solution, if possible; the work ID is CMS-57231. An official decision/announceme...

Cuong Nguyen Dinh | Oct 10, 2026

Optimizely CMS 12 on .NET 10: Fixing a Siteimprove TypeMismatchException

Recently, while upgrading an Optimizely CMS 12 solution from .NET 8 to .NET 10, we encountered a frustrating exception that initially looked like a...

Madhu | Oct 9, 2026 |