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

Cannot recover maps layers order and visibility after migration #10039

Open
geogeek11 opened this issue Sep 19, 2022 · 0 comments
Open

Cannot recover maps layers order and visibility after migration #10039

geogeek11 opened this issue Sep 19, 2022 · 0 comments

Comments

@geogeek11
Copy link

I have migrated a Geonode instance to 4.0, but I'm still puzzled about where the map layer's order and visibility are stored, even if I update the base_resourcebase.blob field with the order and visibility of the correct layers (Using SQL), the changes do not reflect and it keeps using an initial version where all the layers are visible with a yellow dot that the map is not saved.

I have used SQL for the migration processing.

To reproduce the issue, First I have save the map to have the correct object structure, then I alter visibility and order then I update the blob object in base_resourcebase.blob (Using SQL) but the update won't be reflected.

Geonode 4.0
Geonode Docker

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

1 participant