Code push happening shortly!

[mark]

Hi all,

We're doing a code push as mentioned here.

As usual, a code push includes some visual changes (continuing our efforts to modernize common workflows) and also includes some conversions of old pages to be generated in a different way with different markup. As always, we've tested the changes in most of the major browsers and use cases, but some things may break when they meet real-world usage and different technical setups. If we broke it, we'll fix it as soon as we can.

We will be watching this post for comments, so please let us know if you see anything that needs to be addressed and we'll take a look!

Known Issues

• The spellchecker continues to go walkabout. This is intentional, we are deprecating it and removing it. Modern browsers have spellcheck that works in multiple languages and has actually been updated since 1995, so there's no reason for Dreamwidth to continue to try to maintain one.

Fixed Issues

• FAQs had gone missing. Well, the answers. They're back now.
• Replying to comments was incorrectly routing you back to the top level view, rather than the view of the thread you were on. This is fixed.

As always, please do keep an eye on our Twitter account dreamwidth.

Comments

Re: "Disable Custom Replies" ticky box is gone.

[roadrunnertwice]

There's settings there for both. I promise I read what you actually wrote.



If you're changing the default for a community, you can use the "work as" drop-down box at the top of the page to do that.

Re: "Disable Custom Replies" ticky box is gone.

[notaninternetkiller]

Sweet mother of Benji, it worked! Thank you.

But I swear to you, just last week it was there in the presentation tab.

Re: "Disable Custom Replies" ticky box is gone.

[roadrunnertwice]

PHEW

Yeah, IDEK what's up with the timing on its disappearance. Git says the core1 code was changed to hide that option in the UI in 2011, so you shouldn't have seen a recent change.

I can think of a few possibilities... Maybe themes that were saved/compiled into the system before a certain date kept the old setting visible, but if anything ever caused them to get recompiled, they'd lose it even if their code didn't necessarily change, and then maybe something in the code push caused those themes to get rebuilt. Maybe some themes overrode a property somehow to restore it to the UI, but other themes didn't. Stuff like that. Who knows. Main thing is, glad it's working for you in the "new" spot.