Groups.io: Changelog

Subscribe via RSS


October 30, 2026

Members
  • CHANGE: The Bouncing badge was the same light blue as the Mod, Owner and other informational badges, so bouncing members were easy to miss. It's now orange, which sets it apart from the other badges and from the red Bounced badge. https://beta.groups.io/g/main/message/41490
  • BUGFIX: Clicking a color in the Members page Filter also changed the color chosen in the Set Color and new label windows. Each color picker now only changes its own selection.
  • BUGFIX: The Location label and View map link on a member's profile were never translated. They now appear in the member's language once translations are updated.
Moderation
  • NEW: Setting or clearing a topic's status is recorded in the group's Activity log, noting whether it locked or reopened the topic and whether it came from an email link.
Subgroups
  • BUGFIX: In German and Dutch, the note about exporting a subgroup before deleting it put the export link on the wrong words, twice. It now links just the word for export.
Calendar
  • CHANGE: The map on an event's page stayed bright in dark mode and, when the location matched more than one place, could leave some of them off the edge. It now uses a dark map style in dark mode and fits every matching place in view.
  • BUGFIX: The View In Google Maps link on an event's page searched for garbled text when the location contained an apostrophe or an ampersand, such as Fisherman's Wharf & Pier 39. It now searches for the location as written. The link in event emails also used an insecure http address; it now uses https. All View In Google Maps links, including those on database rows and member profiles, now use Google's current map links.
Wiki
  • NEW: The wiki editor has an Insert block menu for adding Note, Tip and Warning callouts, FAQ entries (a question that expands to its answer), buttons, two-column sections, tables and dividers. Each block is inserted with placeholder text to type over, and looks in the editor as it will on the page.
  • NEW: Wiki pages written in Markdown can use GitHub-style callouts: a quote starting with [!NOTE], [!TIP] or [!WARNING] is shown as a Note, Tip or Warning box.
  • NEW: Creating a new wiki page offers templates to start from: Blank, FAQ (an introduction and questions that expand to their answers), Guide (a table of contents, steps and a tip) and Canned answer (a short answer written to be inserted into replies). A template is only starting content; the page can be edited like any other.
  • CHANGE: Wiki pages had almost no styling of their own: headings, tables, code and quotes looked like plain text, and lines ran the full width of the window. Pages now have comfortable line lengths and spacing, a clear heading scale, bordered and striped tables, styled code blocks and quotes, and images that never overflow the page, in light and dark mode. Formatting authors set on their own text still takes precedence. The pinned wiki page above the Topics and Messages lists gets the same styles.
  • CHANGE: Moving between wiki pages meant opening the Pages dropdown, and the page title only appeared in the breadcrumb. On larger screens, wiki pages now list every page in a column on the left, with Home first, the current page highlighted and a filter box when there are more than 15 pages. Each page starts with its title and an "Updated … by …" line linking to its history. A page's On This Page contents move to a panel on the right that stays in view while scrolling, with the wiki's sidebar below it. On phones the Pages dropdown and the inline contents remain.
  • BUGFIX: A wiki page's table of contents was numbered 0.1, 0.2, 0.3 when the page's headings started below the top level, which most pages do. The table of contents now lists headings as written, without numbers of its own, the same on phones and larger screens.
  • BUGFIX: A wiki sidebar or footer written in Markdown or plain text showed its raw text, such as **bold**, instead of formatting it. Sidebars and footers are now displayed like the rest of the page, and their HTML is cleaned the same way.
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.