Open multimartin opened 4 months ago
Having same settings at two different places will confuse everybody and makes no sense IMHO.
As a user of sitemaps from headless systems also, where I call and render html-pages with a shell command - I have no possibility to set and store the settings for such a client.
This is a very unusual way to use UI I guess. For my curiosity, what is your usage exactly ? One option could be to add new optional query parameters to the Basic UI URL (one for each setting) that will overwrite the browse settings.
In OH 4.2.x for BasicUI most settings for the sitemaps appearance has been moved to the settings "wheel" on the sitemap page - and stored in the browser. As a user of sitemaps from headless systems also, where I call and render html-pages with a shell command - I have no possibility to set and store the settings for such a client.
Would it be possible to keep the option of setting all general settings for BasicUI sitemaps in the main web UI - whilst still keeping the option to override those default settings in the individual browser?
So basically add more default options in the main UI - similar to how it could be set pre-4.2.x? Right now you can only enable/disable inline SVG and set the name of the default sitemap.