Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • The QueryStringToHash function needs to be updated so that it doesn’t conflict.

    If you wrap most of the function with an if check on the query variable it will work again.

    
            var QueryStringToHash = function QueryStringToHash (query) {
                    var query_string = {};
                    if (query) {
                            var vars = query.split("&");
                            for (var i=0;i<vars.length;i++) {
                                    var pair = vars[i].split("=");
                                    pair[0] = decodeURIComponent(pair[0]);
                                    pair[1] = decodeURIComponent(pair[1]);
                                    // If first entry with this name
                                    if (typeof query_string[pair[0]] === "undefined") {
                                            query_string[pair[0]] = pair[1];
                                    // If second entry with this name
                                    } else if (typeof query_string[pair[0]] === "string") {
                                            var arr = [ query_string[pair[0]], pair[1] ];
                                            query_string[pair[0]] = arr;
                                    // If third or later entry with this name
                                    } else {
                                            query_string[pair[0]].push(pair[1]);
                                    }
                            }
                    }
                    return query_string;
            }
    

    @johnjamesjacoby could you fix this in the next release?

    I have the same issue. Single site, wordpress 3.0.1, buddypress 1.2.5.2. I’ved debugged it a bit and have discovered that some users are getting a blank activation code, but are being put in status 2. I don’t quite understand why yet, but I’ll update if I find anything.

    I ran into the same problem. I first tried upgrading to WordPress 3.0. That didn’t solve it. Then a little Googling lead me to this thread. Commenting out line 52 solved it like you said. Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)