Paginator broke with latest version Doctrine?

[TheDevilOnLine]

I just updated my symfony using Composer (which also updated my Doctrine etc). All of a sudden I now get the error 'Invalid parameter number: number of bound variables does not match number of tokens'.

I was able to fix this by making a change to /vendor/knplabs/knp-components/src/Knp/Component/Pager/Event/Subscriber/Paginate/Doctrine/ORM/QuerySubscriber.php

I changed line 27 from

$useDoctrineWalkers = version_compare(\Doctrine\ORM\Version::VERSION, '2.2.0', '>=');

to

$useDoctrineWalkers = false;

My doctrine uses version 2.3.x-dev

[pulse00]

I'm having the exact same issue. Something seems to have changed in doctrine, as there have been no real changes in this bundle since July 30.

[robmeek]

Having the same issue

[skydiablo]

I can confirm, have the same error

[Zorpen]

Yep, same here.

[raulfraile]

Same here. Is there a workaround to get it working without editing the component itself?

[TheDevilOnLine]

@raulfraile I'm still trying to figure that out. If I find a way, I'll post it in here as well!

[ChubV]

It is because of changes in the Doctrine pagination implementation
doctrine/orm@88d0933#lib/Doctrine/ORM/Tools/Pagination
doctrine/orm@8a29d91#lib/Doctrine/ORM/Tools/Pagination/Paginator.php

So Pager pagination doesn't work correct using old method of setting parameters
https://github.com/KnpLabs/knp-components/blob/8cfe4061c3ed1e4805e9291dab83e1aa14d42ada/src/Knp/Component/Pager/Event/Subscriber/Paginate/Doctrine/ORM/QuerySubscriber.php#L90-95

[joericochuyt]

confirm

[kiddo13]

composer.phar update with dev-master knp-paginator-bundle, querysubscriber still gives the same error.
Do I have to update it manually? *New to github

[TheDevilOnLine]

@kiddo13 for now you have to update it manually until the maintainers of the KnpPaginatorBundle accept the changes. For the correct change see the pull request @pulse00 made (mine is more of a quick fix)

P.s. Thanks @pulse00 for looking into this some more :-)

[pulse00]

the fix has been merged into knp-components. @TheDevilOnLine actually @ChubV found the regression - i've just created the PR ;)

[blimeycreative]

Is this issue fixed? I have the latest knp-components commit ('Cleanup before tagging version 1.1.2') which includes the @pulse00 PR but I'm still getting the 'Invalid parameter number' error. Is anyone else still having this issue?

[ThomasBerthe]

I'm still having the same issue when the default_options 'distinct' is set to true.
Here is my configuration and my code :

knp_paginator:
    page_range: 5                      # default page range used in pagination control
    default_options:
        page_name: page                # page query parameter name
        sort_field_name: sort          # sort field query parameter name
        sort_direction_name: direction # sort direction query parameter name
        distinct: true                 # ensure distinct results, useful when ORM queries are using GROUP BY statements
    template:
        pagination: KnpPaginatorBundle:Pagination:sliding.html.twig     # sliding pagination controls template
        sortable: KnpPaginatorBundle:Pagination:sortable_link.html.twig # sort link template

$em = $this->getDoctrine()->getEntityManager();
$dql = "SELECT a FROM ProjectxAccountBundle:Account a";
$query = $em->createQuery($dql);
$oPaginator = $this->get('knp_paginator');
$aAccounts = $oPaginator->paginate(
   $query,
   $this->get('request')->query->get('page', 1),
   2
);

[kaiwa]

+1 same issue is blocking me too

Edit: Setting distinct to false as mentioned by @ThomasBerthe is working

[blimeycreative]

Setting distinct to false worked for us too. The issue is still there, but this seems like a valid workaround for now.

[xtofthomas]

Thanks for the tips

[kevindew]

+1 getting the parameter problem as well (including trying the fix)

setting distinct to false has worked as a workaround

[jeremymarc]

any news about this issue ?

[ethanhann]

+1

[geoffreytran]

+1

[stloyd]

Did anyone tested latest changes? Many fixes were merged, so this should be fixed now.

[geoffreytran]

I just updated to the latest with doctrine 2.3.3 and this issue occurs.

Geoffrey Tran

On Feb 7, 2013, at 3:02 AM, Joseph Bielawski [email protected] wrote:

Did anyone tested latest changes? Many fixes were merged, so this should be fixed now.

�
Reply to this email directly or view it on GitHub.

[daFish]

I just updated to the latest hash this version and after that I got this issue.

[vrnagy]

+1

Setting distinct to false as mentioned by @ThomasBerthe is working

[alrayyes]

+1

Edit @ThomasBerthe workaround works for me too.

[MichaelHindley]

Confirming this issue as well with latest doctrine.

[bicpi]

+1

[iknowfoobar]

+1
@ThomasBerthe workaround works for me

[neoshadybeat]

+1

[jsamouh]

👍

[metalvarez]

setting distinc to false works but now when i set some filters to the query the pagination count breaks

[metalvarez]

i commented it out lines between 29 y 34 of /vendor/knplabs/knp-components/src/Knp/Component/Pager/Event/Subscriber/Paginate/Doctrine/ORM/QuerySubscriber.php and now works fine

/*if (version_compare(\Doctrine\ORM\Version::VERSION, '2.3.0', '>=')) {
$useDoctrineWalkers      = true;
$useDoctrineOutputWalker = true;
} else if (version_compare(\Doctrine\ORM\Version::VERSION, '2.2.0', '>=')) {
$useDoctrineWalkers      = true;
}*/

[iknowfoobar]

Switching back to any doctrine version before 2.3 fixes this for me.

[piotrkosytorz]

+1

[jjtorroglosa]

Same issue. Doing what @metalvarez proposes also works for me.

[entymon]

I had the same problem and resolved this like @metalvarez. It works.

[kallosz]

+1 same problem

[PanzerLlama]

+1

[bicpi]

@metalvarez Using distrinct=false, my pagination count is broken, too - but only when the list contains a single item

[Ziumin]

@bicpi try this PR, please KnpLabs/knp-components#48

[stloyd]

Fix was merged, new version tagged, in next few mins should be available at packagist.