technical issue Site hangs after replying to Status Updates

[Splashee 28,537]

Back in May 2022 after the forum upgrade, replying to statuses would sometimes hang the site, and after pressing F5 (refresh), the reply would in fact be there.

But what is causing this situation? It turns out that there are an error (actually 2) in the JavaScript code that stops the execution:

Spoiler

It's a screen shot from Firefox browser, truncated some. Quite easy to replicate by just replying to status updates.

I think the main error is:

Quote

Uncaught TypeError: ips.ui.editor.getObj(...) is undefined
    addToStatusFeed mlpforums.com/uploads/javascript_core/front_front_statuses.js?v=6c16238e661673765013:4

 

 

Might have to do with the front page's status feed, which shouldn't show replies in the first place. This bug might be difficult to track down.

 

EDIT: This method is not accurate in tracking down the bug. The errors are most likely unrelated.

[Silly Druid 6,138]

I can confirm this bug occurs to me.

[Splashee 28,537]

So the browser's Web Developer Tools do break on errors, but when the page hangs, it is not stopped because of errors. There are errors like "Uncaught ReferenceError: jQuery is not defined" on every page load, but that doesn't break the site.

This bug seems to happen if you go to a status from a notification link, and reply to it from there. It doesn't happen if replied to a status that has been loaded in the activity tab. The page freezes probably waiting for something indefinitely, like a callback or promise response.

 

So to cause the error, you could just reply to this status following this link:
https://mlpforums.com/profile/45383-splashee/?status=1067576&type=status

And it did:

 

 

[Rikifive 23,488]

Apparently it is a known bug in this forum software (?)

https://invisioncommunity.com/forums/topic/467928-controllers-can-be-initialized-on-detatched-dom-nodes-if-another-controller-uses-cleancontentsof/

Or at least some other forums seem to face the same issue after one of the past updates.

So chances are it's not our problem, but Invision's.

[Splashee 28,537]

The best cause of action would be to wait until we install the latest forum upgrade. Trying to fix this bug by ourselves would probably (most likely) create more bugs in the future.

[Jeric 46,834]

16 hours ago, Rikifive said:

Apparently it is a known bug in this forum software (?)

https://invisioncommunity.com/forums/topic/467928-controllers-can-be-initialized-on-detatched-dom-nodes-if-another-controller-uses-cleancontentsof/

Or at least some other forums seem to face the same issue after one of the past updates.

So chances are it's not our problem, but Invision's.