On 01/12/2013 10:14 AM, aude wrote:
ContentHandler is fully backwards compatibility so not meant to be disruptive, but has potential to make things easier and better in the future for new features.
Sure. That makes total sense.
The feature is fully enabled with a configuration variable $wgContentHandlerUseDB to support multiple content formats in the same namespace. (e.g. user/site Javascript and CSS pages without the .js or .css suffix, along with wikitext pages in the MediaWiki namespace)
Right now, I'm focused on non-WMF users of MediaWiki and this sounds like something they should be aware of. If they install a new wiki and have $wgContentHandlerUseDB enabled, then what new risks do they need to be aware of? What are things they should be thinking about?
If someone installs MW and wants to use and expand this feature (as the WorkingWiki people might want to), where do they go to find information on it?
Right now, the on-wiki documentation refers to docs/contenthandler.txt. It seems like this area is ripe for on-wiki documentation, tutorials, and how-tos.