Writers are a diverse bunch. Quirky. Independent. Opinionated. In other words, hard to buy for. If you are trapped in a relationship with a writer, get out. If you can’t, attempt to tame your writer with the liberal application of gifts they will appreciate. Here I have gathered a few ideas that range from classic to new-fangled. Each is sure to melt almost any writer’s dark, cold heart.
[amazon_link id=""0547055323"" target=""_blank"" ][/amazon_link] What writer doesn’t want to have their work end up in a “best” collection? Yes, even the ones who scoff at commercialism and popular opinion do. The Best American Short Stories series has been running for a good long time but the collections are kept fresh with yearly guest editors. My favorite feature of these books are the writer’s notes — insightful comments from the writers themselves about their stories. Though the notes
were more essential in the days before the Internet provided instantaneous transmission of a writer’s every 140-character-long thought, they still provide a worthwhile virtual mini-panel on the state of the art in short fiction. If your writer leans more toward genre fiction, check out other collections such as the venerable [amazon_link id=""0312608977"" target=""_blank"" ] Year’s Best Science Fiction[/amazon_link] .
[amazon_link id=""B002FQJT3Q"" target=""_blank"" ][/amazon_link] Digital publishing is an unstoppable freight train charging towards us. Get on board or get squashed to jelly beneath the steel wheels of progress. The Kindle is probably the cheapest and most hassle-free way to hop on board and see what all the fuss is about. The screen is a pleasure to read in bright light, and the smaller size Kindle adds nothing to the weight or bulk of your messenger bag. There are a few quirks. You can’t read in bad light (just like a book) — the screen does not produce any light on it’s own. The smaller Kindle is really too small to effectively display PDFs. If your writer spends a majority of their time squinting at screenplay PDFs on their laptop, then go for the [amazon_link id=""B002GYWHSQ"" target=""_blank"" ]Kindle DX[/amazon_link] .
[amazon_link id=""B00138CX30"" target=""_blank"" ][/amazon_link] Music to write by. Normally, writing music should be instrumental only — can’t have too many words competing for brainspace. But there is something very atmospheric about the tracks on Bob Dylan’s [amazon_link id=""B00138CX30"" target=""_blank"" ] Time Out of Mind[/amazon_link] and the vocals are subdued if plaintive. The track “Not Dark Yet” was featured in the ultimate writer movie, [amazon_link id=""B001ZS5CD6"" target=""_blank"" ]Wonder Boys[/amazon_link] If your writer’s work is filled with angst and wounded characters, this is the record to spin. For a more cinematic, epic, sweeping soundtrack, try [amazon_link id=""B003DUA56S"" target=""_blank"" ]Clash of the Titans[/amazon_link] . Terrible movie, good generic action-movie score.
[amazon_link id=""8883701127"" target=""_blank"" ][/amazon_link] Unassuming and built to last — we may live in the digital age, but when paper is called for the Moleskine notebook provides hundreds of durably bound, creamy off-white pages just asking to be filled with Great Ideas. The spine can be bent clear back on itself without breaking the binding or loosening a single page. The covers are stiff but flexible cardboard and covered with water-resistant oilcloth. Not flashy, but definitely classy. There’s a reason these things are almost a writer’s cliche.
[amazon_link id=""B000GTR2F6"" target=""_blank"" ][/amazon_link] Most writers juggle multiple hats. Writing often has to wait to the very end of the day. That, or it has to come first thing in the morning, long before any reasonable person would think of getting out of bed. It’s no wonder many writers, especially those first starting out, require a constant energy boost. I keep the [amazon_link id=""B000GTR2F6"" target=""_blank"" ]Keurig Platinum [/amazon_link] on my desk. It’s an essential piece of equipment, right alongside my printer and external hard drive. Making a fresh cup of coffee takes about one minute. Thanks to the self-contained filter cups, there is no mess to clean up. At all. Also good for tea, iced coffee, and provides instant hot water for hot cocoa or soup mix.
[amazon_link id=""B001TIJWKQ"" target=""_blank"" ][/amazon_link] And where is your writer supposed to put all the new awesome stuff you buy them? A briefcase is far too corporate and a backpack is far too Kindergarten. A writer has one foot in both these worlds and so does Crumpler. Witness the honestly named [amazon_link id=""B001TIJWKQ"" target=""_blank"" ]Considerable Embarrassment Laptop Bag[/amazon_link] . This bag holds a 15″ laptop with room left over for books, magazines, moleskins and other writerly essentials. Or step up to the even roomier [amazon_link id=""B001TN6S8K"" target=""_blank"" ]Dreadful Embarassment[/amazon_link] , meant
for 17″ laptops (always buy one size larger bag than you think you need). I’ve had a Crumpler camera bag for a couple of years and it’s proven to be tough, well-built and rock-solid.
Of course, if you really love your writer you might consider gifting them with a Crumpler bag stuffed with all the items mentioned here. Your writer may be confused by this strange new emotion called joy, but it would only be a matter of time before the Great American Novel/Screenplay/Haiku is produced.
Of course, if you really love your writer you might consider gifting them with a Crumpler bag stuffed with all the items mentioned here. Your writer may be confused by this strange new emotion called joy, but it would only be a matter of time before the Great American Novel/Screenplay/Haiku is produced.
}}} ",mdbitz Next Release,12118,wp_texturize converting x to × is too greedy,,Formatting,3.0,normal,normal,3.0,defect (bug),closed,needs-unit-tests,2010-02-03T00:39:49Z,2010-04-27T20:22:33Z,Converting x to × in wp_texturize() converts too much. Strings like 4x4 and 4x20=80 should be converted but there are a lot of times when x is in a model number such as rt2x00 where the character should not be converted to a multiplication symbol.,mtdewvirus Next Release,7988,wpautop p (paragraph) bug with div,,Formatting,2.7,normal,normal,,defect (bug),closed,needs-unit-tests,2008-10-28T13:25:17Z,2011-09-22T19:58:29Z,"As [http://comox.textdrive.com/pipermail/wp-hackers/2008-October/022307.html Jan Erik Moström pointed out on wp-hackers], wpautop mis-parses the following line: {{{text
([^<]+)\s*?(]*>)!', ""
$1
$2"", $pee);}}} This says that if a line has a {{{}}} tag, some non-markup stuff, perhaps some space, followed by a closing tag of {{{}}}, {{{}}}, or {{{}}}, then the {{{
}}} is orphaned and should add a closing tag ({{{
}}}) on the right of the non-markup stuff. The mistake that it makes is allowing it to enclose empty space in {{{}}}. It makes this mistake by allowing space characters to be considered as the non-markup stuff. My patch tells it not to do so by changing the above line to the following: {{{$pee = preg_replace('!([^<\s]+)\s*?(]*>)!', ""
$1
$2"", $pee);}}} ",filosofo Next Release,21767,Remove stripslashes from API functions,,Formatting,3.4,normal,normal,3.6,task (blessed),closed,needs-unit-tests,2012-09-02T03:14:56Z,2013-04-16T17:05:06Z,"This ticket attempts to bring consistency to the way slashes are handled throughout the WordPress API functions that persist data. Currently these API functions expect slashed data and strip slashes within their code. Most of the code that invokes these functions understands this and generally passes slashed data to them (sometimes calling `add_magic_quotes()` when necessary). Most of the code understands this, but not all. While auditing the code for the purposes of creating this patch I found a variety of places that do not slash data before passing it to the model functions as it currently should be done. Further, most developers do not think to manually add slashes to the data they programatically create and pass to these functions. Finally, it is not documented in the Codex that all data passed to these functions should be slashed before being passed in. As such, we can generally consider such behavior a bug. There are a few potential caveats, which I will cover shortly. Some of the functions that are being affected here: * wp_insert_post() * wp_update_post() * add_post_meta() [and other meta functions that call add_metadata()] * update_post_meta() [and other meta functions that call update_metadata()] * wp_insert_attachment() * wp_insert_term() * wp_update_term() * up_insert_user() * wp_update_user() * wp_new_comment() * etc... Point being, while it's cool that this stuff can work: {{{ update_post_meta($post->ID, 'key', $_POST['key']); }}} It's not worth the cost of losing data when someone quite reasonably does something like this: {{{ $post_data = array( 'post_status' => 'publish', 'post_type' => 'post', 'post_title' => 'This is my title', 'post_content' => 'Crazy with the backslashes \\\\\\', ); wp_insert_post($post_data); }}} With the current code they would instead need to do this (to not lose data): {{{ wp_insert_post( add_magic_quotes($post_data) ); }}} Developers just don't think to do this, and they shouldn't have to. Here's the real life example that got me diving into this: {{{ $my_api_data = get_twitter_data(); update_post_meta($post->ID, '_my_meta_key', $my_api_data); }}} The data I was saving was in JSON format. I was putting it in like this: {{{ {""profile_image_url"":""http:\/\/a0.twimg.com\/profile_images\/17084282\/alex_king_normal.jpg""} }}} and getting it back liks this: {{{ {""profile_image_url"":""http://a0.twimg.com/profile_images/17084282/alex_king_normal.jpg""} }}} As you can imagine, `json_decode()` fails on this data. The functions that do have examples around of passing $_POST data directly to it are the post meta functions. I think changing them might break a fair bit of custom code that is passing in slashed data. I've created `wp_update_post_meta()` and `wp_add_post_meta()` accordingly that do not expect slashed data and replaced all instances of `update_post_meta()` and `add_post_meta()` with these calls accordingly. It's possible that we may need to do a similar treatment of the other meta functions (user, comment, etc.). I haven't put anything in place for this in the current patch. One additional change that was needed was to the default kses filters on a few properties. wp-includes/default-filters.php {{{ // Strip, trim, kses, special chars for string saves foreach ( array( 'pre_term_name', 'pre_comment_author_name', 'pre_link_name', 'pre_link_target', 'pre_link_rel', 'pre_user_display_name', 'pre_user_first_name', 'pre_user_last_name', 'pre_user_nickname' ) as $filter ) { add_filter( $filter, 'sanitize_text_field' ); add_filter( $filter, 'wp_filter_kses' ); add_filter( $filter, '_wp_specialchars', 30 ); } }}} The `wp_filter_kses` filter has been replaced with `wp_kses_data` - thanks to @markjaquith for this tip here. I also applied this change to the filters initialized in wp-includes/kses.php: {{{ function kses_init_filters() { // Normal filtering add_filter('title_save_pre', 'wp_kses_data'); // Comment filtering if ( current_user_can( 'unfiltered_html' ) ) add_filter( 'pre_comment_content', 'wp_kses_data' ); else add_filter( 'pre_comment_content', 'wp_kses_data' ); // Post filtering add_filter('content_save_pre', 'wp_kses_data'); add_filter('excerpt_save_pre', 'wp_kses_data'); add_filter('content_filtered_save_pre', 'wp_kses_data'); } }}} As this has security implications, it could use extra review and testing. I changed `wp_rel_nofollow()` to no longer strip slashes then add them again (and it was adding them wrong, via a call to `esc_sql()`). Now you can pass unslashed strings to `wp_rel_nofollow()` without losing data as well. I have not thoroughly tested XMLRPC calls yet, that is definitely a needed next step. The `escape()` method within the XMLRPC code looks hinky to me, likely some changes (as well as thorough testing )are needed there. Obviously, this is a big change. I've done my best to test appropriately. I've tested via the admin UI and with simple code examples (attached) and so far things look good. Unit tests that exercise various slash conditions across all objects would be another smart addition to the mix. Related: #18322, #20569 Whew! I think that's it for now - when you find something that breaks, please comment accordingly so it can be fixed/discussed. I expect there are likely a few edge cases I missed, but it's definitely time to get more eyeballs on this (as well as help testing).",alexkingorg Next Release,3362,Missingtag from
(as well as extra
sometimes) invalidates xhtml,,General,2.0.5,normal,normal,,defect (bug),closed,needs-unit-tests,2006-11-16T20:46:58Z,2011-09-22T19:59:57Z,"Wordpress 2.0.5 always seems to miss off the openingtag inside a
(and if it is embedded in text adds a
tag before the) which invalidates XHTML The following text (with a break before the blockquote): Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:
"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."Text after block quote that doesn't go on and on.
becomes:Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:
"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."Text after block quote that doesn’t go on and on.
With a blockquote at the beginning (and no break character before):"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."Text after block quote that doesn't go on and on.
Just separated by some break characters becomes:"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."Text after block quote that doesn’t go on and on.
Just separated by some break characters
Text before blockquote (with a break before the quote): Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:
"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."becomes:Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:
"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."Blockquote at the end (without a break before the quote): Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."becomes:Text before blockquote that goes on and on and on and on and on and on and on and on and on and on and on and on and on and on and on:
"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."Blockquote on its own:"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."becomes"Text withing blockquote that also goes on and on and on and on and on and on and on and on and on."",upekshapriya Next Release,22473,Post-formats radiogroup on custom post types and pages will not update in 3.5 Beta 3,ryan,General,3.5,normal,normal,3.5,defect (bug),closed,needs-unit-tests,2012-11-16T08:14:55Z,2012-11-20T18:31:06Z,"The post-formats are being saved, but the radiogroup will not show selected format after publishing, but stays checked at Standard post-format. Works only on posts.",itworx Next Release,9246,Wordpress cannot update '.htaccess' even though it is writable,westi,General,2.7.1,normal,normal,2.8,defect (bug),closed,needs-unit-tests,2009-02-28T01:15:25Z,2009-08-17T07:52:17Z,"I have attached a patch which fixes the problem. Here are some details: The culprit function was {{{get_home_path()}}} in file {{{wordpress/wp-admin/includes/file.php}}}. The path to {{{.htaccess}}} was turning out to be: {{{ /u/akshay/public_html/wordpress/wp-admin/options-permalink.php/~akshay/.htaccess }}} when it actually should be: {{{ /u/akshay/public_html/.htaccess }}} The reason was that this call was not returning the correct result: {{{ $root = str_replace( $_SERVER[""PHP_SELF""], '', $_SERVER[""SCRIPT_FILENAME""] ); }}} because {{{$_SERVER[""PHP_SELF""]}}} had the value {{{ /~akshay/wordpress/wp-admin/options-permalink.php }}} and {{{$_SERVER[""SCRIPT_FILENAME""]}}} had the value {{{ /u/akshay/public_html/wordpress/wp-admin/options-permalink.php }}} The main problem was that the path manipulation functions did not consider the presence of {{{/~username}}}. My blog URL is {{{http://web.cecs.pdx.edu/~akshay}}}, which is why the path in {{{PHP_SELF}}} was formed the way it was. I have attached a fix which I hope is generic enough to work. Let me know if it is not (in which case, I would need some hints on how to fix it). The patch is attached. ",akd907 Next Release,20412,add_query_arg() doesn't work with already exisitng CGI vars,,General,3.3.1,normal,normal,,defect (bug),closed,needs-unit-tests,2012-04-10T18:06:18Z,2012-04-10T18:24:05Z,"add_query_arg('filter', '125', '/project/?lang=en') returns /project/?lang=en&filter=125?lang=en (with two lang=en).",porton Next Release,7688,get_children not working,,General,2.6,normal,normal,,defect (bug),closed,needs-unit-tests,2008-09-04T17:48:31Z,2011-09-22T20:00:25Z,"in version 2.6 get children is not acting the same as 2.5.1 $mykids is totally empty and page 19 has children that are showing up as such in the raw $post array",security_man Next Release,7326,get_posts not working properly,pyadav,General,2.6,high,blocker,2.6.2,defect (bug),closed,needs-unit-tests,2008-07-16T21:47:40Z,2011-09-22T19:57:05Z,"Here's an example of a get_posts code block that doesn't work. I don't think any get_posts queries are working. ",wpcandy Next Release,20434,cURL fails to follow redirects sometimes,ryan,HTTP,3.4,high,critical,3.4,defect (bug),closed,needs-unit-tests,2012-04-13T08:24:35Z,2012-05-10T21:33:17Z,"r20208 changed the way WP_HTTP (specifically cURL) handles redirects, and as a result broke the way it handles some redirects (both 301 and 302) that were previously working. It doesn't fail on all 301/302 redirects. At first I thought it failed only for requests with more than 1 redirect, but in testing with the Quantcast top 100 lists (assuming these sites should have no problems loading usually) I found an exception to that rule in http://facebook.com, which works and has 2 redirects. Then I thought it only failed for requests with more than 1 301 redirect, but I found an exception to that in http://dailymotion.com, which fails and only has 1 301 redirect (and a 302). Here are a couple examples that fail using wp_remote_get(): http://skype.com, http://microsoft.com, http://dailymotion.com, Here are a couple from the same list that work (and go through redirects): http://google.com, http://facebook.com, http://yahoo.com As of r20208 wp_remote_get() returns empty arrays and strings for headers, body, response, etc. As of r20370 the same failed requests return a WP_Error object with an error code of 'http_request_failed' and an error message of ' malformed' (including the leading space). As of r20460 the same WP_Error objects are still returned.",evansolomon Next Release,19033,"Problem with Hebrew letter ""Nun"" hiding search results",shir.gans@…,I18N,3.2.1,normal,critical,3.4,defect (bug),closed,needs-unit-tests,2011-10-24T08:48:57Z,2012-02-08T15:35:23Z,"In the hebrew installation, when trying to search to website for words with the letter Nun ( נ ), no results found. There was a related problem on an earlier version of wordpress with the same letter, please see ticket here: [http://core.trac.wordpress.org/ticket/11669] Please try to search on this site, the words (נתן, קושניר, אנטולי) which all has the letter נ . no results found, while all names are appears in the site. [http://www.pat.co.il/shirg/comm-it.co.il/he/] We need fix/patch ASAP. Thank you.",shirgans Next Release,10619,Importing WXR breaks serialized postmeta value,westi,Import,2.8.4,normal,normal,3.0,defect (bug),closed,needs-unit-tests,2009-08-14T18:51:07Z,2009-12-22T17:05:53Z,"Because custom field values are passed through the poorly named maybe_serialize() when importing, any values that already contain serialized strings are serialized again, making them useless. Although it would make more sense to me to eliminate the bizarre behavior of maybe_serialize() that may break something else, so I fixed this problem by turning off maybe_serialize() for WXR import.",JonathanRogers Next Release,11354,WordPress Importer duplicates categories,,Import,,normal,normal,3.1,defect (bug),closed,needs-unit-tests,2009-12-07T22:24:50Z,2010-10-25T21:31:38Z,"The WordPress importer duplicates categories. This only seems to affect child categories. To reproduce, get an export file that has parent and children categories. Run the importer multiple times with the same file. View the category screen under Posts->Categories, you should see duplicated child categories. I've included a patch for the process_categories() method that fixes this by explicitly checking if each category_exists(). I've included the same patch for process_tags() method. Tags do not duplicate, but wp_insert_term() is called without checking if the tag exists.",briancolinger Next Release,9870,Fix for WP_Dependencies::dequeue,azaozz,JavaScript,2.8,normal,normal,2.9,defect (bug),closed,needs-unit-tests,2009-05-19T03:56:02Z,2009-10-18T05:51:34Z,"The WP_Dependencies::dequeue method has three major flaws that prevent it from working: does not split handle around '?' to divide handle from arg (see the WP_Dependencies::enqueue method), tries to remove the handle from the queue array by using the handle as an index of the array when the handle is a value of the array, and does not remove a relevant entry from the args array if the handle has an arg. The provided patch (wp-dependencies-patch.txt) was tested with 2.8-beta1-11389 and corrected all three issues.",chrisbliss18 Next Release,23706,Image metadata encoding problem,,Media,3.0,normal,normal,3.6,defect (bug),new,needs-unit-tests,2013-03-06T17:05:43Z,2013-03-07T19:09:32Z,"I uploaded picture DSCF4480.jpg (attached for testing). Metadata for title and caption should be the same: ""Bystřice u Benešova"". But after upload title is right, but caption is damaged: {{{ 'caption' => 'Bystøice u Beneova', 'title' => 'Bystřice u Benešova' }}} Using latest trunk.",pavelevap Next Release,22181,image_make_intermediate_size in wp-includes/media.php always returns FALSE,markoheijnen,Media,3.5,normal,major,3.5,defect (bug),closed,needs-unit-tests,2012-10-13T05:45:42Z,2012-10-15T20:55:47Z,"Found this when one of my theme user running 3.5 reported problem with thumbnails. http://swiftthemes.com/forums/showthread.php?1958-here-we-go-again-thumbnail-featured-pics-dont-work-in-latest-build-of-wordpress&goto=newpost#post7055 In the following function, if statement is followed by a ;, so this always returns false. {{{ function image_make_intermediate_size( $file, $width, $height, $crop = false ) { if ( $width || $height ) { $editor = WP_Image_Editor::get_instance( $file ); if ( is_wp_error( $editor ) || is_wp_error( $editor->resize( $width, $height, $crop ) ) ); return false; $resized_file = $editor->save(); if ( ! is_wp_error( $resized_file ) && $resized_file ) { unset( $resized_file['path'] ); return $resized_file; } } return false; } }}} ",gandham Next Release,18034,Incorrect URL for second page of search results,nacin,Multisite,3.2,normal,normal,3.5,defect (bug),closed,needs-unit-tests,2011-07-08T08:28:09Z,2012-06-28T20:54:21Z,"I enter the Search Term (uptime) into search box in Adminbar First page of results shows up fine at :-[[BR]] https://domain.tld/blogname?s=uptime Link to second page of search results shows blogname '''repeated''' :-[[BR]] https://domain.tld/blogname/blogname/page/2/?s=uptime If I edit the URL manually and visit :-[[BR]] https://domain.tld/blogname/page/2/?s=uptime it works fine. Link to the third page of search results shows fine too :-[[BR]] https://domain.tld/blogname/page/3/?s=uptime Also fourth and fifth pages are OK. Regular page links are fine :-[[BR]] https://domain.tld/blogname/page/2/ I have tested on three different blogs hosted on this multisite.[[BR]] Changed themes (P2 and Twenty Eleven), same results.[[BR]] Tested with Firefox and Chrome browsers.",mark.waters Next Release,16200,Multisite can't find site /foo at /FOO (gives 404),markjaquith,Multisite,3.1,normal,normal,3.5,defect (bug),closed,needs-unit-tests,2011-01-12T13:36:32Z,2012-12-05T17:52:17Z,"Wordpress 3.0.4 and 3.1RC2 - multisite with subfolder installs. Create a site at mysite.com/foo and a page on it at mysite.com/foo/about Works as expected: mysite.com/FOO/about goes to mysite.com/foo/about mysite.com/foo loads foo's home page Doesn't work as expected: mysite.com/FOO loads foo's theme and gives a 404 So, it's only for the home page of a site on a multisite network that is addressed with a different capitalization scheme than the original. going to any subpages works fine.",Madtownlems Next Release,23073,Wrong RewriteRule in a local Multisite installation,markjaquith,Multisite,3.5,normal,normal,3.5.1,defect (bug),closed,needs-unit-tests,2012-12-28T21:59:47Z,2013-01-17T04:01:42Z,"- WampServer on Windows 8 - Install Wordpress in a subdirectory of the document root(here a directory ""multitest"") - Setup multisite in subfolder mode. Rules displayed for .htaccess in the wordpress textarea of the network page are: {{{ RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) c:\wamp\www\multitest/$2 [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ c:\wamp\www\multitest/$2 [L] }}} Result in the browser window of a subsite admin board is an error: Forbidden You don't have permission to access /multitest/C:wampwwwmultitest/wp-admin/ on this server. For the subsite itself, at least paths for css are broken. RewriteRules should be: {{{ RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) /multitest/$2 [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ /multitest/$2 [L] }}} Looking at code source in network.php, I fixed it for my personal use by adding: $rewrite_base = $base; before the htaccess code is displayed to users. This could be done with local multisite installation only. ",Guy_fr Next Release,18592,add trailingslashit to BLOGUPLOADDIR in ms-files.php,nacin,Multisite,3.3,normal,normal,3.3,defect (bug),closed,needs-unit-tests,2011-09-05T09:02:40Z,2011-09-06T15:41:57Z,"BLOGUPLOADDIR is trailingslashit'd inconsistently - since this value can be set by the user, adding trailingslashit to the constant value in ms-files.php will prevent broken images in sub-blogs when in Multisite mode {{{ // WRONG define( 'BLOGUPLOADDIR', $_SERVER['DOCUMENT_ROOT'] . ""/blogs.dir/{$the_id}/files"" ); // RIGHT define( 'BLOGUPLOADDIR', $_SERVER['DOCUMENT_ROOT'] . ""/blogs.dir/{$the_id}/files/"" ); // CURRENT $file = BLOGUPLOADDIR . str_replace( '..', '', $_GET[ 'file' ] ); // PROPOSED $file = trailingslashit( BLOGUPLOADDIR ) . str_replace( '..', '', $_GET[ 'file' ] ); }}} It's subtle, and hard to debug",wonderboymusic Next Release,23192,Use get_user_by() in is_user_spammy(),SergeyBiryukov,Multisite,,normal,normal,3.6,enhancement,closed,needs-unit-tests,2013-01-13T19:25:18Z,2013-02-15T18:13:19Z,"Comes up after reading #23190. Since `is_user_spammy` expects a user name, we should replace `get_user_id_from_string( $username )` with `get_user_by( 'login', $username )`. Same for the id.",ocean90 Next Release,21181,simplify and add filter to is_upload_space_available,westi,Multisite,3.4.1,normal,normal,3.5,enhancement,closed,needs-unit-tests,2012-07-06T21:06:52Z,2012-10-18T13:00:09Z,add a filter to the return value of is_upload_space_available in instances (such as on WordPress.com) when upload_space_check_disabled is set to true but an upload quota still exists.,jkudish Next Release,21600,Reduce calls to sanitize_title_with_dashes in register_(post_type|taxonomy),ryan,Performance,,normal,normal,3.5,defect (bug),closed,needs-unit-tests,2012-08-15T19:24:20Z,2012-08-20T17:25:07Z,"Follow-up: #21593 If #21593 goes in, the post type/taxonomy name is already sanitized with `sanitize_key()` and shouldn't go through `sanitize_title_with_dashes()` again.",ocean90 Next Release,14348,"If it's a HEAD request, stop after the head!",markjaquith,Performance,3.0,normal,normal,3.5,enhancement,closed,needs-unit-tests,2010-07-19T02:31:27Z,2012-10-31T23:01:14Z,"Right now, as far as I can tell, when a HTTP HEAD request is made against WordPress, we go ahead and produce the entire page content, only to have it ignored. Attached is a patch to repair this. While not a huge issue, if you happen to receive lots of HEAD requests, this can make a large difference, as each HEAD request will be much faster and not waste precious resources. I have tried to ensure that this patch, by being in send_headers, will produce a HEAD response functionally identical to the response header of GET/POST requests, as it should be.",mitchoyoshitaka Next Release,15458,Lazy-load usermeta into the user object,nacin,Performance,,normal,normal,3.3,enhancement,closed,needs-unit-tests,2010-11-17T22:47:30Z,2011-12-18T16:28:20Z,"Currently we load all usermeta keys into the user object. This is not ideal, and it doesn't scale when you wish to store a lot of data in usermeta. (Example, BuddyPress profiles.) We can leverage a magic `__get()` method for WP_User and fetch data on demand, instead of our current situation.",nacin Next Release,10853,improve get_page_hierarchy,,Performance,2.8.4,normal,normal,3.0,enhancement,closed,needs-unit-tests,2009-09-25T23:34:12Z,2013-02-18T19:12:31Z,"current get_page_hierarchy has O(N*N) complexity. It is super slow when N is a few thousands. We should improve this to O(N) using techniques similar to #10852. ",hailin Next Release,21970,404 error when a post has the same slug as with a deleted (trash) page.,,Permalinks,3.4.2,normal,normal,3.6,defect (bug),new,needs-unit-tests,2012-09-22T20:25:04Z,2013-04-23T20:14:25Z,"I don't know if this is a bug/issue but I'll share this anyway. A user creates a new '''Page''', for example, with a title ""New Garden"". But decides to delete it/""Move to Trash"" without deleting it permanently. Then creates a new '''Post''' with the same title ""New Garden"". Viewing that post will result to a ""404"" page not found.",janintia Next Release,13459,Conflict between post and page slugs/permalinks when permalink setting is set to /%postname%/,ryan,Permalinks,2.9.2,normal,normal,3.6,defect (bug),new,needs-unit-tests,2010-05-20T04:56:27Z,2013-03-03T03:01:45Z,"If Dashboard -> Settings -> Permalinks is set to /%postname%/, it is possible to create both a page and a post with the same slug. When viewing via the frontend, the page is always displayed. I would have thought that WordPress should prevent a post and a page from having the same permalink. Steps to reproduce: 1. Create and publish a page with any slug. eg. http://domain.com/test/. 2. Create and publish a blog post with the same slug. Wordpress says the permalink for the blog post is http://domain.com/test/, but when you visit that URL it displays the page instead. I can reproduce this on my 2.9.2 install, as well as 3.0 trunk. I'm guessing the bug is present in earlier versions of WordPress as well. Possibly related: #11863",jamescollins Next Release,9064,URLs with commas are not pinged,,Pings/Trackbacks,2.7,high,major,3.6,defect (bug),new,needs-unit-tests,2009-02-07T11:07:20Z,2013-02-17T02:29:45Z,"I use following permalink format on my blog:[[BR]] /%category%/%postname%,%post_id%[[BR]] Unfortunately Wordpress doesn't ping them correctly - URLs extracted from post content don't have suffix with comma and post id.[[BR]] [[BR]] Fix: in file wp-includes/comment.php change line 1400 from:[[BR]] $punc = '.:?\-'; [[BR]] to:[[BR]] $punc = '.:?\-,'; ",sirzooro Next Release,17817,do_action/apply_filters/etc. recursion on same filter kills underlying call,,Plugins,3.4.1,normal,normal,3.6,defect (bug),reopened,needs-unit-tests,2011-06-16T18:04:04Z,2013-05-17T10:24:15Z,"Affects @wp-includes/plugin.php: do_action, do_action_ref_array, apply_filters, apply_filters_ref_array, _wp_call_all_hook When calling a specific hook from a function that was called through that same hook, the remaining hooked functions from the first iteration will be discarded.[[BR]] This is due to the handling of the array of registered functions using internal array pointers instead of a more robust approach. In my example, this problem arose when I tried to programmatically delete a menu in reaction to the removal of a category. I hooked into the delete_term action to do so, upon which another function hooked into delete_term would no longer fire.[[BR]] The obvious workaround is to adjust the priorities accordingly, but it shouldn't be necessary. The current implementation as in apply_filters is: {{{ reset( $wp_filter[ $tag ] ); if ( empty($args) ) $args = func_get_args(); do { foreach( (array) current($wp_filter[$tag]) as $the_ ) if ( !is_null($the_['function']) ){ $args[1] = $value; $value = call_user_func_array($the_['function'], array_slice($args, 1, (int) $the_['accepted_args'])); } } while ( next($wp_filter[$tag]) !== false ); }}} Using the following method instead, both iterations would develop properly: {{{ if ( empty($args) ) $args = func_get_args(); foreach ( $wp_filter[$tag] as $filters ) foreach( (array) $filters as $the_ ) if ( !is_null($the_['function']) ){ $args[1] = $value; $value = call_user_func_array($the_['function'], array_slice($args, 1, (int) $the_['accepted_args'])); } }}}",kernfel Next Release,24159,Chats with spaces in the 'speaker' not parsing correctly,,Post Formats,trunk,normal,major,3.6,defect (bug),new,needs-unit-tests,2013-04-22T17:37:04Z,2013-05-17T22:53:29Z,"Since #23625 is closed and we were asked to make a new ticket, the issue I mentioned still remains. Related to #23947 - currently this is broken in instances where chat names have spaces. http://test.ipstenu.org/testing-1.2013/ That has the post content as follows: {{{ Nigel Tufnel: The numbers all go to eleven. Look, right across the board, eleven, eleven, eleven and… Marti DiBergi: Oh, I see. And most amps go up to ten? Nigel Tufnel: Exactly. Marti DiBergi: Does that mean it’s louder? Is it any louder? Nigel Tufnel: Well, it’s one louder, isn’t it? It’s not ten. You see, most blokes, you know, will be playing at ten. You’re on ten here, all the way up, all the way up, all the way up, you’re on ten on your guitar. Where can you go from there? Where? Marti DiBergi: I don’t know. Nigel Tufnel: Nowhere. Exactly. What we do is, if we need that extra push over the cliff, you know what we do? Marti DiBergi: Put it up to eleven. Nigel Tufnel: Eleven. Exactly. One louder. Marti DiBergi: Why don’t you just make ten louder and make ten be the top number and make that a little louder? Nigel Tufnel: These go to eleven. }}} But nothing shows. You can see the exact same issue here: http://twentythirteendemo.wordpress.com/2013/02/10/never-say-never-say-never/ James Bond's lines are never shown.",Ipstenu Next Release,23572,Add functions to parse Audio / Video data out of arbitrary content or a post,markjaquith,Post Formats,,normal,normal,3.6,enhancement,closed,needs-unit-tests,2013-02-21T06:34:57Z,2013-04-12T18:02:53Z,"= Scenarios == Audio After realizing that a post has a format of audio but no metadata for audio: - Theme does not support Audio, but the content contains an