render_unsafe_content in [4472] could be restricted to read-only pages.

[martin@…]

In my case i don't want to allow the unsafe content to be available on all pages (the scripts are used to allow documentation to have special links for firefox browsers to load pkcs11 modules). So instead of turning this feature on wiki-wide I would be happy and more secure if i could turn it on for read-only pages only (as I'm willing to make that page read-only)

[Christian Boos]

I think it's a good idea.

[anonymous]

This sounds like a great enhancement, I would really like to have that.

Any progress on the issue?

[Christian Boos]

No, it's not exactly clear either how this could be implemented cleanly.

Eventually (ab)using the permission system with a RENDER_UNSAFE_CONTENT capability and in the WikiProcessor, checking that permission for the formatter.resource. The advantage of such an approach would be to be able to modulate the render_unsafe_content on a per-resource basis. It would also be possible to write an IPermissionPolicy plugin that would grant that "permission" for all read-only wiki page.