Unfortunately I could not seem to access to the files because a) the system would not boot and b) the system was encrypted with FileValut 2. Calling Apple didn’t yield a solution except re-formatting the machine and losing all data, but stumbled upon a way to not have to do that:

1. Restart the machine and hold Cmd+R to restart in Recovery Mode
2. Under the Apple menu (top-left) select ‘Startup Disk…’
3. Click on your encrypted disk, then click ‘Unlock…’ (mine is labelled ‘Macintosh HD’)
4. Enter the password of a user who can normally start up the machine and click ‘Unlock’
5. Hit Cmd+Q or go to Startup Disk menu and choose Quit Startup Disk
6. Under the Utilities menu, choose Terminal
7. Type cd /Volumes/Macintosh\ HD (enter the name of your drive instead of Macintosh HD) and hit enter

Voila, now you have access to all of your files on the encrypted drive!

Moral of the story, update both or risk losing some hair!

More detail here. If you still have issues you should be able to e-mail plugins@wordpress.org for assistance (though certainly try the forums first).

add_action( 'wp_ajax_myajaxaction', 'my_ajax_handler' );

function my_ajax_handler() {
    if ( ! empty($_POST) and check_ajax_referer( 'mynonce', 'nonce' ) ) {

        if ( things_go_wrong ) {
            status_header( 500 );
            echo "some informative message or code";
        }

        // ...
    }
}

and in the javascript using success and failure functions rather than deconstructing response text:

var nonce = jQuery("input#nonce").val();

jQuery.ajax({
   type: "POST",
   url: ajaxurl,
   data: {
	   name: encodeURIComponent(tabName),
	   id: tabId,
	   mynonce: nonce,
	   action: 'myajaxaction'
         },
	 success: function(msg) {
               // Handle a successful call
	 },
	 error: function(v,msg) {
            // Handle the error, with the text in msg
         }
});

You could also output the headers manually, but this gives a nice clean way to do it.

I recently added a new validation function to see if the field they entered was a valid twitter hashtag or username.  Though it could be improved (ie. looking for spaces), it does the job initially.  The problem was that the same field name was used for both depending on the value of another dropdown.

To handle enabling or disabling the validation function based on a certain condition, I initially thought you just pass in true or false, such as you do with required:

jQuery('#socialAdminForm').validate({
    rules: {
        component: { twitteruserrequired: true }
    }
    // ...

However the the 3rd parameter (which I’ve labelled, ‘isactive’) needs to be evaluated based on the condition, as the boolean value is passed in here. Here’s an example that determines whether or not to use the validation function based on the select element with id wx-select-social:

jQuery.validator.addMethod('twitteruserrequired', function(value, element, isactive) {
    return !isactive || (value.trim() != '@' && value.substr(0, 1) == '@');
}, "Please enter a valid value");

jQuery.validator.addMethod('twitterhashtagrequired', function(value, element, isactive) {
    return !isactive || (value.trim() != '#' && value.substr(0, 1) == '#');
}, "Please enter a valid value");

jQuery('#socialAdminForm').validate({
    rules: {
        component: { required: true },
        name: { required: true },
        "component_behaviour": { required: true, twitteruserrequired: function(element) {
                return (jQuery("select#wx-select-social").val() == 'twitteruser');
            }, twitterhashtagrequired: function(element) {
                return (jQuery("select#wx-select-social").val() == 'twitterhashtag');
            }
        } }
    }
    // ...

Without the third parameter of the function in addMethod being evaluated for true or false, the validation function will always execute.