Request #1626533

From: fregimus fregimus L. Fregimus Vacerro
: Account with Professional package of service
LiveJournal: username: fregimus
style: (S2) core:  public,  i18n:  none,  i18nc:  public,  layout:  public,  theme:  public,  user:  custom
userpics: base + loyalty = userpics
sup enabled:
email validated? yes
cluster: Steaksauce (#1); data version : 8
design: new    friends page: friends
language: en_LJ
underage no;
Is JavaScript enabled: yes
Request sent from Beta: 0
Photo hosting migration: done
Support category: Troubleshooting  [previous | next]
Time posted: Sun, 28 Apr 2013 00:10:56 GMT (5 years ago)
Status: closed (10 points to astronewt)
Summary: Error 500 attempting to open someone's journal
Original Request:
There is a friend's journal, user name zemleroi, that I am able to open and read normally provided that I am not logged on to LJ. However, when I log on from the same browser, I am sent to the error 500 page immediately. Obviously, I am getting the same error trying to open it while logged in, by either following a link or typing the address into the browser's address bar. This has not changed since Wednesday.

At least one other user reported that they can see the same journal, and another one reported the same error (http://fregimus.livejournal.com/215959.html?thread=6115479#t6115479). Could you please check what might be wrong on your side of the wire? I tried total 3 different browsers on 2 machines, so it does not look like a problem with cookies or other issue at this end. Thanks!
Diagnostics: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0
markf  - Mark
Answer (#6247601)
Posted Mon, 29 Apr 2013 19:23:36 GMT (5 years ago)
Thank you for your report. LiveJournal was undergoing some intermittent problems at the time, which we believe are now resolved. If you're still seeing this error, you are most likely viewing a cached (locally stored) copy of the page in question. Please see [http://www.livejournal.com/support/faqbrowse.bml?faqid=160] for information on how to clear your browser's cache.
fregimus fregimus  - L. Fregimus Vacerro
Comment (#6247835)
Posted Tue, 30 Apr 2013 02:51:01 GMT (5 years ago)
Nope. That does not help. Tried cleaning the cache in Chrome, using Firefox, tried the Incognito window in Chrome (that is supposed to disable the cache in session), all the same thing. Can view the journal anonymously, but getting the 500 goats as soon as I log on.

Ok, just tried IE9 on another machine that I never used to log on to LJ at all, disabled add-ons, switched to in-private mode. Same thing: can open the journal anonymously, error 500 after a log-on. I'd say the cache is exonerated. Looks quite like something is wrong on your side.

A few people already reported seeing the error 500 opening that particular journal (link in the original question; discussion in Russian, sorry). This is the only journal I could not access while logged-on. Looks weird, doesn't it?
rebelsheart rebelsheart  - Tango, The Wild Dream
Answer (#6248153)
Posted Tue, 30 Apr 2013 11:57:26 GMT (5 years ago)
My apologies. Upon further research, it appears that you are encountering a known issue that does not happen very often. You are using a S2 style for your own journal and generally view other journals in your journal's style. Zemleroi is using an S1 style. Due to a bug currently being investigated by LiveJournal's developers, users who use S2 styles that try to view a journal in an S1 style in their own style receive an Error 500 message. Please see the 'Other Comment Pages' section of this FAQ [http://www.livejournal.com/support/faq/175.html] for how to adjust your settings so you do not automatically view other journals in your journal's style.
fregimus fregimus  - L. Fregimus Vacerro
Comment (#6248681)
Posted Tue, 30 Apr 2013 16:10:26 GMT (5 years ago)
Yes, turning off the option to read other journals in my style helped. Apparently I am hitting the same bug.

Is this bug high enough on the fix list? Is it likely it is going to be fixed in the next release? Can you bump it up? :-)
astronewt astronewt  - astronewt
Answer (#6249069)
Posted Tue, 30 Apr 2013 19:25:26 GMT (5 years ago)
This is not a bug that very many users run into, as not very few active accounts still use the old S1 style system. This means that while the bug is reported and is an open issue, it is a minor issue and is unlikely to receive attention ahead of higher-priority issues. I'm sorry for the inconvenience this causes you.

You may wish to contact the user 'zemleroi' and let them know that some of their viewers are encountering this trouble -- they may not have any particular affinity for their current S1 style and may be willing to switch to an S2 style to fix this issue for their viewers.
fregimus fregimus  - L. Fregimus Vacerro
Comment (#6249477)
Posted Wed, 01 May 2013 01:34:07 GMT (5 years ago)
Thanks. Too bad it won't be fixed. :(