[Qgis-developer] Problems editing WFS in QGIS
Scott Clark
sctevl at gmail.com
Tue May 6 09:44:43 PDT 2014
Hello Rene´,
Did this fix get in as a patch? If so, where can I get it for 2.2?
Thanks!
Scott
Scott Clark wrote:
> Excellent news and many thanks!
>
> René-Luc D'Hont wrote:
>>
>> Hi Scott,
>>
>> I have discovered this issue next week and I'm working on a bugfix.
>> I hope to propose a patch or a pull request tomorrow.
>>
>> I'd like to see this fix backported.
>>
>> Regards
>>
>> Le 24 mars 2014 14:58, "Scott Clark" <sctevl at gmail.com
>> <mailto:sctevl at gmail.com>> a écrit :
>>
>> Upon further investigation it appears that WFS authentication is
>> broken. Further testing shows that the Add WFS dialog does not
>> display layers that require basic auth - even when the login is
>> supplied. It will only show the public layers. Note that the
>> WMS auth works great for me.
>>
>> When you try to edit a WFS-T, I believe it is also failing to use
>> the supplied login info. Which results in the error I'm seeing
>> below.
>>
>> I've added the additional details to the existing bug at
>> http://hub.qgis.org/issues/9234
>>
>> Since this makes WFS of very limited use, is this planned to be
>> fixed in an up-coming release? I'll happily be a tester for this!
>>
>> Scott
>>
>> Scott Clark wrote:
>>> I've been having no success using the digitizing toolbar with
>>> WFS-T. I'm using QGIS 2.2.0 with a GeoServer 2.4. The layers
>>> are displaying fine when added through the Add WFS dialog, and
>>> the editing UI is functional. However, on save, it fails (after
>>> freezing up QGIS for a minute or so) with the following message:
>>>
>>> Could not commit changes to layer geonode:incidentes_copeco
>>>
>>> Errors: ERROR: 1 feature(s) not added.
>>>
>>> Provider errors:
>>>
>>> unhandled response: html
>>>
>>>
>>>
>>> It's not specific to these layers and it fails on all of the
>>> layers I pick. I've successfully tested editing using WFS-T on
>>> this particular server using both our OL3 and our mobile client.
>>>
>>> Any ideas on workarounds or what might be going wrong?
>>>
>>> Thanks,
>>>
>>> Scott
>>
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer at lists.osgeo.org
>> <mailto:Qgis-developer at lists.osgeo.org>
>> http://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140506/460eb72f/attachment.html>
More information about the Qgis-developer
mailing list