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-06-28 10:03 pm (UTC)(link)
Unfortunately, the importer is a very complex system with a lot of moving parts, and we don't have control over all of those parts because we're working with a data feed from elsewhere. This means there's a really limited number of people who can troubleshoot! I'm sorry about the hassle; if you leave the support request open, it will stay on the list of "stuff to troubleshoot when there's time", but I can't make any guarantees.
matrixmann: Engineer und tools at your service (Somebody called me?)

[personal profile] matrixmann 2020-06-28 10:31 pm (UTC)(link)
At the moment this would be okay. As the whole issue with crossposting to LJ is also troubled (at times it even works, but mostly not), and it's known there too that the issue isn't too easy to fix, I think it's best to keep one's expectations low if anything can be done about this at all.

I just wanted to note it so that it doesn't get lost.
(Regarding the behavior in LJArchive in this icon issue, I issued an entry in the corresponding LJ community for that program and the feedback that I have on it as of now (didn't expect that to come in that quick), it speaks that other people encounter this icon issue too.)
Edited 2020-06-28 22:31 (UTC)