2.16.3

• Fix bug in code that lets NAWS indicate they have processed a deleted meeting, so that you don't need to be logged in as the serveradmin for it to work
• Fix permissions bug in NAWS import code so that it works if you are logged in as the admin of a parent service body
• Removed use of each function and reserved keyword match for PHP 8 compatibility.

2.16.2

• Added checks to meeting editor:
  • Warning for an in-person meeting if there is information in a virtual meeting field.
  • Warning for a virtual meeting (pure virtual, not hybrid or VM/TC) if there is a location or an address.
• Change default name for TC format from "Temporarily Closed" to "Temporarily Closed Facility"
• Add ability for NAWS to indicate that they have processed a deleted meeting, so that it stops showing up in future NAWS exports. To do this, the spreadsheet with updated World IDs should have a World ID of 'deleted' for deleted meetings they don't need to see again.

2.16.1

• Require a key for HY, TC, and VM formats for every language, including additional format languages; make sure they have the correct world ID and type; make sure they can't be inadvertently mapped other formats.
• Support teamspeak URLs for Virtual Meeting Link.
• Fix a bug with GetSearchResults, which was ignoring the lang_enum parameter. (This was a problem for multi-language servers in which there were formats that used different keys in different languages.)
• Rename the 'Edit Meetings' button in the meeting editor tab to 'Edit Or Create Meetings'.
• Make terminology for World Committee Code for groups and meetings more consistent in the UI; add advice in the meeting editor that normally admins should leave this field alone.
• update URL for API key error documentation

2.16.0

• Field descriptions are now displayed beneath each field to in order to support data validation changes.
• In the meeting editor, HY, TC, VM are now hidden from the formats tab, and instead are controlled using the Location tab Venue Type radio buttons. (They are still visible in the Format Editor however.)
• Added location information checks, as follows:
  • Error if no venue type selected.
  • Error if there is a virtual or hybrid meeting, and none of Virtual Meeting Link, Phone Meeting Dial-in Number, or Virtual Meeting Additional Information is filled in.
  • Error if Virtual Meeting Link contains an invalid URL.
  • Warning if no location information filled in for meeting (minimally, there should be a city/town and state/province, or a zip/postal code).
  • Warning if no street information for an in-person or hybrid meeting.
  • Warning if there is a virtual/hybrid meeting, and no Virtual Meeting Link or Phone Meeting Dial-in Number (just a warning for now though, since Virtual Meeting Additional Information might have enough information to join the meeting).
  • Warning if there is a Virtual Meeting Link but nothing in the Virtual Meeting Additional Information field.
• Added initial support for time zones, hidden behind feature flag.
• Added a "publish" checkbox to the NAWS import functionality to allow new meetings to be either published or unpublished.
• Fixed an issue where map searches using geo_width could return incomplete results when filtered by service body.
• Fixed an issue with which meeting formats are selected for a NAWS export, to make sure the essential ones are included. The default is likely fine as is, but can be overridden with an optional variable $naws_export_formats_at_front in auto-config.inc.php.
• Allow World IDs to be free form text, to better support current NAWS practice.
• Updates to initial versions of formats used for new root servers, including changing "surveillance cameras" to "security cameras" and correcting format type etc for formats that describe different languages

2.16.0-beta2

2.16.0-beta2

2.16.0-beta

2.16.0-beta

2.15.6

• Added support for the OLM NAWS Format code for online meetings.
• Added the train and bus fields to browser view.
• Minor improvements to install wizard. Fix bug regarding names and passwords with single quotes or backslashes (before they would cause a cryptic error; now they are OK -- not that using them is a great idea, but the system shouldn't die strangely). Also, if there is a database access error, and one of the offending fields has whitespace at the beginning or end, give a hint to the user that might be the cause.

2.15.5

• Many service bodies are already using an "HY" format for hybrid virtual and in-person meetings, so we made it official - if you don't already have the "HY" format, this release will create it for you.
• The formats most commonly used for virtual meetings (VM, HY, TC) have received NAWS format codes. This release automatically maps VM, HY, and TC to the appropriate NAWS format code.

2.15.4

2.15.4

2.15.3

2.15.3