Might not be the right place but noticed in the current Beta that partial word search is not currently implemented, any plan for this in the final 2.0?
ie, searching for "search" would not match "searching" in the post content or title.
Might not be the right place but noticed in the current Beta that partial word search is not currently implemented, any plan for this in the final 2.0?
ie, searching for "search" would not match "searching" in the post content or title.
Thanks for fixed the demosite ;D
Will there be a native support of a Progressive Web App? This is THE best feature for me. Just discovered, that the PWA Extension hasn't been updated for 6 months and I am afraid its abandoned... I just built up a community as an replacement for a Facebook group community and the PWA is a real game changer to gain acceptance in the community
Also nested Replies would be a great feature for me
How (not when) is planned migration from 1x to 2x?
Regarding posts, users etc.
I know that addons will have to make an update
Metus24 Will there be a native support of a Progressive Web App? This is THE best feature for me. Just discovered, that the PWA Extension hasn't been updated for 6 months and I am afraid its abandoned...
No, it will remain an extension. But many people use it, including clients from flarum bv, so we carry it's maintenance collaboratively.
Worke5r86 How (not when) is planned migration from 1x to 2x?
The upgrade/migration from latest stable 1.8 to 2.0 should not be an issue in terms of database integrity. Whether extensions you use are compatible by then will be the biggest question for most communities. We are doing our best to make the transition as simple as possible.
luceos I'd chip in to a bounty/crowdfunding drive for a migration tool, but I'd have to assume that some of the functionality that byobu offers will need to be added to the core direct messages extension for it to be usable for most forum owners.
if you want existing flarum forum owners to use the new DM functionality in 2.0, then I think a migration tool needs to be built...otherwise, what's the point in anyone using it?
by the way, what's the difference between a private discussion and a DM? aren't they essentially serving the same purpose?
andrewjs18 by the way, what's the difference between a private discussion and a DM? aren't they essentially serving the same purpose?
Nah, they are not the same, some seem to be confused about that. If we wanted the same thing we could have just asked FoF to pass byobu over to us, and I'm sure they would have accepted.
This extension was created because there was a lot of requests for something solely DM oriented, not linked to discussions.
Byobu allows you to create a private discussion with any number of recipients including groups. You can have multiple private discussions between person A and person B for example. You also have access to all discussion features.
The DM extension keeps a single stream of messages between person A and B (like other common messaging apps). And is completely separate from discussions.
They both serve different use cases. Though I understand that many had to use byobu for a lack of alternatives when their use case might have been more like what the new extension offers.
SychO I was actually surprised the flarum team didn't try to just integrate FoF byobu into the core code as it seemed to me that it is way more suited to do what most people need it do to help make a completed forum software solution.
you mentioned other common messaging apps. what other messaging app does not allow people to send a message to more than 1 person in the same message? I can't think of a single 1. further, what other forum softwares out there (especially ones being actively developed in 2025) do not allow someone to send a PM/DM to more than one person?
andrewjs18 what other messaging app does not allow people to send a message to more than 1 person in the same message?
If you're asking why this new extension doesn't have group messaging, it's because we first wanted to create a first iteration of it for 2.0, then add additional features like group messaging later.
The design was also made with group messaging in mind for the future, you can read more here: https://discuss.flarum.org/d/35114-flarum-20-private-messaging-uiux
As for your question about other messaging apps, the goal here wasn’t to match every feature from day one but to build something sustainable that can evolve over time.
Today we announce the release of Flarum 1.8.10, which primarily addresses a security vulnerability in session handling. We strongly recommend upgrading at your earliest convenience.
See CVE-2025-27794 for further information.
Run the following commands to update:
composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
php flarum migrate
php flarum cache:clear
This release also includes some general improvements, bringing the Flarum 1.x branch one step closer to its final version.
Today's release bumps the versions of flarum/core
and flarum/tags
, see below:
flarum/core
- 1.8.10
flarum/tags
- 1.8.4
A big thanks to @glowingblue for collaborating with us to resolve this security issue!
Hi, sorry for double posting, but I can`t get forward to update my forum.
Here my question:
Flarum
1.8.5PHP
8.1.31MySQL
10.5.26-MariaDB-0+deb11u2
Hi, tried to install 1.8.10, with this Instructions , but getting this error:
Flarum encountered a boot error. Details have been logged to the Flarum log file.
and this multiple times in the Log file:
[2025-03-17 22:22:37] flarum.ERROR: Error: Class "Doctrine\Deprecations\Deprecation" not found in /var/www/clients/xxxxxx/flarum/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOMySql/Driver.php:77
Has somebody a solution for that error? Not sure how to address this...
ThX in advance ️
Dr_Sommer if class not found errors are thrown, try using composer install
to install these missing classes. If that doesn't help try disabling deprecation warnings (as this seems related to doctrine's fallback class) using: https://discuss.flarum.org/d/36404-stopping-deprecation-warnings
@luceos: thx again, that woked perfectly... i did what was described here
SERVER SIDE was already correct, then
Flarum side
Edit your extend.php and add the following before the return [:
error_reporting(E_ALL & ~E_DEPRECATED & ~E_STRICT);
then rebooted the system and installed the new Flarum 1.8.10 Version... working.. ️
Hello,
Security updates are always welcome. I haven't encountered any errors, and everything seems to be working fine. However, I accidentally noticed something—I had mistakenly added display: none; to post-body in my custom CSS. After removing it, I realized that the post body in the main discussions was still missing. To restore all posts, I had to keep the custom code but without the display: none; function in the CSS. In the past, any changes I made via custom CSS would revert to normal after deletion. Has anyone else experienced this issue? By the way, I’ve cleared the cache multiple times.
.Post-body {
font-size: 14px;
line-height: 1.7;
position: relative;
overflow: auto;
overflow-wrap: break-word;
display: none
Xkyer maybe you have additional custom CSS that also affects this element?
It's difficult to provide guidance without being able to see the website. Using the development tools, it should be easy to check which rule(s) apply and guess from where they might come. It's a bit more complicated than vanilla CSS because the Less compiler causes CSS to destructively override previous rules, so to find out the cause we would need to check the browser development tools while the custom CSS has been fully removed, to see what's left and how it causes the post to be hidden.