Comments | lj_releases: Release 82

markf in lj_releases

Release 82

Jul 20, 2011 10:27

We don't have any new features this time around, but do have some bug fixes!

Bug fixes:

Fixed a bug that caused non-public tags to display to people who shouldn't be able to view them in some cases. (LJSV-1665)
Users receiving an "Unknown security error" at ( Read more... )

r82

Comments 15

beloved4always July 21 2011, 11:46:38 UTC

(LJSV-1671)

thanks so much for the fix!

littlexdream July 27 2011, 22:10:15 UTC

Just wanted to make you aware that in the last few hours Firefox 5.0 (the latest version for Windows) has started having the "Content Ending Error" that was only happening on Firefox versions prior to version 4. I have had this error on several occasions in the last few hours whilst on my main journal using Firefox 5.0:

"Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression."

I am not sure if this has anything to do with the new release, because LJ was working OK for me until this morning - aside form site slowness due to the DDoS attacks, however I believe this Content Encoding Error is a separate issue. Doing a hard refresh sometimes works, otherwise logging out and clearing the cache & re logging in is necessary, but the error always comes back - mostly after viewing a page more than once (like doing a refresh or opening the same page in a different tab).

Hopefully this is something you will be able to fix, as I do not like to use other browsers.

littlexdream July 27 2011, 22:11:49 UTC

"Content Ending Error" should read "Content Encoding Error"

inlove August 6 2011, 01:17:44 UTC

What about fixing the fact that a lot of people aren't getting notifications? The main issue I have a problem with is I can't validate two of my accounts, because I'm not getting the emails. Any ideas when this will be fixed ? Thank you! :)

HELP!!! fredbassett August 19 2011, 21:52:15 UTC

Since this release was rolled out, posting has become massively difficult.

I have been posting in the html box for two years as the RTE box has been screwing up posts for ages with line spacing and other issues, but since this release went live, I now can't post in html box either without it adding double line spaces that were not there in the original document.

This is a massive problem when posting long documents.

I know large numbers of other people having the same problem

Please investigate and fix this unintended consequence of this release asap!