Code push over

[fu]

Code push done; let us know here if you see anything strange on the site.

Comments

[tei]

I love the tumblr user tag! :D

[ex_rising236]

Nothing new or strange, all of the new styles are exceedingly wonderful, as is the tumblr user tag, and I just wanted to squee along with tei.

[jumpuphigh]

Did you do something which would cause
Journal View Style When viewing journals (including yours), use this style:
to switch back to the default? Cause mine did.

[jazzfish]

Nothing stranger than usual. :) Although reading the entry title too fast and missing the space between the second and third words made it sound like the code had been shoved and toppled...

[mithras]

We ever going to be able to embed video in comments?

[denise]

Allowing all video embeds in comments can be a security risk, since there's no difference between a video file and a Flash/Java application or embedded application that has the potential to compromise the account of anyone who views it. We do have a bug open to whitelist certain domains so that we can embed things from known-good sites such as YouTube, Vimeo, etc, where the remote site takes steps to make sure there's no harmful content being served, but we haven't gotten the chance to do the necessary work yet!

[anotherslashfan]

I don't know if it's related to the code push, but I can't see embedded videos anymore. Instead, I get a report that the server "embedded.dreamwidth.net" could not be found.

ETA: I can see the embeds again.

[silverhare]

When I try to link to my tumblr (silver-hare.tumblr.com) it comes up as silver-hare. I was wondering how to ensure a hyphen rather than an underscore show up.

[fu]

I'm pretty sure we didn't touch anything in that area with this code push. Have you changed it back to your original setting now?

[jumpuphigh]

I have.

[geminianeyes]

Thanks for the lovely notifs about code pushes. :D Checking out the themes now.

[kareila]

It looks like this is fixed in changelog. I expect to see the fix go live later today or tomorrow.

[yvi]

"DOM is not defined
DOM.addEventListener(window, "load", function (evt) { "

on all reply pages (site scheme and S2)

Context:



DOM.addEventListener(window, "load", function (evt) {
// attach userpicselect code to userpicbrowse button
var ups_btn = $("lj_userpicselect");
if (ups_btn) {

[kareila]

Is that with or without the jQuery beta turned on?

[fu]

Take another look at the themes now; just listed all 64 new themes under Featured *g*

[fu]

Hmmm, yes. We need to fix that (but it shouldn't be causing anything else on the page to fail at least)

ETA: Fixed now!

[fu]

Fixed! Thank you for pointing that out :)

[silverhare]

Thank you. :)

[ex_rising236]

Eeee.

[ninetydegrees]

Not sure this is what Yvi is reporting. Quick Reply is broken for me (beta turned on) on site pages: I always go to the full reply page.

[fu]

Oh oops. That was nasty! Should be fixed now.

[ninetydegrees]

Fixed for me! Yippee! Thanks!

[ninetydegrees]

Don't know if that's on purpose but there are 10 new themes missing in featured, which is very sad.

[fu]

Oh no! Not sure how I missed them -- do you have a list by any chance?

[ninetydegrees]

Loading the doc...

Basic Boxes : Delicate, Heart of Darkness, Histories, Owlish, Profundity, Teal Deer, With Your Rain.

Compartmentalize : Spectrum, Spectrum II, Spectrum III

[fu]

Oh! I think I know what happened; these were committed just before I did my last points distribution, and I was using the wrong fields to filter.

Anyway, added them all to featured. Thank you for catching that!

[gool_duck]

On the 'post' page, where I compose posts in the HTML window, the ticky-box for no automatic formatting is ticked. That means new paragrraphs and newlines fail to appear as I expect them to.

I am used to the ticky-box being un-ticked and hitting enter when I type an entry resulting in the post having anew line.

I don't know why the ticky-box is ticked by default when it was not before.

[kareila]

If you untick it next time you submit a post, it should remember its unticked state from then on. It has been "sticky" in that regard for some time now.

[gool_duck]

Thank you! I'll do that.

encryption

[storyfan]

When I logged in just now using Firefox, I received a message saying my information could be easily read by a third party. What does that mean?

[zdenka]

I haven't been getting comment notifications the last day or so. It's not an e-mail issue, because they aren't appearing in my inbox either. I just checked my settings to make sure I should be getting comments, and everything looks all right there. Could this issue be related to the code push? Or maybe notification is just being slow and it will get there eventually? :-)

[denise]

Hm. If you're not getting comments in your inbox (although it's only comments to entries you specifically subscribe to, and comments to entries in your journals -- not replies to comments you make elsewhere or in comms -- that are directed to your inbox) it's possible that a setting might have gotten unset somehow. Try this:

* go to http://www.dreamwidth.org/manage/settings/?cat=notifications

* Uncheck both "Someone comments on any entry in my journal" and "Someone replies to any comment I make"; save

* Recheck "Someone comments on any entry in my journal", save

* Recheck "Someone replies to any comment I make", save

That should work if it's the problem I think it might be. (You need to leave both of them checked in order to get all your comments emailed.)

[zdenka]

Thanks -- I have tried that. Now I'll see if it worked.

[sylvaine]

I haven't been getting replies to my comments in my inbox, though they show up in my email normally. Could that be related to the code push? As far as I know, I haven't changed any of my settings recently.

[denise]

We didn't change anything having to do with notifications or the inbox at all, so no, it's extremely unlikely, especially since if it were to do with the code push, everyone would be having the problem and it would've have taken a week to show up.

Check out my response here for some steps to go through.

Re: encryption

[denise]

Without the exact message, it's hard to say, but generally it means that you're logging in through the navbar or through the login form on site scheme pages, rather than the dedicated login page, and the browser doesn't recognize the encryption that we're using on those pages. We let people log in from pages that aren't served over a secure (SSL-encrypted) connection, because otherwise we'd have to serve all pages via SSL (which puts a lot of load on the servers) because we do let people log in from everywhere on the site. However, in order to prevent eavesdropping and password sniffing, we do encrypt your login information through alternate means, inside your browser, before the login gets sent (so your password is never sent in the clear) -- some browsers just don't recognize this as 'encryption' for the purposes of showing the warning.

You don't have to worry about it -- your password is never sent cleartext, even if you log in on a non-SSL page.

[alisanne]

The DW crossposting feature seems to not be working.
Help?

[kareila]

LiveJournal seems to be having an outage; the main www site is responding, but journal accounts are not. You can monitor http://status.livejournal.com/ for more information.

Crossposting should be available again once LJ comes back, but you'll need to edit any non-crossposted entries in order to get the crosspost to be attempted again.

[alisanne]

Hm. I seem to be able to access LJ and IJ without difficulty and my DW inbox keeps telling me that it has successfully xposted to both journals, only when I check, nothing.
Will keep an eye on it. Thanks!

crosspost to LJ is acting odd

[dreamhunter_kai_ri]

I did not catch it the other day but did tonight; apparently 4 posts to DW that were set to autopost to LJ recieved failure notices in DW but when I checked LJ, they were present and accounted for. Meanwhile the two I posted tonight (before I caught the failure notices) failed to reach LJ so the failure notices for those were at least accurate.

Thanks,
:)

Re: crosspost to LJ is acting odd

[denise]

Yeah, with LJ being up-and-down, crossposting is going to be a little shaky. I'll make a new post.

[nounsandverbs]

Anyone else getting this message when they try to visit the site in Chrome?

"Requested Range Not Satisfiable

None of the range-specifier values in the Range request-header field overlap the current extent of the selected resource.

Apache/2.2.11 (Ubuntu) mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 Server at www.dreamwidth.org Port 80"

[nounsandverbs]

In Firefox it works just fine.

[denise]

We're working right now on fixing some problems with certain processes using too much memory (see later posts in dw_maintenance), so it's probable you just hit the site during a point when we were restarting the webserver.

[nounsandverbs]

Haven't been able to get to DW via Chrome for more than a week.

[denise]

Weird -- I'm using Chrome (as are many others) with no problems. Do you have any plugins installed that might be causing the problem? If you have any plugins/extensions installed, try disabling them all, then adding them back one-by-one and checking after every add. That might help you narrow down the problem.

If you keep having the problem, can you open a support request with as much detail as you can? (Error messages, troubleshooting steps you've tried, etc.) Someone can help you troubleshoot further.

[sofiaviolet]

I get this error message in Chrome periodically - usually only for the Inbox, though. Clearing the cache fixes it.