Code pushed!

[denise]

The code push is now complete! Please report any problems here for the next 24 hours or so (and to Support after that).

Code tours describing changesets included in this push are:

* 22 Feb - 13 Mar
* 14 Mar - 23 Mar

In particular, we're asking people to turn on the "New JS on Journals" option on the Beta Features page. We've finished converting all the JavaScript inside your journal to JQuery, the more modern JavaScript library we're moving towards. The version available for beta testing now is the release candidate. With the next code push, we will be opting everyone into that beta (with the ability to still opt out of the beta version if you discover a showstopper bug that prevents you from using your journal); with the code push after that, the code will be taken out of beta and you will no longer be able to turn off the new JavaScript behavior at all.

So, turn on the beta now, and report any bugs with JavaScript in your journal to the dw_beta "Last Call" post if you're sure it's related to the new JavaScript, or here if you aren't sure whether or not it's an issue with the new JS!

Comments

[needled_ink_1975]

NO problems that I can see.

Just wanted, mainly, to say thanks for everything.

–Nic

[deadlydelicacy]

I don't think it's the javascript, but from yesterday to today when I'm logged into this account I get eternally loading pages and I can't see my icons with the icon browser. I also can't expand comments. I tried to the the beta test to see if that might fix it but no dice. On my regular account on dreamwidth using the same exact browser I am having no problems but that's a free account with two pictures? Maybe that makes the difference?

[denise]

That sounds like your browser is having issues loading the Javascript fully. Do you have any extensions enabled in your browser such as NoScript?

Try cleaning your browser cache, then restart your browser -- does that help?

[storyfan]

I like the tag selector. The entries in 2 of my comms require multiple labels, and this thing will make tagging so much easier.

Also, I like that the icon selector is still a drop-down feature. Since I know what my icons are called, I don't need to see pictures of all of them. The random icon selector seems to work quickly, even on my slower connection.

[unicorn]

Is the size change in the icon browse popup related to the new js, and is there a way to make it smaller again? The small size took much less time to scroll through.

[denise]

Yes, the new icon browser is part of the new JS! If you'd like to make it smaller, you can choose "images only" in the top right corner (as opposed to 'show meta text') -- that will show you only the icons, not icons + keywords + comments.

crossposting

[storyfan]

I don't see where we click to crosspost.

Re: crossposting

[denise]

Do you mean with the new Create Entries page? (That's the second of the two beta options -- there are two separate beta tests running at the same time.) If so, the setup is customizable; hit the gear icon in the upper right hand corner of the entry form, which will bring you into "settings mode" and let you enable or disable individual modules (and drag and drop the modules to wherever you'd like them to be).

[memorable]

Hey, I'm also getting a lot of visual fatigue from the new browsing system. I know it's good because there's less scrolling downward, but I would prefer if there was some way to never be opted into that. I understand that it's a part of the site changes, but I just did two seconds under it and my eyes crossed. Even a little slimmer would be better than that's currently available.

[denise]

Just to repeat what I said up above -- can you leave a comment on the entry regarding the new JS in dw_beta so we have that feedback all together on the beta feedback page? That way others who are having the problem can also weigh in there and that will help us decide what the best solution is. Thanks!

(Ah, dueling accessibility needs. Isn't it amazing how differently different people react to the same things?)

[thenormalsquint]

I'm not sure if this is related to the code push, but when I have an entry with collapsed comments, Expand All (or sometimes just Expand) gives me an unresponsive script error? It asks me if I want to continue or stop the script but neither option actually works? It just hangs and sometimes freezes Firefox, other times it continues to spin the gears and get nowhere.

[denise]

That can sometimes happen if your browser can't contact the site when you try expanding the page, or if your browser is trying to use an older version of the script (if it has the older JS cached). Can you try clearing your browser cache, then restart your browser and try again? If it still isn't working, report the problem in the JS entry on dw_beta, along with the version of the browser you're using and any extensions you have installed.

[seaivy]

I have not understood one word of this post - nothing.
But thank you for all your hard work.

[athousandsmiles]

Seconded!

[ai_hen]

On my friendslist none of the images show up anymore. And I am following Cake Wrecks . LOL. No fun at all without the images.

[fu]

It looks like the issue is with Cake Wrecks itself! It's down right now; likely will come back up eventually.

[esteven]

Much as I generally appreciate the work you are doing for us, I do not understand a word of this post. Does this mean that at one stage my journa will look different whether I like it or not?

Why do I have to be opted in and cannot have things as they are/were?

[momijizukamori]

I'm just another user here, but - for the most part, everything will look pretty much the same. The Javascript update makes the icon browser look slightly different, but have basically the same functionality, and everything else is the same. It's pretty much all hidden work on the scripts that run display, to make them more modern, and easier for new developers to work on. That's why everyone is being opted in, with eventually no option to opt out - the clunky old code will be gone.

[random_xtras]

...You're not saying that at some point we're going to wind up with that hellacious having to choose userpics by picture thing like LJ cranked out? This is one major reason I came here, to keep the nice, sensible text list. And... are you talking about comment page changes? I'm sorry for being so dense. And thank you so much for listening when we talk.

[maqui]

Hey there; just a random DW user who happened upon this comment, so don't take what I'm saying as offiial or anything like that. But having turned on beta testing to see what the javascript changes are, it looks like it's mostly back-end stuff from what I can tell. The comment pages still look the same, it's mostly just the scripts rendering things like comment expansion that have changed up (they seem a little quicker on my end, actually) and we seem to have the ability to manual collapse comment threads even before automatic collapsing would occur now.

And the icon browsing still allows us to select from the drop-down list - the visual browse window is the same sort of thing as it was before, just organized differently. That also works a little faster from what I'm seeing (and when tested on an iPad, doesn't lag up at all the way the old one had a tendency to).

So really, what we'll be noticing as users is maybe some speed changes to how quickly JS-handled elements are delivered and the visual change to the optional icon browser - in other words, nothing like the redesign of LJ's comment pages and icon selection.

[citymusings]

I haven't turned beta on yet, but when I opened DW this morning, my reading page wasn't working properly. I refreshed it. Still odd. Again. Better, not perfect. If I refresh it enough, I can sometimes get it working, but another refresh makes it all jumbled again. Three screencaps:

Isn't this odd?

[ex_mrs260625]

Hi, citymusings, just a fellow user here. When I look at your reading page, it looks fine, so my guess is that there's an access-locked entry that's messing up the page. If you log out and clear your cache, then go back to the reading page, does it look normal to you?

[pocketmouse]

I have no idea if this is related to the JS change or something else, but the Expand command in comments isn't working for me any more. None of the expand or unfold inline links work -- the icon just sits there and spins. Since no one else seems to be mentioning it, I'm sure it's a problem with my setup, but I don't know what.

[eyesofstrength]

Actually, I'm a fellow user who has been having the same problem for some time now on one of my computers but not the other.

The one having the issue uses Firefox 3.6.4 and Windows XP, my main computer that works uses the same browser, same add-ons and Windows 7 and works fine.

I did get it to work on the other computer in Chrome. Since I only use the other computer when at work, that's a doable workaround for me. But you may want to try clearing your temp files and cookies and restarting and see if that helps. If that doesn't do it, try another browser or disabling add-ons.

[proseac]

*raises hand sheepishly* For we simple few who don't understand any of this, are you saying EVERYONE on DW should be following your instructions, or just those who are involved in beta testing?

If the former, I may be back with more questions, as I've never had anything to do with beta'ing software before. Sorry to be so dumb...

[dhae_knight_1]

Fellow user here; I read it as being an open beta; that is, open to everyone who wants to give it a whirl, see what's changed and what doesn't work. :-)

[frith]

I'm very happy that the site continues to work quite well with Javascript turned off on my old Firefox browser. 8^) I'm a suspicious old luddite and Javascript rubs me the wrong way. On some sites where enabling JS is imperative, waiting for everything to load is a pain. On DreamWidth, everything is so well coded that the times I've left JS accidentally enabled, it did not affect performance. Kudos!

[ex_mrs260625]

Interesting glitch, occurs whether I have the Javascript beta testing on or off. (I haven't noticed it before, but it's a little specific.)

On my reading page, there's a long, cut-tagged entry; immediately below it is an entry with an embedded video. If I scroll past the video, scroll back up, and expand the cut tag, the video will stay where it is, blocking the content in the expanded entry. If, on the other hand, I expand the cut tag before I get to the embedded video, it behaves normally.

I'm using Opera 11.61 on Windows 7. String thingy below:

Opera/9.80 (Windows NT 6.1; U; en) Presto/2.10.229 Version/11.61

I'll go test in another browser. (EDIT: it doesn't appear to happen in Internet Explorer 9 on Windows 7, 64-bit edition. The help window won't let me copy and paste the exact version, but it looks like it's IE 9.08112.)

[denise]

Hmmm. That is odd, and very specific, and I think it has to do with the intersection of redrawing of the page via JS (from the cut tag opening) and the embedded iframe for the video in Opera. Opera is, unfortunately, a very difficult browser to fix display bugs in (due to the way it's coded and the way it tends to make up its own version of the standards), and makes up less than 2% of our traffic, so the amount of effort and energy it takes to fix a rare display bug in Opera is often not commensurate with the return we get, unfortunately. :(

If you notice the problem happening in other cases (ie, not in this specific rare configuration of things all happening together, but more generally) then please do report it to Support so they can file a bug report, but as it stands, I will have to just apologize to you and say that trying to track down the cause of the problem is not a good use of our time unless it happens more often!

[slaymesoftly]

Looks just the same to me. I think my post today may have been before the push, but if not, then it was fine.

[zellieh]

My browser is loading Dreamwidth pages incredibly slowly. Some of them seem to be hanging completely, just the little wheel spinning for hours and hours and hours. (I'm not kidding: I turned my browser on at 11am, and it finally loaded all pages at just after 1pm.)

I use Firefox with NoScript, but I've whitelisted Dreamwidth.org and Dreamwidth.net. Now, this might be a problem with my Firefox browser, but I turned on my Safari browser and that was slow as well, albeit not as slow as Firefox.

I've cleared my browser cache and restarted my browser twice now, and it's still hanging. Also, when pages say they've loaded, they're often only partially loaded -- sometimes icons don't show up, or page style elements are only half-there. Other sites are loading fine. Any suggestions for how I can fix this would be great.

[denise]

Offhand, this sounds like it might be a problem with your network, if the issue is happening in multiple browsers. Try clearing your browser cache in both browsers (and restart them afterwards) just to be on the safe side, but if that doesn't help (and it probably won't, but it's always a good first step), open a support request with a traceroute from your computer to dreamwidth.org (instructions on how to perform a traceroute: on windows, on mac)

You may also want to try rebooting your computer -- sometimes if it's been a while since your last reboot, you can wind up having network problems.

[thepizzalord]

I'm in the midst of importing this journal from LJ, and I've run into... not a problem exactly, more of a confusion. I haven't paid for this account (yet, I was planning to today), but all 83 of my icons imported over even though I should only have space for 15, and I seem to have access to them all. Is this a bug or something?

[denise]

Not a bug! We did it that way to keep from running into a problem we were having where LJ wasn't reporting the right number of icons, so people were trying to delete enough icons to import them and getting errors. So, instead we import all the icons, and then deactivate them when you visit your Edit Icons page (because until all the entries are imported the deactivator script doesn't know which icons are most-used).

This does mean that some people can trick the system into giving them more icon slots as long as they don't visit the Edit Icons page, and we'll get around to running a "cleanup" script eventually! But doing it this way worked around a lot of hassle.