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

[roadrunnertwice]

Net speed might be a problem for the preview (gotta load the image sometime), but *setting the value* is just changing a bit of text that already had to be loaded in order to display the form.

I'm wondering if this is related to the escaping error that broke the keyword display for icons with names like "<_<". Icon choices get sent to the backend by their keyword value, so if the keyword got mangled during shipping, it won't match the real keyword on the backend...

[jhumor]

Oh I hadn’t thought of that since I only use text naming my icons, but yes it could easily be a backend problem. Though you’d think it would be more consistent if that’s the case. I haven’t been posting as much this week, but I’ll continue to keep an eye on it.