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

[whiskeydrink]

Comment Not Posted
You entered an account name but selected "post anonymously" or as the currently logged in account. Please clear the textbox or select the correct posting mode and try again.

Hi, the above error seems to persistently generate if you try to post logged-out anonymous comments but you have Chrome set to store your DW username/password. It's apparently populating the option to log-in as you post the comment even if you have anonymous selected.

[falkner]

I actually have been having this issue with DW for... ever, as far as I can remember.

[wonderland_vogue]

Can't say I'm a fan of trying your workaround for LJ Juggler only to be "temporarily IP banned" from logging into one of my journals for only trying three times to get into the damn thing with this API code thing.

How long do temp bans last because this is INSANELY inconvenient.

[mark]

It's 5 minutes.

Semagic Success!

[runpunkrun]

I followed your instructions and did a test post to my journal and everything worked beautifully! Thank you so much for doing this. I assume this will also work when posting to a community through Semagic?

Re: Semagic Success!

[mark]

Yup, should work! Let us know if not.

ljArchive stopped working

[akatsija]

Looks like ljArchive stopped working after the last change. Was there any change in the way how login credentials are presented to the server?

--
А.Кац и Я

Re: ljArchive stopped working

[mark]

Yup, big changes. See the links in yesterday's announcement for information on how to update clients.

[darjeeling]

Coding in the mini profile sections seems to have gone wonky. Was auto-formatting disabled there? From cursory glance it looks like implied line breaks are no longer being respected and now require an explicit < br > tag?

Visually: not a fan of the new icon browse thing. Having the username in smaller font, sitting above the picture, seems unwieldy especially with so much usable horizontal space to the right of the icon to start with.

Clicking the icon (non-paid accounts) now takes you to your icons page? That's going to get old real quick as people are trying to hit the "More Options" page, the selection dropdown, or the Subject line... especially the Subject line. It'll be a bigger problem on mobile than desktop, but on mobile they're mushed together pretty tight. I know DW has that thing now where it's supposed to remember what you can in the text box if you navigate away from the page but that's hit or miss.

[runpunkrun]

Oh man, can confirm on the profile page's mini bios being a mess. My poor comm: https://fancake.dreamwidth.org/profile

It's definitely eating up the line breaks made by hitting return. And maybe the blockquote tag too?

[monanotlisa]

Thank you! :)

[forcevisions]

As a heads up, I'm getting a lot of 502 errors. It was like a 5 minute impenetrable wall of them, and now it seems to be on and off between loading, 502 errors, and 504 errors.

[mark]

Sorry about that -- I broke things briefly. Should be back to normal now.

[iamnotgod]

Hello!

I was responding to a comment through my inbox (not my email), and was forced to use the 'other account' option to post my comment. I did not have Chrome auto-fill my password, and was not anonymous when I posted.

[mark]

When you say forced, what do you mean? It didn't show your account name/didn't let you select your account normally?

[ex_flameandsong751]

As per an above comment from someone else, coding in the profile is wonky and now requires a < br > tag (as well as explicitly tagging < center > for each and every line needing to be centered) and some of my RP profiles now have huge amounts of white space that I can't get rid of.

Lots of 502 errors at the moment.

However, the work you guys are doing is appreciated 😊

[tessitura]

Yeah, echoing this.

[speedweed]

So I found some weirdness.

When switching between accounts manually I'll log into one and then refreshed and it says I'm logged into the one I was logged into previously. Which I very much had logged out of. This has happened multiple times between multiple journals?

[mark]

_Hmmm_. How are you logging out?

[sweetsleuth]

https://images.plurk.com/6C45AE7uOPlliUTgWvDFxG.png

So this is how it looks on mobile for me... I'm on an android using Firefox. The huge text in the subject line was a thing prior to the update, but the username doesn't line up nicely because of the huge drop down bar.

It looks fine/as intended if I force the browser to use the desktop site, but then the text won't wrap to fit my screen, so that's unwieldy in mobile.

Also was removing the random icon button intentional?

[assholic]

I didn't even notice the removal of the random icon thing, which I should have because I use it frequently. Huh. Aesthetically, I'm not too sure I like it on desktop either. More options being moved up top and the browse covering the actual icon seems like a really weird aesthetic choice. We just got used to having to click on the icon to browse, and now it's like browsing for dummies.

My complaints aren't against Mark and co or any of their work. It's just general mehing. I have OCD, so change for the sake of change really throws me, and it feels (to me) like we just got used to the last changes and now there's new ones. Ones that don't seem to be that helpful (particularly for both mobile and desktop - that preview you showed looks horrible).

I know they're going to need to tweak things to make it more accessible, but it's when the changes seem to be for worse instead of better that I kneejerk make faces at.

Cross-posting engine is broken!

[livelight]

Cross-posting engine is broken!

I have created a post (and then one more test post, with the same symptoms observed). It does not cross-post to LJ. Then I try to edit and see checkboxes "Crosspost this Entry" and "livelight@LiveJournal" cleared. I check them again, press "Save", see message "Crosspost requested to livelight@LiveJournal. You will be notified in your Dreamwidth Inbox if this attempt fails" -- and still nothing happens, and editing shows that checkboxes are cleared again.

Re: Cross-posting engine is broken!

[ysilme]

I have the same issue.

[borntolove]

Do you think it's possible to revert back to the old icon selection drop box? The click new selection picture doesn't load on my Windows 10, Chrome.

[borntolove]

Windows 10 doesn't like that icon click to browse

[momijizukamori]

Quick heads-up that people are reporting some issues trying to use Ctrl+C to copy the API key in Chrome, at least on Windows - most likely Chrome is grabbing some whitespace or formatting or something along with the actual code. Right-click -> copy is fine.

[snickfic]

I think somehow at least one of the image formatting tags is now broken? The height tag (eg height="300") no longer has any effect, and images with that tag are now displaying as their actual image sizes, but the width tag still works fine. Also, all images inside tables seem to display as the size now, much smaller than either their actual image size or as determined by the height or width tags.

[denise]

Can you link to something that used to work and is messed up now?

[alexseanchai]

is turning on and off beta features supposed to rearrange the order the features show up in on that page? because I just turned the new one on and off and on again because of reasons and this also involved turning beta new-entry back on (I hadn't meant to turn it off) and 2FA back off (I hadn't meant to turn it on) and the three things on that page are definitely changing what order they're in and it's weird.

also how do I get my font sizes back where they were? viewing Tropospherical Purple at 90% zoom (Windows 10, Firefox 75.0) puts most of the text at the size I want it, but not the choose-icon drop-down and not my handle right above that, and those are wrong in different directions:



and it looks like the 90% zoom is sticking to dw_maintenance but not to the rest of Dreamwidth, in that viewing the comm in my journal style is now too small, viewing my journal in my journal style is still the right size (since I fiddled that to size right at 100% zoom), and viewing one of my own entries without changing zoom is still Tropospherical Purple and too big.

[roadrunnertwice]

Nothing actually specifies the order of the features on the beta page, so it ends up being random. Every change or refresh will change it. Rare to have multiple betas at a time, so I don't think anyone's really noticed before.

The username indicator is just too small on site skin if the "new everything" beta is enabled. Got that on the list.

Drop-down styling is probably staying put -- that's a complex interaction between the OS's defaults and the Foundation CSS framework these pages use, and I'd rather not breathe on it. 😅 It's also meant to represent the best known balance of usability concerns.

[arethinn]

....Semagic still works with Dreamwidth?? I gave it up years ago but can't exactly remember what was broken enough that I felt I had to. (Crossposting, maybe?)

Is there, or will there be, a way to change the sort order of the new icon browser? I'm not 100% sure, but they appear to be sorted in upload order instead of keyword order like the dropdown text menu.

[denise]

I am reasonably sure the icon browser has always been like that, and I think we had a good reason for why we didn't put in a sort / resort but I can't actually remember what it was, heh.

[anaraine]

I know I'm using an outdated version of Safari (9.1.2), and if that's the problem I'll live with it (since I can't update Safari without rendering it unusable...), but the arrangement of the quick reply is really... weird in my personal opinion. This is how it looked pre-update.

Also, is that white starburst in the left-hand corner (to indicate browsing, maybe?) really necessary, given that you also have the word 'browse' over the default icon?

[denise]

I think that's older Safari not recognizing the positioning, and if that's the case then a fix might not be possible, but I'll flag it for the people who know these things!

No clue what the starburst is in the left; it's not something we're doing deliberately. Possibly another Safari glitch.

[mdlbear]

Charm worked perfectly for me after changing the password to an API key. Note that I only use it from a script in quick post mode; no idea whether any other features may have broken. I just tried jbackup, which I'd been hacking on,and it worked, too, although only because I'd replaced "http" with "https" only last week.

Anyway, a big jump in security for an absolutely minimal effort on my part. Thank you.

[smallredboy]

When posting Rich Text is not working for me, only HTML. Could y'all please fix that?

[denise]

Please try clearing your cache and restarting your browser: does that fix it?

[unicorn]

Thanks so much for this! I'm working on painfully weaning myself off of my accustomed accessibility-unfriendly font sizes, but I think I'll manage. :) However, these are my issues right now:

Beta: Updated journal page components

I am losing my mind at the (Thread) link being the first one to the left at the bottom of comments. Any chance of at least making the order (Reply to this) (Thread) (Thread from Start) (Parent), or better yet, eliminating (Thread) and letting the (link) above stand alone?

Beta: Two-Factor Authentication

I tried turning this on, enabled it in My Account Settings (/manage/settings/), went through the setup process using Duo Mobile, entered the key, had it tell me that everything worked - but then the toggle in My Account Settings turned itself off again. This happens no matter how many times I try to enable 2fa.
Incidentally, how will 2fa interact with the new API trick?

Thank you again, by the way. I know you guys put in an incredible amount of work to keep supporting the common 3rd party apps despite huge changes; it's really above and beyond.

[denise]

2FA isn't entirely working yet, it's just the setup part that's been implemented!

[etfb]

Can confirm that ljdump works with the API key change. I tested it without making a change and got a Python error message that indicated an invalid password. I edited ljdump.config and replaced my plaintext password with the generated API key I got from following the link in the previous dw_maintenance post, then ran it again. It worked!

For those who haven't heard of ljdump: it's a slightly finicky tool that downloads your DW or LJ posts as XML files, in a form that can then be used elsewhere. I'm using a version from 2010 that has a bug where it puts some non-ASCII text in one of the fields so it's not flawless, but I could probably hack it if needed. Source and instructions at https://hewgill.com/ljdump/

[atrophymidwife]

Thank you!

[burn_the_world_down]

Got the API key issue with LJ Juggler sorted out. However, I still can't post without jumping through a bunch of hops. I get the following message if I posted from the reply link in my email when I am already logged in or if I try to comment on the top level of anything:

Comment Not Posted
Invalid form submission. You may have left the reply form open too long, or logged out since you opened the page. Please try posting again.
You entered an account name but selected "post anonymously" or as the currently logged in account. Please clear the textbox or select the correct posting mode and try again.
Your login cookie has disappeared.

Help!

[mark]

Test (clicked on the reply link in the email, and trying to reply).

Edit: So I'm not sure what you're seeing. I just clicked the 'reply at the webpage' link in the comment email I got for this, and it worked? What browser are you using?

[rattfan]

I'm unable to use rich text, only HTML. I see someone else had this problem and was advised to clear cache etc. I've tried this to no avail.


Thanks

Alex

[mbarker]

Clearing the cache didn't fix it for me, either. Using Chrome on Windows 10.