Notes
Last updated on
2 May 2025
Installation
- Read the htmLawed documentation and note the filter's limitations.
- Check for conflicts with any third-party filter modules in use. Re-arranging filters used in a format can resolve conflicts. So can allowing htmLawed let through HTML tags/attributes introduced by other filters.
Updates
- Look for latest recommended versions on the htmLawed module project site.
- The htmLawed library files within the module's directory may be out of date. You can replace them with the latest version from the htmLawed website.
Configuration
- While the default configuration sets htmLawed to be run with config. parameter safe set to 1, security vulnerabilities may be created if other htmLawed parameters are not set appropriately. E.g., if the iframe element is permitted with config. parameter elements, one may want disable srcdoc attribute for iframe through config.'s deny_attribute parameter.
- The htmLawed filter allows use of custom functions during htmLawed filtering. If you want use of such functions, besides setting appropriate values in the Config. fields for the htmLawed module, you would need to have the functions accessible by htmLawed. E.g., in Drupal 6, one option is to have a custom PHP file with the functions in the root Drupal folder and have it included by Drupal by adding a require_once call in the Drupal settings.php file.
Help improve this page
Page status: No known problems
You can:
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion