Without this logic, new forms with an sfWidgetFormDate field would never be considered empty.
…alling of admin generator /create action
…lugin Conflicts: README lib/form/ahBaseFormDoctrine.class.php lib/form/ahNewRelationField.php lib/form/ahNewRelationsContainerForm.php package.xml.tmpl
…values and their respective validators; so the admin generator doesn't crash anymore when the 'new_relationName' widget is in the 'display' array
…0 and 5.3.0 because is_a() is deprecated in these versions - it's not beginning with 5.3.0 - d'oh! :) - bugfix: creating a completely new main object and, at the same time, also adding new related objects did not work
…s (just about a 1:1 conversion of the jQuery one)
- bugfix: fixed a bug regarding Doctrine inheritance (thanks Yves!) - bugfix: to disable the checkbox to delete existing related records set the option formClassArgs to this: 'formClassArgs' => array(array('ah_add_delete_checkbox' => false)) - added new developer: FabryB :) - bugfix: newFormClassArgs option didn't work the way it was described in the README (option was automatically wrapped in an array) => please read the UPGRADE GUIDE that is packaged with this plugin! :) - bugfix: when using the multipleNewForms and newFormsInitialCount options it was indeed creating multiple forms to add related objects but it also did that for ONE-to-ONE relations ;-) - bugfix: newRelationButtonLabel did not work at all :( - new feature: customEmbeddedFormLabelMethod option is a method that is called on each existing related object (not the containing form!) so you can customize the form label that is shown in front of each existing embedded form. This option is new since version 1.4.0. - bugfix: The plugin finally works with embedded forms that have checkboxes, radio buttons and/or file upload fields (what's especially interesting is the use of sfWidgetFormInputFileEditable)! I also finally added unit tests that should cover at least 80% of the functionality. Because I don't have that much time I used the symfony Core's unit tests as a starting point so they actually live inside the lib/vendor/symfony directory of one of my projects. If there's someone who knows how to set up plugin-internal unit tests (with a SQlite database for testing persistence stuff), I'd be glad to provide these unit tests. :) Help's always welcome!
…t the option formClassArgs to this: 'formClassArgs' => array(array('ah_add_delete_checkbox' => false))
- fixed a bug regarding Doctrine inheritance (thanks Yves!)