hello beta testers!

[domtheknight]

At long last there are specific things that need doing!

For some background, check out denise's explanation of technical debt. One of the things she mentions near the end is that we need to mingle JQuery with the existing Javascript the site uses.

This is a big change for how the site works, and it means that things could go wrong when it goes live. We now have a way you can turn on beta testing so that we can see how the new code will operate on a day-to-day basis.

If you want to check it out, you can! If you notice any weird behavior, please let us know - you can comment here.

A couple things to note: not all the features you might enjoy right now will be available in beta testing, because not everything has been rewritten yet. There's a list available on that same page, and you don't need to report those things because our excellent devs are already working on them.

At any point in time if you want to switch back, you can just go to the same page and turn beta features off.

Comments

[pauamma]

Footer on that page says:

Stay tuned to dw_news for upcoming testing opportunities. Thank you.

Maybe it should link to dw_beta instead?

[fu]

Hummm you know I'm not sure. OTOH, dw_news will probably announce the bigger ones as they come out, maybe? (domtheknight, denise: thoughts?)

[domtheknight]

Agreed that news will probably make big announcements, but we would announce things in beta... it doesn't matter to me. Whatever makes more sense is fine!

[afuna]

Hee doesn't matter to me either! Just whichever ends up making more sense for our workflow *G*

Hmmmm. Yeah I think dw-beta is good, will tweak the translation string.

[afuna]

Oh blah it requires a code change, never mind!

[domtheknight]

If it's a bunch of work, then I would say it's not worth it.

[fulminata]

I don't know if this is weird behavior, but once I turned on beta testing for this account, I could no longer use the cut open and close arrows on my pages. (It still works for if I'm logged into another account.)

[sofiaviolet]

Expanding and collapsing cuts with those little arrows is one of the things that hasn't been implemented yet.

[fulminata]

Okay! Thanks for the heads up.

[highlander_ii]

Is this the 'individual entry' ones or the 'expand/collapse all' arrows in the sidebar?

* individual ones work
* 'all' ones aren't there

[sofiaviolet]

I've never noticed the sidebar arrows! Individual entry expand/collapse works as of last code push but it didn't when I posted that comment.

[highlander_ii]

I actually hadn't either until I'd seen your comment - and I thought that's what you were talking about until I reread your comment.

Either way - it inspired me to toy with those arrows (or notice they were missing), so \o/! =)

[sofiaviolet]

The page says that quick reply has been implemented, but I only see it on journal-styled pages. Site-schemed entries send me to the ?mode=reply page.

(Chrome 11.0.696.34 Beta on Mac OS 10.6.7)

[afuna]

Hmmm. I think that we broke something there; should have it fixed by next code push, thanks!

[domtheknight]

Thanks, Fu!

Quick reply

[melannen]

Quick reply comment boxes now have an issue with focus: on a page with a quick reply comment open, page focus and cursor automatically go to the top of the message box, no matter where on the page I click. (This happens in both Opera and Firefox.

(...this is actually an improvement on Opera, which didn't have quick reply boxes at all before, but it really reduces functionality in Firefox.)

Re: Quick reply

[fu]

Should be fixed now! (Huh I hadn't realized that the QR boxes weren't working in Opera at all though; glad that the new version works :))

[hazelwho]

When replying to a post in a friend's journal, the reply box was centered, making it run over into the right-side tags they use in their layout, like this:



I know this is a beta issue because I turned off beta and then turned it back on again, eliminating and then replicating the problem.

[fu]

Thanks, we'll have that fixed by next code push!

[zvi]

I have lost individual expanding cut tags on my reading page today.

The expand all cut tags page says I have no cut tags on my reading page, but this is a lie, because http://telesilla.dreamwidth.org/245615.html is on my reading page and it has a cut tag.

I still have cut tags on my recent entries page and on my day view page and on tag pages.

[fu]

Hmmm. Can you look in your error console? If it says something about not being able to call the function match on an undefined variable... then we'll have that fixed by next code push. If not, can you see if there are any other errors in it at all?

[zvi]

Where is the error console? (Just to be clear‚ I am not talking about on a test install, I'm on the live site.)

[fu]

It's browser specific -- likely it's under View -> Tools -> Error Console, or View -> Developer -> Error Console, or Tools -> Error Console

(depending on the browser -- but let me know which browser you're using I might be able to give you more specific directions)

[zvi]

Hmmm, I definitely had this problem using Chrome at home, but not this morning at work.

I suspect that I'm using a later build at work. Will get back to you when I am at home.

[fu]

Oh hey anything?

I'm planning a code push this weekend or beginning of next, and hopefully that should also take care of it!

[zvi]

It's appearing and disappearing at home in Chrome, and I can't figure out when it will or won't happen. I'm also having problems w/ reading PDFs inline or not, so I think this is a more general problem I'm having with Unity/Ubuntu, instead of a DW thing.

[axiom_of_stripe]

I just lost the expandability on my cut tags due to having this entry on my reading page:
http://kink-bingo.dreamwidth.org/256440.html

If I filter that entry out, my cut tags expand again. If I turn off the beta, my cut tags expand again. I tested this in Chrome 11 and IE 9. I'm using Transmogrified with some custom CSS which I don't think is affecting entries on my reading page (it's only meant to style the page headers and side boxes).

Perhaps it's because of the community link in the subject line?

[axiom_of_stripe]

...Ah-hah, and scrolling up I see to check my JavaScript console in Chrome, which offers this error:

function _initUserhead(context) {
    $("span.ljuser",context).each(function() {
        var $usertag = $(this);

        $("img", $usertag).each(function() {
            // if the parent (a tag with link to userinfo) has userid in its URL, then
            // this is an openid user icon and we should use the userid
            var $head = $(this);
            var $parent = $head.parent("a[href]");
            var data = {};
            var userid;
            if (userid = $parent.attr("href").match(/\?userid=(\d+)/i))

s.dreamwidth.org 379 Uncaught TypeError: Cannot call method 'match' of undefined

                data.userid = userid[1];
            else
                data.username = $usertag.attr("lj:user");
            if ( !data.username && !data.userid ) return;

            data.type = "user";
            $head.contextualhover( data );
        });
    });
}

That error doesn't show when I filter out the entry causing the problem.

[fu]

You're right, it's the community link in the subject line. I really appreciate the messages from the error console btw! We'll have that fixed by next push.

[axiom_of_stripe]

I'm glad I could help! :)

[melannen]

In the context hover menu for communities which I have neither joined nor subscribed to, the line break between "Join Community" and "Subscribe" is missing in the beta site.

[domtheknight]

I think the fix for this is live now.

[ninetydegrees]

Polls results not AJAXed with beta testing turned on. :/

Comments and IE9

[ninetydegrees]

Comments and IE9: I couldn't do anything but edit and track the comment. The other buttons didn't work.