@JaredBusch said in Currently Open Community Issues:
@Tim_G said in Currently Open Community Issues:
@JaredBusch said in Currently Open Community Issues:
@Tim_G said in Currently Open Community Issues:
Oh I haven't seen this thread.
In reference to: https://mangolassi.it/topic/13346/mangolassi-website-semi-frequent-internal-error
I think I've figured out the main issue...
When clicking on a notification, the notification links to, for example: https://mangolassi.it/post/296273
After that, the browser is supposed to automatically redirect to: https://mangolassi.it/topic/13654/for-the-love-of-ipod/11, which it does in all other browsers and Edge pre-1703 update.
In MS Edge now (post 1703), after you left click a notification, it takes you to the first link, and gives you my original error. When I middle click to open it in a new tab, it works as normal, and redirects to the second link.It gives that error on all Windows 10 1703 devices, on the Edge browser. Pre 1703, the issue does not occur in Edge.
Can you replicate the behavior on another site such as community.nodebb.com?
To make sure it is not an issue with how ML is configured.Waiting on a reply to test it out: https://community.nodebb.org/topic/10690/notifications-test-please-reply/1
replied for you.
Yes, same thing. Left clicking on the notification results in the error message. Middle-clicking (to open it in a new tab) works fine.
Looks like it's a NodeBB programming issue:
0_1494882370813_Untitled.jpg
Same thing... it doesn't redirect to the correct URL after left clicking the notification.