-
Notifications
You must be signed in to change notification settings - Fork 16
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
Layer loading through WFS fails #281
Comments
I suspect this is still related to the multiple replies without clear predictability. Sometimes they seem related to the time it takes for a request to complete, sometimes related to the clearing of the cache, but it looks confirmed that it doesn't depend on the plugin. In the case of WFS loading, the style request is performed within the same tasks as the WFS request itself. This might break the logic that pairs the request to the first reply. Maybe here we're handling the first reply for the WFS request but not the one for the style. Let's investigate and handle this case too. |
@giohappy finally, I fixed the error: |
cool @Gpetrak. do you already have a PR? |
@giohappy I have pushed the fixes in the branch: ISSUE_281. I didn't create yet the PR since I want to solve also the second error that is reported in this issue: the one with QGIS crash after loading a layer with an SLD which includes non-english characters (e.g greek characters). Obviously is an encoding issue. The crash happens in this line: |
@giohappy for the sake of clearness, I think that it is better to open a new ssue for the QGIS crash because it is a completely different error. Thus, I can create the PR for the main issue that we investigated. |
ok @Gpetrak please proceed. |
When a user tries to load a layer through the WFS, sometimes the plugin raises the following error:
Sometimes before crashing QGIS exports the following error:
which comes from the
handle_layer_detail
function of the file: seach_result_widget.py, line 250.It’s worth noting that both WFS versions (1.1.0, 2.0.0) were used. Also the WCS seems to work without a crash (tested with the live demo of GeoNode).
The text was updated successfully, but these errors were encountered: