SQL views are not saved if the layer is not saved too
Description
The Save button at the bottom of the Edit SQL view page when modifying a SQL View in GeoServer is expected to be enough to write and flush the configuration changes, at least from a user standpoint. However this is not true, the layer must also be saved using the save button at the bottom of the main Edit Layer page, otherwise, the changes to the SQL View are not applied.
Plan of action:
we need to make it more clear for the end-user that we need to save twice before having the behavior applied because with the current behavior most people will not do the second step.
Environment
None
Activity
Show:
Shadab Gada September 22, 2021 at 7:20 AM
Backport 2.19.x PR:
Shadab Gada September 16, 2021 at 4:59 AM
PR:
Shadab Gada September 15, 2021 at 1:55 PM
I have added the description,
Nuno Oliveira September 15, 2021 at 1:47 PM
indeed bugs should provide information about how to reproduce them, and at very least describe the problem, could you add those missing bits? Thx for the heads up, I’m working with on this one.
The Save button at the bottom of the Edit SQL view page when modifying a SQL View in GeoServer is expected to be enough to write and flush the configuration changes, at least from a user standpoint.
However this is not true, the layer must also be saved using the save button at the bottom of the main Edit Layer page, otherwise, the changes to the SQL View are not applied.
Plan of action:
we need to make it more clear for the end-user that we need to save twice before having the behavior applied because with the current behavior most people will not do the second step.