<![CDATA[Broken Push Notifications]]>Hi community,

I notice that I can not get the newest and unread topic, when I open the form the sort seems not worked as before, I need to changed it manually to NEWEST TO OLDEST. Has anyone else encountered a similar situation？

Cheers~
DunHou

]]>http://developers.maxon.net/forum/topic/16297/broken-push-notificationsRSS for NodeWed, 22 Apr 2026 18:03:50 GMTFri, 18 Jul 2025 03:09:48 GMT60<![CDATA[Reply to Broken Push Notifications on Thu, 11 Sep 2025 07:58:12 GMT]]>Hm, interesting, It works now,

either you did something or the solution is to post a comment to trigger it. Anyway Thanks.
Cheers mogh

]]>http://developers.maxon.net/forum/post/76811http://developers.maxon.net/forum/post/76811Thu, 11 Sep 2025 07:58:12 GMT<![CDATA[Reply to Broken Push Notifications on Wed, 10 Sep 2025 15:33:18 GMT]]>Hey @mogh,

without details from your console, this is hard to answer. The dangling sessions are well known NodeBB problem and the NodeBB team has never fully addressed it. The general consensus is that this is caused by NodeBB locking onto outdated service workers, which when you have still the site open while doing so, might even survive a cache reset.

What I would do:

  1. Check if the problem exists on multiple devices and/or browsers.
  2. Log out.
  3. Close developers.maxon.net.
  4. Remove the whole cache of developers.maxon.net.

When this does not help, I would have to see your console output to see if there are any errors being raised.

Cheers,
Ferdinand

]]>http://developers.maxon.net/forum/post/76806http://developers.maxon.net/forum/post/76806Wed, 10 Sep 2025 15:33:18 GMT<![CDATA[Reply to Broken Push Notifications on Mon, 08 Sep 2025 06:11:17 GMT]]>I still have the same problem. "No push" no "unread toppics". Clearing my Browser Chache does nothing.

any idea ?
cheers mogh

]]>http://developers.maxon.net/forum/post/76801http://developers.maxon.net/forum/post/76801Mon, 08 Sep 2025 06:11:17 GMT<![CDATA[Reply to Broken Push Notifications on Fri, 18 Jul 2025 16:37:32 GMT]]>Hey @Dunhou,

thank you for reporting this. I took the liberty of shortening your posting a bit to make it more suitable for a service note read by everyone. This has nothing to do with your chosen browser but with the service worker stored in the cache of your browser (that it worked in one browser for you was probably caused by the fact that you did not had a stored valid session there). The user account rollback we recently carried out changed the signature of the NodeBB instance, and with that broke all service workers that were registered before the rollback.

I should have foreseen that and communicated it; but I did not, mea culpa. The service workers will be updated automatically when your browser cache is cleared (by default after 24 hours on our site, but there are multiple factors that can influence this). But you can fix this yourself by forcibly clearing the cache of your browser. For most browsers, this can be done by pressing Ctrl + Shift + R (or Cmd + Shift + R on macOS), or by pressing Ctrl + F5 (or Cmd + F5 on macOS) to reload the page without using the cache.

Impacted by this will be all user bound data such as notifications, private messages, presets, and the 'unread' status of topics. I will leave up the warning on site for a while, so that all users are informed.

Cheers,
Ferdinand

]]>http://developers.maxon.net/forum/post/76707http://developers.maxon.net/forum/post/76707Fri, 18 Jul 2025 16:37:32 GMT