HumHub Documentation (unofficial)

HTMLPurifier_URIFilter
in package

AbstractYes

Chainable filters for custom URI processing.

These filters can perform custom actions on a URI filter object, including transformation or blacklisting. A filter named Foo must have a corresponding configuration directive %URI.Foo, unless always_load is specified to be true.

The following contexts may be available while URIFilters are being processed:

 - EmbeddedURI: true if URI is an embedded resource that will
   be loaded automatically on page load
 - CurrentToken: a reference to the token that is currently
   being processed
 - CurrentAttr: the name of the attribute that is currently being
   processed
 - CurrentCSSProperty: the name of the CSS property that is
   currently being processed (if applicable)
Tags
warning

This filter is called before scheme object validation occurs. Make sure, if you require a specific scheme object, you you check that it exists. This allows filters to convert proprietary URI schemes into regular ones.

Table of Contents

Properties

$always_load  : mixed
True if this filter should always be loaded.
$name  : mixed
Unique identifier of filter.
$post  : mixed
True if this filter should be run after scheme validation.

Methods

filter()  : bool
Filter a URI object
prepare()  : bool
Performs initialization for the filter. If the filter returns false, this means that it shouldn't be considered active.

Properties

$always_load

True if this filter should always be loaded.

public mixed $always_load = \false

This permits a filter to be named Foo without the corresponding %URI.Foo directive existing.

Tags
type

bool

$name

Unique identifier of filter.

public mixed $name
Tags
type

string

$post

True if this filter should be run after scheme validation.

public mixed $post = \false
Tags
type

bool

Methods

prepare()

Performs initialization for the filter. If the filter returns false, this means that it shouldn't be considered active.

public prepare(HTMLPurifier_Config $config) : bool
Parameters
$config : HTMLPurifier_Config
Return values
bool

        
On this page

Search results