Issues with the Floxum extension store

treyb

I understand the need for the change, but Floxum is currently returning 500 and 403 errors at https://floxum.com/settings and https://floxum.com/managed-communities respectively.

I am in the middle of migrating hosts this weekend and have been experiencing issues with my Flarum transfers and this explains why. When attempting to use the Floxum composer repository at https://floxum.com/composer, packages such as kilowhat/flarum-ext-custom-paths, kilowhat/flarum-ext-formulaire, and kilowhat/flarum-ext-rich-embeds are not resolving from remote repositories, which I believe is a direct result of these errors.

Hoping this gets resolved soon as it is blocking my migration.

Edit: If anyone is also having a similar situation, running this on your prior server will return the token to add to the new one. composer config bearer.flarum.org

KBExit

treyb I haven't had any issues with directly changing auth.json for all of my client sites and composer updates worked fine. 🤔
Unless these issues are happening after the fact.

rafaucau

I migrated the configuration to Floxum, and there is no reference to flarum.org anywhere in my composer.json and auth.json. It worked initially, but I noticed that the deployment fails even though it works locally. It only worked because of the cache. After running composer clear-cache, it stopped working.

Error: The "https://flarum.org/composer/archive/blomstra/realtime/0.3.3.0.zip" file could not be downloaded (HTTP/2 404 )

In CurlDownloader.php line 668:

  The "https://flarum.org/composer/archive/blomstra/realtime/0.3.3.0.zip" file could not be downloaded (HTTP/2 404 )

I also removed the vendor directory and composer.lock. It still tries to download blomstra/realtime from flarum.org, so something doesn't seem right on Floxum's side.

KBExit

rafaucau the only thing I changed was auth.json at the header portion prior to the actual token and it all works.
If you had added flarum.org repository with premium extensions before all of this, there should be a record of it.

rafaucau

KBExit That may still work because Composer is still using cached packages. Try removing the vendor directory, running composer clear-cache, and then composer update to confirm that it is really working. Of course, don't do that on a production site.

luceos

Hey everyone,

My apologies for the errors here and there. I'll try to keep up with this thread as I patch things here and there. Things that got fixed:

password reset
subscriptions page
managed communities page
settings page

Do let me know if you run into more issues, you can also do that privately with the email address in my profile.

Thanks for your patience.

luceos

Quick update from my side, I am looking at the composer issue where downloads are still coming from flarum.org, and an issue with the subscriptions page.

luceos

Composer now works again. A full re-index of extensions was necessary to cache new json files that composer uses to identify the download tarball link of the specific version.

I am diving onto the other issues reported to me, thank you again for your patience.