Trying to upgrade from beta 12

Kennon1st

I've sadly neglected my Flarum install at agot.cards/flarum for the last year or so, but recently realized that much has happened in the meantime, so I've been trying to follow the update guide at https://docs.flarum.org/update.html#general-steps.

However, it seems that I can't remove any of my plugins before attempting the update. When I deactivate them in the admin panel and then click remove, I get a "Please Wait" message and then go back to the panel and still see the plugin.

Just in case, I attempted the follow the rest of the guide from there, but get the below message when trying to run the update:
_Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires flarum/auth-facebook *, found flarum/auth-facebook[dev-next-back, dev-master, dev-1359-oauth2-improvements, v0.1.0-beta.3, ..., 0.1.x-dev (alias of dev-master)] but it does not match your minimum-stability.
Problem 2
- Root composer.json requires flarum/auth-github *, found flarum/auth-github[dev-next-back, dev-master, dev-1359-oauth2-improvements, v0.1.0-beta.3, ..., 0.1.x-dev (alias of dev-master)] but it does not match your minimum-stability.
Problem 3
- Root composer.json requires flarum/auth-twitter *, found flarum/auth-twitter[dev-next-back, dev-master, v0.1.0-beta.3, ..., 0.1.x-dev (alias of dev-master)] but it does not match your minimum-stability.
Problem 4
- extiverse/bazaar[0.1.0, ..., 0.2.4] require flarum/core ⁰.1.0-beta.6 -> found flarum/core[v0.1.0-beta.6, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- extiverse/bazaar[0.3.0, ..., 0.3.10] require flarum/core ⁰.1.0-beta.8 -> found flarum/core[v0.1.0-beta.8, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- extiverse/bazaar[0.4.0, ..., 0.4.1] require flarum/core ⁰.1.0-beta.9 -> found flarum/core[v0.1.0-beta.9, ..., v0.1.0-beta.16] but it does not match your minimum-stability.
- Root composer.json requires extiverse/bazaar * -> satisfiable by extiverse/bazaar[0.1.0, ..., 0.4.1]._

If there's anything I might try to be able to update, I would welcome the help. Thank you so much!

SychO

Kennon1st However, it seems that I can't remove any of my plugins before attempting the update. When I deactivate them in the admin panel and then click remove, I get a "Please Wait" message and then go back to the panel and still see the plugin.

Clicking uninstall in the extension page doesn't actually remove it, it only deletes all the data related to it. You have to run composer remove vendor/package, for example to remove extiverse/bazaar you have to run composer remove extiverse/bazaar.

Only after properly removing them can you move forward.

Kennon1st

Ah perfect! That's what I get for bein an amateur!

Thanks! I'll give that a try now and see how it goes.

SychO

Kennon1st well not really, we're planning on making that button communicate more clearly what it actually does, so this just proves it needs improving : )

Kennon1st

Oh snap. Still having some trouble. Probably due to my unfamiliarity with Composer and the update process. When trying to remove any of the third party extensions like fof/polls, I get the following response, largely referencing locks and minimum-stability.

_Problem 1
- flarum/approval is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 2
- flarum/auth-facebook is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 3
- flarum/auth-github is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 4
- flarum/auth-twitter is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the updatecommand.
Problem 5
- flarum/bbcode is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 6
- flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 7
- flarum/emoji is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 8
- flarum/flags is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 9
- flarum/lang-english is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the updatecommand.
Problem 10
- flarum/likes is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 11
- flarum/lock is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 12
- flarum/markdown is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 13
- flarum/mentions is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 14
- flarum/pusher is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 15
- flarum/statistics is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 16
- flarum/sticky is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 17
- flarum/subscriptions is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 18
- flarum/suspend is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 19
- flarum/tags is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 20
- extiverse/bazaar is locked to version 0.4.1 and an update of this package was not requested.
- extiverse/bazaar 0.4.1 requires flarum/core ⁰.1.0-beta.9 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 21
- fof/reactions is locked to version 0.2.4 and an update of this package was not requested.
- fof/reactions 0.2.4 requires flarum/core ⁰.1.0-beta.9 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 22
- antoinefr/flarum-ext-online is locked to version 0.4.0 and an update of this package was not requested.
- antoinefr/flarum-ext-online 0.4.0 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 23
- clarkwinkelmann/flarum-ext-circle-groups is locked to version 0.2.1 and an update of this package was not requested.
- clarkwinkelmann/flarum-ext-circle-groups 0.2.1 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 24
- reflar/level-ranks is locked to version 1.2.1 and an update of this package was not requested.
- reflar/level-ranks 1.2.1 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 25
- fof/merge-discussions is locked to version 0.3.3 and an update of this package was not requested.
- fof/merge-discussions 0.3.3 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 26
- fof/split is locked to version 0.4.3 and an update of this package was not requested.
- fof/split 0.4.3 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 27
- fof/links is locked to version 0.2.1 and an update of this package was not requested.
- fof/links 0.2.1 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 28
- fof/spamblock is locked to version 0.2.1 and an update of this package was not requested.
- fof/spamblock 0.2.1 requires flarum/core ⁰.1.0-beta-8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 29
- kilowhat/flarum-ext-wordpress is locked to version 1.3.3 and an update of this package was not requested.
- kilowhat/flarum-ext-wordpress 1.3.3 requires flarum/core >=0.1.0-beta.12 <0.1.0-beta.13 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 30
- veroz1/users-list is locked to version 0.1.3 and an update of this package was not requested.
- veroz1/users-list 0.1.3 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.
Problem 31
- fof/profile-image-crop is locked to version 0.1.1 and an update of this package was not requested.
- fof/profile-image-crop 0.1.1 requires flarum/core ⁰.1.0-beta.8 -> flarum/core is fixed to v0.1.0-beta.12 (lock file version) by a partial update but that version is rejected by your minimum-stability. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Removal failed, reverting ./composer.json to its original content.
Removal failed, fof/polls is still present, it may be required by another package. See composer why fof_/polls.

SychO

Kennon1st oh yeah, checkout https://docs.flarum.org/update.html#major-version-update-guides instead, and when you do step 2, remember to also remove third extension party entries from composer.json (as well as flarum/auth packages, flarum/auth-github, flarum/auth-twitter, flarum/auth-facebook)

[deleted]

SychO it's probably worth pointing out that fof/oauth replaces the previously individual oauth extensions..

Kennon1st

Awesome! Totally managed to get it now!

Now if only I can figure out how to correctly format the Extiverse repository entry. Help on that would be wildly appreciated as well, if possible.

{
"name": "flarum/flarum",
"description": "Delightfully simple forum software.",
"type": "project",
"keywords": ["forum", "discussion"],
"homepage": "https://flarum.org/",
"license": "MIT",
"authors": [{
"name": "Franz Liedke",
"email": "franz@develophp.org"
}, {
"name": "Daniel Klabbers",
"email": "daniel@klabbers.email",
"homepage": "https://luceos.com"
}, {
"name": "David Sevilla Martin",
"email": "me+flarum@datitisev.me",
"homepage": "https://datitisev.me"
}, {
"name": "Clark Winkelmann",
"email": "clark.winkelmann@gmail.com",
"homepage": "https://clarkwinkelmann.com"
}, {
"name": "Matthew Kilgore",
"email": "matthew@kilgore.dev"
}],
"support": {
"issues": "https://github.com/flarum/core/issues",
"source": "https://github.com/flarum/flarum",
"docs": "https://flarum.org/docs/"
},
"require": {
"flarum/approval": "",
"flarum/bbcode": "",
"flarum/core": "¹.0",
"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": "*"
},
"config": {
"preferred-install": "dist",
"sort-packages": true
},
"prefer-stable": true,
"repositories": {
"extiverse": {
"type": "composer",
"url": "https://extiverse.com/composer/"
}
]
}
}
}
}

}
}

SychO

Kennon1st I'm not familiar with that, what was it added for ? I don't think it's relevant anymore

[deleted]

SychO It's added for downloading premium extensions. If you don't have any subscriptions to those, you won't need it

SychO

[deleted] ah that makes sense, I don't think it needs updating then.

luceos

That entry was used by bazaar too to retrieve more information than packagist provides. It's no longer necessary unless you have active subscriptions to premium extensions.

Kennon1st

Yes, there is one premium extension that I'd like to keep using (Wordpress Comments).

luceos

Kennon1st what is your status now? If you're stuck feel free to dm me your composer.json file on discord.