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

Unpublish then republish graph resets all resource map layer config #11633

Open
CWDamm-Kint opened this issue Nov 18, 2024 · 2 comments
Open

Comments

@CWDamm-Kint
Copy link
Contributor

CWDamm-Kint commented Nov 18, 2024

Tested in Arches 7.5 (Arches for HERs). Republishing the graph resets the styling for resource layers (set within the Map Layer Manager) to the defaults.

@chiatt chiatt added this to pipeline Nov 18, 2024
@CWDamm-Kint CWDamm-Kint changed the title Refreshing geojson_geometries resets the styling for resource layers Unpublish then republish graph resets all resource map layer config Nov 18, 2024
@SDScandrettKint
Copy link
Member

SDScandrettKint commented Nov 18, 2024

Example video showing the issue (on AfHER):

map_config_reset_on_publish.mp4

@SDScandrettKint
Copy link
Member

SDScandrettKint commented Nov 28, 2024

Some further notes after digging into this issue:

  • This issue occurs in v7.6 as well as 7.5. It has not been tested in 8.0. Interestingly, it is also an issue back in 6.2.x - if you apply map stylings and then rename a node, the map stylings are reset.
  • The styling reset occurs at unpublish (as this calls save).
  • I see the following psql log statement when unpublishing, which looks to insert new stylings.
2024-11-27 17:17:45.963 GMT [188089] postgres@arches_dev_v7 LOG:  statement: UPDATE "nodes" SET "name" = E'Geometry Node', "description" = NULL, "istopnode" = false, "ontologyclass" = NULL, "datatype" = E'geojson-feature-collection', "nodegroupid" = '60c3af4e-ace0-11ef-a3ca-00155de62b6e'::uuid, "graphid" = 'd2363655-e7a6-4459-8eb3-f289c87dbdde'::uuid, "config" = E'{"radius": 2, "weight": 2, "addToMap": false, "fillColor": "rgba(130, 130, 130, 0.5)", "layerIcon": "", "layerName": "", "lineColor": "rgba(130, 130, 130, 0.7)", "haloRadius": 4, "haloWeight": 4, "pointColor": "rgba(130, 130, 130, 0.7)", "layerLegend": "", "outlineColor": "rgba(200, 200, 200, 0.7)", "advancedStyle": "", "lineHaloColor": "rgba(200, 200, 200, 0.5)", "outlineWeight": 2, "clusterMaxZoom": 5, "layerActivated": true, "pointHaloColor": "rgba(200, 200, 200, 0.5)", "simplification": 0.3, "advancedStyling": false, "clusterDistance": 20, "clusterMinPoints": 3}', "issearchable" = true, "isrequired" = false, "sortorder" = 0, "fieldname" = NULL, "exportable" = false, "alias" = E'new_node', "hascustomalias" = false, "sourcebranchpublicationid" = NULL WHERE "nodes"."nodeid" = '60c3af4e-ace0-11ef-a3ca-00155de62b6e'::uuid
  • The reason this error happens seems to be because the node.config doesn't seem to be updated in self.nodes in graph.py, so it is saving an old version (the original) of config. This seems to be, because when the map stylings are changed in Map Layer Manager, it isn't updating the stored config in graph.py.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants