BinarMorker / TimeWastedOnDestiny

http://wastedondestiny.com
GNU General Public License v3.0
23 stars 3 forks source link

Site does not load when browsing directly to the profile url #43

Closed corsairmarks closed 7 years ago

corsairmarks commented 7 years ago

I was onlyable to get the site to load properly in Chrome. Once it found my gamertag (NikoRedux) it redirected me to a url associated with my Bungie profile (I assume you do a reverse lookup of some kind here).

The search results are at https://www.wastedondestiny.com/search/corsairmarks but browsing to that url directly (even in Chrome) results in a page that infinitely spins.

Here's the stack trace (from Chrome):

application.js:165 Uncaught TypeError: Cannot read property 'forEach' of null
    at Application.self.populateAccounts (application.js:165)
    at application.js:146
    at XMLHttpRequest.Request.request.onload (request.js:21)
Application.self.populateAccounts @ application.js:165
(anonymous) @ application.js:146
Request.request.onload @ request.js:21
XMLHttpRequest.send (async)
Request @ request.js:44
(anonymous) @ application.js:141
Application.self.fetchAccounts @ application.js:138
Application @ application.js:247
(anonymous) @ corsairmarks:281
execCb @ require.js:1696
check @ require.js:883
(anonymous) @ require.js:1139
(anonymous) @ require.js:134
(anonymous) @ require.js:1189
each @ require.js:59
emit @ require.js:1188
check @ require.js:938
(anonymous) @ require.js:1139
(anonymous) @ require.js:134
(anonymous) @ require.js:1189
each @ require.js:59
emit @ require.js:1188
check @ require.js:938
enable @ require.js:1176
init @ require.js:788
(anonymous) @ require.js:982
(anonymous) @ require.js:134
(anonymous) @ require.js:1189
each @ require.js:59
emit @ require.js:1188
check @ require.js:938
enable @ require.js:1176
init @ require.js:788
(anonymous) @ require.js:1014
(anonymous) @ require.js:134
text.get.accept @ json.js:37
xhr.onreadystatechange @ text.js:284
XMLHttpRequest.send (async)
text.get @ text.js:288
load @ json.js:32
(anonymous) @ require.js:1095
(anonymous) @ require.js:134
on @ require.js:517
callPlugin @ require.js:955
fetch @ require.js:824
check @ require.js:856
enable @ require.js:1176
(anonymous) @ require.js:999
(anonymous) @ require.js:134
(anonymous) @ require.js:1189
each @ require.js:59
emit @ require.js:1188
check @ require.js:938
(anonymous) @ require.js:1139
(anonymous) @ require.js:134
(anonymous) @ require.js:1189
each @ require.js:59
emit @ require.js:1188
check @ require.js:938
enable @ require.js:1176
init @ require.js:788
callGetModule @ require.js:1203
completeLoad @ require.js:1590
onScriptLoad @ require.js:1717
BinarMorker commented 7 years ago

The issue resides in the fact that the wrong username is put in the URL. Instead of nikoredux, corsairmarks shows but is not searchable. I will look into a solution.

corsairmarks commented 7 years ago

Great work. I wasn't sure if #42 was the same root cause, so I posted two issues. Thanks!

BinarMorker commented 7 years ago

I fixed the issue in my last release. Please search your username again and close this issue if it is resolved.