LJ Release 92: Bubonic Boogaloo!

[nookiepowered]

It's that time again, Fandomites: time to report on what the newest Livejournal update has changed, broken, fixed, and ignored. News post | LJ Releases post

Billing Notifications

This one is just an oops, but let's get it out of the way first to prevent minor heart palpitations for as many people as possible: when the update went live, the system sent out a bunch of duplicate receipts for old payments. As far as we're aware, that's the extent of it: if you open the notification and follow the link, you'll see it's just a receipt for a payment you already made in March or April.


Changes to Default Comments Style

This is the most obvious change: comment threads on the default style comment page are now extra-collapsed if the thread itself is over a certain number of comments, or the page has more than a certain number of threads on it. By extra-collapsed, we mean that not only are the comments collapsed, so are the threads, so what you see are the first few subthreads, and then one big link that says "and [n] more comments... from [name, other name, other name, etc.]" When you click that, all the subthreads it represents will show up, fully-expanded.

This affects only the default LJ comments page, not any of the custom/classic pages. It may break the Greasemonkey/Stylish scripts some folks are using; if y'all would like to chime in and let us know in the comments, we'll add the info to the main post here. ETA: It doesn't break the style! However, needsnomoon has a bit of code to add here to clean up the color of the new part.


Reply-to-a-Post Notifications

AKA the e-mails you receive to tell you that someone has replied directly to your post or a post you have tracked -- those will now quote only the bits of the main post that are outside of an LJ-cut.

This is a bonus for some people in terms of not having to scroll past the text of an entire post when they're reading replies by e-mail, and a negative for others, if they were using those notifications as a backup filing system for preserving the full text of posts they replied to.


Fixes That Might Affect Us

* Pre-scheduled posts should be less buggy.

* That thing where you get redirected to the Login page even for public posts may be fixed.

* Format=light works again. (But flat view still doesn't, at least on the default style.) Not sure how many RPers use either of those, but JSYK.

* Comment notifications for entries with polls in them should be fixed now.

* New journals are auto-subscribed to news (which they always were) and lj_releases (instead of the increasingly-pointless lj_spotlight).

* Notifications about expiring add-ons should now reference the right add-on. (Instinct says that this fix is what caused the blip with old receipts getting mailed out again.)


New Scrapbook Going Live This Week (Staggered Migration)

(Separate News post.) Which we already discussed here, but a few things have been amended since then, most notably:

* Picture tags, while they won't display in the new version yet, will be preserved, and they hope to add the tag display function back ASAP.

* Photos/galleries with custom-group security levels will be set to private (as was described in the previous post) to make sure nothing glitches and gets shown to the wrong people during the migration. However, those set to friends-only/all-groups will show up as friends-only in the new Scrapbook too, and won't need to be edited.


No1curr

* You can now embed a Spotify player in your journal style.

* "Social capital" and ranking in journal/community popularity is now displayed as part of the gloop of user-data at the top of journal profiles.

* You can now pay 50 bucks for a unique designed-by-you custom userhead that will last for 5 years.


Still Not Fixed

* Any of the ongoing issues with custom/classic comments re: page-breakage and returning you to the main page instead of the thread after commenting.

* ETA: however, this changelog entry (not live yet) looks promising for the future. (Though we don't know if it relates to the custom comments problem, or some glitch with the default comments.)

* Timestamps on custom comment pages.



__

OCD-free mayhem is go. Discuss, suggest, have fisticuffs with ruminants, bring pie and/or cake.

Comments

Should have tested this *tries again*

[need-no-moon.livejournal.com]

I don't see anything broken at first glance.

[nookiepowered]

I'm pleasantly surprised, if that stays the case! This seems like it would mess with the scripts more than the last update did, since it changes the way things collapse, but maybe we got lucky.

[need-no-moon.livejournal.com]

I think they left the classes and id's of the page alone so most is good. I will have to add a wee bit to my css to change the blue of the collapsed thingie, though, but that's not really breaking it.

[need-no-moon.livejournal.com]

Okay, here's what I added to my script if anyone's interested:

/* ----- set fonts ----- */
.b-leaf-seemore-users
{
font-family: Verdana, Helvetica, sans-serif !important;
font-size: 95% !important;
}

/* ----- colour of the collapsed thread ------- */
.b-leaf-inner a.b-pseudo
{
background:#CAE1FF !important;
}

/* ----- colour of the expand link ------- */
.b-leaf-actions a.b-pseudo
{
background:#FFF !important;
}

[nookiepowered]

Awesome, thanks! I've edited the main post to point down here for the code.

And LOL, LJ. Who just send me the notification for your initial comment reply and edit just now.

[need-no-moon.livejournal.com]

Oops! This means I can't fix it. *ducks* Found a better way to do it, the other had some bugs and this doesn't require overriding:

/* ----- set fonts ----- */
.b-leaf-seemore-users
{
font-family: Verdana, Helvetica, sans-serif !important;
font-size: 95% !important;
}

/* ----- colour of the collapsed thread ------- */
.b-singlepost .b-leaf-seemore-more A:link,
.b-singlepost .b-leaf-seemore-more A:link,
.b-singlepost .b-leaf-seemore-more A:visited,
.b-singlepost .b-leaf-seemore-more A:hover,
.b-singlepost .b-leaf-seemore-more A:active,
.b-linkbar
{
background:#CAE1FF !important;
}

ETA: I know, I know. I just realised that they do the collapsey thing on top of the thread as well. So I just threw everything in to avoid any more sneaky links. =oD