Dev Diary: Beta 14

tankerkiller125

meetdilip Our only guidelines/rules for naming Betas so far has been animals from Australia (to honor the softwares roots). And nothing political.

Audaxian

tankerkiller125 You've just done F. G is next, so it surely has to be Goanna 😛. You can then also have a theme tune for Beta 14 (a bit of classic Aussie rock):

luceos

tankerkiller125 animals from Australia

Not animals necessarily. What type of animal is New Holland 😜

jordanjay29

luceos a very strange beast that can no longer be found in the wild. 😉

tankerkiller125

luceos Wasn't around for that release so I don't remember it XD

meetdilip

I will reserve " Kangaroo " for 1.0 .

jordanjay29

meetdilip I'm glad you understand the importance of the kangaroo. 😉

askvortsov

Kangaroo

Pirat

luceos Is it possible to update the design in version 14?

askvortsov

Pirat As of right now, there are no plans for major design changes to Flarum for beta 14. Most of the planned work is focused around architecture changes which will increase Flarum's long term stability.

However, Flarum excels in its extensibility, and it's possible to use a custom extension, as well as custom CSS, to make your own design. 2 examples of innovative design changes with Flarum out of many are:
https://www.devnl.nl/
https://community.giffgaff.com/tags

HisAl

luceos
Is there any plan to fix the redirection issue or lack thereof, when loading a page that requires authentication?
Right now if one tries to access a page that requires to be signed in, the person gets "The page you requested could not be found." instead of redirecting to the login page and then redirecting the person back to the page requested after authentication.

This leads to a lot of confusion from users... many who do not know they need to authenticate just think the page doesn't exit due to error... this is NOT a good user experience.

Any idea when this will be implemented?

clarkwinkelmann

HisAl the first step would be to check whether a GitHub issue exists for this, and create one if necessary.

kalinjul

HisAl Looks like this issue: flarum/core654

tankerkiller125

Mini update from me, I've created a PR (flarum/core2159) to fix the "SameSite Cookie" alert that browsers now show when cookies to explicitly set the SameSite value for cookies. I've also been reviewing PRs when I have time as things have been busier with the warmer weather (yard work).

luceos

The past days I have been:

Reviewing more PR's than usual. The pace of the core team is just amazing 😍
Started on the overhaul for the flarum.org website, so that it is ready for the stable release.

Regular work and family life have been pulling me away from doing extensive core contributions.

TOWUK_ru

maybe update the fonts? there is almost 6 version coming out! 🙂

Links: 5 version | 6 version

luceos

TOWUK_ru that's absolutely true. Having a way for people to update font-awesome more easily would be great too. Currently we're locked due to using the dependency components/font-awesome, if they don't update to reflect the latest versions, we can't either.

My apologies for the silence these past few weeks. Although I haven't been in touch much, we have been plowing through many issues and pull requests. I've seen immense dedication to get changes tested and merged as soon as possible.

We still have several weeks to go before our beta 14 release deadline, so please bear with us. The next release contains changes to the frontend, more specifically a Mithril upgrade and the implementation of Typescript.

matteocontrini

luceos and the implementation of Typescript.

Is that proceeding well? It must be an enormous effort.

TOWUK_ru

luceos great and awesone! i wait this! 🎊

tankerkiller125

matteocontrini there are several major changes to the existing JS implementations that needs merged first so that we can upgrade to Mithril 2 and Typescript easier. Because of how big these changes are the PR process is a bit on the slower side but still progressing pretty well from what I've seen.