Releases: bmlt-enabled/bmlt-server
Releases · bmlt-enabled/bmlt-server
4.1.0
- Settings Management UI:
- All server settings (except database credentials) are now fully configurable through the
Admin UI's Settings page. Settings are stored in the database and can also be managed via the Admin API (/api/v1/settings). - A migration was added to automatically seed settings from legacy
auto-config.inc.phpfile on upgrade.
- All server settings (except database credentials) are now fully configurable through the
- Other smaller features:
- Support creating custom queries with multiple cities/counties (intended for use with printable schedules)
- Add a private "Admin Notes" field on the "Other" tab
- Add a button to the Administration tab to download the laravel log file (useful for sending debugging information to the developers)
- Add a button to the Users tab to download a spreadsheet of users (including information on last login)
- Add a button to the Service Bodies tab to download a spreadsheet of service bodies
- Allow force delete of meetings when deleting a service body (requires confirmation before doing the force delete)
- Bug fixes:
- Fix location map errors when auto geocoding is disabled.
- Fix duplicate format keys in the initial migrations schema and in existing databases
- Fix scrolling problem when searching for meetings (we needed to reset it to the first page of results)
- Fix issue with root server stats, so that they now return the latest results
- Clear cache of meetings when logging in as a different service body (previously, meetings for the old service body would be visible, although you still couldn't edit them)
- Better handling for NAWS export if a service body has no World ID
4.1.0-beta5
- Settings Management UI:
- All server settings (except database credentials) are now fully configurable through the
Admin UI's Settings page. Settings are stored in the database and can also be managed via the Admin API (/api/v1/settings). - A migration was added to automatically seed settings from legacy
auto-config.inc.phpfile on upgrade.
- All server settings (except database credentials) are now fully configurable through the
- Fix location map errors when auto geocoding is disabled.
- Fix duplicate format keys in the initial migrations schema and in existing databases
4.1.0-beta4
- Settings Management UI:
- All server settings (except database credentials) are now fully configurable through the
Admin UI's Settings page. Settings are stored in the database and can also be managed via the Admin API (/api/v1/settings). - A migration was added to automatically seed settings from legacy
auto-config.inc.phpfile on upgrade.
- All server settings (except database credentials) are now fully configurable through the
- Fix location map errors when auto geocoding is disabled.
- Fix duplicate format keys in the initial migrations schema and in existing databases
4.1.0-beta3
- Settings Management UI:
- All server settings (except database credentials) are now fully configurable through the
Admin UI's Settings page. Settings are stored in the database and can also be managed via the Admin API (/api/v1/settings). - A migration was added to automatically seed settings from legacy
auto-config.inc.phpfile on upgrade.
- All server settings (except database credentials) are now fully configurable through the
- Fix location map errors when auto geocoding is disabled.
- Fix duplicate format keys in the initial migrations schema and in existing databases
4.1.0-beta2
- Settings Management UI:
- All server settings (except database credentials) are now fully configurable through the
Admin UI's Settings page. Settings are stored in the database and can also be managed via the Admin API (/api/v1/settings). - A migration was added to automatically seed settings from legacy
auto-config.inc.phpfile on upgrade.
- All server settings (except database credentials) are now fully configurable through the
- Fix location map errors when auto geocoding is disabled.
- Fix duplicate format keys in the initial migrations schema and in existing databases
4.1.0-beta1
- Settings Management UI:
- All server settings (except database credentials) are now fully configurable through the
Admin UI's Settings page. Settings are stored in the database and can also be managed via the Admin API (/api/v1/settings). - A migration was added to automatically seed settings from legacy
auto-config.inc.phpfile on upgrade.
- All server settings (except database credentials) are now fully configurable through the
- Fix location map errors when auto geocoding is disabled.
- Fix duplicate format keys in the initial migrations schema and in existing databases
4.0.4
- Modified the UI to hide the New Meeting button and show a helpful message when a user does not have editing privileges on any service bodies.
- Fixed an issue that prevented users from logging in to Yap servers that use this BMLT server.
4.0.3
- Fixed an issue that prevented the UI from loading on servers with a
RewriteOptions inheritconfiguration. - Fixed
$format_lang_namessetting to work with the new UI. - Fixed a geocoding issue -- if the county and/or zip code is automatically computed by the geocoder, we don't want to feed old and possibly incorrect values to the geocoder if the user edits an address.
- Fixed problems with format key validation.
- Added Portuguese translations.
- Strip legacy
#@-@#separator from custom field values in UI display.
4.0.3-beta1
- Fixed an issue that prevented the UI from loading on servers with a
RewriteOptions inheritconfiguration. - Fixed
$format_lang_namessetting to work with the new UI.
4.0.2
- Added Italian translations.
- Updated German translations.
- Fix favicon.
- Mask visibility=1 fields with asterisks in GetChanges json_data for unauthorized users.
- Fixed an issue where a service body couldn't be edited if one of its meeting editor users had been deleted.
- Fixed admin routes failing to load when accessed via direct URL or bookmark.
- Added database migrations to trim user fields whitespace and to remove nonexistent users from service body assignments.