Hello No, I don't use jdbcconfig module. I doublechecked, the layers that belong to that layergroup are both enabled and advertised and store is enabled. It doesn't show any layergroups in the wms 1.1.1 getcapabilities document when I am not logged in to the GUI (layergroups themselves are visible and accessible on the layer preview page). But older installation (live environment with 2.10.0) does show them. I cloned the data directory for the GS2.15.2 from the old installation.
Maario ________________________________ Saatja: Jan Boonen <[email protected]> Saadetud: teisipäev, 17. september 2019 20:36 Adressaat: [email protected] <[email protected]> Teema: Re: [Geoserver-users] GS 2.15.2 layer group not visible in GetCapabilities Hi Mario, Are you using the JDBCConfig module? I had a similar problem while upgrading from 2.8 to 2.12 and found a solution, see: http://osgeo-org.1560.x6.nabble.com/Layers-missing-in-WMS-Capabilities-after-upgrade-td5356567.html. I'm not sure if the same problem can occur when you are using the file-based configuration, but it's worth to check the resource.advertised, resource.store.enabled and resource.enabled properties of your feature and layer configurations. Kind regards, Jan -------------------------------------- Geodan Buitenhaven 27-A 5211 TP 's-Hertogenbosch (NL) T +31 (0)73 - 692 5151 M +31 (0)6 - 2395 1191 E [email protected]<mailto:[email protected]> www.geodan.nl<https://www.geodan.nl> | disclaimer<https://www.geodan.nl/disclaimer/> -------------------------------------- Op di 17 sep. 2019 om 13:06 schreef Maario Tumanski <[email protected]<mailto:[email protected]>>: Hello I have a GS 2.15.2 installation (Centos 7, openjdk 11). I upgraded it on top of the GS 2.10.0 data directory. I noticed that when making anonymous wms 1.1.1 GetCapabilities request, then the layer groups are not visible anymore. When I log into GUI and repeat the request, then everything works as I expect. Other layers in same workspace are visible in result. On the 2.10.0 installation with the same request, it works. Is this expected behaviour? Thanks and all the best Maario _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/geoserver-users
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
