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

nxmndr

I think it would be nice to be able to override a whole JS class. Currently I am doing

override(Someclass.prototype, 'view', _ => ...)
override(Someclass.prototype, 'oncreate', _ => ...)

Maybe we could have override(Someclass, Myclass) ?

clarkwinkelmann

nxmndr the more you override, the more likely you break compatibility with other extensions. When using the override helper, you are still supposed to call the original method (both extend and override are ways to monkey-patch, generally not to entirely replace). This cannot be done when replacing an entire class.

However you could define your own class extending one from Flarum and use it where you need instead of the default.

Which class would you like to completely override ?

nxmndr

clarkwinkelmann This cannot be done when replacing an entire class.

Good point.

clarkwinkelmann use it where you need instead of the default

In this case, Flarum is using it, so I can't do that.

It is WelcomeHero where I put some slider instead of the welcome message.

Up2Vex

will our accounts from here migrate over to next.flarum.org? or would we need to register again

luceos

Up2Vex discuss will remain isolated from flarum.org. So your account on discuss will remain as is. I hope to include the ability to connect your discuss account on the future flarum.org site or perhaps allow logging in on discuss with your flarum.org account. This will require some discussion in the team before any decision and implementation though.

tolgaaaltas

Flarum (Next) Homepage Review

Hi, I visited next.flarum.org and there's my review. It may be helpful. I'm a web designer and want to share my experiences with the Flarum team.

CTAs

There are three CTA buttons in the hero section which is so wrong to me. First of all, these color choices are wrong. It looks like disabled and not clickable, because of the transparent colors.

Three CTA is too much. Usually, we offer two CTA buttons in one section. One of them is for information and the primary one is for conversion.

Discover extensions section

If I were to design this area, I would place the "explore extensions" button larger, just below the title. We read from left to right, it doesn't make sense to put a button to interact with at the far right and bottom.

Benefits

Do we really need a separate page for "Benefits"? I think it can be used quite effectively as a tabbed area.

I hope you guys don't misunderstand, these are just the ones that first caught my eye and the solutions that I quickly came up with as alternatives.

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

I've patched several issues. Email verification now finally works properly again. Working behind several proxies is a true challenge sometimes 😬

tolgaaaltas I've done a little refactor based on your suggestions. Let me know what you think.

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

treyb

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

m4v3rick

luceos

thanks again!

MIKU-N

luceos I always get error with HTTP403,plz see this issue:flarum-com/flarum-org17

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

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

« Previous Page Next Page »