bug report #161

I was wondering why, http://modxcms.com/bugs/task/161 has been considered complete, the error still exists and it still loops through the javascript errors in modx 9.5.

Please report your MODx version also.

Garry, you’ll need to report your issues in the tracker for them to be followed up upon. The folks in the thread will be notified and Garry (likely) will jump on it quickly.

I did submit a bug report, I was just opening a topic to discuss it, Cuz the bug tracker says the bug is gone, but it still exists in the current stable. I was just wondering what happend, was it just forgotten when 9.5 was compiled?

It seems that only a portion of the bug was resolved. Please use the bugtracker to follow up on it; it will (with almost 100% certainty) get lost in a forum with thousands of posts per month. Thanks.

yeah, should I reference the partially complete bug traker entry #161?

If that’s the one that’s not totally complete, then yes. If it is, then state it can be closed out and open a new bug (I reverted the progress based on this thread).