Hi anakreon, thanks for your answer,
I guess i won't have any other temporary choices. Or i'll put a
partial. I wanted to prevent any actions that could, by human mistake,
uncheck the checkbox.
It was supposed to be a visual reminder to the user who has that flag
set, with the proper credentials.
Still the behavior of the "type: plain" in edit view, is a mistery to
me in regard of the object update action. Or should i say how the
boolean type is handled by the admin generator. I'll be glad to hear
from François or Fabien on how it is supposed to behave.
The 'updateObjectFromRequest' method handle both 'create' and 'edit'
action. And in the case of a create action, the boolean field is set
by default to the value set in the schema. That's fine. But in an
update action, if the type of the field is set to plain, no boolean
field update should occurs. That means that when the cache is created,
the admin generator should check if the boolean type is associated to
the rendering field type : plain. Something like :
Line 269 of the actions.class.php admin generator skeleton schema
(symfony 1.0):
<?php if($input_type!='plain'): ?>
$this-><?php echo $this->getSingularName() ?>->set<?php echo
$column->getPhpName() ?>(isset($<?php echo $this->getSingularName() ?
>['<?php echo $name ?>']) ? $<?php echo $this->getSingularName() ?>['<?
php echo $name ?>'] : 0);
<?php endif; ?>
Maybe it could be a ticket in the trac. Or maybe it is supposed to be
managed by the 20% code created by a symfony developper (my customized
class generator ?).
Regards,
Eric
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---
