Code push done!

[karzilla]

We're updating the site momentarily! Once the dust settles, please let us know if anything isn't working as expected. I'll edit the entry here if we confirm any issues.

Update, 22:30: We've been done for about 30 minutes and haven't seen any issues, so please go ahead and let us know if you notice any problems!

Comments

[mark]

/me pins his hat down.

[denise]

/me passes you the bottle

[mark]

Literally drinking right now. Dalwhinnie. Good stuff!

[denise]

ooooh nice.

(IT'S OKAY, PEOPLE WHO ARE READING THIS, MARK IS NOT DRINKING AND CODE-PUSHING, I PROMISE)

(you know, I'm pretty sure other sites don't have the owners acting like dorks in maintenance comments)

[mark]

(they don't know what they're missing out on!)

[denise]

The fact that we are giant dorks will clearly NEVER BE IN DOUBT

[mark]

Nobody will ever know what we've posted publicly on the Internet, don't worry.

[denise]

Right! Nobody can EVER figure out our cunning plan!

[karzilla]

(you know, I'm pretty sure other sites don't have the owners acting like dorks in maintenance comments)

That's clearly their loss.

[denise]

CONGRATULATIONS TO YOU ON YOUR VERY FIRST CODE PUSH

HEY EVERYONE THIS WAS karzilla'S VERY FIRST CODE PUSH LET'S ALL GIVE HER A BUNCH OF HIGH-FIVE COMMENTS

[feng_shui_house]

Most excellent! I didn't notice a thing, which is Code Push terms = Awesome.

[alierak]

Woo! High five! Ow, less smashing next time!

[musyc]

High-five, high-five! Congrats to you! :D

[geekosaur]

You mean, other sites run by faceless schmucks who constantly make things worse in the name of "new improved looks more like $other_site_run_by_faceless_schmucks"?

[nolongerasleep]

Only thing I notice is a bunch of dorks in the other comments. Not that that is any sort of a problem!

I had to say it.

[denise]

RESOLVED WONTFIX

I regret to inform you that our dorkitude is a permanent condition and no patch has ever been discovered for it. :D

[nolongerasleep]

Which is perfectly fine by me. Always better to know the site is run by people who are as much of dorks as the users are.

[denise]

That's totally our theory and we're sticking to it. It has nothing at all to do with the fact that I have long since completely lost every single last scrap of my giveafuck about trying to hide said dorkitude. :)

[sine_nomine]

*insert nominally sexist comment here about dorkitude, intelligence, and hotness which I know you'll understand and laugh about but there's a concern no one else will get it so I'll omit it!*

*grin*

[musyc]

RESOLVED WONTFIX

Snickered far too hard at that.

[jazzyjj]

I think I just may have found a *major* bug. Your dorkiness seems to have destroyed all the accessibility on here and now I think I've got no choice but to go elsewhere, lol! Only kidding. Actually your dorkiness is very much appreciated, and doesn't seem to have affected the accessibility of the site in any way. At least where VoiceOver and I are concerned. So keep on keeping it real.

[jordannamorgan]

As far as I'm concerned, it's all good when a code push has no obvious effect other than entertainment value via the staff. :D

[denise]

DON'T JINX IT :D

[jordannamorgan]

It's okay, I've got this icon. ;)

[azurelunatic]

YAY CODE PUSH

[karzilla]

I MADE YOU A THING I HOPE YOU LIEK IT

[azurelunatic]

*waits for spammers*

[azurelunatic]

Ooo, subtle change! I like it.

[badly_knitted]

Congrats to karzilla

[jazzyjj]

Ditto from me. Job well done!

[kaberett]

'grats!

Comment notifs still seem to be linking to http. Is that intended? If not I should dig (and also see why support notifs are still providing http links).

[karzilla]

Yes, links in notifications won't change until we turn on HTTPS everywhere in the site config.

[kaberett]

*facepalm* right!

[azaleafae]

I have a minor issue with phone tagging that's been going on since the last code push. The comment body expands and covers up the Post Comment button, making it impossible to post the comment. Here's a screenshot.

Do you think you can fix that?

[karzilla]

We'll definitely look into it! Thanks for the heads up!

In the meantime, as a workaround: if you click the "More Options" button at the bottom of that form before you start typing your response, it will take you to the full page "Post a comment in response" form, which shouldn't have the expansion issue.

[azaleafae]

Thanks. The comment by e-mail is also an effective workaround, but it only works when you reply to a comment, I believe. Right?

[karzilla]

Yes, it seems to be the case that you can only reply via email as a response to a comment notification you've received. If you think that feature could be expanded somehow, let us know over in dw_suggestions!

[karzilla]

A fix for this should go live with the next code push later today. Thanks again for letting us know about it!

[azaleafae]

Oh, it's already been fixed. It was fixed shortly after I reported it.

[anabell_lee]

I can't update my journal. I can't see the toolbar, and nothing I type shows up.
It works fine on my phone, but not on my computer. Could it be my browser?

[denise]

Hm. Can you try clearing your browser cache and restarting it, then checking again? If that doesn't work, try to get a screenshot of what you see when you load the update page, and we can troubleshoot from there.

[anabell_lee]

That didn't work.
Looks like it works with internet explorer though (I've been using google chrome), so I'll just use that. Thanks anyway. :-)

[denise]

I use Chrome too and I don't have any problems, so it's possible it might be one of your extensions interfering with the page! Try disabling all your extensions, or try it in incognito mode. If it works then, you can re-enable the extensions one by one until you figure out which one is the culprit.

[kirathaune]

I'm now unable to see earlier entries on my Reading Page. At the bottom is a message that says, "There are no earlier entries to display. This page displays only the most recent 1000 entries posted within the last 14 days."

This has never happened before. I don't follow a lot of people/communities, but I don't want to lose access to those postings after 2 weeks!

[azurelunatic]

This can be very startling the first time you encounter it! I see that you have a paid account, so you'd be able to use the ?date=YYYY-MM-DD format to view earlier entries on your reading page. (Free accounts would need to visit each person or community individually to see the older entries for those people/communities.)

This limitation isn't new; I don't remember whether it was always in place on LiveJournal or whether it was put in place early on. The ?date=YYYY-MM-DD feature for paid accounts is much newer, but isn't well documented and is hard to discover. I've filed a ticket to make it easier to find on the site, and easier to find in the documentation.

[kirathaune]

The limitation might not be new, but until a few days ago I was always able to go back at least 15-20 pages in my Reading Page. On LJ I am able to go back about 20 pages.

How do I use that format you mentioned?

[denise]

That limit has always been there -- it's necessary to keep the site from falling over. (The reading page is one of the most resource-intensive parts of the site to generate, and older posts are more resource-intensive to include, because it's less likely that they're already cached.) You definitely wouldn't have been able to go back more than 14 days' worth of entries at any point, so it's possible that the people in your circle were posting more and you didn't notice the limit because you just read back to the point where you'd already read those entries and stopped going back!

You can still read those entries by visiting the journals directly -- they aren't deleted after 14 days, but they won't show up on your reading page anymore. Or, you can use the "view the entries that were posted on a specific day" trick that azurelunatic mentioned. It's done by editing the URL. For instance, if you want to see your reading page for entries that were posted on 2015-01-02, you'd use this URL:

https://kirathaune.dreamwidth.org/read?date=2015-01-02

(It only works on your own account, so I can't check to see whether there were actually entries that would have shown on your reading page that day.)

[kirathaune]

Thank you for your response - I guess my peeps are just not posting very much these days.