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

[soupervillain]

The code that makes @username into username isn't working in some of my posts (e.g. the bottom of this one).

[roadrunnertwice]

Probably intentional!

I'm guessing that post has a <raw-code> block, because that's how to make artisan markup like your nav thingy not explode. Raw blocks now leave @ mentions alone.

We recently put a lot of effort into making @ mentions behave reliably, and making sure they DON'T trigger where they shouldn't. MOST NOTABLY, we no longer convert @ mentions in the following places:

- Entries/comments that are set to "don't autoformat".
- Inside <raw-code> / <lj-raw> blocks.
- Inside <code>, <pre>, or <textarea> elements.
- Anything imported from LJ et al.
- Anything from syndicated feed accounts.

We decided "raw" needed to be sort of an escape hatch that doesn't do any "auto" stuff to your markup, because there really needed to be SOME way to do that. So you can still link to users in there, but you'll need to use old-style <user name="yo"> tags.

[soupervillain]

Makes sense, thank you!

Sorry for tl;dr. I can't make it shorter because my cognition is impaired.

[jesse_the_k]

Back in June 2019, runpunkrun explained how to use the at-sign to create Dreamwidth user heads. Two weeks later, I explained how to use the at-sign shortcut for other sites as well.

runpunkrun found a bug when the at-sign is followed by a period.

To test that bug, I created the usershortcutbugs comm. It ran through all the possible issues with touching punctuation, and I filed a support request:
https://www.dreamwidth.org/support/see_request?id=40486

BUT

The new code push has changed how DW interprets the characters. Due to changes in my impairments, I'm no longer able to bug hunt. I'm hoping someone reading is willing to take up the cause.

After the latest code push, the escape character for at-sign stopped working correctly: backslash preceding the at-sign turns off formatting BUT the backslash also displays. (Check out my link above and you'll see some ugly crap!) The new code push also changed how usershortcutbugs displays.

Care to step in? I'd be delighted to provide access to usershortcutbugs if that helps.

yeah, totally

[roadrunnertwice]

Thank you for the offer. If you're willing to give me access to edit posts in that comm, I'd be happy to have it as a resource next time I get a chance to hunt down @mention bugs. (Without being able to see the entry source as-written, I can't really make heads or tails of the bug posts.)

Re: yeah, totally

[jesse_the_k]

THANKS!

You're now a comm admin.

(Part of the problem may be using DW markdown to write about DW markdown, which is always the trickiest).

Re: yeah, totally

[roadrunnertwice]

Thanks! Yeah, for sure. The fact that @ mentions are now excluded from raw blocks should at least make that somewhat easier to deal with... hopefully.