Issues on upgrading

peopleinside · Nov 14, 2020

clarkwinkelmann I still be unable to Upgrade to Beta 14.
I see just now I posted update in "a wrong post".

I'm open to suggestions.

clarkwinkelmann · Nov 14, 2020

You could remove the extensions that cause issues and install them again afterwards.

peopleinside · Nov 14, 2020

clarkwinkelmann when I try to remove fof/upload it doesn't remove.
Also I'm asking why now that extension are compatible I cannot upgrade.
What is blocking me from upgrading?
How can I remove extensions that never remove with composer fof/upload remove?

I removed all extension that cause conflict and now get:

composer update
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires fof/oauth ^0.1.0 -> satisfiable by fof/oauth[0.1.0].
    - Conclusion: don't install illuminate/console v5.7.2 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.3 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.4 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.5 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.6 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.7 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.8 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.9 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.10 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.11 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.15 (conflict analysis result)
    - Conclusion: don't install illuminate/console 5.7.17 (conflict analysis result)
    - Conclusion: don't install illuminate/console 5.7.18 (conflict analysis result)
    - Conclusion: don't install illuminate/console 5.7.19 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.20 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.21 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.22 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.23 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.26 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.27 (conflict analysis result)
    - Conclusion: don't install illuminate/console v5.7.28 (conflict analysis result)
    - fof/oauth 0.1.0 requires flarum/core ^0.1.0-beta.14 -> satisfiable by flarum/core[v0.1.0-beta.14, v0.1.0-beta.14.1].
    - Conclusion: don't install flarum/core v0.1.0-beta.14.1 (conflict analysis result)
    - Root composer.json requires fof/drafts 0.1.13 -> satisfiable by fof/drafts[0.1.13].
    - Conclusion: don't install illuminate/console v5.7.1 (conflict analysis result)
    - flarum/core v0.1.0-beta.14 requires illuminate/queue ^6.0 -> satisfiable by illuminate/queue[v6.0.0, ..., v6.20.3].
    - illuminate/queue[v6.0.0, ..., v6.20.3] require illuminate/console ^6.0 -> satisfiable by illuminate/console[v6.0.0, ..., v6.20.3].
    - You can only install one version of a package, so only one of these can be installed: illuminate/console[v5.7.0, ..., v5.7.28, v6.0.0, ..., v6.20.3].
    - Conclusion: install one of illuminate/console[v5.7.0, ..., v5.7.28] (conflict analysis result)

composer why-not flarum/core v0.1.0-beta.14
flarum/core    v0.1.0-beta.14  requires          components/font-awesome (^5.14.0)
flarum/flarum  -               does not require  components/font-awesome (but 5.9.0 is installed)
flarum/core    v0.1.0-beta.14  requires          dflydev/fig-cookies (^2.0.1)
flarum/flarum  -               does not require  dflydev/fig-cookies (but v1.0.2 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/bus (^6.0)
flarum/flarum  -               does not require  illuminate/bus (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/cache (^6.0)
flarum/flarum  -               does not require  illuminate/cache (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/config (^6.0)
flarum/flarum  -               does not require  illuminate/config (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/container (^6.0)
flarum/flarum  -               does not require  illuminate/container (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/contracts (^6.0)
flarum/flarum  -               does not require  illuminate/contracts (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/database (^6.0)
flarum/flarum  -               does not require  illuminate/database (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/events (^6.0)
flarum/flarum  -               does not require  illuminate/events (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/filesystem (^6.0)
flarum/flarum  -               does not require  illuminate/filesystem (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/hashing (^6.0)
flarum/flarum  -               does not require  illuminate/hashing (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/mail (^6.0)
flarum/flarum  -               does not require  illuminate/mail (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/queue (^6.0)
flarum/flarum  -               does not require  illuminate/queue (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/session (^6.0)
flarum/flarum  -               does not require  illuminate/session (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/support (^6.0)
flarum/flarum  -               does not require  illuminate/support (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/validation (^6.0)
flarum/flarum  -               does not require  illuminate/validation (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          illuminate/view (^6.0)
flarum/flarum  -               does not require  illuminate/view (but v5.7.28 is installed)
flarum/core    v0.1.0-beta.14  requires          nesbot/carbon (^2.0)
flarum/flarum  -               does not require  nesbot/carbon (but 1.39.1 is installed)
[)code]

clarkwinkelmann · Nov 14, 2020

You might have somehow broken your composer install.

You could (backup, then) delete vendor and composer.lock, then run composer install. This will probably cause some extensions and dependencies to update, but if you were trying to update anyway it probably won't break anything. Depending what extensions you have now you might end up on beta 14, or on beta 13 where you can try the commands again.

peopleinside · Nov 14, 2020

clarkwinkelmann Done, it reinstall extensions but still be unable to update to Beta 14, when I try the lock file created still be invalid:

composer remove --no-update flarum/auth-facebook flarum/auth-github flarum/auth-twitter
flarum/auth-facebook is not required in your composer.json and has not been removed
flarum/auth-github is not required in your composer.json and has not been removed
flarum/auth-twitter is not required in your composer.json and has not been removed
./composer.json has been updated
composer update --no-install --with-all-dependencies
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
61 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
composer require --no-update fof/oauth
Using version ^0.1.0 for fof/oauth
./composer.json has been updated
composer install --prefer-dist --no-dev -a
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. It is recommended that you run `composer update` or `composer update <package name>`.
Nothing to install, update or remove
Generating optimized autoload files
Carbon 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.
61 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

There is a way to migrate my community by creating new Beta 14 install?
I need migrate posts, users, extensions.

The upgrade process did not work for two community's I have,

karaok · Nov 14, 2020

peopleinside let's see if we can't get this fixed for you... Can you please copy/paste your composer.json file?

peopleinside · Nov 14, 2020

karaok

{
    "name": "flarum/flarum",
    "description": "Delightfully simple forum software.",
    "type": "project",
    "keywords": [
        "forum",
        "discussion"
    ],
    "homepage": "https://flarum.org/",
    "license": "MIT",
    "authors": [
        {
            "name": "Toby",
            "email": "***@gmail.com"
        },
        {
            "name": "Franz",
            "email": "**@develophp.org"
        }
    ],
    "support": {
        "issues": "https://github.com/flarum/core/issues",
        "source": "https://github.com/flarum/flarum",
        "docs": "https://flarum.org/docs/"
    },
    "require": {
        "askvortsov/flarum-moderator-warnings": "^0.2.4",
        "clarkwinkelmann/flarum-ext-emojionearea": "^0.2.0",
        "clarkwinkelmann/flarum-ext-first-post-approval": "0.1.1",
        "flarum/akismet": "^0.1.0@beta",
        "flarum/approval": "^0.1.0",
        "flarum/bbcode": "^0.1.0",
        "flarum/core": "^0.1.0-beta.13",
        "flarum/emoji": "^0.1.0",
        "flarum/flags": "^0.1.0",
        "flarum/lang-english": "^0.1.0",
        "flarum/likes": "^0.1.0",
        "flarum/lock": "^0.1.0",
        "flarum/markdown": "^0.1.0",
        "flarum/mentions": "^0.1.0",
        "flarum/pusher": "^0.1.0",
        "flarum/statistics": "^0.1.0",
        "flarum/sticky": "^0.1.0",
        "flarum/subscriptions": "^0.1.0",
        "flarum/suspend": "^0.1.0",
        "flarum/tags": "^0.1.0",
        "fof/default-user-preferences": "^0.2.0",
        "fof/drafts": "0.1.13",
        "fof/links": "0.3.0",
        "fof/moderator-notes": "^0.2.5",
        "fof/nightmode": "^0.5.2",
        "fof/recaptcha": "^0.1.0",
        "fof/spamblock": "0.2.1",
        "fof/stopforumspam": "0.2.2",
        "fof/upload": "0.10.0",
        "fof/user-bio": "^0.2.0",
        "fof/user-directory": "^0.3.3",
        "franzl/flarum-open-links-in-new-tab": "^0.1.0",
        "jordanjay29/flarum-ext-summaries": "^0.3.1",
        "nearata/lang-italian": "^0.1.0@beta",
        "noriods/auto-more": "^0.3.0",
        "reflar/cookie-consent": "^0.2.0"
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true
    },
    "minimum-stability": "beta",
    "prefer-stable": true
}

karaok · Nov 14, 2020

peopleinside

Ok, as Clark suggested just now, please delete composer.lock and the vendor folder. Then run composer install after you've placed the changes below:

{
    "name": "flarum/flarum",
    "description": "Delightfully simple forum software.",
    "type": "project",
    "keywords": [
        "forum",
        "discussion"
    ],
    "homepage": "https://flarum.org/",
    "license": "MIT",
    "authors": [
        {
            "name": "Toby",
            "email": "***@gmail.com"
        },
        {
            "name": "Franz",
            "email": "**@develophp.org"
        }
    ],
    "support": {
        "issues": "https://github.com/flarum/core/issues",
        "source": "https://github.com/flarum/flarum",
        "docs": "https://flarum.org/docs/"
    },
    "require": {
        "askvortsov/flarum-moderator-warnings": "*",
        "clarkwinkelmann/flarum-ext-emojionearea": "*",
        "clarkwinkelmann/flarum-ext-first-post-approval": "*",
        "flarum/akismet": "*",
        "flarum/approval": "*",
        "flarum/bbcode": "*",
        "flarum/core": "^0.1.0-beta.13",
        "flarum/emoji": "*",
        "flarum/flags": "*",
        "flarum/lang-english": "*",
        "flarum/likes": "*",
        "flarum/lock": "*",
        "flarum/markdown": "*",
        "flarum/mentions": "*",
        "flarum/pusher": "*",
        "flarum/statistics": "*",
        "flarum/sticky": "*",
        "flarum/subscriptions": "*",
        "flarum/suspend": "*",
        "flarum/tags": "*",
        "fof/default-user-preferences": "*",
        "fof/drafts": "*",
        "fof/links": "*",
        "fof/moderator-notes": "*",
        "fof/nightmode": "*",
        "fof/recaptcha": "*",
        "fof/spamblock": "*",
        "fof/stopforumspam": "*",
        "fof/upload": "*",
        "fof/user-bio": "*",
        "fof/user-directory": "*",
        "franzl/flarum-open-links-in-new-tab": "*",
        "jordanjay29/flarum-ext-summaries": "*",
        "nearata/lang-italian": "*",
        "noriods/auto-more": "*",
        "reflar/cookie-consent": "*"
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true
    },
    "minimum-stability": "beta",
    "prefer-stable": true
}

peopleinside · Nov 14, 2020

Wow this time works.
I get an error for ReFlar / cookie-consent , unistalled this and now I'm on Beta 14.
Thanks!

One community migrated. I will see to migrate also the second as soon as possible.
Many thanks

karaok · Nov 14, 2020

peopleinside Great Was just gonna mention that cookie consent is not compatible yet, and possibly a couple of others too, but at least you're upgraded now!

peopleinside · Nov 14, 2020

karaok yes thanks. Just discovered ReCaptcha even if is ready for Beta 14 seems never work. I opened an issue.

karaok · Nov 14, 2020

peopleinside which recaptcha have you created on google's side? It must be v2 for fof/recaptcha to function - v3 is not supported

peopleinside · Nov 14, 2020

karaok Yes version 2 as I was using before.
I use also with success the invisible ReCaptcha on Beta 13 anyway no one seems work.
FriendsOfFlarum/recaptcha13

karaok · Nov 14, 2020

peopleinside very strange. I had this working previously, but am seeing the same issue as you now. I will investigate