Static pages: markup plugins

[Don Chambers]

Entries have the ability to disable specific markup plugins. Can we get this same ability for each static page? Right now, markup is an "all or nothing" selection.

This probably goes for HTML nuggets too.... might want to allow one specific type of markup, while blocking another.

[garvinhicking]

Hi!

I believe that could be done with changes in the staticpage plugin only. It would simply need to set an $eventData['properties']['disable_markup_blabla'] value, that could be gathered before it.

It's a lot of work to code, though. I can try to look into it mid-january, if you remind me.

This probably goes for HTML nuggets too.... might want to allow one specific type of markup, while blocking another.

That's a bit more challenging, but it could be done with similar code (but requires core s9y update of course).

Regards,
Garvin

[Don Chambers]

Thanks Garvin - I was looking at it from a consistency perspective. An example of it might be that I want to allow the nl2br markup plugin for a static page or html nugget, but disable another one, perhaps serendipity markup, or an optional markup plugin like smarty markup, etc.

[garvinhicking]

Hi!

Definitely! I think your feature request is very useful and must be implemented.

Maybe you can add it to the Sf.Net feature tracker so that it will not get lost?

Regards,
Garvin