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

[ilyena_sylph]

HOLY CRAP THE NEW COMMENT PREVIEW!

I LOVE IT, I LOVE NICK, I LOVE EVERYONE IN THIS BAR!!!

[alexseanchai]

New comment preview?

OOOO! New comment preview!

[azurelunatic]

Hooray!

*previews*

Oh, that's lovely!!!!

[ilyena_sylph]

Isn't it great? I love it!

[schezar]

Did you get rid of the spell check option? I don't see it anymore when I go to preview my comment.

[sporky_rat]

Spell check was old and crusty and tbh, browser spell check was doing most of its job.

FAQ may be broken

[paradoxlyl]

I like the new comment preview page! However, I think the FAQ broke in the code push. While I can see the listing of FAQ topics, when I click and get redirected to the new page I can't see the answered question. I get the dreamwidth page and surrounding features, I get the date the question in the FAQ was last updated, but nothing else.

+1

[redscales]

It's definitely broken in the same way for me, too.

[mycenae]

Not so much an issue as a general question, but do you (or anyone else, I'm happy to poll the crowd) know if there is a a way to stop photos from doing the click-to-fuil-size thing? (It's a cool feature, but it would be nice if there was a way to stop it when coding a post where it's unnecessary).

AND ANOTHER THING:

[mycenae]

Thank you for fixing the photo resize stuff in general, my in-post codes no longer break ;;;;;

[pauamma]

Did the spamwhacking pages shed some of their styling (like borders), or is my memory that they used to have those faulty?

[roadrunnertwice]

kareila and momijizukamori converted a whole bunch of less-traveled pages to the new styles, so it's very likely that that was one of them.

[mark]

Feature request for new comment preview: https://dw-maintenance.dreamwidth.org/82644.html?thread=3299284#cmt3299284

[ravenna]

i'm not 100% sure how to word this, so sorry if it's clunky:

after posting a comment from the new preview page (which is GREAT!!!), you're now taken to the whole main comment page instead of the nested thread, if you were in one. pre-new-great-preview-page, you would land back where you started, plus the new comment. this is kind of weird because you don't see the comment you just posted and you have to scroll around and find it if you're on a page with a lot of comments/collapsed threads, plus potentially contend with lag.

previously, when editing a comment it would do this when published (take you back to the 'main page' of comments vs keep you in your spot), but not when you first made the comment.

+1 to the lag concern

[kingkingcxiii]

I am already seeing lag issues here after posting a couple tags to my RP community this morning. Our logs frequently break 1000 comments and sometimes 2000 even. There is a noticeable increase in the posting time now from before because the site is having to load a whole log instead of just a thread. Is there anyway to go back to the old landing place after posting a comment without messing with the new preview? (Because the new preview rocks!)

[subsequent]

Thank you as always!!

[abyss_valkyrie]

I don't know if it's to do with the coding but I can't import from a community on LJ.I'd previously been doing it easily,switching between community or personal journal while importing.Now the option to import to the community over here doesn't exist.

[bluedreaming]

+1 I also experienced this issue.

[moonvoice]

As of today, the ability to 'select' an icon in the browse menu when creating a post is no longer visible across two accounts and two browsers (Chrome and Firefox latest versions).

It still works for replying to comments though.

So browsing-selecting for icons re: entry creation specifically appears to be broken?

[moonvoice]

WAIT NEVER MIND, I didn't actually select an icon, so it just looked like there was no longer any option at all to select anything because the button is missing.

That doesn't seem immediately intuitive, as it just *looks broken* compared to the old version. But obviously the new format does allow you to select things, you just have to make sure you click the icon first, vs. like...expecting to see a 'select' option beforehand? Okay. Phew.

[picterman]

Вікно Rich text як не працювало так і не працює.

[sporky_rat]

The rich text editor is very old and very buggy. There's not always a lot that can be done if it stops working, but you can try the Beta Create Entry page. It doesn't have a rich text editor yet.

Style=light is back to basics

[jesse_the_k]

....and I’m so happy.

(Intermediate code push overrode my font and color choices from style=light)

Re: Style=light is back to basics

[denise]

Please let us know if anything else about it is wonky -- to fix that problem you identified, we had to do a bunch of stuff to the code that generates it, and it's possible there may still be some horrors lurking!

[ninetydegrees]

Does this mean we can turn off "Updated journal page components" in the beta page? Or are there still parts of this which aren't live yet?

[kareila]

It's still in beta, but hopefully not for much longer!

[valtraid]

<3 :D

[pritkiy_kaban]

Everything seems to be in order for me, except damn Cyrillic symbols at main page - they are messed up again (tried Firefox and mobile Opera).

Unfortunately, neither browser allows to play with page encoding as old school stuff did, so I can't pinpoint encoding Cyrillic text is in. So much for useful feedback!

[roadrunnertwice]

Hi! I'd love to talk more with someone who's seeing Cyrillic badness on some pages.

Are you seeing garbage on the Inbox page, too? Or any other pages besides the front page?

[snickfic]

Has Dreamwidth's search stopped searching new posts? Or possibly just new comments? When I search in the comments for a paid comm I follow, I'm not getting any results from after the code push, even when I search for comments I know exist.

[kareila]

Thanks for flagging this up, we'll look into it.

[altamira16]

I thought that the HTML editor on desktop would do paragraph breaks if a blank line was left between the paragraphs. It doesn't appear to be doing that anymore. Is anyone else seeing this?

[delosharriman]

You know, I think it used to. I for one found that undesirable behaviour, so if it has quit, I'm pleased. I want to be able to include blank lines without messing with my "p" & "b" tags.

[kikyo]

Hi there! It looks the error (comment reply redirects to top level view) is still not fixed, at least on my iPad browser. It works fine on my iPhone. I'm not sure if this is my iPad's fault, as it's very old and I can't update the iOS anymore. But the error didn't exist before. Is this a problem for other people as well? Thanks!

[denise]

Your iPad may be viewing an outdated version of the page. Try closing the browser (not just switching out of it), rebooting the device, and reopening the browser.

community importer broken

[bluedreaming]

Highlighting that this is still an issue (also submitted Request #42145). As long as I know you're aware of it, wait time for a fix/details/even just "can't do this anymore" is totally fine!

original comment thread https://dw-maintenance.dreamwidth.org/82890.html?thread=3307466#cmt3307466
Highlight: can't switch to working as a community, so there's no community import option

Re: community importer broken

[kareila]

I think we have a fix in for this, it just hasn't gone live yet?

[theladyscribe]

Hi there, I'm experiencing a weird thing where, when trying to post on a comm anonymously while logged in, I get taken to a page that says "Invalid Submission Form." The most recent time I attempted to post, I was also force-logged out. This is a recent issue, so I think it might be related to the code push, but I'm not certain of that. (The comm in question is an anon meme where I requested banishment to keep from posting while logged in, so it may also be related to that?)

[denise]

That sort of thing is usually a sign that your browser is caching an old out-of-date version of the page. Please try clearing your browser cache and then restarting the browser!

[jesse_the_k]

Something broke on the new code push — hover text over icons intermittently doesn’t appear.

Haven’t been able to reliably force it to fail. I have screenshots, though. Fails in style=theirs, light, mine. In the same browser session I do see hover text on DW’s xkcd_feed.

OpenID broken?

[emperor]

Hi,

It looks like OpenID logins to DW got broken - cf https://www.dreamwidth.org/support/see_request?id=42199 and a fixing PR https://github.com/dreamwidth/dw-free/pull/2743 now merged.

Any idea when this fix will be deployed, please? [I have a few people who usually use OpenID to read/comment on my posts, and now they can't...]

Re: OpenID broken?

[roadrunnertwice]

Soon, but there’s not a scheduled time yet. Sorry!

In the meantime, there should be a workaround: even though the main Openid login form is broken, you can still use the “More options” comment form to log in.

Your friends can click reply on any public entry, choose OpenID as their user type and check the login box, and click preview; that should log them in without posting the dummy comment, and then they can interact as normal. Hope that helps!

"Disable Custom Replies" ticky box is gone.

[notaninternetkiller]

I submitted a help request for this but it seems to still be an issue.

Shortly after the new code push, myself and a few other members have noticed that when you go into Customise Journal Style > Customise Theme > Presentation, the ticky box for "Disable Custom Replies" is gone.

Worse yet, even if we go through our layout Custom CSS and remove all incidences of "?style=mine" it still doesn't stop the layouts from using the custom reply pages.

Unfortunately the formatting issues with customised comment pages pose a real problem (no threaded view, the vertical stacking of links, etc.)

Are there any work arounds or do you know when the custom "disable custom replies" ticky will come back?

Hey, if this disappearance means you guys are working on the bugs with the customised comment pages, I'm all for it!

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

[roadrunnertwice]

Heya -- are you talking about the setting for whether your own journal style defaults to site skin comments or journal-styled comments?

That's not in the customize theme area; it's in the user settings' "display" section, and its name is "Entry Page Default: Your Journal". Does that help?

As for bugs with journal-styled comment pages -- those work fairly well these days, but only if you're using a style that was designed for Dreamwidth (i.e. a "core2" style). If you're using a "core1" style imported from LJ or IJ, well, those have issues that no one has any plan to ever fix. (I don't speak for staff, but from the perspective of someone who does a bit of volunteer work on the site: There's MORE than enough work to be had improving our own stuff without chasing 1-1 compatibility with some other platform's theme system.)