huuduy216 you can remove the extensions from composer.json before running composer update.

But unless those are extension you decided to no longer use, it's best to wait until all your extension are beta14-compatible before making the update. That way you don't need to remove them.

It's still a good idea to just disable them for the update.

I just updated while watching YouTube on my couch with an iPhone. That’s how easy it is. 😜

I’m crazy though and removed all but core extensions. I shall slowly add some back as they are compatible.

My development environment was updated successfully without any problems. Awesome!

Next step is to go through and verify when all of the extensions I have installed are updated for beta 14.

Awesome jobs team! Keep up the phenomenal work!!

Hari Actually, not yet. Generally speaking we try to get discuss upgraded as early as we can, but we're still waiting on a few of the extensions we use to be updated. Soon though.

clarkwinkelmann
I could, but I don't own an iPhone 😀.
Users of our board want to try and see it themselves if it works. They are suspicious somehow. 😅

Oh, and I will of course install it locally when I am back from holidays.

ok after the update i discovered some of the extensions are no longer compatable with flarum, i hope to get the updates for some of my favorite extensions. Thanks and Cheers:::

    KolaBilewu after the update i discovered some of the extensions are no longer compatable with flarum

    Please remember to read the full announcement, we're very explicit about this release breaking extensions that haven't been updated yet.

    Awesome job! I'm trying migrate my forum to beta 14, just upgraded to beta 13 last month.
    I did a lot of customization for my forum, forked the core repo and checkout a new branch to apply the modification. Hope to keep up with the mainline updates.