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.0
If 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.0
luceos 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.