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

Yellow "i" on ressource - don't know how to get it solved #1670

Open
saxas13 opened this issue Oct 27, 2023 · 1 comment
Open

Yellow "i" on ressource - don't know how to get it solved #1670

saxas13 opened this issue Oct 27, 2023 · 1 comment

Comments

@saxas13
Copy link

saxas13 commented Oct 27, 2023

Expected Behavior

... I didn't expect this to happen at all ...

Actual Behavior

The yellow Point usually calls to action (mostly to save changes). In the overview of the ressources on some ressourcse suddenly a yellow Point with "i" (the one in blue for information) appears but don't has a hint, what needs to be done? We tried opening and saving the ressources, used the sync button and so on, but the yellow "i" persists.

I couldn't find any information in the docs, so maybe someone can give me a hint whether its a bug or a feature ... and how to use it correctly.

Specifications

  • GeoNode version: 4.1.3
  • Installation type (vanilla, geonode-project): geonode-project
  • Installation method (manual, docker): docker
  • Platform: Ubuntu 20.04
  • Additional details:
@giohappy
Copy link

giohappy commented Feb 8, 2024

The yellow icon marks a dirty state for the resource. It could be for many reasons, like changing the viewport on the map, changing a share option, etc.
BTW I confirm that sometimes it happens that it shows even at startup, and this is caused by the internal mechanism that tracks the dirty state.

I will move this issue to the client repo.

@giohappy giohappy transferred this issue from GeoNode/geonode Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants