TextFormatter module best practice – saving formatted content back to page

[AAD Web Team]

Hello, we've been working on a module to convert Microsoft Protected Links (Safe Links) so they display as their original URL.

Protected links leak the email address of the person who copied the link into the page (eg. https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.antarctica.gov.au&data=05|02|EMAILADDRESS%40example.com...)

This is not ideal, and we find more and more protected links turning up now that most of the Microsoft product offerings use protected links (Teams, Office, Copilot etc.)

TextFormatter modules typically only reformat the text on output, leaving the page content containing the protected link. Is it acceptable for a Text Formatter module to save the formatted string back to the page? Maybe as an optional configuration in the module settings? Or, is it better to achieve this using a standard module?

Edited Tuesday at 11:20 PM by AAD Web Team

[monollonom]

10 hours ago, AAD Web Team said:

Or, is it better to achieve this using a standard module?

Like you said a TextFormatter formats on output and thus should leave the original data intact (otherwise this could lead to unexpected behaviours). Best would be to create a module and hook before Pages::save for example to sanitize and convert those safe links

[AAD Web Team]

Thanks @monollonom, we'll trial down the path of a standard module in that case. With configuration options to choose what fields to target.