associated styles not visible in Map Layer Settings -> Style Settings

[saxas13]

Expected Behavior

If a layer has associated styles (additional to it's default style), they are selectable from the layer settings -> Style settings in the drop down menu and can be selected and applied to the layer in a map.

Actual Behavior

The associated styles do not show anywhere and cannot be applied to the respective layer.

Steps to Reproduce the Problem

1. Upload a layer
2. Go to Geoserver and create a new style
3. Add the style as associated style to the newly uploaded layer
4. Add new layer to map, open layer settings, open style settings --> only the default style is in the dropdown list

Specifications

• GeoNode version: 4.1.3
• Installation type (vanilla, geonode-project): geonode-project
• Installation method (manual, docker): docker
• Platform: Ubuntu 20.04
• Additional details: In Version 3 there was a button to refresh the statistics, which got the new styles for the layer and it was possible to use the style in the preview page of the layer (and download the styles) as well as in the maps by changing from default to alternative --> Currently a dataset with different styles needs to get published again to have a different symbolization (i.e. Administrative Regions without label and with label)

[jeff-bradley]

I am also seeing this behavior, the only style adding to as associated styled to get working was the generic style, which i thought wouldnt work because its not under the geonode workspace. The only way i was able to get it to working correct was to manually add a row into the layer_dataset_styles table with the right dataset_id and style_id

[TadeoBennett]

I am also seeing this behavior, the only style adding to as associated styled to get working was the generic style, which i thought wouldnt work because its not under the geonode workspace. The only way i was able to get it to working correct was to manually add a row into the layer_dataset_styles table with the right dataset_id and style_id

Have you managed to address this problem?

[giohappy]

This is part of the change that is planned, but not in the roadmap yet https://github.com/GeoNode/geonode/issues/13227.