I keep the default themes in place, and keep them updated. The WordPress Foundation will keep those themes updated with any security issues, so as long as you keep them updated on your site, I’m not concerned with security problems. The advantage that you have by keeping them is for testing. When you are troubleshooting … Read more
Siege. Test against both an actual post/page (which would theoretically hit page cache, APC, varnish, etc. for every request after the first request), and against a 404 (e.g., randomly generated strings), which would require database queries on each hit. A few helpful flags: -b benchmark (don’t wait between requests) -c N where N is the … Read more
This codex page explains it pretty well I think. The most important and commonly used function is probably esc_attr. Take this example: <a href=”https://wordpress.stackexchange.com/questions/48660/<?php print $author_url; ?>” title=”<?php print $author_name; ?>”> <?php print $author_name; ?> </a> If $author_name contains a ” character you get your attribute closed, and if that character is followed by onclick=”do_something();” … Read more
I did battle with a similar situation recently. Ajax in widgets is no joke! Need to write some pretty crazy code to get things to work across instances. I’m not familiar with live query, but if you say it checks the DOM every second, I might have a less intense solution for you: var get_widget_id … Read more
If memory serves, Drupal’s lead dev summed things up like so last summer: Drupal is, on the UI front, where WP was 3 years ago; and WP is, on the feature front, where Drupal was 3 years ago. My own experience with WP and Drupal are basically so: WP has a prettier/easier UI. Drupal is … Read more
I would abstract the specific SOAP library away, so you can add support for more clients later. Similar to how WP_Http is a proxy for multiple HTTP implementations, and chooses depending on the server capabilities. I must have played with some of these libraries before but I don’t remember which one. In general I prefer … Read more
There’s a few bits here that apply, but the short of it is this code in customize-preview.js: this.body.on( ‘click.preview’, ‘a’, function( event ) { event.preventDefault(); self.send( ‘scroll’, 0 ); self.send( ‘url’, $(this).prop(‘href’) ); }); The event.preventDefault prevents the links from actually working. The following code then sends a message back upwards telling it to a) … Read more
This plugin demonstrates how to do it. Of note, the steps involved are: Register each setting to update/change When creating the control, pass an array as the setting argument When rendering the inputs, pass in the settings key to link and value The settings key is not the name of the setting, but the indices … Read more
I gave a +1 to the @webtoure’s answer because it gives you the right direction, however I think it lacks some checks. First of all it does not check that the theme that’s being activated is a child theme, and does not check that the theme previously active is the parent theme of the child … Read more
Overriding that template would be much easier than getting rid of it. Just the way logic goes. I make no claim it’s efficient idea (late here), but this would get it nuked from edit screen: add_action(‘admin_head-post.php’,’remove_template’); function remove_template() { global $wp_themes; get_themes(); $templates = &$wp_themes[‘Twenty Ten’][‘Template Files’]; $template = trailingslashit( TEMPLATEPATH ).’onecolumn-page.php’; $key = array_search($template, … Read more