Double double posts posts... 📨 📬️ ✉️ 📫️

thunderdragon

Hi everyone! 😇
Almost every time I try to load older threads on any part of Community, I always find myself seeing something like this…

Clearly this is to do with either the scripts on the page loading the same resource multiple times, or (More likely) the scripts aren’t interfacing with the DOM correctly. 🐛
In either case it makes trying to retrieve and access any topic that doesn’t appear on the first page extremely difficult and time-consuming, if not outwardly impossible. 🙁

I imagine this is a known issue already - I’ve seen it in others screen grabs, I think - But will there ever be a decent solution delivered for it? Preferably one that involves moving all of the essential service code serverside and not relying on the Internet-bane that is jQuery and AJAX? 💡
+++ 🚄 ThunderDragon 🤘 +++

mrjeeves

thunderdragon

Reported reported many many times times 😉

Nothing can be done about it until Flarum’s core is fixed, sadly.

I haven’t looked to see if it got fixed, but this sort of fix is already present in some situations, so fingers crossed it isn’t too long until a fix is made.

The issue is a combination of client and server. The fix is for the client to send the ID of the last thread in the list, and the server starts sending data from that thread onwards. For now, it just starts from the number of the last viewed, so if a new thread is made, all the existing threads get bumped down by 1 or more.

frenchielove

thunderdragon blinking annoying isn’t it? Same on my ipad

bluenose55

thunderdragon I see the same after a few 🍺🍷👍

dez_d

thunderdragon I know this can be frustrating and I do experience the exact same thing myself.

If I need to go past page one then I use some additional code to force page 2 , page 3, etc

This piece of code added to the URL can be added to any forum/subtag which allows you to force the page, just change 80 to the page you want, ?page=80

Kudos to sloz for the tip.

tankerkiller125

mrjeeves thunderdragon This issue was resolved in https://github.com/flarum/core/pull/2322 which I believe made it into the beta 14 release of Flarum. If it didn’t make it to beta 14 it will for sure be in beta 15 which has an expected release sometime before Christmas.

mij_sky

thunderdragon glitch it will get sorted

thunderdragon

dez_d This piece of code added to the URL can be added to any forum/subtag which allows you to force the page, just change 80 to the page you want, ?page=80

Awesome! Cheers for passing on the tip dez_d! 🙂

When it comes to interpreting page, does that refer to page of threads as they stand in the DB at point of request? If so, then pulling a few pages from the server and holding them locally could avoid the issue, given the content of each page will change as other users respond to threads otherwise. 📜 👍️

tankerkiller125 This issue was resolved in https://github.com/flarum/core/pull/2322 which I believe made it into the beta 14 release of Flarum. If it didn’t make it to beta 14 it will for sure be in beta 15 which has an expected release sometime before Christmas.

Nice spot there, tankerkiller125! Perhaps giffgaff need to consider updating the community software, given git exists to make these upgrades a quick and easy process. What version of Flarum is giffgaff running, as a matter of curiosity? 😇
+++ 🚄 ThunderDragon 🤘 +++

mrjeeves

tankerkiller125

Good spot 😉

tankerkiller125

mrjeeves After further review of the commits I can confirm that it made it into at least beta 14.1 of Flarum 🙂

tankerkiller125

thunderdragon Perhaps giffgaff need to consider updating the community software, given git exists to make these upgrades a quick and easy process.

Flarum uses composer to handle dependencies and other things, upgrading to beta 14 is not as easy as you might think as beta 14 was a total re-write of the front-end to Mithril 2.0 (the JS framework) meaning that all extensions both Flarum community and giffgaff custom, must be updated before they can update the forums.

To get an idea of how complex it is in the real world the official Flarum community itself has not yet updated to beta 14 due to some of the extensions used not being updated yet.

The good news however is that beta 14 is the last super major breaking update before stable (or at least that’s the plan) so once giffgaff does get upgraded it should be easier for the giffgaff team to upgrade to other versions.