-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
QGIS Server: Exclude composers in OWS tab does not work #17250
Comments
Author Name: Marco Hugentobler (@mhugent)
|
Author Name: René-Luc ReLuc (@rldhont) Will this bug be closed before QGIS 2 branching ? |
Author Name: René-Luc ReLuc (@rldhont) Hi Marco, I have threw a glance at the code and the list of excluded composers is stored in the element WMSComposerList. To fix this bug, we have several solutions :
Which has your preference ? |
Author Name: Marco Hugentobler (@mhugent) Hi René-Luc My preference is to change the element name and the behaviour (currently whitelist -> blacklist). I think it is more usefull to have a list of not-published compositions rather than explicitely publishing every composition. |
Author Name: René-Luc ReLuc (@rldhont) OK, can I propose a patch or directly update master ? |
Author Name: Andreas Neumann (@andreasneumann) Hi, Yes - the blacklist behaviour was already in place before this bug appeared. Also, I think the blacklist is what administrators want. Easier to maintain. Most of the composers would be public except some selected internal ones. Thanks for providing the patch. Andreas |
Author Name: Marco Hugentobler (@mhugent)
Could you make a pull request on github? |
Author Name: Marco Hugentobler (@mhugent) Works nicely, pushed to master branch. Thanks, René-Luc!
|
Author Name: Andreas Neumann (@andreasneumann)
Original Redmine Issue: 8484
Affected QGIS version: master
Redmine category:qgis_server
Assignee: Marco Hugentobler
In the current QGIS server, if one uses a list of "Exclude composers" in the OWS tab, QGIS server lists only the excluded composers and not the composers the map author actually wants. So it acts as a white list and not as a black list.
Thank you for having a look at the problem!
The text was updated successfully, but these errors were encountered: