Hari I uninstalled it 30min ago.
now i have reinstalled extiverse and I forgot to add AUTH key this time
and this is happening now
hope I will now break it ?
i have deactivated author change from flarum dashboard .
should I just hit yes ? it will take care of everything ?
never expected this command will trigger the actual flarum upgrade I thought extiverse will get updated 
extiverse upgrade -vvv.
after upgrade shall I able to use SEO extension in an unsupported manner?
i am really sorry to call you @clarkwinkelmann i don't know how to exit from this .. should I hit yes will it break my live website?
i didn't want to pull you into this but my terminal is open from 10min afraid session will get break
Hari removing the "Author Change" extension isn't dangerous, you will only loose access to the feature, but the forum will continue to work fine.
clarkwinkelmann is it okay to remove from here or need to follow the traditional remove command?
Edit : I have removed it 
I got an error when executing extiverse check command.
In CurlFactory.php line 201:
cURL error 77: error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: /etc/ssl/certs (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) running extiverse 3.2.0 and PHP8.0.6. Is there any solution？
Update:
I switched to PHP 7.4.19 and the command executed successfully. However I found that extiverse says some plugins' compatibility status is unknown even if it is compatible in extiverse website.
luceos Which one?
This is not the case with specific plugins. The unknown compatibility status seems always occur at a specific position.
For example: I executed /path/to/my/php7.4/bin/php ./extiverse check and got the below result:
+--------------------------------------+-----------+---------+------+------------------------------------+
| Extension | Installed | Highest | FLC* | Discuss |
+--------------------------------------+-----------+---------+------+------------------------------------+
| flarum | v1.0.0 | v1.0.0 | | |
| askvortsov/flarum-moderator-warnings | v0.6.0 | v0.6.0 | | |
| flarum/approval | v1.0.0 | v1.0.0 | | |
| flarum/emoji | v1.0.0 | v1.0.0 | | |
| flarum/flags | v1.0.0 | v1.0.0 | | |
| flarum/lang-english | v1.0.0 | v1.0.0 | | |
| flarum/likes | v1.0.0 | v1.0.0 | | |
| flarum/lock | v1.0.0 | v1.0.0 | | |
| flarum/markdown | v1.0.0 | v1.0.0 | | |
| flarum/mentions | v1.0.0 | v1.0.0 | | |
| flarum/statistics | v1.0.0 | v1.0.0 | | |
| flarum/sticky | v1.0.0 | v1.0.0 | | |
| flarum/subscriptions | v1.0.0 | v1.0.0 | | |
| flarum/suspend | v1.0.0 | v1.0.0 | | |
| flarum/tags | v1.0.0 | v1.0.0 | | |
| fof/follow-tags | 1.0.0 | unknown | | |
| fof/formatting | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/17770 |
| fof/forum-statistics-widget | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/22380 |
| fof/polls | 1.0.0 | 1.0.1 | | https://discuss.flarum.org/d/20586 |
| fof/profile-image-crop | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/18286 |
| fof/reactions | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/20655 |
| fof/share-social | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/20401 |
| fof/socialprofile | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/18775 |
| fof/subscribed | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/20917 |
| fof/upload | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/4154 |
| fof/username-request | 1.0.0 | unknown | | |
+--------------------------------------+-----------+---------+------+------------------------------------+
* FLC: Compatibility of extension with latest Flarum version: v1.0.0If I remove the unknown-status plugin fof/follow-tags and fof/username-request , another two plugins' compatibility status will become unknown. Here's the extiverse check result after executing composer remove to the two plugins:
+--------------------------------------+-----------+---------+------+------------------------------------+
| Extension | Installed | Highest | FLC* | Discuss |
+--------------------------------------+-----------+---------+------+------------------------------------+
| flarum | v1.0.0 | v1.0.0 | | |
| askvortsov/flarum-moderator-warnings | v0.6.0 | v0.6.0 | | |
| flarum/approval | v1.0.0 | v1.0.0 | | |
| flarum/emoji | v1.0.0 | v1.0.0 | | |
| flarum/flags | v1.0.0 | v1.0.0 | | |
| flarum/lang-english | v1.0.0 | v1.0.0 | | |
| flarum/likes | v1.0.0 | v1.0.0 | | |
| flarum/lock | v1.0.0 | v1.0.0 | | |
| flarum/markdown | v1.0.0 | v1.0.0 | | |
| flarum/mentions | v1.0.0 | v1.0.0 | | |
| flarum/statistics | v1.0.0 | v1.0.0 | | |
| flarum/sticky | v1.0.0 | v1.0.0 | | |
| flarum/subscriptions | v1.0.0 | v1.0.0 | | |
| flarum/suspend | v1.0.0 | v1.0.0 | | |
| flarum/tags | v1.0.0 | v1.0.0 | | |
| fof/formatting | 1.0.0 | unknown | | |
| fof/forum-statistics-widget | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/22380 |
| fof/polls | 1.0.0 | 1.0.1 | | https://discuss.flarum.org/d/20586 |
| fof/profile-image-crop | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/18286 |
| fof/reactions | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/20655 |
| fof/share-social | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/20401 |
| fof/socialprofile | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/18775 |
| fof/subscribed | 1.0.0 | 1.0.0 | | https://discuss.flarum.org/d/20917 |
| fof/upload | 1.0.0 | unknown | | |
+--------------------------------------+-----------+---------+------+------------------------------------+
* FLC: Compatiblity of extension with latest Flarum version: v1.0.0luceos Looks like your certificates are misconfigured for that php version.
I agree. Switching to an earlier version temporally fixed the problem and I'm now waiting for my service provider's update to fix it.
luceos Add the
~/.composer/vendor/binto your PATH and then simply use it withextiverse
I found this didn't work for me as my composer bin dir wasn't in that location (it was under .config/composer).
Adding the line below to ~/.bashrc then running source ~/.bashrc worked like a charm, and should work on any globally available composer install:
export PATH="$(composer global config bin-dir --absolute --quiet):$PATH"luceos [deleted] I have finally updated PHP version from 7.2 to 7.4 on my vps as I'm preparing for V1.0.0 but I haven't switched to it yet, I need expert guide here that if I switch from 7.2 to 7.4 in my vestacp for my forum, is it gonna create any issue or work on the go? I mean I'm confused if changing a php version on a running site can cause any issue?
HD3D yes it can cause issues, but if you encounter any just run composer update --prefer-dist --no-dev -a immediately. Do not upgrade any dependencies/constraints, do not use the extiverse helper to upgrade, just run that command.
I've upgraded the demos a few weeks ago from 7.4 to 8.0 without issue, I think the same should be possible from 7.2 to 7.4.
HD3D It should work fine, provided you also install all required extensions for that version of PHP you want to use. You'll soon find out if any extensions are missing (in terms of PHP) as there will be an error message that should also tell you which extension is missing. In some cases, you'll also need to restart Apache after adding new PHP extensions.
My upgrade from a previous PHP version to 7.4 went without issue.
CDN18 I'm seeing something similar here in terms of "unknown"
metabullet@vps2:~/public_html$ php extiverse check --ansi | grep "| no"
| flarum/suspend | v0.1.0-beta.16 | unknown | no | |
| fof/reactions | 0.6.0 | unknown | no | |
| fof/realtimedate | 0.3.0 | 0.3.0 | no | |
| justoverclock/flarum-ext-welcomebox | 1.1.6 | unknown | no | |
| kyrne/websocket | 2.5.0 | 2.5.0 | no | |
| nearata/flarum-ext-copy-code-to-clipboard | v1.3.0 | v1.3.0 | no | |
| nearata/flarum-ext-internal-links-noreload | v1.0.2 | v1.0.2 | no | |
| reflar/recache | 2.3.3 | 2.3.3 | no | |
| v17development/flarum-seo | v1.7.2 | unknown | no | |luceos Ummm - not sure. I have 0.3.2.
EDIT - seems I am, yes
[deleted] After switching to PHP 7.4 I'm seeing this on my forum's homepage
<?php
/*
* This file is part of Flarum.
*
* (c) Toby Zerner <toby.zerner@gmail.com>
*
* For the full copyright and license information, please view the LICENSE
* file that was distributed with this source code.
*/
require 'vendor/autoload.php';
$server = new Flarum\Http\Server(
Flarum\Foundation\Site::fromPaths([
'base' => __DIR__,
'public' => __DIR__,
'storage' => __DIR__.'/storage',
])
);
$server->listen();And of course I ran composer update --prefer-dist --no-dev -a
Cleared Cache
And php flarum info
Flarum core 0.1.0-beta.13
PHP version: 7.4.18
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, pcntl, Reflection, SPL, session, standard, sodium, mysqlnd, PDO, xml, apcu, bcmath, calendar, ctype, curl, dom, mbstring, FFI, fileinfo, ftp, gd, gettext, iconv, igbinary, intl, json, exif, memcache, msgpack, mysqli, pdo_mysql, apc, posix, readline, shmop, SimpleXML, soap, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, xmlreader, xmlwriter, xsl, zip, Phar, memcached, Zend OPcache