Re: [Geoserver-devel] Default value for Layer abstracts

2022-01-31 Thread Jody Garnett
Yep, a patch would be welcome (I noticed this yesterday when testing i18n). Also it is really obvious if you read the docs, but of course I did not read carefully enough. Turns out in a bit of classic WMS goodness AcceptLanguages is a KVP property; and not determined by http header. Jody On Mon,

Re: [Geoserver-devel] Default value for Layer abstracts

2022-01-31 Thread Gabriel Roldan
Indeed, looks like misbehavior in both cases IMHO though. Can't speak for the PSC, but my community vote goes for getting rid of that hardcoding. Cheers, On Mon, 31 Jan 2022 at 20:04, Justin Deoliveira wrote: > Thanks Gabriel, nice to hear from you too! > > You're right in that for layer group

Re: [Geoserver-devel] Default value for Layer abstracts

2022-01-31 Thread Justin Deoliveira
Thanks Gabriel, nice to hear from you too! You're right in that for layer groups this has always been the behavior. What I think happened in the recent i18n refactor was that some code was refactored to share the encoding of the title and abstract for LayerInfo and LayerGroupInfo, and in doing so

[Geoserver-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

2022-01-31 Thread Torben Barsballe
Reminder that the next PMC meeting is scheduled for tomorrow, February 1, at 18:30 CET. Cheers, Torben ___

Re: [Geoserver-devel] Default value for Layer abstracts

2022-01-31 Thread Gabriel Roldan
Hey man, nice to hear from you. That seems strange actually, but couldn't track down when it was added, it's already there at the first git commit (44bacafcf1) in June 2011, so it's from the svn days. Wait, yeah, been like that since 2007 at least: https://github.com/geoserver/geoserver-history/c

[Geoserver-devel] Default value for Layer abstracts

2022-01-31 Thread Justin Deoliveira
Howdy folks, First off amazing job on the project, great to see GeoServer thriving and be such a robust and stable tool, kudos to all of the core developers for their hard work. I have a question about a change that I am seeing after upgrading a Geoserver instance from a 2.18.x to the latest stab

[Geoserver-devel] [JIRA] (GEOS-10376) Uncaught Exception at bounds calculation with WFS-T Delete on a datastore containing invalid geometries

2022-01-31 Thread Valerij Dobler (JIRA)
Valerij Dobler ( https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5e7f83cf0c8c030c39b197db ) *created* an issue GeoServer ( https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNDUxODIwY2FjM2UxNDg5YjliOWE4ZjdmNDQwMmM3OTQiLCJwIjoiaiJ9 ) / Bug ( https://osgeo-org.atlas