#919: Assume "strict" validation mode directly inside AgaviValidationManager in
addition to code templates and remove "conditional" default for development
environments
------------------------+---------------------------------------------------
Reporter: david | Owner: david
Type: task | Status: new
Priority: normal | Milestone: 1.0
Component: validation | Version: 1.0.0beta5
Severity: normal | Keywords:
Has_patch: 0 |
------------------------+---------------------------------------------------
We already ship with
{{{
<validation_manager class="AgaviValidationManager">
<ae:parameter name="mode">strict</ae:parameter>
</validation_manager>
}}}
as the default in code templates for new projects.
However, we would like to take the opportunity to make this the default in
1.0 if no mode was given at all (right now, it defaults to the less secure
"relaxed" mode).
Also, as some people have stumbled over this before, we'd like to remove
{{{
<ae:configuration environment="development.*">
<validation_manager class="AgaviValidationManager">
<ae:parameter name="mode">conditional</ae:parameter>
</validation_manager>
</ae:configuration>
}}}
from the default code templates, as several users deployed their
applications to production environments and found that their actions
didn't work anymore because they didn't set up any validators (and didn't
test in a staging environment first).
--
Ticket URL: <http://trac.agavi.org/ticket/919>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
