? Success

User tests: Successful: Unsuccessful:

avatar Bakual
Bakual
22 Jul 2014

This should fix the issue raised with #3940

Currently, $query->setLimit() is overriden by $db->query(). Making the method kind of useless.

This PR will make it so that setQuery checks if there is a limit or offset property set in the $query and uses that one if it's set and setQuery doesn't have an own value set already.

To test you can use the Ajax example plugin like described in the original Issue:

avatar Bakual Bakual - open - 22 Jul 2014
avatar betweenbrain
betweenbrain - comment - 22 Jul 2014

Works like charm. Thanks @Bakual!

avatar malukenho
malukenho - comment - 22 Jul 2014

@Bakual no need tests?

avatar Bakual
Bakual - comment - 22 Jul 2014

no need tests?

You mean unit tests or usage tests?

avatar malukenho
malukenho - comment - 22 Jul 2014

@Bakual unit teste, sorry.

avatar Bakual
Bakual - comment - 22 Jul 2014

@malukenho You want to write some? I don't think there is currently one dealing with that. So it would be very welcome.

avatar malukenho
malukenho - comment - 22 Jul 2014

@Bakual yeep, I want do it :D

avatar wilsonge
wilsonge - comment - 23 Jul 2014

Scrap that did it myself #3948

avatar dbhurley
dbhurley - comment - 23 Jul 2014

Nicely done.

avatar betweenbrain
betweenbrain - comment - 23 Jul 2014
avatar gwsdesk
gwsdesk - comment - 25 Jul 2014

@test
Plugin needs to be published. Ran after that the url and works like a charm
Set to RTC on Joomlacode

avatar wilsonge
wilsonge - comment - 25 Jul 2014

Yay :) Can people please pull #3948 instead of this as that has some unit tests to make sure this bug doesn't come back (exactly the same fix though)

avatar betweenbrain
betweenbrain - comment - 25 Jul 2014

@wilsonge what about changing the scope of #3948 to be just unit tests so that we don't have competing PRs?

avatar wilsonge
wilsonge - comment - 25 Jul 2014

Yeah I can. Whatever works. I just added the fix to show that the bug is fixed after the patch is applied

avatar gwsdesk
gwsdesk - comment - 25 Jul 2014

I am sorry I am lost. What is now the patch to be tested? (me probably
missing out but sure just give me a hand ;-) ) Gimme the correct link
please?

On 7/25/2014 8:46 PM, George Wilson wrote:

Yeah I can. Whatever works. I just added the fix to show that the bug
is fixed after the patch is applied


Reply to this email directly or view it on GitHub
#3945 (comment).

Leo Lammerink
MD GWS - Enterprise Ltd
Skype: gwsgroup
www.gws-desk.com http://www.gws-desk.com | www.gws-host.com
http://www.gws-host.com | www.gws-deals.today http://gws-deals.today

avatar Bakual
Bakual - comment - 25 Jul 2014

It's fine as is. I can merge this PR and take the unittest commit from Georges PR.

avatar wilsonge
wilsonge - comment - 25 Jul 2014

The patch is the same. One just comes with unit tests to prevent the bug reoccurring.

avatar Bakual Bakual - change - 26 Jul 2014
Status New Closed
Closed_Date 0000-00-00 00:00:00 2014-07-26 14:57:29
avatar Bakual Bakual - close - 26 Jul 2014
avatar Bakual Bakual - close - 26 Jul 2014
avatar Bakual Bakual - head_ref_deleted - 26 Jul 2014
avatar Sophist-UK Sophist-UK - reference | 91cbcb8 - 7 Oct 14

Add a Comment

Login with GitHub to post a comment