[Bug] Threads not displaying once inside said thread.

Kira Onime·9/26/2013, 10:22:42 PM·4 votes·729 views

I can see the thread in the community page.

These 2 however do not display.

The 1st one simply shows me a blank page. http://gyazo.com/8876fe4cddcaf3619bfadde925db5bab http://community.na.leagueoflegends.com/c/beta-feedback/2of0Eenx-my-updates-include-my-comments-on-my-own-posts

EDIT: Viewing the source code of the first link, one can find the content of the post body and everything with it. http://gyazo.com/707f8e70f25f4a42433cf20d96ae5f5c

EDIT2: I could be entirely wrong but viewing chrome error console yields an error from one of the js files. http://gyazo.com/366d20deb70cc87013b50afe86f83b73

This one gives me an error that the website is down, even tho it clearly isn't. Refreshing the page does nothing and notice the URL where the title should be, it isn't. I'm going with a wild guess and say it's the asian*?* characters. http://gyazo.com/1096c9ce194b575f12e8857f83d34d9f http://community.na.leagueoflegends.com/c/fancreations/Ox3f53Ey-

EDIT: Ok so for this one, the system doesn't seem to like asian symbols. Opening that tab and then copy/pasting symbols into the URL will send you to the discussion. Could be the collation in the database but I have no idea. http://gyazo.com/db432bc5be6475bc351483b1d798a330

4 Comments

Pryotra9/27/2013, 12:04:48 AM1 votes

I'm getting this, too. If I find any more instances I will post here.

Lot9/27/2013, 12:43:05 AM1 votes

Same here.

RiotKrylhos9/27/2013, 9:12:11 PM1 votes

Thanks for pointing this out!

For those who were curious - here's what went down:

First post http://community.na.leagueoflegends.com/c/beta-feedback/2of0Eenx-my-updates-include-my-comments-on-my-own-posts seems to have had some issues with uploading attachments, and only part of the data made it, the attachment URL reference did not, which caused a severe JS error.

The second post was indeed due to the templating engine attempting to lowercase asian symbols, which then threw off routing.

Both of these issues will be resolved in the update going out later this afternoon.