Weird JS Issue relating to extensions: TypeError: t is undefined

IgorV

The issue

Forum is blank, I can't pinpoint exactly what extension(s) is(are) causing such errors like this, but it looks like it started happening after a server reboot, was working perfectly beforehand for days. I'm clueless, no good...

Flarum information

Flarum core: 1.8.1
PHP version: 8.2.10
MySQL version: 10.6.11-MariaDB-log
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, random, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, apcu, bz2, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, intl, exif, mcrypt, mysqli, pdo_mysql, Phar, posix, readline, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Zend OPcache
+-------------------------+---------+--------+
| Flarum Extensions       |         |        |
+-------------------------+---------+--------+
| ID                      | Version | Commit |
+-------------------------+---------+--------+
| flarum-flags            | v1.8.0  |        |
| flarum-suspend          | v1.8.0  |        |
| flarum-approval         | v1.8.0  |        |
| fof-user-bio            | 1.2.2   |        |
| fof-upload              | 1.3.4   |        |
| fof-moderator-notes     | 1.2.0   |        |
| fof-discussion-language | 1.2.11  |        |
| flarum-subscriptions    | v1.8.0  |        |
| flarum-sticky           | v1.8.0  |        |
| flarum-statistics       | v1.8.0  |        |
| flarum-nicknames        | v1.8.0  |        |
| flarum-mentions         | v1.8.2  |        |
| flarum-markdown         | v1.8.0  |        |
| flarum-lock             | v1.8.0  |        |
| flarum-likes            | v1.8.0  |        |
| flarum-lang-english     | v1.8.0  |        |
| flarum-emoji            | v1.8.0  |        |
| flarum-bbcode           | v1.8.0  |        |
+-------------------------+---------+--------+
Base URL: https://domain.com.br/forum/public
Installation path: /var/www/domain.com.br/forum
Queue driver: sync
Session driver: file
Mail driver: log
Debug mode: off

composer

"require": {
        "flarum-lang/brazilian": "*",
        "flarum/approval": "*",
        "flarum/bbcode": "*",
        "flarum/core": "*",
        "flarum/emoji": "*",
        "flarum/flags": "*",
        "flarum/lang-english": "*",
        "flarum/likes": "*",
        "flarum/lock": "*",
        "flarum/markdown": "*",
        "flarum/mentions": "*",
        "flarum/nicknames": "*",
        "flarum/pusher": "*",
        "flarum/statistics": "*",
        "flarum/sticky": "*",
        "flarum/subscriptions": "*",
        "flarum/suspend": "*",
        "flarum/tags": "*",
        "fof/byobu": "*",
        "fof/discussion-language": "*",
        "fof/moderator-notes": "*",
        "fof/oauth": "*",
        "fof/upload": "*",
        "fof/user-bio": "*"
    },

IgorV

Update!
Found what extension was causing it.

Sticky

I turned it off, and peace and harmony prevailed as everything fell into place, R.I.P to the Pinned posts though.

I don't really know what's the underlying cause, but I can work with this for now, while I try to search the database for answers.

TsXor

This may be caused by a typo in the Sticky plugin, but I cannot make sure.
Take a look at flarum/framework3886 . Maybe you can fix it by correcting that typo.
My fault. Its not. forum.js didn't even change after recompilation.

luceos

If the error happened after a reboot, it is likely that the reboot cleared the opcache or the compiled assets. Make sure to run composer update and php flarum cache:clear.

IgorV

luceos
I also considered that maybe it was cache related, this is configured on a LAMP stack and I only recently enabled caching. Before posting, I updated all dependencies, ran php flarum cache:clear, tried another reboot just in case, but to no avail. 😕

luceos

IgorV you say it is caused by sticky, but are you sure it's not another one. Usually the core extensions are very stable. We would be able to identify the root cause better by visiting the website. Alternatively try disabling all non flarum extensions and see if the issue persists.

IgorV

luceos
As far as I can tell, it's a conflict between sticky and at least one more, maybe fof/byobu` if I had to guess.
It only started happening later on, possibly after some posts were edited/removed...

IgorV

Update, after a while, I turned Sticky back on, and what do you know? Forum somehow is working again.
I guess I'll leave it on, if something goes haywire again, I'll turn it off

clarkwinkelmann

IgorV sometimes, the incompatibility between extension relates to the order in which they were enabled. So this can be one explanation why disabling and re-enabling an extension made a change.

Extensions developers have ways to force the extension order, if we discover which other extension caused the issue it might be as simple as adding a line specifying Sticky most load first in the extension "manifest" file.