should we wait for extensions tests? maybe some of them are incompatible with new version?
masihdindar most should be fine honestly 😉 So do try the upgrade and if you encounter issues with extensions, respectfully report them to the maintainer. That would be a huge help to them.
Thanks, just updated, all went well, all seems fine 👍🏻 Really appreciate your continuing efforts 👏🏻
luceos Rel and target attributes on links can now be modified using extensions
Is there an extension for that already?
CyberGene Is there an extension for that already?
Yeah: luceos/flarum-ext-dofollow, it's like a proof of concept. It has hardcoded defaults though.
Just put echidna online, thank you all.
i18n tag slug no longer crashes, but still prompts an exception.
I will raise it in the support tag.
I want to remove rel="ugc noopener" on the external links too. Is this possible?
kishor yes. For now using a local extender would be easiest. If you create a support discussion I can give an example for that there when I'm fully awake.
luceos Please reply this discussion
Just updated to 1.4. Not an obviuos fact, but sense - Flarum is continuously becoming more convenient, reliable and smooth. Thanks, team!
Hello, it was nice sharing. It was said that there will be an update from the panel in the 1.4 version, I think this option did not come with this version, I would like to thank everyone who supported all the support.
eSozluk if it's not in this version, it will be in the next. We don't restrict ourselves to certain features per release as this could cause immense delays to such release in case the feature isn't finished.
luceos Thank you, I look forward to it, I wish you success
Update worked perfect.
No errors so far and the extensions seem to work as before. 👍️
Update worked like a charm. Best open source forum software imo hands down.
I updated to 1.4.0, it seems work perfectly untill I scan it on https://lab.migratetoflarum.com, it through a ton of errors as below
It was scored an A with 1.3.1 version.
This is due to changes made between v1.3.1 and v1.4 which seem to have affected @clarkwinkelmann's tool. This is most likely the separation of the API payload from the main JS content.
I think "clarkwinkelmann" has fixed it.
I get the same result in 1.4, it's no different with 1.31
Yes, he just announced about this fixing not so long ago at https://discuss.flarum.org/d/10056-migratetoflarum-lab-the-health-scanner-for-flarum/229. Thank you for all hard work that Clarkwinkelmann and the team are doing so far for the community.
You all know what I think about Flarum itself: greatest advantage of flarum is that its source code is on MIT.
Soemone must have put huge amount of work into flarum: thats for sure. Still needs lots of work though.
1.4 and still no proper PWA? @luceos seriously? Same bugs that existed in 1.3 PWA are still not fixed in 1.4 PWA.
CyberGene we discovered an issue with that yes. The new, more scalable solution to setting the post number has this effect. I'm on mobile so I cannot find the issue for it.
Edit, here it is
anonymousDev pwa is a community extension, these are not the responsibility of the core team.