Skip to content
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 is by default broken, when set as not visible to anyone #5167

Closed
tallistroan opened this issue Oct 31, 2019 · 4 comments
Closed

Layer is by default broken, when set as not visible to anyone #5167

tallistroan opened this issue Oct 31, 2019 · 4 comments
Assignees
Labels
minor A low priority issue which might affect only some users and /or not the main functionality
Milestone

Comments

@tallistroan
Copy link

Expected Behavior

When a user uploads a layer and deselects the "Anyone" permission on upload, the layer is visible to the user which upload the layer.

Actual Behavior

When a user uploads a layer and deselects the "Anyone" permission on upload, the geometry and legend for this layer are broken and not visible to the user.

Steps to Reproduce the Problem

  1. Select shp file for upload
  2. Deselect the "Anyone" checkbox for the view and download permissions
  3. Don't enter a specific user to the permissions
  4. Upload the layer
  5. Go to the layer details page. The geometry and legend for the layer are broken and not visible to the user despite the user is now shown in the permissions overview for the layer

Possible workarounds

  • Go to "Change layer permissions" and click "Apply Changes" without changing anything
  • OR run the updatelayers command

By using any of the above method, the layer is afterwards visible to the user

Specifications

  • GeoNode version: 2.10.1, master
  • Installation method (manual, GeoNode Docker, SPCGeoNode Docker): Geonode Docker
  • Platform: Linux
  • Additional details: happens also on http://master.demo.geonode.org
@t-book t-book added the minor A low priority issue which might affect only some users and /or not the main functionality label Oct 31, 2019
@t-book
Copy link
Contributor

t-book commented Oct 31, 2019

hi @tallistroan this is a known bug. What should be done is to prefill the form with the current user:

Bildschirmfoto 2019-10-31 um 15 02 11

I darkly remember I've already created a PR but most likely I missed to merge.

@tallistroan
Copy link
Author

Thanks for the feedback @t-book . I was not able to find a issue for this bug (maybe I oversaw it), thus I created the ticket.

@stale
Copy link

stale bot commented Dec 30, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Stale Bot: Stale issue label Dec 30, 2019
@stale stale bot closed this as completed Jan 6, 2020
@t-book t-book reopened this Feb 1, 2020
@stale stale bot removed the wontfix Stale Bot: Stale issue label Feb 1, 2020
@t-book t-book self-assigned this Feb 1, 2020
@t-book t-book added this to the 2.10.2 milestone Feb 1, 2020
@afabiani afabiani modified the milestones: 2.10.2, 3.0 Feb 14, 2020
@t-book
Copy link
Contributor

t-book commented Mar 23, 2020

@tallistroan closing here with #5588
please reopen if you think this needs further care.

@t-book t-book closed this as completed Mar 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
minor A low priority issue which might affect only some users and /or not the main functionality
Projects
None yet
Development

No branches or pull requests

3 participants