The current Leaflet implementation expects coordinates in latitude-longitude order but GeoJSON and PostGIS works the other way around with lng first. These changes work around this behavior by passing the data to and from db through PostGIS’s `ST_FlipCoordinates` function if the setting `MAPBOX_FIX_POINT_COORDINATES` is something truthy. This is to not break the current behavior. Right now a warning is emitted when this setting hasn’t been enabled but I would recommend to remove this setting and make its behavior the default in the next major version.

Fix missing code in docstrings

fixes #1131 - broken action redirect in FileAdmin

Allow to use empty url for AdminIndexView

Tablib export

Little fix of mongoengine usage example

Remove needless line from the docs

It apparently was copy&pasted by mistake from previous example.

Adding block after filter in list view

More Flexible Exports Without Exceptions

simplify 'skip_checks' for #1194

Don't raise exceptions during export on column_formatters with macros when there is a valid column_formatters_export, column_export_exclude_list or column_export_list configuration available

add unit test for a related table's column object

SQLA - allow using column objects in column_list

SQLA - Allow using column objects in form_columns

fixes #1185

fixes #1185 according to coleifer/peewee@50c9c1d with retro compatibility for peewee's model meta fields hack

Fallback to default location if it was not received from external service