ac7467f0b4
- Added comprehensive AI Assistant system (aiassist/ directory): * Vector search and embedding capabilities * Typebot proxy integration * Elastic search functionality * Message classification and chat history * MCP proxy for external integrations - Implemented Court Status API (GetCourtStatus.php): * Real-time court document status checking * Integration with external court systems * Comprehensive error handling and logging - Enhanced S3 integration: * Improved file backup system with metadata * Batch processing capabilities * Enhanced error logging and recovery * Copy operations with URL fixing - Added Telegram contact creation API - Improved error logging across all modules - Enhanced callback system for AI responses - Extensive backup file storage with timestamps - Updated documentation and README files - File storage improvements: * Thousands of backup files with proper metadata * Fix operations for broken file references * Project-specific backup and recovery systems * Comprehensive file integrity checking Total: 26,461+ files added/modified including AWS SDK, vendor dependencies, and extensive backup system.
21 lines
754 B
Plaintext
21 lines
754 B
Plaintext
HTML.ForbiddenElements
|
|
TYPE: lookup
|
|
VERSION: 3.1.0
|
|
DEFAULT: array()
|
|
--DESCRIPTION--
|
|
<p>
|
|
This was, perhaps, the most requested feature ever in HTML
|
|
Purifier. Please don't abuse it! This is the logical inverse of
|
|
%HTML.AllowedElements, and it will override that directive, or any
|
|
other directive.
|
|
</p>
|
|
<p>
|
|
If possible, %HTML.Allowed is recommended over this directive, because it
|
|
can sometimes be difficult to tell whether or not you've forbidden all of
|
|
the behavior you would like to disallow. If you forbid <code>img</code>
|
|
with the expectation of preventing images on your site, you'll be in for
|
|
a nasty surprise when people start using the <code>background-image</code>
|
|
CSS property.
|
|
</p>
|
|
--# vim: et sw=4 sts=4
|