| Summary | Allow to size restrict the tidy extension |
| Queue | IMP |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | wrobel (at) horde (dot) org |
| Created | 06/22/2011 (5274 days ago) |
| Due | |
| Updated | 06/23/2011 (5273 days ago) |
| Assigned | |
| Resolved | 06/23/2011 (5273 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
[gwr] Support restricting the HTML tidy post processing by the message
size (
Request #10266).5 files changed, 16 insertions(+), 4 deletions(-)
http://git.horde.org/horde-git/-/commit/dadbf4aa9afff91edd21119e0ea80d8eb3217bb3
(might) wish to set installation wide but seem to be unable to modify.
The original problem: I have an installation where the "tidy"
extension fails to postProcess() the HTML message text for large
messages probably due to memory limits. Now I assume the "size"
parameter is what I would like to use in order to avoid post
processing in such cases. Is that assumption correct?
*Horde* (not IMP). HTML cleaning is done within the _cleanHTML()
method in the framework HTML Mime_Driver, not the IMP driver.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Allow to size restrict the tidy extension
Type ⇒ Enhancement
State ⇒ New
(might) wish to set installation wide but seem to be unable to modify.
The original problem: I have an installation where the "tidy"
extension fails to postProcess() the HTML message text for large
messages probably due to memory limits. Now I assume the "size"
parameter is what I would like to use in order to avoid post
processing in such cases. Is that assumption correct?
What would be a reasonable way to make this configurable?
I admit that the basis for my current analysis is somewhat vague as I
have only limited debugging capabilities on this particular
installation.