Tilspire 1.18.0 | tilspire

Tilspire 1.18.0 is out. Community is now free, the paid ticket module becomes Feedback with a new Tracker inside it, members can close their own account, and every screen was gone over for polish. Here is what changes, by who it is for.

From 1.18.0 the Tilspire core is a free, open-source core (MPL 2.0). Up to 1.17.3 it was Apache 2.0.

For site owners #

Community is free. The forums ship with core and show as "Community" in the admin panel. Boards, topics, links and addresses are unchanged, and no licence key is needed.
Tickets is now Feedback, because it now holds Tickets and the new Tracker; its menu items read "Tickets" and "Tracker". It has its own Settings tab, and its public ticket pages are translated.
The Tracker. Members suggest ideas, report bugs, vote and follow a roadmap; staff triage them, and can turn a ticket into a tracker item without the client's name. It is off until you switch it on under Tracker, and then shows as a tab beside Community.
Your own addresses. Under Settings ▸ General, give the Blog, Forums, ticket portal and Tracker their own name and address (/forums can become /discuss); the old address redirects. The admin panel can move away from /adm too; see Security.
Captcha choices: reCAPTCHA v2, reCAPTCHA v3 or Cloudflare Turnstile, each with its own keys. Sign-in and password reset can now ask as well as sign-up; both are off by default.
View as. Staff with the new "View as" permission see the public site as a member, a role or a guest. Nothing can be sent while viewing, and every view is logged.
Theme preview. Staff who may preview themes can try an installed theme that is not live, page after page, on the real site. Only they see it; visitors keep the live theme. A strip at the top names the theme, can copy the live theme's options into it, and stops the preview.
Moderation you can undo. Forum and comment moderators now Hide posts and comments, and can show them again. Deleting for good needs a new permission in each, which Administrators get with the update.
Cookie consent, with Reject all, Accept all and a choice per kind, under Settings. New installs ask; an updated site asks only if it runs the default theme with Google Analytics.
Faster pages for visitors who are not signed in, and theme and core files cached for a week. Signed-in and personal pages are never cached.
A new default theme: a calm sky palette in light and dark, and matching blog, community, ticket, tracker and account pages. A site on its own theme is unaffected.
A clearer Assistant. An empty chat opens with "Needs you" pills that count what is waiting and link straight to it, and its help is a short card in sections. Changes still arrive as drafts; nothing is published without you.

For members #

Close your own account from the account page, with your password and, if you use two-step sign-in, your code. It takes effect at once. Your forum posts and comments stay, shown as "Former member"; Feedback tickets stay with the email address they came from. Accounts with panel or moderation rights ask an administrator instead.
Edit and delete your own comments, within time limits the site sets.
Private ticket links. A ticket link no longer contains your email address, and "Check ticket status" emails you a fresh link. Old email links no longer open.
An account menu in the default theme, with Light, Dark or Auto.

For theme authors #

Themes carry no rules. Buttons such as Reply, Quote and Delete are named actions: the theme places them, core decides who sees them.
Core shows the maintenance page itself, so a theme needs no maintenance code.
The Template API gains section() for renamed sections, plus the Tracker's views. Custom themes keep working; details in site/themes/README.md and Themes.

For module authors and operators #

Operator API: page links, roles, updates and AI usage can be read; comment moderation, field groups and more can be proposed as drafts, none self-approved. The Tracker can be read and proposed too.
Ticket attachments open only for the ticket's client and staff who manage tickets, and Health warns if the folder is served directly.

Polished throughout #

Every admin screen and the default theme's public pages were checked at phone, tablet and desktop widths, in light and dark, and by keyboard. Dialogs keep the keyboard inside and give focus back, every field and button is named, the top bar fits at every width, dark mode has more contrast, and the account pages and their mails are translated. The changelog lists each fix.

Also in this release #

Content locks: a Locked switch on pages and posts, plus bulk Lock and Unlock.
Sign-up limits per address.
Search on the Users, Posts and Media screens.
The admin panel's phone layout.

Updating #

Core and Feedback together. With Feedback switched on, the updater takes core and Feedback to 1.18.0 in one run, core first. A lapsed licence still gets Feedback 1.18.0, as the version this core needs. Blog, Comments and Community travel inside the core package and update with it.
On nginx, deny the ticket uploads folder, which Apache already guards:
```
location ^~ /uploads/tickets/ { return 404; }
```
Captcha on sign-in: a provider outage keeps members out until it passes, and reCAPTCHA v3 and Turnstile need the site to answer on one address only.
An undo to 1.17.x drops a renamed section address.

Apply it from the admin panel's Updates page, or see Updates. New here? Start at Download.

This announcement and the updated documentation were written through the Operator API, under a self-approval the site's owner granted for this release. See the changelog for everything in the release.