Extracted text and test files from source code
This commit is contained in:
parent
676a7ea81c
commit
e7e66a9245
134 changed files with 0 additions and 14081 deletions
|
|
@ -1,53 +0,0 @@
|
|||
PREREQUISITES: Make sure you check HTML Purifier and make sure that you
|
||||
have fulfilled all of its requirements before running this. Specifically,
|
||||
you'll need the PHP extension ctype (in almost all PHP distributions),
|
||||
and it's nice to have dom and iconv.
|
||||
|
||||
* Place the htmlpurifier folder in your drupal modules directory.
|
||||
|
||||
* Download HTML Purifier from http://htmlpurifier.org/ You will need
|
||||
4.0.0 or later.
|
||||
|
||||
* There are two possible ways to install the HTML Purifier library.
|
||||
|
||||
1. Module directory installation. This means installing the library
|
||||
folder under the module directory. This way has the advantage of
|
||||
not depending on other modules. The issue is that when you
|
||||
upgrade the htmlpurifier module the HTML Purifier library gets
|
||||
removed and you have to re-extract the archive in the newly
|
||||
installed module directory.
|
||||
|
||||
2. The preferred way is making use of the libraries API,
|
||||
http://drupal.org/project/libraries. This makes the library
|
||||
available to all sites or to a specific site in a multisite
|
||||
Drupal setup. You'll need to download the libraries API module
|
||||
and enable it before enabling the htmlpurifier module so that in
|
||||
the install phase it can find the library.
|
||||
|
||||
Extract the library folder to libraries directory.
|
||||
|
||||
The final setup should be, when making the library and module
|
||||
available to all sites:
|
||||
|
||||
libraries/htmlpurifier/
|
||||
HTMLPurifier
|
||||
HTMLPurifier.autoload.php
|
||||
HTMLPurifier.auto.php
|
||||
HTMLPurifier.func.php
|
||||
HTMLPurifier.includes.php
|
||||
HTMLPurifier.kses.php
|
||||
HTMLPurifier.path.php
|
||||
HTMLPurifier.php
|
||||
HTMLPurifier.safe-includes.php
|
||||
|
||||
Now you can safely upgrade your htmlpurifier module without
|
||||
having to re-deploy the HTML Purifier library.
|
||||
|
||||
* Go to Administer > Site building > Modules and enable this module
|
||||
|
||||
* You can now create a new input format or add the HTML Purifier to an
|
||||
existing input format. It is recommended that you place HTML Purifier as
|
||||
the last filter in the input format. Reorder the filters if necessary.
|
||||
|
||||
WARNING: Due to HTML Purifier's caching mechanism, dynamic filters MUST NOT
|
||||
be placed before HTML Purifier.
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
|
||||
TODO List
|
||||
|
||||
Non-code
|
||||
- Add better documentation about what's different about configuring
|
||||
the PHP and what's configuring the web interface
|
||||
- Make distinction between module and library clearer
|
||||
- Link to WYSIWYG editors, research integration prospects, and how
|
||||
they're handling security
|
||||
- http://drupal.org/project/htmlarea
|
||||
- http://drupal.org/project/fckeditor
|
||||
- http://drupal.org/project/tinymce
|
||||
- Competitors
|
||||
- http://drupal.org/project/safehtml
|
||||
|
||||
1.3
|
||||
- Improve help text (this might be a good addition to the HTML Purifier
|
||||
core). This would be for filter tips as well as for the form.
|
||||
- Compatibility
|
||||
- Paging comments
|
||||
|
|
@ -1,50 +0,0 @@
|
|||
<?php
|
||||
|
||||
/**
|
||||
* @file
|
||||
* This file is a sample advanced PHP configuration file for the HTML Purifier
|
||||
* filter module. In reality, this file would be named N.php, where N is the
|
||||
* integer identifying the filter this is configuring. The configure page
|
||||
* for HTML Purifier (advanced) will tell you what file to copy this to.
|
||||
*
|
||||
* See this URI:
|
||||
*
|
||||
* http://htmlpurifier.org/live/configdoc/plain.html
|
||||
*
|
||||
* For full information about permitted directives. The most interesting ones
|
||||
* for custom configuration are ones with the 'mixed' type, as they cannot
|
||||
* be configured using the webform.
|
||||
*
|
||||
* @note
|
||||
* A number of directives have been predefined for you in order to better
|
||||
* work with Drupal. You can see what these defaults in the
|
||||
* _htmlpurifier_get_config() function in htmlpurifier.module.php.
|
||||
*
|
||||
* @warning
|
||||
* Please be mindful of the version of HTML Purifier you have installed!
|
||||
* All of the docs linked to are for the latest version of HTML Purifier;
|
||||
* your installation may or may not be up-to-date.
|
||||
*/
|
||||
|
||||
/**
|
||||
* Accepts an HTMLPurifier_Config configuration object and configures it.
|
||||
*
|
||||
* @param $config
|
||||
* Instance of HTMLPurifier_Config to modify. See
|
||||
* http://htmlpurifier.org/doxygen/html/classHTMLPurifier__Config.html
|
||||
* for a full API.
|
||||
*
|
||||
* @note
|
||||
* No return value is needed, as PHP objects are passed by reference.
|
||||
*/
|
||||
function htmlpurifier_config_N($config) {
|
||||
// Set your configuration here:
|
||||
$config->set('Core', 'Lexer', 'DirectLex');
|
||||
// $config->set('Namespace', 'Directive', $value);
|
||||
|
||||
// Advanced users:
|
||||
// $def = $config->getDefinition('HTML');
|
||||
// For more information about this, see:
|
||||
// http://htmlpurifier.org/docs/enduser-customize.html
|
||||
}
|
||||
|
||||
Reference in a new issue