The Future of Flarum in 2023: Balancing Open Source and Success

luceos

tolgaaaltas your feedback is very much appreciated Tolga. In fact I was hoping to iterate over the frontpage design once the migration is done. The biggest hurdle with this migration is/was actually merging three different websites (and respective stacks) into one. Once the site is stable I'll have the site given a rigorous visual revisit, your feedback can then be included as an important part of that 👍️

luceos

This morning I initiated the first step of this migration that leads towards one unified portal for Flarum.

Extiverse was put into read only mode and all data was migrated over into the new application. In addition the new website (previously next.flarum.org) was published under our main domain https://flarum.org. I discovered several minor issues, among other non functional email, that were fixed throughout the day.

Tomorrow account features will be re-enabled on the website, so that Extiverse features can be used from within Flarum.org. I will continue to be as close to my desk as much as possible. In case you encounter any issues with the new website, any of your premium extensions or subscriptions, do let me know here or through my email address in my profile.

luceos

Registrations and log ins are now enabled on https://flarum.org. The biggest issues are now resolved; I've tested the functionality of using the new composer endpoint and using tokens.

Updating from Extiverse

Log in on https://flarum.org using your extiverse credentials
create a new token at: https://flarum.org/dashboard/subscriptions and follow the instructions, including
- set the new token
- set the new repository
remove the old repository from your composer.json:

composer config --unset repositories.extiverse

test the token by running composer update if composer mentions an extension is installed but not found in remote repositories, your configuration failed, get help here or reach out to me personally (see profile)

Please, if you encounter any issues at all. Feel free to report them here or privately.

This new website is a starting point for many countless iterations, the hosting plans currently are disabled so that I can take the time to go over that configuration with due diligence later.

Thanks everyone for your patience so far 🤗

JakeMcCarroll

luceos i cant verify my email; the link gives a 403: invalid signature

luceos

JakeMcCarroll on it, thank you 👍️

JakeMcCarroll

JakeMcCarroll the link gives a 403: invalid signature

luceos the other pages give me a 403: forbidden despite being logged in; is this due to not being verified or?

ganesh

Do we support multi-tenant? @luceos

treyb

luceos I get a 500 Error at https://flarum.org/dashboard/subscriptions after accepting the TaCs.

ernestdefoe

treyb yeah I was about to post about the same thing.

luceos

So I fixed the email verification 403 error. But while I tried deploying another update to fix the subscriptions page 500 error I ran into some trouble from switching Extiverse over to Flarum.org in our composer files. I'm working on it though. My apologies for the inconvenience.

Edit: so.. it now deployed properly the subscriptions page issue should have been resolved.

treyb

luceos I am still getting 500 Error when I hit Continue after accepting the TaCs.

jslirola

I opened an extension I had purchased on Extiverse, then clicked the "subscribed" or "view subscriptions" button and received another 500 error, link: https://flarum.org/premium/subscriptions

XdGoldenTiger

Yep, having the same issue everyone else is having. 500 error

luceos

Yeah confirmed, investigating.

treyb

luceos Mine is working now, I created a token and ran the two commands in Composer.

Testing now on the update to composer.

Edit: No error when running composer update

luceos

Yeah deployments are now finally moving forward again, the subscriptions page issue should be gone. @GreXXL mentioned an issue with the manage team page being 403 forbidden. Checking that now.

luceos

I'm calling it a day. I've fixed the issue with the team manage page. I still have quite a number of issues that I've put into our project planner, which I'll pick during the rest of the week.

If you encounter anything, feel free to let me know.

hongaar

I'm still running into the 403: INVALID SIGNATURE. error when clicking on the Verify Email Address button in the e-mail I received.

luceos

hongaar this should now be fixed. It seems even marking Cloudflare as valid proxy in Laravel, didn't suffice to make it think it is being requested through https. This then caused the signature of email verification to fail.

I have opened an issue tracker for the new website, so that things remain a bit more transparent: github.com/flarum-com/flarum-org, although we - as Flarum BV - also have an internal project management tool I assumed it would be great seeing what is reported and resolved publicly in an orderly fashion 🙈

hongaar

Thanks luceos for your swift response. The error is still there for me, I've posted additional details on the GitHub issue: flarum-com/flarum-orgissues/2.

« Previous Page Next Page »