` wrapper for it but with no Page Title it is not being displayed. If this is by design I think it should be revisited and if this is a defect then the included patch (not very pretty) may offer a possible solution or at least a consideration.
The patch checks if the Page Title is empty and if it is uses the Page ID as the title.",cais
23295,Improved login expiration warning,,Autosave,,normal,normal,3.6,task (blessed),new,has-patch,2013-01-25T22:49:45Z,2013-05-16T03:47:09Z,"The goal here is to improve the user experience when your login has / will expire, as discussed in [http://make.wordpress.org/core/2013/01/07/wordpress-3-6-autosave-and-post-locking/ WordPress 3.6: Autosave and Post Locking] and the [http://make.wordpress.org/core/2013/01/25/agenda-for-todays-autosave-and-post-locking-team/ autosave and post locking team meeting in IRC].
The suggested tactic is to integrate the [https://github.com/Penske-Media-Corp/pmc-post-savior/ PMC Post Savior] plugin into core. That part should be pretty straightforward.
I think 3 valuable enhancements that are on the plugin's roadmap, but not yet complete would be:
* Alert properly on failed requests and lost connectivity. If my internet connection has gone down and I'm still working, I should be alerted that I'm ""Working offline"" and my changes aren't being automatically saved. I don't think this should be a blocking UI, but it should be obvious.
* Block publish/save until login has been verified. Polling duration can be decreased (or maybe even done away with entirely) if we block the Publish/Save/etc actions until we've verified the user's cookie.
* Pre-emptive notification. When approaching the user's login cookie expiration time, say 1 hour before, display a message and allow the user to extend their login. For example, how banking sites notify you when you've been inactive too long and they're about to log you out.",mintindeed
23472,Retrieve the first x bytes of a remote file,,HTTP,,normal,normal,3.6,enhancement,new,has-patch,2013-02-14T01:31:02Z,2013-05-16T12:09:48Z,"A commonly useful functionality in HTTP clients is to only request the first x bytes of a document, this can be useful for example, when you only need to fetch the first few KB of a image so as to determine it's dimensions from the initial metadata in the file.
At present, we have no way to offer this through WP_HTTP, The attached patch is a first-scratch effort at adding it. No proper unit tests so far, just casual testing which confirms it working.
Patch
* Supports all 3 transports
* Handles streaming-to-file as well
* Doesn't include Headers in the byte count
* Works with Redirects
I'll add some Unit tests for this soon hopefully.",dd32
23312,Post Lock Interface for Post List Screen,,Autosave,,normal,normal,3.6,task (blessed),new,has-patch,2013-01-29T03:17:36Z,2013-05-16T15:04:13Z,"For 3.6, we'd like to improve the experience for users with post locks!
For the Post List screen, we'd like to:
- Make it easy for users to tell which posts are locked directly from the post list screen.
- Realtime lock update using Heartbeat API (#23216)
Maybe:
- Make it visible which user holds the lock
- Meta editing allowed while post is locked
",dh-shredder
24269,Twenty Thirteen: Remove twentythirteen_search_form_format(),,Bundled Theme,trunk,normal,normal,3.6,enhancement,new,has-patch,2013-05-06T11:24:32Z,2013-05-16T17:12:49Z,"Per [comment:ticket:23850:19], we can replace `twentythirteen_search_form_format()` with an `add_theme_support()` call once the latest patch is committed.",SergeyBiryukov
24056,Revisions: UI a bit unusable when you have ALOT of revisions,,Revisions,trunk,highest omg bbq,blocker,3.6,defect (bug),new,,2013-04-12T04:35:28Z,2013-05-16T19:33:28Z,"It could be a good idea to limit to last 25 or 50 revisions in the new UI.
I came across an extreme example of this on a WordPress.com site today, where I have something like 130 revisions for the Custom CSS post type. But, this same issue could apply to core post types, though—posts and pages—if the number is high enough.
When I loaded the revisions page, the ""calculating revision diffs"" message rans for a few minutes, and then ""arrow"" to move with was moved way off the screen to the right, creating a horizontal scrollbar.
The next and previous buttons are obscured by the long scrubber timeline graphic.
Screenshot attached.",lancewillett
24346,Revisions reloading all comparisons in two handle mode instead of just available comparisons,,Revisions,trunk,normal,normal,3.6,defect (bug),new,has-patch,2013-05-15T19:41:23Z,2013-05-16T22:09:05Z,"as ahoereth pointed out, see [http://www.screenr.com/vAI7 screencast], all comparisons were reloading after moving one handle; instead, only possible positions for the opposite handle need to be reloaded.
",adamsilverstein
23801,Audio Shortcode: MP3s Display above plain text.,,Shortcodes,trunk,normal,normal,3.6,defect (bug),new,,2013-03-17T03:40:30Z,2013-05-16T22:45:40Z,"MP3's render above text and inline elements that have been entered immediately before.
To reproduce, insert the following content using the HTML editor:
{{{
Just some text up here ...
[audio mp3=""http://wp-content/uploads/2013/03/mp3-hello.mp3""][/audio]
}}}
Something similar to the following should be rendered on the front-end:
{{{
...
Just some text up here ...
}}}
I've tested similar content using both OGG and WAV file types. These files are not effected by the bug. Only MP3s seem to render above paragraphs.
This only seems to occur with the shortcode, I've tested a url on it's own line and it displays correctly:
{{{
Just some text up here ...
http://wp-content/uploads/2013/03/mp3-hello.mp3
}}}
",mfields
23205,New Media Uploader slow for sites with many images,,Media,3.5,normal,normal,3.6,enhancement,new,dev-feedback,2013-01-15T17:17:02Z,2013-05-17T08:11:21Z,"The new media uploader added in 3.5 looks very nice. Unfortunately, its functionality is worse for sites with thousands of images. I think this can be combated by allowing us to select the ""Upload Files"" page as our default after clicking ""Add Media,"" and rather than ""All Media Items"" be the page it jumps to after the image is uploaded, instead have it jump to ""Uploaded to this Post."" Is there any way the WordPress team can make this default? Or add the option to make it default? It's made posting on my site 10 times more annoying, especially for those posts with 40-50 images. And I'm sure there are others who feel the same.",salromano
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
24326,Admin RTL bugs,,RTL,trunk,normal,normal,3.6,defect (bug),new,has-patch,2013-05-12T18:22:37Z,2013-05-17T16:30:45Z,"Hi, This a list of some RTL style bugs I found it today in the beta 3 update.",alex-ye
24327,'Add Media' and Title should show for all formats if Post Formats UI is disabled,,Post Formats,trunk,high,normal,3.6,defect (bug),new,dev-feedback,2013-05-13T05:06:13Z,2013-05-17T17:31:51Z,"In [24037] and [24098], we opted to hide the 'Add Media' button for the Aside, Status, Image, Video, and Audio formats in lieu of their respective UIs.
However, if the Post Formats UI is deactivated through either the screen option, the filter, or lack of post_type support, the 'Add Media' button should show as before, assuming the user has the correct capabilities.",DrewAPicture
24306,Twenty Thirteen: border-box box sizing will break many plugins,,Bundled Theme,trunk,normal,normal,3.6,defect (bug),new,,2013-05-10T17:14:19Z,2013-05-17T17:48:25Z,"WordPress 3.6-beta2-24227
/wp-content/themes/twentythirteen/style.css
{{{
* {
-moz-box-sizing: border-box;
}
}}}
The setting of box-sizing to border-box for all elements rather than the default content-box (as used for twentyten, twentyeleven, and twentytwelve themes) will break the styling of many plugins for Firefox.
Strange that this is only done for firefox and the default setting of content-box is used for other browsers.
Suggest this css property be only used only the elements that need it in conjunction with the CSS3 box-sizing property and other browser equivalents.
Andy Bruin
",professor99
24202,Self-explanatory argument values for new media functions,,Media,trunk,high,major,3.6,enhancement,new,dev-feedback,2013-04-26T13:14:52Z,2013-05-17T19:43:58Z,"We've introduced a bunch of functions, some with a relatively long list of arguments, which accept booleans:
{{{
function get_content_media( $type, &$content, $html = true, $remove = false, $limit = 0 )
function get_embedded_media( $type, &$content, $remove = false, $limit = 0 )
function get_content_audio( &$content, $html = true, $remove = false )
function get_embedded_audio( &$content, $remove = false )
function get_content_video( &$content, $html = true, $remove = false )
function get_embedded_video( &$content, $remove = false )
function get_content_images( &$content, $html = true, $remove = false, $limit = 0 )
function get_content_image( &$content, $html = true, $remove = false )
function get_content_galleries( &$content, $html = true, $remove = false, $limit = 0 )
function get_post_galleries( $post_id = 0, $html = true )
function get_post_gallery( $post_id = 0, $html = true )
function get_content_chat( &$content, $remove = false )
function get_content_quote( &$content, $remove = false, $replace = '' )
function get_content_url( &$content, $remove = false )
}}}
I wonder if we can convert them to use arrays instead for future-proof changes, or at least switch from booleans to self-explanatory values, per our [http://make.wordpress.org/core/handbook/coding-standards/php/#self-explanatory-flag-values-for-function-arguments coding standards].
Otherwise, we might fall into a trap of `submit_button()`: #20492.
",SergeyBiryukov
24288,Timestamps in chat formats should have IDs,,Post Formats,trunk,normal,normal,3.6,defect (bug),new,has-patch,2013-05-08T20:32:35Z,2013-05-17T21:59:58Z,"If we add IDs to the time elements in the chat post format, and possibly wrap them in