Flarum 0.1.0-beta.10 Released

amdad

W w w a t c h out! ~~_ _ I M P E R I U M _ _~~ in the making . . .

KimYunz

ah goood amazing ones!

dexif

If you click on the previous message "1 post was split to You're going a little too quickly.", you will receive the error message “The requested resource was not found.” Then press f5. Then you can’t go back using the browser "Back" button

luceos

dexif the author deleted his post, as this post was the first of the discussion and no other posts are contained in it, it cannot be shown (to regular members).

Tall

Hi,

I'm planning to upgrade tot beta 10 but was curious if any special actions have to be done if you have setup like described in

https://flarum.org/docs/install.html#customizing-paths

For example, manual steps by copy the asset folder public_html folder.

Cheers.

jordanjay29

Tall Nothing needs to change with the skeleton files (anything outside of vendor), nope. You should expect the upgrade to work cleanly and without need for fixing anything before/after.

That said, it's always wise to backup your database, assets(/avatars) folder, composer.json and composer.lock files.

Tall

jordanjay29

Sure, I always make a full backup before upgrading 🙂

Thanks for clearing things up!

Tall

Upgrade went smooth, running on beta 10 now. Thanks guys for your great work 🙂 Keep it up.

dexif

Sometimes I see -1 on notification icon 😉

010101

dexif I think that’s my fault. I’ll take the blame. I’m making this guess because I see my post in your notifications in that screenshot. Yesterday, I went to post in my PWA thread and I got an error. So I posted again. Got an error. And so I posted one more time. Come to find out, it posted my post despite the error, 3 times. So, I deleted two of the duplicate posts.

Because of all of that weirdness, I think it made your notifications -1.

Also, if you look at my PWA thread, it says Brian was the last reply when in reality, I was.

I think it has to do with Halloween. 🎃

datitisev

010101 This more likely has to do with the email issues on discuss that have now been resolved. Discussion metadata wasn't being updated after posting because of the error.

tankerkiller125

datitisev Shouldn't email related things be in a try/catch block to prevent end users from seeing errors when their post actually gets displayed properly? I feel like anything that queries an external service that may/may not be reliable should be in a try/catch block to prevent these kinds of issues.

Franz

tankerkiller125 Even better, we're moving this kind of stuff into background workers that take tasks out of a queue, which not only helps with errors (when things can be safely retried), but also makes things faster even when all things go as expected (e.g. when lots of people are subscribed to one discussion).

tankerkiller125

Franz Perfect! I use Queues a LOT when I build laravel applications for this exact reason. Hopefully it integrates with the Horizon and Redis extension packages?

luceos

tankerkiller125 I've already created a Redis queue package, it's installed on discuss and a staging bokt.nl environment that keeps itself in sync with production phpbb. I've also started with a horizon package but it hasn't been patched for the recent queue changes yet.

mathanhcong

Congratulation!!! 😃

« Previous Page