Update to v2.0 from v1.8

Wlork

Hello,

Last night, I tried to migrate my test forum to 2.0 via Extension Manager. The update was completed but broke my forum.

Today, I want to do it via Composer and would like to know if I am doing it correctly. If I haven't skipped any steps.

1- Uninstall all incompatible extensions
2- All extensions that are already compatible with 2.x remain installed and active
3- In composer.json, set flarum/core to ².0
4- In composer.json, set all other extensions to *
5- Run in Composer: composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies
6- Run php flarum migrate and php flarum cache:clear

Is that all ? Do I also need to change the driver in config.php from mysql to mariadb ? I'm asking because I use mariadb, but my configuration on the main forum is still on mysql and it works fine.

Thaank you for your help in advance

GreXXL

Wlork it would be helpful to see what error you are getting?

Wlork

GreXXL it would be helpful to see what error you are getting?

I didn't look, but I couldn't do anything.... I couldn't create a topic, I couldn't reply.... Nothing. Then I installed Byobu, and the forum no longer displayed. It was completely broken.

If the steps are correct, I'll try again later. And if there's an error, I'll let you know 🙂

Wlork

First issue after run 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 flarum/core ^2.0, found flarum/core[v2.0.0-beta.1, ..., 2.x-dev] but it does not match your minimum-stability.
  Problem 2
    - Root composer.json requires datlechin/flarum-copy-links * -> satisfiable by datlechin/flarum-copy-links[v0.1.0, v0.1.1, v1.0.0, v1.0.1].
    - datlechin/flarum-copy-links[v0.1.0, ..., v0.1.1, v1.0.0, ..., v1.0.1] require flarum/core ^1.2 -> found flarum/core[v1.2.0, ..., v1.8.13]but it conflicts with your root composer.json require (^2.0).
  Problem 3
    - Root composer.json requires fof/discussion-templates * -> satisfiable by fof/discussion-templates[1.0.0].
    - fof/discussion-templates 1.0.0 requires flarum/core ^1.8.0 -> found flarum/core[v1.8.0, ..., v1.8.13] but it conflicts with your root composer.json require (^2.0).
  Problem 4
    - Root composer.json requires fof/discussion-views * -> satisfiable by fof/discussion-views[1.0.0].
    - fof/discussion-views 1.0.0 requires flarum/core ^1.8.0 -> found flarum/core[v1.8.0, ..., v1.8.13] but it conflicts with your root composer.json require (^2.0).
  Problem 5
    - datlechin/flarum-link-preview[v0.1.0, ..., v0.2.2, v1.0.0] require flarum/core ^1.2 -> found flarum/core[v1.2.0, ..., v1.8.13] but it conflicts with your root composer.json require (^2.0).
    - datlechin/flarum-link-preview v1.0.1 requires flarum/core ^1.5 -> found flarum/core[v1.5.0, ..., v1.8.13] but it conflicts with your rootcomposer.json require (^2.0).
    - datlechin/flarum-link-preview[v1.1.0, ..., v1.3.3] require flarum/core ^v1.6 -> found flarum/core[v1.6.0, ..., v1.8.13] but it conflicts with your root composer.json require (^2.0).
    - datlechin/flarum-link-preview[v1.4.0, ..., v1.5.0] require flarum/core ^v1.8 -> found flarum/core[v1.8.0, ..., v1.8.13] but it conflicts with your root composer.json require (^2.0).
    - datlechin/flarum-link-preview[v1.6.0, ..., v1.6.1] require flarum/core ^1.8 -> found flarum/core[v1.8.0, ..., v1.8.13] but it conflicts with your root composer.json require (^2.0).
    - Root composer.json requires datlechin/flarum-link-preview * -> satisfiable by datlechin/flarum-link-preview[v0.1.0, ..., v0.2.2, v1.0.0, ..., v1.6.1].

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

GreXXL

Wlork you haven't set the minimum stability to beta in your composer.json

Wlork

GreXXL you haven't set the minimum stability to beta in your composer.json

It work ! Thank you !

And after several tests, my forum doesn't seem to be broken!

Yesterday, I didn't have this step... So the system must have installed the wrong things. I'll continue testing over the next few days to make sure everything is OK.