[weblabels.fsf.org.git] / crm.fsf.org / 20131203 / files / sites / all / modules-new / civicrm / packages / IDS / vendors / htmlpurifier / HTMLPurifier / ConfigSchema / schema / HTML.AllowedModules.txt

HTML.AllowedModules\r
TYPE: lookup/null\r
VERSION: 2.0.0\r
DEFAULT: NULL\r
--DESCRIPTION--\r
\r
<p>\r
    A doctype comes with a set of usual modules to use. Without having\r
    to mucking about with the doctypes, you can quickly activate or\r
    disable these modules by specifying which modules you wish to allow\r
    with this directive. This is most useful for unit testing specific\r
    modules, although end users may find it useful for their own ends.\r
</p>\r
<p>\r
    If you specify a module that does not exist, the manager will silently\r
    fail to use it, so be careful! User-defined modules are not affected\r
    by this directive. Modules defined in %HTML.CoreModules are not\r
    affected by this directive.\r
</p>\r
--# vim: et sw=4 sts=4\r
Commit	Line	Data
7f254ad8 AE	1	HTML.AllowedModules\r
	2	TYPE: lookup/null\r
	3	VERSION: 2.0.0\r
	4	DEFAULT: NULL\r
	5	--DESCRIPTION--\r
	6	\r
	7	<p>\r
	8	A doctype comes with a set of usual modules to use. Without having\r
	9	to mucking about with the doctypes, you can quickly activate or\r
	10	disable these modules by specifying which modules you wish to allow\r
	11	with this directive. This is most useful for unit testing specific\r
	12	modules, although end users may find it useful for their own ends.\r
	13	</p>\r
	14	<p>\r
	15	If you specify a module that does not exist, the manager will silently\r
	16	fail to use it, so be careful! User-defined modules are not affected\r
	17	by this directive. Modules defined in %HTML.CoreModules are not\r
	18	affected by this directive.\r
	19	</p>\r
	20	--# vim: et sw=4 sts=4\r