pentarou Was the extension enabled when you ran php flarum info ? The only enabled extensions are the core ones...

    @datitisev I try to only use core extensions, I've removed the FoF Links extension, as I was unable to access the configuration panel, here's the output with the extension installed and enabled:

    Flarum core 0.1.0-beta.8.1
    PHP version: 7.3.6
    Loaded extensions: Core, date, libxml, openssl, pcre, zlib, bz2, calendar, ctype, hash, filter, ftp, gettext, gmp, SPL, iconv, pcntl, readline, Reflection, session, standard, SimpleXML, sockets, mbstring, tokenizer, xml, mysqlnd, bcmath, curl, dba, dom, enchant, fileinfo, gd, imagick, imap, intl, json, ldap, exif, mysqli, odbc, PDO, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, pgsql, Phar, posix, pspell, redis, soap, sodium, sqlite3, sysvmsg, sysvsem, sysvshm, tidy, xmlreader, xmlrpc, xmlwriter, xsl, zip, ionCube Loader, Zend OPcache
    +----------------------+-----------------+--------+
    | Flarum Extensions | | |
    +----------------------+-----------------+--------+
    | ID | Version | Commit |
    +----------------------+-----------------+--------+
    | flarum-approval | v0.1.0-beta.8 | |
    | flarum-bbcode | v0.1.0-beta.8 | |
    | flarum-emoji | v0.1.0-beta.8 | |
    | flarum-lang-english | v0.1.0-beta.8 | |
    | flarum-flags | v0.1.0-beta.8.1 | |
    | flarum-likes | v0.1.0-beta.8.1 | |
    | flarum-lock | v0.1.0-beta.8 | |
    | flarum-markdown | v0.1.0-beta.8 | |
    | flarum-mentions | v0.1.0-beta.8.1 | |
    | flarum-statistics | v0.1.0-beta.8 | |
    | flarum-sticky | v0.1.0-beta.8 | |
    | flarum-subscriptions | v0.1.0-beta.8 | |
    | flarum-suspend | v0.1.0-beta.8 | |
    | flarum-tags | v0.1.0-beta.8.2 | |
    | fof-links | 0.2.0 | |
    +----------------------+-----------------+--------+
    Base URL: private
    Installation path: private
    Debug mode: off

    You could try running composer dump-autoload in the Flarum root folder to re-create the loader files.

    @clarkwinkelmann I tried your solution and cleared the cache, but it didn't solve the problem, here is the output:

    Generating autoload filesCarbon 1 is deprecated, see how to migrate to Carbon 2.
    https://carbon.nesbot.com/docs/#api-carbon-2
    You can run './vendor/bin/upgrade-carbon' to get help in updating carbon and other frameworks and libraries that depend on it. Generated autoload files containing 11 classes

      pentarou the Carbon warning can be ignored. The Composer command seems to have been successful.

      So still the same error when trying to access the forum ?

      Here are a few others things that might help us troubleshoot:

      • Can you tell us what kind of server this is (managed, VPS ?) and how it was configured ?
      • Can you post the output of cat vendor/composer/autoload_psr4.php | grep FoF ? This will tell us if Composer has registered the autoloader for the extension or not.
      • Also can you check if vendor/fof/links/src/Listener/AddLinksRelationship.php exists ?
      • Could you try enabling display_errors in your PHP config as described in https://flarum.org/docs/troubleshoot.html#step-1-turn-on-debug-mode and try again ?

      If it's registered and it exists I don't know what could cause the files to not be found. Could it be something related to php 7.3 ? 🤔

          clarkwinkelmann Could it be something related to php 7.3 ?

          Oh, I didn't even notice it was PHP 7.3. Other people have been having issues on PHP 7.3, so that is most likely the cause. I think it's a composer issue, but not entirely sure.

            clarkwinkelmann Unfortunately the same error still occurs:

            • VPS Plesk Onyx Version 17.8.11 Update #56 | 1024M memory_limit | Subdomain

            • Output 'FoF\\Links\\' => array($vendorDir . '/fof/links/src'), (FoF displayed in red text color)

            • Path and file vendor/fof/links/src/Listener/AddLinksRelationship.php does exist

            • Enabled display_errors in php.ini but nothing new shows in both front-end and PHP error log

            • PHP Version: 7.2.19 gives the same error @datitisev, clarkwinkelmann

                  datitisev I have deleted the vendor directory in SSH using rm -rf vendor, confirmed using PHP 7.2 in both domain and shell and executed the composer install command. The vendor directory reappears. I have cleared the Flarum and browser cache, and restart the server, but it still outputs the same error in the front-end.

                      clarkwinkelmann Sure, I use BladeVPS by TransIP, running Plesk Onyx Version 17.8.11 on centos-release-7-6.1810.2.el7.centos.x86_64

                        The same error applies to other extensions like Discussion views as well, but with another class of course, so I don't think the extensions are the problem.

                        There were some duplicate folders such as vendor outside the Flarum root (httpdocs) folder, so I deleted it and it started throwing errors such as Warning: require (../ vendor / autoload.php): could not open the stream: no file or directory which made me think that flarum may have used files and directories outside the httpdocs directory, perhaps this is related to the errors regarding the extensions.

                        Any thoughts on this?

                          pentarou that might be the cause yeah, without an idea of the actual structure and paths configuration it's hard to say. But the error proves that you've been trying to fix the wrong vendor folder.

                              luceos

                              I recall having to move Flarum from a folder to the root because that's how it was initially installed, there must have been a mistake from my side. I changed line 12 in index.php to vendor/autoload.php and now works normally, even with the extension installed and enabled.

                              Thanks for the help, is there something more I need to look at?

                                  pentarou I changed line 12 in index.php to vendor/autoload.php

                                  Do not touch any file inside vendor, that's not how to solve this issue. Please provide the line you changed and the directory structure you have now.

                                  edit: you should be able to delete vendor at all times and get to the same state by running composer install.

                                    @luceos My directory structure is as followed:

                                    /var/www/vhosts/domain.com/
                                    /var/www/vhosts/domain.com/httpdocs (website)
                                    /var/www/vhosts/domain.com/forum.domain.com Flarum subdomain (root)

                                    The only change I made was ../vendor/autoload.php in line 12 of index.php inside of the root of Flarum to vendor/autoload.php

                                      pentarou The index.php should not be in the Flarum root... there's a reason why we moved it to the public folder in beta 8.... Having it there allows access to vendor and config files, which is a security issue.

                                      Did you move it out of the public folder yourself ?

                                          datitisev

                                          Thanks for the clarification, Flarum was installed by default in a subdirectory, so I searched Google to find a solution to move Flarum to the root. I suspect I made a mistake during that process.