Jon,
I sumbmitted a patch to the ticket, which passed all tests included
with sfDoctrinePlugin.
see it here : http://trac.symfony-project.org/ticket/5586
Julien
On Jan 13, 2:53 pm, Jonathan Wage wrote:
> You can run the tests included with the sfDoctrinePlugin in the test folder.
>
> - Jon
>
You can run the tests included with the sfDoctrinePlugin in the test folder.
- Jon
On Tue, Jan 13, 2009 at 1:45 PM, jukea wrote:
>
> Also , if I patch the admin code templates, is there any test I should
> code, before submitting a patch ? I found none for the generated
> admins
>
> Julien
>
>
Also , if I patch the admin code templates, is there any test I should
code, before submitting a patch ? I found none for the generated
admins
Julien
On Jan 13, 2:29 pm, jukea wrote:
> Jon,
>
> I think the filter forms should get passed the table_method with a
> setTableMethod, if any, in the s
Jon,
I think the filter forms should get passed the table_method with a
setTableMethod, if any, in the same way the pager does.
eg :
$filterForm->setTableMethod()
if there's no filter, then we'd still need to do it before the sorting
criteria is added:
$query=Doctrine::getTable('getModelC
Could we just change it so table_method is done first?
- Jon
On Tue, Jan 13, 2009 at 12:48 PM, jukea wrote:
>
> Just to add more information on that matter :
>
> For the sorting feature to work, what I did was move the use of the
> table_method just before the sorting part is added (directly in
Just to add more information on that matter :
For the sorting feature to work, what I did was move the use of the
table_method just before the sorting part is added (directly in the
actions code template)
protected function addSortQuery($query)
{
if (array(null, null) == ($sort = $this->
