Groups.io: Changelog

  1. Updates to the Groups.io service

Subscribe via RSS

October 30, 2026

Databases
  • CHANGE: In a database's map view, the map was a short strip above the table, and it jumped to a new spot every time the page scrolled. On larger screens the map now sits beside the table and stays in view while scrolling; on phones it stays at the top of the screen. Scrolling past or pointing at a row highlights its pin, and the map only moves when that pin is out of view.
  • CHANGE: Map view pins were small, dated icons, and pointing at one showed only the row's first column, which was often blank. Pins now use the site's colors, the highlighted pin is larger, and pins that are close together are grouped into numbered clusters that open up when clicked or zoomed. A pin's popup shows the row's name, address, a couple of its other columns and a View row link, and clicking a pin scrolls to its row and briefly highlights it.
  • CHANGE: The map in a database's map view stayed bright in dark mode. It now uses a dark map style.
  • CHANGE: For tables with more than 1,000 rows, the Map View button just reloaded the list. The list now says that map view is available for tables with up to 1,000 rows.
  • CHANGE: The first map view after importing many addresses could take a long time to appear, because every new address was looked up before the page loaded. Each view now looks up at most 25 new addresses and says how many rows are still being located; refreshing the page adds more of them to the map. An address whose lookup failed because of a temporary error is now tried again, instead of being listed as one that couldn't be placed.
  • CHANGE: Map view is easier to use with a keyboard. A Skip map link jumps from the buttons to the table. Pressing Enter on a pin opens its popup with the View row link ready to use, and Escape closes the popup and returns to the pin. Moving through the table's rows highlights their pins. The scrolling and row highlight animations are turned off for members whose device is set to reduce motion.
  • BUGFIX: In map view, a row whose address Google couldn't find was placed in the ocean off West Africa, which zoomed the whole map out to show it. Those rows are now left off the map and listed above the table, with links to each one. A table with a single address also zoomed in to rooftop level; it now stops at street level.
  • BUGFIX: Importing a CSV file without a header line put values in the wrong columns when the table had an address or link column, because each of those takes several columns in the file. Files laid out the way Export Table writes them now import correctly.

October 9, 2026

Databases
  • CHANGE: Deleting a column from a database table now asks you to confirm and says that its data will be removed from every row. Bulk actions on the Members page now name the action and the number of members (for example, "Remove 3 members?") and say when it can't be undone.

September 25, 2026

Databases
  • BUGFIX: Changing a database table's structure, such as adding, editing, or deleting a column, changed the Updated date of every row in the table to the date of the change. A row's Updated date now changes only when that row's values are edited. Rows whose dates were already changed can't be restored. https://beta.groups.io/g/main/message/41242

September 18, 2026

Databases

September 11, 2026

Databases
  • API BUGFIX: /adddatabaserow, /updatedatabaserow, and /deletedatabaserow returned misleading ID errors for JSON request bodies and reported malformed forms as server errors. They now explain which form encodings are supported and return bad_request errors for malformed forms. https://beta.groups.io/g/api/message/478
  • API CHANGE: The database row write endpoints used the same error for missing, malformed, and nonexistent IDs. Their error messages now distinguish those cases. https://beta.groups.io/g/api/message/478
  • API CHANGE: The database row write documentation incorrectly listed csrf as required when using API keys. It now explains that only cookie authentication requires it, documents form encoding and Google Apps Script's payload option, and clarifies that column field names use the IDs from getdatabases. https://beta.groups.io/g/api/message/478

September 4, 2026

Databases
  • API NEW: The API could read group databases but not change them: /getdatabases and /getdatabaserows were the only database endpoints, so scripted changes meant exporting a CSV and manually re-importing it. Three new endpoints complete the set: /adddatabaserow, /updatedatabaserow, and /deletedatabaserow. Updates are partial - columns omitted from the request keep their current values - and rows are addressed by the id returned by /getdatabaserows. Column values use the same per-column field names as the website's forms (text_<colid>, number_<colid>, date_<colid>, and so on), documented with the new endpoints. Image and GitHub columns cannot be set through the API; on updates their existing values are preserved. https://beta.groups.io/g/api/message/474
  • BUGFIX: Editing a database row with a required image column failed with "This field is required." unless the image was uploaded again, even though the existing image was shown in the form. The same happened when editing extra member data or a group profile with a required image field. The existing image now satisfies the requirement. Removing the image from a required column without uploading a replacement is now rejected, where before it was silently allowed. https://beta.groups.io/g/main/message/41135

1 - 18 of 18  
  • 1