You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: