V0.70 Released

AresMUSH
1

Beta V0.70 is now released with a bunch of fixes and a few new things.

Release Notes.
How to Upgrade (no restart required)

1 Like
2

I have no idea what I did on this one, 'cause everything is fine over in test-server-land, but…

Any idea why it would just take to a dead page when you click on a profile to edit it? It doesn’t give a Sad Picard, just takes you to “https://gray-harbor.com/error?message=” and leaves you staring at an empty page.

My log is full of these errors:

2019-12-16 09:21:58 DEBUG - Handling ConnectionEstablishedEvent.

2019-12-16 09:21:58 INFO - Client connected from XX.XX.XX. ID=4.

at Backburner.join (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73878:19). 

at Backburner._join (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:74161:21)

at Backburner._run (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:74181:16)

at Backburner.end (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73818:12)

at Backburner._end (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:74132:34)

at DeferredActionQueues.flush (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73556:21)

at Queue.flush (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73347:13)

at invokeWithOnError (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73469:9)

at Ember.onerror (https://gray-harbor.com/assets/ares-webportal-416a73f369a416729185c4ee9f745ba7.js:8850:15)

at Class.reportError (https://gray-harbor.com/assets/ares-webportal-416a73f369a416729185c4ee9f745ba7.js:11963:19)

2019-12-16 09:21:54 ERROR - Web client error: Cannot read property ‘next’ of undefined : Error

at Backburner.join (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73878:19). 

at Backburner._join (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:74161:21)

at Backburner._run (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:74181:16)

at Backburner.end (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73818:12)

at Backburner._end (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:74132:34)

at DeferredActionQueues.flush (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73556:21)

at Queue.flush (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73347:13)

at invokeWithOnError (https://gray-harbor.com/assets/vendor-47e156bd798c0d5c1226ec86d31040f1.js:73469:9)

at Ember.onerror (https://gray-harbor.com/assets/ares-webportal-416a73f369a416729185c4ee9f745ba7.js:8850:15)

at Class.reportError (https://gray-harbor.com/assets/ares-webportal-416a73f369a416729185c4ee9f745ba7.js:11963:19)

2019-12-16 09:21:54 ERROR - Web client error: Cannot read property ‘nextSibling’ of null : Error

3

Hmm. I’m not seeing that error on my test server or the demo site.

I checked out your site, and it’s not just happening when editing a profile, but any time you transition away from a profile page to go anywhere else.

That tells me there’s something messed up with the HTML (the DOM, in technical terms) of the profile page itself. The error you’re getting is a generic javascript engine thing, and not anything ares-specific.

Given that I just made a bunch of changes there to add the custom profile stuff, and IIRC you have some custom code changes, my first guess would be that maybe you have a bad merge? You could try comparing your version to master and see if anything looks amiss. If you want, you can also PM me your github fork info and I could take a look.

4

I wound up basically putting everything in the /app/ folder back to vanilla, which fixed whatever it was. File-by-file, I could not for the life of me figure it out.

BUT!

Since I’ve been meaning to do it since I got a new job in October and don’t have the same insane work firewall… this is a good excuse to finally get all this on Github. Coming in 2020.

Thanks for looking at it. :slight_smile:

5

I’m glad it got sorted, though I’m curious what it was. Mystery for the ages I guess :slight_smile: