I use Ozh’ Tweet Archiver to keep a local copy of my tweets, but I wanted to use the new Twitter oEmbed output to easily format my tweets as _tweets_, rather than just a status.
I’ve been circling this drain for years trying to make things just right.
This could be handy if you are importing blog posts from Tumblr, links from Delicious, and tweets from Twitter.
This was tricky and took me several attempts to figure out how to gracefully remove posts in a specified category from the public BuddyPress Activity Stream. Proposed solutions took the approach of stopping the activity from being added to the table; however, this raised issues when an existing post was updated and put in the excluded category, and also when an excluded post was updated to no longer be in the excluded category. Additionally, these posts were not included in the author’s individual Activity Stream, which led to further confusion.
I had to move `bp_blogs_record_post` from `save_post` to `wp_insert_post` to allow `_save_post_hook` to clean the post cache prior to running `in_category()`.
I figured this was more useful as a plugin than as a gist. [BuddyPress Sitewide Notice Widget](http://wordpress.org/extend/plugins/buddypress-sitewide-notice-widget/) is available from the WordPress Plugin Directory.
Curly quotes are a particular nuisance, especially in incoming posts. This function removes them before the post (or comment) is inserted in the database. If an older post containing curly quotes is edited, it will save with straight quotes upon database insert.
In the default state, `wp_nav_menu()` classes for `li` elements are useful as CSS and JS selectors, but are not human-friendly. I prefer to use selectors like `.menu-item-archives` instead of `.menu-item-38008`. This function creates a human-readable class on the `li` elements generated by `wp_nav_menu()`.
In a WordPress multisite installation, users were customizing their meta box configuration in the Screen Options tab (including boxes for various plugins) and having the settings disappear[^1][^2] between sites because WPMS has per user–not per user, per site–options for customizing the Dashboard and Screen Options.
I ended up writing the following plugin to create a series of shadow screen options for each user. This is reasonable on multisite installs with a finite number of users and blogs. If you are not concerned with the number of rows added per user, per blog, then this will allow your users to set Screen Options on a per blog basis. This is especially relevant on multisite installs where blogs have different uses and the active plugin set differs between blogs. Screen Options for plugin-generated meta boxes will be saved on a per site basis for each user, allowing them to retain their Add New/Edit Post appearance on each separate blog.
[Shadow Screen Options](http://wordpress.org/extend/plugins/shadow-screen-options/)
[^1]: [Per user screen options overwrite per site custom meta boxes](http://wordpress.org/support/topic/per-user-screen-options-overwrite-per-site-custom-meta-boxes)
[^2]: [Screen options and meta box settings can lose per-blog meta box positions](http://core.trac.wordpress.org/ticket/17370)
Between WordPress 3.0 and WordPress 3.1, code was added to change certain characters in image captions into their HTML/ASCII character code equivalents. However, some people like to include links in captions, and this new filter broke that ability by swapping valid link code (albeit with strict limitations on the use of single and double quote characters) for HTML characters.
The serving of static image files by `ms-files.php` can be problematic with some server setups, especially those that are using nginx to serve static files. I wrote the following to deal with uploaded files in situations where I don’t care about masking the actual location of the images.