Re: [Qgis-developer] broken WFS client commit

2015-10-27 Thread Raymond Nijssen
Yes, could someone please revert or solve this? I've been meeting this issue since last summer (http://hub.qgis.org/issues/13117) and it prevents some of my customers to upgrade from 2.8, missing all kinds of nice new features. Regards, Raymond On 25-10-15 22:19, Jeremy Palmer wrote:

Re: [Qgis-developer] broken WFS client commit

2015-10-27 Thread Andreas Neumann
The WFS client should really get some love by a developer (and our funds). Currently, it is broken and does not support the newer WFS version. Hopefully, we can fund something from our donations/sponsorships. Andreas On 27.10.2015 09:24, Raymond Nijssen wrote: Yes, could someone please revert

Re: [Qgis-developer] broken WFS client commit

2015-10-27 Thread Raymond Nijssen
Hi Andreas, That would be great, but for now I'd like to have the change that broke this reverted. Raymond On 27-10-15 10:50, Andreas Neumann wrote: The WFS client should really get some love by a developer (and our funds). Currently, it is broken and does not support the newer WFS version.

Re: [Qgis-developer] broken WFS client commit

2015-10-25 Thread Jeremy Palmer
> Should we maybe 'rename' the 'caching' option to be an option which > makes QGIS resend a feature request every zoom/pan? I agree we should revert to the old behaviour and rename the label. This change has now broken a major use case for users of large WFS datasets. Cheers Jeremy This

[Qgis-developer] broken WFS client commit

2015-10-25 Thread Richard Duivenvoorde
Hi devs, Looking at this commit: https://github.com/qgis/QGIS/commit/e4e4839823fad1b980cb815889c18edb9c4352b7 it looks like there there was a checkbox introduced which forces the WFS provider to add a bbox to the requests. but this was already working via the 'cached' option. Currently for