Code has been pushed!

[mark]

Hiya, as per yesterday's announcement, the latest Dreamwidth code has been deployed.

This is the issue/bug/problem tracking post! Please let us know if you see anything... untoward.

Fixed

• Posting an entry would tell you that your password was blank.
• API key generation/deletion was... behaving a little weird.
• Profiles pages were converted to Markdown, but this was too soon. I've put them back to raw HTML, they should look like they did before the push!

Known Issues

• Chrome auto-filling in password forms, when trying to post as the already logged in user, results in an error. Still haven't fixed this one, but we will.
• Reports of logging out possibly not? Need more information, login/logout work for me. Seems transient?

And as a reminder, if you use Semagic et al, please check the link above for information on how to configure it to keep working with Dreamwidth!

Comments

[denise]

Huh. That's incredibly weird -- none of the changes that we've made affected how threading is calculated, and the "parent comment" link is generated absolutely, not relatively (ie, it's not a case of your browser losing a referer header or referring information between windows). The only thing I can think of that might even remotely cause it are a few wacky edge cases... actually, I am pulling this theory out of my ass, but since you're an RP account, I'm gonna guess you use one of the cookie swap extensions like Login or Juggler, right? Try logging out of your account manually, delete the profile for that account in your cookie swap extension, create the profile in your cookie swap extension again, and then log in manually (not with the extension). Does that make it go away?

[assholic]

I had actually done that since the first incident since I re-added this specific account with the API trick. (deleted all accounts, readded manually). The weird thing and why I mentioned it was because of how it happened. The first time was like a glitch with a 502/504. I tried to right-click parent open in a new tab and I had it happen. Closed it and tried again. Closed and tried again. Tried thread from start/thread. And then after about 1 minute of weird tabness, just like a 502/504 blip, it sort of sorted itself out and it opened fine for me again. That was the first time. I'd already cleared my cache/restarted my computer (I do it daily) when the second instance occurred.

I've had random instances within the last month or so where I'm on flatview and, for instance, I go from page 45 to page 46, or I hit '(reload)' and the page displays back a page. It might not even show me the option of going to page 46. the url bar might even read that I'm on page 46, but the page itself is displaying page 45 and there's no page 46 option to go to. I'll refresh a few times and it'll go away. It's something that's been brought up on rpa as an 'am I the only one?' and a few people have had it. Which is what I assumed the parent issue was. Just one of those weird glitches that are happening for a minute before sorting itself out.

[denise]

Ughhhhhh okay then it is something even weirder. I'll see if I can reproduce it at all (I haven't been able to).

[assholic]

I'm not entirely sure it's reproducable. I thought after the first time it wouldn't happen again, that it had to do with all the pushes and api stuff, so I just ignored it. But it was when it happened the second time that I wondered if it was going to fall in line with the other random glitches that have cropped up.

They're not life altering or earth shattering. Just mildly annoying and they all seem to sort themselves out on their own time within less than five minutes, so I'm not gnashing my teeth over it or something. Just figured maybe you'd want to keep a note of the little weird oddities that crop up now and again.