#1307: Make AgaviFormPopulationFilter parsing more lenient
--------------------+-------------------------------------------------------
Reporter: david | Owner: david
Type: task | Status: new
Priority: normal | Milestone: 1.0.4
Component: filter | Version: 1.0.3
Severity: normal | Keywords:
Has_patch: 0 |
--------------------+-------------------------------------------------------
In XML parsing mode, well-formedness errors are fatal, but in HTML parsing
mode, they are not. Similarly, common errors like the one about
{{{ }}} not being defined in XML parsing mode are also not fatal.
These are errors that FPF could recover from.
Of particular note, #1292 describes the problem where libxml does some
internal lookup against a list of known HTML modes in HTML parsing mode,
and complains about tags like {{{<section>}}}. This specific error number
801 could easily be ignored, just like any warning and potentially also
any error. Maybe make it configurable, or dependent on debug mode? Needs a
bit more thought, but certainly worth a shot.
Logging would then have to be more fine-grained as well. Also, a separate
{{{force_parsing_mode}}} parameter in addition to the current
{{{force_output_mode}}} would probably make sense.
See the related #1292
--
Ticket URL: <http://trac.agavi.org/ticket/1307>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
