So with the previous template with no Geofence rule limiting attribute access, GetFeatureinfo request orders columns as they are listed in tabel or layer property. With Geofence rule, they have no particular order, and subsequent request can have even different order from previous requests.
-- View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329633.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
