domtheknight: espresso machine brewing into little white mugs (Default)
domtheknight ([personal profile] domtheknight) wrote in [site community profile] dw_beta2011-04-10 06:29 pm
Entry tags:

hello beta testers!

At long last there are specific things that need doing!

For some background, check out [staff profile] 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.
cmshaw: Leverage: when Hardison pushes the button, everything goes boom (Geeks bring the firepower)

[personal profile] cmshaw 2011-05-31 02:36 am (UTC)(link)
I just lost the expandability on my cut tags due to having this entry on my reading page:

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?
cmshaw: Leverage: when Hardison pushes the button, everything goes boom (Geeks bring the firepower)

[personal profile] cmshaw 2011-05-31 02:46 am (UTC)(link)
...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)) 379 Uncaught TypeError: Cannot call method 'match' of undefined
                data.userid = userid[1];
                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: Close-up of Fu, bringing a scoop of water to her mouth (Default)

[personal profile] fu 2011-06-02 03:00 pm (UTC)(link)
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.
cmshaw: Fullmetal Alchemist: Winry repairs Ed's arm (Mechanic)

[personal profile] cmshaw 2011-06-02 05:08 pm (UTC)(link)
I'm glad I could help! :)