Another update is here. There's a mix of new features, quality-of-life improvements, and some deliberate removals that we think make the overall experience cleaner and more focused towards our 2.0 release.
Pages Character Cap Increased
The character limit for Pages has been raised from 60,000 to 500,000 characters. If you've been using Pages for documentation, rules, or longer-form content, you now have significantly more room to work with. This was a common request and a straightforward one to address.
Expanded CSS & HTML Support in Posts
Posts now support a wider range of CSS and HTML. This gives your members more flexibility in how they format their content, especially useful for communities that rely on creative or detailed post layouts. You can toggle the HTML button in the editor to enable HTML source. An example of what is possible below. For demonstrating purposes, I've chosen a template created by @Sarahkik
Custom Profile Fields: Multi-line Text
Custom profile fields now support a multi-line text option. Previously you were limited to single-line inputs, which wasn't ideal for fields like bios, descriptions, or anything that needs a bit more space. Multi-line fields render properly in the post bit and on profile pages.
Speaking of the post bit, empty or unfilled custom fields will no longer appear there. If a member hasn't filled in a field, it simply won't show. This keeps the post bit clean and avoids unnecessary visual clutter.
Hub Feed Filtering
The Hub feed now supports multi-select community filtering. You can filter by multiple communities at once, making it much easier to narrow down what you're looking at when browsing across boards.
Topic Title Preview
There's a new topic title preview modal. When hovering over a topic in the list, you'll get a quick preview of the opening post without having to click through. It's a small addition that saves time when scanning a busy forum.
Widgets on Category View
Widgets now render next to forums on the category view instead of below them. This is a much better use of screen space and keeps your sidebar content visible where it matters most.
Credits & Shop Extension Improvements
The Credits and Shop extension has received some attention around disabling, uninstalling, and how it integrates with board menus. The experience around toggling it on and off is now more predictable, and menu entries are handled correctly when the extension state changes.
Infinite Scroll Replaces Pagination
This is one of the bigger changes in terms of how the forum feels to use.
Both the topic list and the topic view now use infinite scroll instead of traditional pagination. On the topic list, a "Load more" button lets you pull in the next set of topics without a full page reload. On the topic view, replies load the same way. If you land on a deep-linked page, earlier replies load automatically when you scroll up, and the browser URL stays accurate throughout.
This also means direct links to specific replies still work. If a reply isn't on the current page, you'll be redirected to the correct position automatically.
Removals
We've removed topic descriptions. They were rarely used and added visual noise to the topic list without providing much value. The topic title and opening post preview now serve that purpose better.
The Message and Profile buttons under the post bit have also been removed. These were redundant with the user tooltip and profile link already available on the username and avatar. Removing them gives the post bit a cleaner look, especially on boards with several custom fields or achievements displayed.
UI Preparation for ForumSpark 2.0
A number of UI and UX changes have been made across the topic list and topic view pages. These are incremental adjustments that bring the interface closer to what we're building for FS2. Nothing disruptive, but you may notice things feeling a bit more polished and consistent. Topic list now also shows the last 5 members who replied to that topic. A cool new way to show some activity.
As always, if you run into anything unusual, please report it in the support/bug forum. Feedback is always welcome and appreciated. 😁
