Mentions and Replies not tagging (remaining in raw text)

Crazy_Muffins

Howdy all!

Fresh install, 1.8.13, we're just playing around at the moment and noticed that Replies to posts, and "@" mentions are not behaving. Reply's are showing the raw output and not hyperlinking, and @ mentions while prompting to autocomplete during typing don't actually turn in to a tag or notification for said user.

Screenshot showing what I'm butchering the explanation of 🙂

Issue persists with and without the Pallet theme running, Mentions is enabled and Allow username mention format is on, mention groups is currently set to Members.

Flarum information

Current SysInfo

Flarum core: 1.8.13
PHP version: CLI: 8.4.13, Web: 8.4.13
PHP memory limit: CLI: 128M, Web: 128M
MySQL version: 8.0.45-0ubuntu0.24.04.1
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, random, Reflection, SPL, session, standard, sodium, cgi-fcgi, mysqlnd, PDO, xml, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, intl, exif, mysqli, pdo_mysql, pdo_sqlite, Phar, posix, readline, shmop, SimpleXML, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache
+-------------------------+---------+--------+-------+
| Flarum Extensions | | | |
+-------------------------+---------+--------+-------+
| ID | Version | Commit | Notes |
+-------------------------+---------+--------+-------+
| flarum-flags | v1.8.2 | | |
| flarum-tags | v1.8.6 | | |
| flarum-approval | v1.8.2 | | |
| madeyedeer-pallet-theme | v0.2.5 | | |
| fof-split | 1.1.1 | | |
| fof-polls | 2.3.1 | | |
| fof-oauth | 1.7.3 | | |
| fof-merge-discussions | 1.4.3 | | |
| fof-default-group | 1.1.3 | | |
| flarum-suspend | v1.8.5 | | |
| flarum-subscriptions | v1.8.1 | | |
| flarum-sticky | v1.8.2 | | |
| flarum-statistics | v1.8.1 | | |
| flarum-mentions | v1.8.5 | | |
| flarum-markdown | v1.8.1 | | |
| flarum-lock | v1.8.2 | | |
| flarum-likes | v1.8.1 | | |
| flarum-lang-english | v1.8.0 | | |
| flarum-emoji | v1.8.1 | | |
| flarum-bbcode | v1.8.0 | | |
+-------------------------+---------+--------+-------+
Base URL: https://forum.rustybucket.net
Installation path: /var/www/laravel/public
Queue driver: sync
Session driver: file
Mail driver: smtp
Debug mode: off

GreXXL

Crazy_Muffins there is no known issues about this so I would assume something specific to your setup. After playing around with extensions have you run php flarum cache:clear? Do you have any output in your storage/logs or in the browser console?

Sidenote: The maxmimum recommended PHP version for 1.8.x is PHP 8.3. For later PHP version you will have to wait for Flarum v2 that is currently in beta testing.

Crazy_Muffins

Howdy! Thanks for the reply, when i get a sec i'll snag the logs and get back! These kinds of setups are still a new thing to me, I followed a deployment guide online for deploying a Laravel droplet on DigitalOcean, then pulled down Flarum, made the MySQL instance and then completed the Flarum setup.

I'll have to try and figure out how to change php versions in this sort of setup, solid chance it could be something like that! Everything else is playing nicely, so good reason to start with the system requirements base line (I didn't even realise it was ahead - Woops!)

Edit: Forgot to answer!
Yep, cache clear has been done. I'll figure out installing 8.1, then if it persists report back with the log after that 🙂

GreXXL

Crazy_Muffins by the way although Flarum uses Laravel it's not a Laravel application. So the Laravel container might acually not be the best way to go. What you want is basically a normal LAMP setup where you have access to SSH to be able to run composer commands yourself.

Crazy_Muffins

GreXXL Ahhhh!

I ended up following this for the most part;

Mostly as a lot of this ecosystem is still pretty new to me so not super sure what to go for and avoid. On this setup I do have SSH access but possibly a different type than intended?

Crazy_Muffins

Before doing anything further, I've given the droplet a reboot not expecting that to actually do anything, and presto they are working! (Maybe I didn't actually clear the cache correctly...) I have more than likely not set this up correctly so long term I may still be better to heed your advise and run up under LAMP instead.

Is there a process to backup and import the flarum instance itself, unless doing so would be inadvisable 🙂

GreXXL

Crazy_Muffins it's pretty simple you just backup your database and files (exepct the vendor folder). Move it to the new host. On the new host you edit the config.php to point to the restored new database and run composer install.

Crazy_Muffins

GreXXL Thanks for that - I appreciate the info! 🙂