﻿__group__	ticket	summary	owner	component	_version	priority	severity	milestone	type	_status	workflow	_created	modified	_description	_reporter
Next Release	23891	Post Formats: tab accessibility		Accessibility	trunk	normal	critical	3.6	task (blessed)	new		2013-03-29T10:32:49Z	2013-05-14T14:21:38Z	Post Format UI should allow for natural tabbing through the editable fields.	markjaquith
Next Release	23969	Sometimes when opening the theme customizer, then closing it, the URL gets 'stuck' at /wp-admin/customize.php		Appearance	trunk	normal	normal	3.6	defect (bug)	new		2013-04-06T23:58:26Z	2013-04-16T09:06:40Z	"Just what I said.

If I open the customizer, scroll down a bit, then back up, then click to close it, the URL doesn't change back as it should.

I can then click through to any other page on the admin or front-end, and the URL will still stay as /wp-admin/customize.php

View the bug in action here: http://youtu.be/RbdkudX6yGw"	georgestephanis
Next Release	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-24T19:16:59Z	"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
Next Release	24055	Videos should be responsive when admin size shrinks		Media	trunk	normal	normal	3.6	enhancement	new		2013-04-11T22:41:25Z	2013-05-22T20:21:10Z		wonderboymusic
Next Release	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:

{{{
<div style=""width: 400px; height: 30px;"" id=""mep_1"" class=""mejs-container svg wp-audio-shortcode mejs-audio"">...</div>
<p>Just some text up here ...<br>
</p>
}}}

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
Awaiting Review	24098	Support for HTML5 roles		Accessibility	3.5	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2013-04-16T07:44:16Z	2013-05-12T00:01:07Z	"I was going through http://core.svn.wordpress.org/trunk/wp-includes/kses.php and I realized that most of the new HTML5 tags have been introduced but `role` is a missing attribute.

I feel that since WordPress has already made a move towards HTML5 by supporting `<article>`, `<section>` and other tags, all attributes should be made available too. `role` should be added to the required tags falling under `$allowedposttags`.

Go through the link for more information on [http://www.w3.org/wiki/PF/XTech/HTML5/RoleAttribute roles]."	aniketpant
Awaiting Review	22104	High contrast admin colour scheme		Accessibility		normal	normal	Awaiting Review	feature request	new		2012-10-04T17:35:54Z	2012-11-20T16:57:21Z	"We should consider bundling a high contrast admin colour scheme with WordPress to aid accessibility for the visually impaired.

Some discussion on this has taken place previously on IRC but nothing much beyond that.

Some potential points of discussion:
 * Is anyone in the [http://make.wordpress.org/accessibility/ WordPress accessibility group] an expert on accessibility for the visually impaired? Can we get someone on board for some expert guidance?
 * Is an admin colour scheme sufficient? Would any JavaScript need altering too? If so, would an admin colour scheme suffice as a starting point?

Related:
 * [http://www.timobrienphotos.com/2009/03/hich-contrast-admin-color-scheme-for-wordpress/ A high contrast admin theme plugin]
 * [http://wordpress.org/support/topic/admin-color-scheme Support forum discussing admin theme for visually impaired user]
 * [http://wordpress.org/extend/plugins/easy-admin-color-schemes/ Easy Admin Colour Schemes plugin]"	johnbillion
Awaiting Review	22600	Editor sizing JS puts the resize handle in the wrong place		Administration		normal	normal	Awaiting Review	defect (bug)	new		2012-11-27T03:58:09Z	2012-12-14T23:51:29Z	"If you do the following, say to deal with the post content editor in a different way, the resize handle ends up in the wrong place because there is no status bar:

{{{
wp_editor( $post->post_content, 'content', array( 'tinymce' => false ) );
}}}

The JS that deals with the editor size/height should probably be checking for the status bar before moving the resize handle. Discovered while working on #22491."	helen
Awaiting Review	18264	Future private posts listed as already published with future date specified		Administration		normal	normal	Awaiting Review	defect (bug)	new		2011-07-27T00:05:27Z	2013-02-04T09:27:17Z	"Setting a post to private, and scheduling it for some future date or time, results in the stamp that the post was ""Published on (future date)"" in the publish module.

The discussion on tickets #5608 and #9136 suggests that all private posts are published immediately (and privately), and that this is intentional. So, it's misleading and confusing to report that it already was published on some future date.

In source:trunk/wp-admin/includes/meta-boxes.php#L163, I suggest we replace:

{{{
else if ( 'publish' == $post->post_status || 'private' == $post->post_status ) { // already published
		$stamp = __('Published on: <b>%1$s</b>'); }
}}}

with:

{{{
else if ( 'publish' == $post->post_status ) { // already publicly published
		$stamp = __('Published on: <b>%1$s</b>');
	} else if (  'private' == $post->post_status ) { // published privately
		$stamp = __('Published privately'); }
}}}"	chrisrudzki
Awaiting Review	19085	Removing First Submenu Page in Admin Menu breaks URL for Menu Page		Administration	3.1	normal	major	Awaiting Review	defect (bug)	new		2011-10-29T18:44:19Z	2011-10-29T20:39:29Z	"If you attempt to remove the Post Type Submenu Page in the Admin it breaks the Menu Page URL; it causes the Menu Page URL to be the same as the new first Submenu Page URL:

[[Image(http://screenshots.newclarity.net/skitched-20111029-142108.png)]]

Here is a simple class you can drop into the theme's `functions.php` file to experience this bug. This example is a minimum to trigger the error ''(I simplified the `register_post_type()` call so the example code would have fewer lines):''

{{{
<?php

class Trigger_Admin_Menu_Bug {
  static function on_load() {
    add_action( 'init', array( __CLASS__, 'init' ) );
    add_action( 'parent_file', array( __CLASS__, 'parent_file' ) );
  }
  static function init() {
    global $wpdb;
    register_post_type( 'test-cpt', array(
      'label'   => 'Test CPT',
      'show_ui' => true,
    ));
  }
  static function parent_file( $parent_file ) {
    remove_submenu_page( 'edit.php?post_type=test-cpt', 
                         'edit.php?post_type=test-cpt' );
    return $parent_file;
  }
}
Trigger_Admin_Menu_Bug::on_load();
}}}

I'd provide a patch but the admin menu code is more complex than I can fully understand.  Maybe the person who originally wrote it could fix it? 

Note: Sadly, this is a blocker for one of my client projects.  The client wants the admin menus simplified to reduce the conceptual load on their end users because we are adding many other submenu pages.  Plus I've traced through the core WP code with a debugger for many hours looking for hooks that would allow me to get around this issue, but there simply are no hooks where it would be needed to hack a fix for this."	mikeschinkel
Awaiting Review	21989	update_option() calls sanitize_option() twice when option does not exist		Administration		normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-09-25T05:04:34Z	2012-09-25T05:54:32Z	"
I just spent several hours tracking down an issue when using the Settings API where `sanitize_option()` is called twice which is unnecessary execution especially if sanitization includes calling an external API for username/password authorization ''(this was how another developer set it up for a plugin I was debugging.)''

What happens is that a call to `update_option()` will call `sanitize_option()` and then if the option wasn't previously in the options table `update_option()` will delegate to `add_option()` which calls `santize_option()` a second time.  This would normally be easy to workaround by first calling `get_option()` and testing for `false` and calling `add_option()` instead of `update_option()` if `false`, but not when the Settings API chooses how to call it.

I've looked at the problem and can envision several different ways to solve it such but don't know which the core developers would choose ''(or if they'd choose yet another option I haven't envisioned)'' so I didn't submit a patch:

- Adding a 3rd parameter `$mode` to `sanitize_option()` that identifies the mode ''('add', 'edit', default = 'unknown')'' and thus allow the hook to ignore one of the options ''(this would be more backward compatible but would put the onus on the developer to know to do this)'',  
- Adding a 5th parameter `$bypass_sanitize` to `add_option()` defaulted to `false` that is only passed as `true` in `update_option()` allowing `update_option()` to disable the call to `sanitize_option()` found in `add_option()` ''(this would be less backward compatible and hacky, but seemless to the developer)''
- Adding a 3rd parameter `$bypass_sanitize` to `update_option()` defaulted to `false` that is only passed as `true` from `/wp-admin/options.php` allowing `update_option()` to bypass the call to `sanitize_option()` if an `add_option()` will happen ''(this would be less backward compatible and hacky, but seemless to the developer)''
- Have `/wp-admin/options.php` test for no pre-existing option and then call `add_option()` or `update_option()`, respectively ''(this would be seemless to the developer but less backward compatible and not hacky, and it wouldn't handle the general case.)''

So is this worth fixing to save other users and developers debugging time, and to reduce the chance of subtle errors in new code? If yes, how best to approach?"	MikeSchinkel
Awaiting Review	21271	Make admin backend unit-tests friendly		Administration	3.4.1	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-07-14T14:19:20Z	2012-12-11T13:12:31Z	"Recently I started writing unit tests for my plugins. Beside tests focused on functionality (where I directly call my plugin functions) I write some basic integrations tests, which should test that WordPress will call my function, pass data in expected format and recognize data returned from it. For frontend it is quite easy - theme API is well-defined, so I can write something like this:
{{{
public function test_something() {
	// add new post
	$post_id = wp_insert_post( array( ... ) );
	$this->assertGreaterThan( 0, $post_id );
	
	// go to post page
	$this->go_to( get_permalink( $post_id ) );
	
	// main loop
	$checked_post = false;
	while ( have_posts() ) {
		the_post();
		if ( $post_id == get_the_ID() ) {
			$checked_post = true;
			
			// test that content is modified
			ob_start();
			the_content();
			$result = ob_get_clean();
			$this->assertEquals( '...', $result );
		}
	}
	
	// make sure test above was executed
	$this->assertTrue( $checked_post );
}
}}}
Unfortunately this is not true for admin backend - there most of code is written directly at file level (not in functions and classes), so I would need to either duplicate this code in my tests (bad approach, because would have to monitor original code for changes), or test using whole file (either load it directly or use Selenium) - in this case test would be more complicated.

Therefore I logged this ticket, to start discussion how we can perform refactoring of admin backend to make it more tests-friendly, and how to test it more thoroughly. Most probably we would also need to modify the testing framework (e.g. introduce new `admin_go_to()` method)."	sirzooro
Awaiting Review	19711	Posts edit list window display no information about filtering		Administration		normal	normal	Awaiting Review	enhancement	new		2012-01-02T16:39:30Z	2013-01-22T15:09:32Z	"The ""All Posts"" page lists the available posts.

It can filtered by authors or terms, for example by clicking on a category name or the author name next to a post.

The URL will change to apply the filtering, but there's no other visual indication of  the filtering, nor a link to quickly disable filtering.

This can lead to confusion when users are accessing filtered lists directly or via links in other part of the dashboard.

"	yoavf
Awaiting Review	22056	Integrate a list of notices for newbie users		Administration	3.4.2	normal	normal	Awaiting Review	feature request	new	dev-feedback	2012-09-30T14:39:40Z	2012-10-02T18:21:13Z	"Integrate a list of possible warnings and notices for the power-user (admin) if some problems or security thread occur, or to check if the site was infected with viruses and malicious .php files...

Example:
- Notice: GD Graphics Library is not installed, install this so the images could be resized
- Notice: Your site is not giving search engines the right to index the site, please consider changing the settings.
- Warning: An unknown file mail.php is in the site main directory, please check if you are not infected.
- Notice: Your site files permissions are set to 777, please change to 644 or 640, your site is in a security thread.
- Notice: Upload folder is not writable, please change permission to 755 for the upload dir.
- Notice: Please use a caching file plugin to make your site load faster than ever.
"	alexvorn2
Awaiting Review	23455	Theme Customizer does not load when static Front Page is moved to Trash		Appearance	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-02-12T12:27:37Z	2013-04-23T22:33:32Z	"Steps to reproduce:

1. Go to Pages > Add New, and publish a new page
2. Go to Appearance > Themes > Customize
3. Under Static Front Page, set this new Page as your Front Page. Save changes
4. Go to Pages > All Pages, and trash the page
5. Go back to the customizer
    * The sidebar loads, but not the preview
    * I see the following error in the console: http://i.wpne.ws/MpDR

When commenting out {{{$this->handle_404();}}} in [http://core.trac.wordpress.org/browser/trunk/wp-includes/class-wp.php#L550 wp-includes/class-wp.php#L550], the Preview appears again, but generates quite a lot of notices.

Tested with WordPress Trunk (Version 3.6-alpha-23400)"	jeherve
Awaiting Review	22834	Live Preview should map sidebars as done on activation		Appearance	3.4	normal	normal	Awaiting Review	enhancement	new		2012-12-09T12:51:00Z	2012-12-13T12:07:31Z	"'''Problem:''' 

Sidebar disappears in the live preview after theme deactivated.

'''Reproduce:'''

Fresh install of the WordPress trac:
1. Activate Twenty Ten theme
2. Click the Live Preview of Twenty Twelve
3. No sidebar in the preview

Bug 100%"	alexvorn2
Awaiting Review	21483	Theme Customizer: Use any image from media library for background image		Appearance	3.4.1	normal	normal	Awaiting Review	enhancement	new		2012-08-05T22:42:31Z	2013-04-11T10:28:09Z	"I suggest that users be able to use any image in the media library as a background image from the customizer. At this time, if a user changes the theme background from the customizer, he/she must upload the image. This is already available from the dashboard, under Appearance > Background - it gives the option ""Or choose an image from your media library:"" I suggest that this option available on the dashboard also be available on the customizer. A similar option should be available for header images."	jjonesftw
Awaiting Review	23691	Visiting post-new.php using the back button overwrites an existing post		Autosave		normal	normal	Awaiting Review	defect (bug)	new		2013-03-04T18:54:46Z	2013-03-04T18:54:46Z	"1) visit post-new.php
2) write a post
3) publish it
4) click back in your browser
5) write a new post
6) if you save it as draft or publish it, it will overwrite the old post

Reproducable in Firefox, Chrome and Safari."	jkudish
Awaiting Review	10690	WordPress does not support  non-ascii characters in URLs	markjaquith	Canonical	2.8.4	normal	normal	Awaiting Review	defect (bug)	reopened		2009-08-26T18:26:13Z	2013-03-08T20:31:45Z	WordPress' clean_url() strips out most characters, which are non-ascii for security reasons. This is causing problems, if you want to run a WordPress blog on a domain containing non-ascii-characters (e.g. müller.com), because WordPress generates wrong URLs on redirects.	paddya
Awaiting Review	23231	preprocess_comment should get the normalised comment data		Comments	3.5	low	minor	Awaiting Review	defect (bug)	new		2013-01-18T11:38:02Z	2013-01-18T11:39:30Z	"In '''wp_new_comment''' we normalise some data like user_ID/user_id so that we support people providing both versions but we fire the filter to preprocess the comment first.

This means if someone writes a filter they have to re-implement this normalisation if they want to filter the comment data properly.

An example of where this currently goes wrong is when Akismet tries to fetch the roles of the user submitting the comment - http://plugins.trac.wordpress.org/browser/akismet/tags/2.5.7/akismet.php#L332

This only works if the comment comes via a route that supplies the data correctly and not one that doesn't."	westi
Awaiting Review	23931	wp_insert_comment should require comment_post_ID		Comments		normal	normal	Awaiting Review	defect (bug)	new		2013-04-03T18:41:58Z	2013-04-03T19:06:08Z	"At this moment there is no check for example comment_post_ID. Not sure if there are more checks needed. Reason I asked are a few notices on the unit tests caused by WP_UnitTest_Factory_For_Comment. Those comments don't add a post ID what should change.

Currently, if a null comment_post_ID is passed, the comment isn't connected to a post. This can create confusion. Also Unit tests should run with WP_Debug on."	markoheijnen
Awaiting Review	23988	Add post info on comment.php?action=editcomment		Comments	3.5.1	normal	minor	Awaiting Review	enhancement	new		2013-04-08T12:58:20Z	2013-04-08T14:54:39Z	"When you get a comment notification, if you click on a link to mark as spam, etc, when you get to the edit comment screen, there's no indication of which post/page the comment was in response to, which can be a determining factor in deciding if a comment is valuable, off-topic, or spam. 

We should add an ""In response to"" area that lists the post title, date/timestamp like on comment list screen. If it's in response to another comment that should show as well, but since we don't have that in comment screen functionality yet, at least adding the post info that we already have and show on the list would be a clue and a step in the right direction."	jenmylo
Awaiting Review	23133	Display a warning in the admin if cron tasks fail due to blocked HTTP requests		Cron	3.5	normal	major	Awaiting Review	enhancement	new	dev-feedback	2013-01-07T08:33:05Z	2013-01-29T20:08:25Z	"I recently upgraded my very simple WP site to 3.5 where the following was in use:

Theme: Twenty Eleven
Plugins: None Activated

I have been completely unable to submit a post for publishing in a future date, when the time occurs, I get a ""missed schedule"" message.

The schedule entry in cron is as follows:

Next due (GMT/UTC): Jan 4, 2013 @ 11:28 (1357298880)
          Schedule: One-off event
              Hook: publish_future_post
         Arguments: [0]: 358

Increasing the timeout value in cron.php has made no difference. 

I will need to remain on a lower release until this is fixed or a diagnosis ""kit"" is made available.

I am not using any software other that WP produced at this point and feel that the lack of wp-cron documentation and support in the public domain leaves alot of people clocking many hours googling in desperation...

Make a difference in 2013 and get 3.5 development priorities to de-mystify the methods of fixing wp-cron please :o)"	prb22public@…
Awaiting Review	20233	Preview opens in the same window when edit panel was previously another Preview window		Editor	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-03-13T23:29:16Z	2013-01-03T05:52:29Z	"Steps to reproduce:

1. Create a new post, save as draft
2. Click ""Preview""
3. Go to the Preview window, and from there use the Admin bar to go back to the Dashboard and start writing a new post
4. Save that new post as draft
5. Hit ""Preview""
  * Expected result: preview opens in a new window
  * Result: preview opens in the same window

Is there some way we could get around that? For people working with multiple tabs, it can be really confusing."	hd-J
Awaiting Review	20073	When I publish a draft the posting date is not updated		Editor	3.3.1	normal	major	Awaiting Review	defect (bug)	new	dev-feedback	2012-02-18T20:39:13Z	2012-02-19T15:23:57Z	"I believe this was a bug previously that has come back with the latest version.  If you create a draft post and edit it over time, then publish it the date is NOT automatically adjusted to the date you publish.  It keeps the original date the post was created as a draft, thus putting it behind in the RSS feed and on your posting list.  This used to be an issue before, and seemed to be corrected and has come back up again

Steps to re-produce:
1)  Create a draft today
2)  Wait a couple days then publish
3)  You will see the ""published Date"" is the date it was created NOT the date it was published

This also happens with scheduled publishes "	ccolotti
Awaiting Review	16819	Accessibility: Internal Linking behaviour in Editor / TinyMCE		Editor	3.1	normal	normal	Awaiting Review	enhancement	reopened		2011-03-10T10:52:26Z	2012-10-22T15:58:33Z	"'''Issue'''

The default behaviour of the new 'Internal Linking' feature is to auto-insert the title attribute as a duplicate of the link text.

This is not best-practise and, contrary to some beliefs, doesn't actually aid accessibility.

'''Solution'''

The title field should be blank by default and only included if the uses enters data.

'''Why?'''

Title text is only useful when it is *different* to the actual link text AND provides additional information.  Duplicating the link text in this fashion just adds fuzz to the page.
"	stencil
Awaiting Review	23159	Add Words Counter In The Excerpt Metabox		Editor	3.5	normal	normal	Awaiting Review	enhancement	new		2013-01-09T19:46:57Z	2013-01-11T17:26:24Z	"Hi WordPress Lovers :) , WordPress 3.6 fouces on ""Content Editing"" a small good idea is to add a words counter in the bottom of excerpt meta-box , and a small tip of the current theme max words count .."	alex-ye
Awaiting Review	16963	wp_enqueue_script bug in ie8		External Libraries	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-03-24T20:30:33Z	2011-03-28T19:41:42Z	"In IE 8, if you enqueue jQuery and scriptaculous, the prototype library will be included before jQuery. Because of this, jQuery will overwrite the $ method, and even though it runs noConflict() the variable is broken for both libraries. WP should be aware of this and sort the libraries for this situation. (jQuery should be first, then prototype)

Tested on WP 3.1 in IE 8 build 8.0.7601.17514"	jkmassel
Awaiting Review	22028	Comments feed		Feeds	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-09-28T00:29:04Z	2012-09-28T08:04:24Z	"The problem I have noticed is with the comments feed however I think that this can happen with any of the other feeds.

When there are no comments accessing somedomain.com/comments/feed will cause a 404 error message in some browsers and in others just a blank screen, no errors whatsoever are generated which makes it very hard to figure out what the underlying cause is.

I would suggest providing a message that clearly states the lack of comments instead of a 404 error message or blank page, I think this same problem applies to all other feeds except it is clearly not noticeable as posts are the first things that are created after a clean install but comments can sometimes take longer or may not even happen however the comments feed url is added in the head of the document causing the site to have a broken link."	tlacaelelrl
Awaiting Review	23692	feed_links should have a parameter to choose which feed to display		Feeds		normal	minor	Awaiting Review	enhancement	new	dev-feedback	2013-03-05T14:02:12Z	2013-04-05T08:52:19Z	"Hello,

'''feed_links''' is a function located in wp_includes/general_template.php. It displays 2 feeds in the header : the main feed and the comment feed. The function is activated along with feed_links_extra when automatic-feed-links support is activated.

Currently, developers can't choose if they want both feeds to be displayed, or just one of them. I think this function should be improved.

Here is the current function :
{{{
function feed_links( $args = array() ) {
	if ( !current_theme_supports('automatic-feed-links') )
		return;

	$defaults = array(
		/* translators: Separator between blog name and feed type in feed links */
		'separator'	=> _x('&raquo;', 'feed link'),
		/* translators: 1: blog title, 2: separator (raquo) */
		'feedtitle'	=> __('%1$s %2$s Feed'),
		/* translators: %s: blog title, 2: separator (raquo) */
		'comstitle'	=> __('%1$s %2$s Comments Feed'),
	);

	$args = wp_parse_args( $args, $defaults );

	echo '<link rel=""alternate"" type=""' . feed_content_type() . '"" title=""' . esc_attr(sprintf( $args['feedtitle'], get_bloginfo('name'), $args['separator'] )) . '"" href=""' . get_feed_link() . ""\"" />\n"";
	echo '<link rel=""alternate"" type=""' . feed_content_type() . '"" title=""' . esc_attr(sprintf( $args['comstitle'], get_bloginfo('name'), $args['separator'] )) . '"" href=""' . get_feed_link( 'comments_' . get_default_feed() ) . ""\"" />\n"";
}
}}}

Currently, the only way to display only one feed (the main post feed or the main comment feed) so is to deactivate feed_links with :
{{{
remove_action('wp_head', 'feed_links', 2);
}}}
and then to create our own function to only display one feed.

Do you think this should be improved ?

Regards,"	Confridin
Awaiting Review	23757	convert_smilies should not convert in pre,code tags		Formatting	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-13T14:26:07Z	2013-03-14T11:22:31Z	"This related to this ticket [[BR]]
#23756

The purpose to this ticket is to make writing codes in posts more easier !!
"	alex-ye
Awaiting Review	23050	make_clickable incorrectly formats anchors with URL's and spaces in them in comments		Formatting	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-12-23T00:32:30Z	2012-12-23T16:27:36Z	"When posting a comment, if an anchor tag contains both a URL and some words, make_clickable formats the output incorrectly.

To duplicate, post the following content in a comment:

{{{
Hey! <a href=""http://wordpress.org"">http://wordpress.org is awesome</a> in case you didn't know!
}}}

When viewing the comment, you'll get:

{{{
Hey!
<a href=""#"" rel=""nofollow""></a>
<a href=""http://wordpress.org"" rel=""nofollow"">http://wordpress.org</a> is awesome in case you didn't know.
}}}"	johnjamesjacoby
Awaiting Review	23922	make_clickable() breaks when colon in hash		Formatting		lowest	minor	Awaiting Review	defect (bug)	new	needs-unit-tests	2013-04-03T00:41:39Z	2013-04-03T19:31:00Z	"`make_clickable()` doesn't like this string:

{{{
<a href=""http://en.wikipedia.org/wiki/URI_scheme#tel:"">http://en.wikipedia.org/wiki/URI_scheme#tel:</a>
}}}

It results in this HTML:

{{{
<a href=""http://en.wikipedia.org/wiki/URI_scheme#tel:""><a href=""http://en.wikipedia.org/wiki/URI_scheme#tel"" rel=""nofollow"">http://en.wikipedia.org/wiki/URI_scheme#tel</a>:</a>
}}}

Specifically it's the colon that is causing the issue. It can be a part of the URL too, it doesn't have to be a part of an anchor."	Viper007Bond
Awaiting Review	23236	Add functions to format attributes		Formatting		normal	normal	Awaiting Review	feature request	new		2013-01-19T06:32:57Z	2013-05-16T04:15:04Z	"I'd like to see WP add functions for attributes. These would be extremely useful and resuable for theme devs and internally. I've developed very solid generic functions for this in [http://phat.airve.com phat] and would be happy to make WP versions to the effect of:

{{{
wp_attrs( $array ) // converts array to attributes string
wp_attrs( $name, $value ) // formats attribute string
wp_attrs( $string ) // reformats attribute string
wp_parse_attrs( $string ) parses attributes into assoc array
}}}"	ryanve
Awaiting Review	18190	Don't redirect to 404 page on empty post archives		General	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-07-21T09:05:41Z	2011-07-22T13:55:20Z	"""../archive/2010/09/29"" redirects to a 404 Error because there are no posts that day.

If there are no posts, it shouldn't redirect to a 404 page. It should let the user perform the loop and show a message like this:

""Sorry, there are no posts for that date"""	gazpachu
Awaiting Review	21537	Email address sanitisation mangles valid email addresses		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-08-10T11:24:50Z	2013-01-22T09:00:07Z	"If you change your email address to one including an ampersand then we mangle the address with html entities.

For example:
 * This - peter&paul@sitting.in.a.tree.com
 * Becomes - peter&amp;paul@sitting.in.a.tree.com

This is due to the call to {{{wp_filter_kses}}} on {{{pre_user_email'}}} in {{{default-filters.php}}}.

The was added in [5906] for #4546.

I'm not sure if we need kses filtering for emails - if we do which should probably revert this conversion of the & => &amp; afterwards."	westi
Awaiting Review	19288	Erroneous custom taxonomy screen menu behaviour		General	3.0	normal	trivial	Awaiting Review	defect (bug)	new		2011-11-18T11:36:26Z	2011-11-24T16:24:31Z	"I don't think this could get any more edge case and it's of trivial severity, but I thought I'd report it for completeness' sake.

If a user has the ability to manage terms on a post type, but not the ability to edit posts of that post type, and the post type has more than one taxonomy, then the post type menu doesn't expand as expected when viewing one of the term management screens for that post type.

Steps to reproduce:

 * Register a custom post type that uses its own capability mapping (resulting in `edit_foos` etc).
 * Register at least two custom taxonomies for this post type, with or without its own capability mapping.
 * Give a user (or role) the ability to manage the taxonomy terms but not the ability to edit posts of the post type.

When viewing one of the term management screens for the given post type, the menu doesn't expand as expected (although the new 3.3 fly-outs do show).
"	johnbillion
Awaiting Review	13779	Preview doesn’t work - WP installed in its own directory		General	2.9.2	normal	normal	Awaiting Review	defect (bug)	reopened		2010-06-08T01:32:04Z	2013-02-02T23:02:43Z	"1.  Wordpress is installed on /wp/ subdirectory.

2. Then it was set up to be visible from the site root according to http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory  

3. Site works fine

4. [BUG] Preview for posts & pages isn’t working.  

When I press preview it goes to url like:  
http://example.com/?preview=true&preview_id=235&preview_nonce=aa28f04
and says ""You do not have permission to preview drafts."".

5. If I type subdirectory name “/wp/” in that url by hands, it shows correct preview:  http://example.com/wp/?preview=true&preview_id=235&preview_nonce=aa28f04

6. The situation is getting worse if i'm using permalinks. In that case - there is nothing i can do to see preview. 

ps: I’ve tested that on clean install. "	antares19
Awaiting Review	18266	WordPress does not signal DB errors when adding/updating post		General	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-07-27T05:56:18Z	2011-07-27T05:56:18Z	"WordPress does not signal DB errors when adding/updating post. As I checked, `edit_post()` (defined in wp-admin/includes/post.php) calls `wp_update_post()` but does not check if it returned error. Therefore end user never gets any error message.

I found this when I tried to replace valid SQL query with some invalid one, in order to stop insert operation when custom validation done in `wp_insert_post_data` hook failed."	sirzooro
Awaiting Review	16182	object_term_cache is never cleared for custom post types with non-shared taxonomy		General	3.0	normal	major	Awaiting Review	defect (bug)	new		2011-01-10T22:47:56Z	2011-02-02T19:38:14Z	wp_insert_post() calls clean_post_cache() after updating the post.  However, when clean_object_term_cache() is called, it passes is hard coded to pass in the post_type of 'post'.  So the object_term_cache is never cleared for any taxonomies that are part of the post object type's taxonomies.	prettyboymp
Awaiting Review	20048	Allow mt.getRecentPostTitles to return the sticky flag		General	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-02-15T14:02:03Z	2012-02-15T14:02:03Z	"Would be nice to return the value of the sticky flag in the mt.getRecentPostTitles response. This XML-RPC call is mostly used on mobile clients, and we need to show a visual indicator on ""sticky"" posts. Obviously, we can  call metaWeblog.getRecentPosts, but it is a ""more expensive"" XML-RPC call."	daniloercoli
Awaiting Review	16866	Multisite registration uses extra redirect	spathon	General	3.1	normal	normal	Awaiting Review	enhancement	reviewing		2011-03-16T15:08:34Z	2011-07-16T22:05:43Z	"When you are on a sub-blogg and choose register you are sent to wp-login.php?action=register and because it is a multisite it redirects to wp-signup.php. wp-signup.php then redirects to wp-signup.php on the main site. 

if
{{{
wp_redirect( apply_filters( 'wp_signup_location', site_url('wp-signup.php') ) ); // row 488 in wp-login.php
}}}
were set to network_home_url instead of site_url there would be one less redirects and risk for plugins to cause problems.


"	spathon
Awaiting Review	22845	On 32-bit systems, with post IDs higher than PHP_INT_MAX (2147483647) wordpress does not run fine		General	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-12-10T09:13:01Z	2012-12-12T17:42:54Z	"Logging all the MySQL queries I discovered that the queries that should pick my posts were all doing something like this:

SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647)

This 2147483647 number clearly has something in it: it's the PHP_INT_MAX value on 32-bit operating systems, while on 64-bit machines it's 9223372036854775807 http://php.net/manual/en/language.types.integer.php

So, the problem is divided in 2 parts: I run on a 32 bit system, and I have my IDs a bit too high.

I know that 2147483647 is a bit high for a post ID, but I discovered this the hard way. 
Now, I would have preferred an error message in the administrator interface. Do you think it's a good idea?"	copesc
Awaiting Review	21113	Previous/Next page links maintain all GET variables		General	3.4	normal	normal	Awaiting Review	enhancement	new	close	2012-06-29T14:57:00Z	2013-04-05T12:49:45Z	"The newer/older entries pagination system takes any query string in a inbound request, and includes it in the links generated for the newer/older entries. 

This causes problems when you put wordpress behind a cache, because all it takes is some bot trying a joomla hack to mean all visitors suddenly have a version of that page, including the bad query string, very visible.

For example:
http://kirrus.co.uk/page/6/?test=true

Note, in the 'Newer/Older' links at the bottom of the page, that ""test=true"" will be retained.

These should only really keep query-strings that wordpress knows it'll need, if you're including them? Else, you can basically poison someone's cache with this.

An example of the really bad query string poisoning a cache:
/page/2/?option=com_gk3_tabs_manager&controller=..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2F..%2Fproc%2Fself%2Fenviron%0000"	kirrus
Awaiting Review	23490	"add margin: 0px to ""#titlediv #title"" in wp_admin.css"		General		normal	minor	Awaiting Review	enhancement	new		2013-02-17T14:34:23Z	2013-02-17T14:34:23Z	"Firefox adds some margin to the input, as system css settings...
adding margin: 0 to the title input element makes the title text to be more correctly positioned in the center.

http://wpimpact.com/wp-content/uploads/2013/02/Untitled-6.png

fixed: 

http://wpimpact.com/wp-content/uploads/2013/02/Untitled-8.png"	alexvorn2
Awaiting Review	21642	language_attributes() print WP lang instead content lang.		General	2.1	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-08-20T18:15:37Z	2012-08-20T20:46:33Z	"If you have WordPress in a language does not mean that the content has to be in that language. It would be good if there was an option to select it.

Another detail is for example: If we have the translation ""'''Spanish - Spain'''"", ""'''es-ES'''"", WordPress print ""'''es-e'''s"" instead of ""'''es'''"" simply.
This would be good because it is the only translation into Spanish."	shadowhck
Awaiting Review	21999	Passing cookie arguments to the HTTP API should be easier		HTTP	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-09-26T06:24:38Z	2012-09-26T06:24:38Z	"If you want to set cookies during a remote HTTP request in WordPress, it's currently a rather pain in the ass to do.

Rather than having to deal with `WP_HTTP_Cookie`, it'd be nice if you could just pass a `name => value` array and have the rest taken care for you behind the scenes."	Viper007Bond
Awaiting Review	20907	About screen text assumes user has update privileges		Help/About	3.3	normal	normal	Awaiting Review	enhancement	new		2012-06-11T17:59:18Z	2012-06-11T18:02:42Z	"From the 'About' screen in WordPress:

> Thank you for updating to the latest version!

But I didn't! I am just a lowly editor. My administrator probably updated the site for me.

We shouldn't show this sentence if the user doesn't have the `update_core` capability."	johnbillion
Awaiting Review	24212	Add missing inline docs for esc_attr_x() and esc_html_x()		Inline Docs	2.8	normal	normal	Awaiting Review	defect (bug)	new		2013-04-28T16:02:54Z	2013-04-28T16:02:54Z	"See [source:trunk/wp-includes/l10n.php:22346#L208].

#9650"	ocean90
Awaiting Review	23591	Can't insert media into wp_editor() without quicktags and/or tinymce		Media	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-22T23:39:04Z	2013-03-05T16:15:36Z	"If I set up an editor with no TinyMCE or Quicktags, I'm unable to insert any media.
{{{
$args = array(
	'tinymce' => false,
	'quicktags' => false,
	'textarea_rows' => 5,
);
wp_editor( '', 'test1', $args );
}}}
No js errors or anything. Media modal comes up, I can use it without any issue, but as soon as I click insert (be it single media or gallery), nothing happens.

I have to enable tinymce and/or quicktags to get media insertion to work. 

Here's a simple plugin for testing: https://gist.github.com/trepmal/5016952

I can replicate this in 3.5.1 and trunk, have not tested in anything older.

I don't think this is a browser quirk, but just in case, I've tested and confirmed the issue in Firefox 19 and Chrome 25.0.1364.84 beta both on Mac 10.8.2."	trepmal
Awaiting Review	18396	"Custom post type of ""tab"" creates query conflict with media uploader."		Media	3.0	normal	normal	Awaiting Review	defect (bug)	new		2011-08-13T20:12:11Z	2011-11-28T23:00:38Z	"1. Create a custom post type with name ""tab""
2. Upload media in  (either attached to a post, or not)
3. Return to media uploader and click on ""Library"" tab, no images are pulled

The query being called will check for a post_type of tab with the post_name library, looks like it's due to ""tab=library"" being in the query string. Change the post type or remove the its registration and the problem disappears.

Details: WP 3.0+ (trunk, too), no plugins, TwentyEleven child theme only having a functions.php with the register_post_type function called on init.

I'd love to submit a patch to account for this or it could be listed as a reserved word for custom post types. Looking for direction for next steps. "	theandystratton
Awaiting Review	23409	Featured Images Not Working when From Media Library		Media	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-07T02:37:57Z	2013-02-16T01:39:02Z	"I am in 3.5.1, Multisite, all plugins disabled, using Twenty-Twelve theme. While editing a post, when clicking on ""Set Featured Image"" in the meta box, I get the popup and select the image. I then click ""Save Featured Image."" The box closes. The meta box displays nothing -- just the original ""Set Featured Image"" link. So, I Update the post. Still, no featured image. 

Going through the above steps, I decide instead to upload an image from my computer. When I do, and select it as my featured image, it works.

It seems to choke only on files that are already in the media library.
"	saracup
Awaiting Review	22997	IE 8 issue with new Media Manager		Media	3.5	normal	major	Awaiting Review	defect (bug)	new		2012-12-18T19:25:30Z	2012-12-18T19:38:55Z	When in any post in IE8 you are unable to remove featured images also if you add a new post and attempt to set a featured image the media manager does not open in a model as it should which prevents you from setting the image.	th3fallen
Awaiting Review	23436	Media Gallery - Cropping Image and then Cropping a thumbnail from that crop doesn't work.		Media	3.5.1	normal	minor	Awaiting Review	defect (bug)	new		2013-02-10T17:20:00Z	2013-02-10T18:04:06Z	"'''A recipe for repeating the bug behavior:'''

Navigate to Library in the admin sidebar.

Click ""Add new"".

Drag the 800x480 copy of this or any image to the drag and drop area:

http://en.wikipedia.org/wiki/File:Cheese_platter.jpg

(I suggest this image for ease of recipe duplication and best explanation.)

After the blue status bar has completed, ""Edit"" to bring the media edit window up in a new tab.

Click ""Edit Image"" below the actual image.

Drag anywhere inside the image to create a cropping box.

In the ""Image crop"" pane, set the crop area to 500px width, 100px height.

Drag the cropping box so that the fancy toothpick is as far left as possible along the horizontal axis of the cropping box, but centered vertically. 

Click the ""Crop"" icon. Click ""Save"". Click ""Update"".

Click ""Edit Image"" once again.

Drag inside the newly-cropped image again to create a new cropping box.

In the ""Image Crop"" pane, change the cropping dimensions to 150 x 100. 

Drag the box so the fancy toothpick is somewhere in the left third within the crop boundary. 

'''Important:''' In the thumbnail settings pane, set ""Apply Settings to:"" '''Thumbnail'''.

Click the ""Crop"" icon. Click ""Save"". Click ""Update"". 

Click ""Library"" in the admin sidebar.

The newly preferred thumbnail for our previously-cropped image does not save. Thumbnail remains default, based on center of previously-cropped image. Instead, you will see a small wheel of cheese sliced into six wedges with garnishes for the thumbnail, even though we chose the part with the fancy toothpick."	gr33nman
Awaiting Review	21323	wp_delete_attachment (leaves stale image class wp-image-### in content of post).		Media	3.4.1	normal	trivial	Awaiting Review	defect (bug)	new		2012-07-20T13:33:56Z	2012-07-20T13:33:56Z	"
Here is my Example I'm using:
Running a script below (placed in the wordpress docroot) to delete all thumbnails from the database:


{{{
require_once(""wp-load.php"");
echo 'Working... '; ob_flush();
global $wpdb; 
$attachments = $wpdb->get_results(""SELECT * FROM $wpdb->postmeta WHERE meta_key = '_thumbnail_id'""); 
foreach($attachments as $attachment){ 
     $wpdb->query(""DELETE FROM $wpdb->postmeta WHERE meta_id = '$attachment->meta_id' LIMIT 1""); 
     wp_delete_attachment($attachment->meta_value, true); 
} 
echo 'done!';
}}}

Now after running something like above I'm left with (inside my content of each post) a stale image class tag that no longer points anywhere.

I think a simple regex replace of the post_content for wp-image-#### Inside an Image tag would remove the stale element.

I haven't checked this with other attachment types to see if it also exists, but my guess is it would."	eliddon
Awaiting Review	16989	Add a parameter or filter to get_media_items() for media type.		Media		normal	trivial	Awaiting Review	enhancement	new	dev-feedback	2011-03-28T16:19:55Z	2011-07-17T23:18:21Z	"It's a bit confusing IMO to have all media items appearing in the gallery tab of the media upload popup as it only deals with images. I'm making an audio player plugin with soundmanager2.js that uses an extra media upload tab to organise the uploaded audio files and insert a playlist shortcode into the post.

To do this I had to take a copy of get_media_items() with my filter hardcoded in. I can share my code if desired but it's not the prettiest, I'd like a more wordpressy way of doing this in future releases when you're able."	sanchothefat
Awaiting Review	23424	WP_Image class for handling images from the media library		Media	3.5	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2013-02-08T15:41:24Z	2013-02-08T15:41:24Z	"Since 3.5 we have the class WP_Image_Editor. This needs a file path to be able to manipulate an image. Currently you would have to use something like wp_get_image_editor( _load_image_to_edit_path( $post_id ) ). What is wrong since you are using a ""private"" function.

Currently I'm working on this idea and you can find the code here https://github.com/markoheijnen/WP_Image/blob/master/wp-image.php. What it does now is getting the filepath, be able to get the image editor, add an image size on the fly and getting/updating the metadata.

We really miss something like a WP_Image class in WordPress. However I'm not sure what kind of functionality is needed for it. I like the current class mainly because it gives you the power to create an image size for a specific media image and stores it in the sizes array. When a user removes the media image then also the custom sizes will be removed."	markoheijnen
Awaiting Review	20663	add_image_size needs a $label		Media	3.3.2	normal	normal	Awaiting Review	enhancement	new		2012-05-12T20:47:31Z	2012-05-21T00:05:59Z	"add_image_size() does not have a $label parameter, this effects both localization but more importantly limits the `image_size_names_choose` filter.

The is when you try to add an image to a post and you can select sizes via the radio buttons.

Default sizes have labels like:  `'large' => __('Large')`

the `image_size_names_choose` filter is a great new filter that allows you to alter those radio buttons, but requires you to hardcore the array values for add_image_size() since it does not have a label (unless I'm missing something).

Reference code: https://gist.github.com/2668630

Related: #19990"	wycks
Awaiting Review	19834	More Robust Capabilities for Attachments		Media		normal	normal	Awaiting Review	feature request	new		2012-01-15T00:43:40Z	2012-11-24T15:08:50Z	"Attachments/files should have their own set of capabilities mirroring those of posts, in addition to upload_files. Specifically:

- read_attachments
- edit_attachments
- edit_others_attachments
- delete_attachments
- delete_others_attachments

Currently, attachments rely on the edit_posts capability, which can create complications if you don't want your users to see the ""Posts"" sidebar item, or don't want them to be able to delete the attachments they upload. "	walkinonwat3r
Awaiting Review	21631	HTML encoded characters in the custom menu's URL html are decoded after first save and removed after second save		Menus	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-19T15:27:20Z	2012-08-19T15:49:04Z	"Special characters in the custom menu's URL get double html encoded after second save.

Having an array in the URL that is using square brackets (site.com/key[value]), the links break after the second save of that menu item because the & in the &amp; gets double html encoded."	rocketwood
Awaiting Review	18271	Item hierarchy should be maintained when adding to menu		Menus	3.2.1	normal	minor	Awaiting Review	defect (bug)	new		2011-07-27T20:13:35Z	2011-11-16T06:25:49Z	"Situation:

Create a hierarchy of categories or pages and go to create a custom menu. In the meta boxes on the left hand side, the categories and pages are shown in hierarchical arrangement. Select all categories (for example) and add to menu.

Expected behaviour:

All links are added to custom menu and the hierarchy is maintained appropriately

Actual behaviour:

Hierarchy is lost and all menu items are top-level

This was originally raised by Jane in #17029 however the changeset in the ticket only applies to showing hierarchy in the meta boxes and doesn't cover maintaining hierarchy when adding to menu."	JohnONolan
Awaiting Review	21669	"Make ""Home"" option persistent in Pages box on Menus screen"		Menus	3.4.1	normal	minor	Awaiting Review	defect (bug)	new		2012-08-23T16:57:08Z	2012-08-27T15:09:43Z	"If you have some pages, or even a page, then on nav-menus.php in the Pages box, View All, it will display Home as an option. However, if you do not have any pages at all (mostly Blog on front page scenarios), then it just says ""No items."" in the Pages box. 

It should always be populated with at least the Home option. Oversight on our part that we didn't uncover this behavior before. "	jane
Awaiting Review	20325	Menu item parent classes for page_for_posts (home.php) not properly set on single.php		Menus		normal	normal	Awaiting Review	defect (bug)	new		2012-03-29T12:50:06Z	2013-05-21T14:38:33Z	If one has set page_for_posts (Settings => Read), on single.php wp_nav_menu() will set current_page_parent for the accordant menu item, but it will not set any parent or ancestor classes for its parent menu items as expected. [tested with 3.3.1]	ptietz
Awaiting Review	18842	wp_nav_menu confuses new developers when it falls through to page listing		Menus	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-10-02T10:54:12Z	2013-05-18T20:15:19Z	"It appears that when wp_nav_menu() falls through to a page listing, many menu-specific args are not passed to the page listing, which ultimately confuses new developers.

I seem to answer this at least weekly in #wordpress

One example is the 'container_class' arg, if it falls through to the fallback_cb, the container_class is not applied.

Ideally, template-related arguements should be passed to the fallback (And with pages as the default callback, it should handle these) or wp_nav_menu() should output any extra wrapping divs if appropriate."	dd32
Awaiting Review	23908	wp_nav_menu generates wrong classes for li elements		Menus	3.5.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2013-03-30T13:42:46Z	2013-03-30T13:42:46Z	"Function '''wp_nav_menu''' generates 2 different classes for '''<li>''' with exactly the same meaning: e.g. '''current-page-parent''' and '''current_page_parent'''. It sometimes generates one of them, but sometimes both. 

Also this coresponds to '''current-page-ancestor''' and '''current_page_ancestor''' classes. 

I think there should be one of them, but to preserve compatibility with older websites, it is better to leave both but generate both at the same time, so that user could use either ""'''-'''"" or ""'''_'''"" as separators."	anyname2
Awaiting Review	14698	Adding custom menu items in a WP managed menu		Menus	3.0.1	normal	minor	Awaiting Review	enhancement	reopened		2010-08-25T21:22:12Z	2011-01-29T17:52:21Z	"In Walker:walk() line 932 of classes.php (WP version 3.0.1), the comparison of the parent ID to 0 is done so using ==.  This is an issue if you're trying to manually insert a menu item for a term within a menu consisting of posts.  I would like to be able to set the parent_id to something like 'term:4' (with 4 being the ID of the term).  But because it is a string and comparing a string to zero with == will always equate to false.

I suggest that line 932 is changed from:
{{{
if ( 0 == $e->$parent_field )
}}}
to:
{{{
if ( empty( $e->$parent_field ) )
}}}

The end result I'm looking for is a way to take an existing menu and add in sub-items for a particular item that contains all the terms from a given taxonomy.  Then for each of the term items, add child items for all of the custom posts associated to the term.  For the time being, I'm using a negative db_id to bypass the comparison issue.

Here's a sample of my code:
{{{
function my_get_nav_menu_items($items, $menu, $args) {
  if ($menu->slug != 'primary') {
    return $items;
  }
  $findAProgram = null;
  foreach ($items as $item) {
    if ($item->post_name = 'find-a-program') {
      $findAProgram = $item;
      break;
    }
  }
  if ($findAProgram) {
    $order = count($items);
    foreach (get_terms('program-focus') as $term) {
      $posts = get_posts(""taxonomy=program-focus&term={$term->term_slug}&post_type=programs"");
      if (!empty($posts)) {
        $term = wp_setup_nav_menu_item($term);
        $term->menu_item_parent = $findAProgram->db_id;
        // set db_id to negitive value to avoid collisions with posts with the same ID
        // This is needed due to the non-strict equality check in classes.php
        // line 932 in Walker::walk().  I would love to use a string for the
        // term ID's (something like 'term:4'), but ""any string"" == 0 will
        // always return false.
        $term->db_id = -1*$term->ID;
        $term->menu_order = $order++;
        $items[] = $term;
        foreach ($posts as $post) {
          $post = wp_setup_nav_menu_item($post);
          $post->menu_item_parent = $term->db_id;
          $post->menu_order = $order++;
          $items[] = $post;
        }
      }
    }
  }
  return $items;
}
add_filter('wp_get_nav_menu_items', 'my_get_nav_menu_items', 10, 3);
}}}

"	mackeyn@…
Awaiting Review	23806	Nav Menu Edit Walker per menu item type, not menu?		Menus		normal	normal	Awaiting Review	enhancement	new		2013-03-18T02:09:11Z	2013-03-19T11:53:01Z	"The assignment of a walker to show the menu items on the right side of the Menus screen is set per menu in `wp_get_nav_menu_to_edit()`.

Ideally, it could be overridden per menu item type. That is, posttype, custom and taxonomy menu items can be handled by `Walker_Nav_Menu_Edit`, while a menu item (in the same menu) or 'foobar' can be handled by the `start_el()` from a different walker.

As things stand, I'd have to extend `Walker_Nav_Menu_Edit`, copy `start_el()`, and place the conditional code for what to output in there (in my case, strip out fields that aren't ever going to be used in my 'foobar' menu item type)."	GaryJ
Awaiting Review	15646	Theme menu locations don't appear until a menu is created		Menus	3.0	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2010-12-02T12:33:47Z	2013-03-07T19:17:49Z	"Nacin told me this was by design, but he said to create a ticket after I asked him this: How can a user know what menu to create or whether to create a menu if they don't know the locations that the theme supports?

Related: http://wordpress.org/support/topic/register_nav_menu?replies=29"	JohnONolan
Awaiting Review	16691	Add do_action or menu description in nav-menus.php		Menus	3.1	normal	normal	Awaiting Review	feature request	new		2011-02-27T17:54:14Z	2011-07-27T20:08:16Z	"The nav menu feature uses the taxonomy structure but does not use i.e. the term description.
This field could be used by adding an action in wp-admin/nav-menus.php, for example in line 538 or 552.

{{{

<label class=""menu-name-label howto open-label"" for=""menu-name"">
	<span><?php _e('Menu Name'); ?></span>
	<input name=""menu-name"" id=""menu-name"" type=""text"" class=""menu-name regular-text menu-item-textbox input-with-default-title"" title=""<?php esc_attr_e('Enter menu name here'); ?>"" value=""<?php echo esc_attr( $nav_menu_selected_title  ); ?>"" />
</label>
<?php if ( !empty( $nav_menu_selected_id ) ) :
	if ( ! isset( $auto_add ) ) {
		$auto_add = get_option( 'nav_menu_options' );
		if ( ! isset( $auto_add['auto_add'] ) )
			$auto_add = false;
		elseif ( false !== array_search( $nav_menu_selected_id, $auto_add['auto_add'] ) )
			$auto_add = true;
		else
			$auto_add = false;
		}
?>
<div class=""auto-add-pages"">
	<label class=""howto""><input type=""checkbox""<?php checked( $auto_add ); ?> name=""auto-add-pages"" value=""1"" /> <?php printf( __('Automatically add new top-level pages' ), esc_url( admin_url( 'edit.php?post_type=page' ) ) ); ?></label>
</div>
<?php endif; ?>
}}}

This would allow plugin developers to add additional fields or settings for nav menus and save them on updating or saving the menu.


"	linguasite
Awaiting Review	17397	Inconsistency in allowed site addresses		Multisite	3.1	normal	minor	Awaiting Review	defect (bug)	reopened		2011-05-12T14:40:09Z	2012-11-02T22:34:33Z	"The rules for allowed characters in a site address differ between when you add a new site and when you edit an existing site.

Steps to reproduce:

 1. Go to Network Admin -> Sites -> Add New
 2. Enter `foo.bar` as the site address and hit save. The address will be rejected as containing invalid characters.
 3. Edit an existing site instead, and enter `foo.bar.yourdomain.com` as the domain. The address will be accepted just fine.

Having written that out, maybe this isn't a valid bug because when adding a site you're entering the site address, but when you're editing a site you're editing the complete domain name. Hmm. I'll open it anyway and see what people think.

My core issue is that I'd like to be able to add sites that use fourth-level subdomains (eg `foo.bar.baz.com` when the main site is at `baz.com`). Currently I have to enter a different site address then go in and edit it to the desired domain."	johnbillion
Awaiting Review	16609	"Misleading ""Error establishing a database connection"""		Multisite	3.0.5	normal	minor	Awaiting Review	defect (bug)	new	dev-feedback	2011-02-21T17:31:10Z	2011-02-21T17:31:10Z	"Multisite install shows:

""Error establishing a database connection""

Even if credentials are OK when it doesn't find the domain entry in wp_blogs table, this is very misleading, would be helpful to have the same meaningful error message that /wp-admin shows.

I posted this problem originally at http://wordpress.org/support/topic/misleading-error-establishing-a-database-connection"	roberto.carvajal
Awaiting Review	23750	Uploads go into subdirectory install of WordPress		Multisite	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-12T22:10:59Z	2013-03-13T02:26:44Z	"In upgrading a few sites to WordPress 3.5 and then giving WordPress its own directory (`wp/`), we continually see the uploads end up in `wp/wp-content/blogs.dir` instead of `wp-content/blogs.dir`.

For the time being as a work around we have enabled a network wide plugin that consists of 

{{{

function ms_upload_fix($uploads) {
	$uploads['path'] = str_replace('/wp/', '/', $uploads['path']);
	$uploads['basedir'] = str_replace('/wp/', '/', $uploads['basedir']);
	return $uploads;
}
add_filter('upload_dir', 'ms_upload_fix');

}}}

We do have `WP_CONTENT_DIR` defined and assume it should use this if set."	jondavidjohn
Awaiting Review	16990	WP Multisite doesn't use custom db-error.php	tmuka	Multisite	3.1	normal	minor	Awaiting Review	enhancement	new		2011-03-28T19:19:46Z	2011-07-18T01:23:14Z	"I suppose this is a feature request. I don't see a way to configure a Multisite install to use the same wp-content/db-error.php file as a single wp site install uses. Instead where the db is down the page dies on ""Error establishing database connection"" wrapped in an <h1>.

It could be a complication of using the HyperDB plugin, but it appears that on line 104 of wp-includes/ms-settings.php when the db is down get_blog_details() obviously fails and wp-includes/ms-load.php:ms_not_installed() is called. Unfortunately ms_not_installed() does not redirect to db-error.php, and instead dies, returning
$title = /*WP_I18N_FATAL_ERROR*/'Error establishing database connection'/*/WP_I18N_FATAL_ERROR*/;

Obviously i could hack in a call to wp-includes/functions.php: dead_db() in ms-load.php, but i try to avoid any core hacking to make upgrades easier.

Does anyone have a suggestion for overriding this behavior cleanly? perhaps something in wp-WP_CONTENT_DIR/sunrise.php ?

I suppose if somebody else is interested in the simple fix, here it is. In ""function ms_not_installed"" on line 224 of wp-includes/ms-load.php, insert dead_db();
like this...

{{{
function ms_not_installed() {
dead_db(); //hacked this in so we can get use our custom db-error.php
}}}

The bottom line is that now the visitor will potentially see a more friendly error message when the db or db table is unavailable."	tmuka
Awaiting Review	21910	wpmu_create_user() standardization		Multisite	3.0	normal	minor	Awaiting Review	enhancement	new		2012-09-17T18:03:24Z	2012-09-17T23:36:26Z	"There seems to be some inconsistencies between wpmu_create_user(), create_user(), and wp_insert_user(). The former two are wrappers, and do different things but potential to consolidate and clean up some old code.

Per Nacin:
>nacin: wpmu_create_user() should probably just go away.

>nacin: fairly useless function

>nacin: by default, it looks like wp_insert_user() would create a role-less user.

>nacin: as would wp_create_user()

Looking at wp_insert_user() it sets the default role if none is provided, where wpmu_create_user() would actually delete the default roles and caps. 

Although, I'm not really sure there's a use case where you'd be using both the wpmu_new_user and user_register hooks simultaneously so possibly depreciate the former in favor of the latter. 

One real issue with wpmu_create_user is that it returns false instead of the WP_Error object which is probably not desired since the error could be useful. The false return is used in wpmu_activate_signup() to either set the returned ID or create it's own WP_Error. 

Lastly... documentation for create_user says it returns the ID, but it looks like it could potentially also return a WP_Error object. Didn't test, but possible documentation fix there. 
"	ryanduff
Awaiting Review	21584	Allow to create more networks		Multisite	3.4.1	normal	normal	Awaiting Review	feature request	new	dev-feedback	2012-08-15T00:34:24Z	2013-01-17T23:38:47Z	"After creating a multisite installation allow users to create their own network of blogs.

"	alexvorn2
Awaiting Review	20225	Self-contain wp-includes/load.php, wp-includes/plugin.php		Performance	3.3.1	normal	normal	Awaiting Review	feature request	new		2012-03-13T10:50:01Z	2012-04-01T09:44:46Z	"I'm trying to write a high-performance plugin.

I still want the whole of WP to be used by the admins, and the main part of WP to still be used by most user workflows, but I want certain end users to instead be using an alternate controller, instead of /index.php, when they're doing certain things. 

This new controller I'll write will use a couple of the core files, but skips most for the goal of increased performance. The proposed core files to re-use are:
* wp-includes/version.php
* wp-includes/load.php
* wp-includes/plugin.php
* wp-includes/wp-db.php
* wp-includes/class-wp-error.php

However, wp-includes/functions.php is a can of worms, that if I included, would require me to include many other files, and it spiders out from there.

What would be better is if the following functions that wp-includes/load.php and wp-includes/plugin.php require be moved into those files from the functions file. Specifically:
* wp_die()
* validate_file()
* stripslashes_deep()
* add_magic_quotes()
* _doing_it_wrong()
* trailingslashit()

If they aren't, I'll have to copy-paste them into my custom controller, maintaining separate versions of them (less than optimal).

Of course, this process still requires me to write my own simpler versions of many more complex functions:
* wp_cache_init()
* wp_cache_close()
* wp_get_active_network_plugins()
* is_blog_installed()
* get_option()
* update_option()

but that's completely acceptable.

Moving those first 6 functions from the functions file to the load and plugin files would not negatively affect core, but would positively affect plugin authors' abilities to write high-performance plugins."	scottconnerly
Awaiting Review	18523	Can't change page permalink if slug metabox is removed		Permalinks	3.0	normal	normal	Awaiting Review	defect (bug)	new		2011-08-26T14:42:56Z	2013-04-12T06:32:49Z	"If the slug metabox is removed from the ""Edit Page"" page, it is not possible to change permalinks, using the edit permalink function at the top of the page.

Slug and other metaboxes are removed by the karma theme, in its admin/theme-functions.php (but only if 'ka_hidemetabox' in the wp_options table is 'true'):
    
{{{
remove_meta_box('slugdiv','page','normal');
}}}

Technically, without the slug box, the ""post_name"" field containing the new slug is not sent with the form data when you click the ""Update"" button.  

I believe this is bug was introduced after version 3.1.3. "	dankod
Awaiting Review	17183	previous_comments_link and next_comments_link return wrong url with PATHINFO permalinks		Permalinks	3.1.1	normal	normal	Awaiting Review	defect (bug)	new		2011-04-19T20:13:15Z	2011-08-04T21:26:32Z	"When using PATHINFO permalinks, previous_comments_link() and next_comments_link() return a wrong link, which renders paged comments useless.

Steps to reproduce:
Set permalinks to: /index.php/%post_id%/%postname%/

The functions return URLs similar to: /comments-page-1/#comments
This URL results in a file not found (if no rewrite rules are available, which should not be necessary if the PATHINFO permalink structure is used).

Expected URL: /index.php/comments-page-1/#comments
Manual opening the URL results in the expected/correct paged comments page."	FireMotion
Awaiting Review	18672	"Implement rel=""prev"" and rel=""next"" for archives"	joostdevalk	Permalinks	3.3	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-09-15T12:37:23Z	2012-12-04T22:34:58Z	"As can be seen here:

http://googlewebmastercentral.blogspot.com/2011/09/pagination-with-relnext-and-relprev.html

Google now uses rel=""prev"" and rel=""next"" to navigate paginated archives. As we already do a lot of these types of links (rel=""index"", rel=""start"" etc.) I think we should add these. I'll come up with a first version of a patch."	joostdevalk
Awaiting Review	20563	Add actions between sections in User Edit form		Plugins	3.4	normal	normal	Awaiting Review	enhancement	new		2012-04-27T22:20:08Z	2012-06-12T23:45:44Z	"Currently there is only one hookable area in the User Edit to cleanly output additional fields: 'edit_user_profile' / 'show_user_profile'

I suggest we add another set just before each of the H3 tags on this page (/wp-admin/user-edit.php).

Above Personal Options:

{{{
<?php
	if ( IS_PROFILE_PAGE )
		do_action( 'show_user_profile_personal', $profileuser );
	else
		do_action( 'edit_user_profile_personal', $profileuser );
?>
<h3><?php _e('Personal Options'); ?></h3>
}}}

Above Name:

{{{
<?php
	if ( IS_PROFILE_PAGE )
		do_action( 'show_user_profile_name', $profileuser );
	else
		do_action( 'edit_user_profile_name', $profileuser );
?>
<h3><?php _e('Name') ?></h3>
}}}

Above Contact Info:

{{{
<?php
	if ( IS_PROFILE_PAGE )
		do_action( 'show_user_profile_contact', $profileuser );
	else
		do_action( 'edit_user_profile_contact', $profileuser );
?>
<h3><?php _e('Contact Info') ?></h3>
}}}

Above About:

{{{
<?php
	if ( IS_PROFILE_PAGE )
		do_action( 'show_user_profile_about', $profileuser );
	else
		do_action( 'edit_user_profile_about', $profileuser );
?>
<h3><?php IS_PROFILE_PAGE ? _e('About Yourself') : _e('About the user'); ?></h3>
}}}

For hooking into the save, I believe the existing action 'user_profile_update_errors' will suffice, though I'm not sure if that's the best name for having developers hook into for adding their own field and this runs after error checking.. So we could also add an action before error checking runs to allow for more extensibility to modify existing fields being saved there (letting you still use WP built-in error handling).

This would be added around line 130 in /wp-admin/includes/user.php:

{{{
	// Allow plugins to modify user fields before error handling
	do_action_ref_array( 'user_profile_update', array ( &$user, $update ) );

	$errors = new WP_Error();
}}}"	sc0ttkclark
Awaiting Review	23616	General Handler for Whitelisted Options' Submissions		Plugins		normal	normal	Awaiting Review	feature request	new		2013-02-26T03:06:55Z	2013-02-26T03:09:09Z	As stated over on #18285 WordPress should move away from posting to options.php. In order to do that, the Settings API needs a general purpose function that can be safely called on all Settings Pages that can handle posts to itself (generally referred to as 'take_action' in various places) and can handle what options.php currently does.	WraithKenny
Awaiting Review	22029	Install multiple plugins		Plugins	3.5	normal	normal	Awaiting Review	feature request	new		2012-09-28T00:44:34Z	2013-04-09T08:51:32Z	"The new favourite plugins list is very welcome. On this list, or in general, I would like to be able to install several selected plugins.

The use case is for site admins, pretty much the same use case as for the new favourites list. That featured would be really useful if one could install many plugins at a time, as one can upgrade many selected plugins at a time.

The use case when searching in other categories of plugins is not so obvious. It could be a special feature for the favourites list, or it could be available on all kinds of plugin search results."	knutsp
Awaiting Review	19721	WordPress should support multiple or nested plugin directories	scottnath	Plugins	3.3	normal	normal	Awaiting Review	feature request	new		2012-01-03T16:33:34Z	2012-10-22T11:12:11Z	"WordPress currently only looks one directory deep for the plugin files. This is a limitation in get_plugins. It should look at least two (or more).

Our setup: We have many sites on WordPress and would like to share a set of plugins across them. However, we also have a requirement where each site should have its own unique set of plugins as well. (I realize this seems like an easy job for Multisite or mu=plugins, but they're not something we can adopt currently for various reasons).

Ideally, we can create a symlink (or external/submodule) to our shared plugins folder from inside the core plugins folder and have WordPress recognize plugins within that folder:

* plugins Folder
	* hello-dolly.php
	* akismet
		* akismet.php
	* shared-plugins (symlink)

* shared-plugins folder
	* hello-dolly-enhanced
		* hello-dolly-enhanced.php
	* akismet-enhanced
		* akismet-enhanced.php

Currently, WordPress will ignore both hello-dolly-enhanced and akismet-enhanced.

Themes already support nested folder; plugins should too please!

Thanks,
Scott Nath"	scottnath
Awaiting Review	24423	Focus on post title field when title is empty		Post Formats	trunk	normal	normal	Awaiting Review	enhancement	new	reporter-feedback	2013-05-25T19:23:02Z	2013-05-25T19:28:12Z	"The post formats looks very nice.

One small thing could be more user friendly.
Currently when you change between the post formats then the Title field becomes focused and the title text will be selected.


Happened a lot with me that when I wanted to just use Space to scroll down the page, accidentally deleted the title text. Pressing any key is deleting the selected text in the title field.
Happened a lot with me that when I wanted to just use Space to scroll down the page, but accidentally deleted the title text.

It would be better if the title field getting the focus only if it's empty.

[[Image(http://qikr.co/files/pics/w/wpadminiss29707.jpg)]]


I commented my feedback for Post Format UI title input box, but didn't got any response for that, so I though I open this new ticket.
> http://core.trac.wordpress.org/ticket/24046#comment:61
"	klihelp
Awaiting Review	24137	CPT as a submenu item does not get the correct classes when adding new		Post Types	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-19T15:25:44Z	2013-05-11T00:32:28Z	"When registering a post type as a submenu of another post type, the submenu item does not get high lighted correctly when adding a new item to the post type (the one that is a sub menu).

The post.php and edit.php screens work fine for the submenu post type; it is only post-new.php does that doesn't highlight correctly.

This is similar to #19125 and #22022, but not quite the same.

I think I've tracked the issue down to `get_plugin_page_hookname()` and the `$_registered_pages` global.

The submenu post type key in $`_registered_pages` is (for example)

`download_page_edit?post_type=edd_volume_discount`

but the one retrieved by `get_plugin_page_hookname( ""post-new.php?post_type=$post_type"", $post_type_object->show_in_menu )` is 

`download_page_post-new?post_type=edd_volume_discount`.

It appears the `$_registered_pages` global doesn't include (at least for submenu CPTs) `post-new`, only `edit`."	mordauk
Awaiting Review	20571	problems with slug and view in custom post types		Post Types	3.3.1	normal	minor	Awaiting Review	defect (bug)	new		2012-04-29T23:27:56Z	2012-04-30T06:39:19Z	"when creating custom post type, there are 2 minor problems
1. when setting rewrite to false, it is not possible to edit slug (edit button missing) - this is wrong as slug is needed e.g. for get_post queries by name
2. if the post is set '''not''' publicly_queryable, then anyway the post edit screen shows ""View [custom post name]"" and ""Preview"" button, which then points to 404 screen. "	thomask
Awaiting Review	23207	Add  $labels argument to register_post_status()		Post Types	3.0	normal	normal	Awaiting Review	enhancement	new		2013-01-15T19:32:54Z	2013-03-08T22:59:14Z	"WordPress functions '''register_taxonomy()''' and '''register_post_type()''' has '''labels''' argument. Why not add labels to '''register_post_status()'''?

The current way to add status:
{{{
$args = array(
	'label'                     => __( 'draft', 'text_domain' ),
	'label_count'               => _n_noop( 'Draft (%s)',  'Drafts (%s)', 'text_domain' ),
	'public'                    => false,
	'show_in_admin_all_list'    => true,
	'show_in_admin_status_list' => true,
	'exclude_from_search'       => true,
);

register_post_status( 'draft', $args );
}}}


The new way (using labels):
{{{
$labels = array(
	'name'                      => __( 'Draft', 'text_domain' ),
	'singular_count'            => __( 'Draft (%s)', 'text_domain' ),
	'plural_count'              => __( 'Drafts (%s)', 'text_domain' ),
	'any_other_label'           => __( 'Any Other Label', 'text_domain' )
);
$args = array(
	'labels'                    => $labels,
	'public'                    => false,
	'show_in_admin_all_list'    => true,
	'show_in_admin_status_list' => true,
	'exclude_from_search'       => true,
);

register_post_status( 'draft', $args );
}}}"	ramiy
Awaiting Review	23309	Not all WP_Query::query_vars get updated during WP_Query::get_posts()		Query		normal	normal	Awaiting Review	defect (bug)	new		2013-01-28T15:40:56Z	2013-01-28T19:51:54Z	"There is a lot of logic within the WP_Query::get_posts() method that fills in missing query vars with defaults and manipulates others based on the rest of the query.  However, some of the final states for many of the variables aren't updated in the WP_Query::query_vars array.  For example, the post type is lost as a local variable and post_status is used for building compiling mysql expressions, but never directly updated.

The result is that any plugins that want to recreate the query for another system, (ie, an external search provider) must directly copy much of the business logic that WP_Query::get_posts() has embedded in it in order to fill in for the incomplete query_var array.

"	prettyboymp
Awaiting Review	19392	Add auto-suggest support for all flat taxonomies in Bulk Edit.		Quick/Bulk Edit	3.0	normal	normal	Awaiting Review	enhancement	new	early	2011-11-29T18:37:18Z	2011-11-29T18:58:48Z	"Auto-suggest in the Bulk Edit area for post_tag's was fixed in 3.3. Let's add support for all other non-hierarchy tax's in 3.4. 

See [http://core.trac.wordpress.org/ticket/19176#comment:11 #19176] for more info."	scottbasgaard
Awaiting Review	19343	Allow Quick Edit to be Disabled for Custom Post Types		Quick/Bulk Edit	3.3	normal	trivial	Awaiting Review	feature request	new		2011-11-23T19:41:02Z	2012-11-22T03:17:16Z	"For some custom post types, quick edit doesn't make sense, and it's not easy to disable the quick edit code. You can use CSS to hide it but that still requires the code to be sent to the browser when it's not even needed.

The only other solution is to extend the ''WP_Posts_List_Table'' class and set the ''inline_edit()'' function to return nothing. Something like this: 
{{{
if(!class_exists('WP_List_Table')) {
	require_once(ABSPATH . 'wp-admin/includes/class-wp-list-table.php');
}

if(!class_exists('WP_Posts_List_Table')) {
	require_once(ABSPATH . 'wp-admin/includes/class-wp-posts-list-table.php');
}

class My_Posts_List_Table extends WP_Posts_List_Table {
	function inline_edit(){}
}

function my_admin_head() {
	$wp_list_table = new My_Posts_List_Table();
	$wp_list_table->prepare_items();
}

add_action('admin_head-edit.php', 'my_admin_head');
}}}
Clearly, that is a lot of code to accomplish something so simple.

So, it would be nice if there was some way to disable quick edit. Maybe it could be a feature you could disable via the ""''supports''"" option when you register the custom post type?"	Jick
Awaiting Review	20520	Author Page Pagination Broken		Rewrite Rules	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-04-23T04:16:03Z	2012-04-23T04:37:44Z	"WP 3.3.1 Multisite
Permalink setup: /author/post-name

- If the request is ""domain.com/authorname"" the authors page pagination link is broken.

- If the request is ""domain.com/author/authorname"" the authors page pagination link works fine."	rbaccaro
Awaiting Review	16832	Trouble if the slug of a custom taxonomy is the same as the url of page/post		Rewrite Rules	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-03-11T11:50:43Z	2011-09-29T23:26:24Z	"I got some troubles with the 3.1 version of WordPress concerning the slug of custom taxonomy.

'''An example that work in 3.0.5'''[[BR]]
www.example.com/agency (url of a page)[[BR]]
www.example.com/agency/john-smith (url of a custom type's detail)

Apparently having the same ""folder"" 'agency' only works for one or the other url but not both.

Hope I made myself clear."	LucasHantz
Awaiting Review	19493	post and archive pagination don't work with custom endpoints		Rewrite Rules	2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-12-09T23:55:09Z	2012-04-02T20:54:52Z	"Archive pagination and post pagination are not endpoint-aware, so they break when endpoints are added to them.  

The following example code creates an endpoint, and then uses a filter to add that endpoint to various links on the rendered page:

{{{
add_action( 'init', function() {
	global $wp_rewrite;
	add_rewrite_endpoint( 'foo', EP_ALL );
	$wp_rewrite->flush_rules(false);
} );

add_filter( 'post_link', 'gist_add_endpoint_to_url', 99 );
add_filter( 'get_pagenum_link', 'gist_add_endpoint_to_url', 99 );
function gist_add_endpoint_to_url( $url_base ) {
	$endpoint = 'foo';

	$url_parts = parse_url( $url_base );

	$url = ( isset($url_parts['scheme']) && isset($url_parts['host']) ) ? $url_parts['scheme'] . '://' . $url_parts['host'] : '';

	$url .= isset($url_parts['path']) ? $url_parts['path'] : '';

	$url = user_trailingslashit( $url );

	if ( '' === get_option('permalink_structure') ) {
		$url .= isset($url_parts['query']) ? '?' . $url_parts['query'] : '';

		$url = add_query_arg( $endpoint, 'true', $url );
	} else {
		$url .= $endpoint . '/true';
		$url = user_trailingslashit( $url );
		$url .= isset($url_parts['query']) ? '?' . $url_parts['query'] : '';
	}

	$url .= isset($url_parts['fragment']) ? '#' . $url_parts['fragment'] : '';

	return $url;
}
}}}

You'll see that it works perfectly using the theme unit test, except that paginated posts produce URLs like this:
http://example.com/2008/09/layout-test/foo/true/2/ 
...which doesn't work.  The inverse -- http://example.com/2008/09/layout-test/2/foo/true/  -- also doesn't work, and produces a 404 on top of it. 

Also, the older posts / newer posts produce this format of link:
http://example.com/page/2/foo/true/
.. .which also doesn't work.

If you change gist_add_endpoint_to_url() to add a querystring param, older posts/newer posts links work fine, but post pagination still breaks:
{{{
function gist_add_endpoint_to_url( $url_base ) {
	$endpoint = 'foo';
	$url_base = add_query_arg( $endpoint, 'true', $url_base );
	return $url_base;
}
}}}

If you don't use a permalink structure at all, it works fine, since the pagination params are passed directly in the URL.

I'm not sure if the fix lies in modifying add_rewrite_endpoint() so that it creates pagination urls in wp_rewrite, or modifying the way _wp_link_page() and get_next_posts_link() work.  "	mintindeed
Awaiting Review	21425	the 'edit_users' capability also allows 'promote_users'		Role/Capability	3.4.1	normal	major	Awaiting Review	defect (bug)	new	dev-feedback	2012-07-30T17:07:52Z	2012-09-22T10:11:33Z	"Hello all,

I have found an issue where I have created a Support role in order to have a user make changes to basic user information. What I noticed was that the capability 'edit_users' allows said User (role) to promote users to any role - including admin! I tried removing the cap 'promote_users' and it does nothing.

add_role(
			'support',
			'Support',
			array(
				'read' => true,
				'edit_feedback' => true,
				'edit_others_feedback' => true,
				'list_users' => true,
				'edit_users' => true
			)
		);"	ew_holmes
Awaiting Review	23635	get_objects_in_term - identify matching terms		Taxonomy	3.5.1	normal	minor	Awaiting Review	enhancement	new		2013-02-26T21:29:54Z	2013-02-26T21:29:54Z	"`get_objects_in_term` is great for viewing taxonomy relationships for non-posts. However the return value is too limited for certain use cases. For When fetching object_ids for multiple terms the return value doesn't inform as to the matching term.

For instance this query:

{{{
#!php
$object_ids = get_objects_in_term(array(55, 66, 77, 88, 99), ""my_custom_taxonomy""); 
}}}

Might return an array of object_ids as follows:

{{{
#!php
array(101, 202, 303, 404); 
}}}

However there's no way to tell '''which''' term a particular object_id matched. Did object 101 match term 77? Or maybe it was term 99? Or both?

I've created a modified version of `get_objects_in_term` which will addresses this issue. I'll submit a patch, but am wondering if there's another way to achieve this functionality.  "	leepowers
Awaiting Review	18023	No way to define default page template		Template	3.2	normal	major	Awaiting Review	defect (bug)	new		2011-07-07T06:15:24Z	2011-07-08T17:59:26Z	"The twenty eleven theme is quite nice but there is no way to define the default page template. For a website that needs a sidebar on every single page it is a hasle to have to set (and not forget to doit) the page template to sidebar.

"	Gecka
Awaiting Review	20413	edit_post_link() have not an equivalant without echo		Template	3.3.1	normal	minor	Awaiting Review	defect (bug)	new		2012-04-10T21:16:59Z	2012-04-10T21:16:59Z	"Hello,

The function edit_post_link() (in link-template.php) have not a get_edit_post_link() function which returns what is displayed by edit_post_link().

It exists a function get_edit_post_link() but it returns the '''url''' of the link. Not the link (with <a href...).

It is not fun for l18n. Example :
{{{
<?php printf(__('Filed under: %1$s %2$s', 'azsimple'), get_the_category_list(__(', ', 'azsimple')), get_the_tag_list(__('Tags: ', 'azsimple'), __(', ', 'azsimple'))); ?> <?php edit_post_link(__('Edit', 'azsimple'), __(' &#124; ', 'azsimple')); ?>
}}}
How translator could put the edit_post_link before ""Filed under:..."" with just *.po file ?"	leblogdudeveloppeur
Awaiting Review	18791	Add custom post type support for Author Template functions		Template	3.2.1	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-09-27T12:32:48Z	2011-09-27T19:58:40Z	"Functions defined in `wp-includes/author-template.php` assumes that post type == post. It will be good to enhance them so they will be able to work with specified post type.

At first sight following functions will need update:
{{{
get_the_author_link()
the_author_link()
get_the_author_posts()
the_author_posts()
the_author_posts_link()
get_author_posts_url()
wp_list_authors()
}}}

I suspect there will be other updates needed, to support new `post_type` argument added to author's url."	sirzooro
Awaiting Review	18676	Allow headers, footers, and sidebars to be located inside of subfolders		Template	3.3	normal	normal	Awaiting Review	enhancement	new		2011-09-15T21:38:08Z	2013-02-07T21:50:09Z	"Now that `get_header()`, `get_sidebar()`, and `get_footer()` use `get_template_part()` (see #18331), we should add subfolder support once #15086 goes in.

This is especially useful for sidebars."	Viper007Bond
Awaiting Review	18780	"The caption ""Comment author must fill out name and e-mail"" is ambiguous"	gabrielhtc	Text Changes		normal	normal	Awaiting Review	enhancement	new		2011-09-26T14:46:14Z	2013-02-15T13:38:47Z	"
== Observation ==

Users tend to think that if they uncheck that option, the name and email fields will not be displayed.


== Problem ==

The caption ""Comment author must fill out name and e-mail "" in the ""Other comment settings"" of the Discussion settings is ambiguous.


== What is expected ==

With the current caption, users expect that the name and email fields aren't shown.


== What happens instead ==

The name and email fields are still displayed, but they are now optional instead of being required. Some of the themes do not explain whether the fields are required or optional, so the users think that unchecking the option has no effect.


== Solutions ==

* Changing the caption to a less ambiguous one such as: ""Name and email is optional for guests comments""
* Make sure that the themes show clearly which field is required or not to be able to post the comment."	gabrielhtc
Awaiting Review	22805	Add a hook for the live theme preview event		Themes	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-12-07T11:19:52Z	2013-01-17T23:42:52Z	"We have a hook for theme activation and deactivation, but for the theme live preview - not...

"	alexvorn2
Awaiting Review	16883	"Add check for ""Template Version"" on theme activation"		Themes	3.1	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-03-18T03:28:36Z	2011-10-19T18:15:47Z	"Related: #16395

In addition to adding Template Version to the standard meta information extracted from style.css in `get_theme_data()`, I think that for this information to be useful, a child theme shouldn't be able to be activated unless the template template the child theme uses (parent theme) meets the minimum version requirement identified in ""Template Version"".

A polite and graceful failure, with an error notice, would be preferable :-)

Reason: many times child themes utilize functionality that only exists in the latest version of a parent theme. They're stuck either writing backward compatibility into into their code, or risking whitescreens.

This not only prevents that, but it could be used to gently encourage the user to update the parent theme.

Certainly not a candidate for 3.1.1, but perhaps 3.2?"	nathanrice
Awaiting Review	18959	Allow choosing multiple header images		Themes	3.3	normal	normal	Awaiting Review	enhancement	new		2011-10-15T21:32:15Z	2012-06-25T16:01:02Z	"Please, see small screenshot :)

[[Image(http://trueimages.ru/img/0f/5b/b7cf5f11a2786fc804521503268.png)]]

Description: This is the theme TwentyEleven. I want choose multiple header images, (for example 4,5,6), but i cannot. Only random or only one. Thanks."	wikicms
Awaiting Review	19238	New approach for content navigation section in themes		Themes	3.3	normal	normal	Awaiting Review	feature request	new	dev-feedback	2011-11-12T16:06:01Z	2011-11-12T16:06:01Z	"At this moment the only way to replace default content navigation in theme (previous/next posts links) is to manually edit theme files. Ticket #18585 allows to replace this section, but its scope is limited to Twentyeleven and its child themes. 

Therefore I propose to introduce generic mechanism, which could be used by theme and plugin autors - e.g. add new `content_navigation_template()` theme tag. By default it should look for `navigation.php` file in theme directory and include it. There should be also a new filter, which could be used by child theme and plugin authors to provide alternate navigation section."	sirzooro
Awaiting Review	20978	Upload a theme like an image		Themes	3.5	normal	normal	Awaiting Review	feature request	new	dev-feedback	2012-06-15T18:26:31Z	2012-12-15T16:45:15Z	add option to drag zip files like images on 'theme-install' page, enable multiupload.	alexvorn2
Awaiting Review	23110	Tiny MCE - when adding blockquote, entering twice no longer backs out of blockquote		TinyMCE	3.5	normal	normal	Awaiting Review	defect (bug)	new		2013-01-03T16:48:00Z	2013-01-03T19:47:08Z	When using the visual editor you used to press enter twice to back out of a blockquote and continue writing paragraphs, but now it just adds a nbsp; in the blockquote. Without going into the html view and actually adding content below, there's no way to get out of writing in the blockquote. 	jack.nycz
Awaiting Review	18134	"TinyMCE messes up text when its ""caption"" contains only a space"		TinyMCE	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-07-15T19:58:23Z	2012-09-09T16:32:03Z	"1.) Have a long text [[BR]]
2.) Insert an image inside there with no link pointing anywhere and a caption that contains only a space [[BR]]
3.) Make some <dl>-s, numbered lists etc after that [[BR]]
4.) Insert a new image with full size also, and a caption with only a space. [[BR]]

After this everything is messed up. The whole text before the second image becomes the caption of the first image and the second image disappears."	szotsaki
Awaiting Review	22660	"Admin bar in multisite: mobile tap on ""My Sites"" dropdown in back-end doesn't work"		Toolbar	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-11-30T20:40:17Z	2012-12-21T00:33:39Z	"Quick steps here to reproduce an issue where the ""My Sites"" dropdown (multisite networks) will drop down and show the ""Network Admin"" link and the list of your sites. But, clicking on a site (to expand and see ""Dashboard"", ""New Post"", etc.) does not happen. Tapping the blog name just closes the dropdown.

I'm not sure what's different but I can consistently reproduce this when in the admin back-end (but works OK on front-end admin bar when viewing a site):

From /wp-admin/ on a mobile device (tested on iOS 6, iPhone 5, iPad) with a multisite network:

1. Tap ""My Sites"" in admin bar
2. See ""Network Admin"" and list of sites below
3. Tap one one of the site names

Expected: Site name expands to show ""Dashboard"", ""New Post"", etc. (same behavior as front-end when viewing site). Screenshot: http://d.pr/i/reOi

Actual: Tapping site name simply closes the ""My Sites"" dropdown, does not browse anywhere nor expand menu"	devinreams
Awaiting Review	17999	Failure to Update Notification Persists After Manual Upgrade		Upgrade/Install	3.2	normal	normal	Awaiting Review	defect (bug)	new		2011-07-05T20:30:08Z	2013-01-13T16:42:27Z	"This has been around for a few versions. When an update fails, if the user updates or upgrades manually and WordPress lists the updated version in the Administration Panels, the failure to update notification persists. 

I've sat through four or five updates with the failure notice on every panel, including WordPress 3.2, on several sites."	Lorelle
Awaiting Review	22076	WP Upgrader: update_bulk_plugins_complete_actions and update_bulk_theme_complete_actions should pass information about all plugins/themes to the filter		Upgrade/Install	3.0	normal	normal	Awaiting Review	defect (bug)	new		2012-10-02T07:56:19Z	2012-10-05T23:10:07Z	"In class-wp-upgrader.php, line 1214 there is this line:

{{{
$update_actions = apply_filters('update_plugin_complete_actions', $update_actions, $this->plugin);
}}}

When adding a filter to it like this:

{{{
add_filter('update_bulk_plugins_complete_actions','test_filter',99,2);

function test_filter( $update_actions, $plugins ) {
    echo print_r( $plugins, 1);
    return $update_actions;
}
}}}

Only the last updated plugin info will be printed. However, it should contain information about all the plugins that were updated (since we are dealing with a bulk upgrade here)."	ragulka
Awaiting Review	16492	Improvements to the Wordpress Update Process		Upgrade/Install	3.0.5	normal	normal	Awaiting Review	enhancement	new		2011-02-08T16:45:48Z	2011-07-17T21:54:10Z	"I've some suggestions on how to improve the update process (usability). I guess its not enough for separate tickets so I'm filing them together.

 * When updating Wordpress, a plugin or a theme, I'm being asked for the password to the FTP server. You should add a note there that the password won't be stored in the database. I guess many/some users are uncomfortable with storing their FTP password in the database and won't use the ""update tool"" for this reason.
 * Rename the button ""Update Automatically"" to ""Update Wordpress"". ""Update Automatically"" sound like ""Update now and update automatically in the future when a new Wordpress (and also plugin/theme?) version is available."" This should make the button's function a little bit clearer.
 "	manski
Awaiting Review	20947	feature request: one-click update for core, themes and plugins (all in one)		Upgrade/Install		normal	normal	Awaiting Review	feature request	new	dev-feedback	2012-06-13T22:48:50Z	2012-06-13T22:49:28Z	I'd love to have the one-click update be truly one-click so that you can click once and update core, themes and plugins all at once as opposed to having to initiate three different updates.	jkudish
Awaiting Review	17547	Image upload issues - Size reported as 0x0		Upload	3.1.2	normal	critical	Awaiting Review	defect (bug)	new	dev-feedback	2011-05-24T08:27:21Z	2012-05-16T17:35:28Z	"When I upload any image of any size to my wordpress installation the image uploads fine, but the size is reported as 0x0 and has only one option of inserting it as a full-sized image!

Further inspection of this issue has led me to believe that it lays with wordpress not inserting the correct (if any) meta data for the attachment into the database.

As you can see in the image below, the meta data is present and this image shows all options of inserting the image in the post at all sizes specified in the WordPress media settings panel.

http://www.millerswebsite.co.uk/images/meta%20data.jpg

But as you can clearly see from the image below, when the meta data is missing it shows you can't post the image at any size except full which is stated as 0x0px - Clearly something is wrong!

http://www.millerswebsite.co.uk/images/no%20size.jpg

Many people have had and are still having this issue since 2.5. There are quite a few forum threads relating to it with not a single word from anyone from WordPress.

Several tickets have been submitted to the WordPress Trac system with the issues going unresolved. This is a major problem and many people have reported it, yet nothing seems to have been done.

Sources :

http://core.trac.wordpress.org/ticket/12532

http://wordpress.org/support/topic/cant-adjust-media-file-size-since-upgrading-to-27

http://wordpress.org/support/topic/images-upload-fine-but-wp-shows-0x0-size

http://wordpress.org/support/topic/add-image-size-only-allows-fullsize-with-0x0-dimensions

http://wordpress.org/support/topic/image-upload-in-wp-28-with-translation

If any solution exists to this problem, please let me know, I have been searching for weeks now to no avail. When I talk about solutions, I do not mean using plugins to ""regenerate thumbnails""! Yes I know this works, but it does not solve the problem as its only a temporary fix. Plus it needs to regenerate the images every time you upload a new image.

Side note :
I have tried a completely new installation of WordPress with and with out plugins on a completely different database. I have uploaded and re-uploaded the WordPress files also.

This is the type of image I am uploading. I took it on my Nikon D3100 and compressed to 80% @ 960x768 which makes it 83KB so it's not exceeding any upload limits and I am still having problems.

http://www.millerswebsite.co.uk/images/wordpress/DSC_2165.jpg

My host claims it is not their fault and they have recompiled apache and php for me, the php memory limit is also set to 128mb and file upload size is limited to 8mb.

A phpinfo() can be seen here : http://www.millerswebsite.co.uk/info.php

My original complaint can be seen on the forums here : http://wordpress.org/support/topic/image-upload-issues-size-reported-as-0x0?replies=10"	David_Miller
Awaiting Review	19227	clicking the pinkynail/title in the media-upload.php library tab does not show the full media info.		Upload	3.3	normal	normal	Awaiting Review	enhancement	new		2011-11-10T20:30:35Z	2011-11-10T20:31:40Z	"I am using the latest nightly build.

I am not sure if this is supposed to work this way, but it does have the 'toggle' class and UX wise it should I think.

Steps to reproduce:
1: Open a post/create a new post
2: Click the Upload/insert media button.
3: in the media iframe click 'Media Library'
4: Click on an 'pinkynail' or title in the list

Nothing happens. I would expect clicking the 'pinkynail' or title to activate the same 'toggle' as the 'show' link does as we read left to right, our eyes are drawn to the image and we are generally choosing an image here, so our instinct is to click that. Plus this is how it works in the 'full' (i.e. non-iframe) version. It could also do with css to make the cursor 'pointer'.

Tested in latest versions of Chrome and Firefox in Windows 7"	davidosullivan
Awaiting Review	22993	Admin - users without a role are difficult to find		Users	3.5	normal	normal	Awaiting Review	defect (bug)	new		2012-12-18T17:32:21Z	2012-12-20T06:21:38Z	"There doesn't appear to be a filter to display users *without* a role (see the screenshot). The ideal solution would be to add a filter for ""None"".

[http://i.imgur.com/3S5pH.png]"	logikal16
Awaiting Review	16788	Ampersands in e-mail address become invalid		Users	3.0.5	normal	major	Awaiting Review	defect (bug)	new	dev-feedback	2011-03-07T20:01:38Z	2012-09-19T17:46:32Z	"When an e-mail address contains an ampersand, WordPress improperly escapes the ampersand invalidating the e-mail address.

Example: h&f@domain.com becomes h&amp;amp@domain.com

First of all, the proper HTML entity for ""&"" is '''&amp;'''. Where did the extra '''amp''' come from?

Also, an ampersand is a valid character in an e-mail address and should not be escaped. Escaping it could be a completely different e-mail address.

I have not dug into the code to find out where this is happening but I'd assume in '''sanitize_email()'''."	jfarthing84
Awaiting Review	17370	Screen options and meta box settings can lose per-blog meta box positions		Users	3.1.2	normal	normal	Awaiting Review	defect (bug)	new		2011-05-10T21:13:37Z	2011-08-04T21:13:59Z	"User preferences for admin interface appearance of the Dashboard and the Edit/Add New pages are stored in per-user options in wp_usermeta: closedpostboxes_$page, metaboxhidden_$page, meta-box-order_$page, and screen_layout_$page, where $page is one of 'post', 'page', or 'dashboard'. Users can customize the order of the Dashboard and editing meta boxes to better suit their workflow using the drag-and-drop AJAX interface to move the meta boxes into ordered columns and the Screen Options tab to show and hide the boxes. Many plugins add custom meta boxes to the Edit/Add New Post page.

In a multisite installation, with different plugins active on different blogs, users who rearrange an Add New Post page on a blog with a custom meta box and then rearrange it on a different blog without that meta box will lose the position of the custom meta box. Blogs can have different features and workflows implemented, and having per user options for the appearance instead of per user, per blog options limits the ability of a user to customize the interface.

The expected behavior for moving things around is that it changes on one blog, not on all blogs."	jmdodd
Awaiting Review	17326	Allow new user registrations to be moderated		Users	3.1	normal	normal	Awaiting Review	enhancement	new		2011-05-05T04:29:10Z	2011-05-05T16:02:57Z	"'''Summary'''

When registration is open, have the option to require manual approval of user accounts before they are granted default role status.

'''Details / Suggested Implementation'''

Create a new user role (""Moderated""?) which for all intents and purposes is the same as ""Subscriber"" (`read` capabilities).

If opted into, user moderation would assign new users this new role. Administrators would be able to see these users listed under the Users list and click an approve link which would change their role to the default user role (as per the General Settings).

This would also make it easier for plugins to implement private blogs while having open user registration.

See also: #12030"	Viper007Bond
Awaiting Review	16860	"map_meta_cap use ""manage_network_users""  instead of is_super_admin for  edit_users"		Users		normal	minor	Awaiting Review	enhancement	new		2011-03-15T18:45:07Z	2011-03-15T20:54:07Z	"I find that for a multi-site setup, the ability to edit users is inconsistent. there is a capability called ""manage_network_users"", but this cap if given to ""regular"" admin's does not give them the power to edit users. 
The current code in map_meta_cap  in wp-includes/capabilities.php is:
{{{
case 'edit_users':
	// If multisite these caps are allowed only for super admins.
	if ( is_multisite() && !is_super_admin( $user_id ) )
		$caps[] = 'do_not_allow';
}}}
removing any flexibility, I would suggest having this based on the ""manage_network_users"" capability, giving us much more flexibility in terms of assigning power to control user administration."	sboisvert
Awaiting Review	16698	Better Table field value upgrade check (minor)		Warnings/Notices	3.1	normal	minor	Awaiting Review	enhancement	new	reporter-feedback	2011-02-28T10:31:06Z	2011-03-04T12:48:04Z	"line 1463 on /wp-admin/includes/upgrades.php is

{{{
preg_match(""|"".$tablefield->Field."" ([^ ]*( unsigned)?)|i"",$cfields[strtolower($tablefield->Field)], $matches);

$fieldtype = $matches[1];
}}}

There is no check IF a $matches is found. If there is no match found an error will be displayed 'undefined index 1'. An Error message could be added here.

Can happen : if the sql code contains no spaces between the fieldname and the type it will generate the not found [1].







"	cogmios
Awaiting Review	21061	Can't drag an opened widget to other widget area		Widgets	3.4	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-06-24T19:43:44Z	2012-06-24T19:43:44Z	"the placeholder does not appear and the option to drag the opened widget is not possible, to fix this: to auto-close the widget before drag event (sortable) or add option to accept opened widgets

http://wpimpact.com/wp-content/uploads/2012/06/Untitled-5.png"	alexvorn2
Awaiting Review	21287	Fix Widgets Helper position on start event - sortable		Widgets	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-07-16T09:33:24Z	2012-12-13T12:31:33Z	"the widget helper moves (jumpes) to the left, to the parent left position... 

in Firefox this is not a bug but in chrome it does.

please take a look in the screenshot, the helper jumped to the left....

http://wpimpact.com/wp-content/uploads/2012/07/Untitled-2.png

I tried to use the :

{{{
ui.helper.css('left', ui.placeholder.position().left)
}}}
 
code but chrome does not set a placeholder position, I don't know why, maybe a chrome bug or in jQuery. 

"	alexvorn2
Awaiting Review	19846	Specify 'primary' sidebar, so widgets land in correct sidebar when changing themes		Widgets	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-01-16T21:49:42Z	2012-06-25T19:58:19Z	"With the improvements to widget handling in 3.3, the widgets in a previous theme's sidebar are transferred to your current theme's sidebar. But there's no way to specify which sidebar should receive them.

For example, when you activate the Genesis theme it has three widget areas:
- Header Right
- Primary Sidebar
- Secondary Sidebar

If you install a fresh copy of WP and then activate Genesis, the Header Right widget area is populated with the 6 default widgets ( http://twitpic.com/8618x5 ). It's definitely not ideal for new users unfamiliar with this.

It would be great if there were some way to specify a primary sidebar when registering it, and that's the one the default widgets flow into. 


{{{
register_sidebar( array( 'name' => 'Primary Sidebar', 'id' => 'primary-sidebar', 'primary' => true );
register_sidebar( array( 'name' => 'Secondary Sidebar', 'id' => 'secondary-sidebar' );
// Default: 'primary' => false
}}}

There might be better ways to handle this, but I think it should be done in WP core. If it's up to the themes to solve, we'll have to use solutions like this: https://gist.github.com/1623202"	billerickson
Awaiting Review	23909	Widgets Settings Loaded When No-Needed		Widgets	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-30T16:02:05Z	2013-04-03T19:21:32Z	"Hi, This ticket about the performance in the back-end interface .

WordPress run query to get the active widgets settings in every page even in the dashboard ! , This makes the site admin slow especially when the site have many widgets !

You can use '''Debug Bar''' & '''Debug Bar Extender''' plugins to check the queries ."	alex-ye
Awaiting Review	23423	sanitize_title() in dynamic_sidebar() restricts the use of specific characters for sidebar IDs		Widgets	2.2	normal	normal	Awaiting Review	defect (bug)	new		2013-02-08T13:25:00Z	2013-02-19T05:20:42Z	"In the dynamic_sidebar() function in wp-includes/widgets.php uses sanitize_title() on the given index when it looks for a sidebar with a name that matches the index. After that it leaves the index value sanitized making it impossible to use characters not allowed by sanitize_title() in a sidebar ID.

By not overwriting the given index value with the sanitized version it would still be possible to use any character for the ID. To achieve this, lines 847-853

{{{
$index = sanitize_title($index);
foreach ( (array) $wp_registered_sidebars as $key => $value ) {
	if ( sanitize_title($value['name']) == $index ) {
		$index = $key;
		break;
	}
}
}}}

should be replaced with


{{{
$sanitized_index = sanitize_title($index);
foreach ( (array) $wp_registered_sidebars as $key => $value ) {
	if ( sanitize_title($value['name']) == $sanitized_index ) {
		$index = $key;
		break;
	}
}
}}}"	paulvandermeijs
Awaiting Review	18671	Allow themes to set default widgets		Widgets	3.3	normal	normal	Awaiting Review	enhancement	new		2011-09-15T06:52:41Z	2012-09-16T13:24:25Z	"Rather than having to use a hard-coded fallback HTML sidebar, it'd be cool if a theme could set up default widgets.

#17979 will somewhat remove the need for this but it could still be useful."	Viper007Bond
Awaiting Review	16613	Extend Widget API to allow sidebar/widget manipulation		Widgets	3.1	low	normal	Awaiting Review	enhancement	new	dev-feedback	2011-02-21T22:55:17Z	2013-01-21T17:27:26Z	"There is currently no easy way to add a widget to a sidebar using code. We should add methods of doing this.

A good example usage of such an API could be when a new theme is activated, it could add it's custom widgets to it's sidebar.

API should provide support for adding widget X to sidebar Y (or even just the first sidebar) along with setting some options for the widget and where in the sidebar to add it (top vs. bottom)."	Viper007Bond
Awaiting Review	16581	Meta widget: properly redirect user after logging in / out		Widgets	3.1	normal	normal	Awaiting Review	enhancement	new		2011-02-17T19:20:11Z	2011-02-18T02:11:07Z	"Inside Meta widget, there's a login link. However, the href attribute doesn't contain a redirection query argument.

So, there's a usability problem when someone is reading a post and want to comment, but can't because he's not logged in (and the blog requires logging in to comment). After logging in using the link inside Meta widget, the user is redirected to the admin area, instead of to the post he was reading. It would be a few clicks too many to go back to the post to comment.

The same thing can be applied to the Log out link (when the user's currently logged in). Instead of showing the blank `wp-login.php` form, he should be redirected back to the page where he clicked the link."	garyc40
Awaiting Review	20988	Open a closed sidebar box and enable droppable/sortable in it when you hover a draggable available widget over it	ldebrouwer	Widgets	3.4	normal	normal	Awaiting Review	enhancement	new		2012-06-16T10:27:24Z	2012-06-16T11:00:29Z	"At the moment you have to explicitly open a sidebar box to allow it to except available widgets. In my humble opinion this is bad UX and the sidebar box should expand automatically when being hovered over with a draggable and it should accept the draggable to it's containing droppable/sortable as well.

The obstacles to overcome:
- Since the draggable in most cases overlaps the sidebar box when dragging over it ( unless you move really quickly ) it's hard to register a 'mouseenter'. This could be solved by setting the 'cursorAt' option for the draggable.
- Opening a sidebar box is trivial but activating the droppable/sortable only seems to kick in when the draggable has been released."	ldebrouwer
Awaiting Review	17382	XMLRPC wp_getUsersBlogs Scalability		XML-RPC	3.0.1	normal	normal	Awaiting Review	defect (bug)	new		2011-05-11T20:32:15Z	2012-05-13T16:16:46Z	"If there is a root blog with many sub blogs on it and a user that is an admin on each sub blog, then when the when the XML RPC method wp_getUsersBlogs() is called it does not scale very well. My PHP memory_limit setting was 128MB, and the XML RPC request died when a user was a member of 230+ blogs. I noticed that the number of queries made to the database for a single user that has many blogs that they are an admin is very high.

Affected line: http://core.trac.wordpress.org/browser/tags/3.0.1/xmlrpc.php#L443

I don't know exactly how the code would have to change so I am not providing a patch."	bmorneau
Awaiting Review	17270	strip_tags function in XML RPC needs replacing with regex		XML-RPC	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-04-28T16:32:46Z	2011-04-28T16:32:46Z	"I've been working on a plugin that works with pingbacks, and I have come across a problem with a line in class-wp-xmlrpc-server.php which uses strip_tags. 

(line 3422 in WP 3.1):
$linea = strip_tags( $linea, '<a>' ); // just keep the tag we need

For some reason this function is not working properly at all on some templates (or that is the way it seems) and instead of returning all the <a> tags is cutting a lot of them out, making it seem to the server like there is no target link in the source URI, and thus returning a pingback fault 17 unnecessarily. And this means a large percentage of genuine pingbacks are failing without the user even knowing about it!

I suspect the function is having trouble with plugins that insert javascript near the header of the page, though it could be otherwise, as I have done a test to see what is left after this line is run, it returns some garbled javascript, no links at all from the post content (where the source links actually were), and then the menu links.

I have included a workaround in my new plugin:
http://wordpress.org/extend/plugins/pingchecker/
Basically it does a regex match for links in your content, then echoes them in a hidden div in the footer, making it much easier for the strip_tags function to actually find them. It works pretty well so I'm not fussed myself, but I thought it worth writing about..

This line really needs to be replaced with the regex match in the actual server code for future WordPress users too. I don't know regex myself, but I used sample code I found here (http://regexadvice.com/forums/thread/48395.aspx) for this regex expression, which seems to work really well.

In any case, strip_tags is not doing a reliable job at this and needs replacing. Hopefully this finds its way to the right person able to fix this. Thanks!"	majick777
Future Releases	9698	WordPress back end is not accessible		Accessibility	2.8	normal	major	Future Release	task (blessed)	new		2009-05-01T18:15:41Z	2012-02-20T20:50:25Z	"The WordPress back end violates several WCAG accessibility guidelines, so it cannot be considered accessible to people with disabilities.

Guidelines: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/

Not being an accessibility expert, I am not sure of all of the violations. But guideline 6.3 states ""Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.""

This means that you should be able to do all functions in the WP back end with JavaScript disabled.

As of 2.8-bleeding [11148], there are several things you cannot do with JavaScript disabled:

1) Upload and attach media to a post. You can upload media in the Media section, but the media upload section of the post edit screen is missing without JS, and I see no way to attach it to a post.

2) Add tags to a post or change which tags are on a post. The tags section is totally blank without JavaScript. (It could at least have the default plain-text field that is there behind the scenes and hidden).


"	jhodgdon
Future Releases	13218	Allow to specify name of drop-in which is not a plugin	nacin	Administration	3.0	normal	normal	Future Release	defect (bug)	reviewing		2010-05-02T21:14:23Z	2011-04-07T03:49:48Z	As I mentioned in #11861, plugin DB Cache Reloaded have two files: one main plugin file, and another used as `wp-content/db.php` drop-in. I would like to provide name for the drop-in file, but now the only way is to use the `Plugin Name:` header. Unfortunately when I do this, drop-in file bundled with plugin appears on plugin list. Therefore I need new header, which could I use to specify drop-in name, without that unwanted side effect.	sirzooro
Future Releases	10762	Bulk editing creates invalid URIs		Administration	2.8.4	normal	normal	Future Release	defect (bug)	assigned		2009-09-09T16:53:30Z	2013-05-12T10:27:16Z	They simply get too long for example if you move 999 posts to trash. It might be helpfull to switch to the post form method.	hakre
Future Releases	6342	"Rapidly spamming/deleting comments can break ""infinite river"" feature on comment moderation pages"	mdawaffe	Administration	2.5	normal	normal	Future Release	defect (bug)	new		2008-03-21T22:05:16Z	2011-12-14T13:18:06Z	"Comment moderation pages have an ""infinite river"" feature whereby when you remove one comment (spam/delete), it'll load a new one at the bottom.  Unfortunately, it doesn't seem to catch up if you click more rapidly than about once every 2 or 3 seconds, and you'll ""lose"" comments.  At the end, you may just have one comment that, when dealt with, will be replaced by only one comment.  This may have to do with doubleclicking the ""spam"" link, or maybe clicking the ""spam"" link of the next comment before the river action has finished."	markjaquith
Future Releases	17036	Theme editor shouldn't override root directory files with same names in child directories		Administration	3.1	normal	normal	Future Release	defect (bug)	new		2011-04-03T19:11:33Z	2012-06-27T10:23:07Z	"'''Steps to reproduce:'''
1. Create subdirectory: blogs
1. Create file in subdirectory: index.php
1. Try selecting Main Index Template in Theme Editor

Example is taken from BuddyPress' theme structure. `get_file_description()` doesn't account in any way for the presence of subdirectories since it uses `basename()`."	kawauso
Future Releases	7756	AJAX saving method instead of reloading the page		Administration		normal	normal	Future Release	enhancement	new		2008-09-16T17:36:44Z	2013-01-03T16:12:25Z	"Instead of using a traditional page refresh after saving a post, utilize AJAX, similar to how auto-saving already functions, to save the post.

this would help decrease the load on the server and enhance the user experience."	jdingman
Future Releases	7723	Allow filtering by author on Manage > Posts		Administration		normal	normal	Future Release	enhancement	reopened		2008-09-10T19:59:37Z	2011-12-19T18:04:36Z	"In versions of wp before 2.5 you could select an author from a dropdown on MANAGE > POSTS to see only posts owned by that author. This was very useful for quickly sorting posts and is absolutely necessary when you have editor users without  the 'edit_users' capability, as unlike admin users (most of us) they don't have access to the 'users' tab and thus have no way to see the manage screen sorted by user. The manage screen sorts by user simply by adding ?&author=$id in the url, but for users without access to the 'users' tab, even author id's are innaccessible. 

In the #wordpress-dev irc channel ryan boren expressed that the filter was removed because in some cases there were too many users in the system and the resulting dropdown was slowing down pageload time and ruining user experience. This is a paradox, because the more users your system has the more likely you are to need this filter. 

Wordpress needs to support filtering by author somehow if it wants to be a serious multi-user platform. Our editors are pulling out their hair.

My personal opinion is that the dropdown select should be reinstated. Filters should be added to the list such that only users who can post are listed (other users have no use in the Manage > Posts screen), as well as to show only users with at least 1 post. This should avoid slowing down pages for installations where most users are 'subscribers', which would otherwise mean all open-registration blogs would have hugely long lists. 

Given those two filters, I think that anyone who still has load-time problems should deal with their problem themselves using a plugin. It should be easy to remove the filter dropdown if you don't want it using a plugin, as well as to further filter the authors shown to reduce their number. 

Any installation with that many users deserves the option of deciding if they want the pulldown or not, and I think many would choose to keep it even if there are problems because it is so incredibly useful in filtering through hundreds of users worth of posts. 

(Consider: the full categories list is shown, even if there are hundreds, despite the fact that this has the same effect on performance as many authors does). 

Also in IRC Matt M proposed that some kind of text box + ajax to predict which author you mean could be used for this purpose. I think that is a great idea but would take a lot more work than what I propose (the work for hte pulldown is already done and the old functions are still there, all that's needed is to add filtering and re-work it into edit.php). It could also be used in the 'Users' context for search though, so it could be worth the effort. "	jeremyclarke
Future Releases	7797	Consolidate iframe headers		Administration	2.7	normal	normal	Future Release	enhancement	new		2008-09-26T23:35:46Z	2012-10-30T16:40:45Z	"Currently iframes are being used in multiple locations (ie. thickbox, plugin re-activation, etc) and in each case, theres generally a function for the header and footer, or its inline.

What i suggest, Is to create a standard set of admin templates which print the headers out for the pages.

And a side suggestion:[[BR]]
As an added bonus, It should probably be possible to automatically detect if it was loaded via thickbox ($_GET[TB_iframe] shouldnt be set) and serve the correct header (ie. Full admin side menu if no thickbox)"	DD32
Future Releases	9604	Edit screens expire		Administration	2.8	normal	normal	Future Release	enhancement	new		2009-04-21T06:35:08Z	2009-06-13T02:02:48Z	"Steps to reproduce:
1) Open an edit post (or page) screen
2) Take your browser offline for 24 hours
3) Put the browser back online
4) Edit the post, type a lengthy, thoughtful, dramatic entry
5) Click save draft / publish as you prefer

Expected result: Your poetic prose is committed to infallible digital memory.

Actual result: You're told ""Your attempt to edit blah has failed."" Press the back button and likely see the previous version of your post. Your latest prose exists now only in your memory.

Technical details: I think the nonce expires, so the post screen becomes invalid after a while.

Proposed solution: Add a javascript timeout to warn the user that the edit screen has expired. Provide a mechanism for the nonce to be updated."	chmac
Future Releases	16853	Error 500 when a user has too many sites	PeteMall*	Administration	3.0.1	normal	minor	Future Release	enhancement	accepted		2011-03-14T11:15:57Z	2012-02-13T09:36:58Z	"'''My installation'''
[[BR]]
3.0.1 multi-site installation with more than 7500 blogs, with one user each. I also have one moderation user that can administer each of the blogs.
[[BR]]
[[BR]]
'''The issue'''
[[BR]]
In the admin interface, when I go to Super-Admin -> Users, and when I display the page that contains my moderation user, I get ""''An error (500 Internal Server Error) has occured in response to this request''"". The page tries to display all the sites administered by him (around 7500 of them), hence the error.
[[BR]]
[[BR]]
Updating to 3.1 didn't resolve the problem.
[[BR]]
[[BR]]
'''Recommended enhancement'''
[[BR]]
For each user in the list, display only a certain number of sites, with a possibility to see all of that user's sites, if needed."	luuzan@…
Future Releases	14515	Make admin table content filterable by column	sirzooro	Administration	3.0.1	normal	normal	Future Release	enhancement	assigned		2010-08-03T06:16:40Z	2011-10-21T09:15:42Z	"I would like to modify Author column on post list - add link to user's profile. Now the only way is to add it to 1st column or custom column, and optionally move it later using JavaScript. Therefore I ask to add new actions for default columns, which will allow to do this.

It may be also beneficial to implement this as a general hook which will be called on all columns, including custom ones."	sirzooro
Future Releases	9117	Spam queue doesn't distinguish between filter sources		Administration	2.7	normal	normal	Future Release	enhancement	new		2009-02-12T22:50:51Z	2012-06-19T19:23:07Z	"1. On the Settings / Discussion tab, go to the Comment Blacklist box, and add the string ""the"".

2. Post a comment containing the word ""the"".  It will be caught as spam.

3. Visit the Comments / Spam tab.  Your comment is there, but there is nothing to indicate whether it was caught by the Comment Blacklist, or by Akismet, or by another spam filter.

Result: neither the user nor WordPress knows how to prevent that comment from being caught in future.  Many users will forget about the Blacklist feature and assume their spam filter plugin is faulty.

Suggested fix: comments caught as spam should record the reason.  This should be displayed to the user, and used internally by spam filter plugins to decide how to handle false positives.

"	tellyworth
Future Releases	19123	Top and bottom pagination should be consistent		Administration	3.3	normal	normal	Future Release	enhancement	new		2011-11-03T02:39:23Z	2012-12-24T11:45:33Z	The top pagination on Install Themes and Install Plugins is the new style (box to type in page number), but for some reason the bottom pagination is old style. These should be consistent. IIRC, the bottom ones were reverted because there was a bug we couldn't solve in time for that version's launch, but we never came back to fix it. Both top and bottom should allow text entry of page number.	jane
Future Releases	20013	Clean Up Touch UI for Left NavMenu / Flyouts		Administration	3.3.1	normal	normal	Future Release	feature request	new	reporter-feedback	2012-02-10T16:30:50Z	2013-01-22T15:24:19Z	While the flyout is mostly usable in it’s current state, it is not as intuitive as it needs to be for the best user experience. They are ineffective at best on the Kindle Fire’s Silk Browser, but work pretty well on the iPad.  We need to examine all target devices to ensure interactivity is supported cross-device.	georgestephanis
Future Releases	13516	Hide JS-only widgets on dashboard is no JS		Administration	3.0	normal	normal	Future Release	feature request	new		2010-05-24T13:16:42Z	2011-12-24T16:16:41Z	"We hide screen options and help; we should also hide these widgets instead of displaying by default with the 'you need JS' message. Affected modules: QuickPress, Incoming Links, Plugins, WordPress Development Blog, Other WordPress News. 

We should display an additional module for no-JS people that lets them know that their WordPress install would be even more awesome with JavaScript, and list out some of the features they would gain access to with JS enabled. "	jane
Future Releases	20729	Improve Admin Colors CSS enqueuing		Appearance	3.1	normal	normal	Future Release	defect (bug)	new	early	2012-05-22T17:19:58Z	2012-05-22T17:20:17Z	"The hacky way in which we enqueue the admin colors css means that you get different ordering of the CSS between the development version of the scripts and the script-loader sourced version of the scripts.

This can cause CSS bugs which don't show when developing but do when running with the script loader - e.g. #16827

It also makes it harder to implement a custom css concatenator.

We should do something like - http://core.trac.wordpress.org/attachment/ticket/16827/colors-hacked-fixed.diff

To make this properly enqueue the styles.

We should also make this kind of call fire a {{{_doing_it_wrong()}}} as {{{true}}} is not a url :)

{{{
$styles->add( 'colors', true, array('wp-admin') );
}}}

This code harks back from [7976]"	westi
Future Releases	20859	Theme Installer: Preview should be scrollable on iPad and Kindle Fire		Appearance	3.4	normal	normal	Future Release	defect (bug)	new		2012-06-06T21:51:09Z	2012-06-08T21:10:27Z	"Related to #20805. We've added techniques for smoothly scrolling iframes when they're the only frame on the page, but the theme installer still uses the overlay technique.

We may be able to iron this out in a similar fashion. Given that the old installer also used an overlay technique, this is not a regression."	koopersmith
Future Releases	7301	AtomPub interface should accept new categories provided by clients	josephscott	AtomPub	2.6	normal	normal	WordPress.org	enhancement	reopened		2008-07-15T04:54:22Z	2012-10-31T16:25:19Z	"The AtomPub interface successfully exposes access to the existing categories of a particular blog, via the URL:

http://[myblog]/wp-app.php/categories

But the category listing is identified as ""fixed"", and this pans out. When a  client attempts to provide a category term with a name that has not been seen before, the interface just ignores it.

It would be a nice enhancement to change the category collection to an editable one, and support provision of arbitrary new category names on supplied posts to the wp-app interface.

As it is now, there is no way to add categories via the AtomPub interface.


"	redsweater
Future Releases	9513	Wordpress should allow input of XHTML/HTML via Atompub	josephscott	AtomPub		normal	normal	Future Release	enhancement	new		2009-04-11T23:38:51Z	2011-03-14T09:50:06Z	"One of the intended purposes of Atom standard was to allow better way of including XHTML in the feed than with “escaping it” (see this [http://www.xml.com/pub/a/2003/08/20/embedded.html article by Norman Walsh in xml.com] with followup at [http://norman.walsh.name/2003/06/30/hardline 1], [http://norman.walsh.name/2003/09/18/unescmarkup 2], and [http://norman.walsh.name/2003/09/16/escmarkup 3], there is also [http://www.intertwingly.net/blog/1571.html an interesting discussion under this blogpost] and [http://www.tbray.org/ongoing/When/200x/2003/06/28/Learning Tim Bray’s essay on the same theme]) Even though even [http://norman.walsh.name/2003/09/16/escmarkup#comment0006 Norm agrees that he lost this fight], at least Atom provides ''opportunity'' for conscious authors to use namespaced XML properly.

Now, of course, the problem is that all this beauty is not supported by any known-to-me Atompub-accepting blog server. Particularly when this perfectly valid Atom 1.0 feed (take a look at [http://validator.w3.org/feed/#validate_by_input validator] if you don’t believe me):

{{{
<?xml version=""1.0"" encoding=""utf-8""?>
<atom:feed xmlns:atom=""http://www.w3.org/2005/Atom"" xmlns:dc=""http://purl.org/dc/elements/1.1/"" xml:lang=""en"">
  <atom:title>Late Night Thoughts on Listening to Mahler’s Ninth Symphony</atom:title>
  <atom:updated>2009-04-08T00:13:32+02:00</atom:updated>
  <atom:link rel=""alternate"" type=""text/html"" href=""http://matejcepltest.wordpress.com/""/>
  <atom:link rel=""self"" type=""application/atom+xml"" href=""http://matejcepltest.wordpress.com/feed/""/>
  <atom:author>
    <atom:name>Matěj Cepl</atom:name>
    <atom:email>ceplm@seznam.cz</atom:email>
  </atom:author>
  <atom:id>http://matejcepltest.wordpress.com/</atom:id>
  <atom:rights>Copyright 2007 Matej Cepl</atom:rights>
  <atom:entry>
    <atom:title>John 3:17 or The Golden Middle Ground Between Grace and Sanctification?</atom:title>
    <atom:link rel=""alternate"" type=""text/html"" href=""$url""/>
    <atom:id>urn:mc:ceplovi.cz:atom1:blog:jan-3_17-2008-07-10</atom:id>
    <atom:updated>2008-07-13T00:00:00+02:00</atom:updated>
    <dc:subject>John 3:17 or The Golden Middle Ground Between Grace and Sanctification?</dc:subject>
    <atom:content type=""xhtml"" xml:lang=""en"">
      <div xmlns=""http://www.w3.org/1999/xhtml"">
        <p>There is a couple of things, which make for me sense together
  	(and I am not sure, of course, whether they will make sense to you
  	as well), and which I would like to record here.</p>
        <p>“<span class=""scripture"">For God sent not his
  	Son into the world to condemn the world; but that the world
  	through him might be saved.</span>” (J. 3:17)  In some aspects and for some
  	people (like me) and in certain moments, this is even more important
  	than the previous verse, and yet it is quite rarely mentioned in the
  	Church. Maybe because it so clear, that nobody gets much fame to explain
  	(and there is not much to explain here?). For all of us, who live with
  	the idea of God-policeman, following our doings to punish severely any
  	small misstep, this is the good news.</p>
        <p>There is quite certainly something significantly wrong about preaching,
  	that we always quote only  (John 3:16)  and
  	we don’t continue one verse further. As if we are still more interested in what’s
  	there in gospel for me, and we don’t understand, that we are not the central figures
  	in whole Bible. Not that there wouldn’t be anything there for us, but … that’s another long
  	discussion I would like to have with Dave.</p>
      </div>
    </atom:content>
  </atom:entry>
</atom:feed>
}}}

is sent to Wordpress.com I get [http://matejcepltest.wordpress.com/2009/04/08/john-317-or-the-golden-middle-ground-between-grace-and-sanctification/ rather disasterous result].

According to [http://article.gmane.org/gmane.comp.web.wordpress.devel/27067 Peter Westwood] wordpress treats all content delivered by different modes of remote publishing as the same dummy plain text.

OK, so the request of this ticket (and hopefully place of further discsussion if necessary) is to fix this and make <atom:content type=""xhtml""> considererd and delivered so that wordpress would just accept the nodetree inside of such element as a body of the blogpost without much further changes.

Also #6128 might be caused by this."	mcepl
Future Releases	4965	Blog by Email: any images and attachments in your email are not being posted inline	westi	Blog by Email	2.3	normal	normal	Future Release	defect (bug)	new		2007-09-12T18:15:29Z	2009-10-11T21:07:33Z	"Blog by Email: any images and attachments in your email are not being posted inline

Remaining issue from #4829."	foolswisdom
Future Releases	18734	Subcategory archive does work with any name as parent category in URL		Canonical	3.0.1	normal	normal	Future Release	defect (bug)	new	needs-unit-tests	2011-09-21T15:10:46Z	2012-10-22T23:10:00Z	"Parent category is ''parentcategory'' and his sub category is ''subcategory''.

The URL will be ''domain.com/category/parentcategory/subcategory''.

The problem is, that you will get the same page if you use any words as ''parentcategory''.

Examples:
- ''domain.com/category/xxx/subcategory''
- ''domain.com/category/subcategory''
- ''domain.com/category/foo/bar/subcategory''

IMO {{{redirect_canonical}}} should do his work here (and sometimes it does).

In 3.1 it does redirect.
In 3.1.4 it doesn't redirect; after r17549.
In 3.2.1 it doesn't redirect.
Duck_ found that it does redirect before r18079.
In current trunk it doesn't redirect.


"	ocean90
Future Releases	11856	URL for 1st comments page is not canonical	markjaquith	Canonical	3.0	normal	major	Future Release	defect (bug)	new	reporter-feedback	2010-01-10T19:17:42Z	2011-12-22T01:55:08Z	"When WP generates URL for comments, it always includes comments page number. It should not do this when URL is for 1st comments page - in this case post URL is sufficient.

WP should also redirect to canonical URL version when someone will try to load URL like site.com/some-post/comment-page-1."	sirzooro
Future Releases	11738	sanitize_text_field() issue with UTF-8 characters	hakre	Charset	2.9.1	normal	normal	Future Release	defect (bug)	new		2010-01-06T07:39:11Z	2010-11-13T07:36:00Z	"See Description #11528

Suggested patch does not take UTF-8 properly into account. Function has been degraded in the commit(s) [12499], [12501] to not support shift-spaces any longer. Details about preg_replace and UTF-8 as well as a proper suggestion to fix w/o degration [https://core.trac.wordpress.org/ticket/11528#comment:10 here]."	hakre
Future Releases	12363	Comment permalink wrong when only listing one comment type		Comments	3.0	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-02-24T14:31:51Z	2010-11-13T07:46:50Z	"If you pass the `type` parameter to `wp_list_comments()` (for example, to show comments only and no pings), then comment permalinks can easily use the wrong page number as they expect there to be pings included. This is apparent after leaving a comment and WordPress attempts to redirect back to your new comment.

At first I was thinking you could tell WordPress that you're filtering to a type and it could compensate when determining the page number, but then I realized perhaps it'd just be better for `wp_list_comments()` to check if there were 0 comments returned for the query and if so, see if there are any of that type of comment available. If so, then we know we're on too high of a page number and can instead display the highest existing page. Then again this introduces SEO issues.

Ideas on what to do are welcome."	Viper007Bond
Future Releases	13792	Invalid reply link from comment admin when comment nested level > max		Comments	2.9.2	normal	normal	Future Release	defect (bug)	reopened		2010-06-09T07:05:56Z	2010-11-13T17:53:57Z	"I have a blog with nested comments enabled, max depth of 4. When the last level comment is posted, it no longer contains a Reply link.

However, in the Comment admin, the Reply link is still present. If used, this new reply will show up at the very bottom of the comment list once posted (even if other newer regular comments are entered, this new reply will still show up at the very bottom).

The bug is, basically, that Comment admin doesn't respect the max nested value."	archon810
Future Releases	22261	Recent comments widget makes additional queries when pagination is enabled		Comments		normal	normal	Future Release	defect (bug)	new		2012-10-23T14:19:59Z	2012-10-23T14:19:59Z	A continuation of #15400.	nacin
Future Releases	11359	Don't nofollow links in admin comments		Comments	2.9	normal	normal	Future Release	enhancement	new		2009-12-08T12:23:15Z	2011-04-15T08:25:24Z	"Links in admin comments shouldn't have rel=nofollow.

Admin comments are not user-generated content, and the site owner (admin) is vouching for the links just like when they link from the post itself. 

Therefore, this usage of nofollow is incorrect.

Also, if I go and edit a comment and remove nofollow from a link, WP adds it back. It shouldn't do that either.

Note that in the unlikely event of wanting a link in a comment to be nofollowed, this could still be done manually."	caesarsgrunt
Future Releases	6536	"Introduce the concept of ""read"" and ""unread"" comments for better workflow in the admin"	markjaquith*	Comments	2.5	normal	normal	Future Release	enhancement	accepted		2008-04-02T00:48:54Z	2012-03-08T01:31:11Z	"The Moderation Queue is a great way to manage your comment workflow.  All comments go in there, and you approve, spam, or delete them.  At the end you get a nice little ""0"" and you know you've dealt with all new comments.  This doesn't work for people who don't moderate every comment.  They have no idea when they are done, and which comments they have or have not looked at.

I'd like to add a {{{comment_read}}} column to the comments table.  It would be either ""1"" or ""0"".  There would be a new sub-tab for Comments: ""Unread comments (%d)""  This page would be just like the Moderation page, except that it would only show comments with {{{comment_read = 0}}}.  This could act as ""comment workflow central"" for both people who pre-moderate and people who post-moderate.  Unapproved comments would have the actions: Approve, Spam and Delete.  Approved comments would have the actions: Archive, Spam and Delete.  Clicking any of these actions would both carry out that action AND mark that comment as read, making it disappear from the ""Unread comments"" page.  (""Archive"" only marks it as read).

Enterprising theme developers could even have this status shown on the public blog, so that people know whether their comments have been seen.

For background on this idea, please see [http://markjaquith.wordpress.com/2008/03/20/the-comment-inbox/ The Comment Inbox]

Note that this has benefits for people who moderate every comment, because they can now store comments in the moderation queue (comments they want to remove from the blog, but not delete) without that getting in the way of their comment workflow."	markjaquith
Future Releases	7532	Need comment_modified_date_gmt for approvals and edits		Comments	2.6	low	minor	Future Release	enhancement	new		2008-08-17T04:45:49Z	2009-06-11T12:39:18Z	"Summary:[[BR]]
Currently there is only one date field for comments, comment_date_gmt. This is insufficient, because it represents only the creation date, not the approval date. The function get_lastcommentmodified can only check comment_date_gmt, which means that it can return an earlier date than the approval date. This can lead to RSS feeds wrongly returned HTTP 304 Not Modified responses. There needs to be comment_modified_date_gmt in addition to comment_date_gmt.

Steps to Reproduce:[[BR]]
(1) First comment is submitted.[[BR]]
(2) First comment is mistakenly marked as spam by Akismet.[[BR]]
(3) Second comment is submitted and posted.[[BR]]
(4) Check comments feed in RSS reader. Second comment appears in feed, first comment does not.[[BR]]
(5) Mark first comment as not spam.[[BR]]
(6) Check comments feed in RSS reader again.

Expected results:[[BR]]
Comments feed returns HTTP 200, because there is a new comment in the feed.

Actual results:[[BR]]
Comments feed returns HTTP 304.

Notes:[[BR]]
The same bug could occur in other circumstances. For example, if a comment was held for moderation.

"	lapcat
Future Releases	8071	Refrain from querying all the comments on a post when paged		Comments	2.7	normal	normal	Future Release	enhancement	reopened		2008-11-05T22:17:15Z	2012-07-16T04:35:24Z	"If a post has more than (comment_per_page) comments, we should query them specifically, not query all the comments and sort in PHP (doesn't scale well).

Logic:

if threading is off, use a simple limit query

elseif the page has equal or fewer comments than (comments_per_page), query them all

else query (comments_per_page) parent comments, and keep doing queries for their children, up to the threading limit (10)."	markjaquith
Future Releases	11151	Common White Screen of Death in wpdb		Database	2.8.5	normal	major	Future Release	defect (bug)	assigned		2009-11-16T15:07:53Z	2010-12-08T21:32:54Z	"I imported some 10.000 users into WP through a  custom script, using wp_insert_users().
Import successful, I could log in with new users.
Yet wp-admin/users.php page fails to load the users table; I got the admin header and menu but the page stopped loading when querying the DB for the users data.
I set WP-DEBUG to true, but still no error. NO errors in the server log also.
I eventually had to add 

define('WP_MEMORY_LIMIT', '64M');

to wp-config.php to get the users.php page working.
The problem here is that the page doesn't issue the usual PHP memory limit fatal error, I had to guess to sort it out.
"	nutsmuggler
Future Releases	12302	add_metadata() Fails to Store Serialized Values as BINARY	ryan	Database		high	critical	Future Release	defect (bug)	new		2010-02-20T10:52:15Z	2010-04-18T04:36:44Z	"Symptoms:

WordPress stores corrupt values in post_metadata if there are any non-UTF-8 bytes in the meta_value.

Steps to reproduce:

Call add_metadata() with non-UTF-8 values such as a latin-1 copyright char.

Even though the serialized string goes through prepare() before the query, MySQL is required to truncate the invalid value being assigned to the meta_value field.  The result is that the stored value can never be un-serialized.

This behavior can also be replicated by trying to inject CHAR(169) into any UTF-8 table query."	miqrogroove
Future Releases	10883	db-error.php not used for all DB failures	ryan	Database	2.8.4	normal	normal	Future Release	enhancement	new	dev-feedback	2009-10-01T02:45:28Z	2013-01-25T04:39:55Z	"db-error.php (the optional custom DB error message file to be placed in wp-content) does not get included all the time. Sometimes wp-db.php will use its {{{bail()}}} method to spit out its own message.  This code needs to be there too:

{{{
        if ( file_exists( WP_CONTENT_DIR . '/db-error.php' ) ) {
                require_once( WP_CONTENT_DIR . '/db-error.php' );
                die();
        }
}}}"	markjaquith
Future Releases	12819	wpdb::prepare support for null	ryan	Database		normal	normal	Future Release	enhancement	reopened		2010-04-02T18:15:19Z	2013-05-13T16:39:35Z	"now we can not submit null values using wpdb::prepare. if we lets say have datetime field that can be null, and execute query prepared with $wpdb->prepare(""update table set date_time_field = %s"", null) - it sets value of the field to 0, which results in 0000-00-00 00:00:00 date. what is happening here - null is quoted and passed as a string, that should not be the case."	roxaz
Future Releases	11319	oEmbed should be integrated into Add ... from URL experiences		Editor	2.9	normal	normal	Future Release	enhancement	new		2009-12-03T22:55:05Z	2010-10-28T08:50:33Z	"oEmbed should be integrated into Add ... from URL experiences

enhancement, ENV: WP 2.9-beta-2 ++ (trunk r12320)

For WP 2.9 we removed oEmbed from the UI, #11288.

The ""Embed"" field did not validate the oEmbed, that is part of the reason I recommended not incorporating UI for WP 2.9 -- I think JS based validation is essential to a good experience.

If you use the ""Insert an image from another web site"", once you input a URL, WordPress should automatically check if it is an oEmbed link and adjust and populate the fields as appropriate.

ADDITIONAL DETAILS

If JS is disabled, I see little benefit to including a oEmbed form. The ability just to include oEmbeds on their own line in the content seems like a good balance."	lloydbudd
Future Releases	6619	permalink field misleading in page editor: it displays the erroneous values		Editor	2.5	normal	normal	Future Release	enhancement	new		2008-04-06T14:48:15Z	2009-11-20T20:32:33Z	"if you create a sub-page, the permalink field should display the proper permalink.

currently, if you have:

site.com/page/

and when you create:

site.com/page/subpage/

the permalink shows:

site.com/subpage/

until it gets saved

the expected behavior would be for it to show the correct permalink.

the same remark applies when you then change the permalink. if the parent is no longer page, but rather page-2, then the permalink should update accordingly."	Denis-de-Bernardy
Future Releases	17210	Massive duplication of oEmbed postmeta	Viper007Bond	Embeds	3.1	normal	normal	Future Release	defect (bug)	reopened	dev-feedback	2011-04-21T23:38:35Z	2013-02-15T19:56:22Z	"Hey guys,

Ever since my blog grew to a considerable size (a few million PVs a month) and started slowing down and exploding my server, I've been looking and implementing various optimizations. During one such passes through the data, I noticed this really weird oEmbed related behavior, which I've been observing for a number of WP version upgrades.

I use [embed] shortcodes a lot, and every new post after a few minutes ends up with a ton of oembed caches that don't belong to it at all - they're all from other posts. Posts that don't even have [embed]s at all still have over 100 oembed entries in wp_postmeta.

Here's an example of just a small subset of data residing in the table:

[[Image(http://farm6.static.flickr.com/5230/5641419581_0610c9e267_b.jpg)]]

There are now about 150,000 entries in the wp_postmeta table due to this, half of which are duplicated _oembed entries, which I think has heavy impact on server load. Not only that but I'm sure WP is filling the table up with values by redoing oEmbed queries, which may explain that load shoots up very high at times when publishing.
{{{
mysql> select count(*) from wp_postmeta where meta_key like '_oembed%';
+----------+
| count(*) |
+----------+
|    81499 |
+----------+
1 row in set

mysql> select count(*) from wp_postmeta;
+----------+
| count(*) |
+----------+
|   148451 |
+----------+
1 row in set
}}}

Just look at how many times this random video embed value shows up in the table. I'm sure it was used in only one actual post:
{{{
mysql> select count(*) from wp_postmeta where meta_value like '%p2oWELcd-lI%';
+----------+
| count(*) |
+----------+
|      815 |
+----------+
1 row in set
}}}

Just to clarify - I don't have 815 updates to a single post that may have explained this - these are completely unrelated, separate, published posts.

To put things in perspective, here are the top 20 offenders:
{{{
mysql> select distinct meta_key, count(*) as cnt from wp_postmeta where meta_key like '_oembed%' group by meta_key order by cnt desc limit 20;
+------------------------------------------+-----+
| meta_key                                 | cnt |
+------------------------------------------+-----+
| _oembed_5607e41abb700707540a854ae76182cf | 864 |
| _oembed_984bc07d3bc0f61b6b35230cd2fa7ced | 859 |
| _oembed_da8ae36275b4576cfcd92c0ed455be96 | 859 |
| _oembed_71dd4068a9a6911f50dbe57b3ff477c5 | 858 |
| _oembed_9f817e820c23ccbfac9b22b3474e5dd3 | 858 |
| _oembed_f3c1c03a81bc301b5f1a063f65119328 | 857 |
| _oembed_31bf10d95cb7c8e9f646d9d6e5728da0 | 857 |
| _oembed_25d0ebf59c994050cb604900cf04f53f | 856 |
| _oembed_6265dae657e38579c0a8ddb66132d526 | 852 |
| _oembed_562dd8c13888905cbd15dbd74e8699cc | 849 |
| _oembed_30ea17d1cc73acd925a74373d2be32ec | 848 |
| _oembed_87f16916b4da6571f454266bfbfaebe0 | 847 |
| _oembed_9f1f038d43e973bd60929201eee24f57 | 843 |
| _oembed_d46317d44fe11c0d90ef2cc3b45bce57 | 843 |
| _oembed_b1f8685ba405feee46baf9408eb632f7 | 841 |
| _oembed_1b56f492eba4c4ea698d816d0ecf2d51 | 840 |
| _oembed_fe597714de4081e6e7e78a88256c7db4 | 840 |
| _oembed_fb843e7b604cbc4e1ffa144d4eb300c8 | 839 |
| _oembed_97b12f2f1e59ee6eff95c61095aa5bef | 838 |
| _oembed_2b94d9f7c28ee37bfbead0a622c8be85 | 838 |
+------------------------------------------+-----+
20 rows in set
}}}

I'm quite at a loss here and would appreciate the next debugging steps. I haven't been able to determine where things are going wrong on my own.

Thank you.

P.S. The site in question is AndroidPolice.com"	archon810
Future Releases	16925	Move the WP_Filesystem_SSH2 class to a plugin	dd32*	Filesystem		normal	normal	Future Release	defect (bug)	accepted		2011-03-22T00:16:08Z	2011-07-06T03:57:26Z	"I'd like to consider moving the WP_Filesystem_SSH2 class out of WordPress core and into a plugin.

The reasoning for this is simply due to the fact that the majority of users will not use it, It already requires the PHP extension to basically be custom-compiled (thanks to limited installations coming with the extension). 

In my opinion, This would be better served in a plugin, potentially with a PHP-based version as well: #10348"	dd32
Future Releases	15006	Invalid Content Markup		Formatting	3.0	normal	minor	Future Release	defect (bug)	new		2010-10-01T13:48:12Z	2011-01-13T06:29:30Z	"I have a page post that starts like this:

{{{
<p style=""text-align: right;"">Text Here</p>
<p style=""text-align: right;""></p>
More Text Here
}}}

The HTML source saves correctly, but the page output omits the closing tag for the second P element, causing the rest of the page to be invalid.

If you have any trouble reproducing this I will be happy to debug it on my server."	miqrogroove
Future Releases	4857	More issues with wpautop()	mdawaffe*	Formatting	2.3	low	normal	Future Release	defect (bug)	accepted	needs-unit-tests	2007-08-29T06:47:01Z	2009-11-28T06:33:01Z	"''Not sure if this should slide into 2.3 or if it can wait for 2.4. Change as need be.''

`wpautop()` has issues with closing `</p>`'s when it comes to HTML.

For example:

{{{
Foo<div>Bar</div>
}}}

Results in:

{{{
<p>Foo
<div>Bar</div>
}}}"	Viper007Bond
Future Releases	10645	auto_p and forms		Formatting		low	normal	Future Release	defect (bug)	new		2009-08-18T16:53:40Z	2010-11-13T01:38:14Z	"auto_p will errantly injects paragraph and linebreak tags in certain circumstances within forms:

`<div>
<label for=""select_element"">This is a select box placed <select name=""select_element""><option value=""1"">inline</option</select> with the label.</label>
</div>`

becomes:

`<div>
<label for=""select_element"">This is a select box that is pla­ced<br />
<select name=""select_element""><option value=""1"">inline</option><option value=""2"">inside</option><option value=""3"">within</option></select>

<p>inline with the label.</label>
</div>`

linebreak and paragraph tags should never be inserted inside a label. In this case they are not even properly paired.  It would be nice if the surrounding div was identified and no tags were inserted, although if a paragraph tag wrapped the whole thing, it would not be the end of the world.
"	kingjeffrey
Future Releases	11202	automatic line breaks in comments		Formatting	2.8.5	low	normal	Future Release	defect (bug)	new		2009-11-20T18:47:50Z	2010-04-02T07:34:29Z	"WordPress 2.8.6 has got a Problem with the automatic line break. [[BR]]
Example:[[BR]]
Type the following comment in a WordPress Blog. 
{{{
Thank you for your comment!<blockquote>this is a small quote</blockquote> Next Text 
}}}
Then you have to save the comment. If you validate the your publish, you will see, that the sentence ""Thank you for your comment!"" will be put into the following absurd tags: [[BR]]

{{{
p>Thank you for your comment!<br />
}}}

If you write a comment with the following code (hit return after the word ''comment! ''),[[BR]]

{{{
Thank you for your comment! 
<blockquote>this is a small quote</blockquote> Next Text 
}}}
you will get the right codeform when you validate your comment:
{{{
<p>Thank you for your comment!</p> 
}}}

The same Problem exists when you type [[BR]]

{{{
test 2 <p> break </p> next text
}}}
After the word ''test 2'' you will miss the </p>. [[BR]]

WordPress has got this bug with every single elements like these one: 

{{{
<p>, <ul>, <ol>, <li>, <h1> bis <h6>, <div>, <blockquote> etc.
}}}

When you make manuell a new line in front of these elements, you won't find any problem, so WordPress must put an automatic line break in front of these elements and it doesen't do it. Please fix this nerved bug!!

regards, Dunkelangst from http://www.dunkelangst.org/ "	Dunkelangst
Future Releases	6984	wpautop() formats the the contents of shortcodes		Formatting	2.6	low	trivial	Future Release	defect (bug)	new		2008-05-17T10:34:02Z	2009-11-28T07:20:24Z	"`wpautop()`, the bane of my existence as a plugin developer, is at it again.

Here's an example of some PHP wrapped in a valid shortcode in a post of mine:

{{{
[code lang=""php""]$text = str_replace( array('<p><p>', '</p></p>'), array('<p>', '</p>'), $text);[/code]
}}}

The content that gets passed to my shortcode function is this:

{{{
$text = str_replace( array('
<p>', '</p>

</p>
<p>'), array('
<p>', '</p>
<p>'), $text);
}}}

Expected result: it shouldn't touch the insides of valid shortcodes (like adding line breaks or anything as it is doing now)."	Viper007Bond
Future Releases	5250	wpautop() issue with lists		Formatting	2.3	normal	normal	Future Release	defect (bug)	new		2007-10-24T00:32:38Z	2011-07-30T15:34:50Z	"First of all, my sincere apologies if this is a duplicate.


The problem, in short: WordPress inserted a number of unclosed `<p>` tags into my post. It should either insert correctly closed tags, or none at all. I honestly would prefer the former.


In detail: I had HTML code very similar to this:

<ul>
  <li>text<ul>
    <li>subtext</li>
  </ul>more text</li>
</ul>


This was automatically converted to:

<ul>
  <li>text<ul>
    <li>subtext</li>
  </ul><p>more text</li>
</ul>

Note the extra `<p>` tag in the above, which is unclosed (making the W3C validator choke on my website).

Also note, I was not using the WYSIWYG editor (turning it off was the first thing I did), so it's unlikely to be due to that.


As a workaround, manually inserting properly closed `<p>` tags works just fine:

<ul>
  <li>text<ul>
    <li>subtext</li>
  </ul><p>more text</p></li>
</ul>

Since this workaround exists, the bug is not very prioritary, but it should also (hopefully) be easy to fix."	Narc0tiq
Future Releases	10033	wptexturize and wpautop problems with html comments and object tags		Formatting	2.8	normal	minor	Future Release	defect (bug)	new		2009-06-04T12:06:35Z	2010-11-23T05:43:55Z	"Bumped into this one when upgrading my mediacaster plugin to use swfobject 2.1 (which is not 1.5 compatible), as documented here:

http://code.google.com/p/swfobject/wiki/documentation

I take it I'm not the only one who is going to need to upgrade a plugin. It's minor, since I'll just move the filter further down in the queue, but it's still worth reporting:

{{{
<object id=""m544cf9700db147f751dc34ea1241d8bd"" classid=""clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"" width=""320"" height=""260"">
<param name=""movie"" value=""http://www.youtube.com/v/_nkZ3eHeXlc"" />
<!--[if !IE]>-->

<object type=""application/x-shockwave-flash"" data=""http://www.youtube.com/v/_nkZ3eHeXlc"" width=""320"" height=""260"">
<!--<![endif]-->
<p><a href=""http://www.macromedia.com/go/getflashplayer"">Get Flash 9.0</a> to see this player.</p>
<!--[if !IE]>-->
</object>
<!--<![endif]-->
</object>
<script type=""text/javascript"">
//swfobject.registerObject(""m544cf9700db147f751dc34ea1241d8bd"", ""9.0.0"");
</script>

}}}

Gets turned into the following mess:

{{{
<object id=""m544cf9700db147f751dc34ea1241d8bd"" classid=""clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"" width=""320"" height=""260""><param name=""movie"" value=""http://www.youtube.com/v/_nkZ3eHeXlc"" /><!--[if !IE]>&#8211;><br />
<object type=""application/x-shockwave-flash"" data=""http://www.youtube.com/v/_nkZ3eHeXlc"" width=""320"" height=""260""><br />
<!--<![endif]--></p>
<p><a href=""http://www.macromedia.com/go/getflashplayer"">Get Flash 9.0</a> to see this player.</p>
<p><!--[if !IE]>&#8211;><br />
</object><br />

<!--<![endif]--><br />
</object><br />
<script type=""text/javascript"">
//swfobject.registerObject(""m544cf9700db147f751dc34ea1241d8bd"", ""9.0.0"");
</script>
}}}

So, two/three issues:

 - wpautop should also ignore double object tags, and html comments
 - wptexturize should ignore html comments"	Denis-de-Bernardy
Future Releases	8213	WP text formatting functions handle block-level INS tag incorrectly	markjaquith*	Formatting	2.7	low	minor	Future Release	enhancement	accepted		2008-11-14T14:51:09Z	2009-06-11T14:26:44Z	"From W3C documentation:

""INS and DEL are used to markup sections of the document that have been inserted or deleted with respect to a different version of a document (e.g., in draft legislation where lawmakers need to view the changes).

These two elements are unusual for HTML in that they may serve as either BLOCK-LEVEL or INLINE elements (but not both). They may contain one or more words within a paragraph or contain one or more block-level elements such as paragraphs, lists and tables.""


----


When I want to use INS tag as BLOCK-LEVEL element (to wrap to paragraphs for example) wrong HTML is produced:


{{{
<p><ins datetime=""2008-11-14T14:45:27+00:00"">First paragraph.</p>
<p>Second paragraph.</ins></p>
}}}

Correct HTML should look like this:

{{{
<ins datetime=""2008-11-14T14:45:27+00:00""><p>First paragraph.</p>
<p>Second paragraph.</p></ins>
}}}

I think the same sitiuation occurs for DEL tag.

"	misieg772
Future Releases	5161	balance_tags option should not be in the user interface		Formatting	2.3	normal	normal	Future Release	enhancement	new	dev-feedback	2007-10-08T08:02:49Z	2013-01-22T01:19:58Z	"In the WP Admin → Options → Writing ({{{options-writing.php}}}), there is an option ""!WordPress should correct invalidly nested XHTML automatically"" which controls whether {{{balance_tags()}}} is run on post content or not.

I'm fully supportive of this feature — I think it's important to ensure the HTML that is output to browsers is valid. There have been a few situations where users needed to turn this off, e.g. bugs in the function, or a plugin misbehaves with it on (if I remember correctly, runPHP).

However, this is a KDE-style option where it is put there for a niche case. In 99% of cases, you will want it on.

A few people on the mailing lists have stated a number of times that we should take a GNOME-like approach to these sort of features, and let them be controlled only by plugins. This option is left over from the dark ages of !WordPress, and I don't think the cases for turning it off are big enough to warrant its inclusion in the user interface.

If a plugin has a problem with balancing tags (e.g. runPHP), the offending plugin can simply remove the filter.

{{{
remove_filter('content_save_pre', 'balance_tags);
}}}

(...or whatever the code would be.)

The new canonical redirect feature has far more many problems, and far more justification for it to be turned off, yet I don't see a checkbox ""Redirect links to their canonical URL"" anywhere in the user interface. If anything should have a checkbox, it's the canonical redirect feature — but, it doesn't have any such thing. So, we should remove this checkbox as well."	JeremyVisser
Future Releases	10489	UI Improvements for the gallery tab (edit post)		Gallery	2.8.1	normal	normal	Future Release	enhancement	new		2009-07-26T11:52:10Z	2010-10-28T08:48:06Z	"It would be nice to ever display the ""Gallery Settings"" Section on the gallery tab, even if only one image exists. That would help if you talk via phone and explain someone something. Often from-sections are helpfull to validate wether or not the other is on the same page as you are while explaining something.
"	hakre
Future Releases	16230	Category slugs not cut at 200 characters as it should under some conditions		General	3.1	normal	normal	Future Release	defect (bug)	new		2011-01-14T14:10:23Z	2011-07-17T02:21:27Z	"When a category name is longer than 200 characters, it is cut to 200 and so is the slug automatically created upon category creation.

Now, if you edit the category name or slug afterwards, again trying to set a name longer than 200 characters it is cut again.

But, if you edit the name or slug and use a very long string like this one:

%d1%85%d1%80%d0%b0%d0%bd%d0%b0/%d1%80%d0%b5%d1%86%d0%b5%d0%bf%d1%82%d0%b8/%d0%b4%d0%b5%d1%81%d0%b5%d1%80%d1%82%d0%b8-%d1%80%d0%b5%d1%86%d0%b5%d0%bf%d1%82%d0%b8-%d1%85%d1%80%d0%b0%d0%bd%d0%b0/%d1%81%d0%bb%d0%b0%d0%b4%d0%ba%d0%b8%d1%88%d0%b8-%d0%b4%d0%b5%d1%81%d0%b5%d1%80%d1%82%d0%b8-%d1%80%d0%b5%d1%86%d0%b5%d0%bf%d1%82%d0%b8-%d1%85%d1%80%d0%b0%d0%bd%d0%b0-%d1%80%d0%b5%d1%86%d0%b5%d0%bf%d1%/

Then the slug ends up being longer than the 200 chars limit.

Now if on the Categories list dashboard page you have more categories than visible on one page, and the category you edited above is not on page 1, the page it is on will appear empty (while successive pages will be all right if they contain regular categories)

This has been reproduced on 3.1-RC2-17283"	paolal
Future Releases	2691	HTML comments in posts aren't handled properly.		General	2.8.5	normal	normal	Future Release	defect (bug)	reopened		2006-04-25T03:16:37Z	2011-02-28T06:45:22Z	"When an HTML comment is added in a post, autop adds paragraph ( <p> ) tags around the comment and for multi-line comments line breaks ( <br /> ) are added after every line.  This should not happen in HTML comments.

This ticket is similar to #712 which was closed with wontfix.  I would like to know why this isn't seen as an issue?  It prevents the addition of RDF and other metadata, not to mention just plain old HTML comments in posts."	gord
Future Releases	14581	No magic numbers		General		normal	normal	Future Release	defect (bug)	new		2010-08-10T15:57:59Z	2010-11-26T21:54:49Z	Add defines for the numeric user_status and comment_status values.	ryan
Future Releases	14745	Renaming a Link-Category Resets Link Widget Options of that Category		General		low	normal	Future Release	defect (bug)	new		2010-08-31T13:21:50Z	2010-12-27T17:42:30Z	"When renaming the name of a Link Category that is used as well in a Link Widget, the Link Widget stops working.

Step to Reproduce:

 1. Create a Link Category ""Test Start"".
 2. Add 10 Links into the Category ""Test Start"".
 3. Go to the Widgets Screen and add a new Link Widget to a sidebar.
 4. Select that Link-Widget and set it from ""All-Links"" to the Category ""Test Start"".
 5. Visit your Frontpage so proof that the Widget displays.
 6. Go to the Link Cagegory Editor and quick-edit the ""Test Start"" Category.
 7. Rename it to ""Test End"".
 8. Save Changes.
 9. Visit your Frontpage.

''=>>'' The Widget has disappeared.

'''Expected behavior:''' Widget displaying with the (renamed) link category.

"	hakre
Future Releases	11414	Sidebar Calendar Widget broken		General	2.9	normal	normal	Future Release	defect (bug)	new	reporter-feedback	2009-12-12T22:33:24Z	2010-11-13T07:31:07Z	"I'm giving 2.9 beta a test drive for theme development purposes. On my test installation, I currently have the two default themes and a very simple theme of my own that I developed via a tutorial.

After I upgraded to 2.9 beta, the sidebar calendar started displaying rather oddly. It looks okay when the main page first loads, but when I click the <<Nov link, the calendar rows are way out of whack. When click on <<Oct, it's not as bad, but still incorrect. Then, when I go forward again and hit December, even that is a little bit off.

This happens whether I use the Calendar widget or just the theme's own sidebar, and it happens in all three installed themes.

My test site is at http://bleeder.faltarego.com
or http://faltarego.com/bleeder

Many thanks."	faltarego
Future Releases	11465	custom field duplicated	westi*	General	2.8.4	normal	minor	Future Release	defect (bug)	accepted		2009-12-16T21:09:23Z	2012-04-02T21:14:22Z	"When I enter the information for a custom field and click on Preview without first clicking Add Custom Field, the custom field is saved. But then when I click Publish, it is saved again, appearing in the post twice.

If I click Add Custom Field before Preview, subsequent Publish does not duplicate the custom field. But it is very convenient and efficient to be able to avoid a separate save of the custom field.
"	ericr23
Future Releases	15667	wp_list_pages, if it finds no pages to display, shows random child pages instead because of a bug in get_pages()		General	3.0.2	normal	critical	Future Release	defect (bug)	new		2010-12-03T19:12:46Z	2011-01-16T05:09:28Z	"How to reproduce:[[BR]]
- About page is published
- additionally, there is a number of parent pages[[BR]]
- these each have a number of children[[BR]]
- when calling wp_list_pages(), the ""exclude"" attr excludes all parent pages, and display only the About page.

This works as long as there is at least 1 other page published that is not in the list of excluded IDs. In this example, as soon as the About page is set to ""draft"", wp_list_pages stops working correctly.

So... with no other pages besides the excluded ones published, we do this:

1) wp_list_pages('title_li=&depth=1&exclude=3,5,7');
=> wp_list_pages SHOULD return nothing, but instead it displays all child pages of the first parent page ID in the ""exclude"" attr (here: 3).

Now we now add the ""exclude_tree"" attr just for fun:

2) wp_list_pages('title_li=&depth=1&exclude=3,5,7&exclude_tree=3,5,7');
=> should again return nothing, but instead, it displays the first-ever published child page globally (here: a child page of 5).

It looked like random behavior at first but I've been able to identify the above pattern. I'm guessing it's a failing condition somewhere in the function."	bobsoap
Future Releases	11642	Allow to define upload path and url in wp-config.php		General	2.9	normal	normal	Future Release	enhancement	new		2009-12-27T11:11:35Z	2012-09-28T11:44:33Z	When someone wants to move default directories elsewhere, he/she must do work in two places: add defines to wp-config.php and change upload path on settings page. I think it will be good to introduce two new defines: UPLOAD_PATH and UPLOAD_URL_PATH. When they will be defined, WordPress should use them and do not allow to change these on settings page - similarly to home and site url options.	sirzooro
Future Releases	23168	Introduce remove_post_status		General		normal	normal	Future Release	enhancement	new		2013-01-10T08:32:49Z	2013-05-10T12:37:37Z	Plugins and themes should be able to remove the default post statuses defined by core.	kovshenin
Future Releases	14946	Only enforce OEmbed whitelisting for dangerous types		General	3.0.1	normal	normal	Future Release	enhancement	new	dev-feedback	2010-09-23T08:23:48Z	2010-11-23T21:14:44Z	Of the four OEmbed response types, only two (video and rich) are potentially dangerous. We should be able to allow all photo and link responses, without a whitelist.	markjaquith
Future Releases	7745	Private posts cannot have unpublished or pending review status		General	2.6.1	low	minor	Future Release	enhancement	new		2008-09-15T16:32:19Z	2013-01-22T16:46:33Z	"Posts with private ticked are immediately set to published, and cannot be reverted to unpublished or pending review while private is ticked. Given the default use of private posts, this behavior is understandable, but it seems far simpler if the behavior remained consistent with public posts.

In our particular case, we are using Role Manager to allow subscribers to read private posts. A simple solution that suits our particular needs well. But we really need the full draft/review process, just as with public posts."	nyoungman
Future Releases	9785	Search Enhancements -- consolidated ticket		General	2.8	normal	normal	Future Release	enhancement	new		2009-05-10T23:54:34Z	2012-06-25T01:47:24Z	"Closing the following as dups, pending ""the big search overhaul"" that may never come:

 - #5149 -- search everywhere (with committed patch)
 - #9230 -- search in post and pages and both
 - #5525 -- also search for posts with search query as terms (tags, cats, ...)
 - #5054 -- allow to negate keyword on search
 - #7394 -- assign greater weight to posts with search query in title
 - #7647 -- search in attachment descriptions"	Denis-de-Bernardy
Future Releases	17780	Use PHP native double encoding prevention in htmlspecialchars()		General		low	minor	Future Release	enhancement	new		2011-06-13T08:03:13Z	2011-06-13T08:03:13Z	"Since PHP 5.2.3 the {{{htmlspecialchars()}}} function has an optional {{{$double_encode}}} parameter, which we could use. This can save us a few expensive kses/html decoding calls.

We need to make sure it works the same way as our implementation."	nbachiyski
Future Releases	16867	Where is it appropriate to use filter_var		General	3.2	normal	normal	Future Release	enhancement	reopened		2011-03-16T16:47:13Z	2012-02-08T14:22:28Z	"Now that we require PHP 5.2 we have access to a whole plethora of new functions.  One of those is [http://php.net/filter_var/ filter_var].  It seems like this could be useful for things like validating and filtering E-Mail addresses, URLs, IPs, etc. (there are plenty of [php.net/manual/en/filter.filters.php filters]).

This was brought up in #15379 where nacin said:
  Those can be buggy. We could potentially leverage it internally but we need to watch out for vulnerabilities and what not across PHP versions.

I mostly wanted this to be the place where we decide what could benefit from it and what shouldn't."	aaroncampbell
Future Releases	13436	Wordpress class_exists() conflicts with __autoload() and php_auto_prepend		General	3.1	normal	minor	Future Release	enhancement	reopened		2010-05-18T15:51:26Z	2010-12-14T17:42:54Z	"== Issue ==

Wordpress core (and many plugins) use class_exists().

http://php.net/manual/en/function.class-exists.php

When Wordpress is integrated with custom/third party applications that use php_auto_prepend and autoload() to include/require files based on the $class_name parameter this generates errors as class_exists() triggers the autoload() and the files cannot be found.

== To reproduce ==

Using php_auto_prepend specify a file to include before every page request that contains the following PHP code:

{{{
<?php
function __autoload($class) {
    include($class.'.php');
}
?>
}}}

Visit any front-end or back-end Wordpress page.

== Solution ==

As there is no autoload() function defined in Wordpress core the class_exists() should implement the second class_exists() parameter:

{{{
<?php
if (!class_exists('ExampleClass', false)) {
    ...
}
?>
}}}

This stops calls to __autoload() and would fix the errors seen when integrating Wordpress with apps that implement this.

I have implemented this and tested it and Wordpress works fine, but I can't find out where the SVN repo is for Wordpress 3 Beta 2 (the SVN page on the site takes me to 2.x).

If someone could supply a link for SVN CO of WP3 I can provide the patch."	galbus
Future Releases	14653	Log IP address un UserMeta when account is created		General		normal	normal	Future Release	feature request	new	dev-feedback	2010-08-20T01:41:24Z	2010-10-28T10:18:48Z	"As WordPress becomes more and more a CMS for everything, not just blogs, managing users becoms more important.  With MultiSite and user registration more open, WordPress should have a built in way to record the IP address of a user.

So at registration, log the IP in usermeta. Done, easy.  List it on the user page.

At comments, obviously, it's already logged, so nothing needs be done there.  Also, since you can already click on an IP and list all comments made from that address, there wouldn't be much else that needs to be done."	Ipstenu
Future Releases	16870	consider disabling HTTP transport after multiple failed requests		HTTP	2.9	normal	normal	Future Release	enhancement	new	dev-feedback	2011-03-16T23:18:45Z	2011-07-16T23:31:02Z	"There has been a number of reports over the lifespan of the cURL HTTP transport failing with an error during upgrades:
{{{
WP HTTP Error: name lookup timed out
}}}

This is a common error from cURL on badly configured installations (specifically, IIRC it lacks DNS Resolving in cURL, sometimes it just required an extended amount of time to resolve, others, it simply can't resolve)

Like we do with fsockopen() I think it'd be worth disabling the cURL transport for x hours when it hits this particular error condition..

Related threads: http://wordpress.org/support/topic/dashboard-issues-rss-error-wp-http-error-name-lookup-timed-out and http://wordpress.org/support/topic/plugins-update-failure  Both old threads, so this may only affect a PHP4 version of cURL.. For tracking purposes, I've finally created this ticket."	dd32
Future Releases	15677	It is not possible to install multiple variants of the same language		I18N	3.1	normal	normal	Future Release	defect (bug)	new		2010-12-04T15:07:28Z	2011-06-04T10:21:10Z	"Because of the way {{{mu_dropdown_languages()}}} and {{{format_code_lang()}}} work, it is impossible to have multiple variants of the same language installed. The list of languages returned by {{{mu_dropdown_languages()}}} only includes one variant of each language (the one with the country code which comes last when sorted alphabetically).

For example, if .mo files for es_ES and es_PE are both installed, then only es_PE will be shown.

Furthermore, whatever variant of the language is installed, the name will be the same, not indicating the correct language variant. In the example above, the language name will be ""Spanish; Castillian"", even for the es_PE localisation. This is highly misleading.

A final problem is that the langauge names are not localised themselves, with the exception of ""English"".

The cause of these problems is the fact that {{{format_code_lang()}}} ignores the country code and only considers the language code when choosing the name to return. Furthermore, it returns hardcoded language names rather than translated names.

Since {{{mu_dropdown_languages()}}} uses the return value of {{{format_code_lang()}}} as the key for its internal {{{$output}}} array, this means that later language variants overwrite earlier ones."	caesarsgrunt
Future Releases	7837	Localization of numbers should be supported		I18N		low	minor	Future Release	defect (bug)	new		2008-10-06T16:46:16Z	2009-11-23T15:21:12Z	I'm new to WordPress so please bear with me: I believe localization of numbers should be added to WordPress features. This means that, if you install WordPress and use (for example) Arabic language packs, numbers should be shown using Arabic digits, not English digits.	huji
Future Releases	14981	Two i18n misses		I18N	3.3.1	normal	normal	Future Release	defect (bug)	new		2010-09-27T23:21:29Z	2012-02-07T22:40:08Z	"1) /wp-admin/nav-menus.php: the ""Most Recent"" string (/wp-admin/includes/nav-menu.php:645) should be separated between the Pages context and the Articles context, since they can take different forms according to the language (i.e.: in French, ""Articles"" is masculine, ""Pages"" is feminine.

2) /wp-admin/edit.php: Same contextual need for ""All"", ""Published"", ""Scheduled"" and the rest of the per-status selector, for posts and articles (and others...). "	xibe
Future Releases	20738	Improve Javascript Word Counting for TinyMCE		I18N	3.4	normal	normal	Future Release	enhancement	new		2012-05-23T21:07:54Z	2012-05-30T13:57:17Z	"This is a follow on from #8759 to further improve the code.

While we improved it in 3.4 we can do a better job to more fully support the customisation for all different locales.

For know issues see the comments on the previous ticket."	westi
Future Releases	17120	Class WP_Importer references STDIN which is not available in Web Environments		Import	3.0	low	minor	Future Release	defect (bug)	new		2011-04-13T09:58:12Z	2011-04-13T09:58:12Z	"STDERR is not defined in web environments (only certain CLI environments), you can call fopen('php://stderr'); directly, however this is not delivered to browsers.

Since this is in the Multisite code, CLI imports might be more common, but it's not a given that multisite imports will not be run from the web either.

Code ref:
http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-importer.php#L128
{{{
126	                        $blog = 'http://' . preg_replace( '#^https?://#', '', $blog_id );
127	                        if ( ( !$parsed = parse_url( $blog ) ) || empty( $parsed['host'] ) ) {
128	                                fwrite( STDERR, ""Error: can not determine blog_id from $blog_id\n"" );
129	                                exit();
130	                        }
131	                        if ( empty( $parsed['path'] ) )
132	                                $parsed['path'] = '/';
133	                        $blog = get_blog_details( array( 'domain' => $parsed['host'], 'path' => $parsed['path'] ) );
134	                        if ( !$blog ) {
135	                                fwrite( STDERR, ""Error: Could not find blog\n"" );
136	                                exit();
137	                        }
}}}

I'm unsure of the best way to tackle this, Ideally in a CLI environment we want the error outputs going to STDERR, but since that's not available or visible to web browsers, wp_die() would be a better choice.

One potential method would be to direct wp_die() to STDERR in CLI environments - That might cause problems with the test suite however (I'm unsure)"	dd32
Future Releases	19764	Invalid JSON in custom fields meta value after export		Import	3.3.1	normal	normal	WordPress.org	defect (bug)	new		2012-01-06T17:13:07Z	2012-09-10T10:12:22Z	"Hey there,

I exported a working copy of my online WordPress site to a local copy and noticed that the code gets changed; The backslash is removed which causes the json format to be invalide.
Original code in the custom fields meta

{{{
{""videos"":{""0"":""<iframe width=\""480\"" height=\""360\"" src=\""http://www.youtube.com/embed/YAozOaxXYx4\"" frameborder=\""0\"" allowfullscreen></iframe>""}}
}}}

Becomes in the local site after import 
 
{{{
{""videos"":{""0"":""<iframe width=""480"" height=""360"" src=""http://www.youtube.com/embed/YAozOaxXYx4"" frameborder=""0"" allowfullscreen></iframe>""}}
}}}
"	abdessamad idrissi
Future Releases	8877	dotclear import don't set the post category	westi*	Import		low	normal	WordPress.org	defect (bug)	accepted		2009-01-17T22:05:20Z	2012-05-24T22:32:57Z	"when importing from dotclear, all the posts are set only to the default category.

i think the problem is due to the fact that wp_set_post_categories do nothing if we pass it only one category (don't know why...)

( in /wp-admin/import/dotclear.php, line 479 )
{{{
				// Make Post-to-Category associations
				$cats = array();
				$category1 = get_category_by_slug($post_cat_name);
				$category1 = $category1->term_id;
}}}

should be 
{{{
				// Make Post-to-Category associations
				$cats = array(get_option('default_category'));
				$category1 = get_category_by_slug($post_cat_name);
				$category1 = $category1->term_id;

}}}
"	olivM
Future Releases	4555	Better Typepad / MT Import - Atompub importer	lloydbudd	Import	2.3	normal	minor	WordPress.org	enhancement	new		2007-06-28T03:16:12Z	2011-09-15T17:17:07Z	"Typepad in particular does some really funky things with permalinks. They often have no relation to anything in the title, and none of their ""slug"" information is contained in their standard export, so there is literally no way to redirect those links.

It is possible to create a custom Typepad template that includes the needed information, and modify the WP importer to parse the extra info into slugs. Right now this is a hack, we should make this more intuitive."	matt
Future Releases	12227	Tags are converted to categories upon importation of content from Blogger		Import	2.9.1	normal	normal	WordPress.org	enhancement	new		2010-02-14T18:24:13Z	2012-05-24T22:32:40Z	When I imported posts from my old blog at Blogger/Blogspot, all the tags used for the Blogger posts were converted to categories in WP.  	dwstultz
Future Releases	22837	"WP Needs to Set ""Sender"" and ""Reply-To"" or DKIM/DMARC will not work using wp-mail (via PHPMailer)"		Mail	3.4.2	normal	normal	Future Release	defect (bug)	new		2012-12-09T17:23:48Z	2013-01-24T03:58:25Z	"I notice that for DKIM to function (while using DMARC) correctly for outgoing mail the PHPMailer object needs to make sure the Sender and Reply-To fields match the ""From"" field otherwise the ""Return-Path"" header uses the server it is sending from causing a mismatch.  When this happens DKIM fails authentication on the receiver side because it is not added to outgoing mail.

I tried adding the reply-to and sender header manually to wp_mail() but it did not work.  One had to do the following:

Right now i have to manually modify the /wp-includes/pluggable.php file in the wp_mail() function to include:

{{{
	if (strlen($phpmailer->Sender)==0)
	{
		$phpmailer->Sender = $phpmailer->From;
		$phpmailer->AddReplyTo($phpmailer->From);
	}
}}}

This resolves the problem and DKIM works again.
"	kellogg9
Future Releases	15807	Featured image doesn't attach to post		Media	2.9	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-12-14T11:57:23Z	2010-12-26T23:09:57Z	"When you use an image as featured, it doesn't attach to the post. 

Possibly related with #14390 (post image (thumbnail) in [gallery])

Tests:

• If the image is already attached, it doesn't reattach ✔

• If the image is uploaded while writing the post, it attaches like another image, even if you are not using it in the post. ✔

• If an image is in the media library, not attached, and you use it in your post, it automatically attaches to the post. ✔

• If the image is in the media library, not attached, and you use it as featured image in a post, it doesn't attach ✘
"	bi0xid
Future Releases	10752	Uploading new media to existing posts/pages backdates file location		Media	2.8.4	normal	minor	Future Release	defect (bug)	new		2009-09-08T20:35:20Z	2012-08-28T20:57:35Z	"Using WP 2.8.4, when uploading new media files to a page or post that has already been published, the new file is added in the /UPLOAD_DIR/year/month/ directory that corresponds to the original page/post publication date, rather than the file upload date.

Also, the correct file-upload-date-based directory is created (if it does not already exist), but the file is still placed in the older incorrect directory.

Example: Assume the following...

On /wp-admin/options-misc.php:
  * ""Store uploads in this folder"" (referred to above as UPLOAD_DIR) is set to ""wp-content/uploads"" or any other location, such as ""files""
  * ""Organize my uploads into month- and year-based folders"" is checked

On an existing Page:
  * Page has a published date of 3/1/2008
  * File a_test_file.jpg is uploaded on 9/1/2009
  * UPLOAD_DIR is set to ""wp-content/uploads"", has 777 permissions, and contains no subdirectories or files

WordPress 2.6.x and below would have created the following:
  * /wp-content/uploads/2009/09/a_test_file.jpg

However, WP 2.8.4 is creating:
  * /wp-content/uploads/2008/03/a_test_file.jpg
  * /wp-content/uploads/2009/09


This issue was previously mentioned on the wordpress.org forums as being a known issue with WP 2.7.1: http://wordpress.org/support/topic/254786"	dpie
Future Releases	13568	Add filters to media uploader		Media	3.0	low	minor	Future Release	enhancement	new		2010-05-27T01:02:56Z	2011-12-30T13:12:12Z	"In wp-admin > includes > media.php:

There should be a ""gallery_fields_to_edit"" filter similar to the ""attachment_fields_to_edit filter"", allowing gallery options to be filtered out. (Begins line #1749)

Additionally, it should be possible to disable the ""Insert into Post"" button below each image (I believe it's line #1239 of the current build).

I'm sorry, but my PHP knowledge is insufficient to write a working patch."	nudnik
Future Releases	17247	Crop tool is automatically selected when editing an image		Media		normal	normal	Future Release	enhancement	new		2011-04-27T00:17:31Z	2011-04-27T09:34:31Z	"The crop tool is automatically selected when editing an image with the built-in tools. This can be confusing as the crop button is greyed out and inactive by default.

To reproduce:
1. Create a new post or page
2. Upload an image
3. Click the Gallery tab
4. For the image you uploaded click ""Edit Image""

The crop tool will be automatically selected. If you drag the mouse over the image it will select an area to crop.

A more intuitive behavior would be to have none of the editing tools selected by default.

Currently, the next step is presumed when you click ""Edit Image."" It would be better to leave the next step up to each user so that clicking ""Edit Image"" didn't imply a default action."	andrewspittle
Future Releases	11078	"Media Library tab in post editor should have ""Unattached"" and ""Trash"" filter options"		Media	2.9	normal	minor	Future Release	enhancement	new		2009-11-05T04:16:04Z	2010-01-06T03:45:50Z	"The master Media Library admin page has options for viewing attachments based on their status, not just type—but the post editor media management only allows sorting based on type.

Having at least the ability to filter for unattached media items would be useful when editing a post. Occasionally users could have older media that is not yet attached to a post and could get buried in the media pages by newer items."	markel
Future Releases	13372	Separate Image sizes for different post types		Media		normal	normal	Future Release	enhancement	new	close	2010-05-13T07:59:07Z	2013-01-03T16:14:23Z	Would be nice, especially moving forward with custom post types to have the ability to set different image sizes using an additional parameter of `add_image_size()` for different post types: Page, Post, and Custom.	brandondove
Future Releases	10950	Download external files to Media Library		Media		normal	normal	Future Release	feature request	new		2009-10-13T15:48:43Z	2011-08-04T19:11:02Z	"The media uploader currently allows you to upload a file from your local computer or link to an external URL. 

However, when linking to an external URL (in particular for an image), you don't get the same options as you would have when actually adding a resource to your site's media library.

It would be nice to be able to fetch a file from an external source, and add it to the library, just as with a regular file upload. Then the file could be included in a gallery, you could use the image editor to crop/resize, etc.

Primary use-case would be to fetch an external image into the library without having the extra steps of saving to your local computer, then re-uploading it to your WP site. However, it should work with any allowed content-type (audio, video, pdf, etc).

It may also be useful to save the original URL as attachment metadata.
"	dougal
Future Releases	14884	Add a filter inside admin-ajax.php for walker		Menus	3.0.1	normal	normal	Future Release	enhancement	new		2010-09-16T14:01:31Z	2010-11-18T09:19:16Z	"I'm trying to extend the Wordpress menu system and i can't get the things working from start because inside admin-ajax.php on line 841, there is no filter. I'm talking about this piece of code

{{{
if ( ! empty( $menu_items ) ) {
		$args = array(
			'after' => '',
			'before' => '',
			'link_after' => '',
			'link_before' => '',
			'walker' => new Walker_Nav_Menu_Edit,
		);
		echo walk_nav_menu_tree( $menu_items, 0, (object) $args );
	}
}}}

The Walker_Nav_Menu_Edit class is applied by default.
If someone can add a filter, it would be great for all developers."	dmad
Future Releases	10597	More classes in menu generated using wp_list_pages and wp_page_menu	ryan	Menus		normal	normal	Future Release	enhancement	new		2009-08-12T11:17:41Z	2010-03-01T20:46:38Z	"I think that dev team should think about adding more classes to positions generated by wp_list_pages and wp_page_menu as it's very hard to style those menus. I'm thinking about class ""parent"" for every li that contains another ul etc. We got current_page_ancestor and others but they only work if you're on the child ..."	newkind
Future Releases	14331	Tweaks to menu setup page		Menus	3.0	normal	normal	Future Release	enhancement	new		2010-07-16T21:30:45Z	2012-08-07T10:47:34Z	"It would be great if you could select a parent Page and ""Automatically add children"" to the menu.  

In a similar fashion, it would be great if the Menu could then automatically add any new children Pages created under that Parent."	mrmist
Future Releases	17904	Multisite has more restrictions on user login character set		Multisite	3.0	normal	normal	Future Release	defect (bug)	new		2011-06-27T11:09:12Z	2013-02-12T20:54:04Z	"Multisite has more restrictions on the characters allowed in a user's login name compared to single site. This seems unnecessary and confusing. It was also the root of a recent bug in the importer, see [http://wordpress.org/support/topic/invalid-author-importing-single-wordpress-to-mulitsite-wordpress?replies=21#post-2186667 this forum thread] and the [http://plugins.trac.wordpress.org/changeset/401649 workaround].

I haven't worked up a patch yet since there seem to be a few locations where these restrictions are enforced and I don't know if I have found them all yet:

 - wpmu_validate_user_signup() uses the regex `/[a-z0-9]+/`
 - ms-default-filters.php adds `strtolower` to `sanitize_user`

Relevant: http://mu.trac.wordpress.org/changeset/1689 [12948]"	duck_
Future Releases	12832	Use the same data type for site statuses	database	Multisite	3.0	normal	normal	Future Release	defect (bug)	new		2010-04-03T19:48:20Z	2012-01-31T17:50:59Z	"For status archived we use:

{{{
archived enum('0','1') NOT NULL default '0',
}}}

Fo the others:

{{{
public tinyint(2) NOT NULL default '1',
mature tinyint(2) NOT NULL default '0',
spam tinyint(2) NOT NULL default '0',
deleted tinyint(2) NOT NULL default '0',
}}}

Shouldn't we use the same data type for the others?
"	ocean90
Future Releases	13554	Wordpress MU canonical link redirect failure	markjaquith	Multisite	2.9.2	normal	normal	Future Release	defect (bug)	new		2010-05-26T16:30:37Z	2010-11-13T08:02:46Z	"This problem manifests itself in Wordpress '''MU''' 2.9.2, but '''not''' in Wordpress 2.9.2.

In the MU install where blogs are subdirectories, canonical redirects work correctly for the subdirectory blogs, but not for pages on the root blog.

For example, [http://silverwarethief.com/essays/] is a sub-blog in the wordpress MU install. If you alter that link to [http://www.silverwarethief.com/essays/] wordpress MU will correctly redirect the browser to the canonical url.

However, this does not work with pages on the root blog. [http://silverwarethief.com/about/] is a page on the root blog. If you go to that link, you will correctly find yourself at the ""About"" page. If you then alter the link to [http://www.silverwarethief.com/about/] you will be redirected to the main page of the root blog, not the ""About"" page.

I have seen this behavior manifested on more than one MU install.

"	rundi
Future Releases	12030	Better Options for New Registrations		Multisite		normal	normal	Future Release	enhancement	new		2010-01-26T00:23:07Z	2012-04-18T17:13:58Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/872



At the moment when new users register, there are very few options and not many plugins available.. It would be nice if the administrator could :

1) Allow passwords to be set during registration, rather than having it sent by email.

2) Make Email Verification optional.

3) See the users who haven't confirmed their registrations, and resend the confirmation emails from the admin area..

4) User Moderation : Make it easier to kick out users and delete spammers.. 

5) Invitation Codes (Optional): Allow the admin to create invite codes, which he can distribute, so that the mu install is well knit social community.

I know this is pretty much doable, but there lacks any good solution at the moment.
"	wpmuguru
Future Releases	14172	Implement $scheme in site info in ms-sites edit site		Multisite	3.0	normal	normal	Future Release	enhancement	new		2010-07-01T22:45:33Z	2010-07-03T19:17:45Z	"In WordPress 3.0 with Network enabled, if you were to click:

Super Admin -> Sites -> Edit (next to any site) and then change any of the Site Options i.e. wp_2_options the changes don't save. 

We're running a secure environment and need Siteurl to be HTTPS instead of HTTP. Changing all the parameters to https and clicking Update doesn't save the changes."	firmdot
Future Releases	18161	Bulk action: Add user to multiple sites		Network Admin	3.2	normal	normal	Future Release	feature request	new		2011-07-18T19:07:04Z	2011-09-10T05:44:38Z	"Currently, to add a single user to multiple sites, the super admin has to edit each site, add the user to the site, and then go on to the next site.

To improve this workflow, it would tremendously useful to be able to add a single user to multiple sites in the network admin.

This ticket could have scaling problems to solve."	danielbachhuber
Future Releases	8492	Page name drop-downs do not scale well		Optimization	2.7	normal	normal	Future Release	defect (bug)	new		2008-12-04T22:59:17Z	2009-11-23T21:30:53Z	"The page title drop-downs on options-reading and page.php seem to scale poorly in page loading times when you have a large number (around 1000) of Pages.  

I need to go to bed now so haven't researched this much, but I think the options-reading bit could be improved - I think it's currently fetching all of wp_posts when it only needs the title, which is a fair bit of wasted DB and processing time. 

rev 10051 and previous."	mrmist
Future Releases	16894	Bulk load Comment Meta upon access		Performance	3.1	normal	normal	Future Release	defect (bug)	new	dev-feedback	2011-03-19T11:19:27Z	2011-03-19T12:12:05Z	"When we query posts, we bulk load all of the posts meta and taxonomies at the time of request. Since adding comment meta, we load the comment meta on-the-fly since nothing really currently uses it in core.

I've added a filter to ''get_comment_text'' which modifies the comment content based on the value of a meta key.

The problem arises when multiple comments are displayed on a page, The metadata for every comment is loaded individually:

{{{
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (4)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (5)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (6)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (7)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (34)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (35)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (37)
}}}

in all cases, the function stack is:
{{{
comments_template, wp_list_comments, Walker->paged_walk, Walker_Comment->display_element, Walker->display_element, call_user_func_array, Walker_Comment->start_el, call_user_func, twentyten_comment, comment_text, get_comment_text, apply_filters, call_user_func_array, MY_FUNCTION_HOOKED_TO_GET_COMMENT_TEXT, get_comment_meta, get_metadata, update_meta_cache #12 (0.7ms)
}}}

It isn't ideal that every comment causes an extra query, instead, we should bulk load comment meta for the comments being displayed. 

However, Since comment meta is not always used, in order to keep the load down, I'd suggest that we only bulk load the comment meta '''on the first request for comment meta''', this should allow current users to have no detrimental affect on query count/performance, whilst allowing those who use comment meta to manage each comment better performance."	dd32
Future Releases	22192	update_metadata() and update_option() strict checks can cause false negatives		Performance		normal	normal	Future Release	defect (bug)	new	needs-unit-tests	2012-10-15T03:19:23Z	2012-10-15T10:22:31Z	"Given this:

{{{
add_post_meta( $post_id, 'key', 1 );
update_post_meta( $post_id, 'key', 1 );
}}}

The update should not work, because they are the same. However, the meta cache will have ""1"" as a string, and then it will strict compare it to 1 as an integer. Thus, an unnecessary update will run.

Best I can tell, this could also affect update_option().

It is quite common to use integers and booleans directly into these functions. They should be smart enough to recognize that ""1"" == 1 == true and ""0"" == 0 == false, and that any numeric string is also equal to a properly cast integer.

Unit tests needed.

Ticket from which this was spun: #22189, saving navigation menus is slow."	nacin
Future Releases	16343	API for WP_Scripts: allow async loading, version checks		Performance		normal	minor	Future Release	enhancement	assigned		2011-01-22T18:07:39Z	2011-01-25T15:48:01Z	"When developping a theme lately, I have found myself in the need of directly accesing the internals of the WP_Scripts class. I feel the funcionality I need might well help other developers.


Use cases:

1.- Asynchronously load a (JS) script loaded by a/another plugin

  When loading a certain page, we needed to asynchronously load some (relatively heavy) scripts which are only seldom used. In order to keep page rendering fast, we only load them on demand, after the page frame has been rendered.
  In order to avoid having to bundle (potentially conflicting versions) scripts in every plugin and prevent duplicate loading, I suggest adding an API which would enable querying the source (as used by 'scripts-loader') 


2.- Version checks for loaded scripts

  For high-performance sites, it might be useful to load a Google (or some other CDN) -provided jQuery et al ---which the user might already have cached--- instead of the bundled one, as long as it is the same version.

 Code example:
   $ver = $wp_scripts->version('jquery');
   wp_unregister_script('jquery');
   wp_register_script('jquery',""http://ajax.googleapis.com/jquery/$ver/jquery.min.js"",false,$ver);


(needs discussion)



I can provide the code (or the patch against Core) when the solution is decided (or soonish, if a proof-of-concept is needed)
If WP 3.2 is going to finally be PHP 5.2+, I'd rather basically rewrite WP_Scripts (and/or WP_Dependencies).
"	jltallon
Future Releases	17246	Handling of HTTP 404 errors for non-existing files		Performance		normal	normal	Future Release	enhancement	new		2011-04-26T18:50:15Z	2011-05-12T04:19:27Z	"Generally if WordPress sees a request for a specific file it means the web server couldn't find that file. Currently we run all of WordPress in such cases and output the theme's 404 template.

If the missing file is an image that has been reused 10 times (perhaps a CSS background or sprite) we will run ten extra times on every page load.

What I'm proposing is to short-circuit all requests for specific files very early in the load cycle, the same way we do it for favicon.ico requests and output a generic 404 notice."	azaozz
Future Releases	11585	WordPress should cache failed feed fetches so as to avoid overloading feed sources		Performance	2.9	normal	normal	Future Release	enhancement	new		2009-12-24T02:25:17Z	2010-03-01T16:41:13Z	"Following up on #11219, which fixed the cause of that particular error, but not the one that related to caching of feed errors.

When SimplePie fails to fetch or parse a feed, it should not hammer whichever server the feed came from on every page load. This is bad for two reasons: it disturbs the originating server, and it tremendously slows down page loads when the feed is in an RSS widget on the front end.

Instead, we should cache the error for a reasonably long amount of time (15 minutes? An hour? More?) and bypass SimplePie until that duration expires."	Denis-de-Bernardy
Future Releases	8905	Category pagination broken with certain permalink structures	ryan	Permalinks	2.7	normal	normal	Future Release	defect (bug)	reopened		2009-01-21T07:26:31Z	2013-01-03T21:37:18Z	"If one uses a permalink structure with %category% followed by %postname%, accessing pagination can cause a 404, as WordPress attempts to look for a post called ""page"".

As per http://barefootdevelopment.blogspot.com/2007/11/fix-for-wordpress-paging-problem.html

Presumably can occur with other permalink structures too."	rmccue
Future Releases	5305	permalinks broken when article name is numeric	ryan	Permalinks	2.3.1	normal	major	Future Release	defect (bug)	new		2007-11-01T21:27:54Z	2013-05-09T15:51:24Z	"if you create numeric-only post name, the generated slug is this number - this conflicts with article ID, so it returns different article or 404 page, never the article. It can be then solved by generating manual slug with some char in it, but i think it would be better to include some char in that case, e.g. underscore, like _123

Also if someone will try to solve this, it would be nice to solve other problem - if post slug is begining with the slug of the category, than the category page returns that post, not the category"	thomask
Future Releases	8515	Archive Permalink	ryan	Permalinks		lowest	trivial	Future Release	enhancement	new		2008-12-06T22:08:05Z	2009-06-13T18:39:14Z	"Currently in the permalink settings, you can set a category and a tag base. I propose that an archive base also be added. It would be useful in that you could disallow the archive base in robots.txt (much like many do with the tag and category base), but still allow robots to get the posts.

Presently, doing this is a problem, as if you disallow /2008, for example, it will also disallow the robot to access the individual posts."	LuckyBambu
Future Releases	9825	Enforce permalink history, outright		Permalinks	2.8	normal	normal	Future Release	enhancement	assigned	dev-feedback	2009-05-15T01:06:37Z	2011-02-16T12:02:57Z	"currently, we enforce old slugs and www pref (not even sure that works, since I ended up fixing it in a plugin). canonical doesn't work for pages, or hardly.

we should enforce permalink history, outright. store it in a a db field, and query against it to optimize url2post()."	Denis-de-Bernardy
Future Releases	1914	Permalinks for unattached uploads/attachments		Permalinks	1.6	normal	normal	Future Release	enhancement	reopened		2005-11-19T09:21:26Z	2012-10-31T21:56:22Z	"Currently attachement links are in the form:

{{{
http://www.example.com/?attachment_id=1
}}}


Would look much neater if these matched the permalinks of regular posts (depending on what it is configured to) eg:


{{{
http://www.example.com/attachement/1/
}}}"	dlhau@…
Future Releases	5130	Linking to multiple posts on your site breaks pingback due to comment flooding		Pings/Trackbacks	2.3	normal	normal	Future Release	defect (bug)	new		2007-10-01T17:36:13Z	2010-12-26T03:34:02Z	"http://scott.sherrillmix.com/blog/programmer/web/wp_pingpreserver/

is this useful in WP 2.3?"	Denis-de-Bernardy
Future Releases	12154	Updating a post modifies pingback timestamp		Pings/Trackbacks		normal	normal	Future Release	defect (bug)	new		2010-02-06T21:17:46Z	2010-06-14T00:29:42Z	"Steps to reproduce:[[BR]]
Create blog post 1. Publish. [[BR]]
Create blog post 2. From within the post body, link to blog post 1. Publish. A pingback comment is created for post 1, with the timestamp as for blog post 2.[[BR]]
Edit blog post 2. Do not change publication timestamp. Save changes.

Expected behaviour: Pingback is not affected.[[BR]]
Actual behaviour: Pingback timestamp is changed - instead of the publication time of blog post 2, it is now set to the time when I edited blog post 2."	htoomik
Future Releases	12582	user_registered action suggestion	westi	Plugins	2.9.2	normal	normal	Future Release	enhancement	new		2010-03-11T11:10:48Z	2010-06-23T17:26:12Z	"I am developing theme that should include user login / registration (so we dont have to see wp-login.php ever again).

Now for login it was easy - with the help wp_login_url user is redirected back to whatever page we need after login.

To achieve same thing for registration i added new action in wp-login.php
{{{
$errors = register_new_user($user_login, $user_email);
do_action('user_registered', array($user_login, $user_email, $errors));
}}}
using this action now i can make wp-login.php redirect user to main page and display errors there.

Maybe this could be included in wordpress? Or maybe wp_login_url type function that can redirect user wherever needed? I would personally go with action as it gives much more freedom."	roxaz
Future Releases	14769	"API for ""Settings"" action link on plugins.php"		Plugins	3.0	normal	normal	Future Release	feature request	new		2010-09-02T22:10:35Z	2010-12-07T23:12:33Z	"Plugins should be able to register a ""Settings"" actions link that will then take them to their plugin settings page.

We should try to hook into add_options_page() as well, just by taking the first one that the plugin registers. Probably not really doable to ascertain which plugin calls that function however, without running a backtrace. Maybe try matching the slug with the plugin basename.

Someone is encouraged to run with this before I get to it."	nacin
Future Releases	15514	Category/Tag Converter should include Post Format conversions		Plugins		normal	normal	WordPress.org	feature request	new		2010-11-20T03:13:53Z	2013-01-17T17:10:01Z	"The category/tag converter should include the ability to convert categories or tags to post formats.

The converter in general needs a pretty serious UI or code cleanup, so if anyone wants to own this, that would be awesome, and I will assist."	nacin
Future Releases	11418	Allow adding post thumb via url		Post Thumbnails	2.9	normal	normal	Future Release	feature request	new		2009-12-13T11:05:05Z	2010-01-05T20:57:07Z	currently it is only possible to add post thumbs from blog's gallery	pascal.herbert
Future Releases	15218	Publish box (inner-sidebar) hidden in custom posts without show_ui		Post Types	3.0.1	normal	normal	Future Release	defect (bug)	new		2010-10-26T08:18:19Z	2010-12-08T20:17:16Z	"I'm pretty sure this is a bug as I can't figure out a reason for the following:


----
Create a new custom post type with '''show_ui => true''' ''(which is supposed to hide the menus for it if false)''. Create a post, go to the post edit screen. Now edit the plugin code and '''switch true to false''' for '''show_ui'''. Hit refresh and the inner-sidebar is gone.
----


Is this expected behavior and, if it is?!?!... how should it be handled? Some people need to manage the custom posts by themselves and not have then show up in the menu, trash can,... but they need the editor, scheduling and such.

Thanks a lot."	5ubliminal
Future Releases	13509	Searching doesn't return Private results to logged in users with read_private_ permissions	ryan	Post Types	2.9.1	normal	normal	Future Release	defect (bug)	new		2010-05-24T00:31:11Z	2010-11-13T08:01:18Z	"When you do a search with these requirements...[[BR]]
- You are a registered user.[[BR]]
- You are logged in.[[BR]]
- You have '''''read_private_posts''''' permissions.

... you expect seeing in the results those Private posts that contains your query's terms.

But you end up with showing only the ones that belongs to you. I think the bug is in these lines:


{{{
if ( is_user_logged_in() ) {
	$where .= current_user_can( ""read_private_{$post_type_cap}s"" ) ? "" OR $wpdb->posts.post_status = 'private'"" : "" OR $wpdb->posts.post_author = $user_ID AND $wpdb->posts.post_status = 'private'"";
}
}}}

As '''''$post_type_cap''''' is set to ""any"" when you do a search, the conditional expression always fails as it's asking for this:

{{{
current_user_can( ""read_private_anys"" )
}}}

... and ends up always in the second part of the conditional expression. That is:

{{{
"" OR $wpdb->posts.post_author = $user_ID AND $wpdb->posts.post_status = 'private'""
}}}

Thanks."	inbytesinc
Future Releases	14761	unregister_post_type()		Post Types	2.9	lowest	normal	Future Release	enhancement	new	dev-feedback	2010-09-02T12:00:17Z	2013-05-16T20:42:09Z	"Two use cases:

 1. Remove a core post type. Means that the admin menus should respond in kind, though certain aspects of core like query/rewrite might not like this. Not the main use case regardless.

 2. Removing a post type of another plugin, or potentially more likely, a parent theme.

Example barebones function: http://wordpress.pastebin.com/VexHkgig

Related, unregister_taxonomy() #11058 and unregister_taxonomy_for_object_type(): #14482"	nacin
Future Releases	7605	Press This: Edit URL	noel	Press This		normal	normal	Future Release	enhancement	new		2008-08-26T20:35:04Z	2010-08-19T22:40:44Z	It'd be nice if the Press This bookmarklet had the same edit URL capabilities as the Wordpress administration.	awayken
Future Releases	7604	Press This: Post auto-saving	noel	Press This		normal	normal	Future Release	enhancement	new		2008-08-26T20:33:42Z	2010-08-19T22:41:12Z	It'd be nice if the Press This bookmarklet had the same autosave capabilities as the Wordpress administration.	awayken
Future Releases	17027	Allow WP_Query to return just the count		Query		normal	normal	Future Release	enhancement	new		2011-04-02T18:32:56Z	2011-04-02T18:32:56Z	"Currently, you can't ask just for the total number of posts for a certain query.

You have to execute that query and then retrieve the total using SQL_CALC_FOUND_ROWS.

Maybe a {{{'fields' => 'count'}}} option would do it.

Example where this is needed in Core: #17019"	scribu
Future Releases	9470	Allow get_pages to get child pages of multiple pages		Query	2.8	normal	normal	Future Release	enhancement	new		2009-04-06T10:51:02Z	2012-10-30T20:14:27Z	"I'm doig a lot of WordPress CMS work, and am finding it increasingly annoying that i can only get the children of one page through get_pages. 

It would be great if child_of could also, just like include and exclude, be a comma separated array of pages for which you want to fetch the children."	joostdevalk
Future Releases	12719	Custom taxonomy with query_var set, gets taxonomy query_var appended anyway	dd32*	Query	3.0	normal	normal	Future Release	enhancement	accepted		2010-03-26T12:42:16Z	2010-10-28T08:24:18Z	"In my browser address field, appending my WP url with ""?customtax=termslug"", the real WP query string gets changed to ""?customtax=termslug&taxonomy=customtax&term=termslug"".

This causes cases where I append two custom taxes in the URL to not work. E.g. ""?customtax1=termslug1&customtax2=termslug2"" would result in something like ""?customtax1=termslug1&taxonomy=customtax1&term=termslug1&customtax2=termslug2"" and not work.

If i two sets of custom taxonomies and slugs manually through a query_posts it works, and is not modified by WP."	Silkjaer
Future Releases	9978	Sticky Posts are not ordered correctly after selection	ryan	Query	2.8	normal	normal	Future Release	enhancement	new		2009-05-29T23:14:06Z	2009-06-11T13:28:46Z	"In WP_Query, sticky posts are added/moved to the top of the posts array after everything else is selected and ordered according to the query parameters.

Sticky posts are loaded as a list of post_IDs from the database, according to the order they were marked as sticky.

Sticky posts that were not originally part of the returned posts are queried and added into the collection of sticky posts separately.

None of the handling of sticky posts, or the handling of the entire post array after stickies are added, is date ordered by date/title/whatever was requested.

Stickies need to be loaded/extracted into a separate array, ordered (independently) according to the original query, then added to the top of the post array."	beaulebens
Future Releases	14477	get_pages with child_of only works with uninterrupted hierarchies		Query	3.0	normal	normal	Future Release	enhancement	new		2010-07-30T19:00:50Z	2010-11-23T01:36:16Z	"I have a page X with several children and grandchildren. Some of the grandchildren have a certain meta key and value. I now want to fetch all pages under page X that have this meta key. After reading the documentation of ''get_pages'', I expected this to work with a single call of ''get_pages''.

But if I use get_pages like this:
{{{
get_pages('child_of=X&meta_key=A&meta_value=B');
}}}
it returns no pages at all (hierarchical=0 has no effect). It seems that's because ''child_of'' triggers a call of ''get_page_children'' which only returns uninterrupted hierarchies. Since the query returns only some grandchildren and no direct descendants, the function fails. IMHO, that's a bug.
"	vividvisions
Future Releases	11398	new sort method for query_posts (order by last comment date)	ryan	Query	2.9	normal	normal	Future Release	enhancement	new		2009-12-11T15:44:42Z	2010-06-14T00:30:40Z	"I think we need sorting by latest post comment ability for query_posts. ""Recent comments"" plugins does this but we need this sorting in the core. 

BBPress is planned as a WP plugin according latest chat logs posted by Matt. We gonna have to need this anyway."	erden.ozkan
Future Releases	12769	Disappearing posts/pages (in quickedit mode)		Quick/Bulk Edit	2.9.2	low	minor	Future Release	defect (bug)	new		2010-03-30T08:53:39Z	2011-03-13T22:53:58Z	"Steps to reproduce:
1. Quickedit a post.
2. Click save and instanly click quick-edit on another post.
When the ajax-request completes the first quick-edited post will disappear from the posts table. This is only a display bug."	catahac
Future Releases	11302	Bulk editing posts should pre-fill fields with the same value		Quick/Bulk Edit	2.9	normal	normal	Future Release	enhancement	new		2009-12-01T20:48:41Z	2012-07-13T04:08:11Z	"All I need is quickly move some posts from one category to another.

How to simulate this problem:

Create 2 posts in Uncategorized category.
Check both of them - Bulk actions - Edit.
There is no category selected even if both posts are in Uncategorized. When I check Category1 and click Update, both posts are now in Uncategorized and also in Category1. But no chance remove them from Uncategorized with Bulk actions."	pavelevap
Future Releases	15637	Inline Edit Has No Hooks		Quick/Bulk Edit	3.1	normal	normal	Future Release	enhancement	new		2010-12-02T01:00:50Z	2012-05-11T11:23:26Z	"Currently, I am attempting to make it possible for an author to ""feature"" a post straight from the Quick Edit screen. I am looking in wp-includes/class-wp-posts-list-table.php and there are no hooks or actions for the Quick Edit screen so that I can add a checkbox or another input field in there.

I just want to add a checkbox to ""feature"" the post and then save it to the custom fields of that post, not too hard. But I need the do_action's to be there! Thanks!"	sean212
Future Releases	14326	Renaming tags/categories causes unpredictable results		Quick/Bulk Edit	3.0	lowest	trivial	Future Release	enhancement	new		2010-07-16T02:39:14Z	2010-11-22T17:35:14Z	When renaming a tag/category through quick edit, if the new title contains the character ' — ' (&8220;) the script produces unexplainable results.	kdizas
Future Releases	11472	Should QuickEdit remove posts from lists as needed?		Quick/Bulk Edit	2.9	normal	normal	Future Release	enhancement	new		2009-12-17T10:29:38Z	2013-01-21T23:51:08Z	"Create a draft post. Visit Posts / Edit, and quickedit the draft. Set its status to Published and save. It remains around, with the published status, instead of being removed from the list.

Reporting this just in case, as it might be a UI feature rather than a bug.
"	Denis-de-Bernardy
Future Releases	12208	Add Quick Edit To Media Library		Quick/Bulk Edit		normal	normal	Future Release	feature request	new		2010-02-12T01:45:12Z	2013-04-12T16:28:27Z	I am requesting that a quick edit link be added to the media in the media library like what is on the posts page. I would like to quickly be able to edit titles, alts, and captions at least.	queenofdiy
Future Releases	13382	_wp_post_revision_fields filter is not very useful		Revisions	3.0	normal	normal	Future Release	enhancement	new		2010-05-13T20:57:51Z	2013-01-21T14:48:16Z	"The _wp_post_revision_fields filter allows plugins to modify which post fields get revisioned (the default is title, content, excerpt).

It's pretty useless, though, since it's only run once and can't be changed by post_type.  A custom post type, for example, might only want to enable revisions on the content.

The _wp_post_revision_fields() is also a variation on the getter/setter pattern (static variable) we use in a few places to avoid globals.  It makes the function kind of crazy.

Proposal:  Split into two functions

{{{
@var int|object|array $post post_id or post object or post array
@return array Fields to revision: array( field => i18n'd label )
function wp_get_post_revision_fields( $post ) {
    // filter with _wp_post_revision_fields: pass post_id, post_type, ...?
    // don't cache results
}

@internal
@var array $past post array
@return array Filled $post array with revision info
function _wp_post_revision_fields( $post ) {
    $revisionable = wp_get_post_revision_fields( $post )
    // ...
}
}}}

I'd like to see this in 3.0 if we can, but marking as 3.1 for now."	mdawaffe
Future Releases	16725	Inconsistent leading slash in WP_Rewrite		Rewrite Rules		normal	normal	Future Release	enhancement	new		2011-03-02T17:25:58Z	2011-03-02T17:25:58Z	"#16626 revealed an inconsistency in WP_Rewrite, where {{{$wp_rewrite->front}}} has a leading slash, but the final rules array doesn't.

This is caused by the fact that {{{$wp_rewrite->permalink_structure}}} itself has a leading slash.

Also note that {{{$wp_rewrite->search_structure}}} stands out as the only structure that doesn't have a leading slash.

This should be made consistent somehow."	scribu
Future Releases	12107	Author role overrides edit image title set by editor		Role/Capability	2.8.6	normal	normal	Future Release	defect (bug)	new		2010-02-01T01:56:49Z	2010-11-13T07:42:50Z	"If assigned as 'Author' as Role in Wordpress User Setting, Author cannot add or edit the 'Edit Image Title' field for any images (even though they upload themselves)

Furthermore, if there is an existing text in 'Edit Image Title' field, and if Author 'Save Draft' or 'Update Post' (without doing any editing at all), the Image Title will be removed.

In other words, only the Roles of 'Admin' and 'Editor' are able to add Image Titles to images. The Role of 'Author' cannot add image titles and not only that, by accessing and saving a post, any existing Image Titles added by Admin or Editor becomes removed.

I tested on Wordpress version 2.8.6 and 2.9.1

I have previously posted a thread on the support forum here http://wordpress.org/support/topic/356199?replies=1#post-1365412"	noyu
Future Releases	12061	Treatment of shortcodes by wpautop is incomplete		Shortcodes		normal	normal	Future Release	defect (bug)	new		2010-01-28T02:27:18Z	2013-01-19T08:36:17Z	"There are a number of issues that arise when shortcodes are embedded in a block of content that is filtered by wpautop.  After studying the issue, I have come to the conclusion that the underlying issue is that a shortcode can result in a block-level HTML element or an inline snippet of HTML.  Neither wpautop nor shortcode_unautop have the information necessary to know what the intended to be block-level or text-level, which results in <br /> tags to appear in places where they were not intended and causes invalid markup when paragraphs are not closed properly.

1) shorcodes when registered need to state the display type of the html that they return (inline or block).  In addition, the javascript version of filters need to be provided with the same data.

2) An alternate mechanism for handling shortcodes prior to wpautop needs to be implemented.   To maintain a separation between wpautop and shortcodes, temporarily replacing block-level shortcodes with unique tokens, running wpautop, running wpautop on the content of the shortcode (since this is a separate filter, plugins can disable it on a per shortcode basis), and then replacing the token with shortcodes post-wpautop.

As WP and plugin authors use shortcodes more and more, I think this is an issue that should not be left to the wayside.  Shortcodes especially tied to tinymce buttons make working with WordPress easier for the average content producer.  

"	gcorne
Future Releases	18776	balanceTags should ignore shortcodes & their content		Shortcodes	3.2.1	normal	normal	Future Release	defect (bug)	new		2011-09-26T11:26:10Z	2012-04-27T19:44:20Z	"Take following input:

{{{
something [myshortcode]<b>[/myshortcode]
}}}

after `balanceTags()` it becomes:

{{{
something [myshortcode]<b>[/myshortcode]</b>
}}}

Well, this is not what the shortcode creator probably wanted.

'''Proposed fixes:'''

If you are feeling lazy: Convert `[.*]` to `<$1>` and since balanceTags handles XML it should work, afterwards convert appropriate `<>` back to `[]`. Though this does not give a shortcode creator chance to disallow balancing tags inside it's content which is bad.

Better fix is to allow shortcode creators to decide wether their contents should be balanced:

1. `balanceTags()` should ignore all shortcodes and their contents.
2. Parse all shortcodes in content and on each shortcode call apply filter on so that shortcode creator can hook (if sees it appropriate) on to that. Shortcode creator then can call `balanceTags()` in his filter of that shortcode in order to run `balanceTags()` ''contents of shortcode'' separately if wanted."	ciantic
Future Releases	13606	Comma's in taxonomy term names make them unpickable		Taxonomy		normal	major	Future Release	defect (bug)	new		2010-05-28T21:10:02Z	2010-11-13T03:19:01Z	"In the taxonomy term adder/editor, you are allowed to put comma's in their names, but the JS picker thinks they are two separate terms separated by a comma.

Two possible obvious solutions:
1.) Disallow terms from having commas in the names
2.) Fix the JS"	johnjamesjacoby
Future Releases	11156	Duplicate tag created if tag name contains ampersand	filosofo	Taxonomy	2.9	normal	normal	Future Release	defect (bug)	new		2009-11-16T21:51:37Z	2010-11-13T07:25:30Z	"This is undoubtedly an edge case, but here's what happened:

1. I created a tag with a long name that contained an ampersand. Gave it a shorter slug than the one WP generated.

2. Tagged some posts.

3. While the server was running slow, the autocomplete never came up, and I tagged another post by cutting and pasting the tag name from another screen.

That resulted in a new tag being created with a longer WP-generated slug, instead of the post getting tagged with my older existing tag.

This happened a few times (the server in question is REALLY slow), and I finally realized that the only tags that were incorrectly duplicated were the ones with ampersands."	sillybean
Future Releases	14093	Malformed category hidden from edit-tags, but shows in meta box		Taxonomy		low	normal	Future Release	defect (bug)	new		2010-06-25T19:11:49Z	2011-01-13T08:07:15Z	"Came from a report in IRC by xomp.

In the following example, category 1's parent is category 2, and vice versa.
{{{
mysql> select term_taxonomy_id, term_id, taxonomy, parent from wp_term_taxonomy;
+------------------+---------+---------------+--------+
| term_taxonomy_id | term_id | taxonomy      | parent |
+------------------+---------+---------------+--------+
|                1 |       1 | category      |      2 |
|                2 |       2 | category      |      1 |
|                3 |       3 | category      |      0 |
|                4 |       4 | category      |      1 |
+------------------+---------+---------------+--------+
4 rows in set (0.00 sec)

mysql> select term_id, name from wp_terms;
+---------+-----------------+
| term_id | name            |
+---------+-----------------+
|       1 | Category 1      |
|       2 | Category 2      |
|       3 | Category 3      |
|       4 | Category 4      |
+---------+-----------------+
4 rows in set (0.00 sec)
}}}
On edit-tags, you'll see only Category 3.

In the hierarchical meta box, you'll see:
{{{
Category 3
Category 1
 - Category 2
 - Category 4
}}}
If we decide to show corrupted data, we should be consistent. At the very least, edit-tags should reveal more than the meta box, not the other way around."	nacin
Future Releases	5358	Queried object on multiple tag query holds only first tag	ryan	Taxonomy	2.3.1	normal	normal	Future Release	defect (bug)	new		2007-11-15T05:17:21Z	2013-01-28T14:01:36Z	"On tag page results when two or more tags are queried ('''/tags/foo,bar''' -or- '''/tags/foo+bar'''), only the first tag is in the queried object. So a simple:

{{{ print_r($wp_query->get_queried_object());  }}}

outputs a single associative array of the first tag referenced in the query. One would expect to find an array of all tags in the queried object."	Kafkaesqui
Future Releases	14399	get_term_children doesn't call clean_term_cache() if necessary		Taxonomy	3.0	normal	normal	Future Release	defect (bug)	reopened		2010-07-23T13:32:11Z	2011-01-15T02:01:34Z	"1. Create a taxonomy on something 'non standard'[[BR]]

2. Create a (parent) term.[[BR]]

3. Create a child term. [[BR]]

4. Retrieve child terms of the parent term using, amongst others, get_term_children().

Roughly:

{{{
register_taxonomy( 'where-you-live', 'user', array('hierarchical' => true,  'show_ui' => true, 'query_var' => true, 'label' => __('Where they live')) );

$country = 'USA';
$state   = 'New York';

$tax_country = wp_insert_term($country,  'where-you-live');
$country_term_id = $tax_country['term_id'];
wp_insert_term($state, 'where-you-live', array('parent'=>$country_term_id));

$state_terms = get_child_terms($country_term_id, 'where-you-live');
error_log(print_r($state_terms,1));
}}}

I am expecting an array containing the 'New York' child term, but I get nothing.[[BR]]
Have also tried get_terms() with child_of or parent args, which also fail (presumably for the same reason?)."	miradev
Future Releases	13949	Add a sprintf style argument to wp_list_categories() for title tag.		Taxonomy		normal	normal	Future Release	enhancement	new		2010-06-17T18:01:20Z	2010-10-28T02:10:59Z	"By default, wp_list_categories() will use the value of $term->description for the title tag of every link that it generates. If the argument ""use_desc_for_title"" is set to false, it will produce a string like: ""View all posts filed under $term->name"". With the inclusion of custom post_types into core, it would be wonderful to have more control over this title. The best solution that I can think of is to add a sprintf style argument which will allow themes and plugins to provide a custom format. Something like:

'title_format' => 'View all tacos posted under %s.'

"	mfields
Future Releases	22023	Remove UNIQUE for slug in wp_terms		Taxonomy	2.3	normal	normal	Future Release	enhancement	new		2012-09-27T20:23:10Z	2013-05-14T13:38:13Z	"To set us up for future changes to the taxonomy API, we should remove the UNIQUE key for 'slug' for wp_terms. Said future changes include:

 * Splitting shared terms on update (#5809)
 * Stop creating shared terms (#21950)
 * Forcibly split remaining shared terms
 * Merge wp_terms and wp_term_taxonomy (I can dream, right?)

The term_exists() check should prevent duplicate terms from ever being inserted (before, of course, we fix #5809 and #21950). But, this needs unit tests, particularly because there is a case where term_exists() breaks. See #17689, which blocks this ticket."	nacin
Future Releases	11576	The future of the 'uncategorized' category		Taxonomy	2.9	normal	normal	Future Release	enhancement	assigned		2009-12-23T14:32:42Z	2011-04-15T08:44:01Z	"Is there any plan for removing the 'Uncategorized' category, or at least removing its requirement?  Some users want the ability to only show the_category() when the post is part of a real category. Also, with the introduction of custom taxonomies in 2.9, not all hierarchical taxonomies will have a default term, so this flexibility needs to be introduced anyway.  

I'm curious why the default category was introduced in the first place?  Was it solely for permalink handling?

If attachment:ticket:10122:hierarchical_metaboxes-2.patch is accepted (specifically handling hierarchical taxonomies as int) the following just needs to be added above the checkbox list to allow deselecting of all terms from the taxonomy:

{{{
<input type=""hidden"" name=""tax_input[<?php echo $taxonomy?>]"" value="""" /> 
}}}
"	prettyboymp
Future Releases	7740	Merge Tags		Taxonomy	2.7	normal	normal	Future Release	feature request	new	dev-feedback	2008-09-14T16:56:07Z	2011-10-18T23:46:10Z	"As mentioned in [http://wordpress.org/support/topic/163558 a support thread], tags can get cluttered over time with many different tags meaning basically the same thing. To clean up tagging the ability to merge tags would be a life saver.

The functionality I had in mind was being able to select two or more tags in edit-tags.php and select 'Merge' from the 'Actions' dropdown. When you click 'Apply' a lightbox would open with the following:

  '''What should become the primary tag?'''[[BR]]
  [Textfield][[BR]]
  ''The name is how the tag appears on your site.''
  
  '''What should become the primary tag slug?'''[[BR]]
  [Textfield][[BR]]
  ''The “slug” is the URL-friendly version of the name. It is usually all lowercase and contains only letters, numbers, and hyphens.''
  
  '''Which slugs should continue to point to the new primary tag?'''[[BR]]
  [Textarea automatically filled with the old slugs][[BR]]
  ''One slug per line.''
  
  '''Save''' | '''Cancel'''

The last textarea allows old slugs to still point to the new primary tag - meaning any old URL's will still work.

=== -~- Example -~-~-~-~-~-~-~-~ ===

I've got the following tags which all mean the same thing:

  TV, the box, telly

I select them all in edit-tags.php, select 'Merge' and 'Apply'. In the popup box I choose 'television' as the primary tag, 'television' as the slug, and list the old tags in the textarea.

I now have a tag called 'television' which has ""television, TV, the box, telly"" all pointing to it, so my old URL's still work. All of my posts which use the old tags have now magically swapped to using 'television'."	hempsworth
Future Releases	16929	pass the $type_of_url context param on user_trailingslashit() for CPT's		Template	3.1	normal	normal	Future Release	defect (bug)	new		2011-03-22T08:42:09Z	2011-03-22T09:55:02Z	"Currently get_post_permalink() does not pass the context flag to user_trailingslashit(), this means that for custom post types, it's not possible to target them through the 'user_trailingslashit' filter.

It might be worth checking to see if taxonomies and any other uses of user_trailingslashit() pass the context as well."	dd32
Future Releases	4575	Add functions to return the last-modified timestamp of a category/tag		Template	2.2.1	normal	normal	Future Release	enhancement	new		2007-07-02T12:36:26Z	2009-08-07T18:46:45Z	"Hi, 

All categories Last-Modified dates are the same, and thats a one big rss file i guess.
Is there a chance to send individual Last-Modified dates to these feed ?

Thanks"	delusions
Future Releases	15516	Candidates for new template functions based on code in Twenty Ten		Template	3.1	normal	normal	Future Release	enhancement	new		2010-11-20T06:30:13Z	2010-11-20T07:11:25Z	There are several pieces of code in Twenty Ten which are candidates for abstraction into template functions. I'll make a list shortly and put it up here to get feedback.	johnbillion
Future Releases	14113	Function that could improve the current edit_post_link()		Template	3.0	normal	normal	Future Release	enhancement	new		2010-06-27T15:20:42Z	2010-10-28T05:37:38Z	"Basicly this function is the same than [http://core.trac.wordpress.org/browser/trunk/wp-includes/link-template.php#L820 edit_post_link()] but some little differences which can make it more useful for developers. So far it has two advantages:

'''1)''' The edit link can be easily returned.

'''2)''' It's possible to choose a class for link tags.

{{{
// Returned
function wp_get_edit_link($args = '') {
	$defaults = array(
		'link'   => null,
		'before' => '',
		'after'  => '',
		'id'     => 0,
		'class'  => 'post-edit-link'
	);

	$r = wp_parse_args($args, $predet);
	extract($r);

	if ( !$post = &get_post($id) )
		return;

	if ( !$url = get_edit_post_link($post->ID) )
		return;

	if (null === $link)
		$link = __('Edit This');

	$post_type_obj = get_post_type_object($post->post_type);
	$link = '<a class=""'. $class .'"" href=""' . $url . '"" title=""' . esc_attr( $post_type_obj->labels->edit_item ) . '"">' . $link . '</a>';
	return $before . apply_filters('get_edit_link' , $link , $post->ID) . $after;
}

// Echoed
function wp_edit_link($args = '') {
	echo wp_get_edit_link($args);
}
}}}

'''Example using the function:'''

Returning:

{{{
<?php 
$var = get_wp_edit_link('before=<span class=""my-edit-class"">&after=</span>&class=my-link-class&link=Edit me!');
echo $var;
?>
}}}

Echoing:

{{{
<?php wp_edit_link('before=<span class=""my-edit-class"">&after=</span>&class=my-link-class&link=Edit me!'); ?>
}}}

Results on:

{{{
<span class=""my-edit-class""><a class=""my-link-class"" href=""http://url.to/post.html"">Edit me!</a></span>
}}}"	metacortex
Future Releases	9666	Pass object id in the various formatting filters		Template	2.8	normal	normal	Future Release	enhancement	new		2009-04-28T10:31:44Z	2012-10-30T20:50:38Z	"This is a consolidated ticket, in reference to #9319 and #5746.

Both were requests to pass either of $post or $post->ID as an argument to the_title (both have patches for that).

The same idea could be applied to multitudes of other formatting hooks. They're not always called in the loop, so determining the ID of the object (post, link, category, tag, etc.) isn't always easy in the event that it is useful.

Suggested enhancement:

each filter such as the_title, the_content, etc., but also the_permalink, the_category_link, etc., possibly also the_category, etc., as well... basically any hook that is formatting related and that affects an individual object rather than a collection, should have the object's ID as an argument for easy reference."	Denis-de-Bernardy
Future Releases	16268	Requirement for has_header_image() function?		Template		normal	normal	Future Release	enhancement	new		2011-01-17T12:05:24Z	2011-01-18T11:10:19Z	"I know is pretty easy to do, but would it be a good idea to provide a has_header_image() function for use in themes? Something along the lines of:

{{{
function has_header_image() {
   $header_image = get_header_image();
   return !empty( $header_image );
}
}}}

As the header_image() function just outputs the URL it would be handy to have a conditional function you could use to check when there was a header image to output.

I'm currently working on a plugin that gives you more granular control over using different header images on different pages using the 'theme_mod_header_image' filter. There may be instances when you do not want to show a header at all on some pages. In the current TwentyTen theme for example, no checking is done before the header_image() function is called so in this scenario the header image just appears as a broken image - ideally it should not output the image at all.

Either that or should there be a function which outputs the whole image tag so that if the header_image() function returns false/empty it does not output the tag at all?

What are people's thoughts on this?"	husobj
Future Releases	9719	Please : a filter for $category object in get_the_category_list()		Template	2.8	normal	minor	Future Release	feature request	reopened		2009-05-04T09:09:10Z	2009-06-13T02:57:15Z	"To offer for one post more flexibility in how to display the names of categories in the_category() or in get_the_category_list() -file category-template line 166 - , is it possible to add a filter as the filter existing in wp_list_categories() .  Useful to replace cat name by instance by image ''(iphone compatible theme)'' or to add translation in bilingual or multilingual theme ''(by instance with xili-language plugin)'' without re-creating specific function.

As in classes.php (line 1328), I suggest this modif with a filter named post_list_cats for the start of two loops present in get_the_category_list() (line 187 et 209)


{{{
foreach ( $categories as $category ) {
$cat_name = attr( $category->name);
$cat_name = apply_filters( 'post_list_cats', $cat_name, $category );
}}}


and inside the two loops, $category->cat_name replaced by $cat_name


with this filter it will be more coherent to treate cat list in one post or in sidebar for all posts

Many thanks

"	michelwppi
Future Releases	9818	add a wp_notification functionality to output notices and errors on the front end		Template	2.8	normal	normal	Future Release	feature request	assigned		2009-05-14T09:28:25Z	2010-07-06T22:43:20Z	"On occasion, a plugin needs to return some kind of feedback. It would be nice if a standard hook existed for this.

It could go something like this:

add_filter(wp_notification, foobar)

foobar() appends to an array of notification messages that get displayed to the user on the front end.

then, on page load:

 - in wp_head if notifications is not empty, we add a style, wp_notification, that makes elements of this class invisible, and we load jQuery

 - if do_action(wp_notification) is explicitly called on the page, we display the messages in there, without the class, and disable the notification on the wp_footer hook

 - an action gets fired on wp_footer if do_action(wp_notification) is not called, and we use ajax to place the needed messages in a absolutely positioned div element, with a close button.

we could also add some kind of do_action(wp_commentform_notification), nearby the comments form, to output comment-related errors in their ""correct"" location as well."	Denis-de-Bernardy
Future Releases	17739	Comment prompt text is misleading		Text Changes	3.2	lowest	trivial	Future Release	enhancement	new		2011-06-10T01:24:54Z	2012-11-19T16:46:04Z	"The comment form says, ""Your email address will not be published.""

It can be deceptive b/c people assume it's used for some sort of verification, not that it goes to the site owner/comment moderator, who could very well decide to publish it if he/she happens to be an unethical jerk. People complain about this in support forums and elsewhere every now and then. Quite trivial issue compared to most tickets, but would be nice to take care of it. 

Suggestions for better text welcome."	jane
Future Releases	9774	Warning: Division by zero in /wp-admin/custom-header.php on line 361 (and many more)		Themes	2.8	lowest	minor	Future Release	defect (bug)	new		2009-05-09T18:54:43Z	2011-03-20T17:59:00Z	we might want to check if the needed defines are around and > 0 before allowing the custom-header.php to work.	Denis-de-Bernardy
Future Releases	14824	WordPress is not updating Theme option after making a theme a child theme by adding the line 'Template' to the child`s css without refreshing Theem activation		Themes	3.1	normal	normal	Future Release	defect (bug)	new		2010-09-09T23:27:35Z	2011-01-13T08:51:36Z	"Situation:

If you have 2 Themes on a 2 sites MultiSite install (each site is using one theme) and want to make one of them a child Theme of the other, you will go to one of them and add the line 'Template: NAME OF THE PARENT THEME' and save it.

After doing so the Child Theme will not inherit any Template Files from the parent until you deactivate/activate the Child Theme again.

Although it says in the ""Themes/Appereance"" section of the Child Themes backend 'CHILD THEME NAME uses templates from PARENT THEME NAME. Changes made to the templates will affect both themes.' even before deactivating/activating the Child Theme.

Looks like the template page might be checking the style.css and not update the option."	drale2k
Future Releases	19124	Add prompt on themes.php at end of available themes list		Themes	3.3	normal	normal	Future Release	enhancement	new		2011-11-03T02:43:49Z	2012-11-01T06:45:01Z	For new users, getting a new theme is still overwhelming. Long-term we should overhaul the way the theme management area works, but short term we could add a blurb after the last available theme is listed to prompt user to search/browse for more themes to install.	jane
Future Releases	14932	Featured Images: No way to custom crop when used as headers		Themes	3.0.1	normal	normal	Future Release	enhancement	new		2010-09-22T09:59:34Z	2010-09-22T14:27:21Z	"Custom Headers have Custom Cropping

When a theme uses featured images for per-post headers you don't get that goodness.

Makes feature images more ghetto for custom headers than they should be."	westi
Future Releases	14341	Adjacent image disappears when a caption is added		TinyMCE		normal	major	Future Release	defect (bug)	new		2010-07-17T23:53:02Z	2011-05-20T21:44:17Z	"If you place two images side by side inside a strong tag and then try to add a caption to one of the images, the other image disappears. 

Tested in r15436. 

To reproduce: [[BR]] 
1) Open a new or existing post for editing [[BR]] 
2) Place the sample code from below into the html editor [[BR]] 
3) Switch to the visual editor and try to add a caption [[BR]] 
---> You'll see the other image disappear

Here is a screencast example: http://screencast.com/t/OTNmNjQzN

Here is some sample code: 

{{{
<strong><a href=""http://s.wordpress.org/about/images/logo-grey/grey-m.png""><img class=""alignleft size-full"" title=""grey logo"" src=""http://s.wordpress.org/about/images/logo-grey/grey-m.png"" alt="""" width=""100"" height=""100"" /></a><a href=""http://s.wordpress.org/about/images/logo-blue/blue-m.png""><img class=""alignleft size-full"" title=""blue logo"" src=""http://s.wordpress.org/about/images/logo-blue/blue-m.png"" alt="""" width=""100"" height=""100"" /></a></strong>
}}}"	designsimply
Future Releases	11674	Caption Short Codes Don't Work		TinyMCE		normal	critical	Future Release	defect (bug)	reopened		2009-12-30T19:07:55Z	2010-08-02T05:44:42Z	"I'm testing 2.9.1-RC1 now.  If I create a post, add a gallery plus a captioned image beneath it, this is what shows up in the HTML editing view:

{{{
<div class=""mceTemp"">

[gallery]

<dl id=""attachment_80"" class=""wp-caption alignnone"" style=""width: 160px;""><dt class=""wp-caption-dt""><a rel=""attachment wp-att-80"" href=""mytestsite/2009/12/test-post-3/wp-exif-bug/""><img class=""size-thumbnail wp-image-80"" title=""This is a supercool test"" src=""mytestsite/wp-content/uploads/2009/12/wp-exif-bug-150x136.jpg"" alt="""" width=""150"" height=""136"" /></a></dt><dd class=""wp-caption-dd"">Caption goes here</dd></dl></div>
}}}"	miqrogroove
Future Releases	6331	TinyMCE should have a code button		TinyMCE	2.5	normal	normal	Future Release	enhancement	assigned		2008-03-21T10:52:42Z	2009-10-25T11:23:00Z	"The html editor has a code button on the quicktags bar but TinyMCE doesn't.

This is the only missing feature from TinyMCE that makes me switch to the HTML view when writing my weekly digest posts."	westi
Future Releases	10596	Error when uploading zip package with parent and child themes		Upgrade/Install	2.8.3	normal	normal	Future Release	defect (bug)	assigned		2009-08-12T11:12:29Z	2012-01-06T12:30:14Z	"There's an error when you try to install a package containing parent and couple of child themes using zip package upload from the admin dashboard.

For example i got a 1 big directory called test_template which contains 1 folder test_parent and 3 folders test_child1, test_child2, test_child3. If i upload test_template directory using ftp everything's ok, but when i try to use theme uploader and zip package test_template.zip i get an error caused by not finding a style.css file inside of the test_template directory ... but when i add a style.css file to that directory installation goes fine but templates aren't working till i use ftp and delete that file from that directory. It's troublesome if someone is giving his templates to other users."	newkind
Future Releases	12031	Install do not check the magic_quote_sybase status	dd32	Upgrade/Install		normal	normal	Future Release	defect (bug)	reopened		2010-01-26T00:27:25Z	2012-11-01T20:09:16Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/981

Just try to install on a server that it's magic_quote_sybase is on (okay for Oracle, but fatal for mysql) . It failed to update the wp-config.php and didn't set correctly the .htaccess. "	wpmuguru
Future Releases	15440	PCLZIP_ERR_BAD_FORMAT (-10) : Invalid archive structure during plugin update		Upgrade/Install	3.0.1	low	normal	Future Release	defect (bug)	new		2010-11-16T15:53:13Z	2011-04-03T13:15:03Z	"Currently, as part of our JW Player plugin we include several player skins so that users can customize the look of the JW Player.  These skins are packaged as zip archives.

For a while now we've been getting reports from our users having difficulty performing the automated update/install.  These users are receiving a PCLZIP error which claims the plugin archive is invalid.

From looking at the source code I see that WordPress first attempts to use the ZipArchive PHP module to unzip plugin packages.  This always works for users updating our plugin.  If this is not available it then uses a fallback library called PCLZIP.  After some experimentation, it seems that PCLZIP has difficulty unzipping archives that contain archives.

Is this a known issue from your experience?  If so, is there a workaround other than removing the zip skins from our plugin package?"	LongTail Video
Future Releases	13071	Update bubble appears only at the second load	dd32	Upgrade/Install	3.0	normal	normal	Future Release	defect (bug)	new		2010-04-21T15:51:25Z	2011-04-03T10:54:48Z	"Change the version of a plugin and go directly to ''wp-admin/update-core.php'' page.[[BR]]
You will see the plugin update in the list but the bubbles on the menu appears only after a reload.

"	ocean90
Future Releases	12671	Installer page doesn't check if MySQL tables were created successfully		Upgrade/Install	2.9.2	normal	normal	Future Release	enhancement	assigned		2010-03-22T17:47:33Z	2012-07-02T16:54:02Z	"When running the web-based setup script - My Mysql user didn't have create permissions so no tables were created but the message (underneath all the MySQL errors) said setup was successful. 

I think it would be worth doing a check for no MySQL errors before proclaiming the installation a success."	thedotproduct
Future Releases	14393	Maintenance mode overkill. Please refine usage of it		Upgrade/Install		normal	normal	Future Release	enhancement	new		2010-07-22T22:12:14Z	2010-11-23T21:16:35Z	"Though many tickets have been posted about the Maintenance Mode not resolving, I think that the problem is on a different level.

It is unacceptable that even a failed upgrade of an inactive theme can break a complete Site or even Network. Case in point: I just followed the upgrade alert for an inactive theme, hosted on the WordPRess theme repository. 
(Apparently it had an error (Incompatible Archive. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature.) But the point is, this should not have put the entire network in maintenance mode for 10 minutes.

Maybe a check can be done for plugins, themes etc: if they are active, then maintenance mode can be used (though I am definitely not a fan of it anyway)."	bike
Future Releases	9679	Move Plugin/Theme deletion to new WP_Upgrader class	DD32	Upgrade/Install	2.8	normal	normal	Future Release	enhancement	new		2009-04-29T08:51:55Z	2009-05-10T21:16:43Z	Expansion off #7875, The plugin/Theme deletions should be also handled by the Upgrader class.	DD32
Future Releases	15738	Automate Security Releases		Upgrade/Install		normal	trivial	Future Release	feature request	new	dev-feedback	2010-12-08T21:11:49Z	2012-12-03T23:27:46Z	"When security releases are published, several less tech-savvy users might neglect to update in fear of breaking their site.  In reality, security/maintenance releases don't change the core API and shouldn't break anything*.

We should have an option (disabled by default) that allows these X.X.1-style security updates to happen in the background.  This will keep sites updated and secure and (hopefully) prevent the inevitable ""I wanted to wait to install 3.0.2 and someone hacked my site while I was waiting"" support requests.

The option should be disabled by default, but when users are on the update screen they should see an option to ""install security releases automatically.""

Major releases should always require an explicit action from the user to update the site as they can break themes and plug-ins and could potentially update database schema.

* Except in the rare occasion where a developer hacks core."	ericmann
Future Releases	8754	Uploading images whose dimensions are greater than the maximum size allowed fail to generate thumbnails and no error/failure message is displayed.		Upload	2.7	normal	normal	Future Release	defect (bug)	reopened		2008-12-30T02:50:09Z	2011-08-05T08:31:26Z	"The process of uploading images that have dimensions (physical size) greater than the maximum size allowed by the global setting will fail part way through the process without an error or failure message being displayed.

Example: Uploading a JPEG image with a width of 625 pixels and height of 938 pixels.  This physical size is greater than the maximum size allowed by the default WordPress configuration.

When uploading such an image using the ""Add an Image"" panel the the Flash uploader will stop with the upload progress bar at 100% and displaying ""Crunching…"".  The Browser uploader will return a blank ""Add an Image"" panel display.

In both cases the images are uploaded to the appropriate directory on the server and appear when the post's media gallery is refreshed.  Thumbnail images are not generated for these uploads.  It appears the failure is before or during thumbnail generation.

Note: The maximum image dimension allowed for upload is not the same as the Administration > Setting > Media > Large Size: Max Width and Max Height settings.  In my case these settings are both set at 1024 pixels (above the size of the image I am working with).  It appears this control panel setting only impacts the HTML image tag attributes for posts, so as not to break the visual design with images that are wider than a layout allows.

Now you may ask what is the default maximum dimension for uploaded images.  Unfortunately I cannot find my notes on where exactly the setting is in the WordPress code (it has no Web GUI access that I am aware of).  I had changed this setting once to work around this problem and hoped 2.7 would have fixed the issue.  It is a pain to track down as the location of this setting has changed over time as it moved to different files and functions with each new version of WordPress.

My understanding is that this maximum image dimension setting was set to prevent images over 3 megapixels from being uploaded since those are really big and readers shouldn't have to deal with such images.  This is old thinking from before broadband and photo blogs took off.

See: http://lorelle.wordpress.com/2007/03/28/wordpress-thumbnail-size-limit-hack/

I think the default limit should be raised, but that would be a feature request.  This ticket is to have error messages displayed.

"	DRGDC
Future Releases	14459	Rotate Full Size Images on Upload	azaozz	Upload	3.0	normal	normal	Future Release	enhancement	reviewing		2010-07-29T23:16:17Z	2013-01-06T08:52:07Z	"It may be worth a revisit to #7042.  Some mobile devices that use WordPress for Android are not capturing images in the correct orientation, instead they are writing the EXIF orientation to the image instead (which is a standard method these days).  In wp-android and other external clients that offer full size image upload, these images will not be rotated correctly upon upload.

Since most mobile users are on the go with no access to the wp-admin area to rotate the images themselves, it would work best if the image was rotated for them automatically.  

Hopefully there's a solution that wouldn't strip the EXIF data, some way to copy the EXIF data before rotating, then save it back again?"	mrroundhill
Future Releases	8234	Users with upload_files capability should be able to edit and delete uploaded files without having the edit_post/delete_post capability		Upload	2.7	low	minor	Future Release	enhancement	new		2008-11-15T22:17:14Z	2009-11-20T20:31:07Z	Users with upload_files capability are able to upload files but can't edit/delete his/her own uploaded files without having the edit_post/delete_post capability. Users capable to upload files should also be capable to edit/delete their own uploaded files.	olethomas
Future Releases	7491	thumbnail creation fails silently		Upload		normal	normal	Future Release	enhancement	new		2008-08-09T19:16:19Z	2010-03-06T16:13:08Z	"When thumbnail creation fails, it fails silently, with no indication why it fails. That is a real pain in the ass if you're trying to debug. Frankly, I assumed for months that thumbnailing just wasn't implemented yet- it was only because I noticed that it does work on ma.tt that I even went back and tried to debug the situation.

I'm still not succeeding in actually getting the thumbnailing working, for what it is worth- extensive googling suggested I should install libgd, which I've now done, but no helpful errors from wordpress means I'm just back at square one in terms of figuring out why it is breaking.

There are no other directly pertinent bugs, but #7039 and #1952 mention instances of silent failure being a problem and #2794 has a (now bitrotted) patch creating an error reporting system.

"	tieguy
Future Releases	7580	Use Exif description to autofill the caption		Upload	2.6	high	normal	Future Release	feature request	new		2008-08-23T06:26:39Z	2011-11-19T19:58:35Z	"Hello,
I test a lot of softwares to create a Exif description for my pictures.
Like ""Exif Farm"" or other kind of this softwares.
But When I Upload this picure in wp 2.6 the description will not show!
but i have some picture from the web, and when i upload them, wordpress show the description of it automatically in description Box!
like this picture:
http://www.hinhxinh.com/data/media/8/Beijing_Olympic_2008_-___075.jpg
and show description on it correctly:
http://i33.tinypic.com/2yyqk1t.jpg
Please tell me:
the problem is from Wp,
Or My software is not original?
'''So What should i do to show Description Exif Data in wp Correctly?'''"	mrmax
Future Releases	12720	Delete user and hook confusion when deleting users in Multisite		Users	3.0	normal	normal	Future Release	defect (bug)	new		2010-03-26T12:42:59Z	2010-06-23T17:24:58Z	"Currently:
The hook ''wpmu_delete_user'' fires when deleting user in Super Admin->Users.
The hook ''remove_user_from_blog'' when deleting user under site Users->Authors & Users.
In standard WP:
The hook ''delete_user'' is called when deleting users it should be the same in MultiSite when deleting from Super Admin->Users.
Or add new hooks and deprecate previous.
''delete_user_from_network'' for when deleting a user totally.
''delete_user_from_site'' for when deleting a user from a specific site. This is hook also then fires in non-MultiSite mode since that then corresponds to one site."	andreasnrb
Future Releases	13569	Odd edge case with shared user tables and custom admin username during install		Users		lowest	trivial	Future Release	defect (bug)	new		2010-05-27T06:06:43Z	2010-11-13T08:04:31Z	"1. In install 1, run install.php and use a custom username (NOT called 'admin') and set the e-mail to email@example.com.

2. In install 2, before installing, set up shared user tables with install 1. Then run the installer. You won't have the ability to choose usernames (that's expected). Use the *same* email.

3. Click ""Install."" You'll get hit with a WP_Error object.

What's happening? The logic in wp_install() is to do a username_exists() against the username passed to it. If the user exists, it assumes that you're using shared user tables. Problem is, wp_install() is passed 'admin' from install.php (as that's the default, and you don't see the fields when custom user tables are setup), while your user is not called 'admin'. The e-mail address is already being used for another user however, so it is creating 'admin' and is failing on the duplicate e-mail address.

If the email address doesn't match any user, I imagine you'd instead get an 'admin' user in your second install, which you could promptly delete. I see no problem with that, as the alternatives are to pick which user should become an admin.

So, the fix would be to change username_exists() and the logic that follows, and instead match the e-mail address with an existing user, and make that user the new administrator. If no user with that email exists, we create an admin user and they can tough it out.

I do not feel this is a blocker at all. The symptoms I am seeing should be the same in 2.9.2 if you removed the admin user in install 1, then proceeded to share user tables with install 2 before installing.

It'd be nice to at least prevent the fatal error and allow the install to finish, however. I do want to get to it in 3.0 if I can, since we now are allowing custom admin names. That said, setting to 3.1."	nacin
Future Releases	11959	Value Truncation Still Unchecked in registration.php		Users		normal	normal	Future Release	defect (bug)	new		2010-01-20T22:59:50Z	2010-11-13T07:38:28Z	Functions such as username_exists() fail to perform sanity checks against the storage schema.  As a result, it is possible to register multiple users with the same username, if the length is greater than or equal to the username field size.  Only the first user can login, however anyone re-registering that username can impersonate the first user to reset their password.	miqrogroove
Future Releases	12393	Hooks to enable custom login without editing core files		Users	2.9.2	low	normal	Future Release	enhancement	new		2010-02-26T21:01:06Z	2010-04-23T18:32:10Z	"One of the basic features of wordpress is to avoid having users edit core files.
It is impossible to properly customise wp-login without manually editing the file directly - not good for upgrades!

Need to make login_header function pluggable or add a do_action hook before the <html....> tag
Need to add a login_footer.

In fact what is required was highlighted in #4478 complete with diff file. This was marked as resolved BUT IT WAS NOT! I agree it might be a duplicate of issue #9682 BUT the underlying issue of being able to overwrite the login-header function WAS **NOT** solved.

(see recent support forum requests #252094  and #333994)

The solution MUST allow a replacement of login header (and even better also a replacement of the </body></html> tags from the switch statement with a login_footer function which could also be overrided - pluggable).

Thanks.

In an ideal world need to re-open #4478 to ensure accurate resolution.

Thanks"	sleepuser
Future Releases	8911	Use $WP_User as the standard unit of user information	jeremyclarke	Users		normal	normal	Future Release	feature request	new		2009-01-21T19:51:14Z	2011-08-04T23:15:43Z	"Right now much of the core code and most plugins use the old get_userdata() function to fetch information about users. This works okay for most cases but fails to take advantage of the new $WP_User object type. Using the objects makes the user information much more powerful because you can immediately call methods like $user->has_cap('edit_posts') without messing around. It also just makes sense, and not using the pretty object is silly.

In some places, like edit-user.php, where more functionality is needed there are functions like get_user_to_edit() that make use of the $WP_User object. I think that WP should clearly move towards always using the modeled object version rather than the straight db version in all places, and encourage plugin authors to do the same. 

Luckily the $WP_User wrapper uses get_userinfo to fetch its data and rewrites all the elements into its first level, so effectively the resulting object from $WP_User has all the same data as get_userinfo() and thus deprecates perfectly in all situations. 

My proposal would be to create a new wrapper function to be used instead of get_userinfo():


{{{
get_user($id, $name = '')
}}}


This would just initiate the object and return it, similar to get_post. It's also fits much better in the overall naming conventions of wp with friends like get_term. 

If possible, it might also be good to move the actual database sql from the get_userdata() function into the $WP_User object definition somewhere, that way its all in one place. Looking at it now it also seems like the whole _fill_user() function thing could be done more elegantly to explain itself and the cache better. [problem: pluggable.php has get_userdata(), which complicates things]

Finally, since get_userdata() currently calls _fill_user() every time then fetches all meta_value/key's for the user, wouldn't it be faster to make just one db call that fetches the row from wp_users AND the values from the usermeta table? If you are checking 30 users on your page for some reason (say, a twitter style list of your authors in the sidebar) that would save 30 database connections, which makes a difference no matter what! 

[probably should be in another ticket, but it would also be great to have access to a global function get_users() that fetched a set of users (say, active ones or a specific role) all at once based on criteria like get_terms() or get_posts(), it would save time if you are getting many users and if it added them all to the cache after fetching it would probably be a lot faster than checking each user individually]

I'm very interested in feedback. I'll try to work on a patch at some point soon (mental note: before 2.8 feature freeze)"	jeremyclarke
Future Releases	14376	"admin post.php fails html validation due to use of  ""["" in name/id/for of hidden custom fields"		Validation	3.0	lowest	normal	Future Release	defect (bug)	new		2010-07-21T07:37:54Z	2012-12-25T16:11:48Z	"Post.php is causing many many html validation errors due to hidden screen reader text for post meta fields mainly. Not a major problem, but annoying when attempting to validate admin plugin code.

eg:
{{{
<label class='screen-reader-text' for='meta[1957][key]'>Key</label><input name='meta[1957][key]' id='meta[1957][key]' tabindex='6' type='text' size='20' value='_wp_geo_latitude' />

character ""["" is not allowed in the value of attribute ""id""
character ""["" is not allowed in the value of attribute ""for""
}}}
""["" are allowed in the name attribute.  So perhaps one could simply strip them out them for the 'id' and the 'for'?

Other failed validation messages that occur a lot and appear to be wp generated code:
-   ID ""_ajax_nonce"" already defined
-   reference to non-existent ID ""metakeyselect""

"	anmari
Future Releases	8910	Limit the RSS widget from using its own url		Widgets	2.8	high	major	Future Release	defect (bug)	reopened		2009-01-21T19:40:59Z	2012-02-06T08:15:20Z	"'''NOTE:''' Copied from [http://trac.mu.wordpress.org/ticket/852] since 'This is really a WP issue, not strictly MU. Can you open a ticket in WP's trac?'

I admit that this is not a well conceived thought but I wanted to throw it out.

There's some discussion on the premium site about individual blogs using their rss widgets to display their own feeds. This of course causes issues with an unnecessary rss feed pull as well as old data since the feeds are cached.

May I suggest a check to see if the inputted RSS feed matches the individual blog's own rss feed, kick it out with an error and suggesting to the user that they use the Latest Posts widget instead?

Marking this as 2.8 as it's not a high priority. "	webmaestro
Future Releases	20542	Extend register_widget to allow passing params as second argument	codearachnid	Widgets	3.4	normal	normal	Future Release	enhancement	new		2012-04-25T11:56:19Z	2012-05-15T20:24:50Z	"I ran into an issue recently where I needed to make multiple calls of `register_widget('my_custom_class');` on the same class and have multiple unique widgets registered. 

The problem I ran into is that every time the same class is called it will overwrite the last instance of the same class during the widget constructor request `parent::__construct('unique_id', 'widget title');` This does not allow for reuse of the same class to instantiate multiple widgets. I found that if I were to extend the register method in WP_Widget_Factory to pass through arguments into the extended WP_Widget constructor that I can reuse the same class for multiple widget registations. I am working out the logic to implement this directly into /wp-includes/widgets.php for future functionality improvement."	codearachnid
Future Releases	23012	Refresh the code for the default widgets	Viper007Bond*	Widgets	3.5	low	minor	Future Release	enhancement	accepted		2012-12-20T01:49:37Z	2012-12-21T21:28:45Z	"The default widgets serve as examples for many people to make new widgets. We should make sure they're up to date in terms of coding standards and best practices. There's many places where this is not the case.

A few examples:

* `$instance['text'] = stripslashes( wp_filter_post_kses( addslashes($new_instance['text']) ) );`
* `$text = esc_textarea($instance['text']);` rather than at output

Also tons and tons of formatting issues.

I'll volunteer to take this on."	Viper007Bond
Future Releases	15550	WP_Nav_Menu_Widget needs a filter for args		Widgets	3.1	normal	normal	Future Release	enhancement	new		2010-11-23T21:48:57Z	2011-01-13T08:34:07Z	"I have a very common need to change the walker of a menu printed by WP_Nav_Menu_Widget. The only way to do this is by injecting a new walker on the args array.

By so, I propose changing '''default-widgets.php''':

{{{
function widget($args, $instance) {

	// Get menu
	$nav_menu = wp_get_nav_menu_object( $instance['nav_menu'] );

	if ( !$nav_menu )
		return;

	$instance['title'] = apply_filters('widget_title', $instance['title'], $instance, $this->id_base);

	echo $args['before_widget'];

	if ( !empty($instance['title']) )
		echo $args['before_title'] . $instance['title'] . $args['after_title'];

	wp_nav_menu( array( 'fallback_cb' => '', 'menu' => $nav_menu ) );

	echo $args['after_widget'];
}
}}}

To:
	
{{{
function widget($args, $instance) {

	// Filter for args
	$args = apply_filters('nav_manu_widget_args', $args);

	// Get menu
	$nav_menu = wp_get_nav_menu_object( $instance['nav_menu'] );

	if ( !$nav_menu )
		return;

	$instance['title'] = apply_filters('widget_title', $instance['title'], $instance, $this->id_base);

	echo $args['before_widget'];

	if ( !empty($instance['title']) )
		echo $args['before_title'] . $instance['title'] . $args['after_title'];

	wp_nav_menu( array( 'fallback_cb' => '', 'menu' => $nav_menu ) );

	echo $args['after_widget'];
}
}}}
"	brodock
Future Releases	19635	Non-ASCII chars in user name changed to question marks after sending new plugin request		WordPress.org site		normal	normal	WordPress.org	defect (bug)	new		2011-12-21T13:52:47Z	2012-08-10T18:12:55Z	"I have just sent request to add new plugin to repository, and found that some chars in my name were changed to question marks:

{{{
WordPress Plugins » Requests
user-ranks from Daniel Fru?y?ski (sirzooro) [plugin]
}}}

Should be:

{{{
WordPress Plugins » Requests
user-ranks from Daniel Frużyński (sirzooro) [plugin]
}}}"	sirzooro
Future Releases	17095	format or validate author url from api.wordpress.org		WordPress.org site		normal	normal	WordPress.org	defect (bug)	reopened		2011-04-09T16:44:13Z	2011-04-09T18:04:56Z	"The author url from api.wordpress.org does not seem to do full format checking. Not apparent in browsers since they will understand malformed urls but is a problem when outputting elsewhere.

Example: 
{{{
<author type=""string""><![CDATA[<a href=""http:www.artificium.sk"">Stanislav Gunčaga</a>]]></author> 
}}}


 "	wycks
Future Releases	17917	Profile pages should include activity on local forums as well		WordPress.org site	3.2	normal	normal	WordPress.org	enhancement	reopened		2011-06-28T07:43:21Z	2012-12-07T10:18:46Z	"Since WordPress 3.2 is going to show a link to the profile pages of the various contributors and translators, it seems only fair for that profile page to reflect the activity of those translators on the local forums as well. 

Currently if you go to my profile page for example http://profiles.wordpress.org/users/DeFries/ you will only see some forum activity on the international forum. Most of my activity is done however on the Dutch Forum ( http://nl.forums.wordpress.org ). Something you can see on the profile page of the Dutch forum itself: http://nl.forums.wordpress.org/profile/defries 

For starters, it would be a better suit if the first mentioned profile url shows all of the users activity on the forums, but having both reflect the same would be a warm welcome. Having the two merged could even be a better solution. I'll leave that up to you guys."	defries
Future Releases	14452	Duplicate check for comments: Inappropriate errorhandling for xmlrpc		XML-RPC	3.0	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-07-29T08:44:34Z	2012-06-23T22:48:28Z	The duplicate check for comments just dies in case a dulicate is detected(see wp-includes/comment.php around line 550). This ends up with a html page delivered in any cases. When accessing through xmlrpc this leads to the problem that this html page is send back to the xmlrpc client instead of a proper xmlrpc formated message.	mrutz
Future Releases	5461	Add ability to set description for XML-RPC file uploads		XML-RPC	2.3.1	normal	normal	Future Release	enhancement	new		2007-12-12T22:36:17Z	2009-06-13T03:01:40Z	It's been suggested that we provide a way to populate the description field for file uploads.  This is something that we could add to the wp.uploadFile method.	josephscott
Future Releases	5310	XMLRPC interface should expose mechanism for listing and deleting media resources	josephscott	XML-RPC	2.3.1	normal	normal	Future Release	enhancement	new		2007-11-02T21:34:24Z	2009-10-25T10:05:07Z	"Right now the XMLRPC interface supports the ""newMediaObject"" mechanism that is part of the MetaWeblog API, but lacks any method for inspecting or otherwise manipulating media objects.

I think to support a richer remote client experience, the XLMRPC interface should support at least a method for listing the media objects that have been previously uploaded (similar to what appears in the ""Browse"" tab of the wp-admin post editor), and for deleting a media asset that is present.

"	redsweater
