mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
Mark Smith ([staff profile] mark) wrote in [site community profile] dw_maintenance2020-04-26 01:27 pm

Code has been pushed!

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!

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)

[staff profile] denise 2020-05-04 10:13 pm (UTC)(link)
Our current best guess is that either our CDN or your ISP cached a blank copy of one of the Javascript files that is necessary for the RTE to run for a handful of people, which is why we can't reproduce it. We've forced a cache update on our side with the CDN, but if rebooting your computer didn't work, I honestly don't know what else I can tell you other than waiting it out on your end. What happens if you visit https://www.dreamwidth.org/stc/??fck/fckeditor.js?v=1587938337 ?
satismagic: a face within purple hydrangea (Default)

[personal profile] satismagic 2020-05-05 10:28 am (UTC)(link)
I ended up switching to the beta "Create Entries" page, and then switched back, and now Rich Text is working again. No idea if what you did helped or if switching it off and back on via the beta feature did the trick.

It's nice to have Rich Text back, no matter what fixed this. :)