New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with QGIS v3.0 #89
Comments
It seems there's a |
Fwiw, i've installed it locally using the |
Thanks! The plugin is still rather untested (I adapted some of the tester plugin tests, but not all are passing) I did quite a bit of manual testing, and it seems to be working fine, but due to the complexity of the plugin, still some stuff might not work as before. Once we test it correctly and it works fine, the qgis3 branch will be merged into master and a new version will be released Let us know if you find issues. Regards |
I've been able to browse a simple 2.12.1 sandbox install with very few layers/workspaces, but when i try to modify a setting/layer attribute/style i only get HTTP 400 code from geoserver, apparently because the PUT calls have a On my production instance running 2.8.1 loading the info from the REST api (at the first connect) goes into an infinite loop, ie it queries info all workspaces/layers/datastores/featuretype over and over again (i see the queries in the server log), never stopping. I dunno if it's a consequence of the qgis3 porting, will have to compare against a older version on qgis2, but iirc we saw the same thing (endless loop when collecting server info) when testing with a colleague of mine on qgis2, so it might be distinct bugs. |
Can you provide exact instructions of what you do get the 400 error? So that I try to replicate. |
in the catalog tree, select a a layer, click 'modify' next to the layer title, enter new value, validate, returns
having tcpdump -A running locally, i see this for the PUT call (note the zero Content-length ? and yes, there are several proxies in between, but geoserver-shell is able to put stuff on the REST API so it works):
and the server reply:
Is there a way to enable logging in the requests python module inside the plugin ? |
I cannot replicate this issue. Modifying any of a layer's values worked as expected without any warnings or errors. |
note that qgis3 branch is now called 'master' (readme.md is not updated) |
Does anyone know a status on making the plugin compatible with QGIS 3? Thanks. |
did you eread #89 (comment) ? |
Yes I did. Sorry, being a rookie this does not give me much overview. I’m curious to whether there is an update going on towards QGIS 3? But based on #89, qgis 3 being the ‘master’, I guess that’s the answer. Thanks. |
The link to that branch is broken, FYI. |
So: given that last commit is >2 years ago, i have to ask: is there any movement toward making this plugin compatible w/ QGIS v.3.x? Or is does this plugin and its repo serve only for users of v.2.x? In either case, perhaps readme.md should reflect the fact? |
try with the plugin evolution by Geocat https://plugins.qgis.org/plugins/geocatbridge/ |
Do you plan to update the plug-in for QGIS version 3.0?
The text was updated successfully, but these errors were encountered: