﻿__group__	ticket	summary	owner	component	_version	priority	severity	milestone	type	_status	workflow	_created	modified	_description	_reporter
Future Releases	17948	Enhancements to the login and registration forms	wpdavis	Multisite	3.2	normal	normal	Awaiting Review	enhancement	new		2011-06-30T16:25:01Z	2013-01-14T19:27:28Z	"I would like to propose a significant overhaul of the registration and login forms for 3.2, which I'd be happy to take on. A few things that I think would be helpful:

Combine registration processes for multisite and single-user into one form on one page.
Allow the registration and login to be templatized — no reason this should be for MS only.
Standardize filters, actions and variables between MS and single-user when at all possible.

A few related tickets:

#17904
#17306
#17085
#16866
#16411
#17630"	wpdavis
Future Releases	4010	Add Image Importing to the Blogger Importer	Workshopshed	Import		normal	normal	WordPress.org	enhancement	reopened		2007-03-21T20:21:28Z	2013-04-09T15:59:14Z	The new blogger importer currently does a great job of bringing the blog over to WP, but it leaves the images associated with the blog on blogger.com and/or blogspot.com.  This violates blogger's TOS and risks having the user's image links blocked by blogger.  This change will move those images (using the WP image upload facility, of course) to the user's blog and fix the links as the import is done.	clwill
Future Releases	11890	allow get_the_content to accept post ID	williamsba1	Template	2.9.1	normal	normal	Future Release	enhancement	new	close	2010-01-13T22:58:06Z	2010-01-14T00:48:23Z	"The function get_the_content currently doesn't accept a post ID as a parameter.  I'm suggesting adding this as a fourth parameter allowing this function to work like get_the_title does.

I'll supply a patch if this sounds like a good idea"	williamsba1
Future Releases	4337	Blog by Email: No content is assumed	westi*	Blog by Email	2.2	high	major	Future Release	defect (bug)	accepted		2007-05-25T18:59:09Z	2013-02-05T03:14:40Z	"It seems, the Blog by Email functions is broken in WP 2.2.
Mails are recognized, but only the title/subject is assumed - no content. Content is empty :(
No matter if text email or html email.


{{{
Author = bla@example.org 
 
Content-type: text/plain, Content-Transfer-Encoding: 8bit, boundary: 
 
Raw content:
 
Author: 1
 
Posted title: Test
Posted content:
 
Mission complete, message 1 deleted.
}}}
"	jottlieb
Future Releases	5252	base64-encoded post-by-email post garbled.	westi*	Blog by Email	2.3	normal	normal	Future Release	defect (bug)	accepted		2007-10-24T08:58:20Z	2009-10-11T21:07:58Z	"When posting-by-email, my cellphone submits code using ""content-transfer-encoding: base64"". The message appears (output from wp-mail.php) like so:

Author = [my email] <p><p><b>Content-type:</b> text/plain, <b>Content-Transfer-Encoding:</b> base64, <b>boundary:</b> </p>
<p><b>Raw content:</b><br /><pre>SnVzdCB0ZXN0aW5nIHBvc3RpbmcgZnJvbSBteSBjZWxsLiBTdHJ1Y2sgbWUgd2hpbGUgcmVh
ZGluZyAgUmFwaCBLb3N0ZXIncyBwb3N0cyBhYm91dCB0aGUgZmlyZXMgaW4gQ2FsIHRoYXQg
YmVpbmcgYWJsZSB0byBwb3N0IHRvIHlvdXIgYmxvZyBmcm9tIGEgY2VsbHBob25lIGlzIGEg
dXNlZnVsIGZlYXR1cmUuIA==</pre></p>
<p><b>Author:</b> 1</p>
<p><b>Posted title:</b> =?utf-8?B?Q2VsbHBob25lIHBvc3RpbmcgaW4gV1A=?=<br />
<b>Posted content:</b><br /><pre>SnVzdCB0ZXN0aW5nIHBvc3RpbmcgZnJvbSBteSBjZWxsLiBTdHJ1Y2sgbWUgd2hpbGUgcmVh
ZGluZyAgUmFwaCBLb3N0ZXIncyBwb3N0cyBhYm91dCB0aGUgZmlyZXMgaW4gQ2FsIHRoYXQg
YmVpbmcgYWJsZSB0byBwb3N0IHRvIHlvdXIgYmxvZyBmcm9tIGEgY2VsbHBob25lIGlzIGEg
dXNlZnVsIGZlYXR1cmUuIA==</pre></p><p>Mission complete, message <strong>1</strong> deleted.</p>

The provided patch detects base64-encoded content transfers and base64_decodes them. For some reason (I'm no utf8-expert) the TITLE of the post has ""=?utf-8?B?"" prepended to the actual base64 content (see above), which means a check for this string + a cropping is needed or base64_decode will not decode the post title properly."	kallewoof
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	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	7644	Import Movable Type data using AtomPub.	westi*	Import		normal	normal	WordPress.org	enhancement	accepted	close	2008-08-29T20:33:52Z	2011-09-15T17:17:13Z	This is a split ticket from #7543. This includes the latest Movable Type portion of the code.	cavemonkey50
Future Releases	7543	Import TypePad data using AtomPub.	westi*	Import		normal	normal	WordPress.org	enhancement	accepted	needs-review	2008-08-19T02:44:26Z	2011-09-15T17:17:11Z	"First off, I want to mention that TypePad updated their AtomPub server a few days ago, and their server does not seem to be sending comments. With a little luck, my current code should work fine once that server starts functioning again, but for the time being I would highly recommend not committing this into core.

Instead, I'm hoping people can look over the code and offer suggestions for improvement, test results, etc. While the Summer of Code is officially over today, I will be working on this until the job is done.

Alright, now to what this is. As some of you may know, I've been working on an Atom Publishing Protocol ([http://www.rfc-editor.org/rfc/rfc5023.txt RFC 5023]) based importer this summer for the Google Summer of Code. The diff attached is the latest version of my work.

The advantages of using the Atom Publishing Protocol are as follows:

 * Nothing has to be done in the old blogging software to prepare for import (no export files, etc). Users just enter their blog URL, username, and password and the importer grabs all of the data using AtomPub.
 * More data is imported compared to the old importers, especially with TypePad. Post slugs, comments, trackbacks, tags, categories, excerpts, etc are all imported. Everything used for posts in MT/TypePad is imported using AtomPub.
 * The Atom Publishing Protocol is an established standard. With the exceptions of tag additions (which don't necessarily need updates), the importer should not have to be changed and should continue working well into the future.

I should mention there is one drawback to using the Atom Publishing Protocol. For the time being, it appears pages can not be retrieved using AtomPub. They were retrievable a few weeks ago, and I'm currently talking with Six Apart to see what happened.

I would greatly appreciate any and all feedback. Let me know your suggestions, and I'll be happy to incorporate them."	cavemonkey50
Future Releases	11903	insert_with_markers is not threadsafe	westi*	Permalinks	2.9	normal	major	Future Release	defect (bug)	accepted		2010-01-15T06:27:45Z	2013-02-07T21:53:27Z	"From wp-admin/includes/misc.php the function insert_with_markers may be called multiple times on a busy server and if the htaccess is already in the process of being written it is possible that two PHP threads could attempt to write to it causing corruption such as the following:



{{{
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress
s

}}}

Notice the dangling 's' at the last line"	strings28
Future Releases	10551	wp_die() triggers block when using ModSecurity Core Rules	westi*	Security	2.8.3	low	normal	Future Release	defect (bug)	accepted	dev-feedback	2009-08-05T19:47:28Z	2011-03-22T09:51:47Z	"wp_die() causes ModSecurity (using Core Rules), a commonly used Apache plugin, to throw a 406 error, blocking the message from displaying.

This seems to be triggered by the fact that a 500 error is thrown.  I went and changed the default status code to 401 (Unauthorized) and it worked like a charm.  I just wonder if there is a better fix for this issue... or simply a better status code to use.

Perhaps making a group of functions to make the error codes more focused.

Example:
{{{
wp_die_auth( __('You do not have sufficient permissions to access this page.') );

/**
 * Exits WordPress with Unauthorized status code.
 *
 * @see wp_die()
 */
function wp_die_auth($message, $title = '') {
	wp_die( $message, $title, 401 );
}
}}}"	cstrosser
Future Releases	21737	Users should have to jump through hoops to set passwords of their choosing, and we should guard better against weak passwords	westi*	Security		normal	normal	Awaiting Review	feature request	accepted		2012-08-30T04:07:17Z	2013-04-18T02:44:43Z	"People are terrible at choosing secure, unique, complex, unguessable passwords. Unless someone is using a password storage system, the chances are good that the passwords they're choosing are really weak.

We can mitigate this problem.

1. Let's make the default to always be that WordPress picks a password for you. When installing WordPress, or when creating a new user account, or when changing your password on your profile. The default should be that we generate a secure password for the user. They can remember it, write it down (not ideal, but generally more secure than choosing a weak password), or copy and use it once, check the ""remember me"" box, and not worry about it until their cookie expires on that computer.

2. If they do opt to manually create a password, we need to do better than our current password strength meter. And the lowest level should actually nag them with an AYS before they proceed. I suggest the following, to start, which would trigger the lowest level, and cause them to have to dismiss a warning (or check a checkbox... UI TBD) before continuing:

* compare the strtolower'd version of their password to strtolower'd versions of all their info (username, first/last name, part of e-mail address before the @, etc).
* any password that is shorter than 8 characters
* a blacklist of popular passwords (these lists are available... even grabbing the top 100 would give use good coverage)
* 3 or more consecutive digits (""123456"" and company are very popular)
* anything that looks like a date"	markjaquith
Future Releases	5172	Adding classes to wp_generate_tag_cloud	westi*	Template		normal	normal	Future Release	enhancement	accepted	dev-feedback	2007-10-09T17:09:14Z	2011-04-30T08:50:18Z	"The attached patch changes 2 things on the [source:/trunk/wp-includes/category-template.php#L330 wp_generate_tag_cloud] function. 

1) The current code uses single quotes instead of double quotes, I believe the standard is to use double quotes. I've converted single quotes to double quotes.

2) I've rounded the tag size to a whole number (no decimal places).

3) I've added a class ""tag-cloud-item-X"" where X is the number in the list and a second class ""tag-cloud-size-X"" where X is the size of the tag. . This will allow theme designers to apply different styles to tags. For example changing the colour from cold to hot depending on order or size."	chmac
Future Releases	17487	Codepage issue with the wp.org Credits API	westi*	WordPress.org site		normal	normal	WordPress.org	defect (bug)	accepted		2011-05-18T10:28:47Z	2012-11-22T03:34:06Z	"I was playing with my profile page at wp.org and changed the Name field from:

{{{demetris}}}

to:

{{{demetris (Δημήτρης Κίκιζας)}}}

What the API returns for that is:

{{{demetris (???????? ???????)}}}

It seems the API returns its results in ISO 8859-1. Can we change that to UTF-8?

"	demetris
Next Release	23688	esc_textarea, wp_richedit_pre and wp_htmledit_pre eat post content under PHP 5.4	westi	Formatting	trunk	high	blocker	3.6	defect (bug)	reopened		2013-03-04T17:27:22Z	2013-04-25T09:51:24Z	"Because of a change in default behaviour in {{{htmlspecialchars}}} in PHP5.4 it is possible for these three functions to eat perfectly valid post content and make it impossible to edit existing posts.

Scenario:
 * blog_charset is ISO-8859-1
 * Post contains some 8bit characters

You try and edit the post and instead of the post content you are presented with a blank editor :(

On the front end the posts display fine.

The underlying cause it this change in {{{htmlspecialchars}}}

""5.4.0 	The default value for the encoding parameter was changed to UTF-8.""

Because the string is not a valid UTF-8 sequence an empty string is returned :(


Related to #20368"	westi
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	13473	comment_status should be set to default_comment_status when commentstatusdiv is removed	westi	Comments		normal	normal	Future Release	defect (bug)	reopened		2010-05-20T23:36:24Z	2011-11-24T16:13:29Z	"When the Comment Status box is removed from the Add/Edit Post screens, posts should be created with the comment_status set to the value of the default_comment_status option.

-----

I had hidden the Comment Status box via:
remove_meta_box('commentstatusdiv','post','normal');

and made sure that default_comment_status was set to open:
update_option('default_comment_status', 'open');

After adding a new post it displayed ""Comments Off"" when I was assuming that it should have honored the value of default_comment_status."	jimmcq
Future Releases	13158	Cron : some events may not be scheduled	westi	Cron	3.1	high	major	Future Release	defect (bug)	new		2010-04-27T23:29:46Z	2012-08-03T22:39:04Z	"the problem appears when two different events are scheduled at the same time

what happens in code is :

1st event : _get_cron_array();
2nd event : _get_cron_array();

1st event : _set_cron_array( $crons );
2nd event : _set_cron_array( $crons );


1st event is lost."	arena
Future Releases	11826	Endless Cron Spawn	westi	Cron	2.9	normal	normal	Future Release	defect (bug)	new		2010-01-08T19:09:02Z	2010-12-14T10:00:23Z	"I somehow get it managed to keep such request in memory while they consume CPU all the time. I noticed that first a week ago or so and now I was able to find out some specifics:

{{{
REQUEST_URI /wordpress-trunk/wp-cron.php?doing_wp_cron
REQUEST_METHOD post
}}}

Maybe there is a condition for an endless loop in there?"	hakre
Future Releases	11800	doubled execution of cron jobs	westi	Cron	2.9.1	normal	normal	Future Release	defect (bug)	new		2010-01-07T11:17:53Z	2011-06-02T07:18:50Z	"Hi,

as I've already mentioned in ticket #11505 , cron-jobs occasionally get executed twice (e.g. daily backup arrives two times).

I've changed the code according to the patch attachment:ticket:11505:ticket-11505-stop-gap.patch (which derives from [http://wpengineer.com/ping-problem/]) after my comment:ticket:11505:49 and had no doubles within this time period. This week I've upgraded to WP 2.9.1 and since then backups arrive two, sometimes three times, again.

Looking at the changes from 2.9 to 2.9.1, I have no other explanation for this behavior. - Maybe we should consider having a closer look again on this patch attachment:ticket:11505:ticket-11505-stop-gap.patch .

Greetz,
Berny"	neoxx
Future Releases	12333	"Get ""message"" and ""error"" params in wp-login.php"	westi	General	2.9.2	normal	minor	Future Release	enhancement	new	reporter-feedback	2010-02-22T14:48:41Z	2012-01-11T11:24:26Z	"It might be useful a parameter like ""redirect_to"" to set $message and $error of login_headers() from the url of wp-login.php."	FiloSottile
Future Releases	15760	"LiveJournal Importer mishandles some <lj-cut> and <lj user=""""> expressions"	westi	Import		normal	normal	WordPress.org	defect (bug)	assigned		2010-12-10T04:45:17Z	2011-02-19T18:52:42Z	"There is a note on plugins.trac ticket 1231 that says this should be handled in core.trac instead, so I'm cross-posting it here. The patch and ticket were originally added by a-bishop: 
http://plugins.trac.wordpress.org/ticket/1231

Reproduction steps: 1. Create a LiveJournal? entry that has <lj user=""foo"" /> in it. Note that this is XML-ish 2. Try to use the livejournal-importer on this post.

Bug The <lj user=""foo"" /> gets ignored because the regular expression is too strict.

I've attached a patch that makes LiveJournal? Importer recognize the XML-ish version.

Patch:[[BR]]
http://plugins.trac.wordpress.org/attachment/ticket/1231/livejournal-importer.patch"	designsimply
Future Releases	15381	Rework WP_Scripts to support named groups	westi	JavaScript		normal	normal	Future Release	enhancement	new		2010-11-10T21:59:49Z	2011-03-22T09:26:12Z	"Currently WP_Scripts has some ""special"" code for splitting things across header and footer and concatenating core scripts.

I would like to change it to support the following:

 * Named Groups - so we can have header, footer, ...
 * L10N awareness - so we can auto output the l10n.js file first if we need it - XRef #15124
 * Concatenation opt-out
 * Concatentaion opt-in for plugins.

I was working on this for #15124 until it became apparent that it wasn't right to do it for 3.1 - not enough time to fully test."	westi
Future Releases	18493	HTML E-Mails	westi	Mail	3.2	normal	normal	Future Release	enhancement	reviewing	early	2011-08-22T00:29:44Z	2013-04-13T16:33:09Z	"Wojtek worked on the Enhanced E-Mails project for GSoC this summer.  It's definitely something that would be nice to have in core.  The plugin already exists in the repository - [http://wordpress.org/extend/plugins/enhanced-emails/ Enhanced Emails].  There are still some things that need to be cleaned up in the code, but it works pretty well.

I'm hoping we can clean it up, test it, and get it in core. "	aaroncampbell
Future Releases	12145	Enhance activation process to improve integration with site theme	westi	Multisite		normal	normal	Future Release	enhancement	new		2010-02-06T07:10:13Z	2012-01-11T11:21:04Z	"wp-activate.php creates many notices on load due to theme hackery

an example to start:
{{{
Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\comment-template.php on line 777

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\comment-template.php on line 794

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\general-template.php on line 1588

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\query.php on line 2600
Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\query.php on line 2600

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\post-template.php on line 431

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\query.php on line 2600

Notice: Trying to get property of non-object in G:\www\ho.st\wp-includes\post-template.php on line 1172
class=""page page-id- page-parent logged-in"">
}}}

the problem is, that wp-activate.php attempts to simulate a normal WordPress page, the problem arrises that when the header is included and/or custom code in the theme runs on the header, that the no-existance of the current post id (NULL) causes most of the WordPress functions to complain, as they're expecting a correct post object to be returned.

2 options
 1. Update all API function to move to {{{ if ( ! $_post = get_post(..) ) return false; - This should probably be done anyway
 2. Improve the hackery to allow displaying custom pages such as wp-activate.php more transparently.

Furthur to #2, this might involve creating a page in the database which the API functions can access directly, the activate site page would then become a real page in the eyes of WordPress."	dd32
Future Releases	17615	WP_List_Table::get_columns does not work for plugins	westi	Plugins	3.1.3	normal	normal	Future Release	defect (bug)	assigned		2011-05-30T11:20:56Z	2011-06-11T09:36:27Z	"see Ticket #15386 - the ticket is closed, however I have the very same problem with 3.1.3 version and the solution example provided do not work for me. 

Wordpress claims that there is no function as get_list_table , I have changed it to _get_list_table, after that change it does launch but returns a null object."	cyplo
Future Releases	4893	Audit of all filter and action names.	westi	Plugins		normal	normal	Future Release	enhancement	new		2007-09-02T20:22:27Z	2010-03-18T21:09:32Z	"I think for 2.4 we should do an early audit of all the filters and actions in the core and ensure that they follow the following set of rules:

 1. All names should be unique
 1. All names should be relevant to the calling context
 1. All filters should pass in relevant context information

This should then ensure plugins can easily filter just the things they want to.

This is to avoid messes like {{{the_title}}}

{{{
./wp-includes/post-template.php:        return apply_filters( 'the_title', $title );
./wp-includes/comment.php:      $post_title = apply_filters('the_title', $post->post_title);
./wp-includes/classes.php:              $output .= $indent . '<li class=""' . $css_class . '""><a href=""' . get_page_link($page->ID) . '"" title=""' . att
ribute_escape(apply_filters('the_title', $page->post_title)) . '"">' . apply_filters('the_title', $page->post_title) . '</a>';
./wp-includes/deprecated.php:           $string .= apply_filters('the_title', $post->post_title, $post);
./wp-includes/deprecated.php:           $string .= apply_filters('the_title', $post->post_title, $nextpost);
./wp-includes/link-template.php:        $title = apply_filters('the_title', $post->post_title, $post);
./wp-includes/link-template.php:        $title = apply_filters('the_title', $post->post_title, $post);
./wp-includes/general-template.php:                                             $text = strip_tags(apply_filters('the_title', $arc_title));
}}}"	westi
Future Releases	13347	Mobile user agent detection for vars.php	westi	Plugins		lowest	minor	Future Release	enhancement	new		2010-05-11T16:21:58Z	2011-07-06T16:11:21Z	We've added some user agent detection for mobile clients in the vars.php file, thought it would be good to have in core for plugins and themes to use.  Attaching patched vars.php.	mrroundhill
Future Releases	13548	Settings API to include user options	westi	Plugins	2.7	normal	normal	Future Release	enhancement	new		2010-05-26T07:42:52Z	2013-01-03T19:25:19Z	"Hi,

I've reworked all of my plugins to build upon the [http://codex.wordpress.org/Settings_API new Settings API]. The handling and security are great.

As far as I understand, the Settings API can't be used for user options. - What do you think about an extension of {{{ register_setting }}} & Co. to reflect user options?

Greetz,
Berny"	neoxx
Future Releases	11210	Split wp_new_user_notification() into two functions	westi	Plugins	2.9	normal	normal	Future Release	enhancement	new		2009-11-20T22:05:31Z	2010-09-07T19:02:37Z	"`wp_new_user_notification()` sends emails to newly registered user and to admin. One of my plugins ([http://wordpress.org/extend/plugins/wypiekacz/ WyPiekacz]) redefines it in order to to disable emails sent to admin. Now I want to extend my other plugin ([http://wordpress.org/extend/plugins/user-locker/ User Locker]) so newly registered users will have to activate theirs accounts by clicking on link sent in email. In order to do this, I have to redefine the same function. I how to do this so both plugins could work at the same time - this is not a problem for me. 

However it will be better to allow to redefine only part of `wp_new_user_notification()` function - either one which sends email to new user, or to admin. Therefore I ask to split this function into two new ones. Attached patch does this."	sirzooro
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	11215	Improve naming of child/parent theme functions	westi	Themes	2.9	normal	normal	Future Release	enhancement	new		2009-11-21T09:51:10Z	2012-02-17T15:41:13Z	"We have confusing naming for child/parent theme functions.

We have references to stylesheet/template instead of child/parent which makes it unclear which function should be being used.

In #11033 we introduced a function for loading the child themes textdomain with a clear name.

We should look at deprecating the stylesheet/template nomenclature and use child/parent instead."	westi
Future Releases	10457	Parse shortcodes in text widgets by default	westi	Widgets	2.8	normal	normal	Future Release	enhancement	reopened		2009-07-21T11:27:06Z	2012-03-28T20:10:31Z	Currently, shortcodes are only parsed within post content. It would, to my mind, be a nice enhancement to allow them to be parsed from within text widgets as well. The implementation is trivial, so the only real question is what problems this might throw up.	ionfish
Future Releases	11303	XMLRPC (and APP) APIs should expose all Post/Page/Comment management functionality	westi	XML-RPC	2.9	normal	normal	Future Release	task (blessed)	assigned	close	2009-12-01T22:26:01Z	2010-09-23T20:34:55Z	"In #11243 we hid the trash status from {{{wp.getPages()}}} we also hide it for pages (and comments I guess).

Really these apis should be fully featured to allow clients to support the new things the api does.

We should revert the change made for trash for 2.9 and promote the fact that clients should be graceful when using these apis so as to cope when we introduce new features.

We also need to review the need for extra apis to allow trashing/untrashing of posts/pages/comments etc."	westi
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	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	21540	Add support for responsive video embeds	Viper007Bond	Embeds		normal	normal	Awaiting Review	enhancement	assigned		2012-08-10T17:15:50Z	2013-01-17T17:27:31Z	"By wrapping the html content of a video embed with a container (incl. class name), we could provide a simplified way for Theme authors to make video embeds truly responsive, through basic CSS.

See #21480"	obenland
Future Releases	8833	extract pluggable.php function logic into separate functions	Viper007Bond	Plugins	2.8	normal	normal	Future Release	enhancement	new	dev-feedback	2009-01-09T21:24:15Z	2012-08-31T18:23:53Z	"Currently, when a plugin overrides one of the pluggable.php functions with a custom implementation, there is no way to fall back to the standard version of the function.  Instead, plugin authors have to copy and paste all of the logic from pluggable.php into their custom function.  I'd love to see the actual logic separated out into ""private"" functions that are simply called the public ones.  For example:

{{{
if (!function_exists('wp_get_current_user')) {
    function wp_get_current_user() {
        return _wp_get_current_user();
    }
}

function _wp_get_current_user() {
    /* normal logic for getting the current user */
}
}}}

This would allow me to override the function, but still fallback to the standard implementation if I need to...

{{{
if (!function_exists('wp_get_current_user')) {
    function wp_get_current_user() {
        if ( /* some condition */ ) {
            /* my own custom get current user logic */
        } else {
            return _wp_get_current_user();
        }
    }
}
}}}

This wouldn't actually take that much work, and I'm happy to do it.  Not sure if it would be best to keep it all in pluggable.php, or if the standard implementations should be moved to pluggable.standard.php or something similar. ??

Original wp-hackers thread: http://groups.google.com/group/wp-hackers/browse_thread/thread/31295f83a13dc025"	wnorris
Future Releases	11946	Ensure image MIME type matches extension	Viper007Bond	Upload	3.0	normal	minor	Future Release	defect (bug)	reopened		2010-01-19T08:02:17Z	2012-07-26T22:55:00Z	"Take a bitmap (BMP) and rename it to `.png`. WordPress will say it's an `image/png` everywhere you look. This can cause issues if you're trying to manipulate it (thumbnail it, etc.).

We should either fix the extension or reject it."	Viper007Bond
Future Releases	8470	Large exports break frequently	tott	Export		normal	normal	Future Release	defect (bug)	new	reporter-feedback	2008-12-03T13:51:37Z	2009-11-18T21:21:54Z	"For large wordpress exports frequently the download stops at some point.

This effect seems to be due to bad memory utilization on slow downloads where the content cannot be flushed fast enough to the browser.

Attached patch includes various improvements in content flushing, and for cleaning of variables in order to save some memory."	tott
Future Releases	7813	export function does not preserve encoding	tott	Export	2.7	normal	minor	Future Release	defect (bug)	new		2008-09-30T20:07:25Z	2009-11-24T15:54:10Z	"when exporting strings are always converted to utf-8 while header and encoding is set to encoding used in blog.

this causes trouble when importing later."	tott
Future Releases	8455	Enhance usability in Wordpress Import - preselecting matching authors	tott	Import		normal	normal	WordPress.org	enhancement	new		2008-12-02T09:27:03Z	2012-09-10T10:21:11Z	To increase usability in wordpress imports, especially for imports with many users or imports that are rerun a preselection of authors would increase usability.	tott
Future Releases	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
Future Releases	18999	Quotes in emails	titi	General	3.2.1	normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2011-10-19T10:39:28Z	2011-12-19T01:57:53Z	"Quotes are displayed in plain HTML CODE 
{{{
&#8217
}}}

instead of the a real quote.

This bug is in any email reply notifications containing quote in the post.

Using BBPress 2.0 with Wordpress. French language."	thibotus01
Future Releases	6969	Don't apply wptexturize() to the insides of shortcode tags	tellyworth	Formatting	2.5.1	normal	normal	Future Release	enhancement	new	needs-unit-tests	2008-05-14T11:47:58Z	2011-05-31T08:45:13Z	"I have this for my post contents:

{{{
[code lang=""php""]$foo = 'bar';[/code]
}}}

The problem is my shortcode function gets this passed to it for the content string:

{{{
$foo = &#8216;bar&#8217;;
}}}

`wptexturize()` should be smart enough to not format the contents of registered shortcodes. If plugins want their contents formatted, they can pass the contents to the `wptexturize()` function itself."	Viper007Bond
Future Releases	6819	EXIF data extracted from uploaded images stored incorrectly	tellyworth	Media	2.5	normal	normal	Future Release	defect (bug)	new		2008-04-23T01:13:19Z	2009-11-23T15:25:26Z	Currently extracted EXIF data is stored as a single custom field with a serialized array containing all the data - it should be stored with one-custom-field per data entry, probably with the exif_ prefix.	matt
Future Releases	5953	Absolute upload_path fails	tellyworth	Upload		normal	normal	Future Release	defect (bug)	reopened		2008-02-22T05:39:43Z	2009-11-20T20:03:34Z	"1. On Options/Misc, enter ""/tmp/foo/bar"" as a value for the upload path setting.
2. Write a new post and attach an image.

Expected: the image file should be stored as /tmp/foo/bar/2008/02/file.jpg or similar.

Actual: a 'tmp/foo/bar' subdirectory is created within ABSPATH (if that's possible) and the file is stored there.  Both the filesystem path and URL path just append '/tmp/foo/bar', so you get 'ABSPATH//tmp/foo/bar/2008/02/file.jpg' and 'http://example.com//tmp/foo/bar/2008/02/file.jpg'

An absolute upload_path should probably be rejected unless you also specify an upload_url_path, because there's no way to know what URL corresponds to an arbitrary filesystem path.
"	tellyworth
Future Releases	12945	Constrain wp_page_menu()	technosailor*	General		normal	normal	Future Release	defect (bug)	accepted		2010-04-09T19:39:51Z	2010-05-02T18:49:39Z	"The wp_page_menu() function is the default callback for wp_nav_menu(). IOW, when a user is not using the new menu system, it defaults to this function. While that is good, any number of pages over, say 10, will make a theme puke in many cases.

As a workaround, I suggest we make a default of wp_page_menu() to exclude all pages() except home. It's a stupid idea, I think, but something needs to be done to make this manageable so I'm looking for feedback.

The Pro of taking this approach is that it encourages customization of menus via the WP menu system. It also does not lock theme devs into a particular approach because this stuff can be overidden via arguments and filters.

The con is that the default callback becomes pretty benign and useless. Almost pointless.

Ideas?"	technosailor
Future Releases	8994	Incorporate MediaRSS Plugin into core	technosailor	Feeds		normal	normal	Future Release	feature request	new		2009-01-29T18:00:20Z	2013-01-05T09:05:59Z	Per conversation on the hackers list, this ticket is a working area for incorporation of the MediaRSS plugin (http://wordpress.org/extend/plugins/mrss) into core for WP 2.8.	technosailor
Future Releases	15943	Custom Post Type not set after customizing permalinks.	sterlo*	Multisite	3.0.3	normal	critical	Future Release	defect (bug)	accepted	dev-feedback	2010-12-21T23:42:55Z	2011-01-06T23:11:07Z	"Developing a plugin,

It sets a custom post type on init:
{{{
      register_post_type(
        'staff_listing',
        array(
          'labels' => array(
            'name' => 'Staff Listings',
            'add_new_item' => 'Add a Staff Member',
            'new_item' => 'Staff Member',
            'add_new' => 'Add a Staff Member',
            'singular_name' => 'Staff Member'
          ),  
          'public' => true,
          'publicly_queryable' => true,
          'show_in_nav_menus'  => false,
          'exclude_from_search' => false,
          'show_ui' => true, 
          'hierarchical' => false,
          'rewrite' => array(
            'slug' => 'staff',
            'with_front' => false
          ),  
          'query_var' => 'staff', 
          'supports' => array(
            'title',
            'editor',
            'thumbnail',
            'comments',
            'revisions'
          )   
        )   
      ); 
}}}

If I add a staff member called ""john doe"" and then go to that on the front end - I expect to see this in $wp_query->query_vars:
{{{
[staff] => john-doe
[post_type] => staff_listing
[category_name] =>
[name] => john-doe
[is_404] =>
[queried_object_id] => ###
}}}

(I replaced the ID with ### since it changes from one install to the other)

That '''works''' on a standard WordPress 3.0.3 install.

But does '''not work''' on a WordPress 3.0.3 MU install.

The MU install gives me this:
{{{
[name] => john-doe
[post_type] => 
[category_name] => staff
[is_404] => 1
[is_singular] => 
[queried_object_id] => 0
}}}

Both the permalinks on the MU and standard setup are set as follows:
{{{
/%category%/%postname%/
}}}

If I change the permalink structure on the MU site to the default structure - the problem goes away.

The new URL is: ?staff=john-doe and it sets the following:
{{{
[staff] => john-doe
[post_type] => staff_listing
[name] => john-doe
[category_name] =>
[is_404] =>
[queried_object_id] => ###
}}}"	sterlo
Future Releases	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
Future Releases	9324	Let wp_link_pages do pagination when static page is used for front page	sorich87*	Template	3.0	normal	major	Future Release	defect (bug)	accepted		2009-03-12T17:20:02Z	2010-10-26T13:22:00Z	"Mentioned on WP-Hackers. If a static paginated page is used for the front page and wp_link_pages is used in the theme, the pagination links will return 404 because get_permalink will return the front page URL as the root of paginated links. I marked it as a bug since it can cause 404 errors if you don't know about it.

The enclosed patch tests for is_front_page and static pages using alternate _get_page_link functions for paginated content and using get_permalink for standard paginated links. It even works when a child page is set for the front page. 

This was a quick patch from a custom function, so it could probably be written a little better."	ev3rywh3re
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	12502	wordpress portability	significance*	General		normal	normal	Future Release	enhancement	accepted		2010-03-03T19:30:08Z	2011-08-07T21:13:10Z	"i find it really frustrating moving wordpress from server to server and to a new url.

this is mainly due to the fact that the url is hard coded in the database, requiring me to open up the sql and do a find and replace.

would it be possible to use the $SERVER globals to get the 'blog url' rather than making entries in the database with the http://blog.url/ part of the url?

that would make the process so much easier, since you could just backup/reup the database using your normal database admin tools without messing around with editing the .sql file or going through the processes described at 

http://codex.wordpress.org/Moving_WordPress#Moving_WordPress_to_a_New_Server



would it be possible to make wordpress more portable? i would be happy to help design/code the feature.


Dan"	significance
Future Releases	19466	Last-Modified HTTP header not just for feeds	sergey.s.betke@…	General	3.3	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-12-07T15:44:05Z	2012-12-04T21:36:22Z	"Wordpress write HTTP **Last-Modified**, **ETag** headers just for feeds (**class-wp.php**, **send_headers**). And support **If-Modified** HTTP request header just for feeds. Wordpress 3.3 doesn't support HTTP 1.1 **Cache-Control** header.
The best solution - support HTTP cache-control headers and for html output (full blog). But **If-Modified** HTTP request header (304 responces) for site support optionally (some not-ajaxed widgets and plugins will show wrong information without page reloading).

= WordPress version =
Latest WordPress files - 3.3-RC2-19567 
"	sergey.s.betke@…
Future Releases	21762	Storing a multidimensional array using register_setting double-serializes subarrays identified with a string	sekatsim	Database	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-31T22:43:16Z	2012-09-01T16:36:41Z	"Storing a multidimensional array, such as `$options['my-option'][$id] = ""value""`, into the database using register_setting results in the ""my-option"" string getting double serialized. The option_value is stored as:

`s:9:""'my-option'"";a:1:{s:9:""option-id"";s:5:""value"";}`

The my-option array is encased in both single and double quotes, so that `isset($options['option-id']` evaluates false, but `isset($options[""'option-id'""]` evaluates true."	sekatsim
Future Releases	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
Next Release	23155	Fire update_blog_public action from update_blog_status()	ryan	Administration	3.5	normal	normal	3.6	defect (bug)	reopened		2013-01-09T16:43:00Z	2013-05-01T13:12:46Z	The update_blog_public action is fired from update_blog_public() but not from update_blog_status(). Since update_blog_public() calls update_blog_status() the action should move down the stack and reside along the other actions fired by update_blog_status().	ryan
Future Releases	6822	Admin colors should be per-blog	ryan	Administration	2.5	normal	normal	Future Release	enhancement	new		2008-04-23T02:07:08Z	2010-03-25T05:58:52Z	When shared user tables are used, changing the colors for one blog should not change it for all.	matt
Future Releases	13648	Post link?	ryan	Comments	3.0	normal	normal	Future Release	defect (bug)	new		2010-05-30T22:51:23Z	2010-05-31T20:50:17Z	Adding '''?comments_popup=1''' to the url go to that post id number but in comment view with the trackback to the post with the regular permalink. Found this via search engine that indexed it instead of post url.	giuseppex
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	12257	wpdb Scales Badly Due to Unnecessary Copies of All Query Results	ryan	Database		normal	critical	Future Release	defect (bug)	reopened	early	2010-02-17T03:08:06Z	2013-03-19T05:19:44Z	"While working on #11726, I encountered a reproducible crash in wpdb::query()

The following code causes memory exhaustion on large result sets:

{{{
while ( $row = @mysql_fetch_object($this->result) ) {
	$this->last_result[$num_rows] = $row;
	$num_rows++;
}
}}}

The memory exhaustion message is error-controlled, causing a white screen of death even in debug mode.

I searched wp-db.php for references to $this->last_result, and I found no justification for these object reference copies.  $this->last_result '''should''' be maintained as a MySQL resource and properly optimized using the MySQL client layer instead of this PHP nonsense.

Tagging for dev-feedback to discuss which Milestone is appropriate."	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	21432	Deprecate *_blog_option()	ryan	General	3.4.1	normal	normal	Future Release	defect (bug)	reopened	dev-feedback	2012-07-31T21:53:06Z	2012-10-24T17:44:45Z	"Deprecate get_blog_option(), add_blog_option(), update_blog_option(), and delete_blog_option(). The regular *_option() functions wrapped with switch_to_blog() and restore_current_blog() should be used instead.

Previous discussion:

http://core.trac.wordpress.org/ticket/21270#comment:11"	ryan
Future Releases	12538	WP should cache menus	ryan	Menus	3.0	normal	normal	Awaiting Review	defect (bug)	reopened		2010-03-07T02:10:10Z	2012-01-04T17:34:26Z	"There's a prime example of how to do this in the menu ticket (i.e. the plugin I attached in #11817).

Shouldn't we be doing this in WP as well?

It basically goes:

 - if it's a page, then try a post meta
 - if it's search/404 request, then try a transient
 - if it's anything else, then try a transient

The plugin also handles conditional flushing of the cache based on whether or not the permalink and/or the label changed."	Denis-de-Bernardy
Future Releases	12934	Allow a menu to be added as a menuitem to be a submenu.	ryan	Menus	3.0	normal	normal	Future Release	enhancement	new		2010-04-08T21:55:32Z	2010-10-28T09:12:09Z	"Add capability to add a menu as a menuitem to be a submenu thus allowing multiple menu items to share the same submenus.

See reference in April 8 devchat:

https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2010-04-08&sort=asc#m106225"	mikeschinkel
Future Releases	11957	Change Admin Menu Save-State Rules	ryan	Menus		normal	normal	Future Release	enhancement	new	early	2010-01-20T18:04:19Z	2011-02-28T11:40:19Z	When we redid the menus in 2.7, we built in a save-state to keep open sections you had explicitly expanded until you explicitly closed it. I think it was a good experiment, and in some cases is helpful (like for people who are frequently accessing discussion settings or some such), but overall I think it adds to the problem of having too many menus expanded on a small screen pushing the lower menu items out of reach without scrolling. Mark and I have talked about various options for this, and we both agree that we should remove the save-state feature from the menu. So, the section you're in would stay open and highlighted, and if you opened another menu section to see the subs, if you had another menu open before, it would close. You could only ever have one section open at a time in addition to the one you're currently in. Maybe we could release the original save-state menus controls as a plugin in case there's anyone who prefers it that way. 	janeforshort
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	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	10743	WP rewrite rule bug with & in url path	ryan	Permalinks		normal	normal	Future Release	defect (bug)	new		2009-09-07T19:02:22Z	2010-04-04T07:26:19Z	"We've noticed a peculiar bug in the standard rewrite rules for wp if & is included in any url, as part of the path, not the query string.

EGs:
 * http://tekartist.org/&nbsp/anything
 * http://ma.tt/&blah/test

The rewrite rule serves the default page, without returning a 404.

My best guess at this time is that what is happening is that the inclusion of & in a rewritten path is actually seen as a query param (eg: treated as /index.php?&nbsp=...)"	stephdau
Future Releases	10988	http://domain.tld/keyword searches media library for matching items when logged in	ryan	Permalinks	2.8.4	normal	normal	Future Release	defect (bug)	reopened		2009-10-20T22:19:31Z	2010-05-08T20:51:49Z	"On my site i have a file in the media library called else.jpg. If I access http://lekv.de/else I get the expected 404. If I'm logged in in the backend however, I get redirected to the media item page of else.jpg (where I could download it). Also pretty permalinks have to be enabled using .htaccess files.


To reproduce, you have to create a media library item with a simple name, say else.jpg and upload it, using ""else"" as description in every form field. Then simply enable pretty urls, login into the backend and access http://domain.tld/else.

I hope, this is comprehensible.

My version is 2.8.4 DE-Edition."	squirrelpimp
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	10483	Change post_name's length from 200 to 400	ryan	Permalinks		low	minor	Future Release	enhancement	reopened	dev-feedback	2009-07-25T06:31:52Z	2012-06-18T17:43:31Z	"Hello, guys! Thank you very much for providing such a great piece of software! I love WordPress very much! :)

I use WordPress in Russian language and the URLs on my [http://www.ielnur.com blog] consist of Russian characters. There is a [http://www.ielnur.com/blog/2009/05/снова-бросить-курить-30-тидневное-испытание/ post] with not such a long URL in Russian, but since it gets encoded to special characters it becomes too long to get fit into `post_name` field of `post` table.

I've found what code needs to be changed to increase the length. I make these changes every time a new version is released. I think it would be better to submit a patch here so that others people can benefit from it and I will not need to make those changes every release.

I'm attaching the patch to this ticket and asking you to apply it to the code.

Thank you very much again, guys! You do a great job! :)

Cheers,
Elnur"	elnur
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	13365	WP_Query, author_name, and sticky posts	ryan	Query	2.9.2	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2010-05-12T06:09:42Z	2012-08-30T00:17:35Z	"I have a template which is being used as my front page on WP 2.9.2. In this template I setup my loop with the following code:

{{{
$postresults = new WP_Query();
$postresults->query(""author_name=frontpage&post_types=post&post_status=publish"");
while($postresults->have_posts()) { $postresults->the_post(); ?>
// etc...
}}}

I am not using the ""caller_get_posts=1"" option, but my sticky posts are still showing up in order with other posts rather than at the beginning. If I remove the ""author_name=frontpage"" the sticky posts will move back to the first items, however I am stuck with posts by authors I do not want. Using ""author=2"" results in the same behavior as using ""author_name""."	eryanv
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	11375	allow to disable the private status	ryan	Query	2.9	normal	normal	Future Release	enhancement	new	dev-feedback	2009-12-09T20:54:17Z	2013-01-14T13:27:48Z	"The private status generates all sorts of OR clauses in SQL queries, which is bad from a performance standpoint.

Blogs that do not have any private posts or pages should have the ability to disable the feature altogether, in order to optimize the SQL statements.

Adding an option in a Settings page arguably is plugin material, but WP doesn't currently allow to remove the status altogether.

Were it to be implemented, WP should keep a trace (in a transient) of the following:

{{{
$has_private_posts = (bool) $wpdb->get_var(""SELECT EXISTS 1 FROM $wpdb->posts WHERE post_status = 'private';"");
}}}

checking its value and disabling the type = private type accordingly in non-admin areas would significantly enhance the user experience for those who never use such things."	Denis-de-Bernardy
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	12779	Better support for custom post types in WP_Rewrite	ryan	Rewrite Rules		normal	normal	Future Release	enhancement	new		2010-03-30T20:04:30Z	2012-08-24T05:17:56Z	"See also #12605 and [13773].

We currently use bitmasks in WP_Rewrite, which we should remove and convert to an array of URL types that can be checked using in_array(). We currently do not use bitmask operations in WP_Rewrite that would make them preferable for use.

To currently use custom post types with endpoints, a plugin would need to do the following, from [comment:5:ticket:12605 dd32 in #12605]:
{{{
define('EP_WIKI', 131072); // 2^17. 2^13 is used by core.
register_post_type('wiki', array(
	'label' => __('Wiki'),
	'public' => true,
	'supports' => array('revisions', 'editor', 'title'),
	'permalink_epmask' => EP_WIKI,
	'hierarchical' => true
));
add_rewrite_endpoint('history', EP_WIKI);
}}}

In particular:
> Care would need to be taken that any custom endpoints are in {{{2^x}}} format, and not currently in use by any other plugins loaded.

This would need to be backwards compatible with the existing bitmasks. More or less, {{{WP_Rewrite::add_endpoint()}}} would need to still take bitmasks and convert them to the new format."	nacin
Future Releases	11931	Day/Month/Year Permalink Structure Fails in Archives	ryan	Rewrite Rules	2.8.6	normal	normal	Future Release	enhancement	new		2010-01-17T14:53:37Z	2010-06-23T17:02:55Z	"If you use a permalink structure with %day%/%monthnum%/%year% then the archives automatically become date/%day%/%monthnum%/%year%. Wordpress automatically makes the links to monthly archives date/01/2010 etc (which is good), but if you go to it you get a 404 not found.

Reproduce using for example /%post_id%/%postname%/%day%/%monthnum%/%year%/

I ""fixed"" it with this plugin I wrote, but it will probably fail when things like /page/2/ come into play (that wasn't really important yet). "	Frenzie
Future Releases	10980	DoS in wp-trackbacks	ryan	Security		normal	normal	Future Release	defect (bug)	reopened		2009-10-19T19:25:17Z	2009-10-21T15:42:30Z	"The exploit: http://codes.zerial.org/php/wp-trackbacks_dos.phps

Execution:

$ while /bin/true; do php test.php http://target.bom/wordpress; done
hit!
hit!
hit!
hit!
hit!
hit!
hit!
hit!
hit!
hit!

Notice: fputs(): send of 8192 bytes failed with errno=11 Resource
temporarily unavailable

down!!

Load average: 22.07, 15.18, 8.58 (on target server)

"	gomex
Future Releases	10267	Login form SSL is confusing	ryan	Security		normal	normal	Future Release	defect (bug)	new		2009-06-25T10:12:48Z	2009-11-24T15:56:01Z	"With ssl_admin off, and ssl_login on, the login form sends a secure POST request. But end-users can be confused into thinking that they're about to send a non-secure post unless they view the page's source code.

The attached patch enforces SSL on the form as well, to avoid this confusion.

Brought this up in IRC, and it gets +1 from Viper007Bond and DD32 as well."	Denis-de-Bernardy
Future Releases	11813	Post password stored as plaintext	ryan	Security	2.9.1	normal	normal	Future Release	defect (bug)	new		2010-01-07T17:33:10Z	2012-09-17T15:21:04Z	"When a user specifies a password for a protected post it's stored as plaintext in the database.  Considering the rate at which people recycle personal passwords, does this open a user's site to potential security risks?  

While not necessarily our responsibility, this would raise issues if they use the same password for a login and for their protected posts."	ericmann
Future Releases	13051	admin_url() and site_url() shouldn't need esc_url()	ryan	Security	3.0	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-04-19T16:57:13Z	2010-11-13T03:09:47Z	"I noticed that the 3.0 codeline includes the addition of esc_url() around admin_url() like:

esc_url(admin_url());

I believe that admin_url() and site_url() should be ""safe"" functions to use and should not need escaping. Perhaps they should call esc_url() internally?

I cannot think of a viable reason to allow unsafe results from admin_url() and site_url(), though perhaps there are some internationalization edge cases that I'm not aware of.

If you really need raw access to an unsafe value in wp_options, you can use get_option() to get to it.

Another issue to consider here is input validation and stripping before saving to these fields.

If this is approved in principle, I'd be happy to produce a diff against the current code base.

I think this is very important to address before 3.0 is released as it has a significant impact on theme and plugin developers."	alexkingorg
Future Releases	10237	Implement Content Security Policy to prevent XSS	ryan	Security	2.8	normal	normal	Future Release	feature request	new		2009-06-22T20:50:37Z	2012-06-20T16:12:36Z	"http://blogs.zdnet.com/security/?p=3654

 1. Here’s how Content Security Policy can provide a way for server administrators to reduce or eliminate their XSS attack surface. Website administrators specify which domains the browser should treat as valid sources of script.

 2. The browser will only execute script in source files from the white-listed domains and will disregard everything else, including inline scripts and event-handling HTML attributes. 
   - Note: event-handling is still enabled in CSP without using HTML attributes.

 3. Sites that never want to have JavaScript included in their pages can choose to globally disallow script."	Denis-de-Bernardy
Future Releases	10850	Make register_setting available on the front-end	ryan	Security	2.8.4	normal	normal	Future Release	feature request	new		2009-09-25T09:47:09Z	2009-09-25T09:47:09Z	"hi,

since 2.7.0 we have the function {{{ register_setting($option_group, $option_name, $sanitize_callback = '') }}} in ''/wp-admin/plugin.php'' to securely handle handed over $_POST variables in the admin menu.

afaik, besides of the usage of query_vars (which only work for $_GET variables) we have no counterpart to ''register_setting'' on the front-end. imho, we could increase the security and usability of forms and their variables if we would provide a similar functionality in ''wp-includes''.

what do you think?

greetz,
berny"	neoxx
Future Releases	12729	Fix [6326] - wp_unique_term_slug() when changing the parent	ryan	Taxonomy		normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-03-27T08:04:40Z	2013-06-07T19:23:18Z	"[6326] uses $args (as an array) when it appears it should use $term (an object).

It's never worked, so I'm hesitant to patch it as I imagine it might break something elsewhere in the taxonomy API.

Assigning to ryan for now, who authored the commit."	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	7559	strip_tags() breaks category names with left angle brackets	ryan	Taxonomy	2.6	normal	minor	Future Release	defect (bug)	reopened		2008-08-20T22:17:19Z	2010-07-01T17:44:25Z	"If you create a category named ""<something"", the category name doesn't show up on any of the category listings.  If you create a category named ""some<thing"" the category name shows up as ""some""."	squirreling
Future Releases	5034	Impossible to have duplicate category slugs with different parents	ryan	Taxonomy	2.3	high	normal	Future Release	feature request	new	dev-feedback	2007-09-21T19:29:20Z	2013-02-05T04:23:01Z	"I'm using Wordpress as a CMS tool where categories are used as macro level grouping.

Windows XP -> Utilities
Windows Vista -> Utilities

This is no longer possible with WP 2.3, which ignores parent category when testing whether a slug is unique."	snakefoot
Future Releases	4004	New filter for page title attribute in wp_list_pages output	ryan	Template	2.1.3	normal	normal	Future Release	enhancement	new		2007-03-20T22:45:17Z	2009-06-13T15:40:00Z	"While developing a new theme I realised that the default title attribute for wp_list_pages was to just to reuse the title of the page with no option to change it. Not exactly useful...

I therefore propose a new filter on the title attribute to allow a theme/plugin developer the option of changing the text to whatever they like.

The new filter takes the title attribute and the $page variable as well, so that any post/page related information can also be used... for example the post meta."	Dickie
Future Releases	11905	trac spam	ryan	WordPress.org site		normal	normal	WordPress.org	defect (bug)	reopened		2010-01-15T13:05:08Z	2013-04-21T09:15:45Z	http://core.trac.wordpress.org/ticket/9534#comment:7	scribu
Future Releases	13576	wordpress.org themes list, sidebar broken in IE7	ryan	WordPress.org site		normal	normal	WordPress.org	defect (bug)	new		2010-05-27T14:49:20Z	2012-08-10T18:25:26Z	"wordpress.org themes list
the sidebar in IE7/IE8 is displayed AFTER the themes, Firefox ok."	maurizio04
Future Releases	12696	Add ordering support to plugins_api() when filtered on tag or search term	ryan	WordPress.org site		normal	normal	WordPress.org	enhancement	new		2010-03-24T23:05:09Z	2011-06-07T14:49:00Z	"It would be awesome if you could pass an ordering parameter to plugins_api() that would allow you to return a list of filtered plugins in a specific order.

I'd love to be able to use the API to return a list of the most popular / newest / recently updated plugins on the repo that contain the tag ""buddypress"".

Something like this would be awesome:

{{{
$plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'page' => 1, 'order' => 'popular' );
}}}

Even better, also allow search filtering:

{{{
$plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'search' => 'album', 'page' => 1, 'order' => 'popular' );
}}}

I'd be happy to implement this if I can get access to the API source on WordPress.org."	apeatling
Future Releases	11898	Pagination For Browse Source in Plugin Trac	ryan	WordPress.org site		normal	normal	WordPress.org	enhancement	new		2010-01-14T23:42:38Z	2010-01-15T16:53:59Z	"When you view Browse Source in Plugin Trac it lists 7,000 plugins. This take a long time to load and isn't readable. This page needs pagination or something else.[[BR]]
[[BR]]
Related: http://trac.edgewall.org/ticket/6101[[BR]]
[[BR]]
This was talked about breifly during the dev meeting on January 14th, 2010: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2010-01-14#m56068"	dancole
Future Releases	12475	Method to prune/leave feedback in Kvetch	ryan	WordPress.org site		normal	normal	WordPress.org	feature request	new		2010-03-02T17:12:25Z	2010-03-02T17:12:25Z	"I just saw two items about how it would be nice if upgrades were easier and if there was an automatic upgrader, and it got me thinking that there's no way to leave feedback or flag it if you're logged in.

It would be nice if there was some way to either leave feedback for when a Kvetch is no longer ""valid"" (for lack of a better term) because something has been implemented to address it, or to flag it for someone else to look at it and decide that it should be removed.

This could also be useful if a spam item was displayed, or if an offensive message was left."	ninjaWR
Future Releases	13780	Twenty Thirteen: WordPress Version Requirement Support	ryan	WordPress.org site		high	normal	WordPress.org	feature request	new		2010-06-08T04:15:45Z	2013-06-12T20:14:56Z	"Right now, there seems to be no way to add a minimum required version to a themes style.css.

This should be used for the automatic update of themes build into WordPress. The theme update should only be applied after WordPress is updated to at least that version."	kretzschmar
Future Releases	12336	WP.org Profiles - Trac Replies are not reported	ryan	WordPress.org site		normal	normal	WordPress.org	feature request	new		2010-02-22T19:02:51Z	2010-02-22T19:08:48Z	Since WP.org Profiles already has forum post creations and replies, and Trac ticket creations, it makes sense to add the Trac replies as well.	archon810
Future Releases	12313	WP.org Profiles should add an RSS feed	ryan	WordPress.org site		normal	normal	WordPress.org	feature request	new		2010-02-21T01:01:52Z	2010-02-22T19:09:21Z	"I'm not sure where to report feature requests for WP.org Profiles so I'll do it here.

Considering the Profiles page http://profiles.wordpress.org/archon810 includes the Trac activity (unlike http://wordpress.org/support/profile/276841 which doesn't, though, it's also useful because it does include replies by others to my favorite topics), it'd be awesome to have an RSS feed for this Profile activity so that it can be used in someone's RSS reader or in my FriendFeed or Lifestream.

This may be a BuddyPress request, but since WP.org uses it, I'd say this ticket has merit either way."	archon810
Future Releases	10699	Password Expose Bug in XML-RPC Debugging	ryan	XML-RPC		normal	normal	Future Release	defect (bug)	new	close	2009-08-29T01:46:43Z	2012-09-17T06:20:27Z	"Though this may not effect many users, I was testing something through xmlrpc with logging enabled and came across something that might create a security problem. 

If xmlrpc logging is enabled WP logs the password from the request struct in an unencrypted format. 

Now I understand that not many will open up xmlrpc logging on production blogs, could it be possible that WP just strikes out the password before logging it to the file as it is always the third param so easy to do that, this is because people who might have xmlrpc logging enabled may not change the default log filename and location so anyone can simply run a robot to check for http://blogurl.com/xmlrpc.log and farm passwords (now this may not affect blogs that have WP installed in root since it writes to ../xmlrpc.log, so essentially outside the www access dir, but blogs with WP installed in sub directories will be affected). 

Don't know how critical this is as users have to manually edit the file to enable xmlrpc logging so it might be a non critical bug."	keithdsouza
Future Releases	19915	Add unit tests for AtomPub API	rmccue	AtomPub		normal	normal	Awaiting Review	enhancement	new		2012-01-28T16:25:15Z	2012-09-17T05:52:57Z	"Apologies if this is a duplicate, I couldn't find any.

The AtomPub API is hideously under-tested. Since it's a part of WordPress that doesn't get touched often, it's also one of the most crucial components that needs testing.

I'm working on [https://github.com/rmccue/Gorilla a test runner called Gorilla], which is designed as a replacement for the APE (Atom Protocol Exerciser). This will have a port of all the APE unit tests to PHP, and I'm also going to start writing some new ones for all the new APIs that are being added in #18430, #18431, #18432 and #18433.

These are specifically designed to be able to be independent of Gorilla, so that it will be easy to bring into a normal PHPUnit test suite, and hopefully will be able to run as part of the normal WordPress unit test suite. (Although they'll still need some components of Gorilla to work)

(This is filed under Unit Tests, but AtomPub might be a better component)"	rmccue
Future Releases	15847	Add filter in wp_insert_attachment for $data	rhundesign	Plugins	3.0.3	normal	normal	Future Release	enhancement	assigned		2010-12-16T15:49:24Z	2012-03-21T10:26:16Z	Pretty self-explanatory, patch attached.	pampfelimetten
Future Releases	3329	Need to strip % from the auto-permalink in the editor.	pishmishy*	Permalinks	2.0.5	normal	normal	Future Release	defect (bug)	accepted		2006-11-04T20:41:06Z	2013-01-17T04:11:19Z	"I made an article with ""x = 18,98 * y - %10"" as title, and this generated http://www.example.com/blog/2006/11/03/x-1898-y-%10/ which doesn't work."	Heyneken
Future Releases	5235	Add Pre-flight checks to install	pishmishy*	Upgrade/Install		normal	normal	Future Release	enhancement	accepted	dev-feedback	2007-10-19T17:37:56Z	2010-01-05T21:10:24Z	"It would be nice for the installer to do some pre-flight checks and warn the users of things that will stop WordPress working (either completely or partially)

Candidates for the pre-flight checks:
 * Functions which may be disabled - See #3014
 * Memory limit #5235
"	westi
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	18301	Activating a new theme on multisite is very long-winded	PeteMall*	Network Admin	3.1	normal	normal	Future Release	enhancement	accepted		2011-07-30T23:38:48Z	2012-12-31T18:25:57Z	"Scenario:

I've just uploaded a new theme to my theme directory and I now want to activate it on a site. I head to the Appearance › Themes menu for that site and, whoops, I forgot to activate it on the network first. Now I need to:

1. Click my name in the header
2. Click Network Admin in the dropdown menu
3. Click Sites
4. Find the site and click Edit
5. Click Themes

From there I can enable the theme.

We're not done yet though. We need to traverse a minimum of two screens to get back to the Themes menu of the site (even more if the admin bar isn't enabled) in order to activate it.

Two things would make this process easier:

1. A link from the Themes screen to the Themes tab of the site in network admin, so five clicks become one.
2. The ability to activate a theme from the Themes tab of the site in network admin.
"	johnbillion
Future Releases	22981	Tweets import plugin tracking ticket	PeteMall*	Plugins		high	normal	WordPress.org	task (blessed)	accepted		2012-12-17T18:43:42Z	2013-05-28T20:55:01Z	"This ticket is to track the development of a plugin that can import tweets from a downloaded twitter.com archive. Presumably, such a plugin would be added to the importers list on wp-admin/import.php.

Trac is best when it is used to discuss implementation. If you want to discuss the general idea, please do so on [http://make.wordpress.org/core/2012/12/16/antsy-for-3-6-to-start-and-need-a/ make/core].

Some initial thoughts on implementation:
 * It should use the JSON-formatted data that comes with a downloaded tweet archive. The importer should take the entire zip, extract it, and loop through the monthly files. Anything more is an unnecessary burden on the user.
 * The plugin should import the tweet as actual content. A filter is good idea, if someone wishes to toggle this to instead insert links to tweets (and thus rely on oEmbed). It should also store the JSON-serialized array of data (directly from 1.1 of Twitter's API) in postmeta.
 * It should import posts as a post format. Status makes the most sense; 'link' could also work for links, then there's also 'aside'. The post format to use should be filterable on a tweet-by-tweet basis. The post type to use should be filterable, as a 'tweet' type may be desired.
 * It should handle importing an archive over an existing archive, by looking for the existing tweet (probably IDs as a meta key). I don't think deleted tweets should be removed in this process, though.
 * Remember that tweet IDs are going to be bigger than 32-bit integers, so they must be treated as strings, and we should not try to set a post ID as we might with other importers. This importer should be tested on a 32-bit environment.

Beyond that, there are other ""nice to haves"" that would likely be left to plugins of this plugin, given they are beyond the standard role of an importer. Beau Lebens, for example, has done some/all of this already:
 * Tagging based on hashtags, and a separate mentions and/or in-reply-to taxonomy.
 * Filtering over raw (no-HTML) content to add things like links to hashtags, links in tweets, etc., on display, rather than doing all of this on save. (Should a hashtag link go to the internal tag, or to twitter.com? Maybe the internal tag's description links to twitter.com?)
 * A cron to import new tweets using the same importing methods.

One thing I will suggest: decisions, not options. Note I said ""filter"" a bunch of times, but never the word ""option."" Not that there won't be a need for any user decision here, but we should make a plugin that works well for the common use cases, and leave the rest to other enterprising developers.

Side note: I am working on acquiring a namespace for the Twitter importer in the wordpress.org plugin repository."	nacin
Future Releases	18188	Make it easier to go between Dashboard and site edit pages	PeteMall	Network Admin	3.1	normal	normal	Future Release	enhancement	reopened		2011-07-20T19:22:16Z	2012-04-18T21:01:14Z	"Each site in a network install has a Dashboard and a set of ""edit"" pages (Info/Users/Themes/Settings).

The ""edit"" page URLs are '''/wp-admin/network/site-''settingsName''.php?id=''id''''' where ''settingsName'' is '''info''', '''users''', '''themes''', or '''settings'''. The Dashboard URL is '''/''siteName''/wp-admin/''' where ''siteName'' is, I think?, the site's '''Path''' field as shown in '''/wp-admin/network/site-info.php?id=''id''''' but without the leading and trailing slashes.

The problem is if I am in the ""edit"" pages and want to go to the site's dashboard, I have to click on '''Sites''', then hunt down the site in the list, then click '''Dashboard''' while hovering the mouse over the site's row. I have a similarly convoluted process to get from a Dashboard to the ""edit"" pages.

Does this need to be so complicated? It would be nice for network admins to see links on every Dashboard or ""edit"" page that allows the user to go back and forth between the two easily.

Or even better, how about making the ""edit"" pages just show up as additional items in the Dashboard?"	novasource
Future Releases	22704	Automatic Core Updates	pento	Upgrade/Install	3.5	normal	normal	Awaiting Review	feature request	assigned	dev-feedback	2012-12-03T22:05:04Z	2013-01-14T18:12:02Z	"It's time to think about automatic updates for WordPress Core. Plugins and Themes are a totally different ball game, so it's probably best to leave them for the moment. Currently, I'm thinking it would be a good idea to release this in stages (some of which may be combined, just spelling them out):

- SVN updates in trunk installs
- SVN updates in branch installs
- Opt-in updates in stable installs
- Opt-out updates in fresh installs
- Opt-out updates in all installs
- Remove option for opting out

I'd like to see SVN updates go into 3.6 early, so we can quickly get a good idea of compatibility issues that we're likely to run into when we get to beta.

Finally, are there any features we should be looking at adding to the upgrader for this? More sanity checking, notifications, other?"	pento
Future Releases	21411	Current Local Time for Port-au-Prince, Haiti is incorrect.	patrick@…	Date/Time	3.4.1	normal	minor	Awaiting Review	defect (bug)	new	close	2012-07-29T00:44:29Z	2013-06-13T00:40:26Z	"When the Port-au-Prince Timezone is selected via wp-admin/options-general.php the Local Time is one hour behind. Please see [http://wwp.greenwichmeantime.com/time-zone/caribbean/haiti/time-haiti/] for the correct local time.

Yes, the problem occurs even when all plugins are deactivated and the default theme is activated. "	pnommensen
Future Releases	21455	HiDPI (retina) theme custom backgrounds	Otto42	Appearance		normal	normal	Future Release	feature request	assigned		2012-08-02T17:07:06Z	2012-09-15T05:22:40Z	"We should support HiDPI custom backgrounds.

This will be a bit easier than custom headers, #21389, as we can do a media query in _custom_background_cb(). Worth noting that we will still need to solve some aspect of retina uploads, #21038."	nacin
Future Releases	21389	Retina theme custom headers	Otto42	Appearance		normal	normal	Future Release	feature request	assigned		2012-07-25T19:40:56Z	2013-06-14T15:56:11Z	We should support retina custom headers. Not sure how — ideas welcome.	nacin
Future Releases	21038	Provide an option for creating 2x images of user content (for Retina Displays)	Otto42	Media	3.4	normal	normal	Future Release	feature request	assigned		2012-06-21T13:13:13Z	2012-09-06T17:02:33Z	"Providing high-res images for Retina enabled devices like iPad, iPhone or Macbook Pro is rather easy with retina.js (http://retinajs.com/).

The only thing needed is a @2x version of all images. It would be nice to have an option on the image uploader to enable generation of this images.

This should be rather easy to implement, it would make life much easier."	twam
Future Releases	17595	Cannot subscribe by email to some tags on wp.org	Otto42	WordPress.org site		normal	normal	WordPress.org	defect (bug)	assigned		2011-05-28T04:34:29Z	2011-05-28T05:24:18Z	"To reproduce: 

- Visit http://wordpress.org/tags/disable-comments when logged in
- Click on ""Subscribe to Emails for this Tag""

After reload the link should now read ""Unubscribe to Emails for this Tag"", but it hasn't changed, and the user does not receive emails.

The problem appears to be when people use tags that include a space, i.e., ""disable comments"".
"	solarissmoke
Future Releases	24397	Embiggen the linked WordPress og:image	Otto42	WordPress.org site		normal	normal	WordPress.org	enhancement	assigned		2013-05-23T18:14:33Z	2013-05-23T18:42:00Z	"Looks like !WordPress.org blog posts currently use [http://wordpress.org/about/images/logo-blue/blue-l.png a 150x150 px image] as an Open Graph protocol image to sexify shared links on Facebook, Twitter, Windows 8, LinkedIn, etc.

Facebook has a minimum image dimension requirement of 200x200 px to optimize for selecting an image that works in a variety of display scenarios including HiDPI. Current image is under that minimum dimension. Facebook supports an image up to 5 MB in filesize. Twitter supports up to 1 MB in filesize.

Bump up the size of the default [http://wordpress.org/about/logos/ WordPress logo] used as an og:image on !WordPress.org blog and elsewhere to something huge (ideally > 1500x1500 px) for maximized display opportunities for !WordPress.org link summaries displayed on other sites.

Example URL:
http://wordpress.org/news/2013/04/save-the-date-may-27/"	niallkennedy
Future Releases	21842	Diffrerent Custom Taxonomy Unable to Have Same Term Name  in Version 3.4.2	oneTarek	Taxonomy	3.4.2	normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2012-09-08T09:27:28Z	2012-09-14T23:47:16Z	"Before WordPress version 3.4.2 We know that WordPress does not support same word as category and tags. Assume you have a category named ""iPhone"" and it's slug is 'iphone' and now you want to add a new tag named ""iPhone"" , in this case tag slug will be 'iphone-2'. But if you have a custom taxonomy ""Device"" then the slug will be 'iphone' same as category ""iphone"". It means WordPress did not support same category and tag but can be same with any custom taxonomy. I tested many times this case.

But today after updating <a href=""http://onetarek.com""><strong>My WordPress Blog</strong></a> to version 3.4.2 I found a mistake on it. I have 3 custom taxonomy. 'Type', 'Brand' and 'OS' . Before WP 3.4.2 I was able to use same word as Category and Type and also same slug for those. But now in version 3.4.2 when I am adding new terms It is getting slug with extra number 2. Example: I have a Category 'Apple' it's slug 'apple'. Now I am trying to add a 'Brand' taxonomy term 'Apple', the slug is being created 'apple-2'. But this problem was not in before WP 3.4.2"	onetarek
Future Releases	15414	Rework admin searches and make them compatible with no-js again	ocean90*	Administration	3.1	normal	normal	Future Release	defect (bug)	accepted		2010-11-13T13:53:19Z	2010-12-10T19:36:56Z	"I'm working on #15355 and found some problems with the searches. I will use this ticket to add the patches, one patch for each problem which I have found.

A list with what it not working:
 - ~~Comments search doesn't work without JS~~ fixed
 - ~~Users search doesn't work with and without JS~~ fixed
 - http://grab.by/7nC2 I like the idea with the new tab ""Search Results (1)"", but you will see it only in no-js version and only for themes and plugins search. We should add it for all searches, AJAX search and with no grey bgcolor to be consistent. '''Or''' we must respect the active tab like we did it on comments search, so if 'Sticky' tab is active search only through sticky posts and not all as it is yet. Consistent is the word here.
- Behaviour after a search without any results: With JS it's an empty table and with no-js we have the message ""No xxx found."""	ocean90
Future Releases	19499	Allow wp_nav_menu to return just the links (no <li> tags)	nohalfpixels	Menus	3.2.1	normal	normal	Awaiting Review	enhancement	new	reporter-feedback	2011-12-10T12:15:35Z	2011-12-10T17:44:37Z	"every now and again i find im in the need of the wp_nav_menu function where i only want a list if links, not the outer ul, or the li tags.

there is already scope to remove the outer ul.

but no support for removing the <li> tags from the returned results.

at present i have to do this:


{{{
$foot_nav = wp_nav_menu( array( 'container' => '', 'echo' => '0', 'theme_location' => 'footer_menu' ) );
$foot_nav2 = preg_replace( array( '#^<ul[^>]*>#', '#</ul>$#' ), '', $foot_nav );
$foot_nav2 = preg_replace( array( '#<li[^>]*>#', '#</li>$#' ), '', $foot_nav2 );
echo $foot_nav2;
}}}



this isnt very clean, it would be nice to just be able to pass a parameter the wp_nav_menu function which just returns the links.

i propose something like:


{{{
'return_links' => true,
}}}



the main reason for this is styling centered links in the footer.

its much easier to just center links than it is to center a <ul> and results in much cleaner html with less dom elements."	nohalfpixels
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	20854	functions.php on line 155 ?	Nikolaos Raftopoulos	Multisite	3.3.2	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-06-06T12:45:29Z	2012-07-31T02:42:37Z	"In my network dashboard I get the following error message : 


Warning: number_format() expects parameter 1 to be double, string given in /home/tklighth/public_html/wp-includes/functions.php on line 155"	leondari
Future Releases	21140	"""Display name publicly as"" setting not set until a change is made in the setting"	nickharambee	Users	3.4	normal	normal	Awaiting Review	defect (bug)	new	has-patch	2012-07-02T21:29:48Z	2012-07-02T22:37:46Z	"I have found this issue with several users that I have set up on my site.  The default value for ""Display name publicly as"" is the first name of the user when creating a new user, or at least that is what shows in the ""Display name publicly as"" drop-down menu.  However, when creating a new user, the full name, i.e. the first and last name is what displays publicly.  In order to get only the first name to display publicly I need to set the ""Display name publicly as"" option to another option, save changes, and then reset it to just the first name, and save changes again.

Surely, if it is the first name that shows in the drop-down menu, it should be the first name that actually displays publicly, without having to go through this rather strange process?

I am using the latest version of Buddypress (1.5.6) as well as several other plugins.  I have not tried disabling all of these."	nickharambee
Future Releases	11740	Sorting tags and towns does not work well for utf-8	nbachiyski	I18N	2.9	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-01-06T12:42:24Z	2012-09-02T14:25:29Z	"There are problems with sorting special Czech characters:

1) Options - General - Timezone selection.

Evropa (Europe)
First item should be Amsterdam, but instead of it there is ""Řím"" (Rome in Czech). And this is not right, character Ř should be between R and S.

2) Editing posts - Select from most used tags.

You can create tags ""Rome"", ""Amsterdam"" and ""Řím"".
Tags are also sorted in a bad way, first is ""Řím"".
It is very problematic for Czech users when there are many tags, because it does not help them..."	pavelevap
Future Releases	13069	Use GlotPress list of locales instead of the one in ms.php	nbachiyski	I18N	3.0	high	minor	Future Release	defect (bug)	new		2010-04-21T11:45:41Z	2010-10-28T07:18:48Z	GlotPress keeps track of all languages and locales with some information about them. The list there is also well maintained.	nbachiyski
Future Releases	12905	the_title_attribute() is hard to internationalize	nbachiyski	I18N	3.0	normal	normal	Future Release	defect (bug)	new		2010-04-07T19:47:17Z	2010-10-01T23:29:44Z	"To internationalize the output of the_title_attribute, you have to go through some hoops.

{{{
printf( esc_attr__( 'Permanent link to %s' ), the_title_attribute( 'echo=0' ) );
}}}

Adding a 'formatted' argument to the args array would clean it up a little.

{{{
the_title_attribute( array( 'formatted' => __( 'Permanent link to %s' ) ) );
}}}

Even better would be if we could auto detect what the first parameter was.

{{{
the_title_attribute( __( 'Permanent link to %s' ) );
}}}

It'd require the function to try and detect if it's first argument were a sprintf format.  Maybe: look for %, if found, does sprintf return a string, if so, go for it.

Attached is one way to implement."	mdawaffe
Future Releases	11226	Month name declension case	nbachiyski	I18N	2.9	low	minor	Future Release	enhancement	new		2009-11-22T13:13:43Z	2012-10-19T22:41:46Z	"As I've reported previously, in order to fully translate WordPress into Polish (and probably many more languages), dates have to be declended. This was fixed in #9396, however proper translation into Polish still cannot be accomplished.

You see, the ""January 2009"" is something else for


{{{
""View posts published in January 2009""
}}}


and just


{{{
""January 2009""
}}}


In the former case, it's a locative. In the latter, it's simply a genitive. What needs to be done in order to fix this is passing some kind of information to the date_i18n filter, informing it of the case.

I suggest passing the declension case information (whether it's genitive, locative or something else). That should do it. :)"	waclawjacek
Future Releases	10005	"Some strings need ""no HTML entities"" translator comments"	nbachiyski	I18N	2.7.1	normal	minor	Future Release	enhancement	reviewing		2009-06-02T10:19:50Z	2009-11-23T21:30:48Z	"I've been putting a specific set of custom comments in my PO for some time now, and since WP is now able to handle translator comments very graciously, I think it would be nice to switch them over there.

The following strings need to have an indication warning translators against the inclusion of HTML entities within their translation, because of where the strings are user (RSS feeds, e-mail...). For instance, ""Protected Comments: "" should be translated to ""Commentaires protégés&nbsp;: "", but since it is used in feeds, it breaks them...

Suggestions comment: ""Do not add HTML entities (&nbsp;, etc): used in [context]"".

Here they are (sorry, raw list out of my PO file).

Used in feeds:
  - ""Comments on: %s"", wp-includes/feed-atom-comments.php:19 and wp-includes/feed-rss2-comments.php:22
  - ""By: %s"", wp-includes/feed-atom-comments.php:56 and wp-includes/feed-rss2-comments.php:48
  - ""Protected Comments: Please enter your password to view comments."", wp-includes/feed-rss2-comments.php:56


Used in e-mail:
  - ""Your new WordPress blog has been successfully set up at: ..."", wp-admin/includes/upgrade.php:229
  - ""New comment on your post #%1$s \""%2$s\"""", wp-includes/pluggable.php:968
  - ""Author : %1$s (IP: %2$s , %3$s)"", wp-includes/pluggable.php:970 and wp-includes/pluggable.php:1072 
  - ""E-mail : %s"", wp-includes/pluggable.php:971 and wp-includes/pluggable.php:1073
  - ""URL    : %s"", wp-includes/pluggable.php:972, wp-includes/pluggable.php:983, wp-includes/pluggable.php:993, wp-includes/pluggable.php:1059, wp-includes/pluggable.php:1066 and wp-includes/pluggable.php:1074
  - ""Whois  : http://ws.arin.net/cgi-bin/whois.pl?queryinput=%s"" and wp-includes/pluggable.php:973 and wp-includes/pluggable.php:1075
  - ""Comment: "", wp-includes/pluggable.php:974 and wp-includes/pluggable.php:1076
  - ""You can see all comments on this post here: "", wp-includes/pluggable.php:975
  - ""[%1$s] Comment: \""%2$s\"""", wp-includes/pluggable.php:977
  - ""New trackback on your post #%1$s \""%2$s\"""", wp-includes/pluggable.php:980
  - ""Website: %1$s (IP: %2$s , %3$s)"", wp-includes/pluggable.php:982 and wp-includes/pluggable.php:992
  - ""Excerpt: "", wp-includes/pluggable.php:984 and wp-includes/pluggable.php:994
  - ""You can see all trackbacks on this post here: "", wp-includes/pluggable.php:985
  - ""[%1$s] Trackback: \""%2$s\"""", wp-includes/pluggable.php:987
  - ""New pingback on your post #%1$s \""%2$s\"""", wp-includes/pluggable.php:990
  - ""You can see all pingbacks on this post here: "", wp-includes/pluggable.php:995
  - ""[%1$s] Pingback: \""%2$s\"""", wp-includes/pluggable.php:997
  - ""Delete it: %s"", wp-includes/pluggable.php:1000 and wp-includes/pluggable.php:1081
  - ""Spam it: %s"", wp-includes/pluggable.php:1001 and wp-includes/pluggable.php:1082
  - ""A new trackback on the post #%1$s \""%2$s\"" is waiting for your approval"", wp-includes/pluggable.php:1056
  - ""Website : %1$s (IP: %2$s , %3$s)"", wp-includes/pluggable.php:1058 and wp-includes/pluggable.php:1065
  - ""Trackback excerpt: "", wp-includes/pluggable.php:1060
  - ""A new pingback on the post #%1$s \""%2$s\"" is waiting for your approval"", wp-includes/pluggable.php:1063
  - ""Pingback excerpt: "", wp-includes/pluggable.php:1067
  - ""A new comment on the post #%1$s \""%2$s\"" is waiting for your approval"", wp-includes/pluggable.php:1070
  - ""Approve it: %s"", wp-includes/pluggable.php:1080
  - ""Currently %s comment is waiting for approval. Please visit the moderation panel:"", wp-includes/pluggable.php:1084
  - ""[%1$s] Please moderate: \""%2$s\"""", wp-includes/pluggable.php:1088
  - ""Password Lost and Changed for user: %s"", wp-includes/pluggable.php:1114
  - ""[%s] Password Lost/Changed"", wp-includes/pluggable.php:1115
  - ""New user registration on your blog %s:"", wp-includes/pluggable.php:1135
  - ""Username: %s"", wp-includes/pluggable.php:1136,  wp-includes/pluggable.php:1144
  - ""E-mail: %s"", wp-includes/pluggable.php:1137
  - ""[%s] New User Registration"", wp-includes/pluggable.php:1139
  - ""Password: %s"", wp-includes/pluggable.php:1145
  - ""[%s] Your username and password"", wp-includes/pluggable.php:1148




Used in visual editor (entities break it):
  - ""Edit Image"", wp-includes/js/tinymce/langs/wp-langs.php:421
  - ""Delete Image"", wp-includes/js/tinymce/langs/wp-langs.php:422


Used in an alert() message:
  - ""Enter a word to look up:"", wp-includes/script-loader.php:76


Obviously these were marked for my locale's need, I think all the strings pertaining to these context should be properly commented about this.

Hopefully it is not too late (and is quick enough) for inclusion with 2.8.

"	xibe
Future Releases	6425	Support for RTL in feeds	nbachiyski	I18N		normal	normal	Awaiting Review	enhancement	assigned	close	2008-03-27T20:56:51Z	2012-02-08T06:07:07Z	"In the current state of most Feed readers, the only surefire way to make RTL content display properly is to have directionality enforced inside the content - that is, either with {{<div dir=""rtl"">}}} tags inside CDATA or with Unicode directionality characters (for e.g., RLE and PDF, or &#8235; and &#8236;, or U+202B and U+202C.) for excerpts or titles.

While we currently have pretty good support for RTL languages, there is no support for RTL in feeds - all is left up up to the feed reader.

I suggest adding a mechanism to automatically insert these tags/characters for blogs that have text_direction set to RTL - much in the same way RTL css style sheets are loaded for these blogs.

I have attached a patch that modifies the feed templates to insert these tags/characters. Note that there is no checking of blog directionality here - this is just an example of how to enforce RTL in feeds, not how to enforce it conditionally.

This relate to a previous ticket I submitted (#5517), regarding adding an option to set the feed language - which currently just defaults to EN. Certain feed readers know to display RTL text in proper directionality according to feed language (for e.g., feeds that have their feed language set to HE (Hebrew), will get displayed from Right to Left). While setting feed language is not a comprehensive solution, it is a step in the right direction."	RanYanivHartstein
Future Releases	12477	Search with special characters and similar terms	nbachiyski	I18N		normal	normal	Future Release	feature request	new		2010-03-02T17:42:46Z	2010-03-24T10:25:15Z	"I did:Tried searching for terms Metis and Métis

I saw:Those two searches turned up different sets of results.

I expected:The same set of search results, or at least everything when
I searched for Metis.

Can search be smarter when special characters are involved?"	mrroundhill
Future Releases	4116	wp_texturize to defect certain links in comments and on page	Nazgul	Formatting	2.2.1	normal	normal	Future Release	defect (bug)	reopened	needs-unit-tests	2007-04-09T13:29:33Z	2010-11-23T04:53:07Z	"the wp_texturize() function in formatting.php (includes) of wordpress breaks links of the domain format (number)x(number). 

For example, a comment left by a domain such as www.h4x3d.com, which includes the (4)x(3) in the domain name, renders to www.xn--h43d-rma.com. This breaks the link.

It does occur on the page, but also with in the page comments. 
It does also occur when the text with the special combination is not a link, but plain text."	h4x3d
Next Release	24210	Issues found using a static analysis tool	nacin*	General		normal	normal	3.6	defect (bug)	accepted		2013-04-28T06:16:09Z	2013-05-07T16:35:03Z	"These all look like valid, but minor, issues:
{{{
--------------------------------
File       : wp-includes/class-json.php:495
Reason     : UnknownFunction
Snippet    : class_name($var)
Line       : : new Services_JSON_Error(class_name($var).

--------------------------------
File       : wp-includes/SimplePie/Locator.php:94
Reason     : RequiredAfterOptionalParam
Snippet    : $type = SIMPLEPIE_LOCATOR_ALL
Line       : public function find($type = SIMPLEPIE_LOCATOR_ALL, &$working)

--------------------------------
File       : wp-includes/ID3/module.tag.id3v2.php:433
Reason     : TooFewArgument
Snippet    : substr($footer[5])
Line       : $id3_flags = ord(substr($footer{5}));

--------------------------------
File       : wp-includes/ID3/module.tag.id3v2.php:1586
Reason     : StatementHasNoEffect
Snippet    : $frame_ownerid == '';
Line       : $frame_ownerid == '';

--------------------------------
File       : wp-includes/ID3/module.audio.mp3.php:37
Reason     : TooManyArgument
Snippet    : $this->getOnlyMPEGaudioInfoBruteForce($this->getid3->fp, $info)
Line       : $this->getOnlyMPEGaudioInfoBruteForce($this->getid3->fp, $info);

--------------------------------
File       : wp-includes/SimplePie/Misc.php:127
Reason     : TooManyArgument
Snippet    : SimplePie_Misc::entities_decode(end($attribs[$j]), 'UTF-8')
Line       : $return[$i]['attribs'][strtolower($attribs[$j][1])]['data'] = SimplePie_Misc::entities_decode(end($attribs[$j]), 
'UTF-8');
}}}

Resolved:
{{{
--------------------------------
File       : wp-includes/class-wp-walker.php:118
Reason     : RequiredAfterOptionalParam
Snippet    : $depth = 0
Line       : function display_element( $element, &$children_elements, $max_depth, $depth=0, $args, &$output ) {

--------------------------------
File       : wp-includes/comment-template.php:1298
Reason     : RequiredAfterOptionalParam
Snippet    : $depth = 0
Line       : function display_element( $element, &$children_elements, $max_depth, $depth=0, $args, &$output ) {

--------------------------------
File       : wp-includes/deprecated.php:802
Reason     : RequiredAfterOptionalParam
Snippet    : $echo = false
Line       : function get_author_link($echo = false, $author_id, $author_nicename = '') {

--------------------------------
File       : wp-includes/deprecated.php:1709
Reason     : TooManyArgument
Snippet    : get_the_content($more_link_text, $stripteaser, $more_file)
Line       : $content = get_the_content($more_link_text, $stripteaser, $more_file);

--------------------------------
File       : wp-signup.php:493
Reason     : RequiredAfterOptionalParam
Snippet    : $user_name = ''
Line       : function confirm_blog_signup($domain, $path, $blog_title, $user_name = '', $user_email = '', $meta) {

--------------------------------
File       : wp-signup.php:493
Reason     : RequiredAfterOptionalParam
Snippet    : $user_email = ''
Line       : function confirm_blog_signup($domain, $path, $blog_title, $user_name = '', $user_email = '', $meta) {

--------------------------------
File       : wp-includes/widgets.php:76
Reason     : RequiredAfterOptionalParam
Snippet    : $id_base = false
Line       : function WP_Widget( $id_base = false, $name, $widget_options = array(), $control_options = array() ) {

--------------------------------
File       : wp-includes/widgets.php:93
Reason     : RequiredAfterOptionalParam
Snippet    : $id_base = false
Line       : function __construct( $id_base = false, $name, $widget_options = array(), $control_options = array() ) {

--------------------------------
File       : wp-includes/post.php:4789
Reason     : RequiredAfterOptionalParam
Snippet    : $deprecated = ''
Line       : function _future_post_hook( $deprecated = '', $post ) {

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:173
Reason     : RequiredAfterOptionalParam
Snippet    : $start = 0
Line       : function _rows( $taxonomy, $terms, &$children, $start = 0, $per_page = 20, &$count, $parent = 0, $level = 0 ) {

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:173
Reason     : RequiredAfterOptionalParam
Snippet    : $per_page = 20
Line       : function _rows( $taxonomy, $terms, &$children, $start = 0, $per_page = 20, &$count, $parent = 0, $level = 0 ) {

--------------------------------
File       : wp-includes/rewrite.php:92
Reason     : TooManyArgument
Snippet    : remove_action($hook, $hook, 10, 1)
Line       : remove_action($hook, $hook, 10, 1);

--------------------------------
File       : wp-admin/includes/user.php:350
Reason     : TooManyArgument
Snippet    : delete_user_setting('default_password_nag', $user_ID)
Line       : delete_user_setting('default_password_nag', $user_ID);

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:159
Reason     : TooManyArgument
Snippet    : $this->single_row($term, 0, $taxonomy)
Line       : $out .= $this->single_row( $term, 0, $taxonomy );

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:202
Reason     : TooManyArgument
Snippet    : $this->single_row($my_parent, $level - $num_parents, $taxonomy)
Line       : $output .=  ""\t"" . $this->single_row( $my_parent, $level - $num_parents, $taxonomy );

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:208
Reason     : TooManyArgument
Snippet    : $this->single_row($term, $level, $taxonomy)
Line       : $output .= ""\t"" . $this->single_row( $term, $level, $taxonomy );

--------------------------------
File       : wp-includes/media.php:2453
Reason     : UnknownFunction
Snippet    : sprint($link_fmt, $image)
Line       : $image = sprint( $link_fmt, $image );

--------------------------------
File       : wp-includes/media.php:1040
Reason     : TooManyArgument
Snippet    : wp_mediaelement_fallback($fileurl, $width, $height)
Line       : $html .= wp_mediaelement_fallback( $fileurl, $width, $height );

--------------------------------
File       : wp-includes/Text/Diff/Engine/xdiff.php:30
Reason     : UnknownFunction
Snippet    : xdiff_string_diff($from_string, $to_string, count($to_lines))
Line       : $diff = xdiff_string_diff($from_string, $to_string, count($to_lines));

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:159
Reason     : UseVoidReturn
Snippet    : $this->single_row($term, 0, $taxonomy)
Line       : $out .= $this->single_row( $term, 0, $taxonomy );

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:202
Reason     : UseVoidReturn
Snippet    : $this->single_row($my_parent, $level - $num_parents, $taxonomy)
Line       : $output .=  ""\t"" . $this->single_row( $my_parent, $level - $num_parents, $taxonomy );

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:208
Reason     : UseVoidReturn
Snippet    : $this->single_row($term, $level, $taxonomy)
Line       : $output .= ""\t"" . $this->single_row( $term, $level, $taxonomy );

--------------------------------
File       : wp-admin/includes/class-wp-terms-list-table.php:228
Reason     : UseVoidReturn
Snippet    : $this->single_row_columns($tag)
Line       : echo $this->single_row_columns( $tag );

--------------------------------
File       : wp-includes/wp-db.php:648
Reason     : TooManyArgument
Snippet    : $this->has_cap('collation', $dbh)
Line       : if ( $this->has_cap( 'collation', $dbh ) && !empty( $charset ) ) {

--------------------------------
File       : wp-includes/wp-db.php:649
Reason     : TooManyArgument
Snippet    : $this->has_cap('set_charset', $dbh)
Line       : if ( function_exists( 'mysql_set_charset' ) && $this->has_cap( 'set_charset', $dbh ) ) {

--------------------------------
File       : wp-admin/network/site-settings.php:63
Reason     : TooManyArgument
Snippet    : update_option($key, $val, false)
Line       : update_option( $key, $val, false ); // no need to refresh blog details yet

--------------------------------
File       : wp-admin/network/site-settings.php:126
Reason     : TooManyArgument
Snippet    : esc_html(maybe_unserialize($option->option_value), 'single')
Line       : $option->option_value = esc_html( maybe_unserialize( $option->option_value ), 'single' );

--------------------------------
File       : wp-admin/includes/class-wp-comments-list-table.php:318
Reason     : UseVoidReturn
Snippet    : $this->single_row_columns($comment)
Line       : echo $this->single_row_columns( $comment );

--------------------------------
File       : wp-admin/includes/class-wp-list-table.php:829
Reason     : UseVoidReturn
Snippet    : $this->single_row_columns($item)
Line       : echo $this->single_row_columns( $item );

--------------------------------
File       : wp-admin/includes/class-wp-upgrader.php:1132
Reason     : UseVoidReturn
Snippet    : screen_icon()
Line       : echo screen_icon();

--------------------------------
File       : wp-admin/includes/class-wp-posts-list-table.php:386
Reason     : UseVoidReturn
Snippet    : $this->single_row($page, $level)
Line       : echo ""\t"" . $this->single_row( $page, $level );

--------------------------------
File       : wp-admin/includes/class-wp-posts-list-table.php:401
Reason     : UseVoidReturn
Snippet    : $this->single_row($op, 0)
Line       : echo ""\t"" . $this->single_row( $op, 0 );

--------------------------------
File       : wp-admin/includes/class-wp-posts-list-table.php:447
Reason     : UseVoidReturn
Snippet    : $this->single_row($my_parent, $level - $num_parents)
Line       : echo ""\t"" . $this->single_row( $my_parent, $level - $num_parents );

--------------------------------
File       : wp-admin/includes/class-wp-posts-list-table.php:453
Reason     : UseVoidReturn
Snippet    : $this->single_row($page, $level)
Line       : echo ""\t"" . $this->single_row( $page, $level );
}}}"	rlerdorf
Future Releases	16413	Settings page needs HTML refactoring and UI improvements	nacin*	Administration	3.1	normal	normal	Future Release	enhancement	accepted		2011-01-30T20:22:09Z	2013-05-21T17:50:22Z	"The settings pages haven't had much attention or improvement in a while.

We need to refactor the HTML on the settings pages, as they are still using tables instead of divs.

We also want to make some minor UI improvements including:
- clearer differentiation between option groupings
- using consistent text styles for descriptions and links (including the time zone/date format comment)
- restructure for better readability

Comment if you have any other"	chexee
Future Releases	17451	Unify plugin update notices and include changelog data	nacin*	Upgrade/Install		normal	normal	Future Release	enhancement	accepted		2011-05-16T09:23:25Z	2013-01-16T00:27:00Z	"Currently the after_plugin_row hook is only used on plugins.php which is used by the Changelogger plugin to show plugin changelogs inline.

If the hook is also added to the bottom of list_plugin_updates in update_core.php then changelogs could also be displayed on that page too.

It's only a single line change so not sure how/if it's worth me attaching a patch for this?"	dempsey
Future Releases	15977	Send the Locale in Plugin/Theme Update Check Requests	nacin*	Upgrade/Install	3.1	normal	normal	Future Release	feature request	accepted	early	2010-12-25T20:59:43Z	2013-01-22T00:00:56Z	"Currently, we send locale (and other information about installation) only in wp_version_check and not in wp_update_plugins and wp_update_themes.

Since we still don't know how system for plugins/themes localization will work, I propose that we send this from 3.1.

Why? As said above, there is no definitive agreement on how will localization system work, but it is possible that system wont require changes in core, ie. be same or similar to one I [http://wppolyglots.wordpress.com/2010/12/10/proposal-for-plugins-localization-system/ suggested] over at Polyglots.

In that case localization system will be made independently what means that it'll can start working before 3.2 version. If we don't send locale for plugins/themes, we will need to wait for 3.2 even though that wont be significant change.

In theory, plugin/theme developers could also benefit if alongside locales, we would send all information we send in wp_version_check and later show them as are plugin versions shown now.

I know that is very late for this change but issue with plugin localization tool has been ignored for a very long time as I described in my post mentioned above in more detail."	dimadin
Future Releases	10989	Show changelog for core upgrade	nacin*	Upgrade/Install		normal	minor	Future Release	feature request	accepted		2009-10-21T01:36:14Z	2011-11-15T01:53:20Z	"When clicking on the admin notice that there is an update available, it would be interesting to see a short changelog with a link to the complete changelog of the upgrade besides the two download buttons

Example with the 2.8.5.
Show on the page:
The headline changes in this release are:

    * A fix for the Trackback Denial-of-Service attack that is currently being seen.
    * Removal of areas within the code where php code in variables was evaluated.
    * Switched the file upload functionality to be whitelisted for all users including Admins.
    * Retiring of the two importers of Tag data from old plugins.

More info : http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/"	petervanderdoes
Future Releases	18682	"Make ""WordPress is also available in..."" string translatable"	nacin*	WordPress.org site		normal	normal	WordPress.org	enhancement	accepted		2011-09-16T10:34:02Z	2013-05-27T08:44:01Z	"Currently the links to local sites displayed on !WordPress.org for international visitors are partly English, partly translated:

 !WordPress is also available in Русский.[[BR]]
 !WordPress support forums are also available in Русский.

For better user experience, we should allow l10n teams to translate these strings in Rosetta. Due to different grammatical cases, the language name would probably need a separate context for these links."	SergeyBiryukov
Future Releases	16589	Localized version stats	nacin*	WordPress.org site		normal	normal	WordPress.org	feature request	accepted		2011-02-18T08:52:48Z	2012-04-29T15:57:20Z	"There have been some discussions on localized version stats:

* http://lists.automattic.com/pipermail/wp-polyglots/2009-November/003812.html
* http://lists.automattic.com/pipermail/wp-polyglots/2009-December/003868.html
* http://lists.automattic.com/pipermail/wp-polyglots/2010-July/004859.html
* http://wppolyglots.wordpress.com/2010/12/01/ive-found-some-discussions-about-local-2/
* http://wppolyglots.wordpress.com/2010/08/18/i-am-having-some-problems-with-site-stat/ (related)

Many translators would agree that it would be nice to have them back."	SergeyBiryukov
Next Release	22916	Date/time format translations for front-end	nacin	I18N	3.5	normal	normal	3.6	enhancement	assigned		2012-12-13T14:51:25Z	2013-03-01T15:00:29Z	"Hi.

Since the split of mo/po files between admin and front-end contexts, some resources that were useful for the front-end are now available only for admin. One of them is the date/time format: it's really great it's localized in the reading options panel, but the main purpose of the option remains the front-end and the way the dates and times are displayed, so we need the ""translations"" in the front-end po/mo files.

So the request is to switch the following strings from admin to general text domain:
* F j, Y
* g:i a
* F j, Y g:i a

Thanks."	npetetin
Next Release	20101	Can't use 'show_admin_bar' filter with conditional tags	nacin	Toolbar		normal	normal	3.6	defect (bug)	reopened	dev-feedback	2012-02-22T19:10:11Z	2013-05-30T21:22:15Z	"I'm trying to show the admin bar only on the front page:

{{{
function scribu_show_admin_bar() {
  return is_front_page();
}

add_filter( 'show_admin_bar', 'scribu_show_admin_bar' );
}}}

However, this doesn't work because '_wp_admin_bar_init' is called on 'init', before the main WP_Query is set up."	scribu
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	17861	Bug on WordPress Credits page	nacin	Administration	3.2	normal	normal	WordPress.org	defect (bug)	reopened		2011-06-21T15:56:56Z	2012-11-28T00:15:31Z	"Hi,

There are a couple of bugs on WordPress Credits page.

1.- There is a problem with usernames with dot, for example my username ""j.conti""

I'm on translators list, my name and avatar are correct but the link to my profile is wrong. Now, the link is http://profiles.wordpress.org/users/jconti but my profile is http://profiles.wordpress.org/users/j.conti the bug is deleting the dot.

2.- There is a problem with my name, my name is ""José Conti"" but is showing ""JosÃ© Conti""

attached pic

Thank you"	j.conti
Future Releases	19693	redirect_guess_404_permalink() can catch the wrong post types	nacin	Canonical		normal	normal	Future Release	defect (bug)	reopened		2011-12-30T04:53:09Z	2012-05-24T16:19:12Z	"When I access /blah, and that 404s, redirect_guess_404_permalink() will try to find a matching post name.

If blah is the start of a post name for a random post type (perhaps one used as internal storage), it'll match it and redirect (and then end up 404ing, potentially). There's no constraint on the post type if the post_type query var isn't set, which is going to be common.

We need to come up with a stricter query. (And while we're at it, we should hook redirect_guess_404_permalink() into redirect_canonical() so it may be unhooked without removing all canonical support.)"	nacin
Future Releases	12134	Add image dimensions to smiley img element	nacin	Formatting	3.0	normal	normal	Future Release	enhancement	reviewing	dev-feedback	2010-02-05T02:55:19Z	2011-02-09T06:10:45Z	All smileys are 15x15. Add dimensions to the img element to avoid a double paint by web browsers during page load.	niallkennedy
Future Releases	19065	Please provide original javascript files (.dev.js) for all minified files	nacin	General		normal	normal	WordPress.org	defect (bug)	reopened		2011-10-27T10:18:57Z	2012-06-15T09:01:46Z	"Please provide original javascript files (.dev.js) for all minified files. This is not only useful for debugging, it's also a requirement of some free software distributions like Debian (cf the bug report that prompted all this: http://bugs.debian.org/646729).

Missing files that I noted are (relative to wp-includes/js):
{{{
crop/cropper.dev.js
jquery/jquery.dev.js
jquery/jquery.query.dev.js
jquery/jquery.schedule.dev.js
jquery/jquery.serialize-object.dev.js 
jquery/ui/*.dev.js (all *.js files are minified)
plupload/plupload.*.dev.js (all plupload.*.js files are minified)
swfupload/swfupload-all.dev.js
tinymce/tiny_mce.dev.js
tinymce/tiny_mce_popup.dev.js 
tinymce/plugins/*/editor_plugin.dev.js (all plugins except the WP ones)
tinymce/themes/advanced/editor_template.js
tinymce/wp-tinymce.dev.js.gz
swfobject.dev.js
}}}

I'm not really sure about swfupload/swfupload-all.js, if it's swfupload.js + the 4 plugins minified, then it's ok I guess. But it would be nice to have it documented.

tinymce/wp-tinymce.dev.js.gz is probably also generated from something else but I could not figure out what. It would be nice to document how and when to regenerate it.

I can help to dig out the required files if it helps. Ideally the build process of wordpress would include a way to regenerate automatically the minified files from the corresponding .dev.js file."	rhertzog
Future Releases	11727	Tag cloud widget - font size	nacin	General	2.9.1	normal	normal	Future Release	enhancement	reviewing		2010-01-05T15:49:14Z	2010-08-11T17:23:12Z	"Hi

Not really a bug - but more a question.

The tag cloud widget displays the tags with different font sizes - this works correctly on my blog.

But I don't understand and I think it doesn't make sense to set the font-size with a decimal number:

eg. of HTML code


{{{
style='font-size: 9.3582089552239pt;'
}}}

An integer value of 8 to 22 should be correct in my opinion.

"	tin68
Future Releases	21321	Remove is_null() checks in apply_filters(), do_action(), et al.	nacin	Performance		normal	normal	Future Release	enhancement	reopened		2012-07-20T04:55:29Z	2012-09-16T18:39:00Z	"In apply_filters(), do_action(), and friends, there is a check for `! is_null( $the['function'] )`. As these functions get called collectively thousands of times per page, a tiny check like this can add up.

A few months ago, I decided to track it down. They were shuffled around a bit in [4955], but they actually had roots in [1394]. The link there (http://www.kackreiz.net/wordpress.php) is dead, but I found it at http://www.kackreiz.net/wordpress/apply_filters.html#fixed, via http://wordpress.org/support/topic/bug-in-remove_filterapply_filters?replies=3.

The original bug was that remove_filter() left NULL's in the $wp_filter array, rather than properly unsetting it as it was modified to do long ago. Now that we no longer leave NULL scattered about, this check is safe to remove."	nacin
Future Releases	14011	On subdirectory multisite installs, custom post types on main blog generate bad next/previous links	nacin	Post Types		normal	normal	Future Release	defect (bug)	reviewing		2010-06-20T21:06:51Z	2011-11-22T22:18:34Z	With multisite and subdirectories, the main blog uses site.com/blog/xxx permalinks however custom post types can use site.com/custom/permalink .  The next and previous post template tags generate the links as site.com/blog/custom/permalink .	jorbin
Future Releases	12717	Ability to create new theme files.	nacin	Themes		normal	normal	Future Release	feature request	reviewing		2010-03-26T00:30:26Z	2010-06-21T06:18:43Z	"It would be really nice to be able to create a new file with the theme editor (e.g. loop-category.php) or a new page template for example, when you realise that you need one.

This is related to the last comment in #12716 as creating new versions of parent theme files in your child theme also would be very useful.

Yes.... I know you can use FTP to do this, but when you want to create a new page template quickly and you are in the wrong place it would be a very useful feature.
By the same argument we have the theme editor in the first place, let make it even more useful."	Dickie
Future Releases	15655	Media Upload form does not pass tab name	nacin	Upload	3.0.2	normal	normal	Future Release	defect (bug)	reviewing		2010-12-03T00:00:01Z	2011-11-22T16:52:58Z	"The Media Upload form has an error (wp-admin/includes/media.php line !#1538). It is not passing the tab name, which hinders adding actions based on which Upload tab is selected.

Error:
Get param 'tab' is being set to 'type' which is incorrect.
{{{
$form_action_url = admin_url(""media-upload.php?type=$type&tab=type&post_id=$post_id"");
}}}


Fix:
To top of function add:
{{{
global $tab;
}}}

Change the form action URL (line !#1538) to:
{{{
$form_action_url = admin_url(""media-upload.php?type=$type&tab=$tab&post_id=$post_id"");
}}}

This change also impacts function media_upload_type_url_form (line !#1591). Same fix applies."	jackcrosby
Future Releases	19583	Android honeycomb browser gets detected as old version of Safari	nacin	WordPress.org site	3.3	normal	normal	WordPress.org	defect (bug)	reviewing		2011-12-17T01:30:29Z	2013-03-16T16:55:18Z	"Reported by a friend of mine (see image attachment).

User agent string is:

{{{
Mozilla/5.0 (Linux; U; Android 3.2; en-us; A500 Build/HTJ85B) AppleWebKit/534.13 (KHTML, like Gecko) Version/4.0 Safari/534.13
}}}
"	Viper007Bond
Future Releases	22525	Marking duplicates on Trac without a ticket number improperly resolves the ticket	nacin	WordPress.org site		normal	normal	WordPress.org	defect (bug)	assigned		2012-11-21T11:38:50Z	2012-12-02T16:39:39Z	For some reason, the last ticket I submitted closed itself when I tried to reply to it.  Looking for a Trac bug now.	miqrogroove
Future Releases	18231	Opera Mini being reported as out of date	nacin	WordPress.org site	3.2.1	normal	normal	WordPress.org	defect (bug)	assigned		2011-07-24T05:14:23Z	2012-09-28T16:05:28Z	"From http://wordpress.org/support/topic/latest-opera-mini-flagged-as-old-version-of-opera?replies=1


I use the latest Opera Mini for Symbian v 6.1.25570 for access to my WordPress.org blogs from my mobile phone. It works well for comment moderation, minor edits to posts and upgrading plugins.

Since upgrading to WP 3.2.1 I've been seeing ""It looks like you're using an old version of Opera.."" on my Dashboard.

This message is incorrect as I AM running the latest version of Opera Mini. It's only a minor annoyance but it would be nice if it was fixed."	Ipstenu
Future Releases	23034	wordpress-sources is not up to date	nacin	WordPress.org site		normal	normal	WordPress.org	defect (bug)	assigned		2012-12-21T08:16:31Z	2013-01-10T06:55:04Z	"It would be nice if you could include as part of your standard release workflow a step that ensures that http://code.trac.wordpress.org/browser/wordpress-sources is up-to-date.

For instance WP 3.5 ships JQuery 1.8.3 but the above repository only contains the source for version 1.8.1. JQuery UI is at 1.9.2 while the above repository only contains 1.8.23."	rhertzog
Future Releases	17580	"get_media_item(): add filter to better control ""buttons"" in media upload and make more performant if buttons are already set"	mitchoyoshitaka	Performance	3.1.3	normal	normal	Future Release	enhancement	new		2011-05-26T23:08:45Z	2012-04-27T15:14:40Z	"Two issues in get_media_item():
1. There's no good, clean way to modify the ""buttons"" (things which get stored lumped together in $form_fields[""buttons""]) in the Media Upload, except for the ""delete"" and ""send"" (aka ""insert into post"") which can be controlled via the 'get_media_item_args'. Add a filter for that.
2. Right now we construct the HTML snippets for different buttons, as $send, $delete, and $thumbnail... and then checking whether $form_fields[""buttons""] is already set or not, and then only using them if it's not already set. If a plugin already pre-specifies the buttons HTML, this computation is completely wasteful. Move this conditional earlier.
3. (Terribly minor:) If any of these buttons aren't actually used, <td class='savesend'/> is produced with extra whitespace in it. This is a reflection of the poor design of the code which prints this HTML."	mitchoyoshitaka
Future Releases	9460	Add custom_url_func to be run in template-loader.php	mikeschinkel	Permalinks	2.8	normal	normal	Future Release	enhancement	new		2009-04-04T22:48:30Z	2009-08-19T11:56:57Z	"This is a follow-on from Ticket #9455 where the #9455 attempted to resolve one issue using a shortcut but the shortcut turned out to cause undesirable side effects and also did not address the fact that 404 and noncache headers had already been set.

So this ticket provides a patch that will allow for a custom_url_func to be called at the beginning of template-loader.php. The custom_url_func can be set in a 'parse_query' hook using code that looks like this for the URL ""/foobar/"":


{{{

   add_action('parse_query','my_parse_query');
   function my_parse_query() {
      if ($_SERVER['REQUEST_URI']=='/foobar/')
        set_custom_url_func('my_foobar_func');
   }
   function my_foobar_func() {
      echo 'Hello FooBar!  Bye.';
   }

}}}


Granted, this might not be the best way to accomplish this. For example, using a new filter might be a better way to accomplish this but I was trying not to add additional filter processing overhead assuming that might be a concern. I'm not attached to this particular solution, I just want to be able to get proper control of custom URLs that don't fit any of the existing patterns that have been baked into WordPress core and ideally I don't want it to have to be uber-complex for the plugin or theme developer either.
"	mikeschinkel
Future Releases	18603	Comments on pages which exceed paginate settings create erroneous permalinks	Mike Sagman http://www.dogfoodadvisor.com	Comments	3.2.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-09-06T17:32:14Z	2013-02-07T17:09:36Z	On my website, clicking on any of the Recent Comments that possess large numbers of comments exceeding paginate settings (50 comments) present erroneous permalinks. Only the posts containing enough comments on page 3 or higher present these improperly constructed links that take users to the wrong page (a page that does not contain the comment in question). The problem does not occur on pages containing a limited number of comments. So far, we have removed our Thesis theme and changed to the standard WP default theme. And we've deactivated all plugins. Yet neither solution appears to resolve the issue. Thanks for your consideration. You may view this issue live at http://www.dogfoodadvisor.com	msagman
Future Releases	18733	Show revision number for post/pages in Revision list	midhund	Revisions	3.3	normal	normal	Future Release	enhancement	new		2011-09-21T11:26:33Z	2013-05-02T09:46:41Z	"Sometimes the current revision title is not enough to identify the post/page revisions on the list. So I wish to show the revision number with link to revisions's page.

I have the patch, please review it."	midhund
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	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	2702	Easier way to change page order (AJAX/jQuery?)	mdawaffe	Editor	2.3	normal	normal	Future Release	enhancement	new		2006-05-03T21:36:37Z	2011-10-08T03:23:13Z	"When having a lot of pages, they get harder to manage (see also Ticket #2004 [Pages page should page]).

When needing to change the page order, it's very inefficient to manually change the page order value, or whole series of page order values, just to move one page up or down the list. Suggestions for alternative ways to change the page order are:

In ""Manage - Pages""
1) With up/down arrows (page goes one up or down when the button/link is clicked).
2) or: Drag+Drop (The post/page settings can be dragged and dropped, so why can't this, too?)
"	FireMotion
Future Releases	5117	WordPress (plugin) updates do not warn about unknown plugins	matt	Upgrade/Install	2.6	normal	normal	Future Release	defect (bug)	new		2007-09-30T11:34:17Z	2009-09-02T20:29:29Z	"The WordPress plugin update system does not notify the user if it could not find updates for a subset of plugins. That is, if the user has installed plugins not hosted with WordPress, they are not notified that new versions were ''not'' actually checked for. This can lead the user to believe that all of their plugins are up-to-date when they are not.

Fixing this will require both the server-side and the client to be updated. The WordPress update API will need to return data on which plugins it does not recognize as being hosted, and the WordPress installation will need to render that information so that the user understands which of his/her plugins are ''not'' automatically checked."	Quandary
Future Releases	6106	Post slug improvements	markjaquith*	Administration	2.5	normal	normal	Future Release	enhancement	accepted		2008-03-05T21:08:21Z	2011-09-09T00:02:15Z	" 1. ~~Right now, a post ID is shown as the post slug unless a slug is manually entered.  Instead, it should show the dynamic slug generated from the title.~~  Ideally, as the title is updated.  (maybe using onblur to see if the typed-in title has changed, and doing a quick AJAX request to see what the dynamic slug would be).
 1. There is no way to tell the difference between a tentative slug, and a locked-in slug (either by choice, or by hitting ""publish"").  Perhaps the highlighting could go away and the slug could be bolded to indicate that it is set.

"	markjaquith
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	4332	Unusable comment error pages	markjaquith*	Comments	1.5	normal	normal	Future Release	enhancement	accepted		2007-05-24T20:53:17Z	2012-03-08T01:35:22Z	"No comment error page requires browser navigation to leave

ENV: WP trunk r5486

While viewing a post, I click Submit Comment without entering any information and the result is  (wp-comments-post.php):

WordPress [[br]]
Error: please type a comment.

Dead end: no link back to the page where I meant to comment or maybe accidentally clicked the button, and ""Error:"" makes me feel stupid ;-)

POSSIBLE SOLUTION

I don't see any reason to navigate away from the post post.

ADDITIONAL DETAILS

Assuming the error page is desirable (sure hope not), being able to style it might be useful."	foolswisdom
Future Releases	4298	wpautop bugs	markjaquith*	Formatting	2.7	low	minor	Future Release	defect (bug)	accepted	dev-feedback	2007-05-19T22:14:10Z	2010-04-04T06:42:21Z	"wpautop should at least ignore multiline html tags, and possibly ignore any area enclosed within html.

{{{
<table
 style=""width: 120px; height: 92px; text-align: left; margin-left: auto; margin-right: auto;""
 border=""1"" cellpadding=""7"" cellspacing=""2"">
  <tbody>
    <tr>
      <td><small><small style=""font-family: Arial;"">Once
I saw it here, I instantly knew what I wanted. I love my new woven wood
shades.</small></small><br>
      <small><small>- Ginny Good</small></small></td>
    </tr>
  </tbody>
</table>
}}}

gets formatted as:

{{{
<table<br />
 style=""width: 120px; height: 92px; text-align: left; margin-left: auto; margin-right: auto;""<br />
 border=""1"" cellpadding=""7"" cellspacing=""2""><br />
<tbody>
<tr>
<td><small><small style=""font-family: Arial;"">Once<br />
I saw it here, I instantly knew what I wanted. I love my new woven wood<br />
shades.</small></small><br /><br />
      <small><small>- Ginny Good</small></small></td>

</tr>
</tbody>
</table>
}}}

"	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	3491	new hooks for pingback, trackback?	markjaquith*	Pings/Trackbacks		normal	normal	Future Release	enhancement	accepted		2006-12-21T22:13:25Z	2009-06-13T14:59:54Z	"I'd like to propose two more hooks for Wordpress, one in pingback_ping()
and the other in wp-trackback.php.

background: http://redmonk.net/archives/2006/12/21/voteback/

The first hook would allow plugins to have access to the full text of a
hyperlink on a site that is pinging this site, before the comment is
built for a ping.

The second would allow plugins to have access to the full post data for
a trackback before the comment is built.
"	monkinetic
Future Releases	6379	Image Insert section is confusing, not properly separated from Image Editing	markjaquith*	Upload	2.5	normal	normal	Future Release	enhancement	accepted		2008-03-25T06:29:59Z	2010-10-28T08:21:47Z	"This whole section:

[[Image(http://img339.imageshack.us/img339/7967/picture1td7.png)]]

... is related to inserting that individual photo into the post, but it is slammed together with photo settings that you can change and save.  We really need to demarcate the ""Insert Image into Post"" section better.

Other issues:

 * ""None"" alignment radio button is not selected by default.
 * The Link URL section is incredibly confusing.  At first I thought that was where you could edit the filename.
 * Pressing input buttons to make your link URL selection is unnatural."	markjaquith
Next Release	23136	Do not notify the post author about comments if they are no longer a member of the blog	markjaquith	Comments	3.5	normal	normal	3.6	enhancement	reopened	dev-feedback	2013-01-07T18:45:21Z	2013-04-19T20:08:24Z	wp_notify_postauthor() should not notify the post author of comments if the author is no longer a member of the blog.	ryan
Future Releases	6479	Encourage people to change default tagline	markjaquith	Administration	2.5	normal	normal	Future Release	enhancement	assigned		2008-03-30T19:09:41Z	2013-01-22T00:42:25Z	"A lot of people don't change the default tagline, especially if using a theme that doesn't display it.  But it still displays in their feed.  We should check to see if they still have the default tagline and if so, put a little contextual help in Settings - General that (nicely) encourages them to change it.

Props to Chris Silver Smith for bringing this issue up at WordCamp Dallas."	markjaquith
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	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
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	16240	hide_empty doesn't work in get_terms() when hierarchical isn't set to false	markjaquith	Taxonomy		high	major	Future Release	defect (bug)	assigned	close	2011-01-15T06:06:05Z	2012-09-13T06:34:17Z	"I end up with some 0-count categories when calling {{{get_terms( 'category', array( 'hide_empty' => true ) )}}}

I think it has to do with the child count logic."	markjaquith
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	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
Future Releases	18476	Duplicate code in filesystem classes	kurtpayne	Filesystem	3.2.1	normal	minor	Awaiting Review	enhancement	new	dev-feedback	2011-08-18T17:54:33Z	2012-07-06T14:09:04Z	Each filesystem class extends a base class and most, but not all, include an implementation of chown.  I propose a slight refactoring to include a default implementation of chown in the base class and let each subclass override chown when necessary.	kurtpayne
Future Releases	19649	DFW Auto textarea lengthening is twitchy	koopersmith	Editor		normal	normal	Future Release	defect (bug)	assigned		2011-12-22T21:52:36Z	2012-04-27T21:08:56Z	"The auto textarea lengthening is twitchy. It shoves the content up a line, then pulls it back down.

Best seen in a screencast: http://screencast.com/t/e5zIpkk9nY"	markjaquith
Future Releases	21170	JavaScript actions and filters	koopersmith	General	3.4	normal	normal	Future Release	feature request	new	dev-feedback	2012-07-05T21:34:03Z	2013-05-22T20:38:38Z	"The concept of adding JavaScript actions and filters has been tossed around for some time. We've experimented with various configurations of actions in both the fullscreen and customizer APIs, and they've proven their utility enough to graduate them to a core feature in their own right.

----

I think that a good events API should satisfy these parameters:

1. '''Support jQuery-style dot namespacing''' to allow functions to be easily removed.

2. '''Should (likely) support priorities.''' While seemingly random numbers aren't fun to use, it allows plugins to cooperate without having to know of each other's existence. We can't expect plugin authors to rearrange the array of callbacks.

3. '''Should ''not'' force functions to have unique IDs.''' Anonymous functions are extremely common in JavaScript — forcing them to be named is contrary to the nature of the language.

4. '''Should be structured as a mixin.''' The global event loop should be an instance of the core Events object. Using a mixin will allow developers to easily create event loops for their own plugins (to prevent  polluting the global namespace — think about large plugins, like bbPress). An events mixin will also enable developers to create more powerful abstractions, such as observable values, collections, and pretty much any structural JS object you can dream up.

5. '''Should allow the looping process to be overwritten.''' This will result in less code and added flexibility. The only difference between actions and filters is how they handle the callbacks object. There are other types of looping processes that could be beneficial in JS. One example would be returning false if any callback returns false, which could be used to stop a process, much like the native event.stopPropagation method.

----

'''Why not use custom jQuery events?'''

Custom jQuery events are great when we need to trigger actions on a DOM element. Triggering plain events on the body element (or any other hidden element) is not performant — every jQuery event normalizes an DOM Event object, which we then completely ignore.

'''Should we require jQuery to use the API?'''

I'm not sure. jQuery.Callbacks may be a helpful solution here, provided we can properly integrate priorities and namespacing. jQuery.Callbacks also only requires jQuery.each and jQuery.extend, so writing a shim that doesn't use the rest of jQuery would not be exceptionally difficult. Either way, switching between one and the other as we develop should not be exceptionally difficult."	koopersmith
Future Releases	13247	Drag/drop for add menu item boxes	koopersmith	Menus	3.0	normal	normal	Future Release	enhancement	new		2010-05-04T07:12:03Z	2010-10-28T09:25:22Z	Because checkboxes are no fun. This first patch covers dragging from view all and most used. Search still has bugs.	koopersmith
Future Releases	15957	add two new actions to track template loading	koopersmith	Template		normal	normal	Future Release	enhancement	reviewing		2010-12-23T02:23:07Z	2012-02-14T14:29:32Z	"I would like to add two new actions ""pre_load_template"" and ""post_load_template"" inside the load_template() method.  The purpose of this is primarily for debugging and development purposes.  For example, I'd like to use these actions to add debug comments in a theme's output along the lines of:

{{{
<!-- begin ../themes/twentyten/loop.php -->
...
<!-- end ../themes/twentyten/loop.php -->
}}}

This makes it much easier to identify which theme file is responsible for which part of the final page, particularly in the case where some files are being pulled from a parent theme and some are from the child theme."	willnorris
Future Releases	19627	Themes should be able to opt-in to a static front page	koopersmith	Themes		normal	normal	Future Release	feature request	assigned		2011-12-21T01:42:05Z	2013-03-02T21:47:58Z	"A theme should be able to register that they are designed to have a static front page by default. Core should then pick up on this as part of the activation process and allow them to pick or create a page, or ignore it and show posts on the front.

Twenty Twelve will most likely need this (http://wpdevel.wordpress.com/2011/12/20/default-theme-twenty-twelve/)."	nacin
Future Releases	6814	Async media crunching	koopersmith	Upload	2.5	normal	normal	Future Release	enhancement	assigned		2008-04-23T00:19:05Z	2012-10-22T16:09:26Z	"The upload part of the new multi-uploader is pretty nice now, but it blocks on the ""crunching"" phase, which can sometimes take 20-60 seconds, I assume to create medium thumbnails and such.

The crunching part of the upload should not block the next file beginning the upload process, it should happen asynchronously with the rest of the process."	matt
Future Releases	14466	Widget position uses footer position styling	koopersmith	Widgets	3.0	normal	normal	Future Release	enhancement	reopened		2010-07-30T08:13:12Z	2012-11-07T22:35:08Z	"Hi,

If you add a widget position called Footer with id footer, it has exactly the same id as the footer of the whole admin and because of that the widget position uses the styling from admin footer ie. bigger padding, italic font, darker background. Please see the attached pic.

newkind"	newkind
Future Releases	15783	JavaScript Coding Standards	koopersmith	WordPress.org site		normal	trivial	WordPress.org	enhancement	assigned		2010-12-12T10:56:05Z	2013-04-11T13:36:22Z	"Following up on scribu's and azaozz's comments in #15650, would a JavaScript Coding Standards page on the Codex (equivalent to http://codex.wordpress.org/WordPress_Coding_Standards and http://codex.wordpress.org/CSS_Coding_Standards) be useful?

It would not only include the usual code formatting, whitespace, brace position, semi-colon requirements etc, but also clarify on which code patterns are preferable for performance, both for the specific dependency library, and those that will give the smallest file when minified.

Another idea might be to introduce a file docblock that outlines which JS library or other file dependencies the current file has.

Some references:
 * http://javascript.crockford.com/code.html
 * http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml
 * http://drupal.org/node/172169
"	GamajoTech
Future Releases	12032	Additional Option of Site Admin -> Options -> Allow new Registrations.	kallumamaji	Users	3.0	normal	normal	Future Release	feature request	reviewing		2010-01-26T00:29:42Z	2011-12-29T09:29:57Z	"MU Trac Ticket: http://trac.mu.wordpress.org/ticket/799

Right now the 4 options are: Disabled - noone can register a new account or blog Enabled - blogs and user accounts can be enabled (at the same time as the request) Only User Account - Only a user account can be created. Only Logged in User - Cannot create a user account but those who can log in can create a blog.

Need a 5th option for Create User Account and Allow blog creation if logged in.

With the 5th option it will allow new registrations., but only allow them to request a new blog if they are a valid online user after registration.
"	wpmuguru
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	7773	Duplicate enclosure attributes are created when a client resubmits a post with identical enclosure	josephscott	Optimization	2.7	low	minor	Future Release	enhancement	new		2008-09-21T04:25:07Z	2009-11-17T15:14:49Z	"The support in 2.6 for accepting enclosures via XMLRPC does not discriminate whether the specified enclosure is already attached to the post in question. This has the effect that if a client redundantly re-specifies the enclosure value, WordPress will redundantly add new enclosure custom field entries, each time the post is edited.

The code that accepts <enclosure> elements should only add a new custom field to the post if the enclosure specified is different from the previous enclosure(s). Arguably, for an XMLRPC context, the specified enclosure should always replace the (presumed singular) enclosure on the post.

Right now, the number of redundant enclosure attributes can spiral out of control depending on the number of times a given post is edited by a remote client that re-specifies all the known attributes of a post.

Consider for example, that when resubmitting a post, it's natural and expected to re-specifiy the <title> even if it hasn't changed. This doesn't cause multiple ""title"" attributes to appear on a post. The re-specification of the <enclosure> value shouldn't cause attribute bloat in posts.

Daniel

Daniel

"	redsweater
Future Releases	14902	weblogUpdates.extendedPing does not implement standard	josephscott	Pings/Trackbacks	3.0.1	normal	normal	Awaiting Review	defect (bug)	reviewing		2010-09-19T23:35:37Z	2011-01-13T05:48:24Z	"When a blog post is published or updated, Update Services are notified if they are listed in the Wordpress Writing Settings panel.

The services are notified by the weblog_ping() function in comment.php

That function first attempts an XMLRPC call to the service's weblogUpdates.extendedPing.  If that fails, it attempts to notify weblogUpdates.ping.

if ( !$client->query('weblogUpdates.extendedPing', get_option('blogname'), $home, get_bloginfo('rss2_url') ) ) // then try a normal ping
	$client->query('weblogUpdates.ping', get_option('blogname'), $home);

'''1) The weblogUpdates.extendedPing does not match the published standard.'''

See: 

http://www.google.com/help/blogsearch/pinging_API.html

Where 5 parameters are specified:

* Name of site
* URL of site
* URL of the page to be checked for changes
* URL of RSS, RDF, or Atom feed
* Optional a name (or ""tag"") categorizing your site content. You may delimit multiple values by using the '|' character.

The third parameter should be the page to be checked for changes, and not the RSS feed.

No 4th or 5th parameter is passed.

'''2) The weblogUpdates.extendedPing does not take advantage of notifying the service of the exact page that changed (as is provided in the standard)'''

If implemented correctly, this would allow the receiving service (perhaps a search engine) to come directly to the correct page for re-indexing, instead of trying to figure it out from the RSS feed.

I am unable to find if pingomatic.com publishes a competing version of the standard.
"	Scott Schram
Future Releases	12939	Counterpart to content_save_pre hook not called when getting post content via API	josephscott	XML-RPC	2.9.2	normal	normal	Future Release	defect (bug)	reviewing	dev-feedback	2010-04-09T13:53:57Z	2011-04-05T08:50:45Z	"When a post is submitted either through the web editor interface or from an API call to newPost or editPost, the content of the post is inevitably passed through the content_save_pre filter.

And when a post is opened for editing in the web editor, the content is passed through filters such as the_editor_content and  content_edit_pre.

However, when a post is fetched for editing via XMLRPC API calls such as getPost or getRecentPosts, the content_edit_pre filter is never reached.

This leads to a situation where whatever massaging of the content that a plugin may peform on the way into the database is not reversed on the way back out, for clients of the API. A concrete example of this problem is with the popular Syntax Highlighter Evolved:

http://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/

This plugin performs encoding of the post content before it is stored in the database, and it counts on being able to decode that content by adding filters to hooks such as the_editor_content. However, none of these filters are reached via the API, leading to ""corrupted content"" when users try to edit posts from API clients such as the iPhone WordPress app, or my desktop editor, MarsEdit.

(My previous bug report #10802 exhibits the same symptoms of this bug, but this is a different cause).

In summary:

1. WordPress needs to establish a clear, baseline hooks for massaging content before it is saved to the database, and for un-massaging the content on the way out of the database. Currently there seems to be uncertainty about which hooks need to be overridden and under what circumstances. It seems to me that content_save_pre and content_edit_pre are probably good candidates for this.

2. Whatever hooks are established as the guarantees need to be applied once and only once in both the web-based editing scenario, and in the API editing scenario.

I think that having a well documented pair of hooks for this purpose that works identically in the web editing and API editing cases will do a lot to ensure correct behavior when plugins are installed that massage content, and will make it easy for plugin developers to ""do the right thing"" without relying on hooks that are specific only to the web editor, or to the API.
"	redsweater
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
Future Releases	14966	QuickPress should be a function with alot of hooks	jorbin*	General		normal	normal	Future Release	feature request	accepted	early	2010-09-26T18:12:17Z	2013-02-09T04:20:38Z	"As discussed in IRC, quickpress should be a function that is usable by:

1) Custom Post Types
2) Themes for front end posting ala p2
"	jorbin
Future Releases	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
Future Releases	15642	user-new input fields stretch to the edge of the screen	JohnONolan	Users	3.1	normal	normal	Future Release	defect (bug)	assigned		2010-12-02T09:01:05Z	2010-12-02T11:59:22Z	They shouldn't.	nacin
Future Releases	18848	Filter post listing screen by post parent	johnbillion	Administration	3.3	normal	normal	Awaiting Review	feature request	assigned		2011-10-03T16:19:10Z	2011-10-03T18:56:58Z	"It's not possible to filter a post listing screen by post_parent. This would be super handy for hierarchical post types (eg. Pages) where you may have several levels of hierarchy and want to view only the descendants of a particular page. I'm not sure that we need a UI (eg. dropdown menu) for it, but a working URL query var would be great.

I made an attempt at patching this a while ago using the child_of parameter but it got complicated quite quickly, so I'm putting it out there as a feature request in case anyone feels like tackling it."	johnbillion
Future Releases	20461	View All Gallerys	Jesse Techno	Gallery	3.4	normal	normal	Awaiting Review	feature request	new	close	2012-04-16T22:55:56Z	2012-12-17T15:39:20Z	If you could it would be SO nice to have it so you can see every gallery you have ever posted on your site and then add one gallery to to more then one page/post.	jessetechno
Future Releases	12254	Move show_message() into WP_Error class and add support for various WP_Error features that are missing	jeremyclarke	General		normal	normal	Future Release	enhancement	new		2010-02-16T19:31:05Z	2010-11-29T17:38:59Z	"Revisiting an old ticket about the mass upgrader (#11232) after working on my ticket for the Settings API (#11474) makes me think both cases are running into a wider problem related to the way WP_Error messages are handled system-wide. There just isn't a way to show them that fits with the detailed system that exists around logging errors with WP_Error. In both cases having a built-in way to display all messages logged in a WP_Error object would simplify their code and make their use of WP_Error much more logical and less haphazard.

== WP_Error is intense ==
WP_Error objects can have an infinite number of messages logged inside them into $code groups which themselves can even have multiple message values/ 

{{{
 WP_Error::add($code, $message, $data = '')
}}}

You can then retrieve error messages for a specific code using WP_Error::get_error_messages()

== show_message() is weak ==
In contrast to this useful maleability is the show_message() function used by various updater scripts to access WP_Error messages:

{{{
/**
 * {@internal Missing Short Description}}
 *
 * @since unknown
 *
 * @param unknown_type $message
 */
function show_message($message) {
	if( is_wp_error($message) ){
		if( $message->get_error_data() )
			$message = $message->get_error_message() . ': ' . $message->get_error_data();
		else
			$message = $message->get_error_message();
	}
	echo ""<p>$message</p>\n"";
}
}}}

Living in misc.php, this is clearly not the most loved function in WordPress, but beyond its lack of documentation and arguments it also actually doesn't make sense when combined with the nature of WP_Error, and I'd argue that it should be a first-class citizen of the WP_Error API. 

=== Deal with the input as WP_Error class by default === 
For one thing its argument is named $message, which is a misnomer since it also supports complex WP_Error objects. I think it should be called $error and it should attempt to handle the error object in as much detail as possible. If this function is given a string instead of an error_object it should just show the text with the default formatting. 

=== Move it into the class defintion ===
The function logic should also be moved to be inside WP_Error as ::show_message() as well as maybe adding a ::show_messages() to differentiate between forcing the first message in the object and showing any relevant messages. The original function can be kept as a shell for the class method. 

=== Support $code and $data better ===
The updated function should allow $code values to be specified to show only messages related to a specific error $code (from WP_Error::add()) as well as some kind of option specifying whether the contents of the $data value for the results should be displayed.

=== Add support for 'types' of errors for display purposes ===
To really have valuable visual cues linked with error display the system needs to be adapted to handle error types like 'error', 'updated' and something green like 'success'. Having this be part of hte API would increase the likelihood of people using the system because it will make it easier to quickly add visual errors to a plugin. IMHO the easiest way to achieve this would be to link 'types' with CSS classes expected to exist in wp-admin. 'updated' and 'error' classes already exist, yellow and red respectively, and can be a starting point. This way marking an error as 'error' or 'updated' automatically controls the color it will be when show_messages() is run. 

This would probably require modifying the WP_Error::wp_error() and WP_Error::add() methods to accept a 4th argument, but would be a great step forward. 

=== Use nice formatting ===
I think the formatting should be the same as the 'settings updated' message from after you save a settings page. It is malleable and stands out in the admin:
{{{
<div class=""updated fade""><p><strong> MESSAGE </strong></p></div>
}}}


== Lets make showing errors easy ==
Even though these functionalities aren't needed for the current uses of show_message() in the upgrader process I think they will inform and improve those systems when the changes are taken into account. WP_Error is fairly powerful but not used enough because it is incomplete and awkward. Improving show_message() to fill this hole will mature the API and hopefully get plugin authors using it in more detail. It would definitely make integrating WP_Error into the Settings API much easier. 

== Thoughts on this before I make a patch? ==

I'll try to work on this soon but am interested in feedback. Anyone had this idea before and ran into a wall? Something else you think should be included?"	jeremyclarke
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	8296	Auto generate password for new user	jamierumbelow	Users		normal	normal	Future Release	enhancement	new		2008-11-20T16:25:53Z	2012-07-26T15:46:14Z	It would be nice to have a button that generates a random password to use when you're creating a new user account in the admin section	AaronCampbell
Future Releases	16822	FORCE_SSL_LOGIN causes wp-login.php to have an incorrect https link	jakub.tyrcha*	Security	3.1	normal	normal	Awaiting Review	defect (bug)	accepted		2011-03-10T16:21:25Z	2011-09-10T01:20:12Z	"In this bug, the WordPress logo on the login screen incorrectly links to an https URL. It is easy to reproduce.

First, define('FORCE_SSL_LOGIN', true) in wp-config.php. Then make sure you are logged out of WordPress. (Note: I am running multisite - I don't know if this matters or not.)

1. Visit /wp-login.php. Fill in WRONG credentials (misspell your password) and click the Submit button.
2. wp-login.php redisplays as expected, this time with an https URL.
3. The WordPress logo on the form now links to https://your.site.com. If you click it, you are visiting your site over SSL.

This should not happen. The WordPress logo (and any other links on the login page) should render http URLs."	dbvista
Future Releases	18703	'pre_get_posts'-filter without effect when modifying 'tax_query'. Wrong parameters passed to 'parse_tax_query() ??; WP 3.2.1.	info@…	General	3.2.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2011-09-19T13:10:12Z	2013-06-17T22:27:50Z	"When modifying the 'tax_query' array directly with 'pre_get_posts' filter (e.g. setting 'include_children' to false), then it will firstly  be modified in 'wp-includes/query.php' -> get_posts() after running the filter in line 1911.

But after line 2195 and running 'parse_tax_query' the 'tax_query' 'include_children'-parameter is unwanted reset/changed to the default value.

I think the bug is the following:
 
parse_tax_query() uses and needs values from the 'tax_query'-array but gets passed over only the 'query_vars'-array. so it resets the 'tax_query'-array-parameters in query.php line 1678 and hereby also the previously and individually set 'tax_query' values.

as far as i understand the core, i assume that any changes to the 'tax_query'-array with 'pre_get_posts'-filter will get lost and only changes to the 'query_vars'-array will take effect."	xitromedia
Future Releases	10149	A floating image added in a comment results in a weird layout in the default theme	iandstewart	Themes	2.8	low	minor	WordPress.org	defect (bug)	assigned		2009-06-13T22:33:19Z	2010-10-30T18:36:03Z	I'd have suggested a <div class=clear></div> or something in the default theme, but the bug is actually located within wp_list_comments().	Denis-de-Bernardy
Future Releases	4518	Nested <ol> <ul> lists display incorrectly with default theme	iandstewart	Themes	2.2.1	normal	normal	WordPress.org	enhancement	assigned		2007-06-23T02:33:41Z	2011-08-23T12:48:21Z	A nested ordered / unordered list places bullets AND numbers on the unordered list.  You can see an [http://andrew.jorgensenfamily.us/2005/12/cygwin-openssh/ example of this] on my own site.  The bug is somewhere in wp-content/themes/default/style.css.  I fixed it once before but I don't recall where the bug is now.	andrewjorgensen
Future Releases	13529	Twenty Ten max-width in editor style wraps too early	iammattthomas	TinyMCE	3.0	normal	normal	Future Release	defect (bug)	assigned		2010-05-25T04:46:34Z	2010-11-13T01:26:47Z	"While I get where iammattthomas was going with his change to the mceEditor, in practice it looks confusing...while editing my text, there are arbitrary line breaks that I didn't ask for, and there's no explanation why...

See file: http://core.trac.wordpress.org/browser/trunk/wp-content/themes/twentyten/editor-style.css?rev=13178

I propose eliminating the max-width property.

I apologize if this isn't the right way to do this, it's my first ticket.

I've attached a screenshot so you can see the issue as I see it..."	longjasonm
Next Release	23843	Consolidate and filter get_attached_audio|video|images	helen	Media		normal	normal	3.6	enhancement	reopened	dev-feedback	2013-03-22T07:42:29Z	2013-05-24T19:35:48Z	Seeing as they are so very similar, we should probably just de-spaghetti and consolidate them into `get_attached_media( $type )`. Should also filter the args and the resulting arrays.	helen
Future Releases	5678	Respectfully strip newlines in some importers	hansengel*	Import	2.5	normal	normal	WordPress.org	enhancement	accepted		2008-01-16T11:20:02Z	2012-09-10T09:44:42Z	"Filing this as an enhancement because it could do with some discussion and insight from wiser and more experienced heads before being labelled ""defect"". :-)

I noticed while helping some users import their blogs that importers of HTML content (such as the RSS importer) don't tidy up superfluous newlines in the import format, which results in unnecessary {{{<br/>}}} elements after {{{wpautop()}}} filtering for display. They turn up in the editor too, which reinforces the problem.

I've adapted one of the filter functions to strip superfluous newlines, and changed my RSS importer to use it. The results have been warmly welcomed by users, who no longer have to clean up their imported blog content. ;-)

{{{strip_newlines()}}} should probably go into {{{wp-includes/formatting.php}}}, if there isn't already a function that already serves this purpose. I couldn't find one, so I adapted this. 

Given that similar HTML block/inline-savvy string-replacement code exists in other formatting functions, perhaps there's an opportunity for some refactoring here? I feel kind of silly proposing a function that is almost entirely duplicated from other code in the core.

I've used it immediately before the ""Clean up content"" section in {{{wp-admin/import/rss.php}}}'s {{{get_posts()}}}, and in an Advogato importer that I've written (which also uses HTML as the content format).

{{{
function strip_newlines($text) {
	// Respectfully strip unnecessary newlines
	$textarr = preg_split(""/(<[^>]+>)/Us"", $text, -1, PREG_SPLIT_DELIM_CAPTURE);
	$stop = count($textarr); $skip = false; $output = ''; // loop stuff
	for ($ci = 0; $ci < $stop; $ci++) {
		$curl = $textarr[$ci];
		if (! $skip && isset($curl{0}) && '<' != $curl{0}) { // If it's not a tag
			$curl = preg_replace('/[\n\r]+/', ' ', $curl);
		} elseif (strpos($curl, '<code') !== false || strpos($curl, '<pre') !== false || strpos($curl, '<kbd') !== false || strpos($curl, '<style') !== false || strpos($curl, '<script') !== false) {
			$next = false;
		} else {
			$next = true;
		}
		$output .= $curl;
	}
	return $output;
}
}}}

Thoughts?"	jdub
Future Releases	12370	We need a smarter version of wp_title() and a few other template tags	hallsofmontezuma*	Template	3.0	normal	major	Future Release	feature request	accepted		2010-02-25T08:47:06Z	2011-09-06T16:22:50Z	"Look at Twenty Ten's `header.php` and the code that is needed to output the `<title>`. That's a bit silly.

I suggest we should have a helper function of some type to replace all of that. A smarter and more sophisticated version of `wp_title()`."	Viper007Bond
Future Releases	5998	Invalid Unicode characters	hakre	Charset	2.3.3	normal	major	Future Release	defect (bug)	assigned		2008-02-25T18:17:22Z	2011-02-10T23:09:25Z	"Wordpress does not check for invalid Unicode characters, such as the following:

U+FFFE
U+FFFF

When the pages are served up as XHTML, allowing these characters through generates an XML error. 

WordPress should filter out illegal Unicode code points.

Please see http://www.w3.org/TR/REC-xml/#NT-Char

Also, the regex
[http://www.w3.org/International/questions/qa-forms-utf-8 here] is
incorrect, see [http://intertwingly.net/blog/2008/01/02/Keeping-On-Your-Toes
this page].

"	shelleyp
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	19859	"""Bulk Edit"" Missing The Ability To Edit Tags"	gavinwye*	Quick/Bulk Edit		normal	normal	Awaiting Review	enhancement	accepted		2012-01-20T02:56:24Z	2012-12-20T00:41:06Z	"Though I can add, remove and edit ""categories,"" I cannot do such actions to ""tags"" inside of /wp-admin/edit.php

So basically, I'm interested in a ""bulk tag editing"" GUI for the WordPress admin.

===

I was hoping to find out the status of this feature (planned, not planned, etc) but it appears that no one has spoken about this feature on the WordPress Trac.

Is there any interest in adding this feature? And could the respondent please provide any details on why or why not?

Thank you for your time."	ademos
Future Releases	16173	Make the Calendar widget support custom post types	GautamGupta*	Widgets	3.1	normal	normal	Future Release	enhancement	accepted		2011-01-10T05:35:22Z	2011-09-22T02:14:00Z	The Calendar widget should have support for custom post types (much like how the tag cloud widget supports custom taxonomies) so that the plugins could just have `supports => array( ... 'calendar' ... )` and the calendar would display that post type in the option box (this is just an example, used in the patch I'm gonna attach, we may use some other arg, of course).	GautamGupta
Future Releases	15761	Bulk editing on posts without Javascript enabled results in the post being set to draft	garyc40	Administration	2.9	normal	normal	Future Release	defect (bug)	assigned		2010-12-10T09:03:35Z	2011-06-09T19:49:56Z	"Currently, Bulk editing is available without JavaScript being enabled.

The result of attempting to edit a post, is a redirect back to the posts page with the post being marked as a draft. No UI is offered for bulk editing.

This behaviour exists in trunk, 3.0, and 2.9 from my testing (havn't tested earlier versions).

The Bulk editing screen appears to work without Javascript for modification submittal, so it's possible that a non-js version would be possible."	dd32
Future Releases	8368	Scheduling post time behavior and language refinements	garyc40	Editor	2.7	low	minor	Future Release	enhancement	assigned	early	2008-11-26T17:56:19Z	2013-01-22T17:38:00Z	"On post editor, in publish module, at Publish Immediately-Edit. 

If click Edit, layer opens revealing the entry boxes for date and time of publication but still says Publish Immediately. Text should change to say ""Publish at:"" b/c it's weird if you change time and screen still says immediately until you click OK. 

Move OK button to the right side of module (submission buttons to the right as standard placement) with cancel to left (as with other places).

If you start to type in an alternate time then hit cancel, it reverts to publish immediately, which makes sense. If you have already scheduled the publish time but you decide to change it and start typing a different alternate time, if you hit cancel it does not revert to your originally scheduled time, but to publish immediately. It should revert to your previously saved schedule time. Should have a separate link to revert to publish immediately. "	jane
Future Releases	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
Future Releases	17409	Entity &amp; in menu title breaks XHTML 1.0 Strict validation	Florian	Menus	3.1.2	normal	normal	Awaiting Review	defect (bug)	new		2011-05-13T05:44:03Z	2011-05-13T05:44:03Z	"If i use &amp; in the menu title and use $my_menu =  wp_get_nav_menu_items(""my_menu"") and loop with foreach($my_menu as $menu_item) and connect for building the Menu on $menu_item->title, then an &amp; in the page title or on the menu navigation label is convertet to a simple &, witch returns the validation error ""xmlParseEntityRef: no name""."	Florat
Future Releases	15349	TinyMCE Internal Links Not Extendable	filosofo	General	3.1	normal	normal	Future Release	defect (bug)	new		2010-11-09T05:06:05Z	2010-12-07T19:04:58Z	It needs a couple filters and an action hook so we can modify and extend the content.	filosofo
Future Releases	14741	Allow MS sites to share a posts table	filosofo	General	3.0.1	normal	normal	Future Release	enhancement	new		2010-08-30T22:20:24Z	2010-08-30T22:20:24Z	"MS should allow admins to set a constant in `wp-config.php` that looks for all post objects to be in the main `posts` table.  When that constant is true, one could distinguish sites by a postmeta value.

This would make activity-stream like stuff across sites much easier to do as well as allow network-wide custom post types."	filosofo
Future Releases	15633	Add class to custom menu item when menu url is found in current page	filosofo	Menus	3.0.2	normal	normal	Future Release	enhancement	reviewing		2010-12-01T21:06:41Z	2011-01-15T04:42:44Z	"I found the need to identify custom nav menu items when the page is at a certain URL. For example,

Menu URL: http://mysite.com/wiki/
Page URL: http://mysite.com/wiki/Moose_Attacks

Anything below http://mysite.com/wiki/ is considered to be ""within"" http://mysite.com/wiki/ so I want to add a class to the menu item whenever that happens.

I made a rough patch with the following code, added just below line 381 of wp-includes/nav-menu-template.php in wordpress 3.0.2:


{{{
     if ( strpos($current_url, untrailingslashit($item_url)) == 0 )
          $classes[] = 'current_url_parent';
}}}

This probably brings up other problems, such as other custom menu items having that class, but I hope this can be considered. Thanks

Bradford"	elBradford
Future Releases	13905	No sanity check in map_meta_cap caps throws PHP notices	filosofo	Post Types	3.0	normal	normal	Future Release	defect (bug)	reopened		2010-06-15T16:29:45Z	2013-04-16T21:32:54Z	"`map_meta_cap` assumes that the ID which it's passed when evaluating `edit_post`, `edit_page` and the like actually belongs to a real post object.

In fact, it's quite possible that the object doesn't yet exist (creating a new object, perhaps) or doesn't exist any more (deleted), or that it has otherwise received a syntactically correct ID value that doesn't map to an existing post object (0, e.g.).

Instead, `map_meta_cap` should check that the post object actually exists before attempting to branch on its properties.

Patch also removes some apparent debugging comments."	filosofo
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	11847	wp_tag_cloud counts terms attached to future posts when used with custom taxonomies	filosofo	Taxonomy	2.9.1	normal	normal	Future Release	defect (bug)	reopened		2010-01-09T20:47:18Z	2010-10-29T00:27:24Z	"If you create a custom taxonomy, then attach some terms from that taxonomy to a future scheduled post, attachments attached to a future post, or unattached attachments, they will get counted toward the totals used to draw the tag cloud produced by wp_tag_cloud.

As a result, the sizes of the items in the tag cloud will be wrong, and the tooltips will show the wrong count. In some cases, if a particular term is only attached to future posts, clicking on the link in the tag cloud will result in a 404 because the main $wp_query correctly filters out future posts and unattached attachments when looking at the term's archive.

Correct behavior would be for get_terms to provide an option to filter out future posts and unattached attachments from its results the same as is done when looking at the term's archive."	fwiffo
Future Releases	19443	We can't use WordPress' editor inside a Thickbox	erayalakese	TinyMCE	3.2.1	normal	normal	Awaiting Review	enhancement	new	has-patch	2011-12-04T16:45:36Z	2011-12-05T00:09:24Z	"At my plugin's admin page, a have a EDIT link like this :


{{{
<a class=""button-secondary thickbox button"" title=""EDIT"" href=""<?php echo WP_PLUGIN_URL.'/plugin-name/'; ?>edit.php?id=<?php echo $ID;?>"">EDIT</a>
}}}


When user click it, it'll open href in a thickbox . Thickbox should contain '''/plugin-name/edit.php?id=1''''s content, for example.

It's working very well. But i want to add WordPress' rich text editor to edit.php . I'll explain my problem with a short video.

http://screenr.com/eoEs
"	erayalakese
Future Releases	10947	Problem on import <embed> codes on mt.php script	Edgar Gabaldi	Import	2.8.4	normal	normal	WordPress.org	defect (bug)	new		2009-10-12T16:59:13Z	2012-05-24T22:33:11Z	"I'm having trouble making the import of a file exported by CMS Movable Type.

All posts, categories, comments, users are imported correctly. The problem is that there are blocks of code in posts with the tag <embed> that are not being imported."	edgabaldi
Future Releases	15918	wpautop() breaks inline tags on the same line as block tags	dunno	Formatting	3.0.3	normal	major	Future Release	defect (bug)	new	early	2010-12-20T16:01:31Z	2012-04-11T15:22:31Z	"Hi guys! I've got latest WP installation (3.0.3) and found strange bug in posts parser.

Create article with following HTML:

{{{
<div class=""wassup""><a href=""#"">WP IZ ASSUM</a></div>
}}}

Browser will get: 

{{{
<div class=""wassup""><a href=""#"">WP IZ ASSUM</a></div>
}}}

All seems to be fine! Now get rid of unnecessary div.

Create article with following HTML:

{{{
<a href=""#"">WP IZ ASSUM</a>
}}}

Browser will get: 

{{{
<p><a href=""#"">WP IZ ASSUM</a></p>
}}}

Dunno why there is extra <p> but who cares. All seems to be OK.

Create article with following HTML:

{{{
<figure><a href=""#"">WP IZ ASSUM</a>
</figure>
}}}

Browser will get:

{{{
<figure><a href=""#"">WP IZ ASSUM</a><br />
</figure>
}}}

Now isn't that cool? But check what is even cooler!

Create article with following HTML:

{{{
<figure><a href=""#"">WP IZ ASSUM</a>
<figcaption>NO IT'S BUGGY AS HELL</figcaption>
</figure>
}}}

Browser will get:
{{{
<figure><a href=""#"">WP IZ ASSUM</a></p>
<figcaption>NO IT’S BUGGY AS HELL</figcaption>
</figure>
}}}

Wow! Say hello to invalid markup and rendering problems! Auto-closing of tags turned off. No matter of the settings I still get this nice messed up html. WYSIWYG turned off also."	retrib
Future Releases	17191	Importing the same content duplicates your custom menus	duck_	Import	3.1	normal	minor	WordPress.org	defect (bug)	reviewing		2011-04-20T15:03:40Z	2012-09-12T03:47:39Z	"When I import from one site to another, the importer will notify you if you have duplicate posts but will not import them, as expected, but it does duplicate your custom menu's.

I'm not sure if this is the desired result."	zanematthew
Future Releases	15217	wp importer trunk regression: no longer accepts gz files	duck_	Import	3.1	normal	normal	WordPress.org	defect (bug)	reopened		2010-10-26T04:16:21Z	2010-10-26T18:41:24Z	"wordpress-importer trunk r304267 no longer accepts gzipped WXR files.

This is a regression from the current wordpress-importer importer, v0.2 .

== Actual Results ==

""Sorry, there has been an error.
There was an error when reading this WXR file""

== Environment ==

WordPress Trunk r14360 (3.1-alpha) [[br]]
wordpress-importer trunk [http://plugins.trac.wordpress.org/browser/wordpress-importer/trunk r304267]

== Additional Details ==

Relates to #15197  ""WXR export/import umbrella ticket""

I notice that same error message ""There was an error when reading this WXR file"" is in two parts of the source. It might be better to make each error message more unique and add additional details."	lloydbudd
Future Releases	16294	Remote WXR Import	duck_	Import		normal	normal	WordPress.org	enhancement	reviewing		2011-01-19T01:02:00Z	2012-09-10T10:19:03Z	The attached patch allows a user to submit a URL pointing to a WXR import file, rather then uploading it. The purpose of this is to allow people to import a WXR file that is larger then their server's max_upload_size/max_post_size php.ini settings.	belaraka
Future Releases	14039	Consolidate strings with same meaning but different wording	demetris	Text Changes	3.0	normal	normal	Future Release	enhancement	assigned		2010-06-22T08:14:30Z	2012-11-19T16:52:00Z	"While translating WordPress I often come upon couples or triplets of strings that mean the same thing but are worded differently.  I would like to start consolidating such strings by selecting a preferable version and replacing the other instances with it.

Here is one example:

 *  You are not allowed to edit this page.  <- The one to keep. 
 *  Sorry, you cannot edit this page. 
 *  Sorry, you do not have the right to edit this page.

Here is another:

 *  Submit Comment
 *  Post Comment  <- $label_submit in comment_form()

Before making any patches, I will post all cases here for review and feedback.

The milestone for this would be 3.1, but it seems that I have been designated an “unknown Trac user” and I cannot set milestone and priority."	demetris
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	14049	Upgrade takes an hour to complete due to repeated 30-second FTP timeout	dd32*	Filesystem	3.1	normal	normal	Future Release	defect (bug)	accepted		2010-06-22T17:56:22Z	2011-05-02T06:54:32Z	"On my FreeBSD server (hosted by ISP pair.com), the built-in upgrade feature of WordPress takes at least an hour to complete.  I debugged the problem, and it turns out to be due to a mismatch between the FTP responses WordPress is expecting vs. the FTP responses FreeBSD is actually sending.

(Attached is a dump of phpinfo() from the machine on which I am seeing this problem.)

Steps to reproduce:
1. Clean WordPress installation on FreeBSD
2. Go to the Dashboard, then click Updates
3. Click ""Re-install Automatically""
4. Enter hostname, user name, and password; leave Connection Type as FTP; click Proceed

Actual result:
The update eventually completes successfully, but it takes an extraordinarily long time -- at least an hour.

Expected result:
Should finish much more quickly than that.

I debugged this, and here is what is happening:

- My PHP installation ends up using the ""ftpsockets"" filesystem to do the update.  (If necessary, you can force the use of that filesystem for testing purposes by adding ""define('FS_METHOD', 'ftpsockets')"" to your wp-config.php.)

- Every time anyone calls WP_Filesystem_ftpsockets->exists() to see if a file exists, that function calls ftp->is_exists(), which calls ftp->file_exists() in wp-admin/includes/class-ftp.php.

- That function tests for the existence of a file by sending the FTP command ""RNFR"" (rename from) across the FTP connection.  If the RNFR command succeeds, then the assumption is that the remote file exists; if it fails with an error message, then the assumption is that the remote file does not exist.

- Immediately after sending the RNFR command, if the RNFR succeeded, then is_exists() calls abort(), to send an ABOR -- I'm guessing this is intended to abort the rename.

- However, this is where things go bad.  FreeBSD replies to the ABOR command with ""426 Nothing to abort"".  WordPress's abort() function then attempts to read one more line, but there is nothing to read, so that read attempt times out after 30 seconds.

Here is the way the whole ""exists()"" conversation looks when it works correctly on my Mac:

{{{
PUT > RNFR /Users/mike/Sites/wordpress/ 
GET < 350 File exists, ready for destination name 
PUT > ABOR
GET < 225 ABOR command successful. 
Remote file /Users/mike/Sites/wordpress/ exists
}}}

And here is the way the conversation looks when it times out on my FreeBSD machine:

{{{
PUT > RNFR /usr/www/users/morearty/blog2/ 
GET < 350 You may attempt to rename /usr/www/users/morearty/blog2. 
PUT > ABOR 
GET < 426 Nothing to abort.
[... 30-second delay here, as abort() attempts to read one more line ... and then:]
abort: Read failed
}}}
"	mmorearty
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	11623	review options list and update sanitize_option()	dd32*	Security	2.9	normal	normal	Future Release	defect (bug)	accepted	early	2009-12-26T01:22:13Z	2010-11-13T01:18:42Z	"A lot of options have been added since 2.0.5, and as a result, not all of them have been added to {{{sanitize_option()}}}

Ideally, Options which are to be (int) or absint() should have a filter applied to them here.

Attached patch is for the first option thats brought this up, 'start_of_week' which is tested to be int in some function uses, ignored elsewhere.

I've set this to security as its preventive security.."	dd32
Future Releases	12682	Multiple password reset messages	dd32*	Users	2.9.2	normal	normal	Future Release	feature request	accepted		2010-03-23T15:51:01Z	2011-01-07T00:15:50Z	"There's a security flaw mentioned in #10006: an attacker can bother users with password reset messages.

The problem was reported on Russian support forums by the user receiving hundreds of such messages on his email address. He managed to solve it himself.

He also proposed to introduce some kind of timeout for password resetting. Is it possible?"	SergeyBiryukov
Future Releases	7395	Plugins within a folder (in SVN) should be moved up a level in our plugin upgrader	DD32	Administration	2.6	high	normal	Future Release	enhancement	new		2008-07-24T04:15:58Z	2010-02-13T02:02:12Z	The Paged Comments plugin exists in SVN under a 'paged-comments' directory.  Since the auto-upgrader puts plugins into a directory based on their slug, this results in the plugin being under two 'paged-comments' directories.  We should be able to identify when a plugin's trunk (or current branch) directory contains only another directory, and move the whole plugin up a level.	markjaquith
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	20652	Install plugins with FTP upload, virtual subdomain, bad base dir?	dd32	Upgrade/Install	3.3.2	normal	normal	Future Release	defect (bug)	reopened	needs-unit-tests	2012-05-10T12:02:48Z	2013-05-21T19:58:48Z	"Hi anybody!
I have problem with install plugins with FTP module in WP.

Everything show as OK, but plugin directory is bad. I have subdomain

sub.something.com - this is virtual subdomain from mod_rewrite

dirs are

/www/something.com/something.com[[BR]]
/www/something.com/sub.something.com - here is WP installation, subdomain is virtual from rewrite in httpd.conf

After install - WP say everything OK - but one thing is bad.[[BR]]
Upload is in bad directory - plugin I can found in[[BR]]
/www/something.com/something.com/plugins[[BR]]
no in /www/something.com/sub.something.com/plugins[[BR]]

Is here some way to fix it automatticaly or I can must edit config and basedir of ftp? Why is here this bug?

Thank you !

Pavel
"	rajcz
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	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	10787	Email administrators that an update is available for core|plugins|themes	dd32	Upgrade/Install	2.9	normal	normal	Future Release	task (blessed)	reopened	early	2009-09-15T08:44:47Z	2012-12-03T23:50:09Z	"Inspired by the recent 'email notifications for updates' plugins discussion on wp-hackers/other forums, I'd like to propose the functionality actually be included in core.

I'm thinking of a daily email (Or perhaps, even when WordPress does the update checks) that says along the lines of:

{{{
WordPress would like to notify you that you have 3 updates available:
WordPress 2.9.1
Plugin: Super Plugin 4
Theme: My Theme
}}}

Only email when the updates havn't changed since last email.

Core potential? Or leave it for plugin material?"	dd32
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	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	17642	hook for category edit needed	cardy_web	Administration	3.1.2	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-06-01T16:44:50Z	2011-06-01T16:44:50Z	"I think is needed an hook inside admin-ajax.php (line 1226) case 'inline-save-tax'
When you use ""quick edit mode"" to edit category no hooks get involved so function hooked into {action}_category are never called.
Instead everything work well using classic edit mode"	cardy_web
Future Releases	20456	Creation of new blogs and search for blogs missing	CaputoJen	General	3.3.1	normal	major	Awaiting Review	defect (bug)	reviewing		2012-04-16T14:50:53Z	2012-04-16T14:51:32Z	"Hello:

I recently upgraded to WordPress 3.3.1.  After doing so users have lost the functionality of creating a new blog the link redirects to another page(although admins can do it) and you can no longer search for existing blogs.  I have read the forums, posted to the forums and searched the internet for a reasonable explanation. I have found nothing describing this problem.  I have checked the appropriate settings and everything is turned on for users to create blogs.  At this point, I believe this may be a bug.  This problems occurs using all mainstream browsers on Mac and PC.  Please help as I am not sure what could be causing this issue and my search to find a plausible explanation has turned up nothing!"	CaputoJen
Future Releases	20958	Add to the Template Hierarchy the 410 error page	byteee	General		normal	normal	Awaiting Review	feature request	new		2012-06-14T16:32:57Z	2012-06-14T16:32:57Z	"In my last project where I migrate a web from asp to wordpress, I have some pages that not longer exists. Normally, we do a 301 redirection to the home page or some other place. But digging a little in google, if we get a page that not longer exists, its better to return a 410 response code instead of 301 code (talking about SEO aspects).

I did it manually following this post: [http://otroblogmas.com/retornar-410-wordpress/]

I think that we can include in the Template Hierarchy the 410.php file to show it when we are getting a page that not longer exists. "	byteee
Future Releases	17460	WP Updates througth SSH Script	bugdev	Administration	3.2	normal	normal	Awaiting Review	feature request	new	dev-feedback	2011-05-16T19:57:14Z	2011-05-16T20:45:56Z	"The current WP Update engine is very unsecure, because if there is a webserver issue or a connection timeout, memory overflow, connection issue than the wordpress update is corruptes.

More secure the update will be if we can do/execute a php script or ssh script througth the terminal, what also gives advanced informations about update errors ect."	bugdev
Future Releases	19945	Bug in ../wp-includes/widgets.php	Barti112	Widgets	3.3.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-02-02T08:22:34Z	2012-07-05T14:21:33Z	"in this file there are at some places the following code:

$widget = array_merge($widget, $options);

it is possible that $options is not an array and i become a php-warning.

i think better is to check the arrays before you use this function:

if(is_array($widget) && is_array($options)){
  $widget = array_merge($widget, $options);
}
"	Barti112
Next Release	24364	"Fix  autocomplete=""off"" in Chrome"	azaozz	Administration		normal	normal	3.6	defect (bug)	reopened		2013-05-18T22:45:28Z	2013-05-23T19:25:57Z	"Seems latest Chrome doesn't respect autocomplete=""off"" on <input type=""password"" /> fields. This is a problem in forms where the user has to choose a password like the Profile and Edit User screens. 

When the user wants to change a setting on the Profile screen, the first password field is auto-filled. That results in error on submitting the form: ""ERROR: You entered your new password only once...""."	azaozz
Future Releases	17391	Alternative color schemes and theme settings in editor styles	azaozz	Editor	3.2	normal	trivial	Future Release	defect (bug)	assigned	early	2011-05-12T13:14:56Z	2012-01-14T19:10:10Z	"Hello there. 

There is no support for links color change in editor-style.css. 
If you change it in Theme Options, you will see the same:

{{{
a {
	color: #1b8be0;
	text-decoration: none;
}
}}}

As we want the editor to be WYSIWYRG, maybe we should include this change in editor-style.css too. 

I have tried to do that with `add_editor_style()`, but it is only intended for .css archives. 
I have tried to add it as a filter extending `twentyeleven_print_link_color_style` in `mce_css` and `tiny_mce_before_init`, unsuccessfully.  

All ideas for what can I use to make tinyMCE read the options are welcome. "	bi0xid
Future Releases	18820	Formatting bar loading experience is subpar	azaozz	Editor	3.2.1	normal	normal	Future Release	enhancement	reopened		2011-09-29T21:51:41Z	2011-11-18T07:23:24Z	"When you save a post, the way the formatting bar loads in (Visual and HTML both) is subpar. It pops in really late, and shoves your post content down.

Screencast: http://s3.amazonaws.com/txfx/screencasts/Formatting-Toolbar.mov

Let's make this better."	markjaquith
Future Releases	16284	Remove the wpdialog plugin from TinyMCE	azaozz	Editor	3.1	high	normal	Future Release	enhancement	new		2011-01-18T14:26:28Z	2011-01-18T14:26:28Z	"Combining TinyMCE with jQueryUI is not a very good idea IMHO:

 * TinyMCE has all the functionality to create dialogs which is native, more extended and seems more robust than jQuery UI.
 * The reason why most dialog type scripts use an iframe is to remove any possibility of conflicts with the parent page. In out case such conflict might be introduced by a plugin that alters the edit screen.
 * There were suggestions some time ago to stop using jQuery UI in WordPress admin and replace it with one of the other jQuery plugins with similar functionality that are a lot more concise and robust."	azaozz
Future Releases	17105	HTML 5.0 support	azaozz	Formatting	3.2	normal	normal	Future Release	defect (bug)	new		2011-04-10T19:11:46Z	2012-05-30T22:58:25Z	"All HTML 5.0 block tags have been added in both versions of wpautop(), even tags that aren't fully supported in any browser yet and as of [17625] TinyMCE recognizes all HTML 5.0 tags too.

This ticket is for correcting issues with the HTML 5.0 support in WordPress' general workflow (writing, editing, formatting) and writing testcases for it."	azaozz
Future Releases	19120	Interim login needs some work	azaozz	General		normal	normal	Future Release	defect (bug)	assigned	early	2011-11-02T22:46:42Z	2012-05-02T19:43:33Z	"A CSS style causes a white 20px stripe at the top of the otherwise gray interim login screen.

That should go, and azaozz thinks the popup should as well.

3.3 for now, but the rest may be punted by azaozz."	nacin
Future Releases	21281	"RTL wysiwyg ""padding""/""indention"" action is not works as expected."	azaozz	TinyMCE	3.4.1	normal	major	Awaiting Review	defect (bug)	assigned		2012-07-15T08:33:06Z	2013-02-01T16:11:41Z	"By clicking the padding button(for indention) the action not works - it warpped the text by ""p"" element with '''padding-left''' insted or '''padding-right''' in RTL."	AlmogBaku
Future Releases	18172	Two lay-out buttons active at the same time	azaozz	TinyMCE	3.2.1	normal	minor	Awaiting Review	defect (bug)	reviewing		2011-07-19T11:26:49Z	2012-06-29T13:50:48Z	"1) Click on the center button for writing in the middle. It doesn't matter if you write something or not.
2) Upload a image and line it out at the left or right side.
3) When you select the image two buttons are active. One for the text and one for the image...

(See screen)
"	JonezJeA
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	11378	"Add ""Remove"" link to Widget instances which moves them to ""Inactive"" area"	azaozz	Widgets	2.9	low	minor	Future Release	defect (bug)	new		2009-12-10T08:53:43Z	2010-03-22T23:21:04Z	"Per comments on #10379, we should have a ""Remove"" link on Widget instances that moves them to the inactive area."	markjaquith
Future Releases	12342	New widget option after calling register_widget creating empty widget	azaozz	Widgets	2.9.2	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-02-23T00:36:39Z	2010-11-13T07:45:48Z	"After I register a new widget class that has never been registered before, navigate to the widgets.php admin page and allow the option to be created automatically. The option value looks like this as serialized data:

{{{
a:2:{i:2;a:0:{}s:12:""_multiwidget"";i:1;}
}}}

As you can see there is an empty widget in there for some reason. Basically the unserialized option value looks like the following as an array:

{{{
array( '2' => array(), _multiwidget => 1 );
}}}

This is odd behavior since the first multi number has always started at 2, but with that previous array in there it starts at 3, and randomly which is what irks me. i can't seem to find when it happens or a pattern, so naturally this feels like a bug.

As this does not seem to break anything with the core functionality of WordPress, I would say this is normal priority. What this does do is pose many questions for those of us that dive deep into the Widget API, where our plugins and the functionality of them are dependent on how these things work. My widget plugin is quite large, and I need to know if I can depend on the first multi number of a widget when the class is first registered.

If this is not a bug, and normal functionality, I apologize, and would like to ask for a heads up on the subject.

Thank You,
Jim Isaacs"	jimisaacs
Future Releases	12133	get_field_id() and get_field_name() break when passed a name in array format	azaozz	Widgets	2.9.1	normal	minor	Future Release	enhancement	new		2010-02-05T02:17:10Z	2013-01-21T23:13:01Z	"`get_field_name()` and `get_field_id()` are member functions of the widget API which generate the names and ids for fields on the widget admin screen.

A custom widget cannot use an array format name with this function.

For example, 'myfield[]' or 'myfield![3]' is a valid name for an input field, but this name cannot be passed to `get_field_name()` as the function will strip right square brackets from the name.

Patch upcoming when I find the time."	johnbillion
Future Releases	20178	wpdb class : provide a disconnect / connect to db functions	arena	General	3.4	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-03-05T13:16:21Z	2012-03-05T16:28:46Z	"some hosts automatically disconnect mysql after a short while.
I think it could be interesting to have in wpdb a disconnect and connect functions."	arena
Future Releases	21610	ssh2/sftp doesn't work with chrooted/openssh sftp-internal user accounts (no shell)	albert@…	Filesystem	3.4.1	normal	normal	Awaiting Review	feature request	new		2012-08-16T16:06:35Z	2012-09-10T18:20:52Z	"The current wordpress 3.4.1 wp-admin/includes/class-wp-filesystem-ssh2.php  code will crash php or spin in an endless loop when someone supplies ssh/sftp credentials (username/password) to an (open)ssh server where users don't have a shell and are chrooted to their home directory e.g. by using openssh's sftp-internal server and ChrootDirectory functionality.
There is no neat fix for the code in the WP_Filesystem_SSH2 class. I've implemented a new WP_Filesystem_SFTP class making use of the portable phpseclib library.

At this moment it is necessary to change a line in wp-admin/includes/file.php to be able to use WP_Filesystem_SFTP.
Attached is the code for this new class up for review or for anyone with the same problem."	albert@…
Future Releases	11082	Saving an empty draft dumps user out to edit.php	akhilasuram	Editor	2.7	low	minor	Future Release	defect (bug)	assigned		2009-11-05T15:16:46Z	2012-12-13T20:09:23Z	"ENV: wp trunk r12138 (2.9-rare)

When a user starts up the editor for a new post and attempts to save a post with no title and no content, WordPress dumps the user back out to the list of posts in edit.php with no message or indication as to why this happened. You can edit the publish information (date, status, etc.), tags, and categories, but as long as there is nothing for either the post title or the post content, the behavior is the same.

It's expected that a post with no content whatsoever wouldn't be saved (there's nothing there!), but would be nice if the behavior were easier to understand or explained why nothing was happening."	markel
Next Release	24553	"""{user} is currently editing"" messages on post listing screen causes items on screen to move around"		Administration	trunk	normal	normal	3.6	defect (bug)	new		2013-06-10T11:22:20Z	2013-06-17T18:47:33Z	"A seemingly innocuous feature that could get very annoying for users.

When a user is editing a post, the post listing screen displays a ""{user} is currently editing"" message below the post to other users.

[[Image(http://i.imgur.com/trLry65.png)]]

The appearance and disappearance of this message on each post (which happens periodically via Heartbeat) causes the table row height to change significantly.

Imagine a site with several editors working simultaneously. The post listing screen can jump around enough that it can cause people to mis-click a link if one of the messages appears or disappears just as you go to click a link.

I've already mis-clicked once and I'm only working on a test site with two dummy users. UI elements that cause other elements to move around when their state changes is bad.

Not sure how we can address this. The message is a sizable UI element that we can't really reserve space for. Suggestions?"	johnbillion
Next Release	24447	Avoid losing data after nonces expire		Administration		normal	normal	3.6	defect (bug)	new		2013-05-29T07:55:35Z	2013-06-05T22:42:40Z	"Happens when an admin page containing a form is left open for more than 24 hours and the user decides to submit the form. This is quite rare for most admin pages as the users typically spend short time there. However this can happen on the Edit Post screen too despite that we refresh the basic nonces every `wp_nonce_tick` (12 hours):

- The user starts new post.
- At some point the Internet connection is lost.
- The user decides to finish later and puts the computer to sleep (closes the laptop, etc.).
- The user decides to continue writing more than 24 hours after that.

At this point all nonces have expired and cannot be updated as we've missed the previous nonce_tick update."	azaozz
Next Release	24131	Fix post previews for multisite with domain mapping		Administration		normal	normal	3.6	defect (bug)	new		2013-04-18T22:51:54Z	2013-04-24T02:45:56Z	Currently when previewing latest changes we create a nonce in the admin, then redirect to the front-end and check that nonce on 'init' before showing the preview. This fails sometimes on multisite with domain mapping as they may use JS redirects to log the user in on the front-end.	azaozz
Next Release	21795	Menu collapse option not saved correctly		Administration	3.5	normal	normal	3.6	defect (bug)	reopened	reporter-feedback	2012-09-04T23:39:17Z	2013-04-08T01:00:54Z	"The menu collapse option is not saving correctly when at a resolution > 900px. When collapsing and them re-expanding the menu, the menu auto collapses on each new page load. It's caused by the script deleting the folded setting but not actually setting the unfolded setting as far as I can tell.

The attached patch works for me."	griffinjt
Next Release	23930	Screen option for post formats UI		Administration	trunk	normal	normal	3.6	feature request	new	needs-unit-tests	2013-04-03T18:28:10Z	2013-05-14T18:16:58Z	"As discussed in IRC, there should be a screen option for the post format UI on the post editing screen.

Nacin would like the UI to be hidden by default when the current theme does not support post formats and there are no non-standard format posts in the database. In this case, the UI would have to be enabled by the user. The UI would need to be automatically enabled when a theme that supports post formats is activated.

Willing patchers, make yourself known.

See also #23929

IRC logs:

https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-02-18&sort=asc#m558297

https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-04-03&sort=asc#m588002"	johnbillion
Next Release	23216	"Create ""WP Heartbeat"" API"		Administration		normal	normal	3.6	task (blessed)	new	needs-docs	2013-01-16T20:41:50Z	2013-06-05T03:15:22Z	"The purpose of this API is to simulate bidirectional connection between the browser and the server. Initially it will be used for autosave, post locking and log-in expiration warning while a user is writing or editing.

The idea is to have a relatively simple API that sends XHR requests to the server every 15 seconds and triggers events (or callbacks) on receiving data. Other components would be able to ""hitch a ride"" or get notified about another user's activities.

In the future this can be used to block simultaneous editing of widgets and menus or any other tasks that require regular updates from the server."	azaozz
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	24552	Taking over a locked post does not always load the most recent revision		Autosave	trunk	normal	major	3.6	defect (bug)	new		2013-06-10T10:33:44Z	2013-06-11T04:47:54Z	"Steps to reproduce:

 1. Open up a post for editing, and make some changes to it. Do not save the changes.
 2. Open up the same post for editing using a different user account (in a different browser![1]) and click the 'Take over' button when you get the post lock modal.
 3. Note that the post that loads is not the most recent autosave of the post, but equally importantly you are not shown the message stating this.
 4. Reload the editing screen and you'll be presented with the ""There is an autosave of this post that is more recent than the version below."" message.

Related: #23697

----

![1] The simplest way to do this is to use an Incognito browser window (and [http://wordpress.org/plugins/user-switching/ User Switching]) so you can be logged in as two accounts simultaneously. "	johnbillion
Next Release	23665	Create one autosave per user		Autosave		normal	normal	3.6	enhancement	new		2013-03-02T08:19:35Z	2013-04-03T04:37:51Z	"Currently when autosaving drafts we overwrite them, when autosaving published posts, we keep one autosaved revision. This works well as long as there is only one post author.

Having per-user autosaves will affect only sites with many authors/editors. It will avoid overwriting when more than one user edits a post, provide better audit trail, and let us auto save data stored in the browser even if another user is editing at that moment.
"	azaozz
Next Release	23220	Extend autosave to use the browser's local storage in addition to saving to the server		Autosave		normal	normal	3.6	task (blessed)	new		2013-01-16T22:33:43Z	2013-06-09T00:45:02Z	"There are several types of local (DOM) storage in the modern browsers. Most suitable is the `localStorage` as it's persistent and supported in all browsers back to IE8.

The idea is to save the content in local storage every 10 seconds and push to the server every two minutes. When the server responds and there are no errors, we empty the local storage and start again. The local storage will also be emptied when the user saves the post. Then every time the user visits the admin we can check if the local storage is not empty and offer to recover from there or show a revision diff.
"	azaozz
Next Release	24555	Twenty Thirteen: First image in featured gallery can be blurry if in landscape		Bundled Theme	trunk	normal	normal	3.6	defect (bug)	new	dev-feedback	2013-06-10T18:20:53Z	2013-06-12T22:54:03Z	"[https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-06-10&sort=asc#m625858 Reported in IRC], if a landscape oriented image happens to be the first image in a featured gallery, it appears blurry. Since the medium image size does not crop, the image is most likely not 300px high. This causes the image to be magnified and to appear blurry.

We previously discussed the issue of the best image size to use in IRC, I couldn't find the log in a reasonable amount of time though."	obenland
Next Release	24475	The empty pattern attribute causes Webkit (Chromium 25) to style the URL and Email HTML5 form fields always with :invalid styles.		Comments	trunk	normal	normal	3.6	defect (bug)	new	dev-feedback	2013-05-31T23:20:55Z	2013-06-01T09:09:42Z	"Chromium Version 25.0.1364.160 Ubuntu 13.04 (25.0.1364.160-0ubuntu3)

`input type=""email"" pattern=""""`
`input type=""url"" pattern=""""`

This code is generated for the HTML5 form in Wordpress.

I am using bootstrap 3.0 CSS and it styles the `input:focus:invalid:focus` and `input:focus:invalid` with a red border and text. The issue is using the empty pattern variable the browsers marks everything as invalid. I simply removed the `pattern=""""` and the validation works, the browser then uses default pattern and the styles get removed as soon as the input in that fields are valid. I not tested it with manual pattern that will of course work as well.

Not sure what the reason is you used empty pattern, I am new to this thing, but you might want to remove it or include some default pattern to be able to correctly validate the Email and URL."	nico23
Next Release	24450	Weak CSS selectors for WP Editor styles		Editor	trunk	normal	normal	3.6	defect (bug)	new		2013-05-29T17:40:55Z	2013-05-30T22:32:37Z	If a theme or plugin has an ID definition selector for table rows (#page table tr td), it overrides WP Editor's CSS selector ( .wp_themeSkin tr.mceFirst .mceToolbar tr td ), making the editor toolbar inherit the theme's styles for table data, which can look unsightly. 	ericlewis
Next Release	24197	wp_localize_script() doesn't work for jquery handle		General	trunk	normal	major	3.6	defect (bug)	new	dev-feedback	2013-04-25T20:23:59Z	2013-05-22T17:27:12Z	"Here's another odd bug introduced by WP 3.6 latest development version.

I'm using the following code: [http://snippi.com/s/s058ms7]

In WP 3.5.1 everything worked as it should, and wp_localize_script returned the ""icy_ajax"".

Now, in 3.6-beta1-24067 , I get the following error in my console: ReferenceError: icy_ajax is not defined 

Just try and test it and let me know of any solution :-)

"	IcyPixels
Next Release	24547	"""Go to All %s"" string not ready for i18n"		I18N	trunk	high	major	3.6	defect (bug)	new	dev-feedback	2013-06-09T18:07:29Z	2013-06-10T13:12:13Z	"The ""Go to All %s"" string ([http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/post.php#L1214 location] is marked with %s being any post type: ""Posts, Pages, etc."".

As it is, translators cannot do a direct translation of it: as with any ""any post type""-related string, it should be known that depending on the language, some post types can have a ""gender"", and therefore cannot use the same sentence structure.

For instance, in French, Post is Article, which is masculine, when Page is Page, which is feminine. Translation for this string would then either be ""Aller à tous les articles"" or ""Aller à toutes les pages"".

Either the string is reworked, or translators should be advised to use a sentence structure that works for any content type."	xibe
Next Release	22623	Some string tweaks - duplicity, context, mistake		I18N	3.0	normal	normal	3.6	defect (bug)	new		2012-11-28T20:56:41Z	2013-01-16T00:03:41Z	"1) String ""Path"" has a little different meaning for TinyMCE (HTML position) and Multisite list sites column (subdirectory address). Can we have a context?

2) When you click ""Deactivate"" action link bellow any site (in Multisite admin), site is marked as ""Deleted"" instead of ""Deactivated""? You can ""Activate"" deleted site? Strange...

3) We have strings ""No results found."" (twice) and ""No matches found."" One string would be better instead of three similar strings?

4) String ""Show header text with your image."" is not accurate. You can show header text without header image."	pavelevap
Next Release	23341	Spell checker in the editor shows languages not supported by google spellchecker like hebrew		I18N	3.5	normal	normal	3.6	defect (bug)	reopened		2013-01-31T13:56:06Z	2013-02-01T05:52:57Z	"The spell checker in the editor uses via tinymce code the google translate service. Problem is that WordPress code assumes that the service supports all languages

{{{
/*
translators: These languages show up in the spellchecker drop-down menu, in the order specified, and with the first
language listed being the default language. They must be comma-separated and take the format of name=code, where name
is the language name (which you may internationalize), and code is a valid ISO 639 language code. Please test the
spellchecker with your values.
*/

$mce_spellchecker_languages = __( 'English=en,Danish=da,Dutch=nl,Finnish=fi,French=fr,German=de,Italian=it,Polish=pl,Portuguese=pt,Spanish=es,Swedish=sv' );

/*
The following filter allows localization scripts to change the languages displayed in the spellchecker's drop-down menu.
By default it uses Google's spellchecker API, but can be configured to use PSpell/ASpell if installed on the server.
The + sign marks the default language. More: http://www.tinymce.com/wiki.php/Plugin:spellchecker.
*/
$mce_spellchecker_languages = apply_filters( 'mce_spellchecker_languages', '+' . $mce_spellchecker_languages );
}}}

But google insist that they support only 12 languages http://support.google.com/toolbar/bin/answer.py?hl=en&answer=32703, therefor not any localization can localize it (ok it can, but it is pointless). The end result for hebrew is that any gibberish text thrown at the spell checker returns as good text.

"	mark-k
Next Release	24456	Make audio/video shortcodes consistent with embed		Media		normal	normal	3.6	defect (bug)	new		2013-05-29T21:18:27Z	2013-06-10T11:14:42Z	"The embed shortcode takes URL as its content, but a/v ones take an attribute — make both for both?

See: http://make.wordpress.org/core/2013/05/29/post-formats-ui-is-exiting-core-will-live-as-a-plugin/"	aaroncampbell
Next Release	24458	Remove attachment_url_to_postid()		Media		normal	normal	3.6	defect (bug)	new		2013-05-29T22:16:42Z	2013-06-14T10:27:16Z	"
For A/V shortcodes, include the attachment ID instead of just the URL, making attachment_url_to_postid() unnecessary.

Transition those IDs on import

Remove attachment_url_to_postid()

As per http://make.wordpress.org/core/2013/05/29/post-formats-ui-is-exiting-core-will-live-as-a-plugin/"	aaroncampbell
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	24449	Attachment display settings in the Media Library are ignored for audio and video inside 'Standard' post format and pages		Post Formats	trunk	normal	normal	3.6	defect (bug)	new	dev-feedback	2013-05-29T13:02:21Z	2013-06-18T15:11:01Z	"Sometimes both clients and I will upload audio and video files through the media uploader and link them to Attachment Pages so that people can do the old right click -> Save link as... thang.

Currently in trunk the Link to Attachment Page in the ""ATTACHMENT DISPLAY SETTINGS"" is ignored for audio and video and the new [audio] and [video] shortcodes are applied no matter what is selected.

I can understand that this is desirable behaviour in both the Audio and Video post formats to reduce confusion for the user but I think it would be acceptable to remove those shortcodes in the Standard post format and for Pages (and CPTs) as well. '''i.e. Give the user some control when acceptable.'''

To reproduce this upload either an .mp3 or .mp4 through the media uploader in a Standard Post format or in a Page and under ""ATTACHMENT DISPLAY SETTINGS"" choose ""Link To Attachment Page"" and the shortcodes for audio and video will be apply so that MediaElement.js will be triggered.

I'm not sure if this is the desired behaviour so I'll tag this as a 2nd-opinion."	sennza
Next Release	23863	Post Formats: allow filtering content_width per format in wp-admin		Post Formats		normal	normal	3.6	defect (bug)	new	dev-feedback	2013-03-25T20:55:33Z	2013-04-04T01:10:04Z	"On front-end a theme can filter {{{$content_width}}} like so:

{{{
function twentythirteen_content_width() {
	if ( has_post_format( 'image' ) || has_post_format( 'video' ) ) {
		global $content_width;
		$content_width = 724;
	}
}
add_action( 'init', 'twentythirteen_content_width' );
}}}

But ... functions called in wp-admin that use the global {{{$content_width}}} variable won't be changed.

For example, using trunk and Twenty Thirteen theme:

1. Create a new post, set to Image post format
2. Click Add Media to insert an image
3. Upload an image at least 800 px wide
4. You'll see in ""Attachment Display Settings"" that width for the ""large"" size to insert to the post is 604 pixels and not 724.

Also, even if detecting a Post Format this way worked correctly on edit, it wouldn't work on first post creation because of how the UI uses JS to switch between the formats."	lancewillett
Next Release	24355	Post Formats: any allowed file type can be uploaded to an audio, video or image post		Post Formats	trunk	normal	normal	3.6	defect (bug)	new	close	2013-05-17T16:09:34Z	2013-06-11T13:21:42Z	"To reproduce:

1. Create a new post, select the video post format
1. Hit Select Video from Media Library
1. Choose Upload Files and upload an image
1. Hit Select Video

An image is inserted instead of a video, plus after saving, the dimensions constraints are not applied to the image because it's a video post format."	kovshenin
Next Release	24404	Allow get_the_post_format_image to return image without link		Post Formats	trunk	normal	normal	3.6	enhancement	new	dev-feedback	2013-05-23T20:34:41Z	2013-06-11T18:28:17Z	"When a user adds a link to an image post in the new post format UI, `the_post_format_image()` and `get_the_post_format_image()` functions will always return the image HTML wrapped in the link. 

There are a number of cases in which a theme or plugin author may want to get the image without the link. For example, the author might want to wrap both the image and the title in a link. Having a link wrapped around the image complicates this. 

I think we should either add a new parameter that allows the image to be returned without the link, or create two functions: one that returns the image with the link and one without the link. I personally find it a little misleading to use a function called `the_post_format_image()` and get an image wrapped in a link. 

Separating functions that allow for returning just the image and the image with the link is important for flexibility. I think that wrapping the image in a link is making a decision that the developer should make and is limiting the developer without good reason. This will lead to some weird workarounds that will decrease the stability of community code. Having two functions instead of one does not increase complexity, yet it improves the flexibility of the API.

I'm happy to work on this if people think it's worth adding."	tollmanz
Next Release	24423	Focus on post title field when title is empty		Post Formats	trunk	normal	normal	3.6	enhancement	new		2013-05-25T19:23:02Z	2013-05-27T00:02:44Z	"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
Next Release	24452	Extract Post Formats UI from Core		Post Formats	trunk	highest omg bbq	blocker	3.6	task (blessed)	new		2013-05-29T20:44:16Z	2013-06-17T22:19:45Z	"Per: http://make.wordpress.org/core/2013/05/29/post-formats-ui-is-exiting-core-will-live-as-a-plugin/

This is a tracking ticket for implementing the removal of post formats UI."	markjaquith
Next Release	24484	"Lose the ""remove"" support for media extraction functions"		Post Formats	trunk	high	critical	3.6	task (blessed)	new		2013-06-02T16:34:27Z	2013-06-10T19:34:45Z	See #24452 and http://make.wordpress.org/core/2013/05/29/post-formats-ui-is-exiting-core-will-live-as-a-plugin/	markjaquith
Next Release	24526	Compare two mode can't be triggered from the URL in the new revisions UI		Revisions	trunk	normal	normal	3.6	defect (bug)	new		2013-06-07T00:37:23Z	2013-06-07T02:52:26Z	"The revisions comparison UI in version 3.5 and earlier supported URL parameters to set the revisions to be compared by setting ''left'' and ''right'' query arguments. With the heavily-JS-dependent UI coming in 3.6, there isn't a way to link to specific comparison.

Shouldn't we use pushState to update the URL when comparing two revisions so users can continue to link to a chosen comparison? It can be helpful to share a link to a given comparison when collaborating on changes or auditing where a modification originated from, to name a few scenarios."	ethitter
Next Release	24388	Optimize revisions diff loading - especially when many revisions		Revisions	trunk	normal	critical	3.6	defect (bug)	new	dev-feedback	2013-05-22T20:16:48Z	2013-05-24T23:16:21Z	"Currently viewing the revisions page chokes the browser when there are many revisions (say over 50) - even with a lower number the browser seems overwhelmed by the numerous ajax requests fired to load the comparison diffs.

* limit the number of simultaneous ajax requests
* group diff requests to optimize loading and limit total number of calls when there are many revisions
* caching for diff calculations  "	adamsilverstein
Next Release	24425	Revisions cleanup		Revisions	trunk	high	normal	3.6	task (blessed)	new		2013-05-25T20:47:40Z	2013-06-16T15:18:45Z	"I'm looking over Revisions with Nacin and Koop. We think it needs a general cleanup, on the JS side, and for the Ajax endpoint. Tracking that on this ticket. This might run into some other tickets, but I didn't want to hijack them:

#24056
#24346
#24388"	markjaquith
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
Next Release	24189	{$taxonomy}_relationships cache can easily become stale when a term is updated.		Taxonomy	trunk	high	major	3.6	defect (bug)	new		2013-04-25T11:18:16Z	2013-04-26T02:35:03Z	"The {{{{$taxonomy}_relationships}}} cache stores the information about the terms associated with an object for a particular taxonomy.

If you update the term then we don't invalidate the cache and therefore a call to something like: {{{get_the_terms()}}} will return invalid data.

An example set of steps to reproduce (needs some form of persistent caching like memcache):

 1) Create a new tag and assign it to a post
 2) Use get_the_terms()
 3) Edit the tag to change the description
 4) Use get_the_terms() and find the old description is returned.

Very easy to reproduce in a unit-test.

Re-constituting the relationships cache for every object that is related to the term is probably going to be very expensive.

Maybe we should just switch to only caching IDs and then populating the term data from a different cache?
"	westi
Next Release	24445	Improve is_multi_author() performance		Template		normal	normal	3.6	enhancement	new		2013-05-28T20:49:24Z	2013-06-04T06:17:02Z	"I have 100k posts.

If I delete the function twentythirteen_body_class() - the home page loads in 1 second,
with this function the page loads in 4.4 seconds!
 
I use this for page load time:


{{{
add_action( 'wp_footer',             'footer_timer_stop', 1000               );

// Footer timer to show page load speed
function footer_timer_stop() {
	echo '<!-- stats: ' . get_num_queries() . ' queries. ' . timer_stop( 0 ) . ' seconds. -->';
}
}}}
 


This function is not so important and I think it should be removed."	alexvorn2
Next Release	24586	Headings don't fit in TinyMCE Format dropdown		TinyMCE	trunk	normal	normal	3.6	defect (bug)	new	close	2013-06-16T18:57:56Z	2013-06-18T19:53:32Z	"This is the second section down on the Bugs page at

http://gage.x10.mx/bugs/
----
Look for the exact title. 

The headings don't fit and are cut off in the drop-down box for the core editor for publishing posts and pages. This is also known as the ""paragraph drop-down,"" or the ""heading select drop-down.""

Picture is located on the bugs page. Also, I have moved the JetPack problem over to the Plugins Trac."	Gage Morgan
Next Release	24344	More Tag not visible in the Visual Editor		TinyMCE	trunk	normal	normal	3.6	defect (bug)	new		2013-05-15T10:23:54Z	2013-06-10T19:18:57Z	"When clicking on the ""Insert More Tag"" button in the WYSIWYG editor, the more tag line is not visible. The `<!--more-->` tag has been added & can be seen in the Text Editor but not in the Visual pane.

Both:
{{{
img.mceWPmore {
    background: url(""img/more_bug.gif"") no-repeat scroll right top transparent;
}
}}}
and:
{{{
img.mceWPnextpage, img.mceWPmore {
    -moz-border-bottom-colors: none;
    -moz-border-left-colors: none;
    -moz-border-right-colors: none;
    -moz-border-top-colors: none;
    border-color: #CCCCCC -moz-use-text-color -moz-use-text-color;
    border-image: none;
    border-right: 0 none;
    border-style: dotted none none;
    border-width: 1px 0 0;
    display: block;
    height: 12px;
    margin: 15px auto 0;
    width: 95%;
}
}}}
seem to be missing from content.css when checked using Firebug.

Using 3.6-beta3-24260 (lasest nightly 15/05/13) & Twenty Twelve. The issue has also been confirmed using other themes."	esmi
Next Release	17154	TinyMCE inserts spans with font-styles atributes		TinyMCE	3.1	normal	normal	3.6	defect (bug)	reopened	has-patch	2011-04-17T12:04:38Z	2013-05-15T21:38:38Z	"This is continuation of #14218 which seems to be not fixed in 3.1 and still exist even in current 3.2. Reproducing steps
1. Open WP in latest Chrome (any version) - and probably also in other webkit browsers
2. Create new post
3. create UL with clicking on bullet icon
4. type some Li elements
5. close ul with <- icon (in advanced tinymce line)
6. type some text
7. switch to html view or publish article and see the code, you will see something like

{{{
asdfasdfh
<ul>
	<li>asfasdfa</li>
	<li>asdfa</li>
	<li>asfd</li>
</ul>
<span style=""font-size: small;""><span class=""Apple-style-span"" style=""line-height: 24px;"">adfasdfasd</span></span>

<span style=""font-size: small;""><span class=""Apple-style-span"" style=""line-height: 24px;"">asfasd</span></span>

<span style=""font-size: small;""><span class=""Apple-style-span"" style=""line-height: 24px;"">
</span></span>
}}}

P.S.: i can't select Version 3.2 in the bug report properties
"	thomask
Next Release	23337	TinyMCE, webkit and backspace/linebreak/italic issues		TinyMCE	3.5.1	normal	normal	3.5.2	defect (bug)	new		2013-01-31T08:23:50Z	2013-04-30T08:42:07Z	"On WP 3.5.1 and nightly I notice irregularities in TinyMCE on webkit (Chrome, Safari).

When editing existing paragraphs in TinyMCE visual mode:

- After deleting a paragraph break, it is impossible to insert a single linebreak
- When deleting paragraph breaks, sometimes text will be wrapped in `<em id=""__mceDel"">...</em>`

Steps to reproduce:

1. In a new post, type: ""One[return]two[return]three"" (i.e. three paragraphs)
2. Position the caret before the word ""three"". Hit [delete] to merge paragraphs two and three.
3. Do a shift+return key combo, which should insert a single linebreak. Instead, a paragraph break is inserted.
4. Place the caret before the word ""two"". Hit [delete] to merge paragraphs one and two. The third paragraph is italicised. Viewing the HTML source will show that it has been wrapped in an `em` tag with the id `""__mceDel""`

Expected behaviour:

- After deleting the space between two paragraphs, shirt+return should insert a single linebreak.
- Text should not be italicised without the user having specified for TinyMCE to do so.

I can consistently reproduce this behaviour in Chrome and Safari. Firefox seems to work as expected.

I have tested with a clean install of WP 3.5.1 and the nightly build. I have tested on two different computers.

OS: OS X Lion
Browser: Chrome 24.0.1312.56, Safari 6.0.2"	jnicol
Next Release	24365	Suppressed errors during install		Warnings/Notices		normal	normal	3.6	defect (bug)	new		2013-05-19T12:18:35Z	2013-05-28T13:40:02Z	"Reported in http://wordpress.org/support/topic/36-beta3-24284-throws-a-stream-of-suppressed-errors-during-install:
{{{
PHP Strict standards:  Redefining already defined constructor for class WP_Widget in .../wp-includes/widgets.php on line 93
PHP Notice:  unserialize(): Error at offset 0 of 38 bytes in .../wp-admin/includes/upgrade.php on line 1420
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 589
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 622
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 644
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 655
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 662
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 675
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 675
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 696
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 702
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 708
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 720
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 733
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 746
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 760
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 774
PHP Strict standards:  Only variables should be assigned by reference in .../wp-admin/includes/schema.php on line 787
}}}"	SergeyBiryukov
Future Releases	23760	Cannot use spacebar to trigger OK button or links in Publish widget (eg. schedule settings)		Accessibility	3.5.1	normal	minor	Awaiting Review	defect (bug)	new		2013-03-13T16:23:43Z	2013-04-19T23:16:59Z	"When changing the scheduled publishing time of a post, the OK button after the time fields cannot be triggered by pressing spacebar.

The same applies to all buttons and links in the Publish widget on the Add New / Edit Post page. The Add button in the Tags widget on the same page can be triggered with space since WordPress 3.5. 

Steps to repeat:

1. Create a new post by navigating to wp-admin/post-new.php.
2. Click the underlined link in ""Publish immediately _Edit_"" in the Publish widget.
3. Click the last field (minutes).
4. Press Tab once to move focus to the OK button.
5. Press spacebar.

What happens is the screen scrolling down exactly as if Page Down was pressed.

What should happen is the same that happens when the button (or link) is clicked with mouse, which depends on the button (or link).

Tested on Windows XP & 7 and all the recent Firefoxes I can remember and Internet Explorer 9."	Daedalon
Future Releases	22682	Close Button Breaks in Customizer After Refresh		Accessibility	3.5	low	minor	Future Release	defect (bug)	new		2012-12-02T17:10:01Z	2012-12-04T04:43:17Z	"Steps to reproduce (keyboard only):
1. Open the theme customizer.
1. Tab past the top buttons.
1. Press F5.
1. Now try to use the Close or Cancel button.

Expected result:  Should be able to Close or Cancel.

Actual result:  The button can still be clicked, but it is broken for keyboard usage.

Found in 3.5-RC2-22961 using Chrome 23 and WinXP."	miqrogroove
Future Releases	20880	Keyboard navigation in Appearance > Header is broken		Accessibility	3.3.2	normal	normal	Awaiting Review	defect (bug)	new		2012-06-07T17:40:34Z	2012-06-08T06:27:11Z	"It's impossible to use the Appearance > Header section with the keyboard because the Enter button will submit the form using the top-most submit input, which is not always the Save Changes button. How to reproduce, in Appearance > Header, using Twenty Eleven:

1. Select one of the default header images
2. Check the Show header text with your image option
3. Enter #111 for Text Color
4. Click Save Changes

At this point everything looks fine, but here comes the trouble:

5. Enter #222 for Text Color and hit Enter

You'll notice that #222 hasn't been set as the Text Color, instead your chosen header image (in step 1) has been removed, as if the Remove Header Image button was clicked.

6. Enter #333 for Text Color and hit Enter

You'll notice that #333 hasn't been set as the Text Color, instead it's been set to #000 which is Twenty Eleven's default, as if the Restore Original Header Text button was clicked.

When both Remove Header Image and Restore Original Header Text buttons are not present, the Return key submits the form using Save Changes, as expected. It's not limited to Text Color, but any other element that can submit the form using the Enter key.

I've been facing the exact same problem when doing an options panel for a theme with multiple actions as submit buttons, still haven't found a good solution. Marked as 3.3.2 but I believe it's been around earlier.

Thanks!"	kovshenin
Future Releases	23562	Using Speech Recognition Software with the Add Media Panel		Accessibility	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-20T16:06:02Z	2013-02-20T17:59:42Z	"Linked to #23560 this ticket specifically concerns the speech recognition user's accessibility experience of the Add Media functionality.

I'm using Dragon Naturally Speaking with IE9 on Windows 7 - a typical setup as Dragon works best with IE.

Within the Edit Post screen I can use Dragon to action the Add Media link successfully. The command in Dragon for such an action is ""Click Add Media"". This works, but then I run into the following problem:

* With the exception of Set Featured Image, none of the other links on the panel appear to be directly accessible with Dragon.
* If I select Set Featured Image I can't action any of the other links.

Dragon users can use voice commands to replicate pressing the tab key. The experience then mirrors that outlined in #23560 - but of course this cannot be used to select the images or other files.

It is possible for Dragon users to interact with screens using mouse commands but it is an incredibly laborious and time consuming process - used only as a last resort.

If one of the images is selected, the information panel for that images opens to the right. Unfortunately none of the input fields (for title, alt, etc) are directly available to Dragon. Ironically, the Insert Into Post button can be accessed directly with a voice command.

Some investigation needs to be done as to why most of the links and input fields cannot be directly accessed by Dragon when the panel is opened. This is a parallel with the situation on the Theme Customizer panel. 

It is interesting that the Set Featured Image link and the Insert Into Post button '''can''' be directly accessed. What is different about them?

"	grahamarmfield
Future Releases	23561	Using a Screen Reader with the Add Media Panel		Accessibility	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-20T15:16:55Z	2013-02-20T17:59:54Z	"Linked to #23560, this trac specifically concerns accessibility issues found when using the Add Media panel with a screen reader.

I used NVDA 2012.2.1 with IE9 and FF16.0.2 on Windows 7.

'''IE9'''

* On initially clicking Add Media link in Edit Post page the focus appears to initially be transferred into the edit content textarea within the main page. There is no audible notification that the panel has opened.
* Further tabbing shows that the focus has not been transferred into the panel - so this would be a showstopper for most users.

If you continue tabbing you eventually do come to the panel in the tab order at the bottom of the main page maybe...

* It is possible to tab round the text links in the panel. However actioning the Insert Media or Create Gallery links does not apparently do anything - there is no audible feedback that the contents of the next panel have changed. Suggest that when one of these links is actioned that focus is transferred into the relevant panel - to the heading would be a good place.
* The 'images' select does not have an associated label so it's purpose would not be clear to all users.
* The search box does not have an associated label so screen reader users in IE9 receive no feedback as to the purpose of this text box.
* There is no Go or Search button available to trigger the action for these two input fields - both of which change the content of the panel below. For accessibility reasons the user should be in control of triggering the filtering.
* As mentioned in the other ticket #23560 the main accessibility problem here is that it is not possible to select any of the previous uploaded media.


'''Firefox'''

* When the Add Media panel opens it is not clear where focus sits. But after this first link the focus is transferred into the Add Media panel.
* The close link does not announce itself when tabbing forwards, but it does when reverse tabbing.
* See IE9 section re actioning Insert Media, Create Gallery links.
* AS IE9 re label for media type select box. NVDA does announce Search box label in FF.
* As IE9 re lack of Go or Search button for these input fields.
* As IE9 it is not possible to tab to any of the previously uploaded images/files.

Separate ticket to be raised for Speech Recognition software experience."	grahamarmfield
Future Releases	24042	Help text visibility in title input box is not intuitive		Accessibility	trunk	normal	normal	Awaiting Review	enhancement	reopened		2013-04-11T03:45:04Z	2013-04-12T04:32:03Z	"Currently, the input box for title which shows on a new post creation page uses a label to display the help text- ''""Enter title here""''. This text disappears on focus and an that point of time, there is no place which points out that this input box is for the title.

This problem has been pointed out by a lot of people and it surfaced after the new Gmail design came out. The problems it generated are very similar and as you may have used it, there are no labels for the email recipients field and the subject field.

The issue is not very big as such but it does generate ambiguity in some cases. The solution to this would be to have the label as an overlay on the input, which can slide/move to a new position on focus. And placeholder text can be used as help text. This way the help text will be visible at the start and the label will be visible throughout."	aniketpant
Future Releases	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
Future Releases	21414	"Use the ""Keyboard Shortcuts"" checkbox in the user profile to turn on/off all custom shortcuts"		Accessibility		normal	normal	Awaiting Review	enhancement	new		2012-07-29T20:24:36Z	2012-10-14T11:42:23Z	"Custom keyboard shortcuts can be very handy not only for better accessibility but for faster access to many actions that usually require ""mousing"". For example we could potentially add shortcuts to access the top menu items or the more commonly used toolbar items.

However many of the available keystrokes (modifier [+ modifier] + letter) are already in use. Even worse, different shortcuts are in use in different browsers and different OS.

It would be good to let the users decide whether to enable them. As we already have a checkbox for the comment moderation shortcuts, best would be to make it ""global"". For now that would only affect TinyMCE."	azaozz
Future Releases	24150	tabindex doesnot work proper if metabox added		Accessibility	3.5.1	normal	normal	Awaiting Review	enhancement	new		2013-04-21T04:12:43Z	2013-05-02T12:24:00Z	"Hi,
In {wp-admin} default post add form, if metabox added tab button skips metaboxes and directly goes to Publish box to take action.

Developer who wants to add tabindex to all metaboxes created, add_meta_box function should have parameter to set tabindex which will allow to go through it before publish post or skip if false. "	amolv
Future Releases	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
Future Releases	9445	All Input Tags are not Section 508 Compliance		Accessibility	2.7	normal	normal	Future Release	task (blessed)	reopened		2009-04-02T18:58:32Z	2012-10-09T20:14:56Z	"Not all of the input tags within the Wordpress admin console are section 508 compliant (http://www.section508.gov/). We have scanned the application using compliance software and found many instances where input tags (checkbox, text, textarea, file, radio, etc..) are missing the required label or alt text. (There are many instances where it IS compliant.) 

We (developers at a government agency) have the ability to make the changes, but some of the decisions for which exact text to put in the labels and alt text should probably be decided by a more dedicated Wordpress developer. Please contact me if you want our help or input. 

We believe that the software is extremely close to 100% compliance. Bringing it to 100% would be a huge deal for government agencies wh are trying to get approval to install and run Wordpress internally and externally."	dmo7
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	22222	"""Mode"" buttons bumped below (in 1024x768) when long category name exists"		Administration		normal	minor	Awaiting Review	defect (bug)	new		2012-10-18T17:22:33Z	2013-02-09T20:54:12Z	"If there's a long category name, the category filter <select> menu widens. On a 1024x768 screen, this causes the list/excerpt mode buttons to get bumped down.

screenshot: http://kdl.dropmark.com/25665/1130400

One thought was to move that option to Screen Options, which I think makes more sense anyway. "	trepmal
Future Releases	22735	A given pointer should only show once on a screen		Administration		normal	normal	Awaiting Review	defect (bug)	new		2012-12-04T18:10:44Z	2012-12-14T23:51:42Z	If you have, say, multiple media buttons on a screen, you'll get multiple pointers, each pointing to an instance of that button. This shouldn't happen. In the case of the media button, it should probably only show up for the one associated with the main editor. In terms of the pointers in general, it should only show up once, not for each match in the DOM.	helen
Future Releases	17516	Add Favorite Actions to Admin Bar		Administration	3.2	normal	normal	Awaiting Review	defect (bug)	new		2011-05-19T18:37:03Z	2011-09-10T03:25:31Z	"With the new UI upgrade, the favorite_actions() method was removed from the main UI. After a brief discussion with Westi, it made sense to put the functionality back in as part of the adminbar.

The attached patch does that using the favorite_actions() method (which can now return the filtered list of favorite_actions as an array). We should eat our own dog food."	technosailor
Future Releases	19527	Add New Category Problem While Posting		Administration	3.3	normal	minor	Awaiting Review	defect (bug)	reopened	close	2011-12-13T05:26:08Z	2013-01-22T01:19:25Z	"When adding new category, while you are making a post, If a category is added under a parent category, it doesn't show properly that the new category is under the parent category.

It has been added correctly, but it doesn't show properly the first time."	jainprateek
Future Releases	23141	"Add autocomplete=""off"" to all inputs that have a value"		Administration	3.5	normal	normal	Awaiting Review	defect (bug)	new		2013-01-08T12:49:51Z	2013-01-08T19:44:44Z	"On '''refresh''' in the browser - old data is filled in the inputs, instead of the actual data from the value attribute of the input.

to be more clear : http://www.screenr.com/p2K7"	alexvorn2
Future Releases	20938	Adding existing category duplicates default one		Administration	3.3.2	normal	minor	Awaiting Review	defect (bug)	new	dev-feedback	2012-06-13T13:52:18Z	2013-01-22T03:35:53Z	In the post editing page, if you add a category which already exists, Wordpress duplicates the default category (Uncategorized), instead of showing a warning or doing nothing.	hvsupr
Future Releases	20082	Admin bar links to wrong site in multisite (subdomain) network		Administration	3.3.1	normal	major	Awaiting Review	defect (bug)	new		2012-02-20T09:53:52Z	2012-02-21T08:43:50Z	"The code
{{{
	foreach ( $actions as $link => $action ) {
		list( $title, $id ) = $action;

		$wp_admin_bar->add_menu( array(
			'parent'    => 'new-content',
			'id'        => $id,
			'title'     => $title,
			'href'      => admin_url( $link )
		) );
	}
}}}
generates the wrong URL, whenever I visit a site that has the URL subsite.subsite.example.com but generates the correct URL if the URL is of the pattern subsite.example.com. On subsite.subsite.example.com the admin bar will generate links to subsite.example.com."	niklasbr
Future Releases	16600	AdminMenu rendering code chokes on uppercase		Administration	3.1	normal	minor	Awaiting Review	defect (bug)	reopened		2011-02-20T02:43:25Z	2011-03-05T16:28:13Z	"When registering custom taxonomies for a custom post type, if the post type name contains uppercase letters, the menu items for the custom taxonomies are not shown.

It looks like the post type name is lowercased in some parts of the core code (but no all) and so string comparisons fail.
Just isolated this behaviour, so I'm still not sure how much of the core this affects.

Moreover, when I saved posts with the intended mixed-case name, they have been saved to the DB with lowercased post_type


It it is indeed the intended behaviour, a note should be added to the Codex:
 ""Custom Post Type names must be lowercase""

The attached sample (real) code reproduces the problem by setting ""post_type_tag"" to ""DomainName"" instead of ""domain_name"". Numbers work properly, however.

Tested with latest SVN (RC4 + r17467)"	jltallon
Future Releases	19722	Administering wih SSL and uploading images makes image links HTTPS		Administration	3.3	normal	normal	Awaiting Review	defect (bug)	new		2012-01-03T16:45:51Z	2013-04-29T21:47:16Z	"I am noticing this issue in 3.3 that all uploaded attachments are listed in the library using HTTPS in the location when administerng over SSL. I tried the patch.2 listed and it does not seem to change anything. Previously this was never an issue, but now all my images are getting added as HTTPS when I do not want them to be. I end up searching the DB for "" https://"" and replacing with HTTP after every post.

Will this ever get resolved back to normal so SSL admin can be used without having all attachments over SSL? I only have SSL for login and admin."	ccolotti
Future Releases	21211	Alter how settings_errors are output in options.php		Administration	3.4.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-07-10T23:44:37Z	2012-12-10T18:43:09Z	"The `*_settings_error(s)` and `settings_error` functions are used mainly as part of the Settings API, but with the way that options.php currently handles the settings errors, it assumes that people will use this functionality exclusively with the Settings API. Notice options.php, starting at line 153:

{{{
	/**
	 * Handle settings errors and return to options page
	 */
	// If no settings errors were registered add a general 'updated' message.
	if ( !count( get_settings_errors() ) )
		add_settings_error('general', 'settings_updated', __('Settings saved.'), 'updated');
	set_transient('settings_errors', get_settings_errors(), 30);
}}}

This simply assumes that no other outside source has registered any sort of setting error other than the current options page. TwentyEleven does this, and so if any other source has registered any notices via these functions, the ""Settings saved."" message will not be output because the first bit of logic will fail. I don't think this assumption can (nor should) be warranted, so there needs to be another way to handle this so that themes like TwentyEleven who only call `settings_errors` at the top of their options page don't get unknowingly hijacked by other sources.

I always suggest registering your own errors at the end of the sanitization callback for your setting, and then output those specific errors within settings_errors to avoid any internal conflicts like this.

Just looking for some ways to approach this. :-) 


"	griffinjt
Future Releases	18530	Browser update dismiss setting ignored with JavaScript disabled		Administration	3.2.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-08-27T15:41:24Z	2013-01-22T01:14:57Z	"When working on a corporate desktop you can not update your browser. When freely deciding about when to upgrade you might not even want to upgrade.

Therefore a user setting has been introduced to remove the nag warning. E.g. my linux distro is perfectly ok with it's firefox and it's taken care of by the pacakager. For my OS, I have the latest version.

I needed to press dismiss (with JS enabled, the related report is #17766).

What has been missed is to not display that nag if javascript is disabled. The setting gets ignored.

How to Reproducde

  * Setup a WP 3.2.1 Blog.
  * Log into admin with a Firefox 3 browser.
  * Enable Javascript.
  * Dismiss the Nag.
  * Logout and close the Browser.
  * Restart the Browser.
  * Disable Javascript (if you need to).
  * Log into Dashboard.

Result: Browser Update Nag is displayed.

Expected Result: Browser Update Nag is not displayed as specified by the user."	hakre
Future Releases	16946	Bug between CPT menu_position and add_object_page()		Administration	3.1	normal	normal	Future Release	defect (bug)	reviewing		2011-03-23T10:11:12Z	2012-07-20T13:49:29Z	I write a demo plugin for describe the bug. See attachment.	momo360modena
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	23904	CSS glitch when the browser window width isn't right		Administration		normal	normal	Awaiting Review	defect (bug)	new		2013-03-29T21:20:47Z	2013-03-29T22:29:53Z	"The post editor's layout now switches when the width of the window is narrow enough. But there's an intermediary zone, at least on Webkit/Safari where it's too narrow for the conditional CSS to kick in, yet too wide for the browser to deal with it. I presume, based on what I was working on a few minutes ago, that it's related to paddings.

Screenshot attached."	Denis-de-Bernardy
Future Releases	22022	Can’t properly add pages of type edit.php?post_type=xxx as submenu items to arbitrary parent menus		Administration	3.0	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-09-27T20:22:43Z	2013-01-11T11:22:48Z	"The following code illustrates the problem.
{{{
add_menu_page('My Pages', 'My Pages', 'edit_posts', 'parentslug', array(class, func));
add_submenu_page('parentslug', 'Settings', 'Settings', 'edit_posts', 'mysettings', array(class, func));
add_submenu_page('parentslug', 'Custom Post Type', 'Custom Post Type', 'edit_posts', 'edit.php?post_type=xxx'); 
}}}
When you click on the first submenu item, the menu stays open, displaying the submenu items as it should. When you click on the item for the custom post type, the parent menu is closed and submenu pages are not displayed.

The root of the problem is how $parent_page is handled for pages of type edit.php?post_type=xxx. In get_admin_page_parent(), $parent_file is always set to $submenu[$parent], which may cause the submenu slug to be different from $parent_file. But in _wp_menu_output, if the submenu slug and parent slug are not equal, the 'wp-has-current-submenu wp-menu-open' classes do not get added which means the menu gets displayed as being closed.

Since there are no actions called between get_admin_parent_page() and the output of the menu, the only workaround I can see is some ugly JS that fixes up the classes.

It seems like the least intrusive fix would be to just move the call to apply_filters(""parent_file) in menu-header.php to after the call to get_admin_page_parent() so that $parent_file can truly be overridden. This also seems inline with the intent of the filter.
"	jjharr
Future Releases	17209	Category list table breaks when custom post type label is too long		Administration	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-04-21T21:14:11Z	2012-11-01T06:22:13Z	"Registered a post type which has a longer label than ""posts"" (called ""resources""). List table listing the categories for that post type breaks slightly when a name is over a certain length. Picture attached.

Offending CSS is setting a 10% width to that column.

I can provide a patch. Though since the number of posts is centered, the heading is left aligned. If that column is widened, should the title be centered as well (since left-aligned may look weird at one point)?"	andrewryno
Future Releases	20595	Collapsible Admin menu fails if items are added by code		Administration	3.3.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-05-01T23:27:42Z	2012-05-02T07:48:13Z	"If I add a Button to the admin meny by '''action adminmenu''' the menu wont rebuid from collapsed state due z-index issues. In my opinion creating the menue might be changed to the following: 


{{{

diff --git a/wp-admin/menu-header.php b/wp-admin/menu-header.php
index cdd81b2..8454a3d 100644
--- a/wp-admin/menu-header.php
+++ b/wp-admin/menu-header.php
@@ -164,10 +164,6 @@ function _wp_menu_output( $menu, $submenu, $submenu_as_parent = true ) {
                }
                echo ""</li>"";
        }
-
-       echo '<li id=""collapse-menu"" class=""hide-if-no-js""><div id=""collapse-button""><div></div></div>';
-       echo '<span>' . esc_html__( 'Collapse menu' ) . '</span>';
-       echo '</li>';
 }

 ?>
@@ -181,6 +177,9 @@ function _wp_menu_output( $menu, $submenu, $submenu_as_parent = true ) {

 _wp_menu_output( $menu, $submenu );
 do_action( 'adminmenu' );
+echo '<li id=""collapse-menu"" class=""hide-if-no-js""><div id=""collapse-button""><div></div></div>';
+echo '<span>' . esc_html__( 'Collapse menu' ) . '</span>';
+echo '</li>';

 ?>
 </ul>
}}}

see also: http://wordpress.org/support/topic/admin-menu-wont-dis-collapse-anymore"	digitaldonkey
Future Releases	15466	Database errors on dashboard		Administration	3.1	normal	minor	Awaiting Review	defect (bug)	reopened		2010-11-18T07:11:43Z	2012-09-04T12:33:11Z	"Not sure why it's happening and it's only happening on one of my blogs, but posting it anyway.

== Incoming Links ==

{{{
WordPress database error: [Incorrect string value: '\xD0\xA3 \xD0\xBC\xD0...' for column 'option_value' at row 1]
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_feed_de55c189685ea1944a5f72021d68a360', 'a:4:{s:5:\""child\"";a:1:{s:0:\""\"";a:1:{s:3:\""rss\"";a:1:{i:0;a:6:{s:4:\""data\"";s:1:\""\n\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:7:\""version\"";s:3:\""2.0\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:1:{s:0:\""\"";a:1:{s:7:\""channel\"";a:1:{i:0;a:6:{s:4:\""data\"";s:10:\""\n\n\n\n\n\n\n\n\n\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:4:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:51:\""link:http://www.finalgear.com/ - Google Blog Search\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:109:\""http://blogsearch.google.com/blogsearch?hl=en&scoring=d&ie=ISO-8859-1&num=10&q=link:http://www.finalgear.com/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:108:\""Google Blog Search Results: <b>1,432</b> results for <b>http://www.finalgear.com/</b> - showing 1 through 10\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""item\"";a:10:{i:0;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:37:\""Evora S in next episode of Fifth Gear\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:75:\""http://www.lotustalk.com/forums/f170/evora-s-next-episode-fifth-gear-94777/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:238:\""The next episode of Fifth Gear with feature an Evora S. It will air on November 19th in the UK and for those of us unfortunate enough to not live in England it can be downloaded via torrent client from www.finalgear.com a little while ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:36:\""LotusTalk - The Lotus Cars Community\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:8:\""Mr. Know\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Wed, 17 Nov 2010 02:58:32 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:1;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:9:\""Top Gear?\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:41:\""http://krolyk.livejournal.com/114570.html\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:373:\""У меня иногда спрашивают: что такого интересного я нахожу в передаче Top Gear? Сейчас, накануне запуска в эфир локализованной версии для США, на ТВ вышла передача с ведущими оригинального, британского Top Gear. ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:36:\""Записки Андрея Гуле\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:6:\""krolyk\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Fri, 29 Oct 2010 09:09:31 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:2;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:50:\""New Jeremy Clarkson Blu-Ray/DVD Coming In November\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:85:\""http://blog.webridestv.com/2010/10/new-jeremy-clarkson-blu-raydvd-coming-in-november/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:240:\""Everyone knows Jezza Clarkson from Top Gear, but what many people in North America may not know is that every year, Jeremy comes out with a new DVD, that has some of the feel of Top Gear, but is freed from the format, and there are some ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:15:\""Sports Car Blog\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:11:\""Eric Trytko\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Tue, 12 Oct 2010 11:30:49 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:3;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:72:\""Upcoming Top Gear America Trailer... Thrashes a mid 70s Coupe <b>...</b>\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:135:\""http://www.cadillacforums.com/forums/cadillac-forums-lounge-member-introductions/207377-upcoming-top-gear-america-trailer-thrashes.html\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:171:\""It is sad to see :crying:. http://www.finalgear.com/news/2010/0...ar-us-trailer/ I hope it is a good show but I think they\'re right; nothing will ever top the British one.\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:14:\""CadillacOwners\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""eldorado99\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Sat, 07 Aug 2010 16:26:27 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:4;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:38:\""Top Gear&#39;s Tribute To Ayrton Senna\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:83:\""http://space-action-hero.blogspot.com/2010/08/top-gear-tribute-to-ayrton-senna.html\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:237:\""Last week\'s Top Gear was epic. One of Top Gear\'s best in a while. There was the Veyron Super Sport, Tom Cruise and Cameron Diaz, but most of all, there was a heartwarming and touching tribute to arguably the greatest F1 driver of all ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:22:\""The Meditation Chamber\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:27:\""noreply@blogger.com (Kenny)\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Mon, 02 Aug 2010 14:02:00 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:5;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:28:\""Top Gear Season 15 Episode 5\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:63:\""http://importbible.com/2010/07/29/top-gear-season-15-episode-5/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:233:\""This week\'s Top Gear is packed with action from start to finish. Hammond challenges snow mobiles in his nicely built Touareg, Captain Slow is back at Volkswagen\'s test track to try out their new Bugatti Veyron and lastly Clarkson ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""Import Bible - Automotive Apparel\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:5:\""david\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Thu, 29 Jul 2010 21:40:21 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:6;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:28:\""Top Gear Season 15 Episode 4\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:63:\""http://importbible.com/2010/07/24/top-gear-season-15-episode-4/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:230:\""Season 15 is starting to shape up to be an epic season. In this weeks episode Clarkson compares two super car convertibles and the boys are challenged to build motor homes and of course putting them through various challenges. ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""Import Bible - Automotive Apparel\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:5:\""david\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Sun, 25 Jul 2010 00:45:05 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:7;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:30:\""Post Vacation Reading Material\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:64:\""http://utterlyboring.com/archives/2010/07/19/post_vacation_r.php\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:219:\""Since getting back, I\'ve been trying to catch up on all the email and news that has been sent my way (you\'re always welcome to send more using the contact form on this site or e-mail utterlyboring at gmail dot com). ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:17:\""UtterlyBoring.com\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:7:\""unknown\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Mon, 19 Jul 2010 20:24:17 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:8;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Shared items on July 14, 2010\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:64:\""http://www.dot.alter.si/2010/07/15/shared-items-on-july-14-2010/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:239:\""An overview of interesting articles that came through my Google Reader subscriptions recently. Sony unveils world\'s first consumer HD camcorder with interchangeable lens system. from: Gizmag Emerging Technology Magazine on 14 July 2010 ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:15:\""Connecting Dots\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:6:\""Jernej\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Thu, 15 Jul 2010 06:50:43 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:9;a:6:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:2:{s:0:\""\"";a:3:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:28:\""Top Gear Season 15 Episode 3\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:63:\""http://importbible.com/2010/07/12/top-gear-season-15-episode-3/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:235:\""This weeks episode pits three new high performance sedans against each other in a number of challenges to find out which one is the best. The hosts also review and compare the new Chevorlet Camero versus the new Mercedes Benz E63. ...\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:3:{s:9:\""publisher\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""Import Bible - Automotive Apparel\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:5:\""david\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""date\"";a:1:{i:0;a:5:{s:4:\""data\"";s:29:\""Tue, 13 Jul 2010 05:55:41 GMT\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}}}s:36:\""http://a9.com/-/spec/opensearch/1.1/\"";a:3:{s:12:\""totalResults\"";a:1:{i:0;a:5:{s:4:\""data\"";s:4:\""1432\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:10:\""startIndex\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""1\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:12:\""itemsPerPage\"";a:1:{i:0;a:5:{s:4:\""data\"";s:2:\""10\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}}}}}}}}s:4:\""type\"";i:128;s:7:\""headers\"";a:9:{s:4:\""date\"";s:29:\""Thu, 18 Nov 2010 07:07:10 GMT\"";s:6:\""pragma\"";s:8:\""no-cache\"";s:7:\""expires\"";s:29:\""Fri, 01 Jan 1990 00:00:00 GMT\"";s:13:\""cache-control\"";s:25:\""no-cache, must-revalidate\"";s:12:\""content-type\"";s:23:\""text/xml; charset=UTF-8\"";s:10:\""set-cookie\"";s:138:\""PREF=ID=48169caac9439b57:TM=1290064030:LM=1290064031:S=Ik6CY3EJZro84eTi; expires=Sat, 17-Nov-2012 07:07:11 GMT; path=/; domain=.google.com\"";s:22:\""x-content-type-options\"";s:7:\""nosniff\"";s:6:\""server\"";s:4:\""bsfe\"";s:16:\""x-xss-protection\"";s:13:\""1; mode=block\"";}s:5:\""build\"";s:14:\""20090627192103\"";}', 'no') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)

    Mr. Know linked here saying, ""The next episode of Fifth Gear with feature an Evo ...""
    krolyk linked here saying, ""У меня иногда спрашивают: что такого интересного я ...""
    Eric Trytko linked here saying, ""Everyone knows Jezza Clarkson from Top Gear, but w ...""
    eldorado99 linked here saying, ""It is sad to see :crying:. http://www.finalgear.co ...""
    noreply@blogger.com (Kenny) linked here saying, ""Last week's Top Gear was epic. One of Top Gear's b ...""
}}}

== WordPress Development Blog ==

{{{
WordPress database error: [Incorrect string value: '\xD0\x9D\xD0\xB8\xD0\xBA...' for column 'option_value' at row 1]
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_feed_0ff4b43bd116a9d8720d689c80e7dfd4', 'a:4:{s:5:\""child\"";a:1:{s:0:\""\"";a:1:{s:3:\""rss\"";a:1:{i:0;a:6:{s:4:\""data\"";s:3:\""\n\n\n\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:7:\""version\"";s:3:\""2.0\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:1:{s:0:\""\"";a:1:{s:7:\""channel\"";a:1:{i:0;a:6:{s:4:\""data\"";s:50:\""\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:3:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:14:\""WordPress News\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:25:\""http://wordpress.org/news\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:14:\""WordPress News\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:13:\""lastBuildDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Thu, 30 Sep 2010 03:23:31 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""language\"";a:1:{i:0;a:5:{s:4:\""data\"";s:2:\""en\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:9:\""generator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""http://wordpress.org/?v=3.1-alpha\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""item\"";a:10:{i:0;a:6:{s:4:\""data\"";s:56:\""\n \n \n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:39:\""WordPress for iPhone/iPad v2.6 Released\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:43:\""http://wordpress.org/news/2010/09/ios-v2-6/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:52:\""http://wordpress.org/news/2010/09/ios-v2-6/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Thu, 30 Sep 2010 03:23:31 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:6:{i:0;a:5:{s:4:\""data\"";s:8:\""Releases\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:5:\""apple\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:2;a:5:{s:4:\""data\"";s:3:\""ios\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:3;a:5:{s:4:\""data\"";s:4:\""ipad\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:4;a:5:{s:4:\""data\"";s:6:\""iphone\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:5;a:5:{s:4:\""data\"";s:6:\""mobile\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""http://wordpress.org/news/?p=1497\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:335:\""Attention Apple-gadget-owning WordPress users! Have you been using the WordPress iOS app for iPhone and iPad? Or maybe you tried it a while back and thought it wasn&#8217;t for you? Either way, the new release &#8212; v2.6 &#8212; will knock your socks off. Why? A bunch of reasons: Video. Record, upload, attach, and play videos [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:2319:\""<p>Attention Apple-gadget-owning WordPress users! Have you been using the WordPress iOS app for iPhone and iPad? Or maybe you tried it a while back and thought it wasn&#8217;t for you? Either way, the new release &#8212; v2.6 &#8212; will knock your socks off. Why? A bunch of reasons:</p>\n<ul>\n<li>Video. Record, upload, attach, and play videos within the app. Yay for being able to catch your friends&#8217; and co-workers&#8217; most <del>embarrassing shenanigans</del> <em>creative moments</em> with iPhone video and publish them immediately for all the world to see on your WordPress site.</li>\n<li>A total rewrite of the way local drafts are handled, to prevent the unintentional loss of your pending posts.</li>\n<li>Autosave/post revisions. Bam! One of the &#8220;oh, thank goodness&#8221; features of the web app makes it into the iOS version.</li>\n<li>Easier setup. Faster and easier process for adding your sites to the app.</li>\n<li>Media Library. We&#8217;re gradually getting closer to the media management you&#8217;re used to in the web app.</li>\n</ul>\n<p>There are also numerous bugfixes and performance enhancements in this release, so if you haven&#8217;t been using the app lately, you should consider giving it another try. I&#8217;m personally pretty excited to start using the iPhone version more often now that there are all these fixes and new features. Especially the video upload. You know, for those <em>creative moments</em> that make life fun. <img src=\'http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif\' alt=\':)\' class=\'wp-smiley\' /> </p>\n<p>You can read the full <a href=\""http://ios.wordpress.org/2010/09/29/introducing-version-2-6/\"">2.6 release post on the WordPress for iOS blog</a>, and can download v2.6 from iTunes/the app store. Happy mobile blogging!</p>\n<p style=\""text-align: center\"">* * *</p>\n<p>Not an iPhone user? We&#8217;ve still got your on-the-go back! Check out the WordPress apps for <a href=\""http://android.wordpress.org/\"">Android</a>, <a href=\""http://blackberry.wordpress.org/\"">Blackberry</a>, and <a href=\""http://nokia.wordpress.org/\"">Nokia (beta)</a>. They&#8217;re all 100% GPL, of course, and we&#8217;re always looking for contributors to the development projects, so check the blogs if you have mobile dev skills and want to get involved.</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:48:\""http://wordpress.org/news/2010/09/ios-v2-6/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:1;a:6:{s:4:\""data\"";s:50:\""\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""WordPress Trademark Changes Hands\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:51:\""http://wordpress.org/news/2010/09/trademark-to-wpf/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:60:\""http://wordpress.org/news/2010/09/trademark-to-wpf/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Thu, 09 Sep 2010 23:14:13 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:4:{i:0;a:5:{s:4:\""data\"";s:7:\""General\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:10:\""Automattic\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:2;a:5:{s:4:\""data\"";s:9:\""Trademark\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:3;a:5:{s:4:\""data\"";s:20:\""WordPress Foundation\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""http://wordpress.org/news/?p=1488\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:379:\""The WordPress community took a big step forward today when Matt announced that Automattic has donated the WordPress trademark to the non-profit WordPress Foundation. Moving forward, the Foundation will be responsible for safeguarding the trademarked name and logo from misuse toward the end of protecting WordPress and preventing confusion among people trying to figure out [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:502:\""<p>The WordPress community took a big step forward today when <a href=\""http://wp.me/p4oB3-9ie\"">Matt announced</a> that Automattic has donated the WordPress trademark to the non-profit <a href=\""http://wp.me/pMBRF-1u\"">WordPress Foundation</a>. Moving forward, the Foundation will be responsible for safeguarding the trademarked name and logo from misuse toward the end of protecting WordPress and preventing confusion among people trying to figure out if a resource is &#8220;official&#8221; or not.</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:56:\""http://wordpress.org/news/2010/09/trademark-to-wpf/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:2;a:6:{s:4:\""data\"";s:41:\""\n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:15:\""WordPress 3.0.1\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:50:\""http://wordpress.org/news/2010/07/wordpress-3-0-1/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:59:\""http://wordpress.org/news/2010/07/wordpress-3-0-1/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Thu, 29 Jul 2010 21:38:47 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:1:{i:0;a:5:{s:4:\""data\"";s:8:\""Releases\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""http://wordpress.org/news/?p=1475\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:338:\""After nearly 11 million downloads of WordPress 3.0 in just 42 days, we&#8217;re releasing WordPress 3.0.1. The requisite haiku: Three dot oh dot one Bug fixes to make you smile Update your WordPress This maintenance release addresses about 50 minor issues. The testing many of you contributed prior to the release of 3.0 helped make [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:12:\""Andrew Nacin\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:951:\""<p>After nearly <a href=\""http://wordpress.org/download/counter/\"">11 million downloads</a> of WordPress 3.0 in just 42 days, we&#8217;re releasing WordPress 3.0.1. The requisite haiku:</p>\n<p>Three dot oh dot one<br />\nBug fixes to make you smile<br />\nUpdate your WordPress</p>\n<p>This maintenance release addresses <a href=\""http://codex.wordpress.org/Version_3.0.1\"">about 50 minor issues</a>. The testing many of you contributed prior to the release of 3.0 helped make it one of the best and most stable releases we&#8217;ve had.</p>\n<p><a href=\""http://wordpress.org/download/\"">Download 3.0.1</a> or update automatically from the Dashboard &gt; Updates menu in your site&#8217;s admin area.</p>\n<p><em>Note: If you downloaded 3.0.1 in the first 20 minutes of release (before 2200 UTC), you&#8217;ll want to reinstall it, which you can do right from your Updates screen. <a href=\""http://twitter.com/wordpress/status/19859163982\"">Our bad</a>.</em></p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:55:\""http://wordpress.org/news/2010/07/wordpress-3-0-1/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:3;a:6:{s:4:\""data\"";s:50:\""\n \n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:42:\""PHP 4 and MySQL 4 End of Life Announcement\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:58:\""http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:67:\""http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Fri, 23 Jul 2010 19:01:46 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:4:{i:0;a:5:{s:4:\""data\"";s:7:\""Hosting\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:5:\""MySQL\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:2;a:5:{s:4:\""data\"";s:3:\""PHP\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:3;a:5:{s:4:\""data\"";s:12:\""requirements\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:33:\""http://wordpress.org/news/?p=1447\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:348:\""Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:12:\""Mark Jaquith\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:3021:\""<p>Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the requirements for running WordPress. Now is one of those times. You probably guessed it from the title &#8212; we&#8217;re finally ready to announce the end of support for PHP 4 and MySQL 4!</p>\n<p>First up, the announcement that developers really care about. WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4.</p>\n<p>For WordPress 3.2, due in the first half of 2011, we will be raising the minimum required PHP version to 5.2. Why 5.2? Because that&#8217;s what the vast majority of WordPress users are using, and it offers substantial improvements over earlier PHP 5 releases. It is also the minimum PHP version that the <a href=\""http://drupal.org/\"">Drupal</a> and <a href=\""http://www.joomla.org/\"">Joomla</a> projects will be supporting in their next versions, both due out this year.</p>\n<p>The numbers are now, <em>finally</em>, strongly in favor of this move. Only around 11 percent of WordPress installs are running on a PHP version below 5.2. Many of them are on hosts who support PHP 5.2 &#8212; users merely need to change a setting in their hosting control panel to activate it. We believe that percentage will only go down over the rest of the year as hosting providers realize that to support the newest versions of WordPress (or Drupal, or Joomla), they&#8217;re going to have to pull the trigger.</p>\n<p>In less exciting news, we are also going to be dropping support for MySQL 4 after WordPress 3.1. Fewer than 6 percent of WordPress users are running MySQL 4. The new required MySQL version for WordPress 3.2 will be 5.0.15.</p>\n<p>WordPress users will not be able to upgrade to WordPress 3.2 if their hosting environment does not meet these requirements (the built-in updater will prevent it). In order to determine which versions your host provides, we&#8217;ve created the <a href=\""http://wordpress.org/extend/plugins/health-check/\"">Health Check plugin</a>. You can download it manually, or use this <a href=\""http://coveredwebservices.com/wp-plugin-install/?plugin=health-check\"">handy plugin installation</a> tool I whipped up. Right now, Health Check will only tell you if you&#8217;re ready for WordPress 3.2. In a future release it will provide all sorts of useful information about your server and your WordPress install, so hang on to it!</p>\n<p>In summary: WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4 and MySQL 4. WordPress 3.2, due in the first half of 2011, will require PHP 5.2 or higher, and MySQL 5.0.15 or higher. <a href=\""http://coveredwebservices.com/wp-plugin-install/?plugin=health-check\"">Install the Health Check plugin</a> to see if you&#8217;re ready!</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:63:\""http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:4;a:6:{s:4:\""data\"";s:44:\""\n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:41:\""100 Million Plugin Downloads and Counting\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:46:\""http://wordpress.org/news/2010/07/100-million/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:55:\""http://wordpress.org/news/2010/07/100-million/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Fri, 02 Jul 2010 17:48:34 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:2:{i:0;a:5:{s:4:\""data\"";s:9:\""Community\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1429\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:364:\""WordPress 3.0 Thelonious passed 3 million downloads yesterday, and today the plugin directory followed suit with a milestone of its own: 100 million downloads. The WordPress community&#8217;s growth over the years has been tremendous, and we want to reinvest in it. So we&#8217;re taking the next two months to concentrate on improving WordPress.org. A major [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:12:\""Andrew Nacin\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:2319:\""<p>WordPress 3.0 Thelonious passed <a href=\""http://wordpress.org/download/counter/\"">3 million downloads</a> yesterday, and today <a href=\""http://wordpress.org/extend/plugins/\"">the plugin directory</a> followed suit with a milestone of its own: 100 million downloads.</p>\n<p>The WordPress community&#8217;s growth over the years has been tremendous, and we want to reinvest in it. So we&#8217;re taking the next two months to concentrate on improving WordPress.org. A major part of that will be improving the infrastructure of the plugins directory. More than 10,000 plugins are in the directory, every one of them GPL compatible and free as in both beer and speech. Here&#8217;s what we have in mind:</p>\n<p>We want to provide developers the tools they need to build the best possible plugins. We&#8217;re going to provide better integration with the forums so you can support your users. We&#8217;ll make more statistics available to you so you can analyze your user base, and over time we hope to make it easier for you to manage, build, and release localized plugins.</p>\n<p>We want to improve how the core software works with your plugin and the plugin directory. We&#8217;re going to focus on ensuring seamless upgrades by making the best possible determinations about compatibility, and offer continual improvements to the plugin installer. And we also want to give you a better developer tool set like SVN notifications and improvements to the bug tracker.</p>\n<p>We&#8217;re also going to experiment with other great ideas to help the community help plugin authors. We want it to be easy for you to offer comments to plugin authors and the community, including user reviews and better feedback. We may experiment with an adoption process for abandoned plugins as a way to revitalize hidden gems in the directory. I&#8217;m not sure there is a better way to show how extendable WordPress is and how awesome this community is at the same time.</p>\n<p>As <a href=\""http://wordpress.org/development/2010/06/thelonious/\"">Matt said in the 3.0 release announcement</a>, our goal isn&#8217;t to make everything perfect all at once. But we think incremental improvements can provide us with a great base for 3.1 and beyond, and for the tens of millions of users, and hundreds of millions of plugin downloads to come.</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:51:\""http://wordpress.org/news/2010/07/100-million/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:5;a:6:{s:4:\""data\"";s:44:\""\n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:18:\""Summer of WordCamp\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:53:\""http://wordpress.org/news/2010/06/summer-of-wordcamp/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:62:\""http://wordpress.org/news/2010/06/summer-of-wordcamp/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Tue, 29 Jun 2010 17:19:45 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:2:{i:0;a:5:{s:4:\""data\"";s:9:\""Community\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:8:\""WordCamp\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1418\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:355:\""It&#8217;s been summer for about a week now. Whether you&#8217;re on vacation or burning the midnight oil, attending a local/nearby WordCamp is a great way to spend a weekend. Meet other WordPress users, developers, designers &#38; consultants, learn a little something, maybe share a little of your own experience and knowledge, and break bread (or [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:5678:\""<p>It&#8217;s been summer for about a week now. Whether you&#8217;re on vacation or burning the midnight oil, attending a local/nearby <a href=\""http://wordcamp.org\"">WordCamp</a> is a great way to spend a weekend. Meet other WordPress users, developers, designers &amp; consultants, learn a little something, maybe share a little of your own experience and knowledge, and break bread (or raise a toast) with new friends and collaborators. Here are the WordCamps scheduled for this summer, along with what I know about them.</p>\n<p>July 3: <a href=\""http://wordcamp.de/\"">WordCamp Germany</a> &#8211; Berlin, Germany. I love it that they&#8217;re using BuddyPress for their event site. They have multiple tracks, and what looks to be a nice variety of sessions. It&#8217;s only a few days away, so if you&#8217;re thinking of going, get your tickets now!</p>\n<p>July 10: <a href=\""http://2010.boulder.wordcamp.org/\"">WordCamp Boulder</a> &#8211; Boulder, Colorado, USA. This was WordCamp Denver last year, but the organizers have decided to mix it up and go back and forth between Denver and Boulder, which also has a thriving tech community. This year the venue is the Boulder Theater (so pretty!), and there will sessions for bloggers and devs alike, plus a Genius Bar to help people get their WordPress sites all fixed up. The speaker lineup looks good, and I hear they&#8217;re pumping up the wifi this year. I&#8217;ll be there, likely hunched over a notebook with Lisa Sabin-Wilson (author of <em>WordPress for Dummies</em> and <em>BuddyPress for Dummies</em>) to talk about the WordPress User Handbook project, and/or hunched over a sketchbook with Kevin Conboy (designed the new lighter &#8220;on&#8221; state for admin menus in WordPress 3.0) to work out a new default WordCamp.org theme (using BuddyPress). You can still get tickets!</p>\n<p>July 17–18: <a href=\""http://uk.wordcamp.org/\"">WordCamp UK</a>- Manchester, England, UK. The roving WordCamp UK will be in Manchester this year, and is probably the closest to BarCamp style of all the WordCamps, using a wiki to plan some speakers/sessions and organizing the rest ad-hoc on the first day of the event. I&#8217;ll be attending this one as well, and am looking forward to seeing WordPress lead developer Peter Westwood again. I&#8217;m also looking forward to meeting some core contributors for the first time in person, like Simon Wheatley and John O&#8217;Nolan. Mike Little, co-founder of WordPress, is on the organizing team of WordCamp UK. Tickets on sale now!</p>\n<p>July 24: WordCamp Nigeria &#8211; Lagos, Nigeria. Their site seems to have a virus, so no link from here, but if you&#8217;re in Nigeria and interested in attending/getting involved, a quick Google search will get you to the organizers.</p>\n<p>August 7: <a href=\""http://www.wordcamphouston.com/\"">WordCamp Houston</a> &#8211; Houston, TX, USA. Houston, Texas, birthplace of WordPress! Fittingly, Matt Mullenweg will be there to give the keynote. WordCamp Houston is running three tracks &#8212; Business, Blogger and Developer &#8212; in recognition of the fact that people who are interested in using WordPress for their business may not actually be bloggers or developers themselves. This used to get labeled as a &#8220;CMS&#8221; track at previous WordCamps (including NYC 2009), but with WordPress 3.0 supporting CMS functionality out of the box, &#8220;Business&#8221; is a much more appropriate label. Who wants to bet on if there will be BBQ for lunch?</p>\n<p>August 7 : <a href=\""http://wordcampiowa.org/\"">WordCamp Iowa</a> &#8211; Des Moines, Iowa, USA. Another placeholder page. Happening, not happening? I&#8217;ve emailed the organizer and will update this post once I know more.</p>\n<p>August 7–8: <a href=\""http://wordcamp.org.nz/\"">WordCamp New Zealand</a> &#8211; Auckland, New Zealand. They haven&#8217;t announced this year&#8217;s speakers or topics, but they&#8217;ve been running polls to get community input into the program. Of note: in 2011 WordCamp New Zealand will be shifting seasons and will be in February instead, when the weather is nicer.</p>\n<p>August 20–22: <a href=\""http://2010.savannah.wordcamp.org/\"">WordCamp Savannah</a> &#8211; Savannah, Georgia, USA. Disclaimer: I am completely biased about Savannah, since I&#8217;m one of the organizers. This will be the first WordCamp in Savannah, and it&#8217;s being held at the Savannah College of Art and Design River Club, an awesome venue that used to be a cotton warehouse or something like that. Since Savannah doesn&#8217;t really have a cohesive WordPress community yet (though a fair number of people from Savannah attended WordCamp Atlanta earlier this year), this WordCamp is aimed squarely at building a local community. We&#8217;ll have a local meet-and-greet, regular sessions with visiting speakers (lots of core contributors coming to this one, plus Matt), and on Sunday it will be combination unconference/genius bar/collaborative workspace. Oh, and a potluck! We&#8217;ll also be running a pre-WordCamp workshop for people who have never used WordPress but want to get started, so that they&#8217;ll be able to follow the presentations and conversations littered with WordPress-specific vocabulary over the weekend. Ticket sales just opened, so get your tickets now.</p>\n<p>For a <a href=\""http://central.wordcamp.org/schedule/\"">schedule of all upcoming WordCamps</a>, visit <a href=\""http://central.wordcamp.org/\"">wordcamp.org</a>. The autumn schedule is already packed! If you don&#8217;t see WordCamp in your area and are interested in organizing one, <a href=\""http://central.wordcamp.org/about/\"">get more information and let us know</a>.</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:58:\""http://wordpress.org/news/2010/06/summer-of-wordcamp/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:6;a:6:{s:4:\""data\"";s:41:\""\n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:26:\""WordPress 3.0 \""Thelonious\""\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:45:\""http://wordpress.org/news/2010/06/thelonious/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:54:\""http://wordpress.org/news/2010/06/thelonious/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Thu, 17 Jun 2010 16:26:36 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:1:{i:0;a:5:{s:4:\""data\"";s:8:\""Releases\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1380\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:341:\""Arm your vuvuzelas: WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is now available for download (or upgrade within your dashboard). Major new features in this release include a sexy new default theme called Twenty Ten. Theme developers have new APIs that allow [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:14:\""Matt Mullenweg\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:38078:\""<p>Arm your vuvuzelas: WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is <a href=\""http://wordpress.org/download/\"">now available for download</a> (or <a href=\""http://codex.wordpress.org/Dashboard_Updates_SubPanel\"">upgrade within your dashboard</a>). Major new features in this release include a sexy <strong>new default theme called Twenty Ten</strong>. Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, <a href=\""http://codex.wordpress.org/Appearance_Menus_SubPanel\"">menus</a> (no more file editing), <a href=\""http://codex.wordpress.org/Custom_Post_Types\"">post types</a>, and <a href=\""http://codex.wordpress.org/Custom_Taxonomies\"">taxonomies</a>. (Twenty Ten theme shows all of that off.) Developers and network admins will appreciate the long-awaited <strong>merge of MU and WordPress</strong>, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation. As a user, you will love the new <strong>lighter interface</strong>, the contextual help on every screen, the <strong>1,217 bug fixes and feature enhancements</strong>, bulk updates so you can upgrade 15 plugins at once with a single click, and blah blah blah just watch the video. <img src=\'http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif\' alt=\':)\' class=\'wp-smiley\' /> <em>(In HD, if you can, so you can catch the Easter eggs.)</em></p>\n<p><object classid=\""clsid:d27cdb6e-ae6d-11cf-96b8-444553540000\"" width=\""640\"" height=\""360\"" codebase=\""http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0\""><param name=\""flashvars\"" value=\""guid=BQtfIEY1&amp;width=640&amp;height=360&amp;locksize=no&amp;dynamicseek=false&amp;qc_publisherId=p-18-mFEk4J448M\"" /><param name=\""src\"" value=\""http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.21\"" /><param name=\""wmode\"" value=\""transparent\"" /><param name=\""allowfullscreen\"" value=\""true\"" /><embed type=\""application/x-shockwave-flash\"" width=\""640\"" height=\""360\"" src=\""http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.21\"" allowfullscreen=\""true\"" wmode=\""transparent\"" flashvars=\""guid=BQtfIEY1&amp;width=640&amp;height=360&amp;locksize=no&amp;dynamicseek=false&amp;qc_publisherId=p-18-mFEk4J448M\""></embed></object></p>\n<p>If you&#8217;d like to embed the WordPress 3.0 video tour in your blog, copy and paste this code for the high quality version:</p>\n<pre class=\""brush: xml;\"">&lt;embed src=&quot;http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.21&quot; type=&quot;application/x-shockwave-flash&quot; width=&quot;640&quot; height=&quot;360&quot; wmode=&quot;transparent&quot; seamlesstabbing=&quot;true&quot; allowfullscreen=&quot;true&quot; allowscriptaccess=&quot;always&quot; overstretch=&quot;true&quot; flashvars=&quot;guid=BQtfIEY1&amp;amp;width=640&amp;amp;height=360&amp;amp;locksize=no&amp;amp;dynamicseek=false&amp;amp;qc_publisherId=p-18-mFEk4J448M&quot; title=&quot;Introducing WordPress 3.0 &amp;quot;Thelonious&amp;quot;&quot;&gt;&lt;/embed&gt;</pre>\n<p>For a more comprehensive look at everything that has improved in 3.0 check out <a href=\""http://codex.wordpress.org/Version_3.0\"">3.0&#8242;s Codex page</a> or the <a href=\""http://core.trac.wordpress.org/query?group=status&amp;milestone=3.0&amp;desc=1&amp;order=priority\"">long list of issues in Trac</a>. (We&#8217;re trying to keep these announcement posts shorter.) Whew! That&#8217;s a lot packed into one release. I can&#8217;t think of a better way to kick off the 3.X cycle we&#8217;ll be in for the next two and a half years.</p>\n<h3>The Future</h3>\n<p>Normally this is where I&#8217;d say we&#8217;re about to start work on 3.1, but we&#8217;re actually not. We&#8217;re going to take a release cycle off to focus on all of the things around WordPress. The growth of the community has been breathtaking, including over 10.3 million downloads of version 2.9, but so much of our effort has been focused on the core software it hasn&#8217;t left much time for anything else. Over the next three months we&#8217;re going to split into ninja/pirate teams focused on different areas of the around-WordPress experience, including the showcase, Codex, forums, profiles, update and compatibility APIs, theme directory, plugin directory, mailing lists, core plugins, wordcamp.org&#8230; the possibilities are endless. The goal of the teams isn&#8217;t going to be to make things perfect all at once, just better than they are today. We think this investment of time will give us a much stronger infrastructure to grow WordPress.org for the many tens of millions of users that will join us during the 3.X release cycle.</p>\n<h3>It Takes a Village</h3>\n<p>I&#8217;m proud to acknowledge the contributions of the following <strong>218</strong> people to the 3.0 release cycle. These are the folks that make WordPress what it is, whose collaboration and hard work enable us to build something greater than the sum of our parts. In alphabetical order, of course.</p>\n<p><strong>Committers:</strong> <a href=\""http://www.laptoptips.ca/\"">azaozz (Andrew Ozz)</a> (<a title=\""azaozz at WP Profiles\"" href=\""http://profiles.wordpress.org/azaozz\"">prof</a>), <a href=\""http://dd32.id.au/\"">dd32 (Dion Hulse)</a> (<a title=\""dd32 at WP Profiles\"" href=\""http://profiles.wordpress.org/dd32\"">prof</a>), <a href=\""http://ocaoimh.ie/\"">donncha (Donncha O Caoimh)</a> (<a title=\""donncha at WP Profiles\"" href=\""http://profiles.wordpress.org/donncha\"">prof</a>), <a href=\""http://iammattthomas.com/\"">iammattthomas (Matt Thomas)</a> (<a title=\""iammattthomas at WP Profiles\"" href=\""http://profiles.wordpress.org/iammattthomas\"">prof</a>), <a href=\""http://josephscott.org/\"">josephscott (Joseph Scott)</a> (<a title=\""josephscott at WP Profiles\"" href=\""http://profiles.wordpress.org/josephscott\"">prof</a>), <a href=\""http://txfx.net/\"">markjaquith (Mark Jaquith)</a> (<a title=\""markjaquith at WP Profiles\"" href=\""http://profiles.wordpress.org/markjaquith\"">prof</a>), <a href=\""http://ma.tt/\"">matt (Matt Mullenweg)</a> (<a title=\""matt at WP Profiles\"" href=\""http://profiles.wordpress.org/matt\"">prof</a>), <a href=\""http://andrewnacin.com/\"">nacin (Andrew Nacin)</a> (<a title=\""nacin at WP Profiles\"" href=\""http://profiles.wordpress.org/nacin\"">prof</a>), <a href=\""http://nikolay.bg/\"">nbachiyski (Николай Бачийски)</a> (<a title=\""nbachiyski at WP Profiles\"" href=\""http://profiles.wordpress.org/nbachiyski\"">prof</a>), <a href=\""http://boren.nu/\"">ryan (Ryan Boren)</a> (<a title=\""ryan at WP Profiles\"" href=\""http://profiles.wordpress.org/ryan\"">prof</a>), <a href=\""http://blog.ftwr.co.uk/\"">westi (Peter Westwood)</a> (<a title=\""westi at WP Profiles\"" href=\""http://profiles.wordpress.org/westi\"">prof</a>), and <a href=\""http://wpmututorials.com/\"">wpmuguru (Ron Rennick)</a> (<a title=\""wpmuguru at WP Profiles\"" href=\""http://profiles.wordpress.org/wpmuguru\"">prof</a>). <strong>Contributors:</strong> <a href=\""http://xavisys.com/\"">aaroncampbell (Aaron Campbell)</a> (<a title=\""aaroncampbell at WP Profiles\"" href=\""http://profiles.wordpress.org/aaroncampbell\"">prof</a>), akerem (<a title=\""akerem at WP Profiles\"" href=\""http://profiles.wordpress.org/akerem\"">prof</a>), <a href=\""http://alexking.org/\"">alexkingorg (Alex King)</a> (<a title=\""alexkingorg at WP Profiles\"" href=\""http://profiles.wordpress.org/alexkingorg\"">prof</a>), amattie (<a title=\""amattie at WP Profiles\"" href=\""http://profiles.wordpress.org/amattie\"">prof</a>), <a href=\""http://notfornoone.com/\"">ampt (Luke Gallagher)</a> (<a title=\""ampt at WP Profiles\"" href=\""http://profiles.wordpress.org/ampt\"">prof</a>), <a href=\""http://wpmututorials.com/\"">andrea_r</a> (<a title=\""andrea_r at WP Profiles\"" href=\""http://profiles.wordpress.org/andrea_r\"">prof</a>), <a href=\""http://andreasnurbo.com/\"">andreasnrb (Andreas Nurbo)</a> (<a title=\""andreasnrb at WP Profiles\"" href=\""http://profiles.wordpress.org/andreasnrb\"">prof</a>), <a href=\""http://twitter.com/anilo4ever\"">anilo4ever (Angelo Verona)</a> (<a title=\""anilo4ever at WP Profiles\"" href=\""http://profiles.wordpress.org/anilo4ever\"">prof</a>), <a href=\""http://apeatling.wordpress.com/\"">apeatling (Andy Peatling)</a> (<a title=\""apeatling at WP Profiles\"" href=\""http://profiles.wordpress.org/apeatling\"">prof</a>), <a href=\""http://blog.apokalyptik.com/\"">apokalyptik (Demitrious Kelly)</a> (<a title=\""apokalyptik at WP Profiles\"" href=\""http://profiles.wordpress.org/apokalyptik\"">prof</a>), <a href=\""http://www.mailpress.org/\"">arena (André Renaut)</a> (<a title=\""arena at WP Profiles\"" href=\""http://profiles.wordpress.org/arena\"">prof</a>), <a href=\""http://barry.wordpress.com/\"">barry (Barry Abrahamson)</a> (<a title=\""barry at WP Profiles\"" href=\""http://profiles.wordpress.org/barry\"">prof</a>), <a href=\""http://digitalize.ca/\"">batmoo (Mohammad Jangda)</a> (<a title=\""batmoo at WP Profiles\"" href=\""http://profiles.wordpress.org/batmoo\"">prof</a>), <a href=\""http://dentedreality.com.au/\"">beaulebens (Beau Lebens)</a> (<a title=\""beaulebens at WP Profiles\"" href=\""http://profiles.wordpress.org/beaulebens\"">prof</a>), <a href=\""http://use.perl.org/~belg4mit/\"">belg4mit</a> (<a title=\""belg4mit at WP Profiles\"" href=\""http://profiles.wordpress.org/belg4mit\"">prof</a>), <a href=\""http://matthewgrichmond.com/dev/\"">bigdawggi (Matthew G. Richmond)</a> (<a title=\""blepoxp at WP Profiles\"" href=\""http://profiles.wordpress.org/blepoxp\"">prof</a>), <a href=\""http://fullthrottledevelopment.com/\"">blepoxp (Glenn Ansley)</a> (<a title=\""blepoxp at WP Profiles\"" href=\""http://profiles.wordpress.org/blepoxp\"">prof</a>), <a href=\""http://twitter.com/thenbrent\"">brentes (Brent Shepherd)</a> (<a title=\""brentes at WP Profiles\"" href=\""http://profiles.wordpress.org/brentes\"">prof</a>), <a href=\""http://colinger.com/\"">briancolinger (Brian Colinger)</a> (<a title=\""briancolinger at WP Profiles\"" href=\""http://profiles.wordpress.org/briancolinger\"">prof</a>), <a href=\""http://www.bumbu.ru/\"">bumbu</a> (<a title=\""bumbu at WP Profiles\"" href=\""http://profiles.wordpress.org/bumbu\"">prof</a>), <a href=\""http://www.caesarsgrunt.com/\"">caesarsgrunt (Caesar Schinas)</a> (<a title=\""caesarsgrunt at WP Profiles\"" href=\""http://profiles.wordpress.org/caesarsgrunt\"">prof</a>), camiloclc (<a title=\""camiloclc at WP Profiles\"" href=\""http://profiles.wordpress.org/camiloclc\"">prof</a>), CAMWebDesign (<a title=\""CAMWebDesign at WP Profiles\"" href=\""http://profiles.wordpress.org/CAMWebDesign\"">prof</a>), carbolineum (<a title=\""carbolineum at WP Profiles\"" href=\""http://profiles.wordpress.org/carbolineum\"">prof</a>), <a href=\""http://blog.caspie.net/\"">caspie</a> (<a title=\""caspie at WP Profiles\"" href=\""http://profiles.wordpress.org/caspie\"">prof</a>), <a href=\""http://www.catiakitahara.com.br/\"">catiakitahara (Cátia Kitahara)</a> (<a title=\""catiakitahara at WP Profiles\"" href=\""http://profiles.wordpress.org/catiakitahara\"">prof</a>), <a href=\""http://www.clarksonenergyhomes.com/wordpress/\"">CharlesClarkson (Charles Clarkson)</a> (<a title=\""CharlesClarkson at WP Profiles\"" href=\""http://profiles.wordpress.org/CharlesClarkson\"">prof</a>), <a href=\""http://chdorner.com/\"">chdorner (Christof Dorner)</a> (<a title=\""chdorner at WP Profiles\"" href=\""http://profiles.wordpress.org/chdorner\"">prof</a>), <a href=\""http://gaarai.com/\"">chrisbliss18 (Chris Jean)</a> (<a title=\""chrisbliss18 at WP Profiles\"" href=\""http://profiles.wordpress.org/chrisbliss18\"">prof</a>), <a href=\""http://vocecommunications.com/\"">chrisscott (Chris Scott)</a> (<a title=\""chrisscott at WP Profiles\"" href=\""http://profiles.wordpress.org/chrisscott\"">prof</a>), <a href=\""http://brandonallen.org/\"">cnorris23 (Brandon Allen)</a> (<a title=\""cnorris23 at WP Profiles\"" href=\""http://profiles.wordpress.org/cnorris23\"">prof</a>), <a href=\""http://coffee2code.com/\"">coffee2code (Scott Reilly)</a> (<a title=\""coffee2code at WP Profiles\"" href=\""http://profiles.wordpress.org/coffee2code\"">prof</a>), computerwiz908 (<a title=\""computerwiz908 at WP Profiles\"" href=\""http://profiles.wordpress.org/computerwiz908\"">prof</a>), <a href=\""http://www.cyberhobo.net/\"">cyberhobo (Dylan Kuhn)</a> (<a title=\""cyberhobo at WP Profiles\"" href=\""http://profiles.wordpress.org/cyberhobo\"">prof</a>), <a href=\""http://dan-cole.com/\"">dancole (Dan Cole)</a> (<a title=\""dancole at WP Profiles\"" href=\""http://profiles.wordpress.org/dancole\"">prof</a>), <a href=\""http://danielkoskinen.com/\"">Daniel Koskinen</a> <!--PROF?-->, <a href=\""http://gsocdk.wordpress.com/\"">deepak.seth (Deepak Seth)</a>, <a href=\""http://op111.net/\"">demetris (Δημήτρης Κίκιζας)</a> (<a title=\""demetris at WP Profiles\"" href=\""http://profiles.wordpress.org/demetris\"">prof</a>), <a href=\""http://www.semiologic.com/\"">Denis-de-Bernardy</a> (<a title=\""Denis-de-Bernardy at WP Profiles\"" href=\""http://profiles.wordpress.org/Denis-de-Bernardy\"">prof</a>), <a href=\""http://www.milandinic.com/\"">dimadin (Milan Dinić)</a> (<a title=\""dimadin at WP Profiles\"" href=\""http://profiles.wordpress.org/dimadin\"">prof</a>), <a href=\""http://twitter.com/dndrnkrd\"">dndrnkrd (Dan Drinkard)</a> (<a title=\""dndrnkrd at WP Profiles\"" href=\""http://profiles.wordpress.org/dndrnkrd\"">prof</a>), <a href=\""http://docwhat.org/\"">docwhat</a> (<a title=\""docwhat at WP Profiles\"" href=\""http://profiles.wordpress.org/docwhat\"">prof</a>), <a href=\""http://twitter.com/dougwrites\"">dougwrites</a> (<a title=\""dougwrites at WP Profiles\""<br />\n href=\""http://profiles.wordpress.org/dougwrites\"">prof</a>), <a href=\""http://phiffer.org/\"">dphiffer (Dan Phiffer)</a> (<a title=\""dphiffer at WP Profiles\"" href=\""http://profiles.wordpress.org/dphiffer\"">prof</a>), dragoonis (<a title=\""dragoonis at WP Profiles\"" href=\""http://profiles.wordpress.org/dragoonis\"">prof</a>), <a href=\""http://wpvibe.com/\"">dremeda (Dre Armeda)</a> (<a title=\""dremeda at WP Profiles\"" href=\""http://profiles.wordpress.org/dremeda\"">prof</a>), dtoj <!--PROF?-->, <a href=\""http://dougal.gunters.org/\"">dougal (Dougal Campbell)</a> (<a title=\""dougal at WP Profiles\"" href=\""http://profiles.wordpress.org/dougal\"">prof</a>), <a href=\""http://lionsgoroar.co.uk/\"">duck_ (Jon Cave)</a> (<a title=\""duck_ at WP Profiles\"" href=\""http://profiles.wordpress.org/duck_\"">prof</a>), <a href=\""http://dxjones.com/\"">dxjones (David Jones)</a> (<a title=\""dxjones at WP Profiles\"" href=\""http://profiles.wordpress.org/dxjones\"">prof</a>), <a href=\""http://eddieringle.com/\"">eddieringle (Eddie Ringle)</a> (<a title=\""eddieringle at WP Profiles\"" href=\""http://profiles.wordpress.org/eddieringle\"">prof</a>), <a href=\""http://mindreantre.se/\"">edward mindreantre (Edward Hevlund)</a>, eoinomurchu (<a title=\""eoinomurchu at WP Profiles\"" href=\""http://profiles.wordpress.org/eoinomurchu\"">prof</a>), <a href=\""http://field2.com/\"">empireoflight/Ben Dunkle</a> (<a title=\""empireoflight at WP Profiles\"" href=\""http://profiles.wordpress.org/empireoflight\"">prof</a>), <a href=\""http://www.mindsharestrategy.com/\"">ericmann (Eric Mann)</a> (<a title=\""ericmann at WP Profiles\"" href=\""http://profiles.wordpress.org/ericmann\"">prof</a>), <a href=\""http://www.eddiemonge.com/\"">etiger13 (Eddie Monge Jr.)</a> (<a title=\""etiger13 at WP Profiles\"" href=\""http://profiles.wordpress.org/etiger13\"">prof</a>), <a href=\""http://www.ilfilosofo.com/\"">filosofo (Austin Matzko)</a> (<a title=\""filosofo at WP Profiles\"" href=\""http://profiles.wordpress.org/filosofo\"">prof</a>), firebird75 (<a title=\""firebird75 at WP Profiles\"" href=\""http://profiles.wordpress.org/firebird75\"">prof</a>), <a href=\""http://www.frankieroberto.com/\"">frankieroberto (Frankie Roberto)</a> (<a title=\""frankieroberto at WP Profiles\"" href=\""http://profiles.wordpress.org/frankieroberto\"">prof</a>), <a href=\""http://frumph.net/\"">Frumph (Philip M. Hofer)</a> (<a title=\""Frumph at WP Profiles\"" href=\""http://profiles.wordpress.org/Frumph\"">prof</a>), <a href=\""http://www.garyc40.com/\"">garyc40 (Gary Cao)</a> (<a title=\""garyc40 at WP Profiles\"" href=\""http://profiles.wordpress.org/garyc40\"">prof</a>), <a href=\""http://gaut.am/\"">gautam2011</a> (<a title=\""gautam2011 at WP Profiles\"" href=\""http://profiles.wordpress.org/gautam2011\"">prof</a>), <a href=\""http://twitter.com/garymross\"">Gary Ross (Gazzer)</a> <!--PROF?-->, <a href=\""http://www.dev4press.com/\"">GDragoN (Milan Petrovic)</a> (<a title=\""GDragoN at WP Profiles\"" href=\""http://profiles.wordpress.org/GDragoN\"">prof</a>), <a href=\""http://justintadlock.com/\"">greenshady (Justin Tadlock)</a> (<a title=\""greenshady at WP Profiles\"" href=\""http://profiles.wordpress.org/greenshady\"">prof</a>), <a href=\""http://www.dennismorhardt.de/\"">GIGALinux (Dennis Morhardt)</a> (<a title=\""GIGALinux at WP Profiles\"" href=\""http://profiles.wordpress.org/GIGALinux\"">prof</a>), <a href=\""http://hakre.wordpress.com/\"">hakre</a> (<a title=\""hakre at WP Profiles\"" href=\""http://profiles.wordpress.org/hakre\"">prof</a>), husky (<a title=\""husky at WP Profiles\"" href=\""http://profiles.wordpress.org/husky\"">prof</a>), <a href=\""http://themeshaper.com/\"">iandstewart (Ian Stewart)</a> (<a title=\""iandstewart at WP Profiles\"" href=\""http://profiles.wordpress.org/iandstewart\"">prof</a>), <a href=\""http://ipstenu.org/\"">ipstenu (Mika Epstein)</a> (<a title=\""ipstenu at WP Profiles\"" href=\""http://profiles.wordpress.org/ipstenu\"">prof</a>), <a href=\""http://jacobsantos.com/\"">jacobsantos (Jacob Santos)</a> (<a title=\""jacobsantos at WP Profiles\"" href=\""http://profiles.wordpress.org/jacobsantos\"">prof</a>), <a href=\""http://om4.com.au/\"">jamescollins (James Collins)</a> (<a title=\""jamescollins at WP Profiles\"" href=\""http://profiles.wordpress.org/jamescollins\"">prof</a>), <a href=\""http://jane.wordpress.com\"">jane (Jane Wells)</a> (<a title=\""jane at WP Profiles\"" href=\""http://profiles.wordpress.org/jane\"">prof</a>), <a href=\""http://blog.trailmeme.com/\"">jbsil (Jesse Silverstein)</a> (<a title=\""jbsil at WP Profiles\"" href=\""http://profiles.wordpress.org/jbsil\"">prof</a>), <a href=\""http://bethesignal.org/\"">jdub (Jeff Waugh)</a> (<a title=\""jdub at WP Profiles\"" href=\""http://profiles.wordpress.org/jdub\"">prof</a>), <a href=\""http://www.jeffikus.com/\"">jeffikus (Jeffrey Pearce)</a> (<a title=\""jeffikus at WP Profiles\"" href=\""http://profiles.wordpress.org/jeffikus\"">prof</a>), <a href=\""http://blog.jeffstieler.com/\"">jeffstieler (Jeff Stieler)</a> (<a title=\""jeffstieler at WP Profiles\"" href=\""http://profiles.wordpress.org/jeffstieler\"">prof</a>), <a href=\""http://simianuprising.com/\"">jeremyclarke (Jeremy Clarke)</a> (<a title=\""jeremyclarke at WP Profiles\"" href=\""http://profiles.wordpress.org/jeremyclarke\"">prof</a>), <a href=\""http://www.jfarthing.com/\"">jfarthing84 (Jeff Farthing)</a> (<a title=\""jfarthing84 at WP Profiles\"" href=\""http://profiles.wordpress.org/jfarthing84\"">prof</a>), <a href=\""http://www.jamesdimick.com/\"">Jick (James Dimick)</a> (<a title=\""Jick at WP Profiles\"" href=\""http://profiles.wordpress.org/Jick\"">prof</a>), <a href=\""http://jonsview.com/\"">jmstacey (Jon Stacey)</a> (<a title=\""jmstacey at WP Profiles\"" href=\""http://profiles.wordpress.org/jmstacey\"">prof</a>), <a href=\""http://jobjorn.se/\"">jobjorn (Jobjörn Folkesson)</a> (<a title=\""jobjorn at WP Profiles\"" href=\""http://profiles.wordpress.org/jobjorn\"">prof</a>), <a href=\""http://devel.kostdoktorn.se/\"">johanee (Johan Eenfeldt)</a> (<a title=\""johanee at WP Profiles\"" href=\""http://profiles.wordpress.org/johanee\"">prof</a>), <a href=\""http://lud.icro.us/\"">johnbillion (John Blackbourn)</a> (<a title=\""johnbillion at WP Profiles\"" href=\""http://profiles.wordpress.org/johnbillion\"">prof</a>), <a href=\""http://johnjamesjacoby.com/\"">johnjamesjacoby/jjj (John James Jacoby)</a> (<a title=\""johnjamesjacoby at WP Profiles\"" href=\""http://profiles.wordpress.org/johnjamesjacoby\"">prof</a>), <a href=\""http://johnjosephbachir.org/\"">johnjosephbachir (John Joseph Bachir)</a> (<a title=\""johnjosephbachir at WP Profiles\"" href=\""http://profiles.wordpress.org/johnjosephbachir\"">prof</a>), <a href=\""http://johnluetke.net/\"">johnl1479 (John Luetke)</a> (<a title=\""johnl1479 at WP Profiles\"" href=\""http://profiles.wordpress.org/johnl1479\"">prof</a>), <a href=\""http://john.onolan.org/\"">johnonolan (John O’Nolan)</a> (<a title=\""johnonolan at WP Profiles\"" href=\""http://profiles.wordpress.org/johnonolan\"">prof</a>), <a href=\""http://www.johnpbloch.com/\"">JohnPBloch/wmrom (John Bloch)</a> (<a title=\""JohnPBloch at WP Profiles\"" href=\""http://profiles.wordpress.org/JohnPBloch\"">prof</a>), <a href=\""http://yoast.com/\"">joostdevalk/yoast (Joost de Valk)</a> (<a title=\""joostdevalk at WP Profiles\"" href=\""http://profiles.wordpress.org/joostdevalk\"">prof</a>), <a href=\""http://aaron.jorb.in/\"">jorbin (Aaron Jorbin)</a> (<a title=\""jorbin at WP Profiles\"" href=\""http://profiles.wordpress.org/jorbin\"">prof</a>), joshtime (<a title=\""joshtime at WP Profiles\"" href=\""http://profiles.wordpress.org/joshtime\"">prof</a>), <a href=\""http://serenelabs.com/\"">jshreve</a> (<a title=\""jshreve at WP Profiles\"" href=\""http://profiles.wordpress.org/jshreve\"">prof</a>), <a href=\""http://tyco.ws/\"">junsuijin</a> (<a title=\""junsuijin at WP Profiles\"" href=\""http://profiles.wordpress.org/junsuijin\"">prof</a>), <a href=\""http://www.wangstedt.net/\"">kallewangstedt (Karl Wångstedt)</a> (<a title=\""kallewangstedt at WP Profiles\"" href=\""http://profiles.wordpress.org/kallewangstedt\"">prof</a>), <a href=\""http://www.keighl.com/\"">keighl (Kyle Truscott)</a> (<a title=\""keighl at WP Profiles\"" href=\""http://profiles.wordpress.org/keighl\"">prof</a>), <a href=\""http://agapetry.net/\"">kevinB (Kevin Behrens)</a> (<a title=\""kevinB at WP Profiles\"" href=\""http://profiles.wordpress.org/kevinB\"">prof</a>), <a href=\""http://drylk.com/\"">koopersmith (Daryl Koopersmith)</a> (<a title=\""koopersmith at WP Profiles\"" href=\""http://profiles.wordpress.org/koopersmith\"">prof</a>), <a href=\""http://www.kpdesign.net/\"">kpdesign (Kim Parsell)<br />\n</a> (<a title=\""kpdesign at WP Profiles\"" href=\""http://profiles.wordpress.org/kpdesign\"">prof</a>), <a href=\""http://www.ktdreyer.com/\"">ktdreyer (Ken Dreyer)</a> (<a title=\""ktdreyer at WP Profiles\"" href=\""http://profiles.wordpress.org/ktdreyer\"">prof</a>), <a href=\""http://kurtmckee.livejournal.com/\"">kurtmckee (Kurt McKee)</a> (<a title=\""kurtmckee at WP Profiles\"" href=\""http://profiles.wordpress.org/kurtmckee\"">prof</a>), <a href=\""http://moggy.laceous.com/\"">laceous</a> (<a title=\""laceous at WP Profiles\"" href=\""http://profiles.wordpress.org/laceous\"">prof</a>), <a href=\""http://simpledream.net/\"">lancewillett (Lance Willett)</a> (<a title=\""lancewillett at WP Profiles\"" href=\""http://profiles.wordpress.org/lancewillett\"">prof</a>), <a href=\""http://lloydbudd.com/\"">lloydbudd (Lloyd Budd)</a> (<a title=\""lloydbudd at WP Profiles\"" href=\""http://profiles.wordpress.org/lloydbudd\"">prof</a>), lriggle (<a title=\""lriggle at WP Profiles\"" href=\""http://profiles.wordpress.org/lriggle\"">prof</a>), markauk (<a title=\""markauk at WP Profiles\"" href=\""http://profiles.wordpress.org/markauk\"">prof</a>), <a href=\""http://www.mark-mcwilliams.com/\"">markmcwilliams (Mark McWilliams)</a> (<a title=\""markmcwilliams at WP Profiles\"" href=\""http://profiles.wordpress.org/markmcwilliams\"">prof</a>), <a href=\""http://markoheijnen.com/\"">markoheijnen (Marko Heijnen)</a> (<a title=\""markoheijnen at WP Profiles\"" href=\""http://profiles.wordpress.org/markoheijnen\"">prof</a>), <a href=\""http://markup.com.ua/\"">markup (Sasha Mukhin)</a> (<a title=\""markup at WP Profiles\"" href=\""http://profiles.wordpress.org/markup\"">prof</a>), mattsains (<a title=\""mattsains at WP Profiles\"" href=\""http://profiles.wordpress.org/mattsains\"">prof</a>), <a href=\""http://matiasventura.com/\"">matveb (Matias Ventura)</a> (<a title=\""matveb at WP Profiles\"" href=\""http://profiles.wordpress.org/matveb\"">prof</a>), <a href=\""http://blogwaffe.com/\"">mdawaffe (Michael Adams)</a> (<a title=\""mdawaffe at WP Profiles\"" href=\""http://profiles.wordpress.org/mdawaffe\"">prof</a>) <!--mdwaffe on r12524-->, mentel_br (<a title=\""mentel_br at WP Profiles\"" href=\""http://profiles.wordpress.org/mentel_br\"">prof</a>), <a href=\""http://webdevstudios.com/about/brian-messenlehner/\"">messenlehner (Brian Messenlehner)</a> (<a title=\""messenlehner at WP Profiles\"" href=\""http://profiles.wordpress.org/messenlehner\"">prof</a>), <a href=\""http://twitter.com/miau_jp\"">miau_jp</a> (<a title=\""miau_jp at WP Profiles\"" href=\""http://profiles.wordpress.org/miau_jp\"">prof</a>), <a href=\""http://binarybonsai.com/\"">Michael (Michael Heilemann)</a> (<a title=\""Michael at WP Profiles\"" href=\""http://profiles.wordpress.org/Michael\"">prof</a>), <a href=\""http://codex.wordpress.org/User:MichaelH\"">MichaelH</a> (<a title=\""MichaelH at WP Profiles\"" href=\""http://profiles.wordpress.org/MichaelH\"">prof</a>), <a href=\""http://mikeschinkel.com/\"">mikeschinkel (Mike Schinkel)</a> (<a title=\""mikeschinkel at WP Profiles\"" href=\""http://profiles.wordpress.org/mikeschinkel\"">prof</a>), Miloslav Beňo <!--r14540, r14545-->, <a href=\""http://www.minusfive.com/\"">minusfive</a> (<a title=\""minusfive at WP Profiles\"" href=\""http://profiles.wordpress.org/minusfive\"">prof</a>), <a href=\""http://blogyul.miqrogroove.com/\"">miqrogroove (Robert Chapin)</a> (<a title=\""miqrogroove at WP Profiles\"" href=\""http://profiles.wordpress.org/miqrogroove\"">prof</a>), <a href=\""http://maisonbisson.com/\"">misterbisson (Casey Bisson)</a> (<a title=\""misterbisson at WP Profiles\"" href=\""http://profiles.wordpress.org/misterbisson\"">prof</a>), <a href=\""http://mitcho.com/\"">mitchoyoshitaka (mitcho (Michael 芳貴 Erlewine))</a> (<a title=\""mitchoyoshitaka at WP Profiles\"" href=\""http://profiles.wordpress.org/mitchoyoshitaka\"">prof</a>), <a href=\""http://blog.mmn-o.se/\"">MMN-o</a> (<a title=\""MMN-o at WP Profiles\"" href=\""http://profiles.wordpress.org/MMN-o\"">prof</a>), <a href=\""http://www.herewithme.fr/a-propos\"">momo360modena (Amaury Balmer)</a> (<a title=\""momo360modena at WP Profiles\"" href=\""http://profiles.wordpress.org/momo360modena\"">prof</a>), <a href=\""http://morganestes.wordpress.com/\"">morganestes (Morgan Estes)</a> (<a title=\""morganestes at WP Profiles\"" href=\""http://profiles.wordpress.org/morganestes\"">prof</a>), <a href=\""http://www.misthaven.org.uk/blog/\"">mrmist (David McFarlane)</a> (<a title=\""mrmist at WP Profiles\"" href=\""http://profiles.wordpress.org/mrmist\"">prof</a>), <a href=\""http://nickmomrik.com/\"">mtdewvirus (Nick Momrik)</a> (<a title=\""mtdewvirus at WP Profiles\"" href=\""http://profiles.wordpress.org/mtdewvirus\"">prof</a>), nadavvin (<a title=\""nadavvin at WP Profiles\"" href=\""http://profiles.wordpress.org/nadavvin\"">prof</a>), <a href=\""http://blog.detlog.org/\"">Nao (Naoko McCracken)</a> (<a title=\""Nao at WP Profiles\"" href=\""http://profiles.wordpress.org/Nao\"">prof</a>), <a href=\""http://www.nathanrice.net/\"">nathanrice (Nathan Rice)</a> (<a title=\""nathanrice at WP Profiles\"" href=\""http://profiles.wordpress.org/nathanrice\"">prof</a>), <a href=\""http://www.neotrinity.at/\"">neoxx (Bernhard Riedl)</a> (<a title=\""neoxx at WP Profiles\"" href=\""http://profiles.wordpress.org/nathanrice\"">prof</a>), <a href=\""http://www.niallkennedy.com/\"">niallkennedy (Niall Kennedy)</a> (<a title=\""niallkennedy at WP Profiles\"" href=\""http://profiles.wordpress.org/niallkennedy\"">prof</a>), <a href=\""http://www.rpmurphy.com/\"">ninjaWR (Ryan Murphy)</a> (<a title=\""ninjaWR at WP Profiles\"" href=\""http://profiles.wordpress.org/ninjaWR\"">prof</a>), <a href=\""http://noel.io/\"">noel (Noël Jackson)</a> (<a title=\""noel at WP Profiles\"" href=\""http://profiles.wordpress.org/noel\"">prof</a>), <a href=\""http://nomulous.com/\"">nomulous (Fletcher Tomalty)</a> (<a title=\""nomulous at WP Profiles\"" href=\""http://profiles.wordpress.org/nomulous\"">prof</a>), <a href=\""http://ocean90.wphelper.de/\"">ocean90 (Dominik Schilling)</a> (<a title=\""ocean90 at WP Profiles\"" href=\""http://profiles.wordpress.org/ocean90\"">prof</a>), <a href=\""http://ottodestruct.com/\"">Otto42 (Samuel Wood)</a> (<a title=\""Otto42 at WP Profiles\"" href=\""http://profiles.wordpress.org/Otto42\"">prof</a>), pedger (<a title=\""pedger at WP Profiles\"" href=\""http://profiles.wordpress.org/pedger\"">prof</a>), <a href=\""http://developersmind.com/\"">PeteMall</a> (<a title=\""PeteMall at WP Profiles\"" href=\""http://profiles.wordpress.org/PeteMall\"">prof</a>), pampfelimetten (<a title=\""pampfelimetten at WP Profiles\"" href=\""http://profiles.wordpress.org/pampfelimetten\"">prof</a>), pnettle (<a title=\""pnettle at WP Profiles\"" href=\""http://profiles.wordpress.org/pnettle\"">prof</a>), <a href=\""http://www.pslabs.cl/\"">PotterSys (Juan)</a> (<a title=\""PotterSys at WP Profiles\"" href=\""http://profiles.wordpress.org/PotterSys\"">prof</a>), <a href=\""http://cnpstudio.com/\"">prettyboymp (Michael Pretty)</a> (<a title=\""prettyboymp at WP Profiles\"" href=\""http://profiles.wordpress.org/prettyboymp\"">prof</a>), <a href=\""http://ptahdunbar.com/\"">ptahdunbar (Ptah Dunbar)</a> (<a title=\""ptahdunbar at WP Profiles\"" href=\""http://profiles.wordpress.org/ptahdunbar\"">prof</a>), <a href=\""http://www.bdihot.co.il/\"">ramiy</a> (<a title=\""ramiy at WP Profiles\"" href=\""http://profiles.wordpress.org/ramiy\"">prof</a>), <a href=\""http://ranh.co.il/\"">RanYanivHartstein (Ran Yaniv Hartstein)</a> (<a title=\""RanYanivHartstein at WP Profiles\"" href=\""http://profiles.wordpress.org/RanYanivHartstein\"">prof</a>), <a href=\""http://langui.sh/\"">reaperhulk (Paul Kehrer)</a> (<a title=\""reaperhulk at WP Profiles\"" href=\""http://profiles.wordpress.org/reaperhulk\"">prof</a>), reko (<a title=\""reko at WP Profiles\"" href=\""http://profiles.wordpress.org/reko\"">prof</a>), <a href=\""http://remiprevost.com/\"">remi (Rémi Prévost)</a> (<a title=\""remi at WP Profiles\"" href=\""http://profiles.wordpress.org/remi\"">prof</a>), <a href=\""http://toys.lerdorf.com/\"">rlerdorf (Rasmus Lerdorf)</a> (<a title=\""rlerdorf at WP Profiles\"" href=\""http://profiles.wordpress.org/rlerdorf\"">prof</a>) <!--ALSO r13684-->, <a href=\""http://ryanmccue.info/\"">rmccue (Ryan McCue)</a> (<a title=\""rmccue at WP Profiles\"" href=\""http://profiles.wordpress.org/rmccue\"">prof</a>), rooodini (<a title=\""rooodini at WP Profiles\"" href=\""http://profiles.wordpress.org/rooodini\"">prof</a>), rovo89 (<a title=\""rovo89 at WP Profiles\"" href=\""http://profiles.wordpress.org/rovo89\"">prof</a>), <a href=\""http://ruslany.net/\"">ruslany</a> (<a title=\""ruslany at WP Profiles\"" href=<br />\n\""http://profiles.wordpress.org/ruslany\"">prof</a>), <a href=\""http://skcdev.com/\"">sc0ttkclark (Scott Kingsley Clark)</a> (<a title=\""sc0ttkclark at WP Profiles\"" href=\""http://profiles.wordpress.org/sc0ttkclark\"">prof</a>), scottbasgaard (Scott Basgaard) (<a title=\""scottbasgaard at WP Profiles\"" href=\""http://profiles.wordpress.org/scottbasgaard\"">prof</a>), ScottMac (<a title=\""ScottMac at WP Profiles\"" href=\""http://profiles.wordpress.org/ScottMac\"">prof</a>), <a href=\""http://scribu.net/\"">scribu</a> (<a title=\""scribu at WP Profiles\"" href=\""http://profiles.wordpress.org/scribu\"">prof</a>), <a href=\""http://sergeybiryukov.ru/\"">SergeyBiryukov (Сергей Бирюков)</a> (<a title=\""SergeyBiryukov at WP Profiles\"" href=\""http://profiles.wordpress.org/SergeyBiryukov\"">prof</a>), <a href=\""http://bugssite.org/\"">ShaneF</a> (<a title=\""ShaneF at WP Profiles\"" href=\""http://profiles.wordpress.org/ShaneF\"">prof</a>), <a href=\""http://sillybean.net/\"">sillybean (Stephanie Leary)</a> (<a title=\""sillybean at WP Profiles\"" href=\""http://profiles.wordpress.org/sillybean\"">prof</a>), <a href=\""http://simekdesign.eu/\"">Simek (Bartosz Kaszubowski)</a> (<a title=\""simek at WP Profiles\"" href=\""http://profiles.wordpress.org/simek\"">prof</a>), <a href=\""http://www.simonwheatley.co.uk/\"">simonwheatley (Simon Wheatley)</a> (<a title=\""simonwheatley at WP Profiles\"" href=\""http://profiles.wordpress.org/simonwheatley\"">prof</a>), <a href=\""http://simos.info/blog/\"">simosx (Σίμος Ξενιτέλλης)</a> (<a title=\""simosx at WP Profiles\"" href=\""http://profiles.wordpress.org/simosx\"">prof</a>), <a href=\""http://www.poradnik-webmastera.com/\"">sirzooro (Daniel Frużyński)</a> (<a title=\""sirzooro at WP Profiles\"" href=\""http://profiles.wordpress.org/sirzooro\"">prof</a>), <a href=\""http://sivel.net/\"">sivel (Matt Martz)</a> (<a title=\""sivel at WP Profiles\"" href=\""http://profiles.wordpress.org/sivel\"">prof</a>), <a href=\""http://skeltoac.com/\"">skeltoac (Andy Skelton)</a> (<a title=\""skeltoac at WP Profiles\"" href=\""http://profiles.wordpress.org/skeltoac\"">prof</a>), <a href=\""http://www.lukehowell.com/\"">snumb130 (Luke Howell)</a> (<a title=\""snumb130 at WP Profiles\"" href=\""http://profiles.wordpress.org/snumb130\"">prof</a>), <a href=\""http://rayofsolaris.net/\"">solarissmoke (Samir Shah)</a> (<a title=\""solarissmoke at WP Profiles\"" href=\""http://profiles.wordpress.org/solarissmoke\"">prof</a>), sorich87 (<a title=\""sorich87 at WP Profiles\"" href=\""http://profiles.wordpress.org/sorich87\"">prof</a>), ssandison (<a title=\""ssandison at WP Profiles\"" href=\""http://profiles.wordpress.org/ssandison\"">prof</a>), stencil (<a title=\""stencil at WP Profiles\"" href=\""http://profiles.wordpress.org/stencil\"">prof</a>), <a href=\""http://stephdau.wordpress.com/\"">stephdau (Stephane Daury)</a> (<a title=\""stephdau at WP Profiles\"" href=\""http://profiles.wordpress.org/stephdau\"">prof</a>), <a href=\""http://wp.tekapo.com/\"">tai</a> (<a title=\""tai at WP Profiles\"" href=\""http://profiles.wordpress.org/tai\"">prof</a>), TECannon (Tracy Cannon) (<a title=\""TECannon at WP Profiles\"" href=\""http://profiles.wordpress.org/TECannon\"">prof</a>), <a href=\""http://technosailor.com/\"">technosailor (Aaron Brazell)</a> (<a title=\""technosailor at WP Profiles\"" href=\""http://profiles.wordpress.org/technosailor\"">prof</a>), <a href=\""http://eastcoder.com/\"">tenpura</a> (<a title=\""tenpura at WP Profiles\"" href=\""http://profiles.wordpress.org/tenpura\"">prof</a>), thales.tede <!--PROF?-->, TheDeadMedic (<a title=\""TheDeadMedic at WP Profiles\"" href=\""http://profiles.wordpress.org/TheDeadMedic\"">prof</a>), <a href=\""http://cefm.ca/\"">thee17 (Charles E. Frees-Melvin)</a> (<a title=\""thee17 at WP Profiles\"" href=\""http://profiles.wordpress.org/thee17\"">prof</a>), <a href=\""http://www.toine.ca/\"">thetoine (Antoine Girard)</a> (<a title=\""thetoine at WP Profiles\"" href=\""http://profiles.wordpress.org/thetoine\"">prof</a>), <a href=\""http://bavotasan.com/\"">tinkerpriest (c.bavota)</a> (<a title=\""tinkerpriest at WP Profiles\"" href=\""http://profiles.wordpress.org/tinkerpriest\"">prof</a>), <a href=\""http://tobias.baethge.com/\"">TobiasBg (Tobias Bäthge)</a> (<a title=\""TobiasBg at WP Profiles\"" href=\""http://profiles.wordpress.org/TobiasBg\"">prof</a>), tomtomp (<a title=\""tomtomp at WP Profiles\"" href=\""http://profiles.wordpress.org/tomtomp\"">prof</a>), <a href=\""http://terrychay.com/\"">tychay (Terry Chay)</a> (<a title=\""tychay at WP Profiles\"" href=\""http://profiles.wordpress.org/tychay\"">prof</a>), typeomedia (<a title=\""typeomedia at WP Profiles\"" href=\""http://profiles.wordpress.org/typeomedia\"">prof</a>), <a href=\""http://uglyrobot.com/\"">uglyrobot (Aaron Edwards)</a> (<a title=\""uglyrobot at WP Profiles\"" href=\""http://profiles.wordpress.org/uglyrobot\"">prof</a>), UnderWordPressure (<a title=\""UnderWordPressure at WP Profiles\"" href=\""http://profiles.wordpress.org/UnderWordPressure\"">prof</a>), usermrpapa (<a title=\""usermrpapa at WP Profiles\"" href=\""http://profiles.wordpress.org/usermrpapa\"">prof</a>), <a href=\""http://utkar.sh/\"">Utkarsh (Utkarsh Kukreti)</a> (<a title=\""Utkarsh at WP Profiles\"" href=\""http://profiles.wordpress.org/Utkarsh\"">prof</a>), <a href=\""http://www.ai-development.com/\"">validben (Benoit Gilloz )</a> (<a title=\""validben at WP Profiles\"" href=\""http://profiles.wordpress.org/validben\"">prof</a>), <a href=\""http://www.viper007bond.com/\"">Viper007Bond (Alex Mills)</a> (<a title=\""Viper007Bond at WP Profiles\"" href=\""http://profiles.wordpress.org/Viper007Bond\"">prof</a>), <a href=\""http://blog.sjinks.org.ua/\"">vladimir_kolesnikov (Vladimir Kolesnikov)</a> (<a title=\""vladimir_kolesnikov at WP Profiles\"" href=\""http://profiles.wordpress.org/vladimir_kolesnikov\"">prof</a>), <a href=\""http://edgedesigns.org/\"">willmot (Tom Willmot)</a> (<a title=\""willmot at WP Profiles\"" href=\""http://profiles.wordpress.org/willmot\"">prof</a>), <a href=\""http://emphaticallystatic.org/\"">wahgnube</a> (<a title=\""wahgnube at WP Profiles\"" href=\""http://profiles.wordpress.org/wahgnube\"">prof</a>), <a href=\""http://www.waltervos.com/\"">waltervos (Walter Vos)</a> (<a title=\""waltervos at WP Profiles\"" href=\""http://profiles.wordpress.org/waltervos\"">prof</a>), <a href=\""http://www.nothingcliche.com/\"">wds-chris (Christopher Cochran)</a> (<a title=\""wds-chris at WP Profiles\"" href=\""http://profiles.wordpress.org/wds-chris\"">prof</a>), <a href=\""http://strangework.com/\"">williamsba1 (Brad Williams)</a> (<a title=\""williamsba1 at WP Profiles\"" href=\""http://profiles.wordpress.org/williamsba1\"">prof</a>), <a href=\""http://willnorris.com/\"">wnorris (Will Norris)</a> (<a title=\""wnorris at WP Profiles\"" href=\""http://profiles.wordpress.org/wnorris\"">prof</a>), <a href=\""http://xavier.borderie.net/\"">xibe (Xavier Borderie)</a> (<a title=\""xibe at WP Profiles\"" href=\""http://profiles.wordpress.org/xibe\"">prof</a>), <a href=\""http://blog.yoavfarhi.com/\"">yoavf (Yoav Farhi)</a> (<a title=\""yoavf at WP Profiles\"" href=\""http://profiles.wordpress.org/yoavf\"">prof</a>), <a href=\""http://zeo.my/\"">zeo (Safirul Alredha)</a> (<a title=\""zeo at WP Profiles\"" href=\""http://profiles.wordpress.org/zeo\"">prof</a>), <a href=\""http://h6e.net/\"">znarfor (François Hodierne)</a> (<a title=\""znarfor at WP Profiles\"" href=\""http://profiles.wordpress.org/znarfor\"">prof</a>), and <a href=\""http://zoranzaric.de/\"">zoranzaric (Zoran Zaric)</a> (<a title=\""zoranzaric at WP Profiles\"" href=\""http://profiles.wordpress.org/zoranzaric\"">prof</a>).</p>\n<h3>Bonus</h3>\n<p>If you&#8217;ve made it this far, check out my 2010 State of the Word speech at WordCamp San Francisco, it&#8217;s jam-packed with information on the growth of WordPress, 3.0, what we&#8217;re planning for the future, and the philosophy of WordPress.</p>\n<p><object classid=\""clsid:d27cdb6e-ae6d-11cf-96b8-444553540000\"" width=\""640\"" height=\""360\"" codebase=\""http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0\""><param name=\""flashvars\"" value=\""guid=xj8pDCM4&amp;width=640&amp;height=360&amp;locksize=no&amp;dynamicseek=false&amp;qc_publisherId=p-18-mFEk4J448M\"" /><param name=\""src\"" value=\""http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.21\"" /><param name=\""wmode\"" value=\""transparent\"" /><param name=\""allowfullscreen\"" value=\""true\"" /><embed type=\""application/x-shockwave-flash\"" width=\""640\"" height=\""360\"" src=\""http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.21\"" allowfullscreen=\""true\"" wmode=\""transparent\"" flashvars=\""guid=xj8pDCM4&amp;width=640&amp;height=360&amp;locksize=no&amp;dynamicseek=false&amp;qc_publisherId=p-18-mFEk4J448M\""></embed></object></p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:50:\""http://wordpress.org/news/2010/06/thelonious/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""5\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:7;a:6:{s:4:\""data\"";s:41:\""\n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:7:\""3.0 RC3\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:42:\""http://wordpress.org/news/2010/06/3-0-rc3/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:51:\""http://wordpress.org/news/2010/06/3-0-rc3/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Fri, 11 Jun 2010 20:49:38 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:1:{i:0;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1376\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:257:\""A weekend present, in haiku: Last call; final bugs Itch, scratch, contort; calmly wait For now: RC3 That&#8217;s right. What will hopefully be the final release candidate, RC3, is now available for download and testing. Plugin developers: test your plugins!\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:438:\""<p>A weekend present, in haiku:</p>\n<blockquote><p>Last call; final bugs<br />\nItch, scratch, contort; calmly wait<br />\nFor now: <a href=\""http://wordpress.org/wordpress-3.0-RC3.zip\"">RC3 </a></p></blockquote>\n<p>That&#8217;s right. What will hopefully be the final release candidate, <a href=\""http://wordpress.org/wordpress-3.0-RC3.zip\"">RC3, is now available for download</a> and testing.</p>\n<p>Plugin developers: test your plugins!</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:47:\""http://wordpress.org/news/2010/06/3-0-rc3/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:8;a:6:{s:4:\""data\"";s:47:\""\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:37:\""Expanding the Theme Review Experiment\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:72:\""http://wordpress.org/news/2010/06/expanding-the-theme-review-experiment/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:81:\""http://wordpress.org/news/2010/06/expanding-the-theme-review-experiment/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Wed, 09 Jun 2010 16:06:11 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:3:{i:0;a:5:{s:4:\""data\"";s:9:\""Community\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:2;a:5:{s:4:\""data\"";s:6:\""Themes\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1347\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:272:\""When I was a kid my dad used to practice his typing skills (on a real typewriter no less) with the phrase: Now is the time for all good men to come to the aid of their country. For some reason that has stuck with me all these years. Today I’m going to rephrase and [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:12:\""Joseph Scott\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1962:\""<p>When I was a kid my dad used to practice his typing skills (on a real typewriter no less) with the phrase:</p>\n<blockquote><p>Now is the time for all good men to come to the aid of their country.</p></blockquote>\n<p>For some reason that has stuck with me all these years. Today I’m going to rephrase and re-purpose that line:</p>\n<blockquote><p>Now is the time for great theme developers to come to the aid of their community.</p></blockquote>\n<p>The theme directory has been chugging along for more than a year now. During that time we’ve tinkered with the review process and some of the management tools, but haven’t really opened it up as much as we’d like. It&#8217;s time to rip off the band-aid and take some action; to that end, we&#8217;re looking for community members to help with the process of reviewing themes for the directory.</p>\n<p>Right now this is a bit like a New Year’s resolution to exercise every day: it’s what we need to do, but we’re still figuring out exactly how it will all work. That’s part of the community involvement as well &#8212; we expect that those who pitch in will also help shape the process.</p>\n<p>What’s involved in reviewing themes for the directory? There are some obvious things, such as being familiar with PHP and WordPress theme code (and the <a href=\""http://codex.wordpress.org/Theme_Development_Checklist\"">theme development checklist</a>), with an eye for security issues. You would also need to have the ability to set up a separate install of the latest version of WordPress for testing theme submissions.</p>\n<p>Hopefully a few talented theme developers are reading this right now and saying to themselves, &#8220;I’d love to help! How do I get started?&#8221; Just join the new <a href=\""http://lists.wordpress.org/mailman/listinfo/theme-reviewers\"">theme reviewers mailing list</a> and we&#8217;ll get you up to speed on this new opportunity to come to the aid of your community.</p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:77:\""http://wordpress.org/news/2010/06/expanding-the-theme-review-experiment/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:9;a:6:{s:4:\""data\"";s:41:\""\n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""WordPress 3.0 Release Candidate\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:66:\""http://wordpress.org/news/2010/05/wordpress-3-0-release-candidate/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:75:\""http://wordpress.org/news/2010/05/wordpress-3-0-release-candidate/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Fri, 28 May 2010 02:35:04 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:1:{i:0;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1358\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:345:\""As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What&#8217;s an RC? An RC comes after beta and before the final launch. It means we think we&#8217;ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1993:\""<p>As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What&#8217;s an RC? An RC comes after beta and before the final launch. It means we think we&#8217;ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using WordPress with a wide variety of configurations and hosting setups, it&#8217;s entirely possible that we&#8217;ve missed something. So! For the brave of heart, please download the RC and test it out (but not on your live site unless you&#8217;re extra adventurous). Some things to know:</p>\n<ul>\n<li>Custom menus are finished! Yay!</li>\n<li>Multi-site is all set.</li>\n<li>The look of the WordPress admin has been lightened up a little bit, so you can focus more on your content.</li>\n<li>There are a ton of changes, so plugin authors, please test your plugins <strong>now</strong>, so that if there is a compatibility issue, we can figure it out before the final release.</li>\n<li>Plugin and theme *users* are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.</li>\n<li>There are a couple of <a href=\"" http://core.trac.wordpress.org/report/5\"">known issues</a>.</li>\n</ul>\n<p>If you are testing the RC and come across a bug, you can:</p>\n<ul>\n<li>Report it on the <a href=\""http://lists.automattic.com/mailman/listinfo/wp-testers\"">wp-testers mailing list</a></li>\n<li>Join the dev chat and tell us live at irc.freenode.net #wordpress-dev</li>\n<li>File a bug ticket on the <a href=\""https://core.trac.wordpress.org/query?status=reopened&amp;status=assigned&amp;status=reviewing&amp;status=new&amp;status=accepted&amp;group=status&amp;milestone=3.0\"">WordPress Trac </a></li>\n</ul>\n<p>We hope you enjoy playing with the 3.0 RC as much as we&#8217;ve enjoyed making it for you. Enjoy!</p>\n<p><a href=\""http://wordpress.org/wordpress-3.0-RC1.zip\"">Download WordPress 3.0 RC1</a></p>\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:71:\""http://wordpress.org/news/2010/05/wordpress-3-0-release-candidate/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}}}s:27:\""http://www.w3.org/2005/Atom\"";a:1:{s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:3:{s:4:\""href\"";s:31:\""http://wordpress.org/news/feed/\"";s:3:\""rel\"";s:4:\""self\"";s:4:\""type\"";s:19:\""application/rss+xml\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:44:\""http://purl.org/rss/1.0/modules/syndication/\"";a:2:{s:12:\""updatePeriod\"";a:1:{i:0;a:5:{s:4:\""data\"";s:6:\""hourly\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:15:\""updateFrequency\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""1\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}}}}}}}}s:4:\""type\"";i:128;s:7:\""headers\"";a:8:{s:6:\""server\"";s:5:\""nginx\"";s:4:\""date\"";s:29:\""Thu, 18 Nov 2010 07:10:47 GMT\"";s:12:\""content-type\"";s:23:\""text/xml; charset=UTF-8\"";s:10:\""connection\"";s:5:\""close\"";s:4:\""vary\"";s:15:\""Accept-Encoding\"";s:10:\""x-pingback\"";s:36:\""http://wordpress.org/news/xmlrpc.php\"";s:13:\""last-modified\"";s:29:\""Thu, 30 Sep 2010 03:23:31 GMT\"";s:4:\""x-nc\"";s:11:\""HIT luv 138\"";}s:5:\""build\"";s:14:\""20090627192103\"";}', 'no') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)

    WordPress for iPhone/iPad v2.6 Released September 30th, 2010
    Attention Apple-gadget-owning WordPress users! Have you been using the WordPress iOS app for iPhone and iPad? Or maybe you tried it a while back and thought it wasn’t for you? Either way, the new release — v2.6 — will knock your socks off. Why? A bunch of reasons: Video. Record, upload, attach, and play videos […]
    WordPress Trademark Changes Hands September 9th, 2010
    The WordPress community took a big step forward today when Matt announced that Automattic has donated the WordPress trademark to the non-profit WordPress Foundation. Moving forward, the Foundation will be responsible for safeguarding the trademarked name and logo from misuse toward the end of protecting WordPress and preventing confusion among people trying […]
}}}
"	Viper007Bond
Future Releases	18563	Disallowing editing of .php files in the plugin editor blocks access to allowable extensions		Administration	2.8	normal	minor	Future Release	defect (bug)	new		2011-09-01T04:12:29Z	2011-11-02T00:06:47Z	"By using the editable_extensions filter, a user can disallow the editing of php files (more accurately: files with a php extension...)

{{{
add_filter( 'editable_extensions', 'disallow_php_file_editing' );
function disallow_php_file_editing( $editable_extensions ) {
	unset( $editable_extensions[0] );	
	return $editable_extensions;
}
}}}

However, the file selected when first clicking on the Editor link in the menu is always a php file, so the user is given the ""Files of this type are not editable"" wp_die() message without being presented with a chance to select a file with a different/allowable extension."	trepmal
Future Releases	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
Future Releases	17916	Enqueued styles are only printed on login_footer in wp-login.php		Administration	3.2	normal	normal	Future Release	defect (bug)	reopened		2011-06-28T00:29:48Z	2012-11-05T19:19:34Z	"In my plugin I have this include:
wp_register_style(""cimy_uef_register"", $cuef_css_webpath.""/cimy_uef_register.css"", false, false);

now independently where and when I use the above css, even if I never enqueue or print it... it basically forces the admin panel to be always left instead of the right.

In particular it changes the admin panel menu #adminmenu to stick to the left, also other little things.
The question is:
why this happens even if the CSS is not included at all? Browsing the documentation quickly on that function I didn't find anything useful, please help me."	Cimmo
Future Releases	24084	Fix possible PHP notices after a user is deleted		Administration		normal	normal	Awaiting Review	defect (bug)	new		2013-04-14T22:24:48Z	2013-04-15T23:09:34Z	"`get_comment_author()` doesn't check if a user that has commented still exists and may throw a notice. Also can return the user_login where a user name is expected.

Same in `edit-form-advanced.php` in the code block that outputs ""Last edited by ..."" under the editor."	azaozz
Future Releases	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
Future Releases	22214	Inconsistency in the show_ui parameter for register_post_type		Administration	3.4.2	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-10-17T20:58:42Z	2012-10-18T00:58:36Z	There is an inconsistency with the `show_ui` argument to `register_post_type`. When set to false, the post type listing page is open, while the 'Add new' page is not accessible.	nofearinc
Future Releases	12789	Inconsistent left or right margins on admin screens		Administration		low	minor	Future Release	defect (bug)	new		2010-04-01T02:46:07Z	2012-12-06T06:06:53Z	There are a couple of admin screens where the screen icon is not aligned to the left of the content.	scribu
Future Releases	18101	Last theme reported in Feature Search is Duplicated as first theme in page 2		Administration	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-07-13T13:59:36Z	2011-07-14T11:53:46Z	Search for themes using the features filtering mode. The last theme theme of the first page (if you search for custom background feature the theme is Nona) will be duplicated as the first theme in page 2. Page count in the navigation is correct, and you will get one more theme in the end (e.g. with 121 themes, last page will have two themes instead of just one).	lorthirk
Future Releases	18449	List Table Factory Needs to be Pluggable		Administration	3.1	normal	normal	Future Release	defect (bug)	new		2011-08-16T19:51:33Z	2012-03-31T08:34:37Z	"Better design planning should have been considered for http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/list-table.php

function _get_list_table() is identical to an object factory pattern, which would make more sense as a static member of WP_List_Table.  In other words...

{{{
$wp_list_table = _get_list_table('WP_Terms_List_Table');
}}}

... which looks simple, is actually confusing because it would be more intuitive if written as ...

{{{
$wp_list_table = WP_List_Table::factory('Terms');
}}}

Further, the factory hasn't offered any extensibility.  Locking edit-tags.php against WP_Terms_List_Table makes it unusable for custom taxonomies that need a custom UI.  Despite all of the great API improvements for taxonomies, this case still necessitates duplicating the entire category editing UI within a plugin just to tweak a table column or a link path.

Please adjust the ticket Type and Component as necessary.  It could be a taxonomy design flaw or an administration enhancement, depending how you look at it."	miqrogroove
Future Releases	17675	Masked Domain Issue Introduced with New Update		Administration	3.1.3	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2011-06-03T18:09:03Z	2011-06-03T19:59:41Z	"Hi,

I'm experiencing an issue accessing my wp-admin login page, only when using a masked domain.

My root setup is configured as so:
http://rootdomain.com/othersite/wordpress/

The domain I'm using to access it is located here:
http://redirect.com

When I use the root domain to access the login page directly, there's no problem.  But, when I go to http://redirect.com/wp-admin, or click on any login links while at the redirect.com site, the page doesn't load.  The title bar will load, but nothing else.

This is a new issue introduced with the 3.1.3 update.  The masked domain was working prior to 3.1.3.

I've tried this both on Safari & Firefox (latest versions), using Mac OS X."	ital_dj
Future Releases	20453	Media screen links to non-public post types		Administration		normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-04-16T02:31:56Z	2012-04-16T03:23:46Z	"I have a non-public custom post type registered, so it doesn't get an admin UI.

A file in the media library is attached to one of my custom posts (done at the point the file is uploaded using `media_handle_upload()`). The media item shows up in the Media Library as expected, but the 'Attached To' column links to the editing screen for the parent post, even though the post is non-public.

This allows a user to see the post editing screen for a non-public post type."	johnbillion
Future Releases	21770	Multiple New Feature Pop-ups mess UI		Administration	3.4.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-09-02T11:09:51Z	2013-01-22T03:06:39Z	"WordPress admin and plugins [[Image(http://dl.dropbox.com/u/184353/wordpress-admin-pop-ups.png)]] New Feature Pop-up messages appear on the admin simultaneously, blocking each other messages and functionality. The UI gets seriously messed up.

User attention focuses on how to get rid the overlaping pop-ups rather than reading the messages and understand and start using the new features."	titanas
Future Releases	16162	Pagination and sorting reset after bulk media deletion		Administration	3.1	normal	normal	Future Release	defect (bug)	reopened		2011-01-09T11:43:33Z	2011-10-27T06:23:48Z	When doing Bulk Deletes on paginated Media Library, after performing the delete, I'm back on page 1 regardless on which page I've been before.	hakre
Future Releases	18974	Plugin table IDs can collide with core IDs		Administration	3.3	low	minor	Future Release	defect (bug)	new		2011-10-17T23:14:04Z	2012-01-05T05:33:52Z	"Go to Plugins > Add New and install my ""Local Time"" plugin.

Go to Plugins > Installed Plugins. My plugin's details will show up in italics. This is because the table row is given the ID `local-time` (my plugin's slug) and core has this CSS:

{{{
#utc-time, #local-time {
	padding-left: 25px;
	font-style: italic;
	font-family: sans-serif;
}
}}}

https://core.trac.wordpress.org/browser/tags/3.2.1/wp-admin/css/wp-admin.dev.css#L4287

Targeting this in `options-general.php`:

{{{
<span id=""local-time""><?php printf(__('Local time is <code>%1$s</code>'), date_i18n($timezone_format)); ?></span>
}}}

https://core.trac.wordpress.org/browser/tags/3.2.1/wp-admin/options-general.php#L167

I'm not quite sure why core is using an ID instead of a class. I'm also not quite sure why the plugins table isn't using a prefix of say `plugin-` since the slug can literally be pretty much anything.

Probably better to change the former than the latter for backwards compatibility reasons though."	Viper007Bond
Future Releases	24551	Post locking prevents collaboration		Administration	trunk	high	normal	Awaiting Review	defect (bug)	new		2013-06-10T10:07:32Z	2013-06-10T20:21:22Z	"Occasionally I'll discuss the content of a post with a colleague by opening the editing screen for that post at the same time as my colleague. ''It may be that neither of us are actively editing it'', but we are discussing the content via VOiP or IM or whatever and both looking at it on the editing screen.

The new post editing lock prevents two people from having the editing screen for the same post open at the same time.

[[Image(http://i.imgur.com/PeZ60wd.png)]]

The above modal provides no option for dismissing the modal and viewing the editing screen. Preferably there would be a read-only mode of the editing screen, which disabled the buttons in the publish metabox.

I think this is quite important behaviour. Due to the nature of testing (ie. mostly solitary) it'll be unlikely that people have noticed the new behaviour until people start using it in production environments.

Thoughts?"	johnbillion
Future Releases	17115	Publishing an empty post results in success		Administration	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-04-12T11:32:50Z	2012-11-17T00:15:31Z	"'''Steps to reproduce:'''
1. Go to Add New post screen
1. Publish post
1. Success message is displayed with link to initial auto-draft of post

The issue can be traced back to the `editpost` switch case in `post.php` (line 204), which calls `edit_post()` and `redirect_post()`.

`edit_post()` saves any meta values passed with the post to the auto-draft, which isn't necessarily desirable, and returns the auto-draft post ID.

`redirect_post()` then defaults to status message code 6 which incorrectly reports success in publishing."	kawauso
Future Releases	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
Future Releases	21421	Sanitize/remove admin page slug  from admin menu CSS classes		Administration		normal	normal	Awaiting Review	defect (bug)	new		2012-07-30T11:26:15Z	2013-03-02T21:00:41Z	"As I discovered when testing #21307, browsers won't parse a CSS class name with both underscores and hyphens. Instead, they handle it ''really'' badly.

For example: `.toplevel_page_link-manager` will affect `body` in both Firefox and Chrome.

Plugin page menu items have both an ID and class generated as such, which seems rather redundant. I propose either dropping the redundant and only partly functional CSS class or standardising the menu slug to produce a valid class name."	kawauso
Future Releases	22003	Saving custom fields goes to post-new.php rather than post.php		Administration	2.5	normal	normal	Awaiting Review	defect (bug)	reopened		2012-09-26T15:57:01Z	2012-09-26T19:19:54Z	"Create a new post or page.
Add a title and message.
Add a custom field (click ""Add Custom Field"")

The post is saved, but as you are taken to post-new.php rather than post.php, it looks as if your post has disappeared! All is well - it is actually saved - but it's confusing.

Tested on 3.5-alpha-21989"	curiousdannii
Future Releases	18307	Settings mixed with WP installations sharing same database		Administration	3.2.1	normal	major	Awaiting Review	defect (bug)	new		2011-07-31T21:22:09Z	2012-02-20T20:27:18Z	"I have WP website installed on main domain, and another WP installation on subdomain. These two share users tables.

When I rearrange admin dashboard widgets, or post editor widgets in one installation, other one uses same settings making the mess due to differences in available elements (different plugins installed).

All WP settings cookies are saved without proper setting of the cookie path/domain, and all sub-domains use same cookies as the main domain does. Cookies have to have full domain set to avoid mix-up like it happens now.

Same issue happens with Opera, Chrome and Firefox.

Milan "	GDragoN
Future Releases	15993	Sort arrows improperly wrap on narrow columns		Administration	3.1	normal	normal	Future Release	defect (bug)	reopened		2010-12-27T06:14:21Z	2012-11-01T06:22:32Z	Specifically, I noticed the 'Posts' column on a taxonomy screen (or 'Links' for link categories, etc).	nacin
Future Releases	24415	The 'show_in_admin_all_list' argument for the 'register_post_status' function is ignored when the argument 'public' is set to 'false'		Administration	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-05-25T00:06:51Z	2013-05-25T00:06:51Z	"Hello, 

I stumbled upon a bug in the admin section of WordPress. I'm currently running the latest release (3.5.1) without any third-party plugins. 

After creating some custom post statuses via the 'register_post_status' function, I noticed that posts with them do not appear in the default (all) post listing in the admin section, despite me setting the 'show_in_admin_all_list' argument to 'true'. 

I narrowed this problem down only to the 'public' argument of the same ('register_post_status') function: if the 'public' argument of custom post status is set to 'true', then everything works as expected and the posts with a custom post status appear in the default (all) post listing in the admin section — but this also makes posts with that custom post status appear to the regular users, making them public, hence the name of the argument.

It's worth noting that the 'public' argument has no such buggy effect on the 'show_in_admin_status_list' argument of the same ('register_post_status') function: it doesn't matter to what the 'public' argument is set — the links to the appropriate post statuses are showed at the top of the post listing only based on the 'show_in_admin_status_list' argument, just like it should."	XyntaMan
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	17635	Themes page should have search subtitle		Administration	3.2	normal	normal	Awaiting Review	defect (bug)	new		2011-06-01T12:15:05Z	2011-06-01T14:26:16Z	"Most admin pages display the term that the user has searched for when displaying search results, but the Themes page (under site admin) doesn't.

[16525] seems to have excluded it in the AJAXified list tables, but gives no reasoning."	kawauso
Future Releases	23316	Top level admin sidebar menu items with conflicting positions bury one another		Administration	3.5.1	normal	major	Awaiting Review	defect (bug)	new		2013-01-29T21:07:27Z	2013-01-30T04:23:58Z	"I have now seen two separate instances where a top level admin sidebar menu item wasn't showing up when another Plugin or Theme was activated. In the most recent case, using WP 3.5.1. my Plugin was creating a top level menu item with no position specified (blank, default). When I activated my client's Theme, our Plugin sidebar item disappeared and in place came the Theme Options item. I set our Plugin to use position 70, and it came back in place of the Users top level menu item.

In the earlier case, I had a custom post type that was requesting position 20. Whenever I activated Gravity Forms, my custom post type menu item was disappearing. This was with WordPress v3.5

According to the codex page: ""''WARNING: if two menu items use the same position attribute, one of the items may be overwritten so that only one item displays! Risk of conflict can be reduced by using decimal instead of integer values, e.g. 63.3 instead of 63 (Note: Use quotes in code, IE '63.3').''""

This seems like a bug to me. Why should items be allowed to completely overwrite one another? Shouldn't they just fall in line, albeit randomly when two conflict? I can see tons of problems with Themes and Plugins killing one another's top level menu items, and the user not understanding what's going on when they loose something unexpectedly."	beautomated
Future Releases	22195	URL for views are defined statically.		Administration		normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-10-15T11:31:11Z	2013-05-08T10:44:27Z	"URLs for views/screens on wp-admin/edit.php are defined statically.
[[BR]][[BR]]
why we are not using add_query_arg(); or remove_query_arg(); while adding URL? This is causing serious issues like resetting extra parameters passed to view/screens.
[[BR]][[BR]]
need expert opinion on this i can write patch if required.
[[BR]][[BR]]

{{{
WP_Posts_List_Table->get_views();
}}}



"	valllabh
Future Releases	24297	WordPress 3.6 UI - Post Visibility Buttons Jumps User to Bottom of Page and Does Not Open Option		Administration	trunk	normal	major	Awaiting Review	defect (bug)	new	close	2013-05-09T17:40:52Z	2013-05-10T21:22:30Z	"Using the WordPress.com 3.6 UI test version, in Firefox older than version 19 (tested on 17-19 across multiple Windows computers in my college class) clicking Post Edit > Publish > Visibility jumps the user to the bottom of the web page and the Visibility option does not open to reveal the Public, Private, and Password Protection options. 

Works in Chrome, so the students all switch to Chrome for that exercise. 

This has been in play for almost three weeks. 

These tickets might be associated with the issue: #23817, #23684.

Thanks!


"	Lorelle
Future Releases	23836	add_submenu_page() duplicate menus		Administration		normal	major	Awaiting Review	defect (bug)	new		2013-03-21T16:43:24Z	2013-04-04T03:22:08Z	"Creating two sub-menus with the same ""menu slug"" using add_submenu_page() should create only the last sub-menu.
But it creates two sub-menus with the same ""menu slug"".

Based on documentation ""menu slug"" should be unique for each sub-menu."	king_of_the_ring
Future Releases	19068	admin comment search never resets URL, grows infinitely		Administration	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-10-27T15:23:48Z	2011-10-28T11:53:53Z	"When searching from {{{ /wp-admin/edit-comments.php }}}
the URL will grow infinitely and never reset to it's base.

To reproduce this bug, simply search comments several times and then examine the resulting URL )by copying it to an editor). It will be over 1000 characters easily, because it's simply appending the previous searches and previous nonces for no useful reason.

Instead the form should just use {{{ /wp-admin/edit-comments.php }}} as it's submit base.

But that form should not be using GET in the first place.

Allowing overly long URLs is also a security problem as it can give a window for XSS attacks.

I wouldn't be surprised if this design flaw exists in other parts of WP admin but I'll leave that up to someone else who has more patience.

"	_ck_
Future Releases	22236	edit.php: Apply when Bulk Actions selected forgets tag= filter		Administration	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-10-20T22:54:28Z	2013-05-04T04:29:47Z	"Using WordPress 3.4.2, go to Posts, and click on one of the tags on one of your posts. The URL now contains tag=<tag>, and the screen shows the first 20 posts with that tag.

Now click the Apply button just next to the ""Bulk Actions"" drop-down at the top left.

I expect this to reload the page but otherwise have no effect.

Instead, it reloads the page without the tag=<tag> URL parameter, and shows the first 20 posts (irrespective of tag).

This is surprising and confusing - it's easy to accidentally hit ""Apply"" without having chosen an action, but at first glance it looks like nothing has happened. The user can then go on to do a bulk action (e.g., add category) without realising the tag they previously had selected is now no longer selected.

Note that filters (e.g., by category) that are set up using the Filter button *are* preserved when Bulk Actions / Apply is chosen - it's just tags that are lost."	kw217
Future Releases	22669	iPad: Can't Scroll Plugins Modal		Administration	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-12-01T02:31:23Z	2012-12-02T01:43:48Z	"Steps to reproduce:
1. Tap Plugins
1. Tap Add New
1. Tap Featured
1. On any item, tap Details.
1. Tap Changelog
1. Swipe to scroll

Expected result:

See more Changelog.

Actual result:

The page is scrolling around behind the modal.  Modal not scrolling.

Related: #22064"	miqrogroove
Future Releases	11311	kses converts ampersands to &amp; in post titles, post content, and more		Administration	2.9	normal	normal	Future Release	defect (bug)	new		2009-12-03T01:49:32Z	2013-05-17T10:03:16Z	"Make a test user that has the ""author"" role (i.e. no `unfiltered_html`) and write a post with a title that has `&` in it. After saving, it will becomes `&amp;` due to `wp_filter_kses()`. It gets saved in the database this way too.

It's confusing to the user."	Viper007Bond
Future Releases	16258	nav menus dont save the right type of menu items		Administration	3.0.4	normal	minor	Awaiting Review	defect (bug)	new	reporter-feedback	2011-01-16T12:57:50Z	2011-01-20T20:47:27Z	"the new Navigation menus when the flag is set ""Automatically add new top-level pages"" when adding a new page to the menu and saves the new menuitem will change from ""page"" to ""userdefined"" as type.

It is always only the last item in the menu there is changeing. "	J0rDZ
Future Releases	23477	r21789 creates a breaking change in behavior for get_submit_button		Administration	3.5	normal	minor	Awaiting Review	defect (bug)	new		2013-02-14T23:23:57Z	2013-02-15T17:32:18Z	"A recent change made to get_submit_button (http://core.trac.wordpress.org/changeset/21789/trunk/wp-admin/includes/template.php) has caused an unwanted change in behavior for a button on a site I maintain. Previously, the string passed as the second argument, `$type`, was matched against a switch statement with several unique cases. In the event of a non-match in the switch, the default action prior to [21789] was to assign the parameter's value as the `$class` string without altering it.

The change introduced in [21789] now breaks a string into individual classes, which prevents the use of the unique class names within a string of additional class names. For example, the string `button-secondary save-button action` used to generate a class string in HTML of `button-secondary save-button action`, but now generates the unexpected result `button save-button action` (note lack of '-secondary') because it matches against the following if check on line 1600:

`if ( 'secondary' === $t || 'button-secondary' === $t )`

It should be noted that the phpdoc associated with the function does not name the use case that I was employing, but that the behavior of passing in a space-separated class string has previously resulted in the string being passed through untouched (and the comment here indicates it was known and expected behavior (http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/template.php?rev=21781#L1649), and this is no longer the case. Not sure if this is worth a programmatic fix, or if it might just be worth noting in the function docblock that certain classes are now 'reserved' and cannot be passed into the `$type` string."	vhauri
Future Releases	17249	thickbox modal window dimensions are fixed in wp-admin		Administration	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-04-27T05:01:38Z	2012-01-19T00:03:35Z	"Hello,

When invoking a thickbox modal in wordpress wp-admin, the dimensions of the modal window can't be customized. Because of media-upload.js is replacing the tb_position() function.

This is not needed that way, and media upload modal window size can be set when calling it.

The workaround is rather complicated, please read: http://binarybonsai.com/2010/02/27/using-thickbox-in-the-wordpress-admin/ down to ""The Media Manager Horror"""	DreadLox
Future Releases	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	2013-06-09T00:49:27Z	"
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
Future Releases	24541	wp_is_mobile() includes tablets		Administration	3.4	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2013-06-08T12:41:08Z	2013-06-08T15:02:43Z	"Android tablets have ""Android"" in user agent and Android mobile phones have ""Android"" and ""Mobile"". I use this to distinguish what is tablet and what is a mobile phone.

http://core.trac.wordpress.org/browser/tags/3.5.1/wp-includes/vars.php"	Looimaster
Future Releases	24334	"""edit_form_after_title"" and ""edit_form_after_editor"" hooks wrapper optional?"		Administration	trunk	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2013-05-14T10:51:21Z	2013-05-14T18:38:39Z	"Would it be possible to make the `DIV.edit-form-section` wrapper applied around `edit_form_after_title` and `edit_form_after_editor` hooks in post/page edit screen optional in WP3.6? Or create additional non-wrapped hooks besides?

[http://core.trac.wordpress.org/browser/trunk/wp-admin/edit-form-advanced.php#L462]
[http://core.trac.wordpress.org/browser/trunk/wp-admin/edit-form-advanced.php#L502]

These wrappers were actually introduced in WP3.6, the WP3.5 version was without them. 

'''Explanation of what I do:'''
* `edit_form_after_title` hook - I output UL list of tabbed interface here and open the first tab content DIV
* `edit_form_after_editor` hook - I close the first tab content DIV and output the other tab content DIVs

The first content DIV is always a visual editor. But as you can see, when I open the DIV in one hook and closing it in another one, this was working fine in WP3.5 as no wrapper was added to those hooks. Once there is a wrapper, it obviously messes up the HTML and closes divs prematurely. This is causing issues obviously for tabbed interface.

Screenshot: [http://awesomescreenshot.com/09915rzc37]
Ticket started on Alpha/Beta support forum: [http://wordpress.org/support/topic/wrapper-of-edit_form_after_title-and-edit_form_after_editor-hooks-optional]

Thank you!"	lemmonaid
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	18413	"Ability to Add Custom ""Add User"" Link"		Administration		normal	normal	Awaiting Review	enhancement	new		2011-08-15T14:44:54Z	2011-08-15T14:44:54Z	"For the ldap plugin i'd like to be able to utilize the current location of the ""Add New"" and ""Add Existing"" button to override it to show a button to link to the custom page for the ldap add user page.

Currently there are no hooks or filters that would allow me to add something in there - would it be possible to add in an action in there after the existing code to print out the add buttons?"	axelseaa
Future Releases	21911	Add 'All Themes', 'Parent Themes' and 'Child Themes' tabs		Administration	3.4.2	normal	minor	Awaiting Review	enhancement	new	close	2012-09-17T18:37:44Z	2013-03-08T15:31:36Z	"When you have multiple themes installed which are a mixture of parent and child themes, it can be a bit overwhelming sometimes to have ALL themes lumped together in one view.

It would be nice on the themes.php page to replace the 'Available Themes' text with some tabs such as:

All Themes | Parent Themes | Child Themes

The 'All Themes' tab would show all available themes (default view), 'Parent Themes' tab would only show parent themes, and 'Child Themes' for child themes, but only if any are installed (to prevent an empty tab from being shown).

Hopefully this wouldn't be too hard to implement, but would be pretty handy for the end user for multiple available themes.

An extension to this could have a further tab called something like 'Favorites' where you can flag certain themes you like. This could be a great way of displaying just a select custom subset of themes that you have complete control over (only if at least one theme had been flagged as a favorite).


All Themes | Parent Themes | Child Themes | Favorites
"	dgwyer
Future Releases	22333	Add IDs to .misc-pub-section divs in meta-boxes.php		Administration	3.4	normal	normal	Awaiting Review	enhancement	new		2012-10-31T16:25:40Z	2012-11-13T01:39:40Z	"In `wp-admin/includes/meta-boxes.php` the `post_submit_meta_box` has several sections with class .misc-pub-section. Should you have to style/alter any of them, it's not consistent as:

1. first div has only `class=""misc-pub-section""`
2. second div has `class=""misc-pub-section"" id=""visibility""`
3. third div has `class=""misc-pub-section curtime""`

Since this is a unique box on the screen, I've added two more IDs to div blocks 1 and 3 to allow for easier styling changes. "	nofearinc
Future Releases	21190	Add a action in check_admin_referer() in the event the nonce auth fails		Administration		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-07-08T09:12:56Z	2012-07-08T09:12:56Z	"Currently plugins don't have a way to perform custom handling in the event that a nonce fails in `check_admin_referer()` - Whilst in most cases this will never be needed, I'd like the ability for plugins to be able to use `check_admin_referer()` directly AND have the option of redirecting failed nonces to their own page.

We currently have an action which is fired when a nonce passes:
{{{
do_action('check_admin_referer', $action, $result);
}}}"	dd32
Future Releases	15406	Add a pending post count indicator to the admin menu		Administration	3.0.1	normal	trivial	Awaiting Review	enhancement	new	dev-feedback	2010-11-12T17:28:49Z	2013-01-22T15:21:49Z	"Comments has an indicator bubble on the dashboard with the pending comments count.

Pending posts should have such a feature, since they are quite more important."	iign
Future Releases	23986	Add filter for <html> css class in admin		Administration	trunk	normal	minor	Awaiting Review	enhancement	new		2013-04-08T08:23:10Z	2013-04-08T08:23:10Z	It would be handy (looking at MP6), if it would be possible to alter the CSS class of `<html>` in the backend.	tillkruess
Future Releases	14126	Add hook for message on admin-header in h1-privacy		Administration		normal	normal	Future Release	enhancement	new		2010-06-28T08:35:10Z	2010-10-28T08:46:46Z	"Add a hook for add a message inside from h1 in admin-header.php, same as privacy message in WP 3.0, see example images: [http://drp.ly/1glQ2G]
I think, its great for the UI and create messages about all sites in backend. I change also the ID in class, no redunace on use this style.
Please see the files and sorry for my bad english."	bueltge
Future Releases	21667	Add some user agent to wp_is_mobile		Administration	3.4.1	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-08-23T12:35:29Z	2013-05-07T18:45:53Z	"Hello,

I've run some test with the help of the twitter/G+ community on wp_is_mobile and found some mobile browser that don't pass the test. 

You can see the test here : http://www.inpixelitrust.fr/blog/wp_is_mobile/

I was able to get the user agent of 3 of those which don't work : 

HTC sensation z710 4.0.3 native browser (UA:  Mozilla/5.0 (X11;Linux x86_64; HTC/Sensation/3.32.162.11; fr-de) 
AplliWebkit/534.24(KHTML,like Gecko) Chrome/11.0.696.32 Safari/534.34 )

BlackBerry Playbook (Ua Mozilla/5.0 (PlayBook; U; RIM Tablet OS 2.0.1; en-US) AplleWebkit/535.8+ (KHTML, like Gecko) Version/7.2.0.1 Safari/535.8+ )

Could be great to add those to the UA sniffing :)

"	inpixelitrust
Future Releases	15796	Add spacing in the menu between 59 and 60 to allow menu items to appear above appearance		Administration	3.1	normal	normal	Future Release	enhancement	new		2010-12-13T14:12:51Z	2011-01-06T12:44:41Z	"I would like to place a menu item above appearance however the spacer is directly above the Appearance menu item at 60, the spacer is at 59, just a simple request to appropriate more space that is empty, 55 for the spacer and keep the appearance 60 giving 56,57,58,59 for add_menu items above 60

"	Frumph
Future Releases	24531	Add subpage_file Filter Before Admin Menu		Administration		normal	minor	Awaiting Review	enhancement	new		2013-06-07T10:53:36Z	2013-06-07T10:53:36Z	"For users extending the back end of wordpress, sometimes custom pages added to the main menu will not be flagged as the current page because of unexpected aspects such as additional GET data.

The problem is, setting this directly using a filter like {{{admin_menu}}} does not work due to {{{$subpage_file}}} being set later on (needs confirming), nor does it make sense due to context.

At the top of {{{menu-header.php}}}, there is a filter called {{{parent_file}}}, used to allow plugins/themes to move the submenu tabs around, a suggestion would be to add a {{{subpage_file}}} filter, allowing plugins and the theme to modify the compared url to check the current page.

Would add a patch, but away from my development environment."	Nessworthy
Future Releases	11515	Admin needs standardized way of handling messages (notices) displayed to the user		Administration	3.0	normal	normal	Future Release	enhancement	new		2009-12-19T19:53:03Z	2013-03-15T23:45:50Z	"If you try to upload a media item under Media > Add new without an uploads directory, you get the following vague error message:

{{{
Error saving media attachment.
}}}

If you try instead to upload from the post edit page, you get a much more helpful message:

{{{
Unable to create directory /path/wp-content/uploads. Is its parent directory writable by the server?
}}}

In each case, the root error is the same, but the second error message points the way to a solution.  Even if the user doesn't know herself what that message means, it's a message that provides the necessary information to someone else who does and is trying to help the user. The first message is completely useless, as it states only what we already know: something went wrong.

The reason Media > Add new doesn't offer a helpful message is that the error is generated on one page request, and ''then'' the user is redirected to another page.

We need a standard, cross-page-load way of conveying messages in admin.

I've thought of a few possible ways of doing this:

 * Define and use a standardized set of error codes and associated error messages.  This is similar to what happens currently on many pages: the unhelpful ""Error saving media attachment."" appears when the message argument is set to ""3.""  What I'm suggesting would use a common set of message codes across the admin and be much more detailed.  So the above situation would instead produce a message like ""Unable to create the uploads directory.""
 * Save error messages to a cookie.  Unlike the previous method, this would allow messages to be made particular to their event.
 * Have some kind of user messaging stack.  New messages would be pushed into a user's stack (stored in usermeta) and popped off after a certain time, or when read, etc.  This has the advantage of lasting across sessions and browsers and being usable for other applications, such as PMs between users. 

What do you think?"	filosofo
Future Releases	10726	Admin notifications for more than 1 email		Administration	2.8.4	normal	normal	Future Release	enhancement	reopened		2009-09-05T02:18:51Z	2013-06-11T19:24:17Z	"Please allow admin notifications to go to more than 1 email address. It could be as simple as allowing a comma-separated list.

Better yet, allow sending '''admin''' notifications to all people in the '''administrators''' role."	novasource
Future Releases	18769	Admin should not break if URL changes		Administration		normal	normal	Awaiting Review	enhancement	new		2011-09-24T22:58:42Z	2013-06-03T17:50:55Z	"We manage a lot of users who have WordPress blogs, and probably the number one user support request we have to field comes out of this situation:

1. User decides they want to move their WordPress,
2. They move the folder to a new URL,
3. Their admin page stops working, because it still had the old URL hard-coded.

This is silly and should be fixed."	AmbushCommander
Future Releases	19278	Allow WP_List_Table ::get_bulk_items() to receive a nested array and output optgroups		Administration		normal	minor	Awaiting Review	enhancement	new		2011-11-17T17:25:37Z	2011-11-17T21:38:59Z	"I'm just putting this out there as a possible enhancement to the WP_List_Table... would like feedback as to whether anyone else would find it helpful. If so, I'm more than happy to write up a patch for this.

I think it may be useful to be able to pass a nested array to `WP_List_Table::get_bulk_actions()` and have it output the options within the subarray in an `<optgroup>`. My specific use case is in applying meta fields to a custom table. I would like to be able to define something like this in my `get_bulk_items` function:

{{{

function get_bulk_actions() {
	$actions = array(
		'delete' => 'Delete',
		'outofstock' => 'Mark out of stock',
		'applytags' => array(
			'label' => 'Apply tags to products',
			'actions' => array(
				'featured' => 'Featured',
				'sale' => 'On Sale'
				)
			)
		);
	return $actions;
}

}}}

and have the output look something like this:


{{{
<select name=""action"">
	<option value='-1' selected='selected'>Bulk Actions</option>

	<option value='delete'>Delete</option>
	<option value='outofstock'>Mark out of stock</option>
	<optgroup label=""Apply tags to products"">
		<option value='feature'>Featured</option>
		<option value='sale'>On sale</option>
	</optgroup>
</select>

}}}

A very minor feature, and possibly too fringe of a use case to bother with. But I've worked on a couple projects now where being able to specify markup like that would have made that screen more user-friendly. Any thoughts?"	goldenapples
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	4221	Allow pure wp_nonce_url urls		Administration	2.3	normal	normal	Future Release	enhancement	reopened	close	2007-05-04T04:29:33Z	2012-08-15T03:44:11Z	"wp_nonce_url sends the url through wp_specialchars, which converts {{{&}}} into {{{&#038;}}}

That's great for standards-compliant links, but if you're trying, for example, to use a nonce in a url passed to JavaScript, it can cause problems, as at least Firefox chokes when JavaScript requests a url with {{{&#038;}}} instead of {{{&}}}. 

My patch allows you to toggle off the wp_specialchars; the default behavior remains the same."	filosofo
Future Releases	23162	Allow to call parent_dropdown() for an arbitrary post		Administration		normal	normal	Awaiting Review	enhancement	new		2013-01-09T22:48:08Z	2013-01-09T23:24:26Z	"parent_dropdown() can no longer be used outside of the loop, such as within the wp-admin, because an E_NOTICE will be emitted in template.php:683 since $post is null. 

A simple fix is to change the function argument declarations from 

{{{
function parent_dropdown( $default = 0, $parent = 0, $level = 0 ) {
}}}
to:
{{{
function parent_dropdown( $default = 0, $parent = 0, $level = 0, $post = array() ) {
}}}

and then also change:
{{{
$post = get_post();
}}}
to
{{{
	if ( empty( $post )) {
		$post = get_post();
	}	
}}}

which would allow a WP post object to be passed into the function.

Sorry I am unable to provide an SVN patch.
"	charliespider
Future Releases	24071	Allow users to set three columns on Add Post/Add Page screen		Administration		normal	normal	Awaiting Review	enhancement	new		2013-04-12T23:53:07Z	2013-04-14T06:02:48Z	"These days, an increasing number of people have desktops or laptops with high-resolution monitors. On such monitors, the layout of the WordPress Add Post/Add Page UI is not optimal. 

On, say, a 1920x1080 screen, the first column, containing the TinyMCE editor and title field, occupies the vast middle of the screen, with the WordPress chrome at the left and Column No. 2 at the right. 

If a user has chosen to show additional fields not shown by default - like Excerpt, Send Trackbacks, Custom Fields, Discussion, Slug, and Author - these all appear below the TinyMCE editor, out of sight on a widescreen. Take a lot at the screenshot attached to this ticket. 

Showing two columns by default is perfectly fine, but those with widescreen displays would benefit from gaining the ability to change the number of columns in the screen layout to three without needing a plugin, or having to hack the admin. This doesn't seem like it would be too difficult of an option to add to core. 

Allowing three columns to be set would permit users with hi-res monitors to easily make better use of the screen real estate: all of the available fields would be visible without the need for scrolling. 

Many users, incidentally, utilize fixed-width themes on their sites, and if the theme is sending its CSS to the post editor in order to enable the user to accurately preview what the text will look like (truer WYSIWYG), having a really wide post editor is especially useless. 

I've attached a three-column mockup I made in KolourPaint. The mockup shows what a three-column post editor layout could look like. As you can see from the mockup, all available fields in WordPress Core fit into the viewport. "	avcascade
Future Releases	23738	Audit our secondary button uses		Administration	trunk	normal	normal	Future Release	enhancement	new		2013-03-11T17:31:26Z	2013-05-16T12:12:03Z	"helen pondered in #wordpress-ui that maybe the ""apply"" button in the Screen Options dropdown should be a primary button. There's a good argument to be made that when this panel is down, that ""apply"" button is your new primary.

We should do an audit of our buttons to see if there are any other cases where we could make an action or a temporarily primary action more obvious by using the primary button style."	markjaquith
Future Releases	23577	Better Date Fields		Administration	3.5.1	normal	normal	Awaiting Review	enhancement	new	close	2013-02-21T11:52:59Z	2013-02-22T16:15:20Z	"I think the Dates should be prettified (i.e 2 days ago etc) and the last state put in front i.e (""Published 2 days ago"" rather than ""2 days ago Published"")

As I think it would make it even more user friendly to used.

I have attached a Image showing what I mean."	jscampbell.05
Future Releases	17766	Browser update dismiss button lacks non-JavaScript fallback		Administration	3.2	normal	minor	Future Release	enhancement	new		2011-06-11T11:20:58Z	2011-08-27T15:42:14Z	The 'Dismiss' button in the browser update dashboard box doesn't do its thing without JavaScript enabled.	johnbillion
Future Releases	24530	Change 'Right Now' dashboard actions to filters.		Administration	3.5.1	normal	trivial	Awaiting Review	enhancement	new		2013-06-07T08:55:19Z	2013-06-07T15:24:06Z	"The default dashboard's 'Right Now' meta box (not the network one) has three actions which allow you to extend by adding to the bottom of the table at three points: After the 'Content' column, after the 'Discussion' column, and at the end of the table. 

Similar to filter functionality for things like adding custom columns, the box could, instead, work with filters. By passing an array of rows, this would allow developers to be able to reorder the table rows, and extend the table at whatever position they want to.

({{{dashboard.php:225, wp_dashboard_right_now()}}})"	Nessworthy
Future Releases	23230	"Change hyphen in front of ""Draft"" to em dash"		Administration	3.5	normal	normal	Awaiting Review	enhancement	new		2013-01-18T09:08:47Z	2013-01-25T20:08:00Z	"When a post/page/etc. is saved as a draft there is a ""- Draft"" appended after the title in the overview list in the dashboard.

Rather than using an hyphen (-) it should be an em dash (—) and ideally it should be translatable as the typographic rules for dashes varies with languages.

Rather than ""- Draft"" it should say ""— Draft"""	kkalvaa
Future Releases	12350	Check folder permissions before uploading file		Administration		normal	normal	Awaiting Review	enhancement	reopened		2010-02-23T18:41:57Z	2011-10-09T14:54:04Z	"It would be nice if wordpress - or especially the media-upload module would check if its able or has the necessary file permissions to create the upload directory.
"	not2bug
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	15790	Date column for Scheduled posts should also state the time		Administration	3.0.4	normal	normal	Future Release	enhancement	new		2010-12-13T04:37:07Z	2013-01-22T17:33:17Z	"For obvious reasons, for scheduled posts, it's very useful to see not just the date but the time, but the wp-admin posts interface does not show it - only the date.

It'd be very useful to see the time as well.

Thanks."	archon810
Future Releases	18199	Deprecate IE7 in the Admin		Administration		normal	normal	Future Release	enhancement	new		2011-07-21T21:05:15Z	2013-04-26T01:27:26Z	"markjaquith:
> Everyone hates IE7. It’s insecure. Let’s make it go away. Also, dropping IE6 didn’t give us much beyond goodwill, because most of the hacks we needed for IE6, we also need for IE7. So we could actually clean up our CSS a bit if we dropped IE7."	nacin
Future Releases	12890	Draft and scheduled pages not listed in the Parent dropdown		Administration	3.0	normal	normal	Future Release	enhancement	assigned		2010-04-07T11:59:55Z	2012-07-03T14:15:23Z	"Draft and scheduled pages are not available as choices in the Parent dropdown of the Attributes module.

This is very similar to ticket #8592, regarding private pages. I'm hoping the fix might be simpler for drafts and future posts."	rooodini
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	21034	Flyout Menu on Backend doesn't Loades Untill Whole Page is Loaded		Administration	3.4	normal	normal	Awaiting Review	enhancement	new		2012-06-21T09:43:55Z	2012-06-25T05:30:06Z	"I have noticed this ever since the flyout menu was introduced. Menu items on flyout menus is not shows until the whole page gets loaded. For high speed connection its not a problem but it gets annoying people who connected in dial up (last week my ISP was down so i had to work with dial up for couple of days).

So, we could make the flyout menu items css/js to load on header so it doesn't wait for to load the whole page and make the backend accessible to and less annoying to low speed users.. For testing it you have to log into backend with low speed connection. If you need proof i can make a video with my dial up. Just let me know.

BTW: What i see on firebug that the css for flyout menu loads on header so i don't really find out what causes the menu to not showing on hover until the page loads."	prionkor
Future Releases	14097	Idea for placeholder text		Administration		lowest	trivial	Future Release	enhancement	new		2010-06-26T06:28:25Z	2013-01-22T17:40:03Z	"Placeholder text has a fatal flaw, in my mind: once the field is focused, that placeholder text is gone. This can be confusing, especially if you tabbed into that field or it was selected by default. You can actually use placeholder text instead of labels, for a minimalistic form layout, but only if you correct this flaw.

So here's a potential solution:

http://txfx.net/files/wordpress/labels/

It uses HTML 5's {{{placeholder}}} attribute (newest Safari and Chrome support it), with a jQuery plugin to handle that support for other browsers.

Thoughts?"	markjaquith
Future Releases	17783	Inconsistent theme management screens		Administration	3.0	normal	normal	Future Release	enhancement	new		2011-06-13T12:32:26Z	2011-06-13T13:12:51Z	"On single-site you have tabs, while on multi-site you have an ""Add New"" button:

/wp-admin/themes.php (single-site):

[[Image(http://core.trac.wordpress.org/raw-attachment/ticket/17783/themes.png)]]

/wp-admin/themes.php (multi-site):

[[Image(http://core.trac.wordpress.org/raw-attachment/ticket/17783/ms-themes.png)]]

/wp-admin/network/themes.php (multi-site):

[[Image(http://core.trac.wordpress.org/raw-attachment/ticket/17783/ms-themes-network.png)]]"	scribu
Future Releases	21132	"List tables' ""select all"" should let you really select all, regardless of screen options"		Administration		normal	normal	Awaiting Review	enhancement	new		2012-07-02T04:38:38Z	2012-07-05T15:13:48Z	"The select all checkbox in list tables selects all the items in your current view.  Usually what I really want is to select all the items on all the pages.

As a hack, I'll often leave the screen options setting for items per page on something really high, like 1,000.  Unfortunately this means the tables are often really slow for no benefit (most of the time I don't need them all).  A better solution would be a way to intelligently select all items without needing to show them on the page.

The best example of this that I know of is Gmail, which adds a line above the list of emails when you click the select all box that looks something like this: ""All 50 conversations on this page are selected. Select all 653 conversations in Spam"".  The second sentence is a link that, as expected, selects all of your emails that fit the current view, regardless of paging.  Screenshot attached."	evansolomon
Future Releases	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
Future Releases	22589	Network Admin + Ajax requests		Administration		normal	normal	Awaiting Review	enhancement	new		2012-11-26T09:12:18Z	2012-11-26T14:40:53Z	"Currently there is no Network admin based ajax handler, forcing plugins which exist solely within the Network Admin to either use `wp-admin/admin-ajax.php` or using the `load-{$page_hook}` hook to perform any actions.

This is primarily a problem when the plugin only includes code on a conditional such as `is_network_admin()`, which would be false for a `/wp-admin/admin-ajax.php` request, as a result, only the `load-{$page_hook}` option above is viable for those.[[BR]]
As a work around, plugins can include code on `is_network_admin() || DOING_AJAX` to allow the usage of admin-ajax.php.

Of course, the User Admin also suffers the same issue.

I didn't see any previous tickets, and kind of want to say the existing 'workaround' is appropriate, but recording it here so we can at least close it as wontfix if appropriate."	dd32
Future Releases	16031	New bulk actions hook missing catcher behavior		Administration	3.1	normal	normal	Future Release	enhancement	assigned		2010-12-29T20:31:04Z	2013-03-12T16:47:57Z	"The new bulk actions filter allows you to modify the bulk-actions arrays, but neglects to add the ability to handle the new custom actions. 

The fix is to simply add one new do_action() hook to the default case of each affected page (similar to the way 'wp_ajax_' handles custom ajax requests).

For example, the following might be added to users.php at line 285, immediately after <tt>default:</tt>

do_action( 'bulk_action-'. $wp_list_table->current_action() );"	Veraxus
Future Releases	23680	Obsolete function previously used in Theme Editor		Administration		normal	normal	Awaiting Review	enhancement	new		2013-03-04T03:15:56Z	2013-03-04T03:15:56Z	"`get_real_file_to_edit()` is unused since [12063] and should probably be deprecated: [[BR]]
http://core.trac.wordpress.org/browser/tags/3.5.1/wp-admin/includes/file.php#L96"	SergeyBiryukov
Future Releases	19114	Optimise admin css colors		Administration	3.3	normal	normal	Awaiting Review	enhancement	new		2011-11-02T11:16:11Z	2012-12-24T11:26:56Z	"It is really pain to create own admin color pallete, as the current ones are too complex. E.g. in current colors-fresh.css you are using circa 90 colors, many of them almost identical so noone can see the difference (especially when they are on different pages, places) and you are also using different naming conventions

6hexa #666666

3hexa #666

color name black

and also different case in hexa e.g. #FFFBCC vs. #f1f1f1

IMO the default number of different colors could be decreased to about half without visible concerns and also standardising naming convention would help for creating own themes"	thomask
Future Releases	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
Future Releases	13924	Provide 'reasons to update' text with core update notice in GUU		Administration	3.0	normal	normal	Future Release	enhancement	new		2010-06-16T19:39:25Z	2010-10-28T09:38:35Z	Just like plugins can enter some text to ID why they should be upgraded, we should have this for core. 	jane
Future Releases	23444	Publish actions not readily available after scrolling when editing a post		Administration		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2013-02-11T01:37:14Z	2013-02-11T02:26:42Z	When editing a post in 2-column mode, the user is forced to scroll to the top of the screen. As publishing is always the final action while editing a post, the user should have the metabox available regardless of the user's scrolling.	ericlewis
Future Releases	23233	Radio Button instead of Checkboxes on Comment Moderation option?		Administration	3.5	normal	trivial	Awaiting Review	enhancement	new	close	2013-01-18T16:26:23Z	2013-01-19T03:13:00Z	"Hi! I've been a loyal Wordpress user for years. This is nothing urgent, but something that may improve the user experience.

In Settings > Discussion > Before a comment appears, there are two options: ""An administrator must always approve the comment "" and ""Comment author must have a previously approved comment""

Perhaps I have missed something here, but aren't these options pretty much either/or? If the first box is checked, it's rather irrelevant if the second box is checked, because the first checkbox would override it?

If I'm correct, shouldn't this be changed from a both/and checkbox to an either/or radio button?"	danielmount
Future Releases	22198	Realigning the Discussions Settings page		Administration	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-10-15T14:50:34Z	2013-01-22T03:01:36Z	"[I looked for some tikets for this but didn't find any directly related, so hopefully I haven't missed a big one out there floating around.]  

The Discussions Settings page (options-discussion.php) always trips me up when setting up a new site. There's a lot of options, descriptions, directions, etc on that page — much of which is probably unavoidable. When I visit it, I always think that the hierarchy isn't quite right. 

To help with this, I thought of two half-measures. 

1. A very simple solution: 

Put the ""Allow people to post comments on new posts"" at the top of the options list, with a little space below it. That would make that option the most prominent on the page, without making it stand out too much. 

Like this:
[[Image(http://f.cl.ly/items/3e0c062W0N1l3J2D0q0Y/Screen%20shot%202012-10-15%20at%2011.56.02%20AM.png)]]


2. A more involved solution: 

I really like the new click-to-reveal-the-options at work in the ""Page on Front"" (#16379) workflow and thought it might work well here. 

*Something* in this direction:  
[[Image(http://f.cl.ly/items/022A1G3k0O3q0g1u380L/Screen%20shot%202012-10-15%20at%2012.12.09%20PM.png)]]


The first could be accomplished for 3.5, but the second re-working could be a further down the line item. 
 
"	saltcod
Future Releases	22228	Remove one-time variable from add_settings_error		Administration		normal	trivial	Awaiting Review	enhancement	new		2012-10-19T17:50:08Z	2012-10-19T17:50:08Z	"Append an array to `$wp_settings_errors` without assigning it to a variable in the previous line.

Before:
$var = array( 'type' => $type ... );
$wp_settings_errors[] = $var;

After:
$wp_settings_errors[] = array( 'type' => $type ... );"	niallkennedy
Future Releases	14858	Shortlink On Posts Edit Summary Screen		Administration	3.0.1	normal	normal	Future Release	enhancement	reopened		2010-09-12T23:08:43Z	2013-01-22T17:32:34Z	"We've got a very handy button on {{{/wp-admin/post.php}}} to get the posts shortlink, but that involves going into the post as if you want to edit something!

So on {{{/wp-admin/edit.php}}} would it not be appropriate to add some kind of link/button where we can get without needing to go in and edit the post? - Meaning it doesn't need to load any content, possibly add yet another auto-revision, and such...!"	markmcwilliams
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	20901	Taxonomy descriptions should be TinyMCE editable		Administration		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-06-11T07:49:17Z	2013-05-16T10:16:18Z	"Right now taxonomy descriptions are filtered heavily for HTML and are output as a simple textarea, making it impossible to make those into ""nice"" tinymce editors without a kind of hackish plugin. 

I'd be in favor of making taxonomy descriptions tinymce by default."	joostdevalk
Future Releases	7485	Terrible UX design on XFN section of Write->Link pages		Administration	2.6	normal	normal	Future Release	enhancement	assigned	dev-feedback	2008-08-08T17:02:49Z	2012-01-06T01:43:58Z	"Regarding the XFN section on the Write-Link pages:

The UX on this section is fairly terrible. We give the user an editable ""rel"" field and then don't let them edit it via javascript. Note that if you disable javascript and then edit that field, then your changes are indeed saved and then even show up on the resulting pages correctly. That javascript just won't let you manually edit the field. 

I propose that the javascript on this section be changed to allow manual editing of that field, and to make the checkbox/radio sections just add/remove the relevant bits from the field when they are selected/deselected. Result should allow user to manually insert stuff into the rel field and leave those manual insertions unaltered when changing the radio/checkboxes, unless they conflict with the selections being made directly.

Also, side note, would be nice to add a nofollow checkbox to this section as well, to allow easy addition of nofollow to the rel field, which would be handy for the somewhat over-controlling SEO oriented people. ;)
"	Otto42
Future Releases	20570	Tidying Admin CSS, bringing it up to CSS Code Standards (work in progress)		Administration	3.4	normal	minor	Awaiting Review	enhancement	new		2012-04-29T16:24:09Z	2012-12-24T11:27:12Z	"as per http://codex.wordpress.org/CSS_Coding_Standards, this is an attempt to bring the internal admin stylesheets up to CSS Coding Standards

Some of the changes being made are ...

* Properly intenting top: left: right: bottom: attributes two tabs when following a position:absolute position:fixed or position:relative declaration
* Alphabetizing css properties
* Removing unnecessary browser prefixes
* Placing browser prefixed css properties before the non-browser prefixed versions
* Removing extraneous spaces
* Applying a consistent ordering of browser-prefixed properties (based on length of prefix to get an aesthetically pleasing diagonal line, rather than jagged, inconsistent line endings -- yes, I know it's silly, but it's better than randomness, and alphabetical isn't as useful)
* Applying a uniform method to attribute selectors and url references by wrapping double-quotes around the values (there was no prior standard and a motley assortment of usages)
* Changing colors to 3-character shorthand ( 888888 becomes 888 )
* Changing colors to lower case ( EEE becomes eee )

and probably a couple others that aren't coming to mind right now."	georgestephanis
Future Releases	24472	TinyMCE editor on attachment edit screen		Administration	3.5.1	normal	normal	Awaiting Review	enhancement	new		2013-05-31T01:49:21Z	2013-05-31T01:49:21Z	"Hi,

I have run into an issue where I need the WordPress wysiwyg editor (rather than the stripped down version currently there) on the edit media page.

I have looked at the code that generates the page and there seems to be no filter or action available to override the tinymce value when the call the wp_editor is made.

Would it be possible to add a filter here, so that the false value is overridable if needed?

Thanks,

Adrian."	navitronic
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	22633	Update Icon Inconsistency		Administration		normal	normal	Awaiting Review	enhancement	new		2012-11-29T11:37:57Z	2012-11-29T14:44:27Z	"The update icon at the moment is 2 arrows in a circle in the admin bar ( aka the refresh icon ). In Network Admin it's a pair of tools.

I'd suggest we change these to the same icon rather than have 2 inconsistent icons. I'd also suggest we use a single arrow as the new icon, a refresh/recycle icon isn't as clearcut as it could be ( and what if a caching plugin implements a refresh button to the admin bar? ).

We could follow Google by using an arrow pointing upwards, or we could follow Apples convention with a downwards pointing arrow in a circle"	TJNowell
Future Releases	23731	Use jQuery Menu Aim to improve responsiveness of our admin menus		Administration		normal	normal	Awaiting Review	enhancement	new		2013-03-09T16:00:11Z	2013-03-15T21:01:34Z	"This is a fantastic read: http://bjk5.com/post/44698559168/breaking-down-amazons-mega-dropdown

And it resulted in an MIT-licensed jQuery plugin that we should absolutely consider using to improve our menus: https://github.com/kamens/jQuery-menu-aim"	markjaquith
Future Releases	21622	Validate or sandbox file edits before saving them		Administration	2.7.1	normal	minor	Awaiting Review	enhancement	new		2012-08-17T20:50:45Z	2012-09-24T23:20:03Z	"While using the [http://www.wpzoom.com/themes/academica/ academica] theme, I accidentally missed an ending bracket while editing functions/wpzoom-seo.php in the theme editor. This is used as part of a set of pages creating a theme options page on the dashboard. When the function went bad, it caused my entire installation to be unaccessible.

It was necesssary to ftp to fix the error, because even the dashboard was blanked out by a fatal error. Messing something up in the theme should not cut off access to the dashboard."	eschwartz93
Future Releases	22466	Want to View Pending Comments From Dashboard		Administration		normal	normal	Awaiting Review	enhancement	new		2012-11-15T18:49:39Z	2012-11-19T16:25:06Z	"This is a very awkward aspect of WordPress that I'm just attempting to articulate for the first time:  In the Recent Comments dashboard widget, there is no way to view fully the pending comments.

What it should link to:

* View Comment
* View Post
* Approve Comment
* Edit Comment
* Spam Comment
* Trash Comment

What it does instead:

* Visitor's site or e-mail address
* Edit Related Post
* View Related Post
* Reply to Comment
* Approve Comment
* Edit Comment
* Spam Comment
* Trash Comment

So there are several obvious points of confusion here.

Why would I want to reply to a comment that is pending approval, still hidden, and not even fully displayed to me?

Why can't I see the whole comment?  It only shows me an excerpt here, and in order to actually read the comment I have to click over to Comments on the admin menu and find what I'm looking for manually.

Why does the most prominent link for the comment take me to the post editing screen?  When is this ever useful?

Why is the post link displayed as a tiny little ""#""?"	miqrogroove
Future Releases	21189	We should improve the nonce failure page		Administration		normal	normal	Awaiting Review	enhancement	new		2012-07-08T09:07:17Z	2012-07-08T13:14:00Z	"Currently when a admin nonce expires, in most cases we catch this condition using `check_admin_referer()` which presents expired nonces with a rather ugly uninformative error message:
[[Image(http://f.cl.ly/items/26271g453h2y0K393Y1l/Screen%20Shot%202012-07-06%20at%2012.14.25%20PM.png)]]

I'd like to propose that we make this page a bit nicer to end users - who although are unlikely to hit it (I hope) it'd be nice to let them know what's actually happened.

My initial approach would be to change the page to 
- Include a !WordPress logo, and a link back to the Admin area
- Change the message to something like ""The link you've followed has now expired, In order to complete the action you were performing, please return to the previous page, refresh it, and attempt to follow the link again."".
- In the case where this is happening within the !WordPress admin, it would make sense to have some kind of UI on the page as well - This can currently be done by not using `check_admin_referer()` and using `wp_verify_nonce()` directly and redirecting to an error page.

The current message could often cause confusion, as of course the user wants to do it (They just followed a link!) but as there's no continue button, they're left confused."	dd32
Future Releases	23501	add filter for post count query in WP_Posts_List_Table		Administration	3.5	normal	normal	Awaiting Review	enhancement	new		2013-02-18T14:02:40Z	2013-02-18T19:09:48Z	"I've a custom post type ""products"" with a custom taxonomy ""manufacturers""
I've hooked the parse_query filter when fired from edit.php because I've wanted to show posts based on current user criteria (user can edit only products belong to specific manufacturers).
Everything worked as expected, except for the post count in the table header that shows total amount of posts (not a filtered count).
Digging into the code I've found that inside WP_Posts_List_Table constructor ([http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-posts-list-table.php#L59])the following code is performed:

{{{
$this->user_posts_count = $wpdb->get_var( $wpdb->prepare( ""
				SELECT COUNT( 1 ) FROM $wpdb->posts
				WHERE post_type = %s AND post_status NOT IN ( 'trash', 'auto-draft' )
				AND post_author = %d
			"", $post_type, get_current_user_id() ) );
}}}

I think that the simplest solution is to add a filter for the count query. By this way is possibile to customize the query that reflects the effective post count."	cardy_Web
Future Releases	23856	add style for <hr> tag in the Dashboard		Administration		normal	trivial	Awaiting Review	enhancement	new		2013-03-24T17:07:21Z	2013-03-29T05:21:03Z	"Lines are with black color, 
Lines are important to separate something in a widget for example.
or in a metabox... 

{{{
	border: 0; 
	border-top: 1px solid #DFDFDF;
	border-bottom: 1px solid white;	
}}}
"	alexvorn2
Future Releases	18850	hidden admin page		Administration		normal	normal	Awaiting Review	enhancement	new		2011-10-03T21:43:12Z	2012-07-30T16:22:40Z	"it should be possible to create a hidden admin page.

this is useful for pages, that require parameters which are better inserted in other pages (e. g. using the post_row_actions filter).

if this is already possible, it should be documented somewhere where it might be found.

(btw: i'm not sure, what the difference between feature request and enhancement is. please redeclare as fit)"	ibotty
Future Releases	23785	highlight rows on hover for tables with widefat class		Administration	3.5	normal	minor	Awaiting Review	enhancement	new		2013-03-15T10:57:06Z	2013-04-02T20:58:26Z	"If .widefat tables had this css code system-wide (wp-admin.css)

{{{
.widefat tr:hover td {
      background-color: #DDD;
}
}}}

handling these tables on (extreme) widescreens would be improved.

[[Image(http://picload.org/image/aocipap/widefat.jpg)]]"	cfoellmann
Future Releases	18786	meta_form() should place some restrictions on meta keys		Administration		normal	normal	Future Release	enhancement	new	dev-feedback	2011-09-26T22:37:58Z	2013-04-22T21:12:23Z	"meta_form() echoes out all meta keys into a dropdown for the custom fields box, unless they start with an underscore (as bound by the query).

We should consider is_protected_meta( $key, 'post' ) and/or current_user_can( 'add_post_meta', $post->ID, $key ). This isn't a security thing, just an opportunity to hide some things from the user they don't need to see.

On the other hand, it's definitely a number of extra calculations. is_protected_meta() is light as long as there's no filter on things (and if there is, we probably want to know). current_user_can() might be a bit more weight than necessary here."	nacin
Future Releases	16283	post_exists() enhancement - don't include revisions		Administration	3.1	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-01-18T13:33:51Z	2011-07-17T02:04:03Z	"The current post_exists() function to me has a major downside.  By default all it does it search for title, content and/or date in the wp_posts table.

The problem with this is that it includes revisions.  So for example if you have a post with title ""ABC"" but then later change it to ""DEF"", post_exists(""ABC"") will still return true with the post ID of the revision.

I would suggest either:

 a) Adding post_status not equal ""inherit"" as a default to the function.

 b) Adding a 4th parameter which allows you to pass the post_status value in.

I would be happy to code this if anyone has any feedback on what would be the best approach."	durin
Future Releases	18851	search form in edit.php should keep parameters it does not understand		Administration		normal	normal	Awaiting Review	enhancement	new		2011-10-03T21:48:17Z	2011-11-15T11:29:40Z	"the component is class-wp-list-table.php.

if you carry along some kind of status in the url in the post list (e.g. url=https://example.com/wp-admin/edit.php?post_type=post&my_status=""abcdefg"") the search field should not remove the parameter."	ibotty
Future Releases	14561	wp-admin/edit.php tags of post are hard to compare		Administration		normal	normal	Future Release	enhancement	new		2010-08-08T08:25:02Z	2010-11-18T10:13:25Z	"To get an overview about tags used between articles on the post listing in the admin is hard to achieve by the user because they appear not to be ordered.

A solution could be to sort them alphabetically. That done, it's easier for the user to compare the usage of tag distribution accross the listing."	hakre
Future Releases	15384	wp-login.php refactor		Administration		normal	normal	Future Release	enhancement	new	early	2010-11-11T12:40:35Z	2012-05-31T21:40:02Z	"wp-login.php needs some serious work. When looking to do some improvements in #5919, I realized I literally needed a goto in order to achieve the goals outlined in this comment:

http://core.trac.wordpress.org/ticket/5919#comment:39

I am thinking a WP_Login class with some methods that can handle various different forms, POST handling, and rerouting."	nacin
Future Releases	17517	wpLink should show tags and categories as results too		Administration	3.2	normal	normal	Awaiting Review	enhancement	new		2011-05-19T19:38:36Z	2011-05-21T12:06:36Z	"sometimes you make a series of blogpostings about a topic with one unique tag. 

wpLink (the link assistant in wp 3.1) is very useful for finding ""old"" content, but when you want to link a tag or category you have to type in the url yourself or paste it

Possible solution:

Tabbed interface:
Tab 1 for Posts/pages
Tab 2 Tags/categories"	hebbet
Future Releases	24119	A uniform approach to Plugins / Themes settings		Administration	3.5.1	normal	normal	Awaiting Review	feature request	new		2013-04-18T07:28:14Z	2013-04-26T22:16:55Z	"Yesterday [https://irclogs.wordpress.org/chanlog.php?channel=wordpress&day=2013-04-17&sort=asc#m2987650 in IRC] (#!WordPress), we had a conversation about rules that would help make plugins and themes easier to use, which in turn would make !WordPress easier to use.  

There isn't a rule or guideline whether a plugin should make a tab or link under settings or if it even has to do any of the above. We all agreed that all plugins should have a link under settings. If the plugin enhances a different part of the site, the settings page could just tell you where the plugin feature is located. 

We also agreed that themes should put features like a static front page under customize like most already do, though I heard Responsive doesn't. I was told it puts static front page under settings. If it is a theme feature, then logically you should be able to at least find a link to where the features are under themes. 

Implementing general rules for plugins and themes would make !WordPress easier to use. Does anyone else agree?
    "	ryansatterfield
Future Releases	21925	Ability to upload multiple .zip files to install in bulk		Administration		normal	normal	Awaiting Review	feature request	new		2012-09-19T12:40:09Z	2013-06-14T17:38:01Z	"It'd be nice to have a drag-and-drop or similar functionality to the Media Uploader to be able to select 5, 10, 17 plugins/themes to upload several .zip files at a time.

Of course, if a folder already exists or if you upload a theme .zip to the plugins page or something like that, then display the appropriate error(s). Otherwise, display the success notification per install."	cliffpaulick
Future Releases	12801	Add Info link to plugins management screen		Administration	3.0	normal	normal	Future Release	feature request	new		2010-04-01T19:08:40Z	2013-01-22T01:40:01Z	"Related to #11050 but instead of the search results, on the regular plugins.php screen. Add ""Info"" link to left of Activate/Deactivate action links, which brings in the tabbed info from the repo. If not from the repo, link does not appear."	jane
Future Releases	24511	Backend function for retrieving post row actions.		Administration		normal	minor	Awaiting Review	feature request	new		2013-06-06T10:27:15Z	2013-06-07T12:02:42Z	"For the cases where post titles are not supported for custom post types, but the user may want the quick action links to exist on their edit.php page table rows on hover.

All it would take would be to move the current code into a callable function and would probably only need to accept a post ID. Could then be called using something like {{{get_post_row_actions($post_id)}}}.

It would return the string of links seen normally below the title on hover."	Nessworthy
Future Releases	12273	Better support for sites with LOTS of pages		Administration	2.7	normal	normal	Future Release	feature request	new		2010-02-18T15:10:02Z	2011-04-18T14:41:23Z	"The default page listing is inadequate for sites utilise Pages as their main content type.

An option to collapse the page listing and hide ""all"" sub-pages (only showing top-level) would dramatically improve the UI making it easier to find pages within the WordPress structure.

'''Example:'''

''Current Page View''

{{{
Page 1
-SubPage 1.1
--SubSubPage 1.1.1
--SubSubPage 1.1.2
-SubPage 1.2
-SubPage 1.3
Page 2
-SubPage 2.1
-SubPage 2.2
--SubSubPage 2.2.1
--SubSubPage 2.2.2
}}}

''Proposed Page View''

''Default View''

{{{
Page 1 [+] (< click to expand)
Page 2 [+]
}}}

''Expanded View''

{{{
Page 1 [-] 
-SubPage 1.1 [+] (< click to expand)
-SubPage 1.2
-SubPage 1.3
Page 2 [+]
}}}

''...''

{{{
Page 1 [-]
-SubPage 1.1 [-]
--SubSubPage 1.1.1
--SubSubPage 1.1.2 (> no further levels)
-SubPage 1.2
-SubPage 1.3
Page 2 [+]
}}}
"	mkjones
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	22862	Consider a CSS preprocessor		Administration		normal	normal	Awaiting Review	feature request	new		2012-12-11T22:01:36Z	2013-01-16T10:33:34Z	"The WordPress admin UI CSS is woefully doomed to a life of inadequacy unless we can amenably agree to use technology already available to build a better future for us and our children.

I propose the introduction of SASS for the WordPress admin styling. SASS is a CSS pre-processor that allows us to write DRY, structured, lightweight CSS. In terms of licensing, SASS is GPL-compatible, licensed under the MIT license.

'''Why use SASS over LESS?'''

The answer is simple. SASS is easier to learn and easier to use because it follows the conventions of CSS at its core. In addition, for developers itching to contribute, there are some extremely useful and easy-to-follow reference docs for SASS, making it easy to set up your local development environment and build websites.

'''What are the advantages?'''

The biggest advantage is that we can write less CSS and offer advanced features for theming the WordPress Admin UI. Developers can more easily reskin the WordPress admin.

Another major benefit is that SASS offers the use of variables within our stylesheets. For our purposes, these variables can be used to calculate layout widths, generate color schemes, font sizes, etc.

Another simple advantage is the fact that we can combine all our CSS styles into a single stylesheet, saving precious HTTP requests. In addition, we can easily minify generated CSS files in bundled versions of WordPress, saving file size and killing unnecessary white space, thus decreasing load times of the admin even further.

'''What are the disadvantages?'''

Developers will need to install Ruby and SASS in order to modify styles for the WordPress Admin. For plugin authors, we should write admin UI CSS in such a way that it is easily overridden with a custom CSS file.

In addition, developers would need to learn SASS if they are going to work directly on the styles for the WordPress admin. For the most part, once you've got the idea of variables, mix-ins, and the structure - you're ready to rock.

Last, but not least, when SASS files are modified, they would need to be compiled and committed to Core every time they change. So instead of pushing a single CSS file, you would be pushing potentially many SCSS files and a generated CSS file.

'''In Summary'''

SASS is a great way to reduce code overhead by adhering to DRY principles and will improve performance and modularity in the WordPress admin, which is a top priority."	chriswallace
Future Releases	20301	Enable media library access from blogroll		Administration	3.3.1	normal	normal	Awaiting Review	feature request	new		2012-03-25T08:50:37Z	2012-03-25T17:10:03Z	"Currently WordPress doesn't give you the option to easily add images from your WordPress plugin to your blogroll items (links). I just released a plugin to do that (http://wordpress.org/extend/plugins/blogroll-media-library-image/) and was told this would be a good one to add to core.

I would love to add a diff-file, but I have no idea how to do this."	illutic
Future Releases	24313	Filter Columns by View		Administration		normal	normal	Awaiting Review	feature request	new		2013-05-11T01:18:56Z	2013-05-11T14:12:54Z	"After searching extensively for a way to do this, and discussing this with fellow WordPress developers, I believe I have found a feature that should be added to WordPress.

When you make a new custom post type, if you have WordPress register a UI for it, it outputs a screen named ""All XXXX's"". Within these, WordPress automatically adds filters. So let's say I've registered a CPT called Downloads. 

So I can now use the built in UI for Downloads and filter the page to show just pending downloads, or just published downloads, for instance.

However, the issue becomes what if you want to display a column for some views, but not others. For instance, if Downloads has a column called ""Sales"" where the number of sales of that particular download is stored, it makes no sense to show that column on Pending Downloads (since they can't have sales before being published).

Currently, at least after days of trying to find a way of doing this, there is no way to do this for the tables registered by WordPress. If I make my own List_Table, then I can do this.

However, there should be a way of adding columns based on filter, so that a developer who adds a column programmatically can go:
{{{
if($view != pending){
// register sales column
}
}}}

Feel free to correct me if I've overlooked a method of doing this.

-Chris"	chriscct7
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	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
Future Releases	15289	Make it easier for a non-standard URL to be used to access wp-admin		Administration	3.1	normal	normal	Future Release	feature request	new	dev-feedback	2010-11-02T13:27:05Z	2013-02-07T21:51:15Z	"For some sites it is vital that the admin be accessible via a path other than {{{/wp-admin/}}}. Clients sometimes require this because it is easier for their users. Also, it is useful if replacing another CMS with WordPress for the root of the admin to have the same URL, although this can be partially fixed with a redirect.

Even when not ''required'' per se, some of us prefer to use a different URL to access the admin because it is more intuitive for our users to use something like {{{/admin/}}} instead of {{{/wp-admin/}}}.

To be clear: I am not suggesting renaming the wp-admin directory, nor am I suggesting adding an option in the UI to change the path.

Rather, I am suggesting that small tweaks be ade to make it easier for power-users to enable the use of a different URL to access the admin area.

I suggest making the following changes :

'''1.''' Use relative urls within the admin where possible without affecting standard installations.

'''2.''' Allow power-users to add a constant to wp-config.php to change the path of the admin for those links which have to be absolute.

I don't think there is much work involved and I am happy to do it.

Core devs have in the past stated that the user of alternative urls to access the admin is 'not supported', but it is unclear whether this simply means that it doesn't work at the present time or that the core team is opposed to allowing it to happen.[[BR]]
If the latter is the case, I would appreciate an explanation - I'm sure there is a good reason if that is the case, but I can't for the life of me think what it could be. ;)"	caesarsgrunt
Future Releases	14676	Moderation email option is confusing, limited		Administration		normal	normal	Future Release	feature request	reopened		2010-08-23T17:06:23Z	2012-05-22T00:53:20Z	"The setting is ""E-mail me whenever a comment is held for moderation"" but in that sentence ""me"" is inaccurate; moderation emails are sent to admin_email.

""Email the admin ($admin_email) whenever"" would be accurate.

Here's a related question: Why not send moderation emails to post authors?"	andy
Future Releases	9057	"Need ""restore defaults"" buttons on all admin screens"		Administration	2.7	normal	normal	Future Release	feature request	new		2009-02-06T08:50:30Z	2011-07-08T15:06:31Z	"Need ""restore defaults"" buttons on all admin screen items, else once
you change something, there's no way to get it back to whatever the
default was, or find out even, short of a total reinstall. Includes
""screen options"" items too.
"	jidanni
Future Releases	12004	Select Sidebar when adding Posts/Pages		Administration	3.0	normal	normal	Future Release	feature request	new		2010-01-25T13:26:16Z	2010-01-25T23:28:01Z	"Hey all,

I think it would be a cool feature to be able to create sidebars in WP, and then when creating a page you can choose that specific sidebar.

I think that this can be accomplished by using the ''Parent'' page technique of selecting if the Page has a Parent and if so which one.

Can we develop an option to choose a Sidebar created in the Widgets panel?

Cheers,
Aron
ps: if my help is needed ( im good at design, not coding ) please contact me: info@zipyourmix.com ;)!"	lsddesign
Future Releases	11972	Sort View Post/Pages by Column		Administration	3.0	normal	normal	Future Release	feature request	new		2010-01-21T21:46:27Z	2010-03-21T01:51:40Z	Recently I discovered in WPMU in Site Admin options, you can sort for instance Site Admin->Blogs by last activity date. That is a very handy feature, and certainly would useful for a site with hundreds of nested pages. To be able to sort that list by date, rather than just title would be useful, as it sorts by title of the parent page, and finding a 3rd level child can be difficult to say the least. The search feature is lacking but that is for another ticket.  Likewise, sorting posts by category, author, etc could be useful. Since the functionality seems to already be there for sorting these type columns, and the code's been moved in already, I'd think it'd be a nominal change. I simply don't know what direction these menus are going yet to offer a working suggestion. Just wanted to get my 2¢ in before it's too late.	miklb
Future Releases	23575	Standard UI Classes and Functions		Administration	3.5	normal	normal	Awaiting Review	feature request	new		2013-02-21T09:09:27Z	2013-02-22T02:31:55Z	"It would be nice if wordpress allowed you to use the Post UI natively in my plugins, at the moment I've had to write a few classes for my Plugin Framework that mimic the Publish Metabox and Tabbed Metabox. 

As there is simply no easy way to do this at the moment, I think there should also be a better way of registering hidden menus. I have to jump through loads of hoops just to do this.

"	jscampbell.05
Future Releases	22734	do_action-post_edit_form_tag		Administration	3.4.2	normal	normal	Awaiting Review	feature request	new	reporter-feedback	2012-12-04T18:01:27Z	2013-06-06T12:23:56Z	"Possible to add an action on the form for adding media.

{{{
File : /wp-admin/media.php
Line : 115
}}}

{{{
<form method=""post"" action="""" class=""media-upload-form"" id=""media-single-form"">
}}}

to

{{{
<form method=""post"" action="""" class=""media-upload-form"" id=""media-single-form""<?php do_action('post_edit_form_tag'); ?>>
}}}"	bems78
Future Releases	16379	"Better UI for doing ""Page on Front"""		Administration	3.1	normal	normal	Future Release	task (blessed)	new		2011-01-26T19:47:25Z	2013-03-14T15:20:33Z	"[[Image(http://grab.by/grabs/132427e6c1166ed3e4d8214959b9568a.png)]]

This is the existing ""Page on Front"" UI. The process is as follows:

 1. Create a ""Front"" Page
 2. Create a ""Blog"" Page
 3. Select the ""Front"" Page in the ""Front Page"" dropdown
 4. Select the ""Blog"" Page in the ""Blog Page"" dropdown.

1 and 3 make sense. If you want a page on front, then you obviously need to create a page to live there, along with its content, and then designate it. But the ""Blog"" page is just a dummy. It's sole purpose is to create and maintain a URL for your blog. So why not just have something like this?

Blog URL: http://example.com/ {input box}

If a page exists in the URL they type, it gets used. If not, we create one on the fly as a dummy. This seems a more natural way of doing it. You don't care about the dummy page — you just want to choose an appropriate URL for your blog."	markjaquith
Future Releases	18655	Responsive Admin for Small Screen Devices		Administration		normal	normal	Future Release	task (blessed)	new		2011-09-13T18:44:16Z	2013-01-03T06:24:12Z	Working off of #18198  -  Making the admin respond to small devices, phones, etc. 	saracannon
Future Releases	16339	pushState Test Case		Administration		normal	normal	Future Release	task (blessed)	new		2011-01-22T06:30:41Z	2011-01-27T09:42:50Z	"This isn't a useful bit of code, just a test case to ground future pushState work for 3.2.  Or be ignored by future pushState work for 3.2 :)

Attached is a test case for determining browser behavior when using pushState.

The numbered links use AJAX and pushState.  The ""Other"" link is a real (non-AJAX) link to an external site.

If the state of the page is refreshed via AJAX, you'll see a var_dump( $_POST ).  If the state of the page is refreshed by a page refresh, you won't.

An example of something this test says is broken in Safari 5.0.3 (6533.19.4):

 1. Load the page (state = 0: pageload)
 2. click ""One"" (state = 1: ajax)
 3. click ""Two"" (state = 2: ajax)
 4. click ""Three"" (state = 3: ajax)
 5. click ""Other"" (state = external site: pageload)
 6. go Back in browser history (state = 3: ajax or just history?)
 7. go Back (state = 2: ajax or just history?)
 8. go Back (state = 1: ajax or just history?)
 9. go Back (state = 0: ajax). Everything is fine up to this point, though it's odd we do an AJAX request to get here.
 10. refresh the page once, either by CTRL-R or by hitting enter in the URL bar (state = 3: ajax). That's wrong.  What happened? Why are we here?
 11. refresh the page a second time (state = 0: pageload). As expected.

An example of something the test says is broken in Chrome10.0.642.2 dev:
 1. Do pretty much anything.  Chrome Dev fires a popState event on the first page load.

It could be a badly written test, or a badly written implementation of push/popState handling, or both.  These are the kinds of scenarios we'll need to test, though."	mdawaffe
Future Releases	22857	'Header Image' state isn't removed from images previously used as header image		Appearance	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-12-11T18:54:08Z	2012-12-11T23:04:31Z	"Steps to reproduce:

 1. Set your site's header image from Appearance -> Header by uploading an image or choosing one from your media library.
 2. Repeat step 1.
 3. Visit the Media Library and note that your previous header image still says 'Header Image' next to it.

Not a 3.5 regression as it happens in 3.4.2 too.

"	johnbillion
Future Releases	24032	An issue with the theme customize function and jQuery tabs		Appearance	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-10T15:07:04Z	2013-04-10T18:31:50Z	"WP 3.5.1 ( same happens in the 3.6 beta-1 )
No plugins installed ( vanilla WP )
TwentyTwelve Theme ( happens with TwentyThirteen as well )

So when you have or using jQuery Tabs in a page and you go to the theme customize page, the customizer panel will become sluggish and not very responsive when you hover your mouse over the accordion panel and if you look at the preview, the content is jumbled and also very sluggish.  It seems something is executing in a loop over and over again making it sluggish but I did not see anything in the error console for some reason.  Perhaps this is because it is on an iFrame.

Please note that the page in the frontend loads just fine with the jQuery Tabs and works normally.  It is only when you use the backend theme customize page is where this issue starts.

I have tried this in both 3.5.1 and 3.6 beta-1 and same results.

Here are the steps to reproduce this.

In functions.php load up:

{{{
wp_enqueue_script( 'jquery-ui-core' );
wp_enqueue_script( 'jquery-ui-tabs' );
}}}

In the homepage (any page) put in:

{{{
<div class=""test"">
<ul>
<li><a href=""#abc"">abc</a></li>
<li><a href=""#xyz"">xyz</a></li>
</ul>
<div id=""abc"">
	some content here
</div>
<div id=""xyz"">
	some other content
</div>
</div>
}}}

In theme js, put in:

{{{
$('.test').tabs();
}}}

Then go to your homepage in the frontend to confirm the tabs are working and normal.  Now go to the backend theme customize and you will see the issue I am trying to describe."	splashingpixels.com
Future Releases	23554	Change Header Delete Behavior		Appearance		normal	normal	Awaiting Review	defect (bug)	new		2013-02-20T07:11:27Z	2013-02-20T08:57:30Z	When clicking the Remove header button, it should remove the header image from the list of images for rotation as well as remove from the currently selected image.  Currently you must delete the image from the media library (which may be several hundred or thousand images deep) to remove it from the list.	tribuseric
Future Releases	22148	Customizer Uploader doesn't handle large files properly		Appearance	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-10-10T05:07:34Z	2012-11-11T18:14:45Z	"Both of these tests were with image files larger than the max file size - 3MB images with a 2MB max file size:

Dragging the file onto the upload area, the browser window redirects to the location of the local file, the same as if the file were dragged to a non-dropzone area.

When using the file browser to select the file, the upload fails silently.

In both cases, an error similar the Media Uploader would be preferable.
"	pento
Future Releases	24528	Customizer checkbox with refresh option gives inconsistent values		Appearance	3.5	normal	normal	Awaiting Review	defect (bug)	new		2013-06-07T07:22:53Z	2013-06-09T01:51:02Z	"When adding a checkbox control to the customizer feature with type = refresh, the value returned is sometimes a string and sometimes a boolean, when the checkbox is changed.

I've tested this in 3.5, and 3.6-beta3-24407.

How to reproduce in 3.5:

Load the ""Twenty Twelve"" theme. In the functions file add a test checkbox setting & control:

{{{
$wp_customize->add_setting('test', array(
    'type' => 'option',
    'default' => true,
    'priority' => 10,
    'transport' => 'refresh'
  ));

  $wp_customize->add_control( new WP_Customize_Control( $wp_customize, 'test', array(
    'label' => __( 'Test' ),
    'section' => 'title_tagline',
    'settings' => 'test',
    'type' => 'checkbox'
  )));
}}}

Dump the value into the index.php of the theme:

{{{
<?php var_dump(get_option('test')); ?>
}}}

This is where things get odd:

Load up the customizer, 
'''- Theme should output: bool(true)'''

Toggle the checkbox, allowing for the iframe to refresh each time:
'''All results should be boolean values.'''

Toggle to checkbox to ON, hit save, and refresh the browser window.
'''- Theme should output: string(1) ""1""'''

Toggle the checkbox to OFF, allowing for the iframe to refresh:
'''Value does not update'''

Toggle the checkbox some more, allowing for the iframe to refresh each time:
'''Results will toggle between string(1) ""1"" and boolean(true)'''

ONE LAST TEST:
Toggle to checkbox to OFF, hit save, and refresh the browser window.
'''- Theme should output: string(0) """"'''

Toggle the checkbox some more, allowing for the iframe to refresh each time:
'''Results will toggle between string(0) """" and boolean(true)'''

Thanks"	nathanrowe82
Future Releases	23225	Customizer is Incompatible with jQuery UI Tabs.		Appearance	3.4	normal	normal	Awaiting Review	defect (bug)	new		2013-01-17T09:34:21Z	2013-05-10T03:39:09Z	"Steps to reproduce:

 1. Install the attached mfields-test-jquery-ui-tabs.php plugin.
 2. Open the Chrome console.
 3. Open the customizer and watch the console.

At this point you should see that a slew of XHR requests are triggered. If you reach a certain type of javascript error then the XHR requests will stop and the preview frame in the customizer will go blank.

It seems like jQuery UI Tabs and the customizer are currently incompatible. This will affect any theme or plugin that is using this library including the popular [http://wordpress.org/extend/plugins/genesis-tabs/ Genesis Tabs] plugin."	mfields
Future Releases	21890	Customizer spinner breaks button alignment with longer strings		Appearance	3.4	normal	normal	Future Release	defect (bug)	new		2012-09-14T10:57:02Z	2012-11-08T22:01:23Z	See the screenshot.	SergeyBiryukov
Future Releases	22037	Customizer: Live preview fetches page but does not display		Appearance	3.4.2	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-09-28T15:14:54Z	2012-11-14T17:29:37Z	"I just set-up a plain installation of 3.4.2. Configured it for multisite use. Set-up two sites, both working fine.

When going into a sites Appearance settings to customize the theme (TwentyEleven), the Customizer shows the control panel on the left, but the preview remains blank.

Firebug shows no Javascript errors.

'''It also shows, that a POST request is sent to fetch the front page and that the page is actually returned in the response. It appears the response is just not added to the right-hand preview area.'''"	marcoliverteschke
Future Releases	22498	Disabling Header Text should not reset Header Text Color to default		Appearance	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-11-18T22:31:17Z	2012-11-18T22:31:17Z	"In Appearance > Header, if you uncheck the 'Show header text with your image' option and Save, the Text Color option is reset to whatever the default is.

With JS enabled, the Text Color option is hidden when the checkbox is unchecked, but in no-js both options are displayed all the time. It's odd to set a header text color and uncheck the option only to have it reset your choice to the default.

Related: #22461"	DrewAPicture
Future Releases	24545	Fix Admin Layout When Displaying Errors		Appearance	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-06-09T15:15:40Z	2013-06-10T02:52:45Z	Whenever a PHP error is displayed in the backend, it causes WordPress layout to screw up on the options pages by enlarging the font size and pushing the footer up to the bottom of the viewport so that it's not at the bottom of the page, instead, the bottom of the screen up so when you scroll to the bottom of the page, it's actually 3/4 way or 1/2 way up the page.	sunnyratilal
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	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
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	21492	Theme customizer > Static front page: missing error message when front page and posts pages are similar		Appearance		normal	normal	Awaiting Review	defect (bug)	new		2012-08-06T00:15:25Z	2012-08-06T01:11:40Z	"Steps to reproduce:

1. Activate Twenty Eleven
2. Open the Customizer
3. In ""Static Front page"", choose the same page as your front page and Posts page:
  * You do not receive any warning 
  * http://i.wpne.ws/IYAO
  * In Reading Settings, you do actually receive a warning: http://i.wpne.ws/IY2S (see http://core.trac.wordpress.org/browser/trunk/wp-admin/options-reading.php#L99 )

Would it be possible to display the same warning in the Customizer, to avoid any confusion for the users?

Related: #19627 and #16379"	hd-J
Future Releases	20733	Theme customizer doesn't order sections based on order added		Appearance	3.4	normal	normal	Future Release	defect (bug)	new	early	2012-05-22T23:36:48Z	2013-01-21T15:16:04Z	"When adding sections to the theme customizer, sections with the same priority are given seemingly random order. From the [http://core.trac.wordpress.org/ticket/19910 original customizer ticket]:

> Settings and sections both contain priority parameters (you can specify these in the constructor or alter them afterwards) which serve as the primary means of sorting sections before they're rendered. The order settings/sections are added serves as a secondary sorting mechanism (tiebreaker) when multiple items share the same priority.

I was under the impression that if the priority was the same, the sections would appear in the order they were added. However, if you add sections A, B, and C (in that order) it seems to display them in order B, C, A.

To replicate, add this code to your theme:

{{{
add_action( 'customize_register', 'theme_customize_register' );

function theme_customize_register( $wp_customize ) {
	// Register Section A
	$wp_customize->add_section( 'theme_section_a', array(
		'title'    => 'Section A',
		'priority' => 35,
	) );
	$wp_customize->add_setting( 'theme_option_a', array(
		'type'              => 'option',
	) );
	$wp_customize->add_control( 'theme_option_a', array(
		'section'    => 'theme_section_a',
		'type'       => 'text',
	) );

	// Register Section B
	$wp_customize->add_section( 'theme_section_b', array(
		'title'    => 'Section B',
		'priority' => 35,
	) );
	$wp_customize->add_setting( 'theme_option_b', array(
		'type'              => 'option',
	) );
	$wp_customize->add_control( 'theme_option_b', array(
		'section'    => 'theme_section_b',
		'type'       => 'text',
	) );

	// Register Section C
	$wp_customize->add_section( 'theme_section_c', array(
		'title'    => 'Section C',
		'priority' => 35,
	) );
	$wp_customize->add_setting( 'theme_option_c', array(
		'type'              => 'option',
	) );
	$wp_customize->add_control( 'theme_option_c', array(
		'section'    => 'theme_section_c',
		'type'       => 'text',
	) );
}
}}}

'''Expected result:''' Sections show up in order A, B, C

'''Actual result:''' Sections show up in order B, C, A

Sorry if I'm doing something stupid, or if this isn't the intended functionality. I'm running trunk without any plugins."	andyadams
Future Releases	23956	jQuery UI Datepicker adds empty but visible div at bottom of page		Appearance	3.5.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-04-06T01:52:12Z	2013-04-06T08:19:52Z	"This bug seems to be related to the [http://bugs.jqueryui.com/ticket/4111 this] jQuery UI bug, which has been fixed, but the following WordPress stylesheet seems to be making the bug re-appear:

wp-includes/css/jquery-ui-dialog.min.css

As far as I can tell, removing the following rule seems to fix it:


{{{
.ui-helper-clearfix:after {
    content:""."";
}
}}}
"	julianm
Future Releases	22237	Add a keyboard shortcut for collapse/expand in the customizer		Appearance		normal	normal	Awaiting Review	enhancement	new	close	2012-10-21T02:59:31Z	2012-10-24T17:33:30Z	Can we add a keyboard shortcut to the customizer for collapsing/expanding the left panel?	designsimply
Future Releases	21792	Add link to settings.general from appearance.header		Appearance		normal	normal	Awaiting Review	enhancement	new		2012-09-04T19:38:50Z	2012-09-04T19:40:36Z	"Multiple users that we've tested have ended up on appearance->header when asked to change their ""site title"".  It seems logical.  Should we add a link there?"	lessbloat
Future Releases	22348	Add support for custom background default images		Appearance	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-11-02T19:25:12Z	2012-11-02T19:25:12Z	"When specifying custom header default images for a theme, I always forget that you can't do the same for custom backgrounds.

It would be highly desirable to be able to set default background images, just as you can with custom headers."	dgwyer
Future Releases	17800	Custom Header bug with deleted images		Appearance	3.2	normal	normal	Awaiting Review	enhancement	new		2011-06-14T12:43:15Z	2012-12-03T12:08:03Z	"I'm not a tech.
I've added images to Twenty Eleven header.
I wrong and I've deleted few images directly using ftp now you can see in the image that the header has the markers of the images without the images.

"	pivari
Future Releases	22880	Customize Themes without activation		Appearance		normal	normal	Awaiting Review	enhancement	new		2012-12-12T11:34:51Z	2012-12-12T11:38:58Z	"Add a posibility to customize deactivated themes with the Theme-Customizer without activating them by default.
Useful for Blogs running multiple Themes between which the frontend user can switch."	kkkrys
Future Releases	21059	Customizer color picker has no remove button		Appearance	3.4	normal	normal	Awaiting Review	enhancement	new		2012-06-24T11:34:12Z	2013-04-11T10:23:37Z	There is no remove button for color picker in the customizer. It would be great if we could remove the color or set it to the default if we don't need the color.	kcssm
Future Releases	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
Future Releases	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-06-07T15:37:29Z	"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
Future Releases	21666	Theme customizer reset		Appearance	3.4.2	normal	normal	Awaiting Review	feature request	new		2012-08-23T10:09:49Z	2013-05-18T13:13:22Z	"It would be useful to be able to reset the settings to the defaults as specified in the add_setting() class method when setting up each setting.

These could be reset on a section by section basis and/or for ALL settings."	dgwyer
Future Releases	21785	Add header image uploads with cropping to the customizer		Appearance	3.4	normal	normal	Future Release	task (blessed)	new	early	2012-09-04T04:56:41Z	2013-05-22T10:06:20Z	See #21355 for an explanation for why header image uploads (sans cropping) was removed from the 3.4 branch. This ticket is about adding it back, with a crop step, to ensure proper support.	nacin
Future Releases	15069	Autosave function assumes that there is only on tinyMCE on the page		Autosave	3.0.1	normal	normal	Future Release	defect (bug)	new	early	2010-10-08T10:28:12Z	2011-01-14T09:35:22Z	"Autosave javascript assumes there is only one tinyMCE instance on the post editor page, thus breaking autosave feature under the next circumstances:
1. Content editor is in HTML mode
2. Some custom tinyMCE instances are added to the page by some plugin or theme.

A patch that fixes that problem is attached."	karevn
Future Releases	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
Future Releases	22601	Make post content autosave work more generically		Autosave		normal	normal	Awaiting Review	enhancement	new		2012-11-27T04:00:31Z	2012-12-14T23:51:36Z	"The JS for autosave/AYS looks for the contents of `#post #content`. While we should fix the other JS issue related to targeting `#content` in #22600, it seems that autosave/AYS should be looking for the textarea (or whatever type of input) with the name of content instead, since having that data in the form will save to the post content. That way, if somebody does choose to use a different ID but the right input name, the autosave benefits will kick in.

Discovered while working on #22491."	helen
Future Releases	19960	Problem posting by email from MailChimp		Blog by Email	3.3.1	normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2012-02-04T01:24:20Z	2012-09-15T19:18:09Z	"Blog by email seems to have a strange bug. 

If I try to post something by email from my gmail account, it works fine. But if I send the email via MailChimp, the posting doesn't work. No post is created, published or draft...it's as if the mail was never received by WordPress

This applies to both self-hosted WordPress and wordpress.org

I have tried doing the same thing with other services such as blogger.com, and it works fine there."	sooskriszta
Future Releases	19984	Issue with Default Post Format		Blog by Email	3.3.1	normal	major	Awaiting Review	enhancement	new	has-patch	2012-02-07T20:29:41Z	2012-08-24T01:34:27Z	I set my Default Post Format as Aside. So I expect all my posts via email will appear as Aside, same as Default Post Category does perfectly while post via email. But it is always posting as Standard whenever I post by email. Kindly fix this. Wordpress is Awesome :)	binarymag
Future Releases	14798	Twenty Ten Theme - adding an extra skip link		Bundled Theme		normal	normal	WordPress.org	defect (bug)	new		2010-09-07T12:07:33Z	2012-08-09T20:12:48Z	"Being able to skip to content is good, but currently there is no easy way to jump to the sidebar menu. 

In order to add this extra skip (jump to menu) link I've changed the div to ul. CSS changes are similar to #14795 but tweaked to allow for the new markup.

"	elfin
Future Releases	24599	Twenty Thirteen: Horizontal scrollbar appears in large viewports		Bundled Theme	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-06-18T20:49:06Z	2013-06-18T20:56:12Z	"Starting from 1614 pixels up to 1600 pixels viewport width, the page (.site) width is 2 pixels wider than the body width, causing an horizontal scrollbar to appear. It seems to be caused by the following rule:

{{{
.site {
	-webkit-box-sizing: content-box;
	-moz-box-sizing: content-box;
	box-sizing: content-box;
}
}}}

which I don't understand why it has been introduced as of changeset 23962."	gorgoglionemeister
Future Releases	24143	When define('WP_CONTENT_DIR', 'your-dir') twentythirteen - The theme directory does not exist.		Bundled Theme	3.4	normal	normal	Awaiting Review	defect (bug)	reopened	reporter-feedback	2013-04-20T10:08:16Z	2013-05-06T22:57:39Z	"If you use either of following in you wp-config.php you'd automatically get a Broken Themes.

{{{
define('WP_CONTENT_DIR', 'your-dir');
define('WP_CONTENT_URL', 'your-url');
}}}

The following themes are installed but incomplete. Themes must have a stylesheet and a template.

Name 	Description

twentythirteen 	The theme directory does not exist."	azizur
Future Releases	14782	Accessibility: Twenty Ten Theme - links, forms, skip link		Bundled Theme		normal	normal	WordPress.org	enhancement	new		2010-09-04T15:50:01Z	2012-09-27T13:42:46Z	"Starting off with changes to the CSS only.

Links: colors amended where necessary. added underscores and/or color changes for active, hover and focus.

Gallery image links: adjusted things to use margin to center the image rather than padding, to allow for adding highlighting on image links.

Skip link: now appears above the #access menu when tabbing through the page.

Grey text/links: was 888 this just failed the color contrast, so changed it to 777 throughout.

Forms: added highlight for input text and textarea, for active and focus."	elfin
Future Releases	21506	Standard Theme Hooks		Bundled Theme		normal	normal	Awaiting Review	enhancement	new		2012-08-07T02:10:55Z	2013-03-28T22:12:58Z	"During the hack day at WordCamp SF, Konstantin Kovshenin and I sat down to work out a solution to allow for better communication between themes and plugins. We propose that core introduce 4 new hooks into the default WordPress themes allowing plugins to add custom markup relative to common theme elements. While many other theme locations could be recognized, we have only included hooks that we could provide at least three use common use cases for.

header_after: Allows custom markup to be inserted after all visual header elements have rendered. Possible use cases for this hook include:

 * Breadcrumb navigation.
 * Links to social profiles.
 * Advertising.
 * log in/out form.

post_after: Allows custom markup to be inserted after all visual elements have rendered for the current global post object. This hook would fix the issue originally reported in #18561. Possible use cases for this hook include:

 * Sharing links.
 * Related posts.
 * Ratings.
 * Author bio.

comment_after: Allows custom markup to be inserted after all visual elements have rendered for the current global comment object. Possible use cases for this hook include:

 * Upvote/Downvote control.
 * Ratings.
 * Show/hide threads functionality.

footer_after: Allows custom markup to be inserted after all visual elements have rendered for the footer. While this action is similar to {{{wp_footer}}}, it would be possible for the theme author to move this into nested html elements. To my knowledge, {{{wp_footer}}} is intended to fire immediately before the closing {{{body}}} tag. Possible use case for this hook include:

 * Links to social profiles.
 * Advertising.
 * The ""small print"" or copyright information.

If standardized hooks such as these were recognized by core, it would also have a positive effect on child theming. Theme authors would no longer need to override entire files just to introduce an element of two.

We have prepared 3 patches for the default themes to demonstrate placement of these hooks as well as a plugin to demonstrate their usage."	mfields
Future Releases	23184	Twenty Eleven/Twelve: Mismatched lines in GitHub Gists		Bundled Theme	3.5	lowest	normal	WordPress.org	enhancement	new	close	2013-01-11T19:29:36Z	2013-04-26T14:26:57Z	"GitHub Gists are displayed with the code and line numbers misaligned, due to the difference in font-size and/or line-height of `<pre>` and `<table>` elements. 

Originally reported in [http://wordpress.org/support/topic/gists-look-crazy-with-twenty-twelve this thread] and on wp.com.

Example: http://themebuster.wordpress.net/gist-test/"	obenland
Future Releases	14791	Twenty Ten Theme - Better Link Highlighting		Bundled Theme		normal	normal	WordPress.org	enhancement	new		2010-09-07T10:18:19Z	2012-09-27T13:42:49Z	mainly changing the state of text decoration(underline/none). This aids users that tab through links on a page identify where they are.	elfin
Future Releases	14792	Twenty Ten Theme - gallery changes		Bundled Theme		normal	normal	WordPress.org	enhancement	new		2010-09-07T10:22:33Z	2012-09-27T13:42:52Z	With reference to #14791 those changes will produce an ugly 10px wide border in red on focus/hover etc. This patch does fix this, at the expensive of top/bottom margins. This therefore may need an additional patch before it can be applied.	elfin
Future Releases	24595	Twenty Thirteen: Load Genericons in a More Plugin-friendly Way		Bundled Theme		normal	normal	Awaiting Review	enhancement	new		2013-06-18T08:20:27Z	2013-06-18T08:20:27Z	"Genericons are a useful tool for plugins, but it is currently difficult to use them in a plugin in an efficient way. It would be nice if Twenty Thirteen loaded them in a way that would both play nicely with plugins that want to use them and set a standard for how plugins should load them.

I came up with a couple of options:
- Package Genericons directly with WordPress, instead of bundled through Twenty Thirteen, and register as a style in core ({{{wp_register_style()}}}), then {{{wp_enqueue_style('genericons')}}} in both Twenty Thirteen and plugins. Plugins could also package Genericons if targeting WordPress <3.6. The loaded stylesheet would just contain the {{{@font-face}}} declaration. But having Genericons available directly in core wouldn't be as appropriate as, for example, having Dashicons available (for front-end use) would be.
- Move the {{{@font-face}}} declaration to its own file and load it with {{{wp_register/enqueue_style()}}}. Plugins could check for Genericons with {{{wp_style_is()}}} and load them if necessary, which would decrease the potential to load from multiple places. This would establish a ""correct"" method for loading Genericons in plugins and at least provide the tools to avoid duplicate declarations, but could be messier to implement in plugins.

Both methods have advantages and disadvantages, and there are probably additional possibilities, but I think we should do something a bit more standardized than the current setup (loading Genericons from the main {{{style.css}}} file)."	celloexpressions
Future Releases	23834	Twenty Thirteen: add visual Indicator for menu items with children		Bundled Theme	trunk	normal	normal	Future Release	enhancement	new		2013-03-21T04:07:43Z	2013-03-21T23:38:44Z	"It's helpful to have a visual indicator when a top level menu item contains a hidden drop down menu.

This patch adds a filter to wp_nav_menu_objects in order to add the class ""has-children"" to top level menu items that contain children.  This allows us to style it with psuedo element, similar to how the menu-toggle is styled for smaller screens.

The filter I used was posted by @chipbennet on the WordPress Theme Reviewers List. The same functionality could also be achieved by a Custom Nav Walker (see http://wptheming.com/2013/03/drop-down-menu-indicator/), but Chip's solution seemed more straightforward.

Neither method works unless a menu has actually been set.

"	downstairsdev
Future Releases	15385	Use get_template_part() for post formats in Twenty Ten		Bundled Theme		normal	normal	WordPress.org	enhancement	new		2010-11-11T13:36:47Z	2013-02-19T04:25:57Z	"Let's encourage some standardization in themes by giving Twenty Ten the following:
{{{
get_template_part( 'post-format', 'aside' );
get_template_part( 'post-format', 'gallery' );
}}}
We'll leave the default in loop.php, I'm thinking, though we could also use post-format-default.

I'm going to comment on #14746 that I think, if post formats are supported, then 'default' should always be supported and should be enforced as the default, even if nothing is stored yet for that post."	nacin
Future Releases	24514	Collaborative theme development		Bundled Theme		normal	normal	Awaiting Review	feature request	new		2013-06-06T11:19:20Z	2013-06-06T11:19:20Z	"It would be very interesting if, for the next theme (Twenty Fourteen), all the development process (desing, early decisions, etc.) will take place on trac (or github, for example).

It will be a way for designer/developers to interact and, above all, a great learning tool."	gorgoglionemeister
Future Releases	23330	Allow autoloading all options, not just autoload = yes options		Cache	3.5.1	normal	normal	Future Release	defect (bug)	new		2013-01-30T21:12:57Z	2013-02-21T04:26:41Z	"For 5 years on wordpress.com we have ignored the autoload field for options. In wp_load_alloptions(), autoload = yes is not part of the query. Why? Because wordpress.com has a persistent cache. Thus, the transients that constitute the bulk of autoload = no options are stored in cache, never in the options table. Querying autoload=yes makes the query slower for no reason.

Having autoload = no options also complicates notoptions caching. Core has a notoptions cache that would be unnecessary if you can assume that wp_load_alloptions() loads every option. If an option is not in alloptions, then it does not exist.

Other large sites that use a persistent cache might also like to ignore the autoload flag. Core could automatically switch to ignoring autoload when an external object cache is being used, but administrators might want to control this so they can clean out old transients from options tables and do whatever other housekeeping is desired. So, let's add a filter that allows toggling this. When autoload is being ignored the wp_load_alloptions() query does not include autoload=yes and notoptions is not used."	ryan
Future Releases	22661	Allow object caches to degrade gracefully		Cache		normal	normal	Awaiting Review	defect (bug)	new		2012-11-30T20:53:57Z	2013-01-10T00:08:36Z	"Because of the way object caches are loaded, if a custom object cache can't run (say, Memcached or APC is not actually installed), it cannot gracefully degrade to the built-in object cache.

Witness this code in {{{wp_start_object_cache()}}}:

{{{
 	if ( ! function_exists( 'wp_cache_init' ) ) {
		if ( file_exists( WP_CONTENT_DIR . '/object-cache.php' ) ) {
			require_once ( WP_CONTENT_DIR . '/object-cache.php' );
			$_wp_using_ext_object_cache = true;
		} else {
			require_once ( ABSPATH . WPINC . '/cache.php' );
			$_wp_using_ext_object_cache = false;
		}
		$first_init = true;
	} else if ( !$_wp_using_ext_object_cache && file_exists( WP_CONTENT_DIR . '/object-cache.php' ) ) {
		// Sometimes advanced-cache.php can load object-cache.php before it is loaded here.
		// This breaks the function_exists check above and can result in $_wp_using_ext_object_cache
		// being set incorrectly. Double check if an external cache exists.
		$_wp_using_ext_object_cache = true;
	}
}}}

So a custom object cache is loaded. If it wants to bail and defer to the built in object caching, it can do that by doing the include itself. But then WordPress sets {{{$_wp_using_ext_object_cache = true;}}} '''after''' that require. So WordPress thinks it is using an external object cache when it's actually not. This leads to oddness.

This can sometimes be hacked around by adding a callback to the very first WP action available that sets {{{$_wp_using_ext_object_cache = false;}}}, but that has issues: calls to the object cache might be made before that code can run, and {{{add_action()}}} is not always available at that point (because some {{{advanced-cache.php}}} drop-ins load the object cache really early. See Batcache.

Proposed solution: change the order of the {{{require_once()}}} and the setting of {{{$_wp_using_ext_object_cache}}}. That way, the external object cache can override the variable."	markjaquith
Future Releases	22526	Changing category doesn't invalidate cache		Cache	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-11-21T11:55:37Z	2012-11-21T11:55:37Z	"Hi,

I am using object-cache.php Memcached v2.0.2 (Dropins) with the current WordPress version, but I don't think this has anything to do with the dropin.

I noticed that category changes don't invalidate/update the cache.

For example:
1. Create a category ""Foo"".

2. Assign some postings to ""Foo"".

3. View your postings in backend and frontend, so that results get cached.

4. Rename ""Foo"" category to ""Bar"".

5. Reload some postings, which are in that category. But they still display the old ""Foo"" category instead the new ""Bar"" category name.

Flushing memcached would ""solve"" this problem, that's why I think renaming categories don't invalidate/update the cache."	Whissi
Future Releases	22478	Remove $force argument from WP_Object_Cache::delete()		Cache	3.4.2	normal	normal	Future Release	defect (bug)	new		2012-11-16T19:02:07Z	2012-11-16T19:02:07Z	This was introduced way back in [3086] and hasn't been needed for years.	ryan
Future Releases	14485	Taxonomy hierarchy cache isn't properly refreshed		Cache	3.0	high	normal	Future Release	defect (bug)	new	needs-unit-tests	2010-07-31T03:11:13Z	2013-04-30T20:46:25Z	"I've developed a plugin that can create parent and children categories at the same time. It works well at 2.8.6 but it doesn't work as what I expect at 3.0.

When I create new parent and children categories at the same time, it only shows parent category in the Categories dashboard, but the children category is actually created. If I create another category or delete one category, the children category shows up. I think it should be a problem of wordpress cache, but I have no idea where to start tracing.

I use wp_create_category at wp-admin/includes/taxonomy.php to create categories. Besides, I have tried clean_term_cache but it didn't help. And I didn't activate other plugins when I tested this plugin.

It happened exactly when creating NEW parent and children categories."	thealien
Future Releases	22174	_get_non_cached_ids() should use wp_cache_get_multi(), if available.		Cache	3.4.2	normal	normal	Future Release	defect (bug)	new		2012-10-12T14:12:40Z	2013-01-10T00:10:20Z	Add wp_cache_get_multi() to all cache backends and conditionally use it in _get_non_cached_ids() so that post objects can be fetched from cache in parallel.	ryan
Future Releases	14254	update_meta_cache fails; query too large?		Cache	2.9.2	normal	normal	Awaiting Review	defect (bug)	reopened	dev-feedback	2010-07-09T19:49:22Z	2013-03-13T10:10:05Z	"In the file meta.php, around line 183 in the 'update_meta_cache()' function, it tries to do a query but I noticed this can fail (ie. crash wordpress) if there are too many post id's in the query.

The function is being called from query_posts(), with 'posts_per_page' set to -1.

An example query that crashed it:
{{{
SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (1009,1006,989,933,902,860,859,858,857,793,838,837,836,827,825,310,780,777,776,775,774,773,770,763,760,759,758,757,728,756,755,754,753,752,751,750,748,746,
732,736,729,726,725,724,723,722,720,719,717,716,715,710,709,503,692,289,625,268,593,583,582,332,32,30,28,26,24,22)
}}}
Maybe there is some limit associated with queries of this type internal to wordpress, as this query works fine in phpMySql.

Apologies if this is already reported or irrelevant in 3.0!
"	newpixel
Future Releases	22176	Cache the results of the posts_request_ids query		Cache	3.4.2	normal	normal	Future Release	enhancement	new		2012-10-12T14:59:37Z	2013-01-10T00:11:47Z	We are to the point where we could replace the advanced post cache plugin with something in core that is far simpler. We're most of the way there since introducing the split query. And with #22024 we have a good way of doing per-blog cache invalidation for classes of objects, which would be needed by this. Leveraging wp_cache_get_multi() as suggested in #22174 would provide a complete replacement for the adv post cache plugin.  http://plugins.svn.wordpress.org/advanced-caching/trunk/advanced-caching.php	ryan
Future Releases	19008	Introduce a notoptions cache for site options		Cache		normal	normal	Awaiting Review	enhancement	new		2011-10-19T21:11:47Z	2013-02-19T18:52:05Z	"Following up on #18955.

Adding a 'notoptions' cache for site options would be consistent with normal options."	duck_
Future Releases	18488	set_transient crashes when value parameter is a SimpleXMLElement object		Cache	3.2.1	normal	normal	Awaiting Review	enhancement	reopened		2011-08-19T18:58:02Z	2012-09-01T18:03:16Z	"I have been developing a plugin that obtains information about high and low tides in the UK. The data is obtained from another site as a SimpleXMLElement. I found that when I passed a value to set_transient that had been assigned directly from the SimpleXMLObject then it was being received as an object and somewhere in the innards of the function the routine crashed. My workaround was to cast the assignment.
e.g. this failed

{{{
$title = $channel->item->title;
$store = '1';
$secs = bw_time_of_day_secs();
$secs = 86400 - $secs;
$set_transient( ""bw_tides_title_"" . $store, $title, $secs);

}}}

but change line 1 as below and it works

$title = '''(string)''' $channel->item->title;

Two questions therefore. 
1. Am I misinterpreting the documentation that says I don't need to serialise the value? What does mixed actually mean.
2. Does set_transient have to crash when the parameters are wrong?

The problem is completely reproducable. I now have a working solution so I don't need a fix right now. I just want to understand.
Herb 

"	bobbingwide
Future Releases	23327	Cache incrementors for get_bookmarks()		Cache	3.5.1	normal	normal	Future Release	task (blessed)	new	early	2013-01-30T18:24:08Z	2013-04-16T17:11:33Z	"Make use of a caching incrementor and store queries in individual cache buckets to avoid memory exhaustion.

Pattern this after #23167, which does the same thing for get_pages().

See #23173 for an explanation of the motivation behind this."	ryan
Future Releases	23173	Don't cache arrays of query results in a single cache bucket		Cache	3.5	normal	normal	Future Release	task (blessed)	new		2013-01-10T19:05:17Z	2013-04-16T17:10:11Z	We have started using one cache bucket per query with passive invalidation controlled through a last_changed incrementor. See #22024 for an example. We also need to do this with get_pages(), wp_get_archives(), and elsewhere. On wordpress.com we have hacked some of these into separate buckets because saving multiple queries per cache bucket results in huge buckets. We have seen 72MB get_pages caches. Let's finally clean this up for good. Some of the last_changed work done for #22176 can be used here.	ryan
Future Releases	20388	?cpage=N URLs do not have canonical redirection		Canonical		normal	normal	Future Release	defect (bug)	new		2012-04-07T05:43:02Z	2012-05-22T01:07:50Z	?cpage=N URLs aren't redirected to their pretty URL counterparts. They should be.	markjaquith
Future Releases	22879	Canonical Link Missing on Front Page		Canonical	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-12-12T11:03:05Z	2012-12-30T19:54:30Z	"Canonical links are provided for posts, so if someone links to /2012/12/my-post/?whatever then Google will know it is a duplicate of /2012/12/my-post/

But if someone links to /?whatever there is no canonical address."	miqrogroove
Future Releases	14201	Canonical redirect kicks in in case of category/tag base containing other chars then a-z, 0-9, _ and -		Canonical		high	major	Future Release	defect (bug)	new		2010-07-05T09:03:39Z	2011-09-22T09:49:50Z	"'''Expected behaviour'''

Whatever the category base is, if we go to a properly formed category pretty permalink, canonical redirects shouldn't kick in.

'''Actual behaviour'''

If the category base is non-ASCII (for example: баба), the canonical redirect tries to redirect to the same URL. The redirect sanitizer removes the category base from the URL, because it is non-ASCII and redirects to {{{<root>//category-name/}}}. This prevents endless redirects and usually results in 404.

'''Why does it happen?'''

Category base is always used verbatim. It can't be URL-encoded, because the percent signs will be interpreted as permalink variables. Because of that the generated urls will be always in the form: {{{<root>/баба/<url-encoded-category-name>/}}}.

The contents of {{{$_SERVER['REQUEST_URI']}}} are always URL-encoded, so the requested URI is: {{{<root>/%D0%B1%D0%B0%D0%B1%D0%B0/<url-encoded-category-name>/}}}.

Canonical redirect functionality assumes the requested URL would be the same as the generated term URL and since they are different tries to redirect.

'''Solutions'''

The easiest one is to assume that if we had come to the right category page without any get variables, we don't need the logic for redirecting to the canonical category page. This is valid statement, because that logic relies only on removing get arguments.

The only disadvantage with that solution is that doesn't solve the more general problem of discrepancies between generated and requested URLs.  But for now it will do a good job."	nbachiyski
Future Releases	23074	Changing post's URL and then setting it back causes redirect loop		Canonical	3.5	normal	normal	Awaiting Review	defect (bug)	new	close	2012-12-29T00:44:50Z	2012-12-30T06:59:34Z	This morning, I changed the URL of one of my posts, but then changed my mind and set it back. When you change the URL of your post, WP automatically creates a redirect from the old page to the new page, which is good, but in this case it led to an unintended consequence: after I changed the link from A to B and then back to A, it set up a redirect from A to B and a redirect from B to A, causing anyone trying to access A or B to end up in a redirect loop between the two (or possibly it created a redirect loop from A to A; I'm not sure). It should check for such loops when you update the URL to avoid this problem.	vbuterin
Future Releases	23602	"Incorrect canonical redirect if p=123 query argument present in ""paged"" archives"		Canonical	3.5	normal	normal	Awaiting Review	defect (bug)	new		2013-02-25T08:34:19Z	2013-02-25T08:34:19Z	"URLs that include `page/n` AND `p=n` query variable, such as:

http://example.com/page/3/?p=123

will issue a 301 redirect to the homepage. This is being reported as incorrect behaviour in Google Webmaster Tools, because:

  The target URL does not exist and your server is not returning a 404 (file not found) error. 

  Your server is redirecting requests for a non-existent page, instead of returning a 404 response code. This creates a poor experience for searchers and search engines.

A fix would be to strip the `p=` query variable and redirect to the paged archive. 

From: 

http://example.com/page/3/?p=123

to:

http://example.com/page/3/
"	kasparsd
Future Releases	23408	Link to rss-feed in default installation causes redirect loop		Canonical		normal	major	Awaiting Review	defect (bug)	new		2013-02-06T21:20:04Z	2013-02-20T02:56:37Z	"I noticed, that google webmastertools complained about dead links in my blog.
Those links were hidden in the html-code and were links to rss-feeds of attachments. (e.g. ?attachment_id=1647&feed=rss2)
When i try to open the link, it returns a 301 error and if the new url is called, anoter 301 error is shown. After two or three times, the original url is shown again by a 301 error message.

I installed two clean installations on different servers, which show the behaviour either. If i use the link ""?attachment_id=1647&feed=rss""  the correct feed is loaded. (using rss instead of rss2 which is provided by the template)

It seems that the error is caused by the function get_post_comments_feed_link(...) in ""wp-include/link-template.php used wp-include/canonical.php.
When i add another line to the function to return a link with ""attachment_id="" and not ""p="" or ""page_id"", the comment feed is loaded without errors.
But the fact, that rss feeds do not cause an error and rss2 feeds create a loop makes me think, that another module may be defect and my workaround is not a solution.

Regards

Fabian"	clusterone
Future Releases	20383	Strip trailing punctuation with canonical URLs		Canonical		normal	normal	Future Release	defect (bug)	new		2012-04-07T03:59:49Z	2012-07-13T00:47:29Z	"A follow-up to #7537 where we removed %20 and "" "" from the end of URLs, we should try to remove all sorts of punctuation from the end of a URL, both URL-encoded and decoded.

Example bad URLs we should surely be able to resolve:

http://ma.tt/2012/03/productivity-per-square-inch/%7B

http://ma.tt/2012/03/productivity-per-square-inch/)

http://ma.tt/2012/03/productivity-per-square-inch/,

http://ma.tt/2012/03/productivity-per-square-inch/!

More difficult when there is no trailing slash in the permalink structure (or the link requested, regardless of permalink structure), but if is_404() is taken into account, it should be doable to trail various pieces of punctuation and see if we can get things to resolve."	nacin
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	20386	"Year permalinks ""win"" against category permalinks"		Canonical		normal	normal	Future Release	defect (bug)	new		2012-04-07T05:20:55Z	2012-07-16T04:14:43Z	"We need to decide whether category permalinks should take priority over year permalinks.

e.g. /2008/?category_name=cat-a

Should that stay the same, or redirect to:

/category/cat-a/?year=2008

We have a unit test which is failing."	markjaquith
Future Releases	17337	wp_old_slug_redirect() fails with multiple post_type query		Canonical	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-05-06T10:36:19Z	2011-05-06T10:36:19Z	"If I have a query something like this:

{{{
[query_vars] => Array
        (
            [name] => panasonic-tv-review
            [post_type] => Array
                (
                    [0] => review
                    [1] => small_review
                )
        )
}}}

The new post slug is ""panasonic-250-tv-review"", and there is a `_wp_old_slug` meta key with the old slug. One would expect `wp_old_slug_redirect()` to kick in and do the redirect. However, `wp_old_slug_redirect()` will fail with a query with multiple post types, (looking at http://core.trac.wordpress.org/browser/trunk/wp-includes/query.php#L3494). This will knock the `$wpdb->prepare()` ass `$post_type` is now an array. 

I can write a patch for this if I can get the go ahead."	joehoyle
Future Releases	18385	"Canonical redirections not suited for Queries with multiple query vars and ""pretty permalinks"" in general"		Canonical	3.2	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-08-12T09:05:03Z	2011-08-12T12:21:47Z	"When the Canonical code was originally written, it served it's purpose quite well. However, over the years the number of Query vars which can be used to access content via has increased, and so have the number of archive views. This has lead to increased complexity in the Taxonomy canonical code which has needlessly caused bugs.

What I'm proposing, is that it might be time to lay to rest the current `if.. elseif.. elseif..` style checks, It's not possible for 1 if branch to handle every single access point without duplicating another branch.

As a result, I've put a half-finished together alternate version of Canonical, It's based on tallying up which query vars have been used/accounted for and removing any duplicates.. It's certainly not the best, but it's fairing better with the unit tests so far.

{{{
Unit Testing: http://unit-tests.trac.wordpress.org/browser/wp-testcase/test_includes_canonical.php
Before: FF.......FFFF..FFF.....F......FFFFFF.F....F.....FF....FF...
 After: FF...........FFF..................FF..................F....
}}}

It's a work in progress, but it's worth considering IMO.

Attaching a diff, and the full file (since the diff is going to be rather unreadable in some sections)"	dd32
Future Releases	20283	Create new variable or function in $wp_query object to get canonical URL of any site's page		Canonical	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-03-22T14:42:36Z	2012-03-24T12:08:55Z	"For the sake of Search Engine Optimization it's recommended to set canonical URL inside <link rel='canonical'> tag in any site's page. Incorrect URL can exist in search engine index. For example: http://example.com?some_param=some_val&cat=3,4. URL points to categories with id equals 3 and 4, but we have another unnecessary parameter 'some_param'. It's malicious! We must set canonical URL to http://example.com?cat=3,4.
So It's advance to have canonical URL generated some way. I propose to set function or variable inside WP_Query class to retrieve canonical URL to any opened page.

In WP_Query we have variable WP_Query::query which consists of all necessary parameters for that propose. But we must use $wp_rewrites also.
Any thoughts?
"	egorpromo
Future Releases	21765	Redirect to canonical URL if URL has 'preview' parameter with any nonempty value and user not log in		Canonical	3.4.1	normal	normal	Awaiting Review	enhancement	new		2012-09-01T13:18:44Z	2012-09-01T15:15:07Z	"if any URL has nonempty GET-parameter 'preview' that there is noredirection to canonical URL.
If we have http://example.com?p={post_id}&post_type={post_slug}&preview=true there is no redirection to correct URL like http://example.com?{post_type}={post_slug} or like http://example.com/{post_type}/{post_slug} (if site has permalinks). This is bad for SEO and bad user experience. If user not log in there must be redirecttion."	egorpromo
Future Releases	20224	WordPress should always add a / at the end of URLs		Canonical	3.4	normal	normal	Awaiting Review	enhancement	reopened	close	2012-03-13T09:54:17Z	2012-03-14T12:36:36Z	"Users can change permalinks. They can add whatever they whant at the end of each url. For example :[[BR]]
- mydomain.com/myurl
- mydomain.com/myurl/
- mydomain.com/myurl.php
- mydomain.com/myurl.html
- mydomain.com/myurl.htm
- ...

There is a bug with search engines and empty URLs (mydomain.com/myurl). Google, Yahoo or Bing consider that it's not the same URl as mydomain.com/myurl/. They always try to add a / at the end of those URLs : it creates duplicate content for search engines that harms website visibility. For example, if a WordPress Blog uses /%postname% as permalink, Google is going to index both url:
- mydomain.com/myurl
- mydomain.com/myurl/

In order to correct this issue, WordPress should always add a / at the end of empty URLs (for example, without a / or without extension like .php, .asp, .html, ...)."	Confridin
Future Releases	18547	"Add rel=""nofollow"" to reply to comments link"		Comments	3.2.1	normal	minor	Awaiting Review	defect (bug)	reopened	close	2011-08-30T14:20:31Z	2011-09-01T14:56:00Z	"This is an easy problem to diagnose and fix. Basically, the reply to comment links all contain a query parameter—?replytocom—in the destination URL.

Google does a poor job of ""deciding"" whether or not these are unique URLs, and as a result, these URLs are often indexed. This leads to duplicate content issues, which leads to users bitching :D

Here's a sample of some search results where the ?replytocom query parameter resulted in a bunch of duplicate indexing:

[http://www.google.co.in/search?cx=c&sourceid=chrome&ie=UTF-8&q=site:callingallgeeks.org+replytocom+#q=site:callingallgeeks.org+replytocom&hl=en&prmd=ivns&filter=0&fp=1&biw=1366&bih=667&bav=on.2,or.r_gc.r_pw.&cad=b Google]

Thanks!"	pearsonified
Future Releases	19930	Add tabindex to Comment Submit button		Comments	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-01-30T14:54:21Z	2012-05-03T15:40:22Z	For accessibility reasons, it would be nice to be able to add tabindex to the comment form submit area.	wpsmith
Future Releases	22792	Cannot change name attribute of comment submit button		Comments	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-12-06T17:03:01Z	2012-12-06T17:20:24Z	"This prevents developers from using client-side validation, as the name attribute being set to ""submit"" interferes with the .submit() method.  I can change the id and the label of the submit button, but that is all.

The default WordPress server-side validation is unacceptable from a user-experience standpoint.

This would be the solution for me, which I find cumbersome (http://wordpress.stackexchange.com/questions/65001/error-when-posting-comment-form-the-error-is-typeerror-eh-is-not-a-function). 

The developer should be allowed to set the name attribute of the submit button (maybe through the use of comment_form())."	willi828
Future Releases	10377	Comment fields should have max lengths		Comments	2.8	normal	normal	Future Release	defect (bug)	new		2009-07-10T14:34:27Z	2012-07-13T01:05:25Z	"Hello, I don't know if exactly it's a bug or use javascript validation, but i think so there's no 	
treatment for this, or was fix in the new version.

In the section of comments(Wordpress 2.8), we can insert how many characheters we wants, generating an SQL Exception and breaking the all system.

The solution is simple, use the property maxlenght in the tag 
<input /> e limit the characters if will be send to database.



"	muriloazevedo
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	17714	Comment/pingback handlers don't check whether the post type supports comments		Comments	3.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-06-07T06:09:02Z	2011-06-07T06:17:45Z	"wp-comments-post and XML-RPC don't check post type support for comments before accepting them - I think they should. We can't rely solely on `$post->comment_status` because that may not always be set to ""closed"" even if the post type doesn't support comments (see also #13473)

Maybe we could add a check to `comments_open()`?"	solarissmoke
Future Releases	16976	Don't use photo as avatar class in comments		Comments	3.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-03-27T00:54:44Z	2011-03-27T01:07:30Z	"If you use an image in your post with class 'photo' to show it in Google's search results as a rich snippet is not possible if you make use of avatars in your comments. Google will pick the last class 'photo' image on the page to show as the search result.

Suggestion is to change the avatar class in comments to from 'photo' to 'comment-photo'. A post image is more important than a comment avatar to use for rich snippets."	Okoth1
Future Releases	14711	Indexes for comment_author_email and user_id		Comments	3.0	normal	normal	Future Release	defect (bug)	new	early	2010-08-27T07:18:30Z	2011-01-08T19:36:17Z	"There are currently no indexes on any of the author columns in wp_comments.  That means there's no efficient way to count the comments written by a given commenter, for example.

The enclosed patch adds two separate non-unique indexes, one each for comment_author_email and user_id.
"	tellyworth
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	21845	Losing comment reply by accidentally clicking on another comment		Comments	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-09-08T13:17:20Z	2012-09-17T22:31:50Z	"This is a usability bug.

When replying to a comment in the Edit Comments (wp-admin/edit-comments.php) page, double-clicking on another comment will open that comment for editing and wipe away the reply you were writing. 

If you want to highlight a word to copy from the comment that you are replying to this can be done by double-clicking the word. So completely by accident your reply is wiped out. This occurred on wordpress.com so I'm guessing their using the latest 3.4.2 version."	icc97
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	8755	Should be able to specify page order with wp_list_comments()		Comments	2.7	normal	major	Future Release	defect (bug)	new		2008-12-30T02:50:53Z	2009-11-17T15:48:45Z	"Passing the parameters ''reverse_top_level'' and ''reverse_children'' into the ''wp_list_comments()'' function only reverses the order of the comments '''on each page''', and not the entire comment list overall. It is therefore impossible to display the newest comments first using this function, when comments are great enough to be paged. At least, not without globally changing the comment order for the entire site using the Discussion settings screen so that the ""last"" page is displayed first.

It should be possible to specify the page order in wp_list_comments() by, for example, passing a page_order parameter with 'asc' or 'desc' available."	marky
Future Releases	16770	The comments field in the post table gets set to 'closed' for all posts, and commenting options change from those set		Comments	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-03-06T00:48:21Z	2011-03-06T17:25:27Z	"these problems are documented in this forum topic. http://wordpress.org/support/topic/why-is-my-comments-closed-in-all-posts-open-in-all-pages?replies=13#post-1768692 

It has happened to me twice"	linusinutah
Future Releases	15905	Using wp_list_comments using both the type and callback arguments causes the first comment to be repeated		Comments		normal	normal	Future Release	defect (bug)	new	close	2010-12-20T03:12:18Z	2011-01-27T07:01:44Z	"I'm using wp_list_comments like so: 

{{{
	<ol class=""commentlist"">
	<?php wp_list_comments('callback=comment_callback&type=comment'); ?>
	</ol>
}}}

When including the comments on a page listing many posts (like the home index page), the callback function is always passed the first comment that is encountered.  Trying get_comments before wp_list_comments shows the proper comments that should be displayed, but the callback always receives the same comment as it's argument.

Removing '&type=comment' yields the expected output.  My current workaround is to remove '&type=comment' and only respond to comments with an empty string for the comment_type in my comment callback function.
"	benschell
Future Releases	23369	WP_Comment_Query meta query 'count' conflicts with 'group by'		Comments	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-02T13:39:20Z	2013-02-02T14:52:54Z	"This problem relates to {{{/wp-includes/comment.php}}}, both 3.5.1 and trunk are affected. The following line number refers to the 3.5.1 version. 

At line 195, definition of class {{{WP_Comment_Query}}} , a typical meta query will generate such SQL:

{{{SELECT * FROM wp_comments INNER JOIN wp_commentmeta ON (wp_comments.comment_ID = wp_commentmeta.comment_id) WHERE ( comment_approved = '0' OR comment_approved = '1' ) AND comment_post_ID = 22 AND ( (wp_commentmeta.meta_key = 'my_flag' AND CAST(wp_commentmeta.meta_value AS CHAR) = 'my_value') ) GROUP BY wp_comments.comment_ID ORDER BY comment_date_gmt DESC }}}

Note that at line 357, a meta query will always generate a {{{GROUP BY}}} clause. This works for comment rows. Say that I've got 3 comments matching this query, I'll see each of them in a row:

{{{
comment row 1, data
comment row 2, data
comment row 3, data
}}}

However, this query doesn't work well then {{{$count = true}}}. Note that by specifying {{{$count = true}}}, the function only changes {{{'SELECT *'}}} into {{{'SELECT COUNT(*)'}}}. For 3 comment result, I'm seeing something like this:

{{{
1
1
1
}}}

And you can see, because there's a {{{'GROUP BY'}}} clause. And each comment has a unique ID. The result is 3 'grouped row' of comments, and each will always have count of 1.

Therefore, the result of {{{$wpdb->get_var()}}} will be either 1, or NULL (when nothing is matched). I believe this behavior is not by intention.

To get count working, {{{'GROUP BY'}}} clause must be removed when $count is true."	heshiming
Future Releases	4916	comment_type function doesn't return the comment type string		Comments	2.3	normal	normal	Future Release	defect (bug)	assigned		2007-09-06T07:41:30Z	2012-03-12T11:37:16Z	The comment_type function in comment-template.php only echoes string that explain the comment type. Sometimes we need the string to be returned instead of echoed, e.g. for i18n purposes.	hudatoriq
Future Releases	22635	comments made on iPad get the comment_author_url removed in the pre_comment_author_url filter		Comments	3.4.2	normal	major	Awaiting Review	defect (bug)	new		2012-11-29T14:21:04Z	2012-11-29T22:18:48Z	"I have tested this on version (3.5-RC1-22909) nightly build too.

if I submit a comment with a valid author url using the iPad then the URL gets removed by the pre_comment_author_url filter in wp-includes/comment.php 

'''works'''
* windows 7 works fine
* windows xp works fine
* debian box works fine
* macbook pro works fine

'''Not working'''
* iphone ios 5.1.1
* ipad ios 5.1.1

duplicable on local, live and someone elses site.

I can see the POST vars show all the proper data.

in wp-includes/comment.php the wp_filter_comment function the `$commentdata['comment_author_url']` exists before 

{{{
$commentdata['comment_author_url']   = apply_filters('pre_comment_author_url', $commentdata['comment_author_url']);
}}}

(line 1291 of wp-includes/comment.php (3.4.2)

but is gone after the filter has been applied,

this happens only if using an ipad or iphone.


"	commentluv
Future Releases	14809	comments_by_type doesn't always get reset		Comments	3.0.1	normal	minor	Future Release	defect (bug)	new	reporter-feedback	2010-09-08T01:18:20Z	2011-07-09T17:40:40Z	"in wp-includes/comment-template.php , in function comments_template(), it is possible for $wp_query->comments to be set but for $wp_query->comments_by_type NOT to get reset when it should be reset to array().  We ran into a bug because:[[BR]]
- on a single page (actually inside of a widget), we were pulling comments from multiple posts[[BR]]
- for each post, we were requesting get_comments(array('type' => 'comment'))[[BR]]
- in wp-includes/comment-template.php , in function wp_list_comments(), code says:
{{{
		if ( 'all' != $r['type'] ) {
			if ( empty($wp_query->comments_by_type) )
				$wp_query->comments_by_type = &separate_comments($wp_query->comments);
			if ( empty($wp_query->comments_by_type[$r['type']]) )
				return;
			$_comments = $wp_query->comments_by_type[$r['type']];

}}}
unfortunately, since we were running that again and again, it would not recalculate $wp_query->comments_by_type each time.

I think that the function comments_template() in wp-includes/comment-template.php should have the following line added:
{{{
     $wp_query->comments_by_type = array();
}}}
right after the line where $wp_query->comments is set."	nmassey
Future Releases	16010	get_comments()  returns as result (by default) comments that were not approved.		Comments	3.0.3	normal	normal	Future Release	defect (bug)	new		2010-12-28T16:41:11Z	2011-01-13T04:00:49Z	"I see two problems in behavior of ""get_comments()"" function (wp-includes/comments.php: 180).

1. The function returns as result (by default) comments that were approved and also comments that were not approved. 
I think that this does not fit the standard of all functions in WP that by default return only posts/comments that have been published/approved.

2. I think that there is no support of cookies of current responder. In other words, a parameter that allows the following functionality does not exist.
comment_approved = '1 'OR (comment_author =% s AND comment_author_email =% s AND comment_approved = '0')
( wp-includes/comments-template.php: 852)"	mati1000
Future Releases	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
Future Releases	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
Future Releases	19256	Ability to mark a comment as spam from the trash		Comments	2.9	normal	normal	Awaiting Review	enhancement	new		2011-11-16T03:07:48Z	2011-11-16T09:42:58Z	"Say you're scrolling through comments in the trash and you realize a comment should have ended up in spam instead.

There's no easy way to untrash then re-spam the comment — you'd lose it and it'd get restored to its previous status. You can't edit it and modify its status from there, either.

I think there should probably be a way to spam a comment from the trash. (For that matter, I don't think there's an issue with being able to edit a trashed comment, too. Perhaps you want to modify it then untrash/approve it.)"	nacin
Future Releases	20977	Add Dynamic Comment Statuses		Comments	3.4	normal	normal	Awaiting Review	enhancement	new		2012-06-15T17:12:07Z	2012-06-15T17:21:37Z	It would be great to add some filters/actions that would allow plugin developers to add additional statuses to comments.	supercleanse
Future Releases	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
Future Releases	21571	Add support multiple comment types in get_comments		Comments		normal	normal	Awaiting Review	enhancement	new		2012-08-14T00:49:42Z	2012-08-24T19:54:42Z	"Custom comment types are a nice way to categorize comments, however, if you wish to retrieve multiple comment types you cannot use ''get_comments''.  This enhancement request (patch attached) adds support for multiple comment types a la:

{{{
$comments = get_comments( array(
  'post_id' => $post->ID,
  'type' => array(
    'a-sweet-comment-type',
    'some-other-comment-type',
  ),
));
}}}"	borkweb
Future Releases	15520	Break date/time into a separate column in Comments views		Comments		normal	normal	Future Release	enhancement	new		2010-11-20T15:30:35Z	2012-03-08T10:18:38Z	"Now that column sorting is in, it makes sense to break the date and time a comment was made into a separate column in the Comments view so they can be sorted chronologically.

Currently, the time is part of the content column, which can be confusing as if someone sorts by that column it becomes an alphabetical sort."	markel
Future Releases	24489	Can't set comments to view in popup		Comments		normal	normal	Awaiting Review	enhancement	new		2013-06-03T22:50:43Z	2013-06-03T22:50:43Z	"add option in ""Discussion Settings"" page to view comments in a new window... 

"	alexvorn2
Future Releases	12521	Disable Site Wide Discussions - Admin Settings		Comments	3.0	normal	normal	Future Release	enhancement	new		2010-03-05T01:44:26Z	2011-08-27T08:42:14Z	In the admin discussions options there should be an option to completely disable discussions site wide.	ceenz
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	9775	Duplicate comment check is too strict		Comments	2.7.1	normal	normal	Awaiting Review	enhancement	reopened		2009-05-09T21:27:38Z	2012-08-19T23:33:35Z	"The duplicate comment detection mechanism doesn't allow duplicate comments on the same post, even from the post author. That's not good.

The duplicate comment check should only block the new comment if there is no other comment posted between the new comment and the old comment."	scribu
Future Releases	10869	Eliminate moderation on admin comments		Comments		normal	normal	Future Release	enhancement	new		2009-09-28T10:18:53Z	2009-11-28T12:34:10Z	"Currently, if comment moderation is enabled, comments left by the admin are also moderated, requiring approval before they're posted.  

Proposed change: If comment moderation is activated, all replies and comments left by the admin are auto-approved."	heather_r
Future Releases	13857	Email notifications lack a link to the comment, from address could be improved		Comments		normal	normal	Future Release	enhancement	new		2010-06-11T21:27:24Z	2010-10-28T01:47:17Z	"'''Email Notification'''
For the 6+ years I believe I have been using WordPress, the emails that notify me someone has made a comment have several links in them.

'''Fields within an email notification'''
Email, Url, Whois, Comment, All Comments, Delete, Spam

The comment, at least in plain text emails, contains html markup, which often is encoded making it hard to read, depending on the comment complexity.  I suggest a simple strip_html style function be ran on the comment copy.

The link to the comments only takes you to the comments, but does not add in the identifier in the url to take you to that specific comment.  The blog I am managing has 30+ comments on each page, making it harder than it should be to get to the comment and reply.

An example of a better method might be:
http://example.com/foo-bar-baz/#comment-7348
Compared to:
http://example.com/foo-bar-baz/#comments
----
'''Email Headers'''
The From header in the email is is correctly set to the ""Name"" value the user filled into the comment form, the email address is set to wordpress@example.com where example.com is the domain of the site.

However, the reply-to header is correctly set to the actual sender.  Bounces (NDR's) and the cosmetic view of an email could all be improved with a simple condition:

{{{
if is_valid(emaIl) then
  from = name & ' <' & email & '>'
  reply-to = from
else
  // looks like they did not set the data
  // fall back to some sane defaults
end if
}}}


"	hexley
Future Releases	23800	Filter Comment Blacklist, to delete duplicated terms		Comments		normal	normal	Awaiting Review	enhancement	new		2013-03-16T23:37:13Z	2013-03-16T23:37:13Z	"Hi,

In Comment Blacklist, when I save terms, duplicates are not eliminated.

Would be good if the function array_unique would remove these duplicate terms."	shadowhck
Future Releases	23797	Hard coded HTML marking in comment_form()		Comments	3.5.1	normal	normal	Awaiting Review	enhancement	new		2013-03-16T21:16:23Z	2013-03-17T14:50:58Z	"Hello

it seems so ugly hard coding has slipped in the comment form. 

On line 1554 of comment-template.php, there is some hard-coded html :
 {{{
<h3 id=""reply-title"">
<?php comment_form_title( $args['title_reply'], $args['title_reply_to'] ); ?>
<small><?php cancel_comment_reply_link( $args['cancel_reply_link'] ); ?></small>
</h3>
 }}}

Semantically speaking, a H3 is far from being optimal. 
Also, filters exists for all other elements of the comment form. 
The h3 and small should not be hardcoded. 

A new value could be included in the defaults : 

 {{{
'comment_reply_markup' => 
    '<h3 id=""reply-title"">%1$s <small>%2$s</small></h3>',
 }}}

and line 1554 replaced by : 

 {{{
<?php printf( $args['comment_reply_markup'], 
comment_form_title( $args['title_reply'], 
$args['title_reply_to'] ), cancel_comment_reply_link( $args['cancel_reply_link'] ); ?>
 }}}

Thanks a lot, hope you'll take it :)"	Marie-Aude
Future Releases	12392	Move comment fields to meta data instead		Comments		normal	normal	Future Release	enhancement	new		2010-02-26T20:09:24Z	2012-07-16T04:19:52Z	"Look at the comment table:
{{{
CREATE TABLE $wpdb->comments (
  comment_ID bigint(20) unsigned NOT NULL auto_increment,
  comment_post_ID bigint(20) unsigned NOT NULL default '0',
  comment_author tinytext NOT NULL,
  comment_author_email varchar(100) NOT NULL default '',
  comment_author_url varchar(200) NOT NULL default '',
  comment_author_IP varchar(100) NOT NULL default '',
  comment_date datetime NOT NULL default '0000-00-00 00:00:00',
  comment_date_gmt datetime NOT NULL default '0000-00-00 00:00:00',
  comment_content text NOT NULL,
  comment_karma int(11) NOT NULL default '0',
  comment_approved varchar(20) NOT NULL default '1',
  comment_agent varchar(255) NOT NULL default '',
  comment_type varchar(20) NOT NULL default '',
  comment_parent bigint(20) unsigned NOT NULL default '0',
  user_id bigint(20) unsigned NOT NULL default '0',
...
}}}
A lot of that is not actually being used on many sites and could be moved to standard meta data, available on demand, but not pulled out by default.

Specifically:

comment_author_IP - Used by Akismet and blacklist functions, included in emails sent to post authors/moderators, but once stored in the DB it's never really used again.

comment_karma - Used by some of the importers as a space to store temporary data. Not actually used by core for anything serious anywhere.

comment_agent - Used by Akismet and blacklist functions, but once stored in the DB it's never really used again.

These could be pushed to meta and thus still made available, but without them being in the main table.

This is a long term change, because some plugins would likely break. So the columns should be deprecated for a while first.
"	Otto42
Future Releases	17951	Move or duplicate comment actions at top of each comment row		Comments		normal	normal	Awaiting Review	enhancement	new	close	2011-06-30T17:29:35Z	2013-01-21T23:31:29Z	"When I attempt to take an action on a comment and the comment is EXTREMELY long, it takes a while to get to the SPAM link since it's at the bottom of the comment.

This ticket is to simply propose moving the actions to the top, rather than the bottom of the comment. Or perhaps duplicate the actions there, since they are only visible on hover anyway."	chriswallace
Future Releases	20490	Move submit_button to wp-includes for frontend inclusion & use with comment-template.php		Comments		normal	normal	Awaiting Review	enhancement	new		2012-04-19T18:04:55Z	2012-04-23T14:43:09Z	"It would be nice to be able to use submit_button() on the frontend as well (cf. #15064). It appears that #16066 ""fixed"" #16061, which it did, but moving the submit_button functions would enable to revert back to the use of submit_button(). Moreover, I recommend changing the comment-template.php in wp-includes ([http://core.trac.wordpress.org/changeset/16066#file2 16066#file2]) to use a filter with the submit_button to enable attributes like onClick. As it stands right now, if a user wants to track comments in their analytics they have to hide the original and add a function hooked into comment_form and redo all the args."	wpsmith
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	23179	New avatar related option - use gravatar  only for registered users		Comments		normal	normal	Awaiting Review	enhancement	new		2013-01-11T15:40:59Z	2013-01-21T04:42:39Z	"The use of gravater is problematic because there is no attempt to verify that a comment with which an email was used was actually left by the owner of the email (AFAICT gravatar doesn't even have an API for authentication).

This makes impersonating to someone else that have a gravatar in a wordpress site comments much too easy. 

IMO non autogenerated gravatars should be displayed by default only for users for which it is known that they actually own the email address, which are usually only the registered users."	mark-k
Future Releases	22889	Reconsider no-JS ?replytocom= links		Comments		normal	normal	Awaiting Review	enhancement	new		2012-12-12T15:13:20Z	2012-12-14T13:05:31Z	"We have a no-JS fallback for comment replies. Normally JS moves the comment form around. For people with JavaScript disabled, they follow the `?replytocom={123}` link. This results in a lot of extra crawling by search engines (potentially an additional crawl per reply-able comment!) in exchange for enabling an awkwardly executed, likely underused, and non-essential feature for non-JS users.

I'd like to consider making comment reply JS-only."	markjaquith
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	3842	Should make nofollow implementation cleaner and easier to remove		Comments	2.1.1	normal	normal	Future Release	enhancement	new		2007-02-22T10:08:56Z	2011-07-23T06:44:21Z	"{{{rel=""nofollow""}}} didn't appreciably stop comment spam, and there are many arguments for why it is a '''bad''' idea (and not just a failed idea).  We should consider axing it."	markjaquith
Future Releases	16576	comment_form() fields being displayed only for non logged in users		Comments	3.0.5	normal	normal	Awaiting Review	enhancement	new		2011-02-16T18:15:44Z	2011-10-19T23:28:16Z	"I've just noticed this - When using the '''comment_form()''' function and adding some comment meta fields,using the fields array in the $args, these fields are being showed in the front-end only for non logged in users.
In this case, the registered users can never use these comment fields.

Look at wp-includes/comment-template, lines 1561-1573 (WP 3.0.5), it parse the $args['fields'] in the else block - 

{{{
<?php if ( is_user_logged_in() ) : ?>
	<?php echo apply_filters( 'comment_form_logged_in', $args['logged_in_as'], $commenter, $user_identity ); ?>
	<?php do_action( 'comment_form_logged_in_after', $commenter, $user_identity ); ?>
<?php else : ?>
	<?php echo $args['comment_notes_before']; ?>
	<?php
	do_action( 'comment_form_before_fields' );
	foreach ( (array) $args['fields'] as $name => $field ) {
		echo apply_filters( ""comment_form_field_{$name}"", $field ) . ""\n"";
	}
	do_action( 'comment_form_after_fields' );
	?>
<?php endif; ?>
}}}

I think it is better that added meta fields should be displayable for all users (logged in and not logged in), or even to add a parameter to let the developer decide which extra fields are shown to logged or not logged users.


"	maorb
Future Releases	14510	comment_notes_before does not work.		Comments	3.0.1	normal	normal	Future Release	enhancement	reopened		2010-08-02T18:39:34Z	2011-02-18T04:51:54Z	"I am unable to get the comment_notes_before to work.

Using the code:

{{{
comment_form(array( 'comment_notes_before' => 'some text' ));
}}}

... does not work.  it just leaves the default text there.

{{{
comment_form(array( 'comment_notes_after' => 'some text' ));
}}}

... does work.  It allows you to put whatever text you want."	hotforwords
Future Releases	19903	wp_count_comments() and get_comments_count() both do SQL queries		Comments	3.3.1	normal	normal	Future Release	enhancement	new		2012-01-26T22:16:42Z	2012-04-18T20:35:04Z	"{{{wp_count_comments()}}} and {{{get_comments_count()}}} are similar functions, with a few differences:

* Their results are returned in different formats:
 * {{{wp_count_comments()}}} returns an object of:
  * spam
  * approved
  * moderated
  * total_comments
  * trash
  * post-trashed
 * {{{get_comment_count()}}} returns an array of:
  * spam
  * approved
  * awaiting_moderation
  * total_comments
* {{{wp_count_comments()}}} caches, but {{{get_comment_count()}}} always hits the database.
* {{{get_comment_count()}}} is used nowhere in WordPress core.

I propose that we add 'trash' and 'post-trashed' reporting to {{{get_comment_count()}}}, and then have {{{wp_count_comments()}}}  use {{{get_comment_count()}}} instead of doing its own SQL queries.

See #6884 and #19901"	markjaquith
Future Releases	20025	Add a filter for post types when viewing list of comments in the backend		Comments	3.3.1	normal	normal	Awaiting Review	feature request	new		2012-02-12T14:03:49Z	2012-02-12T14:38:23Z	Filtering comments based on post type	nprasath002
Future Releases	12223	Adding a titles to comment levels with the walker class		Comments		normal	normal	Future Release	feature request	new		2010-02-14T11:20:07Z	2010-02-14T17:52:36Z	"Hi Everyone! 

This is only my second post here, and my first feature request, so please excuse me if I have duplicated something or my solution is completely unsuitable. 

I am experimenting with the CMS capabilities of Wordpress, especially the enhanced post_type GUI in the new 3.0 alpha release. While building a sort of Yahoo Answers type platform, I wanted to have 1st level comments as answers to a question (a post), and 2nd level comments as comments on the answer (1st level comments). I wanted to label comments on an answer as ""comments"", but this is not really possible to do, to my knowledge, using ""wp_list_comments"".

I created my own function for wp_list_comments so I didn't have to modify Wordpress core, in order to get at the walker class at the bottom of wp_list_comments. I wanted to use start_lvl to add a title for comment level 2. However, start_lvl in ""class Walker_Comment extends Walker"" will only let you change the list type to ""ul"", ""ol"" or ""div"". My idea is to add an argument which would allow you to add a title, along with specifying it's heading (or surrounding tag). As I said, I am not an expert on Wordpress coding standards, so the following code may be completely off. 

{{{
/**
   * @see Walker::start_lvl()
   * @since unknown
   *
   * @param string $output Passed by reference. Used to append additional content.
   * @param int $depth Depth of comment.
   * @param array $args Uses 'style' argument for type of HTML list.
   * @param array $args Uses 'title' argument for title text.
   * @param array $args Uses 'title_heading' argument for title text heading level.
   */
	

function start_lvl(&$output, $depth, $args) {
  $GLOBALS['comment_depth'] = $depth + 1;
  
    switch ( $args['style'] ) {
      case 'div':
        break;
      case 'ol':
        echo ""<ol class='children'>\n"";
        break;
     default:
     case 'ul':
        echo ""<ul class='children'>\n"";
        break;
    }
	
	if (!empty ($args['title'])) {
	  
      if(!empty ($args['title_heading'])) {
	    echo '<'.$args['title_heading'].'>';
	  }
	  
	  echo $args['title'];

	  if(!empty ($args['title_heading'])) {
	    echo '</'.$args['title_heading'].'>';
	  }
	
	}
	
}
}}}"	danielpataki
Future Releases	18417	Comment whitelist in discussion settings		Comments		normal	normal	Awaiting Review	feature request	new		2011-08-15T18:48:46Z	2011-08-17T09:49:25Z	"Currently, there are methods for automatically flagging comments for moderation or blacklisting comments, but there's no way to auto-approve comments that meet a certain criteria.

In Discussion Settings, it would be nice to have ""Comment Whitelist"" option to automatically approve comments from a specific IP address, using a specific email address, or matching certain keywords.

One use case: a conference or workshop where lots of people are posting comments from the same IP address often invokes the ""Slow down, you're posting too fast"" message. Instead, we should be able to add the IP address to the whitelist (possibly temporarily) so that everyone can comment without hitting the restriction.

The concern I can think of is that this would add another large paragraph box to the Discussion Settings view."	danielbachhuber
Future Releases	18630	Custom Comment Validation Error		Comments	3.3	normal	minor	Awaiting Review	feature request	new		2011-09-09T19:49:33Z	2012-04-04T18:16:21Z	"One of the things that bugs me about WordPress is not being able to customize the wp_die() function that is called on comment form validation. I have seen some people sugget core hacks, eek. I'm hoping that a hook is added to allow overriding of the default wp_die(). Maybe even a new template file wp_error.php that would be called first. 

I haven't found a lot of discussion on this in trac just #11286 and #10551"	bandonrandon
Future Releases	19621	Cron not working in WP 3.3		Cron	3.3	normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2011-12-20T12:15:32Z	2012-04-23T21:15:31Z	"Hi,

I was working on wordpress cron and found that the cron doesn't synchronize the times even when the traffic is visiting site pages. The script works fine WP 3.2.1

Please check this. I believe wp-cron.php is not run in this latest release. "	hassanasad
Future Releases	8923	cron timeout is too short		Cron		normal	normal	Future Release	defect (bug)	reopened	reporter-feedback	2009-01-22T23:50:57Z	2011-09-21T17:13:46Z	"Many users have reported  that 2.7 cron sometimes fails to publish future post. 
And it is further reported that it depends on the number of jobs on the cron queue - when the queue is too long, it will miss some. 

I believe this is because we set the timeout value too short: 

wp_remote_post($cron_url, array('timeout' => 0.01, 'blocking' => false));

When making a request to wp-cron.php, it won't return until all cron jobs are executed.  And 0.01 is just too short time span. It doesn't hurt to give it sufficent time, such as 10 minutes. It will return as long as the mature crons are fired up and executed (in most cases, it's going to be at most a few seconds ). 
"	hailin
Future Releases	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@…
Future Releases	17957	wp_reschedule_event & daylight saving		Cron	3.2	normal	normal	Awaiting Review	enhancement	reopened		2011-07-01T09:03:28Z	2013-04-11T23:18:10Z	"When a recurring event is established using the WP cron functions the function takes a Unix timestamp and a recurrence interval.

In the situation where daylight saving changes the local time, the timing of an event can change by an hour. So, if a database backup is set to run at midnight when the clocks change this can start to happen at 11pm or 1am instead since the timing of the event is based on an initial static time (Unix timestamps reference point is January 1, 1970) and a static interval period.

An enhancement to the cron functions would be to account for an obey daylight saving changes so that events schedule for midnight actually occur at midnight irrespective of the time of year."	MattyRob
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	23383	High archive page numbers cause invalid database queries		Database	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-02-04T20:36:30Z	2013-02-05T13:46:24Z	"Visiting `http://www.viper007bond.com/category/videos/page/6805063692754011230` on my site generates the following database query:

`SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (21) ) AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'private') GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 6.805063692754E+19, 10`

Note the scientific notation `LIMIT` value.


PHP: 5.3.15-pl0-gentoo[[BR]]
MySQL: 5.2.12[[BR]]
WordPress: r23386
"	Viper007Bond
Future Releases	18210	Update_post_meta is case insensitive on meta_key, but get_post_meta is NOT		Database	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-07-22T07:05:28Z	2013-02-28T16:06:54Z	"In WordPress 3.3-aortic-dissection and 3.2.1

get_post_meta is case sensitive on the meta-key

BUT

update_post_meta is NOT case sensitive

Thus If there is a pre-existing meta record with a key in say UPPERCASE, then one can issue an update for a lowercase key that one can not then fetch as it does not exist - only the uppercase key exists. 


Example Code

{{{

	$meta = get_post_meta ($post->ID, '_allday');
	if ($meta ) { echo '<br />got lower: '; var_dump($meta);
	}
	$meta = get_post_meta ($post->ID, '_ALLDAY');
	if ($meta ) { echo '<br />got upper: '; var_dump($meta);
	}
	update_post_meta (21, '_allday','Tried to update lowercase');
	$meta = get_post_meta ($post->ID, '_allday');
	if ($meta ) { echo '<br />got lower: '; var_dump($meta);
	}
	else { echo '<br />Tried to get lower but no go';
	}
	$meta = get_post_meta ($post->ID, '_ALLDAY');
	if ($meta ) { echo '<br />Still have upper: '; var_dump($meta);
	}


}}}



Output of above:



got upper: array(1) { [0]=> string(14) ""tis the upper."" }
Tried to get lower but no go
Still have upper: array(1) { [0]=> string(25) ""Tried to update lowercase"" } "	anmari
Future Releases	22408	wp_insert_attachment and _real_escape input validation and better error handling		Database	3.4.2	normal	trivial	Awaiting Review	defect (bug)	new	dev-feedback	2012-11-10T21:47:03Z	2012-11-10T21:49:25Z	"Recently when using the `wp_insert_attachment()` function I passed the whole result of the `wp_check_filetype()` function for the `""post_mime_type""` attribute, instead of the `""type""` property from the filetype check result. What I got was an error in the `_real_escape()` function which expected a string, but received an array, which didn't quite help me find my error.

I believe some kind of type checking would be nice for both the `_real_escape()` function as well as the `wp_insert_attachment()`.

It seems suitable if the `wp_insert_attachment()` function returned a `WP_Error` object in case there are issues with the passed arguments.

I'm not sure, however, what the best solution would be for the `_real_escape()` function -- return false, fail quietly, raise an exception or also return a `WP_Error`.

I would have proposed a patch, but I'm not sure what solution to implement. Let me know if I should do it in a certain way and I'll submit a patch for review, saving you a little time for other ticket review."	magadanski_uchen
Future Releases	9642	Database Schema Optimizations		Database	2.8	normal	normal	Future Release	enhancement	assigned		2009-04-24T19:42:40Z	2013-02-16T16:15:57Z	Diffs coming...	Denis-de-Bernardy
Future Releases	18105	Improve JOIN efficency of tax_query		Database		normal	normal	Awaiting Review	enhancement	new		2011-07-14T04:28:59Z	2012-06-04T23:40:00Z	"Use of multiple items in a tax_query creates an inner join for each entry. This seems unnecessary.

Example query:

{{{
array(
  'tax_query' => array(
    'relation' => 'OR',
    array('taxonomy' => 'tax1', 'field' => 'slug', 'terms' => 'term1'),
    array('taxonomy' => 'tax2', 'field' => 'slug', 'terms' => 'term2'),
  )
)
}}}

Resulting SQL:

{{{
SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts  
INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) 
INNER JOIN wp_term_relationships AS tt1 ON (wp_posts.ID = tt1.object_id) 
WHERE 1=1 AND
...
AND (wp_term_relationships.term_taxonomy_id IN (XXX) 
  OR tt1.term_taxonomy_id IN (YYY) ) 
...
}}}

Each new entry in the array creates another inner join on the term_relationships table, along with an associated select argument.

However, the term_relationships table is defined with these main keys:

{{{
CREATE TABLE $wpdb->term_taxonomy (
 term_taxonomy_id bigint(20) unsigned NOT NULL auto_increment,
 term_id bigint(20) unsigned NOT NULL default 0,
 taxonomy varchar(32) NOT NULL default '',
...
 PRIMARY KEY  (term_taxonomy_id),
 UNIQUE KEY term_id_taxonomy (term_id,taxonomy),
}}}


This basically means that the term_taxonomy_id is a unique ID for the row, and it's pointing to a unique relationship between some term and some taxonomy. Essentially, term_relationships defines what terms are in what taxonomies.

Therefore, the extra inner join and selection are entirely unnecessary. All references to a term in a taxonomy are unique. This isn't individual terms we're looking for in this query, but term+taxonomy. 

An equivalent SQL statement to the one given before would be this:

{{{
SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts  
INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) 
WHERE 1=1 AND
...
AND (wp_term_relationships.term_taxonomy_id IN (XXX, YYY) ) 
...
}}}

This is equivalent because both XXX and YYY point to a specific term+taxonomy combination, not just to a term.

For the similar relation = AND case (instead of relation = OR), this query would be equivalent:


{{{
SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts  
INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) 
WHERE 1=1 AND
...
AND (wp_term_relationships.term_taxonomy_id IN (XXX) 
AND (wp_term_relationships.term_taxonomy_id IN (YYY) ) 
...
}}}

We get a second statement in the where clause, but note the lack of a second inner join and lack of referencing it. This greatly improves performance. 

Only one inner join is ever actually required for any number of items in the tax_query, thanks to the pre-lookups being performed to find the proper term_relationship entries.

Similar enhancements might be available for the meta table, however that is more complex and may be more difficult to improve.
"	Otto42
Future Releases	21212	MySQL tables should use utf8mb4 character set		Database	3.4.1	normal	minor	Awaiting Review	enhancement	reopened		2012-07-11T04:26:12Z	2012-10-09T06:56:41Z	"Historically, the MySQL utf8 character set has only supported the first character plane of UTF-8. With MySQL 5.5.3, it now supports the entire character plane, using the utf8mb4 character set. This character set is 100% backwards compatible, and does not require more space than utf8 for characters that fall within the utf8 set, only using an extra byte for characters outside of the utf8 set.

References:

http://en.wikipedia.org/wiki/Mapping_of_Unicode_character_planes [[BR]]
http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html"	pento
Future Releases	22884	What if I delete wp_posts table from database.		Database	3.5	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-12-12T12:48:24Z	2012-12-13T11:51:20Z	"I am not a experienced or mature programmer but I have seen it While I was playing with database of WordPress.

I have deleted wp_posts table in database in WordPress - 3.5(beta).

It looks normal on other pages at admin side but when i open single post it shows post-new.php and when hit save, it shows ""wp_error"" with this message ""You are not allowed to edit this post.""

That's OK. I was expecting error but not this type of error.

It seems WordPress doesn't know that its most important table has gone away and that's why admin may not know( well for a while). I think its not good. well I don't know its issue or it is way it behaves with database and its normal but I think WordPress should know what exactly happened.

when I have updated WordPress with stable 3.5 it has updated but database is still same which is normal.

Should we( can we )track tables( some of tables which are important ) by PHP ?"	mukkundthanki
Future Releases	22196	add $wpdb->upsert function		Database	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-10-15T12:48:33Z	2012-10-15T14:53:24Z	"If i read http://codex.wordpress.org/Class_Reference/wpdb right, we have only insert and update functions, but for many occations, if would be lovely, if we would have upsert function as well (using INSERT ... ON DUPLICATE KEY UPDATE http://dev.mysql.com/doc/refman/5.1/en/insert-on-duplicate.html).

So when i am inserting e.g. posts using database function, i do not have to check if post with that id exist (good for some migration / importing tools etc.)"	thomask
Future Releases	23061	get_post_meta() on post with large amount of meta keys uses too much memory		Database		normal	normal	Awaiting Review	enhancement	new		2012-12-27T13:40:17Z	2012-12-27T14:54:48Z	"I think it's likely there has been a ticket on this in the past, but I couldn't find one so here goes!

If I have a post that have say 25k post meta entries, and I call `get_post_meta( $id, 'foo', true )` then `update_meta_cache` is going to cause all post metas to be loaded into memory.

In most cases I can see this makes sense, however I recently had an issue where I was storing contest votes as meta keys, a post had 30k votes, and would take about 70MB of memory to get any meta key of that post (even if I didn't want votes). This is fairly edgecase, but the idea that all meta for a post is always loaded even if you don't want it is perhaps over presumptuous as a dev may be storing a large amount of data in meta.

With persistant object caching this is somewhat worse, as the object cache store gets very large. 

I am not proposing this functionality is removed, maybe just a filter or something in http://core.trac.wordpress.org/browser/trunk/wp-includes/meta.php#L524 so one could either adjust the query or perhaps pass an array of meta keys to exclude from the sql query"	joehoyle
Future Releases	21055	Interface for wpdb compatibility		Database		normal	normal	Awaiting Review	feature request	new		2012-06-23T17:30:13Z	2012-08-24T01:40:01Z	"==Summary==

From the wp-includes/wp-db.php file:
{{{
It is possible to replace this class with your own
by setting the $wpdb global variable in wp-content/db.php
file to your class. The wpdb class will still be included,
so you can extend it or simply use your own.
}}}

When one implements a db class that does not extend wpdb, it would be safer that the new class implements an interface. This interface may be called wpdb_compat and would assure that the class has all necessary methods/properties. Of course, wpdb_compat should be supported by wpdb too.

== Design Strategies ==

My patch adds:
* wp-includes/interfaces/wpdb-compat.php

Very small edits to:
* wp-includes/wp-db.php
* wp-includes/load.php
* wp-admin/install.php

At the moment, WordPress does not include any interface; this means that there is not a directory for interfaces.[[BR]]
In my first draft, I put it in wp-includes/interfaces so that - if more interfaces will be added in the future - they will have a logical place.
"	santec
Future Releases	22194	PHP x64 compatibility issue with date values		Date/Time		normal	major	Awaiting Review	defect (bug)	new		2012-10-15T09:39:11Z	2012-10-15T10:36:05Z	"Hi,

seems like WordPress is using the ""0000-00-00 00:00:00"" value as magic value for date values, which aren't set instead of NULL.

This is working fine for any PHP x86 builds, because the magic value is also an invalid date.

But PHP x64 builds support this value. It is no longer invalid. It is now a valid date! This will result in problems, because some functions are expecting that parsing this date will return false, but now on x64 systems they won't get an invalid date, when they are expecting one.

So the problem is, that WordPress is using a valid date as magic value for an invalid date aka default value.

Fixing this issue will require a SQL schema change and to update all the code, checking for ""0000-00-00 00:00:00""...

For references, see ticket #21987 and https://bugs.php.net/bug.php?id=53662"	Whissi
Future Releases	23203	Scheduling Posts assumes GMT but UI uses local timezone (creating undesired scheduled posts)		Date/Time	3.5	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2013-01-15T15:32:09Z	2013-01-16T13:16:59Z	"I experienced an odd behavior when going to edit a page on a newly created site in a multisite environment. The site uses the New York timezone (GMT-5).

When quick-editing the page, I changed the title and slug, but pressing ""Update"" set the page as ""Scheduled"" rather than leaving it ""Published"". This was very confusing, and took a while to figure out and then explain to the end user. It seems that although the date/time is shown in the UI in the current time zone, once submitted the form interprets the time as if it were in GMT. To the end user, it looks like the page should be published since the time shows what we thought was a 5 minutes ago. In reality, the time in the date field is not recognized as 5 minute ago but 4 hours and 55 minutes in the future.

This is a problem in the full edit form for pages in this newly created site as well. When I go to edit the published time/date, the posted time in my timezone is shown. However, ''even if I hit 'Cancel' the ""Update"" button changes to ""Schedule""''."	bananastalktome
Future Releases	20973	date_i18n() produces invalid output for shorthand formats		Date/Time	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-06-15T13:39:50Z	2013-04-04T16:36:54Z	"date_i18n() function relies on parsing passed format to make adjustments. However shorthand formats are not handled and produce invalid output.

Example:

{{{
var_dump( date_i18n( 'Y-m-d\TH:i:sP', time() ) ); // 2012-06-15T13:34:03+03:00 << ok
var_dump( date_i18n( DATE_W3C, time() ) ); // 2012-06-15T13:34:03+03:00 << ok
var_dump( date_i18n( 'c', time() ) ); // 2012-06-15T13:34:03+00:00 << broken time zone!
}}}


Hook-level fix:

{{{
add_filter( 'date_i18n', 'fix_c_time_format', 10, 3 );

function fix_c_time_format( $date, $format, $timestamp ) {

    if ( 'c' == $format )
        $date = date_i18n( DATE_W3C, $timestamp );

    return $date;
}
}}}

See [http://wordpress.stackexchange.com/q/54700/847 Why time functions show invalid time zone when using 'c' time format?]

Possibly related (can't say for sure from description) #13538"	Rarst
Future Releases	19813	Keyboard shortcuts for editing posted date		Date/Time	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-01-12T09:28:13Z	2012-01-12T17:39:31Z	"In short, I thought it would be a nice feature to be able to use the Up/Down arrow keys to increment or decrement the values within the post published date/time input boxes. I found this stackoverflow post with the basics of how to retrieve keystrokes and alter the value based on which one was pressed. 

http://stackoverflow.com/questions/7742364/incrementing-value-integer-in-an-input-type-field.

I then altered the code to prevent negative numbers and stay within the limits of each field type.

Days get 1-31
Year gets 1900+
Hours get 0-23
Minutes get 0-59

JS could probably be cleaned up a bit and condensed, but I wasn't quite sure how to separate them all out. Maybe someone with more js-fu can help out with that"	tw2113
Future Releases	19849	Pass $comment_date to get_comment_time filter		Date/Time	3.3.1	normal	minor	Awaiting Review	enhancement	new		2012-01-17T17:50:50Z	2012-01-17T17:50:50Z	"I was writing a function to customize the formatted time to include the timezone in the comment meta data using the get_comment_time filter. In order for me to properly indicate whether daylight savings time was in effect at the time of the comment, I needed to globalize $comment to get the comment_time property. The filter passed the $date variable which is the formatted time part of the timestamp but not the $comment_date variable which contained the entire timestamp from $comment. In the function I developed, the $date string wasn't used at all. I returned the formatted time string from $comment->comment_date directly. 

Since get_comment_time() already establishes $comment_date, why not pass it to the filter as well?"	lexhair
Future Releases	15921	date column filter in media list table		Date/Time	3.1	normal	normal	Future Release	enhancement	new		2010-12-20T18:25:49Z	2011-03-23T17:08:18Z	"please add a filter for date column in media list table, like posts list table.

in wp-admin\includes\class-wp-media-list-table.php @ line:288
replace:
{{{
<td <?php echo $attributes ?>><?php echo $h_time ?></td>
}}}

with:
{{{
<td <?php echo $attributes ?>><?php echo apply_filters( 'media_date_column_time', $h_time); ?></td>
}}}"	gonahkar
Future Releases	24369	"""Open link in a new window/tab"" shows the wrong information"		Editor	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-05-19T23:55:56Z	2013-05-19T23:55:56Z	"I noticed that the ""Open link in a new window/tab"" checkbox in Wordpress' editor sometime shows the wrong information. I can get this consistently by:

1/ writing a post in word, including links inserted in Word

2/ copy the text to WP's editor

3/ links will be converted from Word in clean HTML and will open in the same window by default

4/ select the first link and open ""Insert/Edit Link"" by clicking on the Link button. The first time, the box will be unchecked. That's correct.

5/ change that first link to ""Open link in a new window/tab"". click on Update

6/ go to the next link and open ""Insert/Edit Link"" again. Oh no it shows the ""Open link in a new window/tab"" checked while the HTML code shows that it is NOT targeted to ""_blank"".

Example: WP's editor says that this will open in aa new window: http://screencast.com/t/rxR6oeEjL

Bur the HTML is clear: it's not targeted to ""_blank"": http://screencast.com/t/xDBnYsh9Z

Thank you,"	hubertnguyen
Future Releases	20609	<p> tags  in Editor not working on editing with wp_editor, wenn disabling media_buttons or quicktags		Editor		normal	normal	Awaiting Review	defect (bug)	new		2012-05-03T16:36:01Z	2012-05-05T01:01:57Z	"When disabling the media_buttons or quicktags via the third argument in wp_editor via a settings array, <p> tags are not displayed any more, so there are no line breaks any more in the editor. Only ""      "" is in the source code. The Problem also occurs, when changing 'quicktags' or 'media_buttons' in class-wp-editor.php in the core to false. wpautop is still true.

"	julian42
Future Releases	19947	Copy paste behavior in Visual mode differs from HTML mode		Editor		normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-02-02T13:13:11Z	2012-02-02T13:13:11Z	"Copy a random html page from a random site including links and images and paste it into the WYSIWYG Editor Visual mode and it will include the images and links. Basically it (mostly) looks like the copied page. If you paste the same into the WYSIWYG Editor HTML tab and it will strip out _all_ HTML markup and just leaves the plain text, without the images or links.  

Expected: 
I would expect the Visual and HTML mode of the WYSIWYG editor to behave the same, either both use the code (displaying the results of the markup code in the Visual tab and the markup code itself in the HTML tab) or both strip out all html.   

"	BjornW
Future Releases	22185	Distraction Free Writing mode lacks any controls on touch devices		Editor	3.2	normal	normal	Awaiting Review	defect (bug)	new		2012-10-13T22:39:05Z	2013-01-10T00:30:44Z	"Distraction Free Writing mode on touch devices is pretty disastrous. All the controls disappear, meaning you can't apply any formatting and - more importantly - you can't save your content or exit fullscreen mode.

Not sure what would be best:
 1. Don't autohide the controls at all on touch devices.
 2. Autohide the controls but add a toggle button which shows up on touch devices to toggle the controls on again.
"	johnbillion
Future Releases	18627	Google Chrome handles bulleted lists differently in Visual Editor than other browsers		Editor	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-09-09T16:10:51Z	2011-09-09T16:10:51Z	"In Firefox (working functionality):

1. create brand new post or page
2. in the visual editor, click Bulleted List icon
3. In Format menu choose H1
4. Type some text (it's inside a ul >> li >> h1)
5. Press Enter

Result: a new bullet, and we've lost the H1 style (just inside a ul >> li now)

Try this with Chrome 13.x

1. create a brand new post or page
2. in the visual editor hit the Bulleted List icon
3. in the Format menu choose H1
4. Type some text (it's inside a ul >> li >> h1)
5. Press enter

Result: no new bullet. We're inside a ul >> li >> div

Also tested in IE 7 and 8 (works fine). haven't tried other WebKit browsers."	tomauger
Future Releases	11986	HTML comments in post/page content get wrapped in P tags		Editor	2.9.1	normal	normal	Future Release	defect (bug)	new		2010-01-23T19:32:13Z	2010-06-14T01:39:31Z	"I don't know if someone already caught this i had mentioned it to someone in the #chat but

When you write a post or a page and include comment html tags

the comments end up being wrapped in <p> tags

<p><!-- comment --></p>

An older plugin i use makes use of comment tags to know where to insert content but comments may be used for other reasons inside posts.

the more comments you add
the more line breaks errr paragraph breaks 

additionally the plugin I was using could not pickup the comment tag and insert the content.


"	NPSites
Future Releases	16116	Hide 'Move to Trash' for auto drafts		Editor	3.0	normal	normal	Future Release	defect (bug)	new	dev-feedback	2011-01-06T05:54:59Z	2013-01-22T16:52:51Z	"The 'Move to Trash' link should not appear for auto-drafts. 

This was the original intent of what [13905] removed, which I want to say was designed to reflect additional scenarios."	nacin
Future Releases	22996	IE8 - Hierarchical Taxonomies with bulk terms cause massive slow-down / freeze		Editor		normal	minor	Awaiting Review	defect (bug)	new	dev-feedback	2012-12-18T19:18:02Z	2013-01-06T08:07:28Z	"For a project, we have about 550+ terms in a single taxonomy, the other taxonomies have around 10-40 each themselves too. There appears to be an issue when IE8 comes across too many checkboxes on a page, and this recently was exacerbated by an upgrade to WP 3.5. The upgrade itself didn't cause it, but it coincided with the addition of a few new terms (don't know how many were added before the upgrade just yet, will post if I find out more info).

To reproduce, you've gotta have a large amount of terms for your taxonomies, then go into the post editor (for whatever post type you're testing on), and ensure your taxonomies have 'hierarchical' set to true in their definitions. I've seen the issue crop up on save (on subsequent load of the page w/ success message on it), and on open of the edit page itself.

The issue seems to be more severe for IE8 on Windows XP Service Pack <= 1, but I've seen it cause a massive slow-down for newer XP versions, just not freeze up entirely like it did on the XP SP 1 machine I was primarily testing on.

''I'm not really sure'' what the solution is going to have to be here, or if this will serve merely as a paper-trail for the folks searching for information about this.

I did a blanket forceful change for checkbox input to autocomplete on the meta boxes associated to hierarchical taxonomies using the following Gist to resolve the freezing for now:

https://gist.github.com/4330772

Here's the info you'll probably ask for, I went down to the basics to see exactly what the cause was:

1. No plugins activated (except a small plugin that had the Gist in it to resolve the issue for me)

2. Standard Twenty Twelve theme activated

3. Tested and found the issue happening on both WP 3.4.x and WP 3.5

4. Tested on XP SP 1 with IE8, saw the greatest degradation of performance here

5. Tested on XP SP 3 with IE8, saw a noticeable freeze and then slow-down of performance as the page loads here"	sc0ttkclark
Future Releases	19645	Image caption gets removed when editing image dimensions.		Editor	3.3	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-12-22T16:24:34Z	2011-12-23T18:25:53Z	"When editing an image placed into a post in a certain way, the caption of the image is removed.

Steps to reproduce:
1. Edit a post that contains an included image.
2. Click the edit options icon when selecting the image.
3. Go to the advanced image settings(make sure the image does have a caption).
4. Empty the width field.
5. Press the submit button.
-> The caption of the image is set empty.

Remarks,
In my case only leaving the width input field blank caused this issue."	JanJaapKempenaar
Future Releases	23103	Non image caption shortcode lost when switching from text to visual editor and back		Editor	3.4	normal	normal	Awaiting Review	defect (bug)	new		2013-01-02T16:40:25Z	2013-02-13T05:56:05Z	"1. Add the line in text editor 
{{{
[caption caption=""test"" width=""300""]Checkuot this text[/caption]
}}}

2. switch to visual editor 

3. switch back to text and you get 
{{{
<dl class=""wp-caption alignnone"" id="""" style=""width: 310px;""><dt class=""wp-caption-dt"">Checkuot this text</dt><dd class=""wp-caption-dd"">test</dd></dl>
}}}
"	mark-k
Future Releases	13327	Post editor puts content through wpautop() before displaying it to users without JS enabled		Editor	3.0	low	normal	Future Release	defect (bug)	new		2010-05-10T21:42:50Z	2010-11-12T11:24:54Z	"'''Steps to reproduce:'''

 1. With JS on, change to the Visual Editor
 2. Disable JS
 3. Add a new post
 4. Save as draft
 5. Note that the content is wrapped in {{{<p>}}} tags in the textarea.

[[Image(http://img19.imageshack.us/img19/6363/screenshot20100510at524.png)]]

'''Expected:'''

No paragraph tags are added."	markjaquith
Future Releases	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
Future Releases	14749	Scrollbar position jumping in the Appearance->Editor newcontent textarea		Editor	3.0.1	normal	normal	Awaiting Review	defect (bug)	new		2010-09-01T01:32:10Z	2012-11-01T05:14:52Z	"As I am editing code in the Appearance Editor main textarea called newcontent, the scrollbar slider will jump upward to a new position moving the current line being edited down.

On a vista machine using ie8 with wp3.0.1 and the 2010 theme, a single character stroke will move the scrollbar up 3 lines.  

On an xp machine using ie8 with wp3.0.1 and a custom theme, a single character stroke will move the scrollbar up 8 lines.  Ocasionally the scrollbar will only move 1 line and every keystroke will bring the down.  Pasting text can and often does bring the line being edited below the visible area of the textarea.

It is very frustrating when it jumps around like this."	Giant Slayer
Future Releases	21311	"The ""Paste as plain text"" feature in TinyMCE produces double-line breaks between paragraphs."		Editor	3.4.1	normal	minor	Awaiting Review	defect (bug)	new	close	2012-07-19T10:41:13Z	2012-07-20T08:44:55Z	"Mac OSX Lion, Chrome, WordPress 3.4.1

See attached SWF for a screen-video demonstration.

 • In WP-Admin -> Posts -> Add new, with the editor in visual mode, click the ""Pase as plain text"" icon [[BR]][[BR]]
 • Paste your content into the window that pops up and click ""Insert"" [[BR]][[BR]]
 • Note that two paragraphs seem to be double-line breaked. [[BR]][[BR]]
 • Switch to HTML mode and note that there are extra ""&nbsp;"" spaces inserted between paragraphs. [[BR]]

 "	uxtremist
Future Releases	21460	The accesskeys in Quicktags don't work in all browsers		Editor		normal	normal	Awaiting Review	defect (bug)	new		2012-08-03T19:21:56Z	2012-08-03T22:01:43Z	"IE (Alt+letter) works properly. Firefox (Alt+Shift+letter) only focuses the corresponding Quicktags button sometimes. Doesn't perform the action. If the button is hidden, performs the action (this shouldn't happen in Quicktags). Chrome doesn't seem to do anything. Opera works differently: Shift+Esc brings a list of all defined access keys on that page. The Quicktags access keys are not listed there.

"	azaozz
Future Releases	21934	Title field on Insert/edit link form shouldn't allow autosuggest		Editor	3.4.2	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2012-09-19T21:10:18Z	2012-09-20T22:37:44Z	"When entering a link through the ""Insert/edit link"" thickbox form, Firefox displays autosuggest dropdowns for both the URL field and the title field.

This would be helpful, except that the javascript keyboard handlers bound on keydown/keyup prevent the browser UI from being accessible.

What happens is:

1. User tries to add link to text through the editor (Visual or HTML).
1. User enters the correct URL into the URL field, and exits that field by hitting ""tab"".
1. User begins typing the link title. Firefox browser UI helpfully suggests some similar titles.
1. User sees a title they'd like to use, and hit the keyboard down arrow, thinking that this will select the correct title for them.
1. What actually happens is that the first link listed below in the link to existing content gets selected. This overwrites what's been entered in the URL and title field.
1. User says, WTF just happened.

Solutions:

- Adding `autocomplete=""off""` to these two form fields would prevent Firefox from displaying its autosuggestions. This might fix the problem, but feels kind of like a bandaid.

- A keydown/keyup handler could be attached to each of the text input fields with event.stopPropagation could stop the ui keyboard behavior when typing into those fields."	goldenapples
Future Releases	18946	Too long tags make the cross not moving anymore.		Editor	3.2.1	normal	minor	Awaiting Review	defect (bug)	new		2011-10-14T13:13:48Z	2011-10-22T13:29:27Z	"If you have a long tag like a long title of a book or movie title or game title and you more the cross doesn't move with the tags.

Look to the screenshot for more info"	jonezjea
Future Releases	21853	Unable to Add Whitespace After Hyperlinks		Editor	3.3.2	normal	major	Awaiting Review	defect (bug)	new		2012-09-09T06:22:43Z	2012-09-09T15:10:02Z	"This bug seems to have developed somewhere after version 3.1.

To reproduce this bug:

1. Start a new post or page.
2. Click the HTML tab.
3. Paste this snippet:

{{{
<ul>
	<li><a href=""http://www.google.com/"">Parent item</a>SPACEME
		<ul>
			<li>Child item</li>
		</ul>
	</li>
</ul>
}}}

4. Click the Visual tab and note how the hyperlink runs up against the word ""SPACEME"".
5. Click the HTML tab.
6. Add a space before ""SPACEME"".
7. Click the Visual tab.
8. Like magic, the space has vanished! :(

Curiously, I am unable to reproduce this behavior if I add the space on the Visual tab rather than the HTML tab.  Very buggy!"	miqrogroove
Future Releases	24161	Updating long post quickly could result in post truncation		Editor	3.5.1	normal	critical	Awaiting Review	defect (bug)	new		2013-04-23T00:45:20Z	2013-04-23T02:30:41Z	"I've observed a bug yesterday when updating a 10,000 word post frequently while testing another feature. The last update ended up eating almost half of the post at the end and went unnoticed until today when it was pointed out by users.

I've examined the update history and indeed found the last update to not contain a good portion of the post - it just cuts off.

The only explanation I have for this behavior is that because the post is so long, the update button was pressed while the textarea field was still loading, which interrupted the loading process and submitted whatever was loaded at the time. This is very dangerous - a race condition like that could demolish long posts or posts on slower connections.

A solution here should be a validation function that makes sure the post was loaded before the Update button is clickable. Perhaps just tie the onload to the Update button so it's disabled until the browser confirms things are loaded. I'm open to other suggestions, but I'm now definitely scared of one of the authors or myself accidentally truncating content."	archon810
Future Releases	24439	WP3.6-beta3 deletes <dd> tags		Editor	trunk	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-05-28T09:00:42Z	2013-05-28T17:20:17Z	"I just installed nightly WP3.6-beta3 and I activated Twenty Thirteen theme because I wanted to test chat post format.

I pasted the following demo content and all <dd> tags are stripped no matter what I do:

{{{
<dl>
	<dt><cite class=""fn"">M</cite>: </dt>
	<dd>Too many free radicals. That’s your problem.</dd>
	<dt><cite class=""fn"">M</cite>: </dt>
	<dd>Yes. They’re toxins that destroy the body and the brain, caused by eating too much red meat and white bread and too many dry martinis!</dd>
</dl>
}}}
"	Looimaster
Future Releases	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
Future Releases	23382	WordPress admin panel lags		Editor		normal	normal	Awaiting Review	defect (bug)	new		2013-02-04T19:02:20Z	2013-05-20T00:01:32Z	"I'm using Windows 7, brand-new laptop with i7 processor, 8GB RAM and 1080p resolution.

I have created a post with 15 1920x1080 images in it and a lot of content (25000 characters). Results:

=== CHROME & CHROME CANARY ===
It's far from being usable at all. It lags that much that cursor doesn't even change from ""default"" to ""pointer"" when I hover over ""Publish"" button. Even switching to WordPress Admin Panel tab takes 5 seconds. Textareas are not resizable because lags prevent my mouse cursor from doing anything. Actually, entire Admin Panel lags, all these Drag&Drop widgets etc.

=== FIREFOX ===
A bit better than Chrome, everything lags but at least I can resize textareas and after 10 seconds it becomes usable. Nonetheless, it's not as smooth as other websites.

=== IE10 ===
Excellent. Not even a single slowdown!

=== SAFARI ===
Very close to IE10.

I think that WordPress Admin Panel is stuffed with heavy Javascript. Maybe it's worth taking a look at that. The module that seems to be the heaviest is TinyMCE - when this appears then lags appear as well. Chrome works fine everywhere except WP Admin Panel.

Good luck guys and thank you for your hard work during WordPress development :) My complaints are here only to make it better. I can live with these lags (since I can do it in IE10) but those are just my thoughts (many people use Chrome)."	Looimaster
Future Releases	23332	iPad Can't Move Cursor in Visual Editor		Editor		normal	normal	Awaiting Review	defect (bug)	new		2013-01-30T23:13:50Z	2013-02-11T23:33:20Z	"I've been ramping up iPad usage with WordPress both for mobility as well as testing.

The more I use it, the more frustrated I become with the visual editor.  Due to what appears to be multiple bugs with both iOS and WordPress, I am often unable to move the cursor and must switch to the Text tab to do my editing.

When tapping into the Visual editor in a long post, the screen auto scrolls so that the cursor is sitting directly above the keyboard, and the admin bar moves to the middle of the page, covering most of the remaining editing area.  This blocks the view of any preceing or following text, and makes it very awkward to write sentences longer than the editor is wide.

To move the cursor to a different part of the post, I have to un-focus the editor and the tap into the editor on a different line.  The only place I can reliably land the cursor is at the end of a line, so to change anything in the middle of a paragraph, I have to use the text editor."	miqrogroove
Future Releases	23321	ins button in text editor produce semantically different HTML then the U button at the visual editor		Editor		normal	minor	Awaiting Review	defect (bug)	new		2013-01-30T06:54:51Z	2013-01-30T06:54:51Z	"U button at the visual editor makes something like 

{{{
<span style=""text-decoration: underline;"">text</span>
}}}

while the ins at the text editor makes

{{{
<ins datetime=""2013-01-30T05:44:49+00:00"">text</ins>
}}}

It is actually not easy to understand that the intentions behind both are equivalent - underline the text*, but semantically they have different meaning, and in the context of WP usage the styling one has probably the more correct meaning.

Alternatively, if ""ins"" is important html tag then why it is not possible to add it in the visual editor.

related #20149

*Browsers by default underline ""ins"" but twentyeleven and twentytwelve remove it."	mark-k
Future Releases	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
Future Releases	18979	Add $post_type parameter and a filter to meta_form()		Editor		normal	normal	Awaiting Review	enhancement	new		2011-10-18T03:55:56Z	2012-04-01T12:29:54Z	"In the current version, meta_form(), the function which outputs Custom Fields form used in Edit Post pages, shows all meta keys you have used regardless of post type. Sometimes this gives users unwanted options.

I'd like to suggest adding $post_type parameter to meta_form() to show only meta keys you have used in the same post type. In addition, it would be better if there were a filter for the meta keys."	takayukister
Future Releases	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
Future Releases	23339	DFW in HTML mode should have switch text direction button for RTL languages		Editor		normal	normal	Awaiting Review	enhancement	new		2013-01-31T12:22:55Z	2013-02-01T19:14:02Z	It is hard to edit HTML when the flow of the text is right to left. The normal HTML editor has this button when used in RTL environment.	mark-k
Future Releases	20237	Default editor needs support for non-DFW fullscreen mode		Editor	3.3.1	normal	minor	Awaiting Review	enhancement	new	close	2012-03-14T23:13:51Z	2012-12-27T22:54:22Z	"There's currently no way to change whether or not to use distraction-free-writing (DFW) mode for the default WYSIWYG editor. When inserting a new editor via the wp_editor() function, you can pass 'dfw' => false as one of the settings arguments; but in 'edit-form-advanced.php', the editor is hard-coded to use DFW.

Many people prefer to make layout and styling adjustments in full-screen view, so it seems strange to have this preference hard-coded. Recommend adding an option to Settings > Writing to select between DFW and classic full-screen."	danblaker
Future Releases	20186	Default font in the Visual Editor doesn't work well in all languages		Editor		normal	normal	Future Release	enhancement	new		2012-03-06T20:41:53Z	2012-05-02T20:25:57Z	As the title. This is somewhat unnoticed as most themes seem set the fonts there with editor-style.css. However we would need a default that works well for themes that don't set that.	azaozz
Future Releases	17388	Distraction free writing mode submit button text		Editor	3.2	normal	normal	Awaiting Review	enhancement	new		2011-05-12T12:11:09Z	2011-05-12T12:11:09Z	"The text on the submit button in distraction free writing mode should match that of the submit button on the main editing screen. Currently it always says ""Update"" for published posts, and ""Save"" for other statuses. It should say ""Save Draft"", ""Save as Pending"" etc when relevant (and change when you change the post status dropdown too)."	johnbillion
Future Releases	24047	Line numbers in post editor text mode?		Editor	3.5.1	normal	normal	Awaiting Review	enhancement	new		2013-04-11T17:48:32Z	2013-04-11T22:23:28Z	"I would love to see line numbers in the post editor when in text mode. This and/or the cursor returning to the editing point when updating a post.

It can be very annoying that the cursor always returns to the top of the editor when a manual update is initiated. Making a lot of small edits in various parts of a longish post can be really tedious."	dgwyer
Future Releases	18245	Make the visual editor KSES filter/user capabilities aware		Editor		normal	normal	Future Release	enhancement	new		2011-07-25T18:11:21Z	2011-08-23T20:16:45Z	"Currently the visual editor assumes ""unlimited html"" for all users. This can result in some surprises when a user doesn't have that capability.

We can make a function that translates the KSES allowed tags and attributes into TinyMCE format and sets the editor accordingly."	azaozz
Future Releases	22412	Save posts via Ajax		Editor	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-11-11T12:18:09Z	2012-11-12T09:39:16Z	"When editing a post/page (as with any other type of document) one of the primary benefits is the undo/redo feature.

However, as soon as you update your changes you lose access to undo your previous keystrokes before the update. If you could save posts via Ajax then you would still be able to undo/redo post edits seamlessly.

Perhaps there could be a toggle in general settings for this option, and have it enabled by default?"	dgwyer
Future Releases	18943	Scroll back to previous editor position after post save/update		Editor	3.2.1	normal	normal	Awaiting Review	enhancement	new		2011-10-14T10:23:05Z	2012-09-21T14:38:47Z	"I work exclusively in html mode in the WordPress editor, but this probably applies to the visual mode too.

When editing long(ish) posts it is really frustrating that the cursor position defaults to the beginning of the post after saving/updating.

Constantly having to manually scroll back down to the previous cursor position after updating, soon gets really tedious.

Focus always seems to be returned to the post title text box after saving/updating a post. It would be more intuitive to return focus to the main editor instead and automatically jump to the previous cursor position."	dgwyer
Future Releases	23630	Simplify the DFW implementation		Editor		normal	normal	Future Release	enhancement	new	early	2013-02-26T16:44:57Z	2013-03-06T20:04:42Z	"I was sad to see that distraction free writing [http://make.wordpress.org/core/2013/01/08/wordpress-3-6-distraction-free-writing-improvements/#comment-7469 didn't get picked up] for 3.6.  I decided to play around with a rough proof of concept to see how difficult it would be to use the existing TinyMCE instance for DFW.

Benefits of handling it this way include:

- It eliminates the need (and complexity) of juggling multiple instances of TinyMCE
- We'll be able to remove a bunch of the old DFW code
- It makes the transition between regular mode and DFW mode much more smooth
- It can be as fully featured as we want it to be"	lessbloat
Future Releases	15139	Texteditor: link button always enabled		Editor		normal	normal	Future Release	enhancement	assigned		2010-10-17T08:27:06Z	2012-01-06T01:32:10Z	"When you make a link you are forced to write the text in the editor and select the text before the link button is usable. I have seen users fail to understad this and getting stuck at creating links.

It might be better if the link button was enabled as default and if no text was selected a textfield with the link text appeared in the insert/edit link.

Another alternative is that the link text textfield (just mentioned) is visible all times but if text is selected it's written there by default. Otherwise it's left blank."	olalindberg
Future Releases	22154	The 'More' tag placeholder looks terrible		Editor		normal	minor	Awaiting Review	enhancement	new		2012-10-10T20:12:36Z	2012-10-11T05:17:18Z	Really, it does.	johnbillion
Future Releases	20309	Visual Editor: Editor styles overwrite FF minimum font size settings when a small size is set		Editor	3.4	normal	normal	Awaiting Review	enhancement	new		2012-03-27T14:08:50Z	2012-03-27T14:08:50Z	"This issue can be found when using Minimum font size accessibility settings in Firefox, instead of the Zoom settings.

* When editor-style.css defines a specific font size, the text in the visual editor cannot be made smaller than this font size.
* If I set the default font size to a bigger value than the one set in editor-style.css, it works.

Could we change this, so that all contents in the dashboard always fit the minimum font size defined in FF, whether that size is a small value or a big one?

Possibly related: #12825"	hd-J
Future Releases	18222	Visual clue after saving in fullscreen edit mode		Editor		normal	minor	Awaiting Review	enhancement	new	close	2011-07-22T19:45:00Z	2011-07-23T08:09:24Z	"You can save your current state while writing an article in fullscreen edit mode by pressing Ctrl+S.

However, there is no visual indication after this that the article has been saved or while saving.

This should be added."	mathbr
Future Releases	21649	_WP_Editor class is currently marked as final		Editor		normal	normal	Awaiting Review	enhancement	new		2012-08-21T13:13:08Z	2012-08-21T17:16:30Z	"Revision [19420] turned

{{{
class _WP_Editors{}
}}}

from wp-includes/class-wp-editor.php into 

{{{
final class _WP_Editors{}
}}}

I'm aware that editor API is currently under large changes but it would be great if plugins could extend _WP_Editors class by removing ""final"" keyword."	Marko-M
Future Releases	23323	img quicktag is so inferior to add media, should be merged or removed		Editor	3.5	normal	normal	Awaiting Review	enhancement	new	close	2013-01-30T09:55:50Z	2013-01-30T20:16:31Z	"Right now, in the text editor there are two ways to add an image, with the ""img"" button or the ""add media"" button. ""Add media"" contains all the functionality of ""img"" and adds much more, while ""img"" is ugly and feels like an historical artifact.

IMO ""img"" should be deleted or be an alias to ""add media"""	mark-k
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	22180	"Add attachments to ""existing content"" area in link dialog"		Editor	3.4	normal	normal	Awaiting Review	feature request	new		2012-10-12T20:59:26Z	2012-11-13T01:30:57Z	"At the moment, the process for linking to attachments within the editor is rather cumbersome. Each time someone wants to link to a PDF document or other item they've uploaded through the media interface, they have to take the following steps:

1. Upload the file through the media uploader
2. Press the File URL button in the media modal
3. Copy the URL from the ""Link URL"" box
4. Close the media modal
5. Highlight the text they want to link
6. Press the ""Insert/edit link"" button in the editor toolbar
7. Paste the URL from their clipboard into the URL input

It would be nice if attachments could be included in the ""Link to existing content"" area within the link dialog.

I can see two possible ways of implementing this. Either simply include attachments in line with the pages, posts and custom post types that already display in that area; or, use a tabbed interface to switch back and forth between the normal ""existing content"" list and a list of existing attachments.

When I discussed this with Nacin and a few others at WordCamp Baltimore, we proposed adding a preference (possibly based on the information that's stored when the user uploads the media) determining whether the permalink leads to the attachment page or the actual file.

Based on my preliminary research, it looks like implementing this will essentially take two steps:

1. Add 'attachment' to the `$pts` array at the beginning of the `_WP_Editors::wp_link_query()` method.
2. If the preference has been set to link to the actual file, the code will need to adjust the `permalink` value in the `$results` array for anything that comes up as an attachment.

I'll look at starting a patch for this over the next few days, unless someone else gets to it first. Thanks."	cgrymala
Future Releases	21188	Fullscreen (distraction-free) editor should have a preview button		Editor		normal	normal	Awaiting Review	feature request	new		2012-07-08T08:36:00Z	2013-01-08T14:01:54Z	"Per http://alexking.org/blog/2012/07/06/wordpress-fullscreen-preview-button

I do find it annoying to have to exit fullscreen, preview, then flip back to fullscreen."	markjaquith
Future Releases	19109	Want display fullscreen button only html editor mode.		Editor	3.2.1	normal	normal	Awaiting Review	feature request	new		2011-11-02T03:18:48Z	2011-11-02T03:37:55Z	"v3.2.1 writing fullscreen mode is display button both visual mode and html mode or visual mode only.

I want to display html mode only button. Want the following specification.

1. visual mode and html mode
2. visual mode only
3. html mode only <- new

Regards."	tatsuya
Future Releases	11489	iTouch useability in the editor out of the box		Editor	2.9	low	minor	Future Release	feature request	new	dev-feedback	2009-12-19T03:47:58Z	2013-02-01T11:37:40Z	"I have tried to write a post in 2.9 in iPod Touch and the text zone has some problems:

* When you write the title, if you want to write the post the keyboard doesn't appear. You must move to another text-editable zone and go back to the main text zone to have the keyboard. 

* Once you have the keyboard, you have capslock activated and cannot deactivate it (you can deactivate letter-per-letter). 

I have tried in 2 different iTouchs with the same result. 

I put it as low because WordPress has an iPhone/iTouch app and don't know if happens the same in other mobile platforms. "	bi0xid
Future Releases	23776	"A string of text starting with ""http://"" turned into a paragraph"		Embeds	2.9	normal	normal	Awaiting Review	defect (bug)	new		2013-03-14T21:11:00Z	2013-03-15T07:10:14Z	"
In either editor, if there's a line of text that starts with http:// wordpress will create a new paragraph.

This description box isn't working to show what I mean see this support post.

http://wordpress.org/support/topic/a-string-of-text-starting-with-http-turned-into-a-paragraph"	winterstreet
Future Releases	24395	Remove PollDaddy oEmbed support -- PollDaddy no longer supports oEmbed		Embeds	trunk	high	normal	Awaiting Review	defect (bug)	new		2013-05-23T16:31:41Z	2013-05-23T17:16:29Z	"After some befuddling experiences, I contacted PollDaddy to ask why their oEmbed support was not working, since it's built-in.  Polldaddy confirmed for me that they no longer support oEmbed:

{{{
Hi,

Wordpress has polldaddy oEmbed support hard-coded to look for your oEmbed
provider at http://polldaddy.com/oembed/, but it looks like that page is
currently a 404. This is making bad things happen for lots of people
worldwide using wordpress and trying to embed polldaddy polls. 

If you could look into this, that'd be great. 

Hi Justin,

We've not supported oEmbed for over a year now. If you want to embed a 
Polldaddy poll you will need to use our WordPress plugin, or one of the other
Polldaddy embed methods.

Thanks,
-- 
John Godley
Automattic | Polldaddy | WordPress.com

-- 
john
}}}

Thus, attached is a patch to remove polldaddy support from core. "	justinph
Future Releases	24296	Viddler oembed has new endpoint, old one strips maxwidth		Embeds		normal	normal	Awaiting Review	defect (bug)	new		2013-05-09T17:34:41Z	2013-05-09T17:34:41Z	"Viddler changed their oembed endpoint:

http://developers.viddler.com/documentation/oembed/

Now it's ""http://www.viddler.com/oembed/"" instead of ""http://lab.viddler.com/services/oembed/"".

They have the old endpoint redirecting, but unfortunately, the redirection strips off the maxwidth (and possibly other) parameters, which can result in incorrectly sized videos when using oembed with Viddler.

Example:
http://lab.viddler.com/services/oembed/?url=http://www.viddler.com/v/bdce8c7&format=json&maxwidth=250

Redirects to:
http://www.viddler.com/oembed/?url=http://www.viddler.com/v/bdce8c7&format=json

We should change the endpoint in class-oembed.php to the new one. If the new endpoint is used directly, with no redirect, then it does correctly handle the maxwidth parameter.
"	Otto42
Future Releases	23395	Video elements removed after revision		Embeds	3.5.1	normal	critical	Awaiting Review	defect (bug)	new		2013-02-05T14:19:40Z	2013-02-05T14:19:40Z	"Users have been reporting that when they make a revision to an article that includes embedded videos, their updated version removes all YouTube embed videos. This is occurring from both Text & Visual editor views. Restoring a previous revision does not resolve the issue. This also happens when ""previewing"" a post prior to publish. 

Site with issues: http://porchdrinking.com

Thanks!
- Chris"	chris_pd
Future Releases	24124	YouTube embed fails silently		Embeds	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-18T14:43:39Z	2013-04-18T14:43:39Z	"I have never been able to get the YouTube embed to work by [embed] or just quoting the URL. I tried finding out why today, and tracing through what the code does, I find it times out trying to fetch JSON for the oEmbed data via php-cURL from YouTube. (In fact I think it is the DNS lookup that is particularly slow here, but I don't think it makes much difference where the cause is, and it seems to fail not just on the server I'm developing on, but also on other servers). It consistently takes about 7 seconds for YouTube to reply on the system I'm testing on, and I see the timeout is 5 seconds. Now I know what the problem is I have added a filter to increase the timeout.

The biggest problem though is that it fails quietly. There is no error message on saving a post. Secondly, it behaves randomly and marginally - sometimes it works, sometimes it doesn't, depending on the load at YouTube presumably.

I think the author should at least be told their post has failed and why. However, if the timeout is consistently too low, there is then no way to make it work, without changing PHP code in a much more knowledgeable way than a typical user.

Ideally, you'd then offer the opportunity to repost with a larger timeout. If this were available, then the post could be refused publication until it works.

Just increasing the default timeout globally isn't a good solution, as saves will appear to hang, and I don't really know what side effects that might have elsewhere."	frankieandshadow
Future Releases	14759	Improve the way oEmbed deals with caching		Embeds	3.0.1	normal	normal	Future Release	enhancement	new		2010-09-01T23:47:30Z	2013-03-15T07:57:59Z	"As Matt pointed to me today, caching oEmbed results to post meta is kinda lame.

I originally did this because I didn't want the HTML in old posts changing on it's own, say for example if the oEmbed provider got compromised. However I think that's extremely unlikely since we only whitelist major websites that can be trusted.

Perhaps instead we should use transients to cache this data. That way when embed HTML is updated, posts will eventually be updated too due to expiring caches. I'm thinking a cache time of a week would be good, but with some random +/- to make sure multiple caches don't all expire at once.

A good example of this is Vimeo. Anyone who embedded a Vimeo embed in their post before a few weeks ago got `<object>`-based embeds. However now Vimeo gives out `<iframe>` based ones. The only way currently to update the old embeds to the new HTML (without using a few lines of code) is to edit all of the posts and re-save them to trigger a cache update. That's painful.

Alternate suggestions welcome though."	Viper007Bond
Future Releases	23149	YouTube Embedding is incorrect for https:// URLs		Embeds	3.5	normal	normal	Awaiting Review	enhancement	new		2013-01-08T19:46:28Z	2013-05-29T22:37:13Z	"Reference: #18719, #20102, Conversation from 9-19-2012:
https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2012-09-19&sort=asc#m459455

This is incorrect and a bug. If the user has posted an https link, then we should send the correct parameters to YouTube to get an https value in the resulting HTML returned.

At present, there is no way within WordPress to get the proper https code in a YouTube oEmbed iframe when https is actually desired.

"	Otto42
Future Releases	24170	oEmbed / Vimeo: Support player.vimeo.com-style URLs		Embeds		low	minor	Awaiting Review	enhancement	new		2013-04-23T21:24:58Z	2013-04-23T21:24:58Z	Vimeo also supports URLs like http://player.vimeo.com/video/64213430 for its oEmbed endpoint. It would be nice if the core regex also handled these URLs.	danielbachhuber
Future Releases	24318	oEmbeds in feeds		Embeds	trunk	normal	normal	Awaiting Review	enhancement	new		2013-05-11T16:31:46Z	2013-05-13T19:06:43Z	"The [http://wordpress.org/news/2013/05/wordpress-3-6-beta-3/ latest blog post] on wordpress.org included links to a playlist on Rdio and Spotify. As per #24242 these are converted to oEmbeds.

When viewing this post in Google Reader, neither the Rdio or the Spotify embeds are displayed, presumably because they both use an iframe. This led to the paragraph above it not making a lot of sense (see screenshot).

Is it safe to assume that any oEmbed which uses an iframe will not be displayed in an RSS reader? I genuinely don't know the answer to this as I only use Google Reader (not for much longer of course).

Should we implement a fallback (ie. just display the link as-is) in the RSS feed if the oEmbed uses an iframe?"	johnbillion
Future Releases	23622	Support Google Maps / Docs / Spreadsheet embeds		Embeds		normal	normal	Awaiting Review	feature request	new		2013-02-26T06:08:17Z	2013-05-30T18:47:41Z	"Google Maps and Drive (docs, spreadhseets, and presentations) all can do embeds, but don't support oEmbed. Still, I think they're big enough for the core to have support for natively. We already have Google Video support, and it's pretty much dead now.

Initial patch attached. 

- To get a Maps URL, view a Google Map, then select the ""Link"" icon in the left menu bar, top-right corner.
- To get a docs/sheet/presentation URL, open the item, select ""File->Publish To Web. Once it's published and visible to the web, the dialog will give a link for you to copy/paste.

This uses the normal embed handler, meaning that either the [embed] shortcode or just pasting the URL on a line by itself will trigger the embed. Width and height parameters are supported, and Presentations has special parameters to allow full-screen viewing.
"	Otto42
Future Releases	14584	HTML entities in category and tag elements		Export	3.0.1	normal	normal	Awaiting Review	defect (bug)	new		2010-08-11T05:47:13Z	2010-08-11T05:47:13Z	"The script wp-admin/includes/export.php creates CDATA blocks for category and tag data which contain HTML entities. Normally, these characters should appear un-encoded in the CDATA blocks, see #4321.

I suspect this problem may have been considered at some point, but currently the line in question is commented out : http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/export.php?rev=9148#L102

The solution, I think, would be to replace that comment with html_entity_decode($str) "	lavamind
Future Releases	22279	Wordpress Export/Import deletes carriage returns		Export	3.4.2	normal	major	Awaiting Review	defect (bug)	new		2012-10-25T20:02:42Z	2012-10-25T20:02:42Z	"Wordpress export does not translate or escape bare CR characters in a CR/LF pair.  They show up unfiltered in the WXR export file.  I see this both in post_content and in strings that were serialized into a post_meta field.  The CR characters are in the WXR file, unfiltered.

Then, Wordpress import loses these CR characters.  They are simply erased.  It may be because SimpleXMLParser can't or won't open the XML file in binary mode, so line ending translation can & does happen.  That's just a theory, but if it's true then this behavior might *not* happen on all platforms or with all PHP versions.  (I'm seeing this on OS X 10.6.8, PHP 5.4.4.)

In the worse case -- mine -- the munged string is a small component of a complex datastructure that is serialized in a postmeta record.  In this case, the entire meta_value field is deleted on import, because the data won't unserialize, because its length has changed.

It seems to me that WP Export should escape any character that might be threatened in transit.  I'm no XML lawyer, but some sources claim that unescaped CR characters are invalid XML.

To reproduce: 

* store a carriage return in a post.  
* export it to a WXR file.
* examine the WXR file for the raw carriage return (^M).
* import that file.
* search for the carriage return."	mykle
Future Releases	19864	Abstract export_wp() for use by CLI scripts		Export	3.3.1	normal	normal	Awaiting Review	enhancement	reopened		2012-01-20T18:16:17Z	2012-05-20T04:15:19Z	"Need to be able to execute an export from the PHP CLI for the purpose of running cron / maintenance scripts that write out exports.

This would include writing additional hooks that allow the arguments to be pulled from the cli as well as hooks that allow the output to redirected from the output buffer to a file.

Related ticket: #19863, extra hooks for manipulating content and arguments of an export"	scottconnerly
Future Releases	19307	"Need ability to export ""All content"" but limited to date range"		Export	3.1	normal	normal	Future Release	enhancement	new	early	2011-11-20T23:19:43Z	2012-07-11T07:39:18Z	"Need ability to export ""All content"" but limited to date range

==== ENV ====

 WP 3.3-beta3-19254 (trunk r19367)

==== Additional Details ====

For a larger site is a common scenario to need to export all content, but because of resource limitations or time constraints it cannot be done in a single export.

Exporting individual post types is not a work around, further you lose attachments on posts when exporting just ""posts"", and that breaks features including Featured Images.

==== Also Consider ====

Another common scenario for media and enterprise customer is wanting to export a period of time to further analysis that content, or stage it in their development environment for debugging an issue, or developing new designs and features."	lloydbudd
Future Releases	14757	users with no posts are not exported		Export	3.0.1	normal	normal	Awaiting Review	enhancement	reopened	dev-feedback	2010-09-01T18:14:31Z	2011-04-02T19:49:19Z	I just exported a large standalone site and imported into a multisite setup, and I discovered that a number of users who hadn't yet posted anything didn't get moved to the new site.	sillybean
Future Releases	22014	$arg was undefined, added it as optional param		External Libraries	2.5	normal	trivial	Awaiting Review	defect (bug)	new		2012-09-27T09:40:45Z	2012-09-27T09:56:35Z	"The variable $arg was not defined, so I added it as an extra parameter.

wp-admin/includes/class-ftp.php 
function nlist

Patch here :
https://github.com/h4ck3rm1k3/WordPress/commit/1bb897fc0e20de43122a468d1dae85ad2ad33c37"	h4ck3rm1k3
Future Releases	22492	Duplicate MIME-Version header		External Libraries	3.4.2	normal	minor	Awaiting Review	defect (bug)	new		2012-11-18T03:16:33Z	2012-11-18T10:46:26Z	"In certain cases, Wordpress sends emails containing two ""MIME-Version"" headers. This causes email rejections from some Amazon SES SMTP servers in particular.

To reliably reproduce, a default multisite install with BuddyPress can be used. When a user tries to register and create a website, the activation email contains this bug. Unfortunately I don't know how to reproduce this error with Wordpress itself, but I believe this bug is related to the Wordpress core. If any plugin happens to set a custom header of ""MIME-Version"" to an email message, Wordpress core is the culprit for the insertion of the duplicate mail header.

Patch attached to this report, it's a trivial fix. All the fix does is checks to see if ""MIME-Version"" was already included in custom mail headers, and if so, don't insert the duplicate header."	ryderlewis
Future Releases	23364	Unstable sorting with jQuery UI 1.9.1 and above		External Libraries	3.5	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2013-02-02T03:07:18Z	2013-02-02T03:09:35Z	"There seems to be an issue with jQuery UI (sortable) 1.9.1 and above that affects (rather severely) sorting of elements inside sortable source and target containers. I haven't seen this affect core, but since WP has been shipping with one of the affected versions (1.9.2) since 3.5, I'm worried about potential repercussions on WP theemes, plugins or projects relying on this script. For instance, Ultimate Tinymce, by Josh Lobe and myself (recently), has been affected by this.[[BR]]
[http://elblawg.com/jqueryui-test/ Here] is a testing platform I created on my server about the problem. Choosing any version of UI newer than 1.9.0 will result in said behavior.[[BR]]
[http://bugs.jqueryui.com/ticket/9041 Here] is the ticket I submitted to jquery UI Trac and [https://github.com/MarventusWP/jquery-ui/commits/master here] the Commits to their github project.[[BR]]
Finally, as recommended by Andrew Nacin on the wp-forums list, [http://jsfiddle.net/Marventus/THwqS/1/ here] is a JSFiddle that reproduces the problem.[[BR]]
I am not really sure what to do about this, but I thought I should leave it on record just in case.
Thanks!"	Marventus
Future Releases	18521	Wp_mail function: email subject with multibyte chars is not encoded properly		External Libraries	3.2.1	normal	major	Awaiting Review	defect (bug)	new		2011-08-26T08:51:11Z	2011-08-27T00:51:21Z	"'''Problem:'''
When an email with multibyte characters (like Swedish é, å, etc.) in the subject is sent from Wordpress (using wp_mail), the subject of the email at the reciever end looks like this: =?UTF-8?Q?New_site_name_Site:_J=C3=A9t_inqsfzxb_p=C3=A5_?= =?UTF-8?Q?=C3=A9?=

'''Reproduce:'''
Create the new blog with a multibyte char in the blog title and then activate it.
For example: go to /wp-content/wp-signup.php and create a new user. After that you will be asked to create a new blog. Create one and put some é and å characters in the blog title. After that you will recieve the first email (which should be ok), asking to activate the account. Activate it, then you will get the second email with the screwed subject.

'''Reason:'''
The reason is phpmailer class which double-encodes the email subject (only when sending mail using php mail() function though). The problem in these lines (wp-includes/class-phpmailer.php, taken from WP 3.2.1):
(lines 657, 663, 671, 677)
$rt = @mail($val, $this->EncodeHeader($this->SecureHeader($this->Subject)), $body, $header, $params);
$rt = @mail($to, $this->EncodeHeader($this->SecureHeader($this->Subject)), $body, $header, $params);
$rt = @mail($val, $this->EncodeHeader($this->SecureHeader($this->Subject)), $body, $header, $params);
$rt = @mail($to, $this->EncodeHeader($this->SecureHeader($this->Subject)), $body, $header);
The subject is first encoded with EncodeHeader function, and after that encoded again by mail() function itself.

'''Fix suggestion:'''
Since mail() function does proper encoding of subject, we don't need to encode it ourselves. So those lines should be replaced by:
$rt = @mail($val, $this->Subject, $body, $header, $params);
$rt = @mail($to, $this->Subject, $body, $header, $params);
$rt = @mail($val, $this->Subject, $body, $header, $params);
$rt = @mail($to, $this->Subject, $body, $header);
I've tried this on my server, and it works well.

'''Conclusion:'''
Hope it will be fixed and included in the release soon. Although, i've found the good enough temporarily solution overloading wp_mail() with a plugin, but still would be nice to see the solution in the wordpress core."	jetpackpony
Future Releases	24495	thickbox's inline content will not trigger unless it is preceeded by an ampersand		External Libraries	3.5.1	normal	minor	Awaiting Review	defect (bug)	new		2013-06-05T07:37:24Z	2013-06-05T07:37:24Z	"When using the built in thickbox, you are required to set up your links with an ampersand before the inlineId parameter or it will not pick this up.

This means that by calling inline content with  `<a href=""#TB_inline?inlineID=foo-bar"">`, you will get an empty thickbox, where as calling `<a href=""#TB_inline?&inlineID=foo-bar"">` it will function as intended and load the inline content for the thickbox."	Clorith
Future Releases	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
Future Releases	24132	Add jQuery 2.0 to available scripts to enqueue		External Libraries	trunk	normal	normal	Awaiting Review	enhancement	new		2013-04-18T23:09:24Z	2013-04-22T07:02:25Z	"jQuery 2.0 was released, and is a major release, more than previous ones. the 2.0 branch removes support for IE8 and down. Personally, I think it'd be best to add it alongside jQuery 1.9.x instead of outright replace. That way people who want to use the 2.0 branch can, but those who need legacy IE support still, can still use 1.9.x.

My thoughts were for a new enqueue handle of 'jquery2'."	tw2113
Future Releases	21769	Can we remove un-minified versions of all external libraries?		External Libraries	3.5	normal	normal	Future Release	enhancement	new	dev-feedback	2012-09-02T09:32:35Z	2012-10-24T20:50:12Z	"With [21646] and [21648] we had removed the un-minified versions of Jcrop and jQuery Color.

A quick search through the plugin repo shows that there is only one plugin which includes the script directly:

Pie Register: http://plugins.trac.wordpress.org/browser/pie-register/trunk/pie-register.php#L1444

Should we be consistent and remove the un-minified versions of other external libraries too? These would be:

* colorpicker.js
* hoverIntent.js
* jquery.imgareaselect.js
* cropper.js (not used in core anymore and no minified version exists)
* json2.js
* tw-sack.js"	ocean90
Future Releases	19489	Consider updating jquery.hotkeys plugin		External Libraries	3.3	normal	normal	Future Release	enhancement	reopened		2011-12-09T18:50:05Z	2013-01-22T19:40:32Z	"The current version of the jquery.hotkeys plugin in trunk is ""(beta)(0.0.3)"", where as the [https://github.com/tzuryby/jquery.hotkeys/blob/master/jquery.hotkeys.js latest version] (as linked to from the credits screen) is 0.8.

Incidentally, this 0.8 version from tzuryby is credited as being authored by John Resig (and indeed, he appears to have his own [https://github.com/jeresig/jquery.hotkeys repo] for it."	GaryJ
Future Releases	19449	Fix Farbtastic to make it work with empty input fields, too		External Libraries	3.3	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-12-05T17:38:08Z	2011-12-05T17:38:08Z	"Farbtastic requires that the color input field has either a color value or at least a '#' character. If it's empty it won't work. This seems like an artificial limitation and requires workarounds if the integrated Farbtastic is used for input fields that may be empty, i.e. for theme or plugin options where the color is optional. If the color fields has a default value there's no issue but having empty color fields is a useful and valid use case. 

This could be fixed in /wp-admin/js/farbtastic.js, line 192

Old:
if (this.value && this.value != fb.color) {

New:
if (this.value != fb.color) {


Looks like WP is working around this for the 'custom background' for themes (which is empty by default) by adding a hardcoded '#' and saving the background-color without '#' 

/wp-includes/theme.php, line 1772:
$style = $color ? ""background-color: #$color;"" : '';

/wp-admin/custom-background.php, line 303:
<input type=""text"" name=""background-color"" id=""background-color"" value=""#<?php echo esc_attr(get_background_color()) ?>"" />

"	BytesForAll
Future Releases	16494	"Remove ""no conflict"" mode from bundled jquery"		External Libraries	3.1	low	minor	Awaiting Review	enhancement	new	close	2011-02-08T18:45:49Z	2012-07-14T11:04:26Z	"Remove ""no conflict"" mode from jquery

Over the last six months more and more of the themes I review for large sites have being using Google's CDN version of jquery (deregistering the bundled), not to get the benefit of CDN, but because most jquery libraries are dependent on $ and the developers don't know or want to deal with getting them to work in ""no conflict"".

I image we originally put in place ""no conflict"" mode for bundled jquery, as part of the transition from Prototype.

I appreciate it is hard to measure the impact of this type of change, but wanted to trac this all the same.

=== Additional Info ===

http://codex.wordpress.org/Function_Reference/wp_enqueue_script#jQuery_noConflict_wrappers

http://docs.jquery.com/Using_jQuery_with_Other_Libraries"	lloydbudd
Future Releases	10955	Replace ThickBox		External Libraries	2.9	normal	normal	Future Release	enhancement	new	dev-feedback	2009-10-14T14:37:42Z	2013-02-01T15:59:30Z	"Have you thought about replacing ThickBox?  It is no longer under development (as their site says) and it doesn't conform to standard jQuery plugin practices.  For example, I'm trying to use it for a plugin of mine and I'm wanting to tie into the ""onClose"" event for ThickBox which isn't too easily done.  I know I could just include one of the other plugins, like colorbox, with my plugin but I think it'd be a great service to other developers if you included a more flexible library.


(I would have assigned this to 3.0+ but the option isn't available.)"	aaron_guitar
Future Releases	19419	wp-admin/media.php: allow to add a default src		External Libraries	3.2.1	normal	normal	Awaiting Review	enhancement	new		2011-12-02T21:15:34Z	2011-12-22T23:01:36Z	"something like 

in file wp-admin/media.php :

function type_url_form_image($image_url) { 
  
    .
    .
    .
    <input id=""src"" name=""src"" value=""'.$image_url.'"" type=""text"" 
    .
    .
    .

    }

might be helpful because the function can be reused for plugins"	mostyk
Future Releases	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
Future Releases	15610	Comments on attachments don't appear in site-wide comments RSS feed		Feeds	3.1	normal	minor	Future Release	defect (bug)	new		2010-11-29T21:05:37Z	2010-12-11T14:00:22Z	"Tested against r16950.

Comments that are entered against an attachment do not appear in the site-wide comments RSS feed (e.g., http://sitename.com/comments/feed/).

To test:

 1. Add an attachment of any kind (usually image), then View the attachment.
 2. Post a comment on the attachment page.
 3. Check the site's comments RSS feed - the comment will not appear."	markel
Future Releases	21225	Dashboard Incoming Links - Google blogsearch fails when get_option( 'home') is not a TLD		Feeds	2.5	normal	minor	Awaiting Review	defect (bug)	new	dev-feedback	2012-07-12T02:47:09Z	2012-07-12T04:23:56Z	"When WordPress gets installed and the first time a user visits the dashboard the dashboard_widget_options get set for dashboard_incoming_links.  The Google blogsearch link gets set based on your settings for wp_home.  If your developing on a local machine most likely wp_home is not a true TLD.

Google blogsearch incorrectly returns incoming links when the site: url is not a true TLD.  For example I'll use an install where wp_home is set to http://wp.patch.  The link that gets formed is:

http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://wp.patch/

If you visit that link you will notice that results are getting returned just using the ""patch"" keyword.

If the sited gets moved to live production you will continue to get the incorrect incoming links unless the dashboard_widget_options get manually changed or deleted.

Also to note is that the Google blogsearch API has been deprecated:  https://developers.google.com/blog-search/

My suggestion is to remove the widget or hide it by default in screen options like we did for some of the stuff in post.php.

Another option is to do a check and return WP_Error if wp_home is not a TLD before setting the dashboard widget options."	c3mdigital
Future Releases	21753	Feed excerpts are missing important filter formatting		Feeds	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-31T14:20:56Z	2012-08-31T14:20:56Z	"Excerpts included in feeds are missing important formatting because the relevant filters are not applied (e.g. wpautop).

In file wp-includes/feed.php, function the_excerpt_rss() does not apply the same filters as the_excerpt() whilst results in lost formatting instructions.  By comparison, function the_content_feed() ensures that the same filters declared for the_content() are applied.

A suggested patch is attached. Note that for symmetry between the_excerpt_rss() and the_content_feed() this patch also removes the (unnecessary?) filter ent2ncr() from the_excerpt_rss() and retains the (controversial?) escaping for CDATA blocks (see #3670).

A few related issues are worth mentioning. Firstly, shortcodes are still not applied to excerpts (see #7093). Also, the (obsolete?) RDF feed does not make use of a CDATA block unlike those for RSS, RSS2 and Atom (see #20888). Finally, a similar problem occurs with comment text in feeds (see #16466)."	mdgl
Future Releases	22101	"Gallery shortcode with link=""file"" is not linking the file in the RSS feed"		Feeds	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-10-04T16:14:16Z	2012-10-27T15:58:55Z	"Hi,
In a WordPress site I'm currently developing I want to use the stock gallery shortcode. I use [gallery link=""file""] to link directly the image URL which, should fix Flipboard, Currents et al. showing just a little thumbnail. 

In the page the code is displayed properly and the a tag links the image file, but, on the RSS feed, it links to the attachment page. 

I've tested this in the latest nightly version 3.5-beta1-22104 and on the stable 3.4.2. I attach the output of the page and the feed. "	ifrins
Future Releases	16544	RSS2 feeds are published as text/xml rather than application/rss+xml		Feeds	3.0.5	normal	trivial	Awaiting Review	defect (bug)	new	close	2011-02-12T21:25:45Z	2011-02-13T06:00:04Z	"It seems to me that there is a bug in feed-rss.php, feed-rss2.php and feed-rss2-comments.php

All files have the following header

header('Content-Type: ' . feed_content_type('rss-http') . '; charset=' . get_option('blog_charset'), true);

Which seems to publish the feed as text/xml rather than application/rss+xml which I believe it should be."	Orakel78
Future Releases	22362	Titles of RSS feeds lacks spacing - words are run together		Feeds	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-11-05T15:30:23Z	2012-11-05T16:40:58Z	"Line 24 of wp-includes/feed-rss2.php has:

<title><?php bloginfo_rss('name'); wp_title_rss(); ?></title>

There's no space between those two parts. In my (development) site, for the feed for a category ""News"" (which is the main one I'm offering up), that results in:

<title>SitenameNews</title>"	DavidAnderson
Future Releases	19368	UTF-8 characters truncated mid-byte sequence in excerpt in RSS2 feed		Feeds		normal	normal	Awaiting Review	defect (bug)	new		2011-11-27T05:54:33Z	2011-11-27T15:08:14Z	"I received [https://code.google.com/p/feedparser/issues/detail?id=306 a bug report at a project I maintain] and discovered what appears to be a bug in Wordpress 3.2.1.

The trouble is that the `description` element is being truncated in the middle of a UTF-8 multibyte character, which is producing garbage binary data. An example can be found at:

http://www.arnaudmontebourg.fr/?feed=rss2

I downloaded [http://themocracy.com/2009/07/alibi3col-free-wordpress-theme/ the site's theme] but found nothing that would affect `post_excerpt` or `the_excerpt_rss`. I then downloaded Wordpress trunk and attempted to figure out where the problem might be, but I'm unfamiliar with the Wordpress source and couldn't find anything after tracing through multiple files using grep.

I did discover that `trackback_url_list()` in `wp-includes/post.php` appears to be using a simple `substr()` call that might cause problems with multibyte characters. However, I'm more concerned with the potential for malformed feeds.

I've included a copy of the feed XML in question for longevity."	kurtmckee
Future Releases	20379	dashboard_incoming_links fails to update when 'home' changes, so google rss is wrong		Feeds	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-04-06T16:04:00Z	2013-02-12T22:50:59Z	"When the user changes 'home', the wp_option 'dashboard_widget_options' is updated. But WP fails to update it completely, so the default Google RSS syndication URL is broken.

The borked value is:

dashboard_widget_options: dashboard_incoming_links: url

which is of the form

http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://example.com/

The string at the end, example.com, is supposed to change but it does not.

Here is the problem.
(Trunk has the same code as the current ver. 3.3.1.)

http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/dashboard.php#L59
constructs 'url' as follows, expanded for readability:

{{{
'url' => isset($widget_options['dashboard_incoming_links']['url'])
	? apply_filters(
		'dashboard_incoming_links_feed',
		$widget_options['dashboard_incoming_links']['url']
	)
	: apply_filters(
		'dashboard_incoming_links_feed',
		'http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=' . $num_items . '&output=rss&partner=wordpress&q=link:' . trailingslashit( get_option('home') )
	),
}}}

Since 'url' is already set, it never changes! The value of get_option('home') is not used.

This code block is only reached when 'home' has changed, or on initial setup, so it does not make much sense to ignore 'home'.

I'm not sure if there is any reason to keep the tertiary. Solution 1 below is the simple fix.
Solution 2 is a heuristic fix to handle the case where a plugin or theme has updated the database, instead of using the filter. It mimics the current (possibly wrong) behavior in that case.

Solution 1:
{{{
$widget_options['dashboard_incoming_links'] = array(
	...
	'url' => apply_filters( 'dashboard_incoming_links_feed', 'http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=' . $num_items . '&output=rss&partner=wordpress&q=link:' . trailingslashit( get_option('home') ) ),
}}}

Solution 2:
{{{
$url_prefix = 'http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=' . $num_items . '&output=rss&partner=wordpress&q=link:';
$url = $url_prefix . trailingslashit( get_option( 'home' ) );
if ( isset ( $widget_options['dashboard_incoming_links']['url'] ) ) {
	if ( 0 !== strpos( $widget_options['dashboard_incoming_links']['url'], $url_prefix ) ) {
		$url = $widget_options['dashboard_incoming_links']['url'];
	}
}
$widget_options['dashboard_incoming_links'] = array(
	...
	'url' => apply_filters( 'dashboard_incoming_links_feed', $url ),
}}}

The importance of this bug is twofold:
1. No clear workaround for the user, even with basic PHPMyAdmin skills. The incorrect value is in a serialized array in the table 'wp_options'.
2. Users may not realize the feed is borked, since there is no Dashboard UI. I think there used to be. The WP forums have several 5-year old threads about it.

By the way, $num_items never changes by default. It could only be updated by plugins or themes, and Solution 2 assumes they know what they are doing there too.
"	kitchin
Future Releases	4253	Category feeds don't indicate they are category feeds		Feeds		normal	normal	Future Release	enhancement	new		2007-05-13T04:35:10Z	2009-06-14T13:43:40Z	"Okay guys, here is a patch for WordPress that properly titles and describes category RSS/Atom feeds.  I didn't know how to set the URL for the feed to the URL of the category, so what I'm doing is just leaving the bloginfo URL as it is, but I hope you can whip that out from your fabulous hacking heads.

This patch makes sense because of several reasons.  My personal reason is that I'm running a magazine with different sections (using categories as the section) at rudd-o.com, and I'm encouraging subscriptions to the section feeds instead of the whole magazine, but the feeds themselves don't say which category they're from.  Now with this patch they do.

Another thing that I'm not sure about, and I'd like a response in the form of a comment here (I'm tracking this bug via RSS): do I have to htmlspecialchars() before doing the print's ""..."" in this patch?  The question, more properly phrased, is: if I print a get_category_name(), should I print it htmlspecialchar()red, or should I just print it out, and trust that the WordPress category administrator won't let people type random HTML?  Another way of posing the question would be: if I type an ampersand (&amp;) in the category name, what should the theme display, ""&amp;"" or ""&""?  This is keeping me up at night, need some sleep, please help =).

"	RuddO
Future Releases	11053	Conditional Tags should work in feeds as well		Feeds	2.8.5	normal	normal	Future Release	enhancement	new		2009-10-31T14:56:17Z	2010-01-17T14:20:19Z	"I try to get the following to work:

{{{
function xxx_filter_cat()
{
	if (is_author()) query_posts(""cat=4"");
	if (is_front_page()) query_posts(""cat=2,3"");
}

add_action('rss2_head', 'xxx_filter_cat');
}}}

It should alter the rss2 feed, depending if it should get generated for the general homepage, or for a single author.

But: It doesn't work at all - is_author and all the other is_* functions I tried always trigger false. is_feed works, but well, doesn't help me very much.

It would be easy to manipulate the generated feeds if wp would support the already built-in conditional tags in the feeds as well."	pampfelimetten
Future Releases	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
Future Releases	24534	Add hooks to style feeds using xslt		Feeds	3.5.1	normal	trivial	Awaiting Review	feature request	new		2013-06-07T15:27:11Z	2013-06-07T15:27:11Z	"There were a few discussions several years ago about this (#1380), which essentially went nowhere.

Any odds that, with Google Reader and Feedburner on their death bed, we could have e.g. <?php do_action('rss2_stylesheet'); ?> after the xml declaration in wp-includes/feed-rss2.php, and similar hooks for other feed types, so as to offer an explanation on how to subscribe to visitors who click a feed link?"	Denis-de-Bernardy
Future Releases	23589	FS_CHMOD_FILE doesn't work for ssh		Filesystem	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-02-22T21:34:44Z	2013-02-23T00:19:11Z	"Steps to reproduce:
1. set up ssh access for !WordPress (FTP_* constants).
2. `define('FS_CHMOD_FILE', 0664)`.
3. install some theme.

Expected result: files have 0664 permissions.

Actual result: files have default permissions (0644).

I believe this happens because filename is ltrimmed before sending over SSH, but not restored before changing permissions. See [http://core.trac.wordpress.org/browser/tags/3.5.1/wp-admin/includes/class-wp-filesystem-ssh2.php#L164 this]."	x-yuri
Future Releases	24107	Plugin/Theme installer asks for connection info when wp-content is writable but wp-admin is not		Filesystem		normal	normal	Awaiting Review	defect (bug)	new		2013-04-16T21:39:34Z	2013-04-17T01:08:42Z	"For background, please see [http://www.chrisabernethy.com/why-wordpress-asks-connection-info/]

When installing a new plugin or theme, WP first checks to see if it can directly write to the filesystem.  If so, it proceeds.  If not, it asks the user for FTP connection info.

The directory to which it NEEDS access is /wp-content

However, the directory it CHECKS is /wp-admin

get_filesystem_method() should be changed (or parameterized) to check only /wp-content in cases where /wp-admin access is not needed.  This will allow installations to have a higher filesystem-security setting for /wp-admin than for /wp-content, while still utilizing direct filesystem access."	peckjon
Future Releases	21452	When uploading media wp_unique_filename() treats capitalisation as being different.		Filesystem	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-02T13:24:11Z	2012-08-02T13:24:11Z	"On most web servers ""Photo.jpg"" and ""photo.jpg"" can be treated as different files.

The problem is when backing up a local copy (to my Mac) it will not let both these files exist at the same time - it wants to replace one with the other as it treats lowercase and uppercase as the same.

I suggest that we should do the same with uploads so that if ""Photo.jpg"" exisits and you upload ""photo.jpg"" is is renamed to a unique name.

I guess this would require a fix in the wp_unique_filename() function."	husobj
Future Releases	23196	mkdir not recursive (in wp-includes/functions.php)		Filesystem		normal	normal	Awaiting Review	defect (bug)	new		2013-01-14T08:35:51Z	2013-01-14T10:25:01Z	"This January, Wordpress tried to create a directory and a subdirectory in ""uploads"": ""2013"" and inside it ""01"".

`mkdir($target)` was used to create these two directories, but since the $recursive option (3rd argument) was not set, this operation failed.

I have just checked this path and it does exist, hence I suspect this procedure is being done somewhere else (and succeeding).

Still, this is a problem since:
1. It is showing up in our error logging system.
2. It is very easy to fix.
3. It potentially fixes more problems than it seems.

The solution is to change this line:

    1306:        if ( @mkdir( $target ) ) {

To the following:

    1306:        if ( @mkdir( $target, 0777, true ) ) {


On a sidenote, PHP's default directory creation mode is 0777 (so the above code is best for compatibility), but as you may know, it is not good in terms of security, so you may want to look for a more secure fix (eg, lowering the mode if it doesn't cause problems)."	uuf6429
Future Releases	21453	Appending hyphen before numbers when creating a create unique filename in wp_unique_filename()		Filesystem	3.4.1	normal	normal	Awaiting Review	enhancement	new		2012-08-02T13:32:00Z	2012-08-02T13:32:00Z	"When WordPress appends a number to a file to create a unique filename, it just adds a number to the file.
ie If ""photo.jpg"" exists then ""photo1.jpg"" is created

I suggest that it should include a hyphen so the file would be called ""photo-1.jpg""

The main reason is that if you upload files ending in numbers then then the new filename is less easy to read.
ie If ""photo234.jpg"" exists then ""photo2341.jpg"" is created

Would be nicer if it produced ""photo234-1.jpg""

It's only cosmetic but it does make it easier to search for images in the uploads folder if you need to for any reason, especially if you have uploaded a load of images from a camera DSC123.jpg, DSC124.jpg etc"	husobj
Future Releases	20716	Control how and when request_filesystem_credentials outputs creds form		Filesystem	3.4	normal	normal	Awaiting Review	enhancement	new	reporter-feedback	2012-05-21T02:02:08Z	2012-05-21T02:05:10Z	"When using WP_Filesystem in a plugin or other external app, you can initialize it this way:

{{{
if ( false == ( $creds = request_filesystem_credentials( $url, $method, false, false, $form_fields ) ) ) {
    return true;
}
}}}

Makes sense. If the method isn't direct or we don't have the credentials we need, `request_filesystem_credentials` outputs a form and returns false. Then we check again to make sure the credentials can be verified, and it not, we continue to output the form until the credentials are good.

{{{
if ( ! WP_Filesystem( $creds ) ) {
    request_filesystem_credentials( $url, $method, true, false, $form_fields );
    return true;
}
}}}

`request_filesystem_credentials` arbitrarily outputs the form whether you want it to or not, unless you explicitly filter the `request_filesystem_credentials` function itself. Using this in conjunction with Ajax, you have to use output buffering to catch the output and return it to the Ajax script for processing or else you get errors. This definitely isn't ideal.

I'd suggest storing the form in a variable and possibly pass a parameter that determines whether or not we want to actually output the form or not. Or, if there is another (better) way, that's cool too. Just some way to help `request_filesystem_credentials` determine how we want to interact with credentials should we need them.

"	griffinjt
Future Releases	22772	Introduce HOMEPATH		Filesystem	3.5	normal	normal	Awaiting Review	enhancement	new		2012-12-06T03:05:42Z	2013-03-03T20:23:48Z	"I was poking around with get_home_path() and wondering if there's any reason to not set a constant HOMEPATH (like ABSPATH) in the root index.php

I'd seem to be more reliable then get_home_path() and that function could simply return the new constant.

get_home_path has it's origins 8 years ago when the code was very different: [1567]"	WraithKenny
Future Releases	22946	Default filter erroneously turns FTP hostnames into HTTP links		Formatting	2.0.4	normal	normal	Awaiting Review	defect (bug)	new		2012-12-14T20:01:51Z	2012-12-22T19:40:55Z	"The function _make_web_ftp_clickable_cb in wp-includes/formatting.php is invoked upon any hostname matching ""www."" or ""ftp."" at the beginning. It pre-pends 'http://' and makes the link clickable (i.e. wraps it in <a href="""">).

As a default that makes sense for things beginning www. - but not for everything beginning ftp.

In my case, I was using the plugin WP Better Emails, and sent out an email with this line (approx):

`Here is the FTP server: ftp.example.com`

WP, by default, ""helpfully"" totally mangles this into:
`Here is the FTP server: <a href=""http://ftp.example.com"">http://ftp.example.com</a>`

The recipient of my email now believes that I was sending him an HTTP link, and is confused that it does not work. But in fact I never sent such a link - that was WordPress mangling what I did send.

Sure, some FTP servers will also have HTTP listening. But by default WordPress assumes that they all do, which is crazy.

Proposed solution: on line 1471 of wp-includes/formatting.php (as found in 3.4.2), change:
{{{
$ret = preg_replace_callback( '#([\s>])((www|ftp)\.[\w\\x80-\\xff\#$%&~/.\-;:=,?@\[\]+]+)#is', '_make_web_ftp_clickable_cb', $ret );
}}}
by removing the ""ftp"" case, hence:
{{{
$ret = preg_replace_callback( '#([\s>])((www)\.[\w\\x80-\\xff\#$%&~/.\-;:=,?@\[\]+]+)#is', '_make_web_ftp_clickable_cb', $ret );
}}}
The function _make_web_ftp_clickable_cb should then be renamed by removing ftp_, since the case of turning FTP hostnames into clickable HTTP links would have been removed."	DavidAnderson
Future Releases	22971	Don't work quotes auto closing in that case		Formatting	3.5	normal	minor	Awaiting Review	defect (bug)	reopened		2012-12-17T12:06:43Z	2012-12-18T13:33:41Z	"Hello, use latest wordpress version - 3.5.

If I enter


{{{
""My Simple Text""
}}}
to wordpress text editor - all right quotes close automatically and it will have view:
«My Simple Text»

But if I'll write 
{{{
""My Simple Text 2013""
}}}

It will have view:
«My Simple Text 2013""

conclusion: quotes auto closing don't work if string ends by numbers
"	Stafox
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	20342	Opening Double Quote after 3 hyphens converted to double closing quote		Formatting	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-04-01T20:16:05Z	2012-04-01T20:16:05Z	"The string:

{{{
<p>I also remember the line in ""Casey at the Bat"" when he struck out---""There is no Joy in Mudville!!!""</p>
}}}

is converted to this in WordPress 3.3.1:

{{{
<p>I also remember the line in &#8220;Casey at the Bat&#8221; when he struck out&#8212;&#8221;There is no Joy in Mudville!!!&#8221;</p>
}}}


Seems to be what should be an opening quote that follows an Em dash is always converted into a closing quote."	PetesGuide
Future Releases	20943	Paragraphs get removed in table cells when Visual editor is refreshed		Formatting	3.2	normal	normal	Awaiting Review	defect (bug)	new	needs-unit-tests	2012-06-13T19:06:04Z	2013-04-18T16:14:03Z	"As far as I know, this issue has been around since 3.1.  It's not a bug in 3.0.4.  I even stopped upgrading at 3.0.4 for any sites where I knew the client would need to edit tabular data.  For security reasons, it's time to upgrade these and I'd REALLY like this issue to be fixed.

The problem happens when using paragraphs in a table cell.  When I hit enter to create a new paragraph within a table cell, it looks fine.  If I then hit Update/Publish, when the page refreshes, WordPress converts that paragraph break into a single line break.  If I then click Update again, WordPress removes that linebreak entirely and the paragraphs are essentially merged.

I can also reproduce this behaviour without even clicking Update.  If you just switch to HTML mode and then back to Visual mode, the same issue occurs."	JboyJW
Future Releases	14491	Quotation mark broken after ciphers		Formatting	3.0.1	normal	normal	Future Release	defect (bug)	new		2010-07-31T09:26:39Z	2010-11-28T03:26:14Z	"As a default bug in Wordpress, quotation marks like the following ones don't work if they are positioned after ciphers/digits:
{{{
&#8242;
}}}
{{{
&#8217;
}}}
The problem is that after the digits the HTML special chars are actually '''not''' like the ones posted above. After ciphers/digits, the following source code shows us:


{{{
&#8220;2010&#8242;
}}}

{{{
&#8217;2011&#8242;
}}}

'''''Here's the solution like it should be in the source code:'''''

{{{
&#8220;2010&#8221;
}}}

{{{
&#8217;2011&#8217;
}}}"	Dannny
Future Releases	21689	Unbalanced <p> tags are generated when shortcodes are followed by HTML tags and wpautop is enabled		Formatting	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-26T06:58:21Z	2013-03-07T03:42:49Z	"This bug was encountered in separate plugins, but it seems that its source is in the core:

http://wordpress.stackexchange.com/questions/21414/wordpress-wpautop-shortcode-generating-invalid-markup

https://github.com/pods-framework/pods/issues/271"	dandv
Future Releases	22230	WP adds <br /> before <select even where there is no line break in source code		Formatting	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-10-19T21:49:26Z	2013-01-31T11:24:25Z	"My source code in the WP HTML editor:

{{{
<label for=""sellby"">How soon do you need to sell?</label><select id=""sellby"" name=""sellby"" required=""1"">
}}}

Note how there is *no line break* between </label> and <select

HTML generated by WP, however:

{{{
<label for=""sellby"">How soon do you need to sell?</label><br />
<select id=""sellby"" name=""sellby"" required=""1"">
}}}

Um, how (and why?) did that extra <br /> get in there?

This also happened when I was using the Visual editor; switched to the HTML editor to see if it was an error on my part but nope - there is no line break whatsoever in my HTML source code, so I have no idea why WP insists on adding one.

It's particularly vexing because I would like my text label to be next to (on the same line as) my select boxes, but WP is forcing it to be on the next line, which is making my form look awful.

AFAIK it's only happening with select boxes, but it's pretty consistent for me.

Since it's happening with the HTML editor as well as the Visual editor I left the Component as General so better minds than mine can categorize it appropriately."	chirael
Future Releases	18136	WordPress Adding Spurious </p>		Formatting		normal	normal	Awaiting Review	defect (bug)	reopened		2011-07-15T22:03:38Z	2012-11-14T02:06:32Z	If you look at this page: https://singpolyma.net/2011/06/dystoparx-part-12/ WordPress seems to be adding extra </p> tags before the </div>s  This causes major well-formedness problems on the page.	singpolyma
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	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
Future Releases	23605	esc_url() strips spaces instead of encoding them		Formatting		normal	normal	Awaiting Review	defect (bug)	new		2013-02-25T17:41:21Z	2013-02-27T23:56:38Z	"If I pass a URL into `esc_url()` that contains a space, the space is stripped instead of encoded.

To reproduce:

{{{
$url = 'http://example.com/foo bar/';

echo '<pre>';
var_dump( $url );
var_dump( esc_url( $url ) );
echo '</pre>';
}}}

The resulting URL ends up as `http://example.com/foobar/` instead of the expected `http://example.com/foo%20bar/`"	johnbillion
Future Releases	23975	force_balance_tags in get_the_content breaks non-HTML formats		Formatting	2.8	normal	normal	Awaiting Review	defect (bug)	new		2013-04-07T10:05:44Z	2013-04-07T10:58:50Z	"The change in r11398 (to fix #9765) breaks Markdown formatted articles that use angle bracket links: `<http://example.com/>` turning it into `<http: //example.com></http:>`.

If we call force_balance_tags after adding the more link, we need to establish filter hooks for formatters. This should have happened before r11398 already, but because balancing tags wasn't forced, this issue has not affected sites that disable balancing tags in their preferences.

Typically formatters attach to the `the_content` filter (among others). This should probably change into a `get_the_content` filter (similar to `get_the_excerpt`) that is called early on the full content of the post.

I haven't yet decided where the best place for the new filter would, or if it would be better to undo the force_balance_tags call.

Thoughts? I could work on the change, but would rather prefer some input first."	ruckus
Future Releases	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
Future Releases	23308	"make_clickable problem with multiple ""Punctuation URL character"""		Formatting	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-01-28T15:09:59Z	2013-01-28T15:09:59Z	"make_clickable problem with multiple ""Punctuation URL character""

E.g.
{{{
http://www.wordpress.org/some-(parentheses).html
}}}
Results in this html code:
{{{
<a href=""http://www.wordpress.org/some-(parentheses)"" rel=""nofollow"">http://www.wordpress.org/some-(parentheses)</a>.html
}}}
But obvious should be:
{{{
<a href=""http://www.wordpress.org/some-(parentheses)"" rel=""nofollow"">http://www.wordpress.org/some-(parentheses).html</a>
}}}

I suggest to replace:
wp-includes/formatting.php:1603
{{{
[\'.,;:!?)]  # Punctuation URL character
}}}
with
{{{
[\'.,;:!?)]{1,}  # Punctuation URL character
}}}"	DrPepper75
Future Releases	23756	make_clickable should not convert the URLs in pre,code tags		Formatting	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-13T14:17:36Z	2013-03-14T10:44:29Z	"Hi , Maybe it's a duplicate ticket but I tried to search in history.

Anyway , The purpose of this ticket is to have a clean snippet code posts .. for now it's hard to do it by plug-in .. and many people remove make_clickable filter at all !

So let's make it possible in 3.6 :)"	alex-ye
Future Releases	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
Future Releases	24157	safecss_filter_attr doesn't allow rgb() in inline styles		Formatting	2.8.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-22T16:30:45Z	2013-05-25T22:07:38Z	"I thought there should be a ticket somewhere, but I couldn't find it!

So, `safecss_filter_attr` (which is used in `wp_kses` etc, does not allow inline styles that include rgba() etc, like his:

{{{<span style=""background: rgb(0,0,0)""></span>}}}

I am not sure if this is intended, though not sure why it would be, there is a comment in `safecss_filter_attr`

{{{if ( preg_match( '%[\\(&=}]|/\*%', $css ) ) // remove any inline css containing \ ( & } = or comments}}}
"	joehoyle
Future Releases	14050	shortcode_unautop() should also remove the <br /> added after shortcodes		Formatting	3.0	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-06-22T18:15:27Z	2013-01-19T08:38:00Z	"Currently `wpautop()` wraps a shortcode in `<p>` tags as well as adding a `<br />` tag after the shortcode. We then use `shortcode_unautop()` to remove the `<p>` tags, but the `<br />` stays.

To replicate, just drop a few caption shortcodes into a post and set them all to align left or right. You'll see that even though they all float (assuming that's how your theme handles them) they stair step down because of the extra `<br />`

I'm not a regex expert so someone should probably double check my patch, but it seems to work for me."	aaroncampbell
Future Releases	18549	wp_texturize incorrectly curls closing quotes after inline HTML end tags		Formatting	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-08-30T21:54:26Z	2013-03-22T13:39:47Z	"The following source HTML:
{{{
The word is ""<a href=""http://example.com/"">quoted</a>"".
The word is '<a href=""http://example.com/"">quoted</a>'
The word is '<a href=""http://example.com/"">quoted.</a>'
The word is '<a href=""http://example.com/"">quoted</a>'.
The word is '<a href=""http://example.com/"">quot</a>'d
}}}

Gets incorrectly transformed by wp_texturize() as:
{{{
The word is &#8220;<a href=""http://example.com/"">quoted</a>&#8220;.
The word is &#8216;<a href=""http://example.com/"">quoted</a>&#8216;
The word is &#8216;<a href=""http://example.com/"">quoted.</a>&#8216;
The word is &#8216;<a href=""http://example.com/"">quoted</a>&#8216;.
The word is &#8216;<a href=""http://example.com/"">quot</a>&#8216;d
}}}
'''Note:''' all the double/single quotes in the above examples that should be closing are instead opening)

This renders in the browser like this:
{{{
The word is “quoted“.
The word is ‘quoted‘
The word is ‘quoted.‘
The word is ‘quoted‘.
The word is ‘quot‘d
}}}

The problem here is that wp_texturize splits the text on all start/end tags, which makes sense for block-level tags, but not inline-tags like {{{<em>}}} and {{{<a href="""">}}}.

formatting.php line 67:
{{{
$textarr = preg_split('/(<.*>|\[.*\])/Us', $text, -1, PREG_SPLIT_DELIM_CAPTURE);
}}}

However if you change it to only split the content on block-level tags, you'll need something more sophisticated/complex than a regular expression to avoid curling quotes within html."	justincwatt
Future Releases	20444	wpautop acts on a single line of text		Formatting		normal	normal	Awaiting Review	defect (bug)	new		2012-04-15T03:02:06Z	2012-10-10T14:11:40Z	"HTML markup on a single line wrapped in a block element is interpreted and changed by wpautop. The wpautop function is described as replacing ""double line-breaks with paragraph elements"" which led me to expect the single line would not become many lines.

{{{
echo wpautop( '<div><p>Hello world</p><span>WordPress</span></div>' );
}}}

{{{
<div>
<p>Hello world</p>
<p><span>WordPress</span></div>
}}}

Extra <p> before the <span>.

I expected wpautop would find no newlines and return the original string.

The same string placed inside a HTML5 or XHTML 1 Strict document <body> is parsed as valid by W3C Validator.

Plugins acting on the_content with a priority less than 10 may have their single-line markup reinterpreted by wpautop."	niallkennedy
Future Releases	2833	wpautop breaks style and script tags		Formatting	2.0.3	low	normal	Future Release	defect (bug)	reopened	needs-unit-tests	2006-06-17T20:36:00Z	2012-09-09T21:01:21Z	"When I create a post in which I want to include Javascript or some styles, WordPress 'breaks'when showing those posts, because all newlines in the SCRIPT and STYLE tag are converted into BR tags.

Example:
{{{
<style type=""text/css>
.matt { color: #FFFFFF; }
</style>
}}}
Becomes:
{{{
<style type=""text/css><br />
.matt { color: #FFFFFF; }<br />
</style><br />
}}}

And:
{{{
<script type=""text/javascript""><!--
google_ad_client = ""xxxxxxxx"";
google_ad_width = 120;
google_ad_height = 60;
google_ad_format = ""120x60_as_rimg"";
google_cpa_choice = ""CAAQ2eOZzgEaCD4zuVkdzt_CKI-293M"";
//--></script>
}}}
Becomes
{{{
<script type=""text/javascript""><!--<br />
google_ad_client = ""xxxxxxxx"";<br />
google_ad_width = 120;<br />
google_ad_height = 60;<br />
google_ad_format = ""120x60_as_rimg"";<br />
google_cpa_choice = ""CAAQ2eOZzgEaCD4zuVkdzt_CKI-293M"";<br />
//--></script><br />
}}}

This happens because wpautop adds those BR tags to the post. (As it should, just not within STYLE or SCRIPT tags.)

I've made a (temporary?) workaround for this by creating a pre and post event for wpautop, which substitute the necessary newlines by a temporary value in the pre event and placing them back in the post event. Although I think this should be incorporated in wpautop itself.

See also: http://wordpress.org/support/topic/76433 and http://wordpress.org/support/topic/76297

While searching trac I also found ticket #2346, which is about the same problem, but which was for 2.0 and self-closed by the submitter?

P.S. I have TinyMCE turned of."	Nazgul
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	24556	wptexturize() edge case bug with specific sentence structure		Formatting		normal	normal	Awaiting Review	defect (bug)	new	needs-unit-tests	2013-06-10T22:15:29Z	2013-06-11T03:00:41Z	"I discovered a very very edge case bug with `wptexturize()` where the below text will be output with the opening quote as the closing quote html entity (e.g. `&#8221;`) instead of the opening quote html entity (e.g. `&#8220;`) as expected.

Here's the text. The words can be replaced with anything else as long as they follow the same pattern.

{{{
Uppercase. ""Uppercase lowercase word-with-apostrophe's lowercase lowercase""
}}}

Here's how it gets output on the front-end:

[[Image(https://dl.dropbox.com/s/zbrilmyoo8awkjo/2013-06-10%20at%203.08.39%20PM.png)]]

The exact same problem happens regardless of the theme used. I can also consistently reproduce on WordPress 3.5.1 as well as with trunk. No plugins installed.

I've tracked the bug down to the, [http://core.trac.wordpress.org/browser/trunk/wp-includes/formatting.php#L89 opening quote regex] in `wp_texturize()`.

My regex foo isn't good enough to figure out a proper solution here unfortunately."	jkudish
Future Releases	16957	wpuntexturize - problem with numbers and non-breaking spaces		Formatting	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-03-24T10:21:33Z	2013-01-14T01:37:56Z	"1) Insert following code into HTML editor and publish.

{{{
New <strong>Year ""2011"" will be</strong> fantastic.
}}}

Then look at website:

{{{
<p>New <strong>Year &#8221;2011&#8243; will be</strong> fantastic.</p>
}}}

You can see wrong html quotes.

2) I also worked with TinyMCE editor (only writing simple text, paragraphs, strong, moving some parts of text by CTRL+C and CTRL+V). But after publishing, there were hidden non-breaking spaces in text. There were on different places, for example before ""("" and after characters ""."", ""í"", ""é"", etc. But they were random. I am not sure how it can be caused? Non-breaking strings were not visible and also not transformed into &nbsp; HTML entity on website. I noticed them only in HEX editor, when examining HTML source code (C2 A0).

Of course, when these non-breaking spaces were before (or after) quotes, then quotes were not recognized regurarly by wpuntexturize, example:

{{{
Nemám žádné ""úžasné"" schopnosti.
}}}

Is transformed by wpuntexturize into:


{{{
<p>Nemám žádné &#8221;úžasné&#8221 schopnosti</p>.
}}}

You can see wrong open quote:

{{{
instead of &#8220 there is &#8221;
}}}

But only when hidden non-breaking space (C2 A0) is between žádné a ""úžasné""."	pavelevap
Future Releases	9306	Additional smart quote suggestion		Formatting		low	trivial	Future Release	enhancement	new	close	2009-03-09T05:09:36Z	2011-02-05T11:04:09Z	"If a user writes a post that contains a quotation inside parentheses, the open quote mark is not used. I suggest that when a quotation mark (double or single) is used after an open parenthesis, it should be a left-quote “ instead of a right quote ”. In order to be as complete as possible, it would probably be best to ensure that this is only done in the event that white space is used prior to the open parenthesis so as to prevent it printing the wrong one if, say, a sad-face smiley is used inside a quotation, like so:

'''''She told me, ""Aw, you make me a sad panda now. :(""'''''

If it's done so that it will only open the quote correctly after white space \s or a carriage return, I think that will cover the vast majority, if not all, of the situations where it would need to be used."	cloak42
Future Releases	16790	Functional spec for wpautop		Formatting		normal	minor	Awaiting Review	enhancement	reviewing		2011-03-07T22:06:30Z	2012-09-17T05:55:42Z	"I've put together an algorithm-based [http://www.mrclay.org/wpautop-functional-specification/ functional spec] that I hope could be useful in maintaining wpautop. Also might be handy is this combination of [http://code.google.com/p/mrclay/source/browse/trunk/tests/php/MrClay/AutoP/wpautop-fails.in.html wpautop failure cases].

The algorithm is based on work I've started on a DOMDocument-based implementation (a project I contribute to needs an MIT-licensed version), and although it's incomplete and slow, it does a bang-up job so far.

DOMDocument may just be too slow or strict in its parsing to allow the variety of markup that wpautop needs to accept, but it's ace at the level of surgical precision needed to do this right."	mrclay
Future Releases	20120	Space before slash to close BR		Formatting	3.4	normal	trivial	Awaiting Review	enhancement	new		2012-02-25T04:08:58Z	2012-02-28T14:57:50Z	"Kind of a petty, I admit, but I noticed http://codex.wordpress.org/WordPress_Coding_Standards shows this as the standard, and I figured I'd help out by checking if any such occurrences exist (using the following):

`find -name '*.php' -type f | xargs egrep -n ""<br\/>""`

Diff attached (my first)...but I won't have my feelings hurt if the ticket is closed and I am banned from trac :)"	bananastalktome
Future Releases	22402	Stripping non-alphanumeric multi-byte characters from slugs		Formatting		normal	normal	Awaiting Review	enhancement	new		2012-11-10T05:07:10Z	2012-11-22T03:13:41Z	"`sanitize_title_with_dashes()` strips non-alphanumeric characters from a title to create a slug. Unfortunately it only strips ASCII non-alphanumeric characters. Apart from a few exceptions, all multi-byte characters are preserved. This means all non-Western (and plenty of Western) non-alphanumeric characters end up in the slug as they're treated just like any other multi-byte character.

As an example, here are some common non-alphanumeric Chinese characters which would ideally be stripped from slugs, but are not:

 * 。 (U+3002, Ideographic Full Stop, %E3%80%82)
 * ， (U+FF0C, Fullwidth Comma, %EF%BC%8C)
 * ！ (U+FF01, Fullwidth Exclamation Mark, %EF%BC%81)
 * ： (U+FF1A, Fullwidth Colon, %EF%BC%9A)
 * 《 (U+300A, Left Double Angle Bracket, %E3%80%8A)
 * 》 (U+300B, Right Double Angle Bracket, %E3%80%8B)

Obviously it would be impractical to make a list of ''all'' the non-ASCII characters we want to strip from slugs. The list would be gigantic.

So the question is, would it be possible to use Unicode ranges to blacklist (or whitelist) whole ranges of characters to be stripped from (or preserved in) slugs? Is this practical or even desirable?

Or would it make more sense to continue using a list of just the most common multi-byte characters to be stripped?

The latter makes a whole lot more sense, but the former is a more complete solution.

Thoughts?"	johnbillion
Future Releases	11616	Text copied form visual editor don't store font color		Formatting	2.9	normal	minor	Future Release	enhancement	new	close	2009-12-25T09:14:51Z	2011-03-26T18:56:14Z	"if i copy something out of the post editing tool, and if i paste it into another, the color is not copied too.
Just the ""bold / underline ect...""

i have to ajust the color every time myself :(
"	warsheep
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	20522	the sanitize_file_name_chars filter and ch(0)		Formatting		normal	minor	Awaiting Review	enhancement	new	needs-unit-tests	2012-04-23T08:26:28Z	2012-04-24T00:41:12Z	"the sanitize_file_name_chars filter is tricky to use due to the chr(0) ending the array :

both 
{{{
special_chars[] = $my_char; 
}}}
and 
{{{
array_push($special_chars, $mychar);
}}}
have no effect.

so the only way to add some char to the array is to use array_unshift :
{{{
array_unshift($special_chars, $mychar);
}}}

adding 

this is mostly a php issue, but it could be useful to add some notice to the WordPress documentation.

"	olivM
Future Releases	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
Future Releases	9437	Allow the use of inline SVG in posts		Formatting	2.5	normal	normal	Future Release	feature request	reopened		2009-04-01T13:39:25Z	2011-03-31T07:18:17Z	"My WordPress 2.5 install serves the application/xhtml+xml MIME type (true XHTML) for the purposes of inlining SVG which I've done on my 'blog chrome'.  However, if I try to inline SVG in the contents of a post as follows:

<svg xmlns=""http://www.w3.org/2000/svg"">
  <circle cx=""50"" cy=""50"" r=""30"" fill=""blue"">
    <animateTransform attributeName=""transform"" type=""scale"" to=""1.5"" dur=""2s"" fill=""freeze""/>
  </circle>
</svg>

WordPress mangles it into:

<svg xmlns=""http://www.w3.org/2000/svg""><br />
  <circle cx=""50"" cy=""50"" r=""30"" fill=""blue""><br />
    <animatetransform attributeName=""transform"" type=""scale"" to=""1.5"" dur=""2s"" fill=""freeze""/><br />
  </circle><br />
</svg>

There are two problems with this:

1) WordPress converts the <animateTransform> element into a <animatetransform> element.  WordPress should at least preserve the case of the element (whether this is on a whitelist of SVG elements or all elements I don't care).  List of SVG elements are here: http://www.w3.org/TR/SVG11/eltindex.html

2) The extra <br /> elements.  These are forgivable since the elements are simply ignored by the browser's SVG parser.

Can someone confirm the behavior in WordPress 2.7.x?"	codedread
Future Releases	17993	the_content vs get_the_content		Formatting	3.2	normal	normal	Awaiting Review	feature request	new	close	2011-07-05T14:00:01Z	2012-09-14T17:28:19Z	"Wordpress lacks of a main function: obtain full formatted ""content"" without echo! Maybe good to add a param to the_content() like echo(bool)?

I wrote it:

{{{
function the_content_noecho($more_link_text = null, $stripteaser = 0) {
       $content = get_the_content($more_link_text, $stripteaser);
       $content = apply_filters('the_content', $content);
       $content = str_replace(']]>', ']]&gt;', $content);
       return $content;
   }
}}}
"	merlinox
Future Releases	11023	Gallery Category Doesn't change with article		Gallery		normal	normal	Future Release	defect (bug)	new		2009-10-24T01:49:09Z	2009-12-08T00:56:23Z	Lets say I have a default category setup called Drafts that all articles go into at first by default. Then on completing the article before posting it live, I movie it to another category called News (no longer having the draft category ticked also). If I've added an image with that article that I click to view a bigger picture of in the gallery page (image.php). It still shows it as being listed under the Drafts category, while the article itself is listed under just News category.	mrgtb
Future Releases	23873	Gallery shortcode orderby does not support multiple column sorting		Gallery	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-03-27T21:13:53Z	2013-04-05T12:42:03Z	"In wp-includes/media.php, function gallery_shortcode, lines 689-694 are:

{{{
// We're trusting author input, so let's at least make sure it looks like a valid orderby statement
if ( isset( $attr['orderby'] ) ) {
	$attr['orderby'] = sanitize_sql_orderby( $attr['orderby'] );
	if ( !$attr['orderby'] )
		unset( $attr['orderby'] );
}
}}}

The sanitize_sql_orderby function requires commas between multiple column names. If you enter, for example orderby=""menu_order ID"", the lack of a comma causes the parameter to be deleted from the query.

Just after this test, on line 698, a multi-column sort without the comma delimiter is used as the default value.

If you enter commas to get past the sanitize_sql_orderby test, logic in wp-includes/query.php, function get_posts will not accept the commas (lines 2358 - 2361) and all but the last of the columns are ignored.

This issue should be considered along with those raised in #17065 and #16584. Thank you."	dglingren
Future Releases	22773	"""Gallery Settings"" should be extensible"		Gallery	3.5	normal	minor	Awaiting Review	enhancement	new		2012-12-06T03:17:19Z	2013-01-06T02:29:57Z	"This isn't necessarily new to 3.5, but now that we have a great gallery management system, I think we need to allow developers to customize the Gallery Settings fields (other than Link To / Columns / Random).

My specific use - which I think is common - is a completely custom gallery shortcode for a client. First and foremost, the client would like to be able to ""title"" the gallery itself, so a hook allowing the addition of custom field(s) would be needed. Ideally, the default fields would also be filterable so they can be removed as well (though I suppose we can do that with CSS now): for instance, most custom gallery implementations don't use the ""columns"" option."	jakemgold
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	17142	Prettier gallery display and navigation through core		Gallery	3.3	normal	normal	Awaiting Review	feature request	reopened		2011-04-15T16:14:13Z	2012-07-13T22:44:10Z	"WordPress gallery display and navigation typically feels rather crude from the user point of view. With digital cameras dumping images as IMG_XXXX or long numeric strings, the default image titles are usually prominent and ugly in most of the themes I've tested (see attachments for examples). Some themes use thumbnail navigation instead, but those implementations also feel dated in many (most?) cases.

I realize that the theory is display/navigation is determined by the themes, and that display/navigation can be greatly altered via various plugins...  but the reality of how this plays out results in a default user experience that simply feels outdated. 

Many (most?) themes seem pretty unimaginative in their gallery output and IMHO a more elegant out-of-the-box display and navigation experience seems like it would really be useful for all WordPress users. I would think most users expect something like a Lightbox experience at minimum, but I am not ideologically tied to any particular solution. 

Is there something we could do on the core side to strongly encourage (or even gently enforce) a prettier default construct? 
"	hew
Future Releases	16909	some Location headers are using relative url's (2)		General	3.1	normal	normal	Awaiting Review	defect	new		2011-03-21T00:25:26Z	2011-04-02T13:24:37Z	"I started this in #14062 and already did some fixes for 3.1.

Just collecting some more and providing patches."	hakre
Future Releases	18701	"""hierarchical"" argument for get_pages() does nothing"		General	3.0	normal	normal	Awaiting Review	defect (bug)	new		2011-09-19T06:48:32Z	2011-11-16T00:17:33Z	"The `hierarchical` argument for `get_pages()` is never actually used. It is in an `if` statement, but one that requires `child_of` to also be set:

{{{
if ( $child_of || $hierarchical )
	$pages = & get_page_children($child_of, $pages);
}}}

Props Vynce Montgomery for pointing this out to me."	Viper007Bond
Future Releases	24023	3.5/wp-includes/functions.php : missing break statement		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	reopened		2013-04-10T02:44:54Z	2013-04-10T18:59:20Z	"Line 263:

{{{
switch ( $token ) {
case 's' :
if ( '""' !== $data[$length-2] )
return false;
case 'a' :
}}}

Need ""break"" after ""return false"", because return happens only if condition met. Otherwise - falls to case 'a'
"	tivnet
Future Releases	24480	404 error when creating a new site when WP is in a subfolder		General		normal	minor	Awaiting Review	defect (bug)	new		2013-06-01T20:00:22Z	2013-06-01T20:00:22Z	"With WP placed in a subfolder, i.e.:


{{{
/index.php
/wp-config.php
/wp <-- WP in here
}}}

You get a 404 error when creating a site. It redirects you to /wp-admin/install.php instead of /wp/wp-admin/install.php"	Denis-de-Bernardy
Future Releases	24030	Add an action for when nonce verification fails		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-10T10:21:37Z	2013-04-10T10:21:37Z	"Currently when a plugin (or core) calls `check_admin_referer()` there is no way for auditing (or debugging) plugins to hook in and record an event that the nonce check failed.

Previously it was possible to use the `explain_nonce_$nonce` filter to do this, but that was removed in [21133].

If a plugin wants to record an event for a failing nonce, it'll need to call wp_verify_nonce() manually itself, and die afterwards, or call `check_admin_referer()` after verifying the nonce itself for logging purposes.

I'd suggest either resurrecting the previous filter as an action (for back compat) or adding a new nonce failure hook."	dd32
Future Releases	23905	Add_post_meta strips slashes		General	2.5	normal	normal	Awaiting Review	defect (bug)	new		2013-03-30T00:20:29Z	2013-03-30T05:32:01Z	"Let's assume that JS generated an object that I want to store in custom field. Everything goes smooth when I convert it back and forth from JS to PHP and from PHP to JS (using json_encode() and json_decode()) and it even works when I do update_post_meta() manually in my file but this stops working as soon as WordPress Importer tries to load it from XML file (in XML it's still valid object) using add_post_meta().

This is the code from importer from the bottom of process_posts() function:

{{{
if ( $key ) {
	// export gets meta straight from the DB so could have a serialized string
	if ( ! $value )
		$value = maybe_unserialize( $meta['value'] );
		$value = '{""0"":{""type"":""text"",""text"":""""},""1"":{""type"":""html"",""html"":""<div class=\""cssclass\"" style=\""margin-top: 3em;\""><p>here goes html</p></div>"",""css_class"":""""}}'; // I added this for test purposes

	add_post_meta( $post_id, $key, $value );
	do_action( 'import_post_meta', $post_id, $key, $value );
}}}


This is an object:

{{{
{""0"":{""type"":""text"",""text"":""""},""1"":{""type"":""html"",""html"":""<div class=\""cssclass\"" style=\""margin-top: 3em;\""><p>here goes html</p></div>"",""css_class"":""""}}
}}}


It strips slashes from HTML tags (before each double quote sign) from objects that are stored as strings. I bet it shouldn't happen. Why would add_post_meta strip slashes or anything if XML explicitly says:


{{{
<wp:meta_value><![CDATA[{""0"":{""type"":""text"",""text"":""""},""1"":{""type"":""html"",""html"":""<div class=\""cssclass\"" style=\""margin-top: 3em;\""><p>here goes html</p></div>"",""css_class"":""""}}]]></wp:meta_value>
}}}

which in XML language is considered ""use as is. Do not modify"". I think that it might be a bug."	Looimaster
Future Releases	13926	Adding 'page-attributes' to a custom post type slows down edit screen in the admin		General	3.0	normal	normal	Future Release	defect (bug)	new		2010-06-16T20:01:17Z	2010-10-28T01:52:55Z	"When I add 'page-attributes' to a custom post type it takes roughly 1.5 to 2 min for the edit screen to load...  When I remove 'page-attributes' edit screen load is extremely fast.

Under the post type i created I have 5000+ entries."	granulr
Future Releases	16672	Admin Bar and param href = FALSE		General	3.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-02-26T00:21:52Z	2011-02-27T11:21:37Z	"Current i dont find an solution to add an element in the admin bar with a a-tag inside the li-tag. But the function add_menu has an param href and is also possible to add the value false, but the a-tag ist always visible


maybe a fix on wp-includes/class-wp-admin-bar.php

{{{
	/* Helpers */
	function recursive_render( $id, &$menu_item ) { ?>
		<?php
		$is_parent =  ! empty( $menu_item['children'] );

		$menuclass = $is_parent ? 'menupop' : '';
		if ( ! empty( $menu_item['meta']['class'] ) )
			$menuclass .= ' ' . $menu_item['meta']['class'];
		?>

		<li id=""<?php echo esc_attr( ""wp-admin-bar-$id"" ); ?>"" class=""<?php echo esc_attr( $menuclass ); ?>""><?php
			if ( ! empty( $menu_item['href'] ) ) : ?>
				<a href=""<?php echo esc_url( $menu_item['href'] ) ?>""<?php
					if ( ! empty( $menu_item['meta']['onclick'] ) ) :
						?> onclick=""<?php echo esc_js( $menu_item['meta']['onclick'] ); ?>""<?php
					endif;
				
				if ( ! empty( $menu_item['meta']['target'] ) ) :
					?> target=""<?php echo esc_attr( $menu_item['meta']['target'] ); ?>""<?php
				endif;
				if ( ! empty( $menu_item['meta']['title'] ) ) :
					?> title=""<?php echo esc_attr( $menu_item['meta']['title'] ); ?>""<?php
				endif;
				
				?>><?php
			endif;
			
			if ( $is_parent ) :
				?><span><?php
			endif;

			echo $menu_item['title'];

			if ( $is_parent ) :
				?></span><?php
			endif;

			if ( ! empty( $menu_item['href'] ) ) : ?></a><?php endif; ?>

			<?php if ( $is_parent ) : ?>
			<ul>
				<?php foreach ( $menu_item['children'] as $child_id => $child_menu_item ) : ?>
					<?php $this->recursive_render( $child_id, $child_menu_item ); ?>
				<?php endforeach; ?>
			</ul>
			<?php endif; ?>

			<?php if ( ! empty( $menu_item['meta']['html'] ) ) : ?>
				<?php echo $menu_item['meta']['html']; ?>
			<?php endif; ?>
		</li><?php
	}
}}}
"	Bueltge
Future Releases	20927	Ampersand inside HTML comment causes wp_insert_post to loop infinitely		General	3.3.2	normal	normal	Awaiting Review	defect (bug)	new		2012-06-12T19:54:46Z	2012-06-14T13:09:40Z	"I'm encountering an issue with wp_insert_post where, when the post_content contains an HTML comment containing an ampersand (ie, ""<!-- & -->""), wp_insert_post seems to be getting stuck in an infinite loop. As far as I can tell, it is endless escaping the & into &amp; over and over.

I've attached a small script that reproduces this error; you need to replace the HTTP_HOST and the path to wp-load.php to reflect your own machine for it to run. I've reproduced this issue on two different machines, both running Ubuntu 12.04, one on Wordpress 3.3.1 and the other on Wordpress 3.3.2.

The most bizarre thing about this issue, to me, is if you move the contents of the includeFiles() function out of the function and into the main body of the script, the issue no longer occurs. Somehow, including wp-load.php from a function is causing the infinite loop."	jpayette
Future Releases	21729	Better logic for comments email notification		General		normal	normal	Awaiting Review	defect (bug)	new		2012-08-29T15:26:37Z	2012-11-22T03:49:45Z	"Please see attached patch.

- If comment_author_email is known, it can be used in ""From"" email header.

- Also in ""Reply-To"" header we can use comment_author.

I am not sure if there is any reason for current logic, but my friend noticed it and he thought that this way it would be better..."	pavelevap
Future Releases	16487	Bug wp_new_user_notification() when using it in multisite mode		General	3.0.5	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-02-08T09:04:08Z	2011-02-08T12:07:48Z	"In the file ""wp-includes/pluggable.php""
into the function named ""wp_new_user_notification""

$blogname = wp_specialchars_decode(get_option('blogname'), ENT_QUOTES);

This is correct but, in mutisite mode,

that one return the site name where you are logged into, not the blogname you are going to create.
$message .= wp_login_url() . ""\r\n"";

for example, i try to create test1.mynamesite.com
i'm logged on primarysite.mynamesite.com with my super admin account.

Into the mail i recieved, with ""Your Username and password""
the url is ""http://primarysite.mynamesite.com/wp_login.php""

it had to be ""http://test1.mynamesite.com/wp_login.php"".

In the other mail recieved with the complete message, acces code and url, all is perfect, just in the mail when adding the user to the new site."	wp_user59
Future Releases	17442	CSS selector #wpadminbar * overwrites accessibility generic selectors like screen-reader-text		General	3.2	normal	normal	Awaiting Review	defect (bug)	new		2011-05-15T10:42:59Z	2011-05-15T12:52:23Z	"I just was looking to update one of my plugins for 3.1/3.2 making use of the new admin bar.

My plugin makes use of the `.screen-reader-text` CSS class but it is overwritten in the admin-bar by `#wpadminbar *`"	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	14268	Comments editor HTML tag		General	3.0	normal	normal	Future Release	defect (bug)	new		2010-07-10T19:16:16Z	2010-11-22T18:22:42Z	"With a vanilla (2.8.4 -> 3.0) installation, if you go and edit the comment from Mr Wordpress, you will see that in the editor you can find the HTML code of the apostrophe for ""post's"".

{{{
Hi, this is a comment.<br />To delete a comment, just log in and view the post&#039;s comments. There you will have the option to edit or delete them.
}}}

The problem comes with a production env with European languages where comments are full of accented letters that make the reading almost impossible."	pkirk
Future Releases	20081	Custom Post Type/Custom Taxonomy Does not filter.		General	3.3.1	normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2012-02-20T08:04:56Z	2012-02-20T08:41:56Z	"I have tested this on 4 different sites and found the same issue. At first I thought it was the code I copied then I realized the issue was happening with core. 

'''
Steps to produce:''' 
Use register_post_type to add a post type, say ""objects""

Use register_taxonomy to create custom tax, say ""attributes""

Be sure to have 'show_ui' => true

Create a post, give it a tax. IE: attribute1

Create a second post, give it a different tax. IE: attribute2

On the menu navigate to your tax menu page

here it will list attribute1 and attribute2. 

It will show 1 post in each, and the number 1 is a link to edit.php 
where it creates this URL string:
yoursite.com/wp-admin/edit.php?post_type=objects&attribute=attribute1

'''Expected Result:'''
The page should now be filtered down to JUST posts that have that attribute. 


'''Actual Result:'''
All Posts are still visible. Filtering has no effect. 

I found this by creating custom columns and with my switch listing links to the Tax's to be filtered. I've never gotten it to work. 
I do have a great script I believe by YOAST that creates a drop down to filter Tax's but this actually changes the global query itself. 

"	DennisSmolek
Future Releases	20438	Custom Post Types with Post Format support aren't registered against post_format taxonomy		General		normal	normal	Awaiting Review	defect (bug)	new	close	2012-04-13T16:56:40Z	2012-11-20T18:15:16Z	"When a custom post type adds support for {{{post-formats}}}, this doesn't actually register the {{{post_format}}} taxonomy for the post_type.

Here's a quick test:

{{{
add_action( 'init', function() {
        register_post_type( 'not-post', array( 'supports' => 'post-formats' ) );
        global $wp_taxonomies;
        var_dump( 'post supports post_format:', in_array( 'post', $wp_taxonomies[ 'post_format' ]->object_type ) );
        var_dump( 'not-post supports post_format:', in_array( 'not-post', $wp_taxonomies[ 'post_format' ]->object_type ) );
} );
}}}

The {{{post_format}}} taxonomy doesn't get returned when {{{get_object_taxonomies}}} is called for the custom post type and one side-effect of this is that the {{{post_format_relationships}}} cache does not get flushed by {{{clean_object_term_cache}}} leading to stale values when a post format is changed.

(The {{{post}}} post_type is immune to this because core registers the {{{post_format}}} taxonomy with it.)

When a post_type adds support for post-formats, an explicit association should be made between the post_type and the {{{post_format}}} taxonomy."	batmoo
Future Releases	15837	Custom Taxonomy: Admin Menu Not Selecting Current Item		General	3.0.3	normal	normal	Awaiting Review	defect (bug)	new		2010-12-15T21:57:24Z	2011-01-09T14:01:43Z	"Story: Developing a plugin that adds a Custom Post Type and then a Taxonomy.

Problem: Adding the Taxonomy and displaying the Menu Item on the Admin section, when selecting the menu item - there seems to be a difference in functionality depending on what tag the Taxonomy hooks onto.

For example code:
{{{
      register_taxonomy(
        'mytaxonomy',
        'myposttype',
        array( 
          'labels' => array(
            'name' => 'Manage XXX',
            'add_new_item' => 'Add New XXX',
            'new_item_name' => 'New XXX Name',
            'add_new' => 'Add New XXX',
            'singular_name' => 'XXX'
          ),  
          'public' => false,
          'publicly_queryable' => true,
          'show_ui' => true,
          'hierarchical' => true,
          'rewrite' => array(
            'slug' => 'XXX',
            'with_front' => false
          ),  
          'query_var' => 'XXX'
        )
      );
}}}

The above code adds the Menu Item for the Taxonomy to the new Custom Post Type menu I created.

When I select the new Taxonomy...it ""open"" or ""behaves"" as though it expects to see it under the ""post"" tag.

It does not select the Taxonomy Menu Item as ""current"".

Expected result: Select Taxonomy Menu Item -> Menu Item obtains CSS class of ""current"".

Actual result: Select Taxonomy Menu Item -> Menu Item doesn't obtain a CSS class and IF the Posts menu was ""collapsed"" it expands.

Now - conversely if I add the Taxonomy Menu Item to the tag ""post"" - it DOES add the CSS class.

This seems to be inconsistent functionality and I believe that it's not there's something surrounding it that has to be malfunctioning."	sterlo
Future Releases	16009	Define z-index on the new admin bar		General	3.1	normal	normal	Future Release	defect (bug)	reopened		2010-12-28T15:41:24Z	2011-01-06T12:08:20Z	"Proposal for z-index to be defined on the new admin bar (so that it will work in harmony with browser toolbar --> Web Develoepr Toolbar's ""Display Element Information"" Feature)

When the new admin toolbar is showing,
crucial information from the Web Developer Toolbar's 
""Display Element Information"" balloon becomes hidden.

Specifying a z-index for the admin toolbar seems to resolve this problem.

ie.
I changed line 92 of class-wp-admin-bar.php, 
FROM:

{{{
<div id=""wpadminbar"">
}}}

TO:

{{{
<div id=""wpadminbar"" style=""z-index:1000;"">
}}}


It seems that the z-index value is somewhat arbitrary to getting these two toolbars to work in harmony... as I've tried values ranging from 0 to 1000, and they all worked."	BlueKachina
Future Releases	10902	Display problem with exclude option in wp_list_pages		General	2.8.4	normal	normal	Future Release	defect (bug)	new	reporter-feedback	2009-10-04T19:45:38Z	2011-04-02T11:50:55Z	"Create pages A,B,C and D, A parent of B, B of C and C of D[[BR]]
A[[BR]]
-B[[BR]]
--C[[BR]]
---D[[BR]]

call in a template 
<?php wp_list_pages(""exclude=6""); ?>
(6 is the ID of page B)

I get this display :[[BR]]
* A[[BR]]
* C[[BR]]
* D[[BR]]

when I expect :[[BR]]
* A[[BR]]
* C[[BR]]
-* D[[BR]]"	toutantic
Future Releases	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
Future Releases	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
Future Releases	21204	Encoding problem with errors and warnings		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-07-09T16:31:04Z	2012-07-09T22:01:05Z	"There are several functions for debugging and their messages are also localized. For example _deprecated_argument(), _doing_it_wrong(), etc. But when these functions are fired, encoding of the whole administration (not only error messages) is damaged (see attached screenshot).

It is not very good because even if debugging is turned off, some errors can be still triggered - for example trigger_error() in ms_subdomain_constants() function, etc."	pavelevap
Future Releases	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
Future Releases	15674	Error when trying to logout		General	3.0.2	normal	normal	Awaiting Review	defect (bug)	reopened	reporter-feedback	2010-12-03T23:46:21Z	2011-08-07T20:51:51Z	"I get this error when trying to logout of WordPress 3.0.1 & 3.0.2:

""This webpage is not available. The webpage at http://my.site.com/wp-login.php?action=logout&_wpnonce=12c23f0af8 might be temporarily down or it may have moved permanently to a new web address.""

and

""Error 101 (net::ERR_CONNECTION_RESET): Unknown error.""

in Google Chrome and

""The connection was reset""

in Firefox. Both browsers running on Windows XP SP3. I tested this on another computer running Windows XP SP3 (different ISP) and got the same error in Firefox.

Strangely, I do not get these errors at all on my Mac, in both Chrome and Firefox; they both logout correctly. It also works correctly on my iPhone.

I've tried cleaning cache and cookies in both browsers, reseting my sub-domain in my host's control panel, changing to the default theme; none of which worked at all.  Must be some kind of bug, lots of reports about this in the forums.

See thread here:  http://wordpress.org/support/topic/error-when-trying-to-logout?replies=9"	interconnect
Future Releases	24554	Errors in post.php seems silent.		General		normal	normal	Awaiting Review	defect (bug)	new		2013-06-10T13:49:15Z	2013-06-10T13:49:15Z	"wp-includes/post.php, around line 2933.

if ( 'default' != $page_template && ! isset( $page_templates[ $page_template ] ) ) {

The defined template did not exist in theme, and as a result my custom fields was not saved. The error was silent. (I as a user did not notice it).

Maybe the error should get displayed to the user?"	nilo85
Future Releases	24470	Fire Fox 21.0 FireBug Reporting Error from jquery.js?ver=1.8.3		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-05-30T22:39:32Z	2013-05-30T23:15:36Z	"After searching, there appears to be no previous reporting of this issue. I believe it is being caused by a recent update to the Fire Fox Browser after 3.5.1 release. I haven't seen it come up before FF V. 21.0.
{{{
uncaught exception: DataCloneError: The object could not be cloned.
https://website.com/wp-includes/js/jquery/jquery.js?ver=1.8.3
Line 2
}}}

This error is consistent on return url after payment is processed via PayPal. As many as 92 cyclical references. 

Some references for a solution:

http://stackoverflow.com/questions/7506635/uncaught-error-data-clone-err-dom-exception-25-thrown-by-web-worker

The original exception was most likely thrown because you tried passing a host object to the web worker (most likely a dom element). Your subsequent attempts don't throw the same error. Remember two key points: there isn't shared memory between the different threads, and the web workers can't manipulate the DOM.

postMessage supports passing structured data to threads, and will internally serialize (or in some other way copy the value of the data recursively) the data. Serializing DOM elements often results in circular reference errors, so your best bet is to map the object you want serialised and extract relevant data to be rebuilt in the web worker.

Further Explanation to this cause:

https://developer.mozilla.org/en-US/docs/Web/API/Worker?redirectlocale=en-US&redirectslug=DOM%2FWorker#postMessage%28%29

 

"	robert.lang
Future Releases	15619	General Settings Tab Not Allowing trailing URL slash to be stored in Site & WordPress address (URL)		General	3.0.1	normal	normal	Future Release	defect (bug)	reopened	dev-feedback	2010-12-01T02:35:11Z	2011-01-21T10:15:11Z	"**Thank you for all of the efforts you've made regarding plugins easier to maintain - I deeply appreciate it.** 

When WordPress is installed in a subfolder, attempts to add the trailing slash currently will not save properly. From this URL:
http://www.domain.com/wordpressinstalledinfolder/wp-admin/options-general.php

The General Settings Tab - WordPress address (URL)
The General Settings Tab - Site address (URL)

Want to enter ""http://www.domain.com/wordpressinstalledinfolder/""
***it won't let me enter a trailing slash on the end like it will in other URL fields on the site.***

Request: Please tweak this field to allow storage of folder trailing slash.




"	dsquared
Future Releases	17445	Give a speed kick to combined is_serialized() + is_serialized_string() + maybe_unserialize() usage		General	3.2	normal	normal	Awaiting Review	defect (bug)	new		2011-05-15T14:13:18Z	2011-05-15T21:14:14Z	"In #17129 is_serialized_string() has been speed up by 23%. That was for the function itself.

However, that function is used in contexts that make the call to is_serialized() directly or indirectly via maybe_unserialize().

Most often these calls are redundant and must not be done at all.

If preconditions are already met, is_serialized_string() can be replaced with a simple check for the 's' or 'S' format and maybe_unserialize() can be replaced with @unserialize($data) as that's the code executed in maybe_unserialize() when is_serialze() had returned true on $data;"	hakre
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	19383	Hide post formats next to post titles if the active blog theme does not support post formats		General	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-11-28T18:16:12Z	2011-11-29T18:47:55Z	"If I'm using a theme that supports post formats—e.g. Twenty Eleven—then next to each title on `wp-admin/edit.php` I'm able to see not only the title name but also the post format that corresponds to its respective post.

If I switch to a theme that does not support post formats at all I am still able to see post formats associated with their respective posts.

This is not good for a few reasons:

* Showing a post format next to a title while a theme that doesn't support post formats is active is confusing. ""Why does my post have the word Image/Link/Status/Quote by it? What does that mean?""
* There is no way to edit or remove a post format associated with a post when a theme that does not support post formats is active, so the labels are useless.

When a theme that does not support post formats is active those format labels should be hidden. The posts can of course still retain their formats in case a user switches back to a theme that supports theme, but otherwise they should be hidden."	philiparthurmoore
Future Releases	18102	IE8 and wp_tiny_mce has broken Link button		General	3.2	normal	normal	Awaiting Review	defect (bug)	new		2011-07-13T14:07:43Z	2011-07-13T17:57:57Z	"With IE8 and custom-generated WYSIWYG editors created with wp_tiny_mce, the link button doesn't work correctly.  What happens is quite interesting:

On the first click, the Add/Edit dialog link box appears full sized, but empty.

Dismissing the box and clicking the link button again will give you just the Add/Edit link dialog box's title, but not even a box.

Dismissing that box and clicking on it a third time will finally generate an Add/Edit link form in the dialog box, but it won't be functional.

As far as I can tell, there are no JavaScript errors displayed.

This works correctly in Chrome, FireFox, and IE9. The problem only exists in IE8 as far as I can tell.  I tested on 3.2 and 3.2.1

The issue occurs with a default theme, but not with all plugins disabled (because plugins are required to create such a WYSIWYG box).  The issue does NOT exist on the default post/page add/edit screens.  Examples of plugins affected are WYSIWYG Widgets (http://wordpress.org/extend/plugins/wysiwyg-widgets/) and Rich Text Tags (http://wordpress.org/extend/plugins/rich-text-tags/), although I discovered the issue while developing my own plugin.

I also put together a bare-bones plugin to help verify the issue in case that helps (see the new menu item in Settings):
http://dl.dropbox.com/u/5148765/lems_wysiwyg_test.php  (requires WP 3.2+)

While it's possible that the real problem is how we're calling wp_tiny_mce (and I certainly apologize if that's the case), all 3 of us developers have run into this issue independently.

Let me know if you need any more info!"	MadtownLems
Future Releases	23478	"Impossible to view posts titled ""WP Content"" or ""WP Includes"" with some forms of permalinks"		General		normal	normal	Awaiting Review	defect (bug)	new	close	2013-02-15T06:33:05Z	2013-02-15T09:35:07Z	"Posts titled ""WP Content"" or ""WP Includes"" (without quotes) are impossible to view when using the following forms of permalinks:

1. /%postname%
2. /%postname%/

A post titled ""WP Content"" will have a permalink of either http://example.com/wp-content or http://example.com/wp-content/, '''both will show a blank page'''.

A post titled ""WP Includes"" will have a permalink of either http://example.com/wp-includes or http://example.com/wp-includes/, '''both will show the directory index of the wp-includes directory'''.

WordPress should either:

a) make it possible to view both posts normally

b) warn the user or make it not possible to have a combination of some post titles and some certain forms of permalink."	kjasdu
Future Releases	21658	Meaningless adjacent post links for pages		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-22T12:34:26Z	2012-08-22T12:34:26Z	"In WP 3.3 we removed a number of obsolete <link> elements from the page header leaving just those with rel=""next"" and rel=""prev"" generated by function adjacent_post_rel_link_wp_head() in file wp-includes/link-template.php [see #18128].

This change brings the function of these links into sharper relief and raises several concerns. Presently, they are generated only for singular pages/posts that are not attachments.

Such links make some kind of sense for ordinary posts, because these can be considered to be part of an ordered collection where the next/previous relationship is meaningful. It may also make sense for custom post types, depending on the use to which they are being put.

For pages, however the links generated refer to the next/previous pages as they happen to be stored in the WP database and these are unlikely to have any meaningful relation to the originating page.

Others have reported performance and other problems with browsers such as Firefox that use these links to prefetch content [see #12603, #14382 and #19018].

You can see their point! If I'm viewing page ""about"" what are the chances that I will next want to view the page ""contact"" just because this happens to have the next sequential ID in the WordPress database?

At the very least, I believe that these links should not be generated for pages.  Better still would be to follow Google's advice [see #18672] and use these just for paginated content (i.e. individual posts/pages [with <!--nextpage-->] or archives [including blog home]). Some potential patch code is available against #18660 which raised a similar issue. Links between adjacent posts can be left to the usual navigation elements within the page body."	mdgl
Future Releases	16584	Media Gallery sorts images by two columns despite get_posts not supporting this properly		General	2.6	normal	normal	Future Release	defect (bug)	new		2011-02-17T22:25:55Z	2011-02-20T17:08:05Z	"In the get_media_items function in wp-admin/includes/media.php, attachments are sorted first by menu order, then by post ID by the following line:

{{{
$attachments = get_children( array( 'post_parent' => $post_id, 'post_type' => 'attachment', 'orderby' => 'menu_order ASC, ID', 'order' => 'DESC') );
}}}

However, the get_posts in wp-admin/includes/query.php function does not properly support this. It splits up orderby by spaces, and then throws out 'ASC,' as it does not match a valid value. Due to a lucky coincidence, it turns into ORDER BY menu_order, ID DESC which still works in the same way.

I often want to display the first x uploaded images to a post, but allow changing which images are considered the first x via menu_order. If I solely order by ID ASC, that won't work. If I solely order by menu_order ASC, that won't work either, since the ones at the top of the list (latest uploaded) become first in the menu order. The only way to get it to work is to sort by menu_order DESC, ID ASC - but using 

{{'orderby' => 'menu_order DESC, ID', 'order' => 'ASC'}}

doesn't not work since the 'DESC,' gets ignored.

There are two possible interpretations of this bug:

a) Remove 'ASC,' in the line I mentioned since it's not valid according to the current rules for get_posts

b) Make get_posts properly support the above method by not having it throw out the extra order condition.
"	smerriman
Future Releases	19588	"Move to Trash results in a page with a ""0"""		General	3.3	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2011-12-17T15:41:04Z	2012-01-13T06:24:36Z	In the latest wordpress, if I delete a draft either the bulk delete , or individual move to trash, it loads a page with a zero. If I publish the draft, then move to trash, it works. I searched open tickets and could not find anything specific on this flow. 	astriker
Future Releases	23781	New Post Publishes to Wrong URL		General	3.4.2	normal	major	Awaiting Review	defect (bug)	new		2013-03-15T04:59:52Z	2013-03-16T01:13:12Z	"The ""Permalink"" displayed in the editor for new posts may be wrong, and changes (surprise!) when the Publish button is clicked.

Steps to reproduce this:
1. Start typing a title in a new post.
1. Wait for an auto-save and Permalink to appear.
1. Make the title longer.
1. Type a post body.
1. Click Publish.

Expected result:

The new post should be published at the Permalink being displayed on the post editor.

Actual result:

A completely different permalink is generated based on the current title.  The new page gets cached at the ""wrong"" URL before any changes can be made.  General pandemonium ensues.  Etc.  (It's not a blocker bug, but it is so completely annoying!)"	miqrogroove
Future Releases	20360	New Sidebar Takes Over Previous Sidebar Widgets		General	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-04-05T00:09:43Z	2012-04-05T00:09:43Z	"When creating a new sidebar in a theme already utilizing a sidebar, the new sidebar takes on the widgets of the sidebar previously occupying that place of order.  For example, a theme currently has these sidebars, with widgets in use:

Sidebar
Footer

Adding a new sidebar in a array:


{{{
$sidebars = array('Home Page Sidebar','Sidebar','Footer');

foreach ($sidebars as $sidebar) {

  register_sidebar(array('name'=> $sidebar,

    'before_widget' => '<article id=""%1$s"" class=""widget %2$s""><div class=""container"">',

    'after_widget' => '</div></article>',

    'before_title' => '<h3>',

    'after_title' => '</h3>'

  ));

}
}}}

Home Page Sidebar takes the widgets of the Sidebar when it takes in place in line."	imikedesigns
Future Releases	20935	No display in the WYSIWYG editor.		General	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-06-13T05:58:51Z	2012-06-13T05:58:51Z	Sometimes, nothing in the visual editor in me does not appear and you can switch to HTML view.	OldShaterhan
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	16845	Notice: Undefined index: post_id  in wp-admin/media-upload.php		General	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-03-13T08:09:22Z	2011-03-15T11:34:06Z	"Installed 3.1 on my server. when i edit a post and trying to insert a image from another site using: /wp-admin/media-upload.php?tab=type_url . im missing post_id in that url. then i dont get the ""insert into post"" button. 
error msg:
Notice: Undefined index: post_id in /var/www/blog/htdocs/wp-admin/includes/media.php on line 1639 
Notice: Undefined index: post_id in /var/www/blog/htdocs/wp-admin/includes/media.php on line 2223 "	spaam
Future Releases	24432	On multisite when SSL active on page: 'http' $scheme not working in get_admin_url(), but works in get_site_url()		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-05-27T07:11:40Z	2013-05-27T07:38:34Z	"get_site_url()  wp-includes/link-template.php, line 1964
get_admin_url() wp-includes/link-template.php, line 2006

In multisite specifying 'http' $scheme in get_admin_url() has no effect, links are still served as https.  Yet, specifying 'http' $scheme in get_site_url works fine.

As a workaround, use: get_site_url($blog_id, 'wp-admin/', 'http') until get_admin_url fixed."	Just a guy
Future Releases	19188	Only one dashboard widget can't be moved into second column unless Screen Options is expanded		General	2.9	normal	normal	Awaiting Review	defect (bug)	new		2011-11-06T22:02:54Z	2011-11-07T21:01:20Z	"A crazy weird issue. Since 2.9, a single dashboard widget can't be dragged (easily) into the second column unless the Screen Options are expanded. 

Screencast: http://cl.ly/3y0j1o2f3A2f3l06120R"	ryanimel
Future Releases	17077	Page parent li elements in nav menus not always given current-page-parent class		General	3.1	normal	trivial	Awaiting Review	defect (bug)	new		2011-04-07T09:53:45Z	2011-04-07T09:54:04Z	"Using a fresh WP3.1.1, 2010 theme, Theme Unit Test data, adding a navigation menu with Parent Page as an item without any child items and then navigating in the browser to Child Page 1.

The <li> for the parent menu item doesn't get assigned the current-page-parent class.

It does get the current-page-ancestor class, and none of my themes demand the current-page-parent class specifically so I've tagged this as trivial."	andymacb
Future Releases	11235	"Pages whose ancestors are not all ""published"" cannot be used as parents for other pages."		General	2.9	normal	normal	Future Release	defect (bug)	new		2009-11-23T01:04:01Z	2009-11-23T15:27:55Z	Pages with trashed parents cannot be used as parents for other pages (they do not appear on the list).	caesarsgrunt
Future Releases	23412	Password protected pages - redirect after login		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-02-07T10:32:30Z	2013-03-02T16:03:02Z	"Hi,

I am using WP 3.5.1 and I have found out that after a successful login to a password protected page, WP won't redirect back.

This is because referrer is empty.

So I have modified page login script to have hidden ""_wp_http_referer"" field in form.

After that, login redirects back to page normally.

Here is my script:
{{{
	function my_password_form() {
	    global $post;
	    $label = 'pwbox-'.( empty( $post->ID ) ? rand() : $post->ID );
	    $o = '<form class=""protected-post-form"" action=""' . get_option( 'siteurl' ) . '/wp-login.php?action=postpass"" method=""post"">
	    <p>' . __( ""To view this protected post, enter the password below:"" ) . '</p>
	    <label for=""' . $label . '"">' . __( ""Password:"" ) . ' </label><input name=""post_password"" id=""' . $label . '"" type=""password"" size=""20"" /><input type=""submit"" name=""Submit"" value=""' . esc_attr__( ""Submit"" ) . '"" />
	    <input type=""hidden"" name=""_wp_http_referer"" value=""'.get_permalink().'"" />
	    </form>
	    ';
	    return $o;
	}
	add_filter( 'the_password_form', 'my_password_form' );
}}}


This functions returns empty URL to wp-login.php script:
{{{
function wp_get_referer() {
	$ref = false;
	if ( ! empty( $_REQUEST['_wp_http_referer'] ) )
		$ref = $_REQUEST['_wp_http_referer'];
	else if ( ! empty( $_SERVER['HTTP_REFERER'] ) )
		$ref = $_SERVER['HTTP_REFERER'];

	if ( $ref && $ref !== $_SERVER['REQUEST_URI'] )
		return $ref;
	return false;
}
}}}
I hope this helps.

I have tried this with all plugins disabled, and also on 20-12 theme, same error occurs.

Bye,
Dubravko

"	dood_cro
Future Releases	17002	Pasting Large Amount of Text Through Paste-from-Word TinyMCE button leads to Whitescreen upon publishing		General	3.1	normal	minor	Awaiting Review	defect (bug)	new	reporter-feedback	2011-03-30T19:04:53Z	2011-04-01T16:58:15Z	"I needed to paste a large MS Word document into a WordPress page, so I used the Paste-from-Word button on the Visual Editor to do so. When I tried to publish the page, I got a whitescreen with the URL /wp-admin/post.php

After testing the problem in various ways, I determined that the problem arose only when the amount of words in the page were more than 10,000. The page posted fine when there were fewer than 10,000 words.

Using WordPress 3.1, CommentPress Theme, Mac OS X 10.6.7, Chrome browser"	mkgold
Future Releases	20260	Post by email posting same message multiple times		General	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-03-19T15:40:57Z	2012-03-20T08:45:04Z	"I am using the Post by email feature for a Wordpress.org blog. I post by mail once a day and daily to the blog, usually around midnight. There are usually between 2 and 6 messages posting on any given day (sent as individual emails).

I have set up a secret POP email address to which I send emails, and these emails are picked up by Wordpress as Posts on my blog.

However, I am seeing the messages post multiple times; sometimes twice, sometimes up to 10 times in a row on the blog.

It usually happens for all messages on certain days, but some days this does not happen at all. I have not been able to identify a pattern of which days have this problem or if it is related to the number of messages posting on a particular day.

This issue began happening around October 2011; previously, I didn't notice this problem.

Environment:
Wordpress.org 3.3.1
Thunderbird 7.1 email client; publish messages sent in text mode, with word wrap off
Google Apps account used as secret email. Account set to POP. All forwarding, etc. is turned off.

Steps: 1) wp-mail.php modified to post regardless of author, per bug 18923 which keeps messages stuck in Pending status 2) User from which posts sent is registered as Editor or Admin in Wordpress site. 3) Theme footer modified to include automatic checking for incoming messages 4) Email account is setup in mail client that matches the Admin/Editor email in Wordpress 5) Message to post is sent to the secret address by user

Result: 1) Wordpress on certain days posts the messages with no problem; other days, it posts multiple copies of the message. Usually, either all messages post multiple times or all post one time for a given day; I have not noticed that if one message on a particular day posts multiple times that another will post only once. 2) There can be anywhere from 2 to 10 copies of the same message posted. 3) I have tried to modify my POP account settings so that messages get Archived when read, rather than staying in the Inbox; however, this did not fix the problem.

Note: I use Google Apps as the email server for both the From: mail and the secret address mail. 

I have not been able to find other discussions on this topic, nor track down any possible root cause of it.

Message of one of the posts that posted multiple times is attached."	bloggertype
Future Releases	20185	Postname Permalink with no title yields 404 error		General	3.3.1	normal	normal	Awaiting Review	defect (bug)	reopened	close	2012-03-06T19:16:44Z	2012-04-27T19:30:20Z	When I change the permalink structure to %postname%, I get a 404 for all posts that don't have titles. The URL for each of these posts appears to be correct - it includes the ID instead of the title, but the post being served is listed as not found. If I change the generated permalink so that it is 3 digits rather than 4 or so that it has some alphabetic characters in it, all is OK.	ikemarrus
Future Releases	21520	Prevent recursive script dependencies in wp_enqueue_script		General		normal	normal	Future Release	defect (bug)	new		2012-08-08T17:21:43Z	2012-10-23T20:32:51Z	"If a script sets itself as a dependency, we should catch that, strip out the dependency, and throw a {{{_doing_it_wrong}}}:

{{{wp_enqueue_script( 'my-script', '/path/to/file.js', array( 'my-script' ) );}}}

This may need to be done at the lowest level possible, i.e. {{{_WP_Dependency}}}"	batmoo
Future Releases	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
Future Releases	21872	RSS Widget, and all of fetch_feed() I believe, forces its own feed order of Post Date DESC		General		normal	normal	Awaiting Review	defect (bug)	new		2012-09-11T15:25:32Z	2012-09-11T15:58:00Z	"My events management plugin wanted to provide Upcoming Events via RSS.  I wrote a pre_get_posts filter to modify the order and orderby of the event's feed to be Ascending based on a the event's start date, and it was good.

Good, however, for only as long as you don't subscribe to the feed using WordPress (whether it be the event site or one on a totally different network).  WordPress, upon fetching the feed, always re-sorts the posts according to the post date.  Subscribing with something like iGoogle, will show me my upcoming events in the order that I've coded.

Is this an intentional design decision? It feels to me that the generating site should be responsible for the order of the feed, and WordPress should respect the generating site's wishes and present the feeds in the order it is given."	madtownlems
Future Releases	21234	Recursive directory creation & get_calendar() for custom post types		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-07-12T12:31:28Z	2012-07-13T00:28:43Z	"Hello!
I made two patches, and sent the pull request on githab.

https://github.com/WordPress/WordPress/pull/12
https://github.com/WordPress/WordPress/pull/14

And I want to join to contributers team. How can I do it? 
Irc chanel is Terminated :("	avaddon
Future Releases	21134	Registering and enqueueing on the same action can cause enqueueing to happen before registering		General	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-07-02T11:00:17Z	2012-07-03T01:42:10Z	"We have two plugins, plugin1 and plugin2. Plugin1 registers a script, Plugin2 wants to enqueue this script. Both of these routines are executed on the [http://wpdevel.wordpress.com/2011/12/12/use-wp_enqueue_scripts-not-wp_print_styles-to-enqueue-scripts-and-styles-for-the-frontend/ _enqueue_scripts] action.

There is a chance that enqueueing in Plugin2 will happen before registering in Plugin1 and therefore fail.

Possible fixes:

* Every time we enqueue a script, registered in another plugin, we use a higher priority. I am not a fan of this approach, because it is opaque – we need to document each enqueue like this, because the next developer might not know why did we use higher priority.
* Every time we register a script, we use a lower priority. I am not a fan of this either, because we will have to do this for almost every register, because we can't know if another plugin won't try to enqueue our scripts.
* Violate core recommendation and register the script on an earlier hook. I am not a fan of  approach for obvious reasons.
* Add {{{_register_scripts}}} hooks and recommend plugin authors to register their scripts at this time.

I would prefer if we added another set of hooks, because it both makes sense to register on a register hook (as opposed to enqueue hook) and it separates the two actions, so that we can execute them at different times.

When we agree on a solution, I would be happy to write the patch.
"	nbachiyski
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	15833	Script concatenation fails to take external dependencies into account.		General	3.0	normal	normal	Future Release	defect (bug)	new		2010-12-15T17:35:17Z	2011-01-16T02:19:59Z	"Script concatenation places the concatenated script include first, before any scripts loaded separately.  If one of the scripts in the concatenation relies on a script outside the concatenation the dependency order is ignored.

When the dependencies are all internal to the concatenation things work fine (for example script4 relies on script3):

* concat=script1,script2,script3,script4,script5

But when script3 is loaded externally, script4 will break:

* concat=script1,script2,script4,script5
* external-script3

This becomes apparent if jQuery is loaded from a non-standard location (via a plugin or the [http://codex.wordpress.org/Function_Reference/wp_enqueue_script#Load_a_default_WordPress_script_from_a_non-default_location code from the Codex]) in that the visual editor fails to function correctly because source:/trunk/wp-admin/js/editor.js uses jQuery (which it fails to register as a dependency, see ticket:15830, but when I fixed that locally the results were the same).

I'm working around this in [http://wordpress.org/extend/plugins/use-google-libraries/ Use Google Libraries] by globally disabling concatenation, but it would be nice if this was fixed.


If possible, it would be nice if the loader was smart enough to do something like:

* concat=script1,script2
* external-script3
* concat=script4,script5

Or at least flagged the script with the dependency as unsafe for concatenation:

* concat=script1,script2,script5
* external-script3
* script4
  


"	jczorkmid
Future Releases	20008	Search Results Paging Doesn't Work on Lighttp 404 Handler		General	3.3.1	normal	major	Awaiting Review	defect (bug)	new		2012-02-10T07:01:47Z	2012-02-10T23:02:55Z	"Quote from http://core.trac.wordpress.org/ticket/11723

I'm running Wordpress on lighttpd, using server.error-handler-404 = ""index.php"", all the pretty permalinks work perfectly. However, when doing a search, i only get the first results page, that is mysite.com/?s=query works but '''mysite.com/page/2/?s=query''' doesn't (i get shown the home page saying it's on page two of it). Paging on categories, archives and tags works as expected too.

I believe this is a Wordpress error, as the variables are being correctly passed to the script. Strangely '''mysite.com/index.php/page/2/?s=query''' or '''mysite.com/?s=query&page=2 works''' as expected, i have tried exploring the code but i don't really know about the internals of the wordpress core.

I tried the solution but not working for me.

{{{
function wp_fix_lighttpd() { //checks if URI has parameter and sets globals
	if (isset($_GET) && isset($_SERVER['QUERY_STRING'])) return;
	$donga = explode('?', $_SERVER['REQUEST_URI'], 2);
	if (count($donga) > 1) { 
		$_SERVER['QUERY_STRING'] = $donga[1];
		parse_str($donga[1], $_GET);
		$_REQUEST = array_merge( (array)$_GET, (array)$_REQUEST);
	}
}
}}}

I hope anyone can help me fix this. Thanks.
"	anniyan07
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	20338	Slugs and special chars		General	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-03-31T16:18:03Z	2012-03-31T16:18:03Z	"When Wordpress generates a slug, the apostrophe mark is stripped.

Examples :

""I'm open"" > im-open[[BR]]
""L'équipe"" > lequipe[[BR]]
""Suzy's Place"" > suzys-place[[BR]]

If the apostrophe is changed to ""-"" the auto generated slug will be more ""readable"" (and better for seo) :

""I'm open"" > i-m-open[[BR]]
""L'équipe"" > l-equipe[[BR]]
""Suzy's Place"" > suzy-s-place[[BR]]

Maybe a constant to define what strategy to adopt ? "	amirhabibi
Future Releases	20890	Standardize line endings of wp-config-sample.php and wp-fullscreen.css		General		normal	trivial	Awaiting Review	defect (bug)	new		2012-06-08T15:24:46Z	2012-06-08T15:57:59Z	"Two core files seem to have invalid line endings (\r).
{{{
~/data/wp$ ack -l ""\r""
wp-includes/js/tinymce/plugins/wpfullscreen/css/wp-fullscreen.css
wp-config-sample.php

~/data/wp$ cat -vT wp-config-sample.php | head
<?php^M
/**^M
 * The base configurations of the WordPress.^M
 *^M
 * This file has the following configurations: MySQL settings, Table Prefix,^M
 * Secret Keys, WordPress Language, and ABSPATH. You can find more information^M
 * by visiting {@link http://codex.wordpress.org/Editing_wp-config.php Editing^M
 * wp-config.php} Codex page. You can get the MySQL settings from your web host.^M
 *^M
 * This file is used by the wp-config.php creation script during the^M
}}}"	xknown
Future Releases	20822	Switching visual/html on wp_editor used on front end not saved as new default		General	3.3.2	normal	minor	Awaiting Review	defect (bug)	new		2012-06-04T06:45:12Z	2012-06-04T06:45:12Z	"Using the wp_editor on the frontend it doesn't default to the last used state it defaults to the last used state on the back end.

I did find that using:
add_filter( 'wp_default_editor', create_function('', 'return ""tinymce"";') );

inside the function I am using to replace the front end comments with the visual editor worked around this a for me by defaulting to visual which works as well for me in this case as last used, but the default should probably change globally when a logged in user toggles between the two _or_ should get saved independently.



"	jb510
Future Releases	20133	Tags with diacritical marks issue		General	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-02-28T18:06:15Z	2012-02-28T18:06:15Z	"I can't add tags to post with diacritical marks (for example polish word ""bąk"") and then the same word without diacritical marks ""bak"" from edit post panel, because function term_exists() in wp-includes\taxonomy.php returns true when checking if this tag already exists. I can do this from tag edit panel, but this is more time concuming."	partyzant
Future Releases	21237	"Terminology for ""Front"" and ""Home"""		General		normal	normal	Awaiting Review	defect (bug)	new		2012-07-12T13:59:40Z	2012-08-17T19:25:29Z	"The following related tickets all have discussions concerning the Terminology for ""Front Page"" and ""Home Page"" is some way.

#16379 - Better UI for doing ""Page on Front"" [[BR]]
(UI effected by the terminology)

#10158 - Deprecate is_home() and is_single(), in favor of is_blog() and is_post() [[BR]]
(Conditional Tags effected by the terminology)

#18705 - home_url() and is_home() with a static front page [[BR]]
(URL function effected by the terminology)

Additionally, Template files are effected by the terminology (home.php and front-page.php)

This ticket is intended to discuss the best options that address the above terminology concerns for the sake of consistency and usability. If a determination is made here, hopefully we can use the terminology to inform the above tickets."	WraithKenny
Future Releases	18322	The Road to Magic Quotes Sanity		General	3.2.1	normal	normal	Future Release	defect (bug)	new		2011-08-03T20:26:25Z	2013-04-22T01:18:34Z	For back compat reasons, wp_magic_quotes() performs addslashes() on GPCS data.  This is a pain, especially given that some core API expects slashes and some doesn't.  In hopes of someday losing the automatic GPCS slashing, let's introduce a flag to turn off the slashing as well as slash and unslash functions that consult the flag.  If slashing is on, these functions add and strip slashes.  If slashing is off, they return data unchanged.  Plugin authors can start using these functions and testing their code with GPCS slashing turned off and on.  Eventually, GPCS slashing would default to off and all calls to the slash and unslash functions could be removed from core.	ryan
Future Releases	22746	The metadata_exists() function should return the correct value if the get_$meta_type_metadata filter returns a non null value		General		normal	normal	Awaiting Review	defect (bug)	new		2012-12-05T00:04:20Z	2012-12-05T00:04:20Z	"The line [http://core.trac.wordpress.org/browser/trunk/wp-includes/meta.php?rev=23043#L324 324] should return $check instead of true, otherwise the filter doesn't normally work when someone wants to always return false for a given meta key.

Here's a quick way to reproduce it
{{{
> add_filter('get_user_metadata', '__return_false'); return metadata_exists('user', 1, 1)
TRUE
}}}"	xknown
Future Releases	23729	Ticket #11289, IE bug fix: always pad the error page with enough characters		General		normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-03-09T06:25:21Z	2013-03-20T15:59:02Z	Is it really such a good idea to put the padding where it is currently in the error pages? This causes all sorts of problems with Dom parsers... it should be placed somewhere after the html tag or better yet in the body... almost looks like someone is very proud of their fix and wants the world to see it lol	wp4j
Future Releases	24171	"Trashing a page selected as ""Page on Front"" produces homepage 404"		General		low	minor	Awaiting Review	defect (bug)	new		2013-04-23T21:58:26Z	2013-04-23T22:33:28Z	"Steps to produce:

1. Create a new page called ""My Home Page"". Add some bacon ipsum.
1. Assign the page as your static home page.
1. Trash the page, but don't delete it.

Expected behavior: My homepage reverts to a list of my most recent posts

Actual behavior: 404 template is loaded.

In r6337, we started listing most recent posts when the page is ''deleted''. However, there's a short circuit (added later) in `wp_delete_post()` to `wp_trash_post()`, which doesn't delete the option. This results in the homepage not being reset until the post is actually deleted.

I think the trashing behavior should be consistent with deleting behavior. 

Related: #16379, #14403"	danielbachhuber
Future Releases	15030	Unserialize deep when returning arrays of metadata		General		normal	normal	Future Release	defect (bug)	new		2010-10-04T11:05:52Z	2010-12-08T19:34:06Z	"Currently when retrieving an array of metadata values for an object (no meta key specialized), they are retrieved as serialized. Only when meta key is specified do we unserialize.

We should array_map( 'maybe_unserialize' ) on what we plan to return instead of forcing plugins to call that themselves."	nacin
Future Releases	22807	Updating a non-expiring transient with a new expiry date does not make it expire		General	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-12-07T11:38:18Z	2012-12-07T11:38:18Z	"Consider this:
set_transient( 'Bug', 'v1');
set_transient( 'Bug', 'v2', 10 );

The second line will update 'Bug' with 'v2', but will not set autoload to 'no'. Hence, 'Bug' does never expire, and you can get its value 'v2' infinitely using

echo get_transient( 'Bug' );"	bersbers
Future Releases	21185	Upload/insert popup not scrollable on iPad		General		normal	normal	Awaiting Review	defect (bug)	new		2012-07-07T20:58:36Z	2012-07-07T20:58:36Z	"When using iPad (testing with a v1 iPad) the upload/insert popup is not scrollable so if you expand an image by clicking ""show"" you cannot scroll down to the"" insert into post"" link."	husobj
Future Releases	24133	WP_Query, multiple 'orderby' values glitch		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-19T02:45:46Z	2013-04-19T02:48:08Z	"According to the documentation, WP_Query argument 'orderby' allows for multiple values, but it doesn't work.

Looking in the code i found out why, the 'order' is only being applied to the last item in the list.

So for instance: 
    ('orderby' => 'title menu_order', 'order' => 'DECS')
Will end up as
    ""ORDER BY $wpdb->posts.menu_order, $wpdb->posts.post_menu_order DECS""

To fix (I hope), the following needs to be done to query.php line 2387
    $orderby_array[] = $orderby.' '.$q['order'];
"	racura
Future Releases	23995	Weird Error After Post Published Successfully		General	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-04-08T20:46:26Z	2013-04-09T23:20:59Z	"I didn't get the exact message, but I was stuck on the New Post screen after clicking Publish with something to the effect of: The server connection has been lost.  This message will go away once you get reconnected.

I ended up clicking on Visit Site and I could see that the post was already published.

My server has been acting up a bit today, so I figured this is a good time to test out the new post saving logic.  I'm not sure if this was the intended experience though?

Tested on 3.6-beta1.  Only happened once so far."	miqrogroove
Future Releases	20326	Widget dropped in sidebar with name=sidebar-two shows up in sidebar with id=sidebar-two (and different name: some-other-name)		General		normal	normal	Awaiting Review	defect (bug)	new		2012-03-29T12:53:15Z	2012-03-29T13:57:28Z	"Hi,

reproducing steps:
register 2 sidebars:

sidebar 1: 
id   = 'sidebar-one'
name = 'sidebar-two'

sidebar 2: 
id   = 'sidebar-two'
name = 'some-other-name'

drop a widget in sidebar 1, and it will also after reloading the widget page show up in sidebar 2...

Also: widgets dropped in sidebar 2 disappear.

OK, OK, i shouldn't be mixing up sidebar names and ids like i did (sorry), am going to change that in my setup now, I just wanted to point out that I thought that assigning a widget to a sidebar was related to its id only. This current behavior strikes me a little strange :)







"	ruud@…
Future Releases	23092	"Word count, Edit Post > Publish > Visibility, Published Date & Status ""Edit"" links don't work"		General	3.5	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2012-12-31T02:38:48Z	2012-12-31T23:03:22Z	"hosting platform:

Apache 2.2.23
PHP 5.4.10
FreeBSD 8.3
WordPress 3.5 (no modifications to codebase & themes, no plugins)

- client:
Mac OS X
Firefox and Safari

prior to upgrading to 3.5, Edit Post > Publish > Visibility, Published Date & Status ""Edit"" links worked as expected. I can make changes then hit Update.

after upgrade to 3.5, these Edit links no longer work. Tons of load-styles.php errors. Word count is always set to 0 - Quick Edit works just fine.

tw2113 (from #wordpress Freenode) suggested I enable script_debug in wp-config.php and that resolve the issues I was having. Word count now works also.

As tw2113 have mentioned, I shouldn't need to have script_debug enabled just to get your post editor working.

Any thoughts?

Please advise, thank you!"	scaturan
Future Releases	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
Future Releases	19192	Wrong term count for private posts		General		normal	normal	Awaiting Review	defect (bug)	new	close	2011-11-07T09:00:15Z	2011-11-14T21:22:33Z	"The term manager page (wp-admin/edit-tags.php) shows wrong counts when the terms contain private posts. 

Steps to reproduce:
 - Create a private post and assign it to a category or a tag.
 - Visit the wp-admin/edit-tags.php

The term count does not change. However, when you click on the posts column, the edit posts screen will correctly show the private post."	xknown
Future Releases	21268	_wp_page_template is getting 'stuck' to a page		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-07-13T22:21:42Z	2012-07-13T22:21:42Z	"Unmodified WP 3.4.1 / Ummodified TwentyEleven theme

Create a page (id=2).  Manually add a postmeta entry for 

{{{
post_id=2, 
meta_key = _wp_page_template, 
meta_value = pagefull.php
}}}


The page now opens with margin: 0 7.6%;  (correct!)

Now try to change it back to default, either by removing the _wp_page_template postmeta record or by editing the page -> Page Attribute / Template.  The page will not revert back to Default.  It continually displays as Full Width, and a postmeta item telling post_id 2 to use _wp_page_template = pagefull.php is added.

http://wp34.roveridx.com/?page_id=2

This behavior does not happen in 3.3.2."	shawmutsteve
Future Releases	24457	add_filter('gettext' ignores get_post_type after deleting a featured image		General		normal	normal	Awaiting Review	defect (bug)	new		2013-05-29T22:08:41Z	2013-05-31T14:38:35Z	"Steps to reproduce:

1. register a custom post type using 'register_post_type', in the example my post type is 'gorilla_residents'.

2. use the following code to filter the 'Set featured image' text for a specific post_type:

{{{
function change_featuredimage_txt($translated) {
    global $post;

    if (get_post_type($post) == 'gorilla_residents') {
        $translated = str_ireplace('Set featured image', 'Set Gorilla Avatar', $translated);
        $translated = str_ireplace('Featured Image', 'Gorilla Avatar', $translated);
        $translated = str_ireplace('Remove featured image', 'Remove Gorilla Avatar', $translated);

    }

    return $translated;
}
add_filter('gettext', 'change_featuredimage_txt');
}}}

3. In the admin, create a new instance of the post type, e.g. a Resident.

4. Asign a featured image. NOTE: the correct filtered text is displayed.

5. Remove/Delete the featured image.
NOTE: the incorrect featured image text is displayed.

It looks as though the add_filter('gettext' ... function in my functions.php is being ignored after the ajax delete featured image function is called."	vmodha
Future Releases	20690	add_post_meta/update_post_meta and cache		General	3.3.2	normal	normal	Awaiting Review	defect (bug)	new		2012-05-16T14:33:30Z	2012-05-16T14:33:30Z	"I have a custom post type with 2 fields for price, second one has 5% discount and I want to populate it automatically by hooking to 'save_post'. 

I have a working logic that calls update_post_meta() (or add_post_meta() ) for the second field but it doesn't get executed even with several post updates. However, if I end my function call with a var_dump that outputs the values from the function, everything goes smooth.

It looks like some caching issue to me that gets flushed per var_dump call, anyone able to reproduce?"	nofearinc
Future Releases	14754	add_query_arg() refactoring		General		normal	normal	Future Release	defect (bug)	new	needs-unit-tests	2010-09-01T16:32:20Z	2011-03-23T19:34:24Z	"The function add_query_arg() looks like that it could benefit from a refactoring. Especially the handling of optional parameters (did introduce PHP 4 that language feature?) can benefit by a sligh touch-up.

Attached patch reflects only the first few lines of the function."	hakre
Future Releases	19921	"always use require_once for wp-load.php (fixes ""ABSPATH defined multiple times"")"		General	3.3.1	normal	normal	Awaiting Review	defect (bug)	new		2012-01-29T18:09:46Z	2012-02-10T17:53:45Z	"The `wp-load.php` file should always be included via `require_once`.  This allows developers to include files when necessary with having to run into the ""ABSPATH defined multiple times"" notice (let alone waste time processing the file).

In trunk, require_once is already used in the majority of cases for `wp-load.php`:
    * 24 require_once
    * 8 require
    * 1 include

This has come up because of a situation in a plugin where it is necessary to manually include the `wp-login.php`.  But then `wp-login.php` calls `require wp-load.php` and the constant re-declaration notice arises.

In two cases, the patch changes relative paths (eg `./` to `dirname(__FILE__)`) to avoid safe mode problems and improve the ability to run files from anywhere(1), which is helpful for testing from the command line.

(1) Paths in PHP are relative to the present working directory, not the directory the file is in."	convissor
Future Releases	20415	big tags formatted incorrectly in rss		General		normal	normal	Awaiting Review	defect (bug)	new		2012-04-11T06:45:13Z	2012-04-11T06:45:13Z	"several (doubled, tripled) big tags formatted incorrectly in rss, may be single big tags behave same way

what is formatted


{{{
<blockquote><p><big><big>123</big></big></p>
<p><big><big>123</big></big></p></blockquote>

}}}

in normal view is formatted


{{{
<blockquote><p><big><big>123</big></big></p>
<p>123</p></blockquote>

}}}

in rss.


( and it is just

{{{
<blockquote><big><big>123
123</big></big></blockquote>

}}}
in editor)"	qdinar
Future Releases	24596	get_avatar() is using BuddyPress thumb image		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-06-18T08:36:58Z	2013-06-18T15:36:12Z	"I am using the get_avatar() function in the loop to display the post author's avatar.

{{{
<?php $author = get_the_author(); ?>
<?php echo get_avatar( get_the_author_meta('ID'), 120, '', $author ); ?>
}}}

In bp-custom.php, I have set a default height and width on BuddyPress avatars

{{{
define ( 'BP_AVATAR_THUMB_WIDTH', 40 );

define ( 'BP_AVATAR_THUMB_HEIGHT', 40 );
}}}

Even though my get_avatar() function is outputting an avatar 120x120 in size, the 40x40 BuddyPress thumb is being used which is resulting in a stretched avatar being displayed (see attached screenshot)."	henrywright
Future Releases	16408	get_bloginfo('template_url') is not returning valid URLs.		General	3.0.3	normal	normal	Awaiting Review	defect (bug)	new		2011-01-30T08:04:50Z	2011-02-01T04:04:00Z	"There seems to be a general consensus on the #wordpress IRC channel that URLs cannot contain spaces. I agree with this, and I'm almost sure the entire internet community would to. Based on this axiom, get_bloginfo('template_url') should return URLs with spaces properly encoded, otherwise, it's not returning a valid URL, hence it's not returning a URL at all. I'm guessing that get_bloginfo('template_url') is suppose to return a URL, so this must mean that it's not currently (as of version 3.0.3) doing what it's suppose to.

As for what a properly encoded space character in a URL would be, I'm not exactly sure. I know it's either %20 or +, but I wont make the decision as to which of these it is.

If you by any chance believe that URLs *should* contain spaces, then that's another problem related to wp_enqueue_script. wp_enqueue_script removes spaces from it's URL. Again, if you think URLs should contain spaces, then wp_enqueue_script should include them.

Either way you think about it, get_bloginfo (including bloginfo) or wp_enqueue_script contains a defect. You may argue that you should not use spaces in your directory/file names to begin with, but this argument is irrelevant.

Thank you. I would appreciate this issue not being overlooked. :)"	figaroo
Future Releases	22950	get_boundary_post Does not return single post object		General		normal	normal	Awaiting Review	defect (bug)	new		2012-12-15T00:56:48Z	2012-12-15T11:49:01Z	"`get_boundary_post` Seems not to return a single `post` object, the way `get_adjacent_post` does.

It seems that `get_boundary_post` should call `array_shift` or `get_post` on the results, in a similar way to `get_adjacent_post`.

It's just odd that the behavior is different."	pathawks
Future Releases	17374	get_pages() with child_of forgets sort		General	3.1.2	normal	normal	Awaiting Review	defect (bug)	new		2011-05-11T10:06:17Z	2011-05-11T10:06:17Z	"If you call {{{get_pages()}}} with both the {{{child_of}}} and {{{sort_column}}}, the sorting is not applied.

{{{child_of}}} makes it select all pages (sorted) and later applies a subselect via {{{get_page_children()}}}. This subselect can mess up the sort order.

An example was reported on http://wordpress.stackexchange.com/questions/16921/get-pages-not-ordering-as-it-should

Related: #12821"	janfabry
Future Releases	20853	get_post_custom show directly serialized data from the post_meta arrays.		General	1.5	normal	minor	Awaiting Review	defect (bug)	assigned	dev-feedback	2012-06-06T05:39:23Z	2013-03-11T16:46:21Z	"get_post_custom show directly serialized data from the post_meta arrays.
For example:

If I save a data with:

{{{
			update_post_meta(	$post_id,	'camp',
				array(
					'some'	=>	$var,
					'thing'	=>	$var_2
				)
			);
}}}


When I use get_post_meta(); :

{{{
	$var_get = get_post_meta($post_id, 'camp', true);
	echo $var_get['some']; // Fine.. Print: $var content.
}}}


but, when I use get_post_custom() :

{{{
	$var = get_post_custom($post_id);
	echo $var['some']; Metod, (Not work because ""Returns a multidimensional array"" with all values, and 0 is the first or the unique value).
	echo $var['some'][0]; /* Metod, >:( , Not work. Print:

a:2:{i:some;s:4:""this"";i:thing;s:7:""content"";}	*/
}}}


Instead of display ""array"", and can not handle sub arrays."	shadowhck
Future Releases	20251	get_preferred_from_update_core can return false		General		normal	normal	Awaiting Review	defect (bug)	new		2012-03-17T14:51:41Z	2012-03-17T14:51:41Z	"I just had a case in my network installation where get_site_transient( 'update_core' ) returned false.
In this case it gave an error message at core_update_footer();

When I went back to Network admin updates page and press 'check_again' the error went away.
The error can be caused because of running the recent nightly build (3.4-alpha-20205).

What was weird that in the site wp-admin there still was the balloon that there was an update when I had the error. When I pressed the button the balloon went away what is the correct."	markoheijnen
Future Releases	22369	get_transient() do not call delete_transient() when deleting one		General	2.8	normal	normal	Awaiting Review	defect (bug)	new	close	2012-11-06T01:27:01Z	2012-11-10T10:33:00Z	"Hello

i was wondering why get_transient() is not calling delete_transient when deleting a timeouted transient.

Piece of code from get_transient()
{{{
				$transient_option = '_transient_' . $transient;
				$transient_timeout = '_transient_timeout_' . $transient;
				if ( get_option( $transient_timeout ) < time() ) {
					delete_option( $transient_option  );
					delete_option( $transient_timeout );
					return false;
				}
}}}

but i need to trigger the ""deleted_transient"" hook.
Can we do that:
{{{
				$transient_option = '_transient_' . $transient;
				$transient_timeout = '_transient_timeout_' . $transient;
				if ( get_option( $transient_timeout ) < time() ) {
					delete_transient( $transient_option  );
					return false;
				}
}}}
"	juliobox
Future Releases	20368	htmlspecialchars() returns empty string for non-UTF-8 input in PHP 5.4		General		normal	major	Awaiting Review	defect (bug)	new		2012-04-05T12:43:23Z	2013-03-04T18:04:55Z	"The default value of the input `$encoding` parameter for `htmlspecialchars()` changed to UTF-8 in PHP 5.4.  The prior default was ISO-8859-1.  The function's UTF-8 handler checks the input, returning an empty string if the input isn't valid UTF-8.

WordPress will see the UTF-8 validator kicking because most of the `htmlspecialchars()` calls don't use the `$encoding` parameter.  This will cause major problems for sites that have a `DB_CHARSET` other than `utf8`.

[http://article.gmane.org/gmane.comp.php.devel/71783 Posting 58859 to php-internals] by Rasmus gives a clear example of the problem.  Here is a link to [http://thread.gmane.org/gmane.comp.php.devel/71777 view the whole thread], starting with posting 58853).

Creating two centralized functions is an approach for resolving this problem.  This route is simpler and easier to maintain than adding the parameters to each `htmlspecialchars()` call throughout the code base.

1. `wp_hsc_db()` for safely displaying database results.  Uses `DB_CHARSET` to calculate the appropriate `$encoding` parameter.  MySQL's character set names are not equivalent to the values PHP is looking for in the `$encoding` parameter.  Please see the `hsc_db()` method in the [http://plugins.svn.wordpress.org/login-security-solution/trunk/login-security-solution.php Login Security Solution plugin] for a mapping of the valid options.

2. `wp_hsc_utf8()` for safely displaying strings known to be saved as UTF-8, such as error messages written in core.  Uses `UTF-8` as the `$encoding` parameter.  

Some calls in core use the `$flags` parameter, so these new functions will need the parameter too.  The default should be `ENT_COMPAT`, which works under PHP 5.2, 5.3 and 5.4.

It may be suggested that WP use `htmlspecialchar()`'s auto-detection option (by passing an empty string to the `$encoding` parameter).  This is not advisable because it can produce inconsistent behavior.  Even the PHP manual says this route is not recommended."	convissor
Future Releases	23407	http 403 should be returned for private content		General	3.4	normal	normal	Awaiting Review	defect (bug)	new		2013-02-06T20:32:29Z	2013-02-07T09:18:40Z	"Right now a 404 is returned which indicates that there is no content at the URL while all you need to do in order to see it is to login.

Same probably applies to posts which where published and returned to draft state.

"	mark-k
Future Releases	17078	is_active_sidebar() doesn't work with Numeric sidebar ID's		General	2.8	normal	normal	Awaiting Review	defect (bug)	new		2011-04-07T10:06:54Z	2011-09-19T15:07:09Z	"This needs a small fix: 

Function is_active_sidebar( $index)  converts $index to a string

then uses wp_get_sidebars_widgets() to see if the sidebar is active

..but keys in the array wp_get_sidebars_widgets() generates can be integers if the ID's of the registered sidebars are integers"	lanceo
Future Releases	24319	jQuery not loading in Admin.		General	trunk	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-05-11T18:24:45Z	2013-05-12T15:12:28Z	"I was encountering an odd bug after updating to the newest nightly.

It appeared that no js scripts were being loaded by load-scripts in wp-admin.  Since CSS was obviously being included, I compared load-scripts.php and load-styles.php and found what appears to be a missing directory separator.

Changing

define( 'WPINC', 'wp-includes' );

to

define( 'WPINC', '/wp-includes' );

in wp-admin/load-scripts.php seems to have fixed the problem.  I'm not sure if this is the correct fix, but I did find it odd that load-scripts.php used different syntaxes to include their respective filenames:

from wp-admin/load-scripts.php:

require(ABSPATH . WPINC . '/script-loader.php');
require(ABSPATH . WPINC . '/version.php');

and from wp-admin/load-styles.php

require(ABSPATH . '/wp-includes/script-loader.php');
require(ABSPATH . '/wp-includes/version.php');"	willhaynes24
Future Releases	18070	jpg vs. jpeg error when editing a LINK URL image in a post		General		normal	major	Awaiting Review	defect (bug)	new	reporter-feedback	2011-07-11T16:21:13Z	2011-07-11T22:28:04Z	"This problem deals with an unfortunate discrepancy between file extensions .jpg and .jpeg -- The results equate to frustrating 404 errors and lightbox plugins that seem to be broken.

Here's what happens:

1) Upload an image with file extension '.jpeg' (note the 'e') and insert it into a post, with a blank 'Link URL'.

2) Now that the image is in the body of the post, edit the image's Link URL. (hover-over the image in the post and click the small icon on the upper-left that appears). If you click the 'File URL' button to auto-full the Link URL box, it will autofill the correct image address, but with a '.jpg' extension!

This lead to 404 errors, a lightbox plugin that appeared broken, and had me thinking it was an .htaccess issue from my hosting company....

NOTE: it autofills with the correct file extension when clicking the 'File URL' button is clicked upon initially inserting the image, however it fails when using the secondary menu that is available after inserting the image.

Thanks for fixing this!

(originally posted at https://wordpress.org/support/topic/bug-jpg-vs-jpeg-error-when-editing-a-link-url-image-in-a-post?replies=4)"	multimule
Future Releases	10458	lighttpd/1.4.22 does not populate _REQUEST['action'] for wp-login.php		General	2.8	normal	normal	Future Release	defect (bug)	reopened	has-patch	2009-07-21T14:10:36Z	2010-05-10T08:50:09Z	"lighttpd/1.4.22 does not populate _REQUEST['action'] for wp-login.php, this in turn disabled any action in the switch statement breaking the ability to logout.

Symtoms of this bug are: clicking logout in wordpress 2.8 and going to the login page but not really logging out.  Clicking logout in wordpress 2.3 and being redirected right back to the /wp-admin page.

adding this code to wp-login.php, fixes the behavior and re-enables all features in wp-login.php.

I don't know the wordpress code but if there is a section which deals with idiosyncrasies of web servers that lighttpd be detected and this code be run to deal with it. 

//
// Main
//


if (strpos($_SERVER['SERVER_SOFTWARE'], 'lighttpd') !== false)
{
$_lighty_url = $base_url.$_SERVER['REQUEST_URI'];
$_lighty_url = @parse_url($_lighty_url);
$_SERVER['QUERY_STRING'] = $_lighty_url['query'];
parse_str($_lighty_url['query'], $_lighty_query);
foreach ($_lighty_query as $key => $val)
$_GET[$key] = $_REQUEST[$key] = $val;
}
"	myrond
Future Releases	16916	make_clickable() and URI in context		General	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-03-21T15:56:00Z	2011-03-21T15:56:00Z	"I just stumbled over [http://tools.ietf.org/html/rfc3986#appendix-C Appendix C.  Delimiting a URI in Context] and was wondering if this has been taken into account for the make_clickable() routine so far.

Looks like <> angle brackets are  especially recommended as a delimitier.

IIRC we ingore it so far, would be nice to support the RFC."	hakre
Future Releases	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
Future Releases	19197	phplinter error reports against wordpress core.		General		normal	normal	Awaiting Review	defect (bug)	new	close	2011-11-07T17:34:14Z	2011-11-09T14:42:40Z	"One of our developer has been developing phplinter which can be found here [1] which gives wordpress core rather poor grade many of which are simply due to you guys having spaces mixed with tabs and whitespace after final close tag and others generally considered bad practices and few probably more serious.

Instead of me filing indvidual bugs for all of those I think it's best that you just git pull the phplinter and run it against wordpress then point your web browser against the report and flag/fix those that are relevant and those that are not.

An simple cli example is as follow...

#phplinter -wFIH  wordpress/ -o lintreport/ 

380 files, Average score: -2.86

Worst: wp-includes/class-simplepie.php with -303.39

[1] https://github.com/robotis/PHPLinter"	vikingnr1
Future Releases	22630	plugin_basename() fails on case-sensitive plugin directories		General	1.5	normal	minor	Awaiting Review	defect (bug)	new		2012-11-29T06:11:13Z	2012-11-29T17:06:49Z	"When `WP_PLUGIN_DIR` has slightly different casing to the actual path, `plugin_basename()` returns the full path to the plugin file.

For example:

If `WP_PLUGIN_DIR` is set to `C:/Website/wp-content/plugins`, but the actual file-system path is `C:/Website/wp-content/Plugins`, `plugin_basename()` will return the full path to the plugin file.

The `plugin_basename()` function uses a `preg_replace` statement to find path to the plugin relative from `WP_PLUGIN_DIR`. If the actual path to the plugin directory does not match case to `WP_PLUGIN_DIR`, the preg_replace will fail. This is because preg_replace is not case sensitive."	bungeshea
Future Releases	23402	remove_query_arg messing up some URLs		General		normal	normal	Awaiting Review	defect (bug)	new		2013-02-06T01:00:41Z	2013-02-06T15:15:02Z	"I'm using remove_query_arg to strip utm campaign parameters from user-submitted URLs, but for some URLs it is replacing dots with underscores.

E.g. if you pass http://www.nanowerk.com/news2/newsid=28843.php into this:


{{{
$url = remove_query_arg( array(
	'utm_source'
	'utm_medium',
	'utm_campaign',
	'utm_term',
	'utm_content'
	), $url );

}}}

it returns http://www_nanowerk_com/news2/newsid=28843.php



"	lumpysimon
Future Releases	24543	screen options in post editing should always show a checkbox for comments and versions		General	3.5	normal	normal	Awaiting Review	defect (bug)	new		2013-06-09T07:23:17Z	2013-06-09T07:23:17Z	"1. Start a new post
2. click the screen options button
3. can't toggle the display of comments or versions for the edit screen as they are not displayed as part of the options

The way I understand it the sceer option are associated with a user and not a port, but the current implementation forces the user to ""hunt"" for an appropriate post in order to be able to change the setting.

In addition, comments is off by default which makes it harder to discover the functionality."	mark-k
Future Releases	22781	setUserSetting cannot handle hyphens		General	2.7	normal	normal	Future Release	defect (bug)	new	early	2012-12-06T06:18:39Z	2013-06-14T23:24:14Z	"sanitize_key() can, setUserSetting should be able to as well. It's not that sanitize_key() plays a role, but it sets expectations for what is allowed in keys across core. Both keys and values should be able to accept a hyphen.

The post-thumbnail image size cannot be remembered, for example, if it is added to image_size_names_choose."	nacin
Future Releases	20077	shortcode_parse_atts should not force arguments to be lowercase		General		normal	normal	Awaiting Review	defect (bug)	new	close	2012-02-19T19:21:33Z	2012-02-20T17:42:42Z	"Inside wp-includes/shortcodes.php, the shortcode_parse_atts() function forces shortcode arguments to be lowercase.  So if your shotcode had something like [my_shortcode MyVar=123], then your code that uses something like ""print $MyVar;"" fails... you have to use ""$myvar"" instead.  This is counter-intuitive.  I understand that there needs to be some restrictions on what is a valid parameter name (see http://core.trac.wordpress.org/ticket/9405), but I think it makes the most sense that the parameter names can correspond to any valid PHP variable name;  PHP variables ARE case-sensitive, so this arbitrary restriction of forcing lower-case parameters seems like the incorrect approach."	fireproofsocks
Future Releases	20740	strip_shortcodes Chokes On Empty Shortcodes		General	3.3.2	normal	minor	Awaiting Review	defect (bug)	new		2012-05-23T22:58:56Z	2012-05-23T22:58:56Z	"It appears the regex for strip_shortcodes doesn't recognize empty shortcodes. For example, a caption shortcode like this would only have the opening shortcode tag stripped:


{{{
[caption id=""attachment_3360"" width=""288"" caption=""Some caption""][/caption]
}}}


The closing caption tag remains in the resulting string.

I realize this is a fringe case (why would you have an empty caption?), but it popped up for me when working with a popular plugin that attempts to generate an excerpt by doing the following:

{{{
$content = strip_tags($content);
$content = strip_shortcodes($content);
}}}

Seems harmless--but if a caption contains only an image tag, the strip_tags removes it, and the strip_shortcodes chokes on the now-empty shortcode. Or even worse, if you have a second caption shortcode in the content, it strips EVERYTHING between the first opening caption tag and the second closing caption tag.

And I have to imagine there are some custom shortcodes that may be legitimately empty for some reason. I dunno.

To reproduce:

{{{
$content = '[caption][/caption]

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

[caption][/caption]';

$content = strip_shortcodes($content);

echo $content;
}}}
"	MathSmath
Future Releases	23492	svn:ignore wp-config.php		General	trunk	low	minor	Awaiting Review	defect (bug)	new		2013-02-17T17:59:42Z	2013-02-17T17:59:42Z	`wp-config.php` very often exists in Subversion checkouts, but it should never be committed. Could we add a `svn:ignore` property for it?	nbachiyski
Future Releases	24371	tags and editing publishing date do not work		General		normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-05-20T13:37:34Z	2013-05-20T14:22:07Z	Create a new post via firefox. try to change publishing date to future, does not work. try to add tags using most used tags and also adding new tags, no tags are added. at some point, I saved this as a draft but I think it was after I tried to changed the publishing date.	Shira.victor
Future Releases	12056	"target=""_blank"" being stripped from Profile Bio and Category Description"		General	2.9.2	normal	normal	Future Release	defect (bug)	new		2010-01-27T16:50:00Z	2011-05-31T19:32:07Z	"Many apologies if this is a duplicate. I have searched but did not find it yet posted.

I noticed that target=""_blank"" is being stripped from my ""a href"" tags my profile ""Biographical Info"" field even though the ""a href"" with the URL and closing tag still remain. It happens every time I save my profile. 

This was independently verified.

It is a regular wordpress install running 2.9.1 (not wordpressmu, etc.).

My original thread can be found here:
http://wordpress.org/support/topic/355388?replies=1"	lovewpmu
Future Releases	14938	title of add_settings_section and add_settings_field		General		normal	normal	Future Release	defect (bug)	new		2010-09-22T16:44:40Z	2011-01-16T17:10:15Z	"When the title of both these functions is left blank, they echo 
<h3></h3> and <table><th>.... on to the page. 

When the title is left blank, they shouldn't add the blank tags."	gandham
Future Releases	11734	trackback_rdf() for IDN (xn--) Domains produces invalid HTML		General	3.1	normal	normal	Future Release	defect (bug)	new	close	2010-01-06T01:10:55Z	2012-02-20T12:22:02Z	"Hello

The trackback_rdf() function from wp-includes/comment-template.php wraps the ""<rdf:RDF>...</rdf:RDF>"" output inside ""<!-- ... -->"" HTML comments, probably to be safe as not all Browsers understand them.

When using Wordpress 2.9.1 on a site with an international domain name [1] that contains special characters like German ""Umlauts"" like äöü, this domain name is written as e.g. xn--tst-qla.de for täst.de.

Now the output of trackback_rdf() suddenly gets a ""--"" which is the SGML/HTML comment separator mark [2]. Firefox 3.5.6 e.g. sees this as the end of the comment and therefore shows the final ""-->"" as text to the user.

As the whole RDF tag is supposed to be invisible for the user, it's a bug in Wordpress :-(

Here is an real world example output:

{{{
                     <p class=""post-tags"">

                      </p>
				  <p class=""post-info"">
					  				  </p>
				  <!--
				    <rdf:RDF xmlns:rdf=""http://www.w3.org/1999/02/22-rdf-syntax-ns#""
				xmlns:dc=""http://purl.org/dc/elements/1.1/""
				xmlns:trackback=""http://madskills.com/public/xml/rss/module/trackback/"">
			<rdf:Description rdf:about=""http://xn--bcher-entdecken-zvb.de/wordpress/index.php/wortlieblinge/""
    dc:identifier=""http://xn--bcher-entdecken-zvb.de/wordpress/index.php/wortlieblinge/""
    dc:title=""Wortlieblinge""
    trackback:ping=""http://xn--bcher-entdecken-zvb.de/wordpress/index.php/wortlieblinge/trackback/"" />
</rdf:RDF>				  -->
			  </div>
}}}


Sadly I have not yet come up with a solution. PHPs urlencode() does not escape a double dash - which is ok as its usually perfectly valid. Maybe someone with RDF experience has a good idea.

bye,

-christian-


[1] http://en.wikipedia.org/wiki/Internationalized_domain_name#Example_of_IDNA_encoding

[2] http://htmlhelp.com/reference/wilbur/misc/comment.html



"	lathspell
Future Releases	23429	undefined tinyMCE: no ?> at the end of load-scripts.php		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2013-02-08T22:01:36Z	2013-02-14T03:47:40Z	"I noticed a theme throwing an error in console today. I noticed ""Uncaught ReferenceError: tinyMCE""

In particular, switchEditors.switchto() and a few others like .do - where undefined. I thought that was strange. I googled the error and eventually found this thread: http://wordpress.org/support/topic/javascript-error-in-admin-panel-with-load-scriptsphp?replies=2

Adding ?> to the end of load-scripts.php fixed the issue.

Very strange bug. I have seen it on 2 installations now (4 referencing the two in the support forum thread) - but I am unable to recreate it anywhere else."	chaos1
Future Releases	22233	update_option() fails when value has nested objects		General	3.4.2	normal	minor	Awaiting Review	defect (bug)	new		2012-10-20T16:29:08Z	2012-11-22T03:28:30Z	"This gist has an example of how this problem can be reproduced: https://gist.github.com/3923757

If you run the three functions in three separate page loads you will see that the foo attribute of `$b` doesn't get saved. It seems to be some kind of cache problem. 

I've been able to reproduce this in 3.4.2, 3.4.3-alpha and 3.5-beta2 "	exz
Future Releases	24266	update_post_meta doesn't change post modified date		General	3.5.1	normal	normal	Awaiting Review	defect (bug)	new		2013-05-05T05:10:14Z	2013-05-06T04:04:17Z	"In building an application I wanted to query for posts that were modified since a specific date/time. 

The only issue is the majority of our changes are to post meta and not to post content, this means these changes don't show up in the query. 

To solve this I'm tying into the action, but I feel like this is something that should be done by default."	DennisSmolek
Future Releases	21900	update_post_meta() returns FALSE when meta_value to be updated is the same		General	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-09-15T17:15:17Z	2012-10-13T00:52:12Z	"Since [14564] update_metadata() (wp-includes/meta.php [20435]) in lines 129-136 checks to see if the meta_value to be updated is the same as the value that already exists in the database.  The point of this check, presumably, is to prevent running a needless UPDATE query.  That's fine and good.

Currently, if the values are the same the function returns FALSE.  I think it should return TRUE in this case.  While I understand that from one point of view it should be false, since nothing was actually updated, if I'm trying to update my metadata to a certain value, and the end result is that the value in the database matches the value I submitted, isn't that a win?  In other words, even though no UPDATE query was actually executed, the postmeta was ""updated"" to have the value that was specified in update_post_meta().

Here's an example of when this could be an issue:

{{{
function my_plugin_ajax_save_metadata() {
    // create a success flag
    $success = true;
    // $postid passed in via post variables
    $postid = $_POST[ 'postid' ];
    // data fields from post passed in from a serialized array
    parse_str( $_POST[ 'data' ], $fields );
    // my custom post meta fields all have names that begin with _mymeta
    foreach( $fields as $key => $val ) {
        // if a field is one of my meta fields, attempt to update it
        if ( false !== strpos( $key, '_mymeta' ) ) {
            // if $val is the same as what's already in the db, $success will be false
            $success = update_post_meta( $postid, $key, $val );
        }
        if ( false === $success ) {
            // uh-oh, update_post_meta failed, need to handle it
            // but updating a meta value to the same value is not really a fail
            $message = ""Error updating metadata: $key = $val"";
            break;
        }
    }
    echo ( $success ) ? 'Success.' : $message;
    exit;
}
add_action( 'wp_ajax_save_meta', 'my_plugin_ajax_save_metadata' );
}}}

Of course, I could use get_post_meta() to find out if values have changed before calling update_post_meta(), but since update_metadata() already does this (line 131), it seems wasteful for me to have to do it.

I guess another alternative would be to return something besides TRUE or FALSE when the values are the same, but I'm not sure what that would be.
"	mcbenton
Future Releases	10770	wp-cron uses excesive CPU cycles		General	2.9	normal	critical	Future Release	defect (bug)	new	reporter-feedback	2009-09-12T11:49:09Z	2010-02-20T18:37:21Z	"Users are suddenly finding their accounts suspended because of excessive CPU cycles. However after investigating it appears the web hosting companies are properly configured and no hacks have occured. It seems that wp-cron is looping and consuming huge amounts of cpu cycles.

'''Versions:'''
This occurs across the past several versions on fully updated versions.

'''The effect:'''
Excessive CPU cycles with resulting suspension of a users account.

'''Plugins and Theme:'''
I detect no relationship to plugins and themes. I am presently running only 8 plugins.

'''Frequency:'''
Sadly, this is an intermittent issue. But a check of the Wordpress.org forum will show regular questions about this problem.

'''Server Environment:'''
Host is [http://www.inmotionhosting.com]. Fully updated and seemingly well maintained.

'''Additional:'''
There is a link from a 2.6 problem at [http://trinity777.wordpress.com/2008/10/28/wordpress-26-the-issue-of-wp-cronphp/]. Although it refers to an old version I think the issue is still unresolved and his work might prove useful to you.

Thanks
"	jbevans
Future Releases	24057	"wp_list_bookmarks links target="""""		General	3.5.1	normal	minor	Awaiting Review	defect (bug)	new	reporter-feedback	2013-04-12T11:28:53Z	2013-04-15T23:41:22Z	"When adding links via the add links function in WordPress, the default target of the link is _none.

The problem is, the code generated for that code is
<a href=""..."" target="""">, target being an empty string. This is not HTML5 compliant, as target has to have at least 1 character."	moscar09
Future Releases	17015	wp_list_pages incorrect hierarchy when using include and sorting by title		General	3.1	normal	minor	Awaiting Review	defect (bug)	new		2011-04-01T17:02:31Z	2011-04-02T04:12:21Z	"I am using wp_list_pages to create a page hierarchy. I only want the grandchildren of specific pages, so I generate a list of page IDs to send to wp_list_pages. I sort them by page title.  The hierarchy is not handled correctly when a grandchild's title sorts before its parent.

How it should come out:[[BR]]
About Us[[BR]]
 -Board of Directors[[BR]]
   --Annual Reports[[BR]]
 -FAQ[[BR]]
 -Initiatives[[BR]]
  --Ohio...[[BR]]
  --Reach[[BR]]

How it comes out:[[BR]]
About Us[[BR]]
 -Annual Reports[[BR]]
 -Board of Directors[[BR]]
 -FAQ[[BR]]
 -Initiatives[[BR]]
  --Ohio...[[BR]]
  --Reach[[BR]]

I've moved things around and verified that this sorts correctly:[[BR]]
About Us[[BR]]
 -Board of Directors[[BR]]
   --ZZZAnnual Reports[[BR]]
 -FAQ[[BR]]
 -Initiatives[[BR]]
  --Ohio...[[BR]]
  --Reach[[BR]]

If one grandchild has a sort order above its parent, all the grandchildren are pulled above the parent in the hierarchy. For example:[[BR]]
About Us[[BR]]
 -Board of Directors[[BR]]
   --ZZZAnnual Reports[[BR]]
 -FAQ[[BR]]
 -AAAAOhio...[[BR]]
 -Reach[[BR]]
 -Initiatives[[BR]]"	JohnColvin
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	21659	wp_mail() problem with Reply-To header		General	3.4.1	normal	normal	Awaiting Review	defect (bug)	new		2012-08-22T14:43:43Z	2012-08-22T14:43:43Z	"I am using in email headers also Reply-To:

{{{
$headers .= ""Reply-To: \""$name\"" <$email>\r\n"";
}}}

But there is a problem when name contains special non-English characters.

Example (from email headers):

Name: Žlutý kůň

{{{
Reply-To: =?UTF-8?Q? ""=C5=BDlut=C3=BD_k=C5=AF=C5=88"" _ <my@email.com>,
  ?=@example.com
}}}

I think that it is somehow related to wp_mail() function, because I also tried to use SMTP plugin and it worked well:

{{{
Reply-To: =?UTF-8?Q?""=C5=BDlut=C3=BD_k=C5=AF=C5=88""_<my@email.com>?=
}}}

Also when I use simply mail() instead of wp_mail() then everything works well. Problem can be seen only for Reply-To header, all others work well (for example From).

I am using WP 3.4.1."	pavelevap
Future Releases	16516	wp_page_menu documentation of the sort_column parameter		General	3.0.5	normal	trivial	Awaiting Review	defect (bug)	new		2011-02-10T15:13:13Z	2011-02-10T15:13:13Z	"The [http://core.trac.wordpress.org/browser/tags/3.0.5/wp-includes/post-template.php#L810 source code documentation] for wp_page_menu reads:

{{{
* <li><strong>sort_column</strong> - How to sort the list of pages. Defaults
* to page title. Use column for posts table.</li>
}}}

The actual default value is {{{'menu_order, post_title'}}} (correctly, as per [http://core.trac.wordpress.org/ticket/10266 Ticket 10266]).

"	FrancescoRizzi
Future Releases	22739	wp_register_script/wp_enqueue_script problem		General	3.4.2	normal	minor	Awaiting Review	defect (bug)	new	reporter-feedback	2012-12-04T18:51:01Z	2013-01-16T04:27:53Z	"First of all: sorry for my bad English.
Hi, i've seen may be a bug while programming a plugin (Len Slider).
I have some handle-scripts like jquery, jquery-ui to enqueue, its ok. Also I have my known js-files to enqueue, ok too. BUT! When I want to enqueue dynamic js (gets from folders via glob), it enqueue too BUT BEFORE jquery, jquery-ui itc. When I enqueue script with custom handle and in foreach loop, BUT with deps parameter as array of jquery, jquery-ui etc. And this dynamic js-file loads BEFORE jquery or jquery-ui! Now I solve the problem by load known handles jquery, jquery-ui in header and my own in footer, but i think we need to look for core to solve it.

You can see it on Len Slider in len-slider/lib/lenslider.class.php:313 - lenslider_make_skins_files_wp_head method

Also I think about parameter like priority for wp_register_script/wp_enqueue_script(style) functions to load it by this range."	tigusigalpa
Future Releases	12657	wp_signon() adds one filter per call		General	3.0	normal	normal	Future Release	defect (bug)	new		2010-03-20T11:52:10Z	2010-10-02T00:35:56Z	"If wp_signon() is called multiple times, the filter will be added multiple times. Next to this a lot of the function seems to be just typed in in the wish that it does work instead of doing things properly. See quote: ""ugly hack to pass this to wp_authenticate_cookie"" or leftover TODO markings and the like.

Should be put in order prior to next release."	hakre
Future Releases	18944	wrong url in sortable column headers when behind a reverse proxy		General	3.2.1	normal	normal	Awaiting Review	defect (bug)	new	reporter-feedback	2011-10-14T11:50:57Z	2012-08-09T18:33:29Z	"Hi, I have a wordpress site behind a reverse proxy. All works fine but for the urls used in the headers of sortable columns.

For instance, the links of ""Title"", ""Author"", etc. of the table of posts in wp-admin/edit.php --> Posts report something like ""http://backend/backend-dir/..."" while they should be ""http://frontend/frontend-dir/..."".

I don't think this is a proxy configuration problem because, AFAICS, the rest of the site is working: I can make posts, pages, media, install themes and plugins.

I tried to play with $current_url al line 649 of
wp-admin/includes/class-wp-list-table.php 
but with no luck.

I suppose that pagination may have the same problem.

"	gamboz
Future Releases	19332	'Edit Category' page lacks hooks to edit form fields		General	3.2.1	normal	minor	Awaiting Review	enhancement	new		2011-11-22T17:18:13Z	2011-11-22T17:18:13Z	"The default 'Name', 'Slug' and 'Description' form fields are stuck in place on Categories and Custom Taxonomies. 
There are hooks before and after the form (eg {$taxonomy}_pre_edit_form), but nothing to modify the basic output. 
These fields, especially 'slug', can scare civilians and it would be nice not to have to use JS to hide them."	duncanjbrown
Future Releases	22325	Abstract GPCS away from the superglobals		General		normal	minor	Future Release	enhancement	new		2012-10-30T21:15:41Z	2013-03-21T00:27:16Z	"As discussed at #wpcs, it looks like we want to move away from directly using the GPCS superglobals. This gives us a way to handle slashing backwards compatibility moving forward.

This is still a heap of versions away, but this is a way to keep any notes central."	rmccue
Future Releases	23471	Abstraction of post format parameters (wp_update_post(), XML-RPC, template tags)		General	trunk	normal	normal	Future Release	enhancement	new		2013-02-13T19:55:58Z	2013-05-16T12:07:38Z	"#19570 is introducing a UI for post formats. Correspondingly, various post meta fields will be introduced to store the extended data that's used in some post formats (eg. the URL field for a link or the source field for a quote).

Anything that interacts with the XML-RPC API and wants to support post formats (eg. future versions of the [http://wordpress.org/extend/mobile/ WordPress mobile apps]) will therefore need to:

 1. Send the various post format meta fields in its requests, and
 2. Receive the various post format meta fields in responses.

There should be some abstraction available at all levels of saving and fetching posts, don't we have to deal with the post meta fields directly. We should:

 1. Introduce a new parameter to the `wp.newPost` and `wp.editPost` XML-RPC methods for specifying the values of the extended post format fields when saving posts,
 2. Introduce a new parameter to the `wp.getPost` and `wp.getPosts` XML-RPC methods for returning the values of the extended post format fields when fetching posts,
 3. Introduce a new parameter to `wp_update_post()` for specifying the values of the extended post format fields when saving posts, and
 4. Introduce template tags for displaying/returning the values of the extended post format fields.

Point number 4 may be being covered somewhere else. I know it's been mentioned in IRC but I couldn't find mention of it on Trac.

The end result of this is that extended post format data is abstracted from its storage method.

Consideration: Which of these fields will be required and which are optional (on a per-post-format basis).

Thoughts? I'm happy to volunteer a first patch (or patches)."	johnbillion
Future Releases	18816	Add 'offset' parameter and 'ancestral' boolean to wp_nav_menu		General		normal	normal	Awaiting Review	enhancement	new		2011-09-29T16:13:42Z	2011-09-29T16:13:42Z	Since we can now call wp_nav_menu multiple times and there is the very useful 'depth' parameter, I believe adding an 'offset' parameter would be very beneficial in many situations. This would allow you to start at the children of the main pages for example and combined with depth it becomes very powerful. An 'ancestral' => 'true' option could output only menu items that the current page is a descendant of. Currently if you want to display a main menu in the header and then a submenu on page.php you either need a tricky custom walker or terrible CSS 'visibility:hidden' or 'display:none' situations.	signyourbikeout
Future Releases	21014	Add Action to Form Tags In Settings Pages		General	3.4	normal	normal	Awaiting Review	enhancement	new		2012-06-18T19:04:14Z	2012-06-18T19:04:14Z	"It would be nice to have additional hooks that allow adding attributes to form tags in settings pages.

For example, if you would like to allow a user to upload an image in a settings page, you need to add the enctype attribute to the form tag. Having a hook would allow you to avoid doing this with JS.

user-edit.php and user-new.php allow this using the 'user_edit_form_tag' and 'user_new_form_tag' hooks respectively, and it appears that edit-tag-form.php is adding this also. (http://core.trac.wordpress.org/ticket/15261)"	desrosj
Future Releases	24579	Add Drag'n'Drop UI to plugin and theme manual uploaders		General	trunk	normal	normal	Awaiting Review	enhancement	new		2013-06-14T17:03:38Z	2013-06-14T22:45:31Z	"We have this nice looking easy to use drag-n-drop UI for our media, is there anything stopping us from having it for our plugin and theme uploaders? I know most people use the search that goes through the .org repo, but it's foolish to think that's the only place people ever get their products. This would help facilitate a consistent user experience throughout the entire WP Admin.
"	tw2113
Future Releases	21168	Add ability to remove a parent theme's page templates		General		normal	normal	Awaiting Review	enhancement	new		2012-07-05T19:32:31Z	2012-08-05T23:54:15Z	"When building a website using a child theme, I'll often want to remove page templates that the parent theme provides but aren't useful/relevant to the specific site I'm building. 

You can create a page template with the same name to override the parent theme's, but you can't simply remove it.

This could be a use case of #13265, or we could add function that leverages #13265"	billerickson
Future Releases	18296	Add an action to Custom_Image_Header admin_page()		General		normal	minor	Awaiting Review	enhancement	new		2011-07-29T17:31:17Z	2011-09-01T15:25:24Z	Add an action (do_action('custom_header_top');) to the admin page for themers to add more settings using the settings api.	wpsmith
Future Releases	18550	Add args to signup_finished action		General	3.2.1	normal	normal	Awaiting Review	enhancement	new		2011-08-31T00:07:01Z	2011-08-31T00:31:40Z	"In wp-signup.php there are 2 calls to do_action( 'signup_finished' );

1) When an user sings up.
2) When a new user sing up and a new site (in Multisite) is created.

It'd be good to have a way to diferenciare this differente scenarios. Also, it'd be good to have the registered user info passed to this action.
"	rabino
Future Releases	11212	Add filter to wp_parse_args()		General	2.9	lowest	normal	Future Release	enhancement	reopened		2009-11-21T05:23:01Z	2011-02-02T09:23:16Z	"This will allow for some l33t hackery (basically being able to modify a wide variety of functions).

Think we could squeeze it into 2.9 since it's just a filter?"	Viper007Bond
Future Releases	23237	Add tag function to format markup		General		normal	normal	Awaiting Review	enhancement	new		2013-01-19T06:46:55Z	2013-05-16T04:32:30Z	"Related to #23236 I'd like to add a generic function for making html tags:

{{{
wp_tag( $tagname, $attrs, $inner_html ) // returns an html tag
wp_tag_e( $tagname, $attrs, $inner_html ) // echoes an html tag
}}}

$attrs could be an array|string, and the tag should only close if $inner_html is defined, like tag() in [http://phat.airve.com phat]."	ryanve
Future Releases	16431	Adding include to wp_list_comments()		General		normal	normal	Awaiting Review	enhancement	new		2011-02-01T04:27:50Z	2011-02-01T07:23:31Z	"I have been building a simple forum on Wordpress using posts as questions, top-level comments as answers, replies as comments on answers. 

Choosing a best answer is available, which adds the ID of the chosen answer (comment) ti the postmeta of the question. 

I would like to arrange my answers so that the first one is the chosen best answer, and below you can view the normal flow of answers.

It would be nice if this could be done using wp_list_comments(). I would call it once and use ""include"" to show just the one comment, and then I would call it again without the include to show the usual flow of comments. 

I believe this might be generally helpful in other cases as well though.  "	danielpataki
Future Releases	22631	Allow change of dropins folder		General	3.5	normal	normal	Awaiting Review	enhancement	new		2012-11-29T07:02:44Z	2012-11-29T15:44:06Z	"Dropins are stored in the `wp-content` directory. Currently there is no way to alter this (short of editing core code).

The `get_dropins()` function does not utilize filters or predefined constants in any way.

Probably the best method here would be to define `WP_DROPINS_DIR` constant in `/wp-includes/default-constants.php` that can be overridden in wp-config.php."	bungeshea
Future Releases	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
Future Releases	17526	Allow themes and plugins to disable options in the admin		General		normal	normal	Future Release	enhancement	new		2011-05-20T20:19:50Z	2011-05-20T22:09:04Z	"I frequently set options in functions.php by hooking 'pre_option_*', thus whatever the user does in the admin interface they can't change it.

There should be a filter to make the option obviously disabled to the user (it should probably also set the disabled attribute on the form fields) and perhaps add a short message saying for instance ""This option was changed by $plugin_name, visit $link to change it."" or ""This option has been set by the '$theme_name' theme. It cannot be changed."""	holizz
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	21521	Audit use of set_time_limit()		General	3.4.1	normal	normal	Future Release	enhancement	new		2012-08-08T17:28:21Z	2012-10-18T13:07:12Z	Core calls this half a dozen times. The call in wp_get_http() interferes with unit tests. Unit tests will terminate 60 seconds after wp_get_http() is called. Let's justify each use of set_time_limit() and remove what we can.	ryan
Future Releases	18954	Automatically whitelist screen options added via add_screen_option()		General		normal	normal	Future Release	enhancement	new	early	2011-10-14T22:54:08Z	2011-11-25T19:27:18Z	"{{{set_screen_options()}}} currently maintains a hardcoded whitelist of screens that can set options.

The list is extendable via the filter:

{{{
apply_filters('set-screen-option', false, $option, $value);
}}}

but that's sort of a pain.  If a plugin calls {{{add_screen_option()}}}, it should be added to the whitelist automatically.

Also note that {{{set_screen_options()}}} is called so early, there's no convenient place for plugins to add to the {{{set-screen-option}}} filter.  The best workaround I've been able to come up with is to manually call {{{set_screen_options()}}} again inside the page's {{{load-$hook}}}.

Example naive plugin code that does not work in <=3.3.

{{{
# Inside a menu page's load-$hook
// Display per-page settings in screen options
add_screen_option( 'per_page', array( 'label' => __( 'Things' ) ) );
}}}"	mdawaffe
Future Releases	21258	Autosuggest for tags suggests tag already chosen		General		normal	normal	Awaiting Review	enhancement	new		2012-07-13T12:38:03Z	2012-07-13T12:38:03Z	"When entering tags in the meta box on a post (or page) edit screen in admin, the AJAX autosuggest will suggest tags that have already been added to the post (i.e. shown below the input field).

Steps to reproduce:

1. Go to the post edit screen.
2. Add a tag (example: ""Apple"") to the current post.
3. Type ""App"" in the tag entry field and wait for autosuggest to come up.
4. ""Apple"" is listed in the suggestions dropdown.

I've investigated this a little, and I don't think there's a really easy patch for this (mostly because of how suggest.js works). However, it would imho be very elegant to fix this. Perhaps autocomplete.js can be of service here (see issue #12399)?"	roytanck
Future Releases	18561	Better Way to Insert Things Below Individual Posts		General	3.2.1	normal	minor	Awaiting Review	enhancement	new		2011-09-01T03:56:21Z	2013-04-22T19:02:15Z	"More and more plugins want to drop stuff in below each post (especially common among plugins focused on encouraging the sharing of content). There's not really a great way to do it, though, if your single-post-area doesn't end with the last line of body text. Many themes put the byline/date/metadata below -- rather than above, which used to be the norm -- the post content, including our own Twenty Eleven.  See the screenshot to see how ugly it is when a plugin (or two, or more) uses the the_content filter to insert something at the ""end"" of each post. 

Inserting the sharing and like rows (in this example) at the bottom of the post text before the byline/classification metadata seems wrong. It should go below that, so it is closely related to commenting, not part of the content itself. The plugin-generated widget is not ""by"" the post author, after all.

I have been told that options for addressing this are basically either modifying the theme and/or getting a new filter in place. Whatever we need to do, let's do it, because misplacing plugin-provided tools inside the content rather than after it is a) really bad IA, and b) crazy ugly."	jane
Future Releases	19825	Bugs and modifications to localize script		General		normal	normal	Awaiting Review	enhancement	new		2012-01-13T16:47:55Z	2012-01-18T20:00:08Z	"After working in trunk, I noted that I get a fatal error when trying to localize some objects with wp_localize_script informing me that I cannot use an object of that type as an array. For tests, I've done this with $wp, $wp_query, $wpdb, and $wp_scripts on a clean install with no plugins.

I also have been working on sites that would like to compress all of their JS calls into a single request where possible, but in the past I was not able to keep localizations that certain scripts required, and had to leave them out.

With the changes I've made in this patch file, the issues regarding pushing arbitrary objects for localization are addressed. It also stores those objects, rather than a string of JS with $wp_scripts. This allows me to pull the localizations used for some files, and attach them instead to another file using wp_localize_script.

As a side benefit, by not processing the object into JS until output, we are able to preserve the data cleanly, and reduce process on any script that may be dequeued later that has such dependencies.

I would like to submit this patch as a core patch for a future release. Its design is fully compatible with existing functionality in 3.3, with the exception of any code modifying the underlying data key in an enqueued script directly."	ssmathias
Future Releases	18243	Can you make `add_settings_error` work for custom top-level admin menus?		General	3.2.1	normal	normal	Awaiting Review	enhancement	new		2011-07-25T13:13:33Z	2013-03-15T23:46:07Z	Currently when trying to use the Settings API on custom top-level admin menus, `add_settings_error` will fail to work. It fails silently, and no error message is displayed. I'm told this is because `options-head.php` is not included on custom top-level admin menu pages.	jcskyrocket
Future Releases	20298	Change requires to require_once		General	3.3.1	normal	normal	Awaiting Review	enhancement	new	close	2012-03-24T22:39:20Z	2012-04-01T17:58:37Z	"Wordpress partially uses ""require"" to include files. I'd prefer to have require_once everywhere where a file really shouldn't be included twice. I'm currently developing an HTTP-Server (https://github.com/pp3345/Pancake) with a function to keep ""static"" codefiles (for example files that only do class-definitions and don't actually really execute any code) in some kind of a cache so that they don't need to be loaded again on every single request in order to improve performance. When I now, for example, load the wp-includes/class-wp-walker.php into the cache at the beginning and then Wordpress tries to require the file again, it fails with an Fatal Error due to trying to define the class again. Using require_once instead of require in Wordpress can be done quickly and would easily fix this. Also, it could improve the codes quality a bit."	pp3345
Future Releases	22110	Check for current conditional		General	3.4	normal	normal	Awaiting Review	enhancement	new		2012-10-05T17:12:18Z	2012-10-11T00:37:05Z	"More than once I've needed a programmatic way to determine what page is being displayed, for example when implementing event tracking recently:


{{{
add_action( 'wp_enqueue_scripts', function() {
	wp_enqueue_script( 'my-site', get_template_directory_uri() . '/js/mysite.js', array( 'jquery' ), '1', true );

	// Figure out what type of page we're on
	$is = '';
	foreach ( $GLOBALS['wp_query'] as $key => $value ) {
		if ( true === $value && 'is_' === substr( $key, 0, 3 ) ) {
			$is = substr( $key, 3, strlen($key) );
			break;
		}
	}
	wp_localize_script( 'my-site', 'event_tracking', array(
		'category' => $is,
	) );
} );

}}}
And then used like:

{{{
<a onclick=""_gaq.push(['_trackEvent', event_tracking.category, 'more-stories', 'click']);"">Action</a>
}}}

Now granted the above way to determine the current page is a little janky, and has at least one flaw (on custom post type archives because both ""is_archive"" and ""is_post_type_archive"" are set, and it will find ""is_archive"" first, every time).  TBH this was me with a bowl of chili in one hand trying to avoid typing out ""if ( is_* ) { } elseif ( is_* ) { } elseif ( is_* ) {} ..."".  

A saner function would probably explicitly check each conditional, which would make it a little more tedious but also more maintainable:

{{{
function where_am_i( $return = 'simple' ) {
	global $wp_query;
	
	if ( ! isset( $wp_query ) ) {
		_doing_it_wrong( __FUNCTION__, __( 'Conditional query tags do not work before the query is run. Before then, they always return false.' ), '3.5' );
		return false;
	}
	
	$primary = null;
	$secondary = null;
	$tertiary = null;
	
	// Tried to maintain the hierarchy from query.php
	if ( true === $wp_query->is_robots ) {
		$primary = 'robots';
	} elseif ( true === $wp_query->is_attachment ) {
		$primary = 'attachment';
		$secondary = 'single';
		$tertiary = 'singular';
	} elseif ( true === $wp_query->is_page ) {
		$primary = 'page';
		$tertiary = 'singular';
	} elseif ( true === $wp_query->is_single ) {
		$primary = 'single';
		$secondary = 'singular';
	} elseif ( true === $wp_query->is_search ) {
		$primary = 'search';
	} elseif ( true === $wp_query->is_time ) {
		$primary = 'time';
		$secondary = 'date';
		$tertiary = 'archive';
	} elseif ( true === $wp_query->is_day ) {
		$primary = 'day';
		$secondary = 'date';
		$tertiary = 'archive';
	} elseif ( true === $wp_query->is_month ) {
		$primary = 'month';
		$secondary = 'date';
		$tertiary = 'archive';
	} elseif ( true === $wp_query->is_year ) {
		$primary = 'year';
		$secondary = 'date';
		$tertiary = 'archive';
	} elseif ( true === $wp_query->is_date ) {
		$primary = 'date';
		$secondary = 'archive';
	} elseif ( true === $wp_query->is_category ) {
		$primary = 'category';
		$secondary = 'archive';
	} elseif ( true === $wp_query->is_tag ) {
		$primary = 'tag';
		$secondary = 'archive';
	} elseif ( true === $wp_query->is_tax ) {
		$primary = 'custom_taxonomy';
		$secondary = 'archive';
	} elseif ( true === $wp_query->is_author ) {
		$primary = 'author';
		$secondary = 'archive';
	} elseif ( true === $wp_query->is_post_type_archive ) {
		$primary = 'post_type';
		$secondary = 'archive';
	} elseif ( true === $wp_query->is_feed ) {
		$primary = 'feed';
	} elseif ( true === $wp_query->is_trackback ) {
		$primary = 'trackback';
	} elseif ( true === $wp_query->is_comments_popup ) {
		$primary = 'comments_popup';
		$secondary = 'comments';
	} elseif ( true === $wp_query->is_preview ) {
		$primary = 'preview';
		$secondary = 'singular';
	} elseif ( true === $wp_query->is_admin ) {
		$primary = 'admin';
	} elseif ( true === $wp_query->is_comment_feed ) {
		$primary = 'comment_feed';
		$secondary = 'comments';
		$tertiary = 'feed';
	} elseif ( true === $wp_query->is_404 ) {
		$primary = '404';
		$secondary = 'singular';
	} elseif ( true === $wp_query->is_home ) {
		$primary = 'home';
		if ( true === $wp_query->is_posts_page ) {
			$secondary = 'posts_page';
			$tertiary = 'page';
		} else {
			$secondary = 'static_page';
		}
	}
	
	if ( 'detailed' === $return ) {
		$details = compact( $primary, $secondary, $tertiary );
		$details = array_filter( $details ); // Remove empty
		return $details;
	}
	
	// 'simple' === $return
	return $primary;
}
}}}

Should it use $wp_the_query so that it always acts on the main query?  "	mintindeed
Future Releases	13504	Create cookie name hash option		General		normal	normal	Future Release	enhancement	new		2010-05-23T16:45:47Z	2010-05-23T16:46:10Z	"I put this on future release but we should do it early in 3.1. Currently, by default,

an upgraded MU install has an empty string as a cookie name hash

a single WP site uses the siteurl option as the seed for a MD5 hash

a WP -> WP 3.0 network uses the main site's siteurl option + '/' as the seed for a MD5 hash

We should move these to a common more appropriately name option/site option and give the super admin(s) the ability to change it and/or generate a new one."	wpmuguru
Future Releases	20317	Delete auto-draft using window.onbeforeunload		General		low	normal	Awaiting Review	enhancement	new	dev-feedback	2012-03-28T22:50:27Z	2012-03-28T22:53:23Z	"When a user goes to post-new.php, a new auto-draft post is created.

Old auto-drafts are garbage-collected: #19663

To lessen the need for GC, we could send an AJAX request to delete the auto-draft immediately when the user navigates away from the page (but not when he presses the Submit button).

"	scribu
Future Releases	15930	Deleted page bin view?		General	3.0.3	normal	normal	Future Release	enhancement	new	dev-feedback	2010-12-21T10:32:30Z	2010-12-26T22:43:21Z	"I hoped I was able to see the pages which I delete (in the trashbin) but the all stay dark... So I can't view them!

I think it would be a good feature to see them to see if somebody didn't delete the wrong page! Or when you need something form a deleted page that you can still get it without restoring it first"	JonezJeA
Future Releases	21714	Enable Intermediate choice in UI if Full Size Image is exact match to Intermediate Image		General	3.4.1	normal	minor	Awaiting Review	enhancement	new		2012-08-28T15:56:09Z	2012-08-28T15:56:09Z	"
This is simply a minor usability enhancement for Media Gallery. If an image is uploaded that is exactly the same size as an intermediate image (300x300 = Medium for example) it is not a choice when inserting that image into a post. It would be nice if it was a choice pointing to the full/original image since full is the same size as the intermediate.

It seems to be caused in the image_downsize function in /wp-includes/media.php because image_get_intermediate_size returns false. 

I believe image_downsize can be updated as such to provide this enhancement:

Line 162 (if statement) Currently:
{{{
	if ( !$width && !$height && isset($meta['width'], $meta['height']) ) {
		// any other type: use the real image
		$width = $meta['width'];
		$height = $meta['height'];
	}
}}}

could be updated to read the intermediate width and height and set intermediate to true if it is an exact match to the original image:

{{{
	if ( !$width && !$height && isset($meta['width'], $meta['height']) ) {
		// any other type: use the real image
		$width = $meta['width'];
		$height = $meta['height'];
		// add check for real image being exact match to intermediate image to enable intermediate choice in UI
		if (isset($_wp_additional_image_sizes[$size])) {
			$goal_width = intval($_wp_additional_image_sizes[$size]['width']);
			$goal_height = intval($_wp_additional_image_sizes[$size]['height']);
		} else {
			$goal_width = get_option($size.'_size_w');
			$goal_height = get_option($size.'_size_h');
		}		
		if ($width == $goal_width && $height == $goal_height)
			$is_intermediate = true;
	}

}}}


Thanks for considering, and hope I put this in the right place,
Andrew
"	andrewteg
Future Releases	24588	Excerpt enhancement request		General		normal	normal	Awaiting Review	enhancement	new		2013-06-16T21:31:54Z	2013-06-17T08:29:50Z	"I originally posted this on WordPress StackExchange but I think that this should go to trac for consideration as well.

I was wondering what should be used in index.php (post listing page): `the_excerpt()` or `the_content()`?

1. Twenty Thirteen uses `the_content()` but this prints entire content unless `<!--more-->` exists and it completely ignores Excerpt field from [Posts > Add New > Excerpt].
2. So, I used `the_excerpt()` instead but this doesn't react to `<!--more-->` tag at all and it just grabs first 55 words or uses manual Excerpt and doesn't produce ""Read more..."" link.

What I think is the most expected behavior is this:

- print 55 words
- but react to `<--more-->`
- and if manual excerpt is specified, use this instead (most people don't want the beginning of their post to be their excerpt so this is of crucial importance)
- produce optional ""Read more..."" link

I know what you say here:
- http://codex.wordpress.org/Function_Reference/the_excerpt
- http://codex.wordpress.org/Excerpt
- http://www.rarst.net/script/wordpress-excerpt-teaser/

But what I described above looks like the most intuitive to me for post listing pages. The excerpt should be a single, configurable function that is suitable for both BLOG and ARCHIVES. And `the_content()` can stay for SINGLE.

Currently neither `the_content()` nor `the_excerpt()` works for BLOG and requires filters.

`the_content()` would do the job right but I think that most theme users aren't familiar with `<--more-->` tag and they rather expect that themes will create proper excerpts for post listing pages rather than displaying full post content (and after all `the_content()` ignored manual excerpt so it's a big drawback). Currently this can be achieved only with custom filters."	Looimaster
Future Releases	18391	Expand WP_DEBUG_LOG and make WP_DEBUG_DISPLAY work as expected		General		normal	normal	Future Release	enhancement	reopened		2011-08-13T05:45:21Z	2011-10-25T05:20:06Z	"== WP_DEBUG_LOG ==

WP_DEBUG_LOG currently creates wp-content/error.log. We should expand this to allow a path.

To do this, if WP_DEBUG_LOG is !== true, != 1, != 'true', (anything else?) and 0 === validate_file(), we should treat it as a path.

== WP_DEBUG_DISPLAY ==

Setting WP_DEBUG_DISPLAY to false does not set display_errors to false. Instead, it prevents display_errors from being set to on. This forces a call to ini_set to turn off display_errors, assuming your php.ini is set to On, as expected for a development environment configuration.

Instead, setting WP_DEBUG_DISPLAY to false should set display_errors to false. I've been thinking about this for months now, and the only situation I can come up with that this would be a compatibility issue would be when you deliberately have a production php.ini on production and a development php.ini in development. In this situation, WP_DEBUG_DISPLAY = false would screw up your development environment only -- the only breakage would be showing less errors, rather than more.

WP_DEBUG_DISPLAY === null can remain a passthrough.

Patch forthcoming."	nacin
Future Releases	23677	Feed autodiscovery for custom taxonomy and perhaps date archives		General	3.5	normal	normal	Awaiting Review	enhancement	new		2013-03-03T16:53:09Z	2013-03-03T16:53:09Z	"In #21648 we enabled the ""autodiscovery"" of feeds for custom post types. Further review of this solution reveals a few remaining issues:

a) Function `feed_links_extra()` in file `wp-includes/general-template.php` still does not add `<link>` tags for autodiscovery of either custom taxonomy archives or date (year/month/day) archives. You can argue that feeds for date archives might not be particularly useful, but they are generated, so why do we not provide links to them?  A helper function does exist to obtain the link for custom taxonomy archive feeds, but there is no corresponding support for date archives.

b) The helper functions for obtaining feed links in file `link-template.php` are not particularly easy to use, requiring much examination of the queried object.  If a theme or plugin wishes to include explicit hyperlinks to feeds (i.e. `<a>` tags) then it is presently forced to duplicate much of the code from function `feed_links_extra()`. I suggest the bulk of the code from here should be moved into a new function within `link-template.php` where it can be reused to generate either `<link>` or `<a>` tags as needed.

c) We seem to have a helper function for feeds containing search results with comments (`get_search_comments_feed_link()` in `wp-includes/link-template.php`). Whilst this feed is generated, it's not clear why ""search"" is treated specially here and why if this was considered useful there are no corresponding feeds for comments on other archives."	mdgl
Future Releases	21096	Filter on is_front_page return value		General		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-06-28T10:32:03Z	2012-06-29T13:05:58Z	"When you set a page (as 'placeholder' with same slug) as front page which is actually a post type archive to front page, is_front_page() will always return false on that page. The return value of the is_front_page() function is not filterable.

Attached patch adds this filter in the most basic way."	CoenJacobs
Future Releases	21641	Filter on pending/draft array in wp_insert_post()		General		normal	normal	Awaiting Review	enhancement	new		2012-08-20T16:53:56Z	2012-08-20T16:53:56Z	"Hi

In wp_insert_post() function, there is no possibility to add a status to the list of status for which postname can be set to empty (no filter). Thus, to have the 'pending' like behaviour for a custom status it seems you have to update the postname to '' and the gmt to 000-00 after the insert, as you have to hack the permalink construction too.

In the same way, it would be nice to add the $post parameter to the filter 'display_post_states' in the '_post_states($post)' function (wp-admin/includes/template.php), in order to add easily a post state according to a custom status of the post (seems better as retrieving the global $post of the admin loop).

Hope these are real issues. Sorry if not.

Regards
"	villagora
Future Releases	22612	Filterable default for wp_safe_redirect/wp_validate_redirect		General		normal	normal	Awaiting Review	enhancement	new		2012-11-27T21:00:22Z	2012-11-29T18:06:41Z	The default/fallback for {{{wp_safe_redirect}}} is {{{admin_url()}}}. It would be nice to have a filter to be able to modify this (e.g. redirect to {{{home_url()}}} instead, which is probably a better default anyway).	batmoo
Future Releases	20748	Include CPT Posts in Author Count & Archive Page		General		normal	normal	Awaiting Review	enhancement	new		2012-05-25T17:59:48Z	2012-05-25T18:07:20Z	"For whatever reason, the default behavior is to only count the number of 'post' that an author has published.

With the advent of custom post types, they should be included as well if the CPT has the 'author' capability.

Currently, the author archive can include CPTs if you manually alter the query - this should be enabled by default if authorship is allowed."	iridox
Future Releases	20439	Introduce __return_one function		General		normal	normal	Awaiting Review	enhancement	new		2012-04-13T19:38:53Z	2012-04-30T18:37:22Z	Following #20357 and #18845 , I feel it would be useful to have a return function for 1 for use with filters.	bananastalktome
Future Releases	23169	Introduce register_post_status_for_object_type		General		normal	normal	Future Release	enhancement	new		2013-01-10T08:35:46Z	2013-05-10T12:37:39Z	Similar to what `register_taxonomy_for_object_type` does with taxonomies.	kovshenin
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	17301	Keep the connection open when doing upgrades or long-running operations		General		normal	normal	Awaiting Review	enhancement	new		2011-05-02T06:27:39Z	2012-04-28T17:44:21Z	"When we do long-running operations like upgrades-over-FTP, we may go a while without sending any data, which may cause the connection to be closed. We should investigate whether we can send some ""hey, still here"" dummy data down the pipe to keep the connection from being unceremoniously closed on us.

For example, Rackspace Cloud Sites runs behind load balancers that cut the connection after 30 seconds of no data. I was able to defeat it by manually flushing some dummy data like so:

{{{
<?php

for ( $i = 1; $i < 46; $i++ ) {
	echo ""$i...<br />\r\n"";
	flush();
	sleep( 1 );
}
echo ""DONE"";
}}}"	markjaquith
Future Releases	22283	Load login page over HTTPS if FORCE_SSL_LOGIN is set		General		normal	normal	Awaiting Review	enhancement	new		2012-10-26T03:08:52Z	2012-11-24T15:09:34Z	"Currently, if FORCE_SSL_LOGIN is set, we will make the HTTP POST request containing the username and password over SSL when logging in, but not the GET request for the login page.  Users shouldn't have to examine HTML to figure out if their password is being sent in plain text.  To ensure user confidence that they are logging in via an encrypted connection, we should redirect requests for the login page to https:// if FORCE_SSL_LOGIN, not only if FORCE_SSL_ADMIN is set.  Troy Hunt explains the issue well in his post here - http://www.troyhunt.com/2011/01/ssl-is-not-about-encryption.html

While FORCE_SSL_ADMIN is obviously ""best"" it is not always possible or practical, but this at least makes the login experience consistent.

"	barry
Future Releases	19745	Login Form Dropdown		General	3.3.1	normal	minor	Awaiting Review	enhancement	new	close	2012-01-05T02:35:47Z	2012-01-06T02:38:39Z	It would improve user experience if the login button on the admin bar had a dropdown with a login form. This only applies to websites that show the admin bar to logged out users. 	dancole
Future Releases	18680	Make SSL login-only possible (while leaving admin unencrypted)		General	3.2.1	normal	normal	Awaiting Review	enhancement	new	reporter-feedback	2011-09-16T05:54:33Z	2011-09-27T17:19:50Z	"There are two options to be set in wp-config.php to enforce secure connections.

With the following configuration, the login AND the backend will be done via SSL:
{{{
define( 'FORCE_SSL_ADMIN', false ); // or true
define( 'FORCE_SSL_LOGIN', true );  // or false
}}}
As those are 'FORCE' parameters, one might consider it correct that, even though one is set to 'false', both will be via HTTPS.

However, WordPress is currently missing an option to have ONLY the login data sent encrypted and go on to the admin interface via a normal (non-encrypted) connection. That scenario requires additional redirections on the webserver."	multimule
Future Releases	22534	Make bundled JavaScript LibreJS compatible		General		normal	normal	Awaiting Review	enhancement	new		2012-11-22T01:27:21Z	2012-12-16T06:45:43Z	"Many free software advocates don't want to run proprietary JavaScript code in their browsers. The Free Software Foundation has releases a Firefox extension called LibreJS that blocks non-free JavaScript from running: https://www.gnu.org/software/librejs/

WordPress is released under the GPLv2 license, but LibreJS still blocks WordPress JavaScript files because they don't have the appropriate license blocks.

To fix this, we can either add comments to the top of each .js file with the license, or we can use JavaScript web labels to define the license for each js file in HTML.

Here are instructions for marking your JavaScript as free so that LibreJS users will execute it:
https://www.gnu.org/software/librejs/free-your-javascript.html"	micahflee
Future Releases	11438	Make relative links absolute in feed		General	2.9	normal	major	Future Release	enhancement	new	close	2009-12-14T23:21:21Z	2011-04-06T04:23:47Z	Relative links should be made absolute for the feed, because {{{/}}} means nothing in a feed reader.	caesarsgrunt
Future Releases	17340	Mark up script-loader.php versions for programmatic updating		General		normal	normal	Awaiting Review	enhancement	new		2011-05-06T18:51:56Z	2011-05-08T14:51:36Z	"Whenever we update one of our dev CSS or JS files, we have to use YUI to re-minify them, and bump their version number in script-loader.php. The YUI part can be done programmatically, but it's not quite possible to bump the script-loader.php version numbers without manual intervention. If the number strings (yyyymmdd{optional-abcd suffix}) were marked up with PHP comments in a standardized way, we could automate that step as well.

Since any script would have the file name in hand, I propose the following:

{{{/*#wp-admin/css/wp-admin.dev.css#wp-includes/css/fake.dev.css*/'20110203b'}}}

That is, a PHP comment block that immediately starts with a hash (#) and is followed by one or more dev URLs that the version number applies to (multiple ones separated by another hash), and immediately followed by a version string enclosed in single quotes, in the format:

{{{/'([0-9]{4})([0-9]{2})([0-9]{2})([a-z]?)'/}}}"	markjaquith
Future Releases	20725	Media library inconsistency		General	3.3.2	normal	normal	Awaiting Review	enhancement	new		2012-05-22T10:26:45Z	2012-05-22T10:26:45Z	"I need to put extra filters using restrict_manage_posts to Media library and i have noticed, that my filters did not appear on Media library iframe, opened when adding new media in post. It is handled with wp-admin/includes/media.php via media_upload_library_form function, which seems to be very old comparing to media library in class-wp-media-list-table

e.g. it does not use 	$this->months_dropdown( 'attachment' ); but wrotes 25 rows of code which  do the same.

IMO it could be migrated to the new code

also it misses the 			
do_action( 'restrict_manage_posts' );
line, which is important for my desired functionality (when i hardcode it there, it works)"	thomask
Future Releases	22293	New Filter for wp_update_term		General		normal	normal	Awaiting Review	enhancement	new		2012-10-26T22:26:54Z	2012-10-26T22:46:31Z	"I need a filter for $slug in this function. I want to check if there is a page with the same slug, because i don't use the category base.

Thanks very much."	baernty
Future Releases	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
Future Releases	18003	On the Credits page, add Male/Female tags for each person, for use in translation		General		normal	normal	Future Release	enhancement	new		2011-07-06T12:20:16Z	2011-07-06T18:16:56Z	"The Credits page mentions contributors along with their role in the project: ""Lead Developer"", ""Guest Committer"", etc.

When translating to certain languages (for e.g., Hebrew), these roles are translated differently when the person is male or female. For example, in Hebrew there would be a different translation for male lead developers (מפתח ראשי) and female lead developers (מפתחת ראשית).

This doesn't cause an issue with translation at the moment, since the only woman on the credits page that has her role mentioned in Jane, and she's the only ""User Experience Lead"". So in translation, we can translate everything else as male and only translate that string as female.

In the interest of future proofing the credits page, I suggest we add two different strings for each role - male and female. In English and other languages will use both the same way, but languages that are not gender-neutral will be able to translate them correctly. This would obviously require that we know the gender of all the people mentioned.

I tried very hard to ignore all the political aspects of this issue - I hope we can get through this without having to discuss them :)"	RanYanivHartstein
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	16755	PHP5-port - uniqid()		General	3.1	normal	normal	Awaiting Review	enhancement	new		2011-03-05T11:15:01Z	2011-03-05T11:15:01Z	"[http://www.php.net/manual/en/function.uniqid.php uniqid()] does not need a prefix (any longer).

Places in use can be checked if they need to have it passed or not.

Related: #16753"	hakre
Future Releases	13412	Parent parameter returns no results in get_pages()		General		normal	normal	Future Release	enhancement	new		2010-05-16T16:53:40Z	2010-05-16T17:03:13Z	"The get_pages() function in post.php returns no results when parent != 0, rather than returning the pages that are children of the immediate page. 

Given page ID 30, which has 3 child pages, calling get_pages('parent=30') will return nothing.

The problem is in the following lines (line ~2600 at the time of writing):
if ( $child_of || $hierarchical )
	$pages = & get_page_children($child_of, $pages);

Hierarchical, by default, is set to true, this this conditional will typically be true. When it does so, it filters out all of the pages retrieved up to this point and, by the time it returns, there are no pages left.

The quick work-around I'm currently using is to call the following instead:
get_pages('parent=0&hierarchical=0'), overriding the default value so that conditional doesn't execute.

The one exception to this is that calling get_pages('parent=0') should function even with this bug."	jda10487
Future Releases	18823	Pass $post_id  as second argument to delete_postmeta action		General	3.2	normal	minor	Awaiting Review	enhancement	new		2011-09-30T12:29:51Z	2011-09-30T14:38:00Z	"in every case (in WP 3.2) where a postmeta is deleted, the context is aware of the post_id or post_ids affected.  The do_action calls for added_postmeta, update_postmeta, and updated_postmeta all pass the post_id as the second argument.  For parallelism, and because it is useful, please pass it for delete_postmeta (and deleted_postmeta). 


"	Vynce
Future Releases	9763	Please include IdeaWebServer in $is_apache (in wp-includes/vars.php)		General	2.7.1	low	normal	Future Release	enhancement	new		2009-05-08T22:22:45Z	2013-01-06T09:04:39Z	"IdeaWebServer is a web server software developed an used in largest polish ISP server farm. This software handles over 205972 domains (according to http://top100.pl/). I hope its worth including support for IdeaWebServer in Wordpress.

Installing Wordpress on IdeaWebServer is easy (as it is mostly apache compatible), but two tweaks need to be done.

Tweak 1st: include IdeaWebServer in $is_apache

Tweak 2nd: use only ""http://host/redirect"" redirections (no ""Location: /somewere"", only ""Location: http://host/somewere"")

Here comes the patch (against r11244):
{{{
Index: wp-includes/vars.php
===================================================================
--- wp-includes/vars.php	(wersja 11244)
+++ wp-includes/vars.php	(kopia robocza)
@@ -65,7 +65,9 @@
  * Whether the server software is Apache or something else
  * @global bool $is_apache
  */
-$is_apache = ((strpos($_SERVER['SERVER_SOFTWARE'], 'Apache') !== false) || (strpos($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed') !== false)) ? true : false;
+$is_apache = ((strpos($_SERVER['SERVER_SOFTWARE'], 'Apache') !== false) ||
+(strpos($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed') !== false) ||
+(strpos($_SERVER['SERVER_SOFTWARE'], 'IdeaWebServer') !== false)) ? true : false;
 
 /**
  * Whether the server software is IIS or something else
Index: wp-includes/pluggable.php
===================================================================
--- wp-includes/pluggable.php	(wersja 11244)
+++ wp-includes/pluggable.php	(kopia robocza)
@@ -857,6 +857,9 @@
 
 	$location = wp_sanitize_redirect($location);
 
+	if ($location[0] == '/')
+		$location = get_bloginfo('url') . $location;
+
 	if ( $is_IIS ) {
 		header(""Refresh: 0;url=$location"");
 	} else {
}}}

[http://www.burghardt.pl/2008/03/wordpress-na-serwerze-ideawebserver-w-homepl/ More about this issues (in Polish).]"	burghardt
Future Releases	22303	"Please parse a ""vendor"" file"		General		normal	normal	Awaiting Review	enhancement	new	close	2012-10-29T15:31:54Z	2012-10-30T10:06:14Z	"Hi,

I'm working on improving Wordpress packaging in fedora.

One of our need is to allow the use of system libraries instead of bundled copy (forbidden by Guidelines).

I would like to propose, as various projects already, to include a ""vendor"" file.

Goals:
- without this file: no change
- with this file: use constant from it
- allow to define patch for each library (rather than a global WPINC)

Note: this is not the same as wp-settings, which are user configurable settings, while ""vendor"" are system configuration (not to be altered by users)

Work proposal.

(probably) in default-constants.php

if (file_exists('vendor.php')) include_once('vendor.php');

For PHPMailer (for exemple)

if (!defined('WP_PHPMAILER_INC')) define('WP_PHPMAILER_INC',  ABSPATH . WPINC);

And of course, 
require_once WP_PHPMAILER_INC . '/class-smtp.php';

Using this, we could package wordpress in a simpler way, without altering provided sources, just adding this vendor file.

For example, see what have be done in GLPI
https://forge.indepnet.net/projects/glpi/wiki/GlpiPackaging

If you accept this feature, I will work on it and submit the patches (probably various, one per library, as I will progress on this work).
"	remicollet
Future Releases	16462	Plugin Editor does not work for Must-Use Plugins		General	3.1	normal	normal	Awaiting Review	enhancement	new		2011-02-05T12:11:50Z	2011-02-05T12:11:50Z	"Since [10737] (WP 2.8), WordPress has support for so called [http://hakre.wordpress.com/2010/05/01/must-use-and-drop-ins-plugins/ Must-Use Plugins]. Since [13233] (WP 3.0) those are listed in the admin panel.

By default, Plugins can be edited on the ''Edit Plugins'' page ({{{/wp-admin/plugin-editor.php}}}).

On WordPress 3.0.4 it's not possible to edit Must-Use plugins.

User who can edit plugins should be enabled to edit the ''must-use''-variant of plugins as well.

Related: #11861
"	hakre
Future Releases	20148	Preview post in Webkit browser doesn't render Flash objects		General	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-03-01T10:14:49Z	2013-02-10T21:49:21Z	"When inserting a Flash <object> via HTML and use Preview function in Chrome it doesn't show.

- Tested on a clean WordPress 3.3.1 install, no plugins activated, theme: twentyeleven.
- The <object> code is available in the sourcecode. It just doesn't render... When you hit refresh it shows.
- Tried this on multiple work stations (Windows and Mac os). All versions of Chrome.
- Only in Chrome. Firefox has no issues with this function.
- There is no difference between Multisite or Single site installations.
- I'm Administrator (or Network administrator) in all cases.

Issue is also on WordPress support forums: http://wordpress.org/support/topic/preview-post-in-chrome-mac-os-doesnt-generate-flash-objects
"	thomasvanderbeek
Future Releases	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
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	22049	"Reading settings let users choose between ""Full text"" or ""Summary"" for the feeds but not for the blog page"		General	1.2	normal	normal	Awaiting Review	enhancement	new		2012-09-30T00:35:38Z	2012-10-01T11:20:57Z	"Please make the life of new Wordpress users easier.

Why not let users chose with a simple option if they want Wordpress to show the ""Full text"" or a ""Summary"" of the posts on the blog page?

== Scenario ==

'''> OPTION 1:'''

If user checks option 1 (""Full text"") the blog page would ''always'' (!) show Full text.

'''> OPTION 2:'''

If user checks option 2 (""Summary"") the blog page would show summaries based on the following priority order:

'''1)''' Teaser (generated with the ""more"" tag"")

'''2)''' Manual excerpt (if there is no ""more"" tag in the post)

'''3)''' Automatic excerpt (if there is no manual excerpt and no ""more"" tag in the post)

The way it is working now seems very confusing to me. Relation between ''manual excerpts'', ''automatic excerpts'' and ''teasers'' is everything but simple to understand for a beginner. Moreover some themes use the ""''the_content()''"" tag in their post template while others use the ""''the_excerpt()''"" tag. This makes the whole thing even more difficult to understand when switching from a theme to another.

Such a '''basic''' option is available for the feeds. It should also be available for the pages, shouldn't it?

'''Please check the attached image as my English is not perfect.
'''

Thanks

P.S. The ""[http://wordpress.org/extend/plugins/post-teaser/ Post teaser]"" plugin might be a good starting point."	Lorangeo
Future Releases	22400	Remove all, or at least most, uses of extract() within WordPress		General	3.4.2	normal	normal	Future Release	enhancement	new	early	2012-11-09T22:47:37Z	2013-03-13T15:19:56Z	"`extract()` is a terrible function that makes code harder to debug and harder to understand. We should discourage it's use and remove all of our uses of it.

Joseph Scott has [http://josephscott.org/archives/2009/02/i-dont-like-phps-extract-function/ a good write-up of why it's bad]."	Viper007Bond
Future Releases	21941	Remove get_post_format_slugs()		General		normal	minor	Awaiting Review	enhancement	new	dev-feedback	2012-09-20T14:40:52Z	2012-09-20T14:41:03Z	"I just encountered the `get_post_format_slugs()` function, which is basically just wrapping `get_post_format_strings()` and setting the strings as keys too. So its output is an assoc array where the keys equal the values.

The three times core calls it, it does it the following:


{{{
// ~/wp-includes/posts.php -> set_post_format()
if ( 'standard' == $format || !in_array( $format, array_keys( get_post_format_slugs() ) ) )

// ~/wp-includes/posts.php -> _post_format_request()
$slugs = get_post_format_slugs();
if ( isset( $slugs[ $qvs['post_format'] ] ) )
	$qvs['post_format'] = 'post-format-' . $slugs[ $qvs['post_format'] ];

// ~/wp-includes/theme.php -> add_theme_support()
switch ( $feature ) {
	case 'post-formats' :
		if ( is_array( $args[0] ) )
			$args[0] = array_intersect( $args[0], array_keys( get_post_format_slugs() ) );
		break;
}}}


So in every case it would've been enough to simply call `get_post_format_strings()`.

Do we really need this function?"	F J Kaiser
Future Releases	23367	Remove message parameters fron admin URl's in the browser address bar		General		normal	minor	Awaiting Review	enhancement	new		2013-02-02T07:31:20Z	2013-02-02T07:31:20Z	"Scenario: When a post is being published successfully ""message=6"" is appended to the URL. If I refresh the page while in that state I will get the ""post published"" message again, although nothing was done.

There is probably nothing functionally wrong with the way things work now but it can be esthetically more pleasant if that parameter was removed which in turn will eliminate the message problem.

This can be done on browsers that support the history API of HTML5. The following piece of code can be used after displaying the message or maybe it can be generalized to work in the admin footer.

{{{
<script type=""text/javascript"" charset=""utf-8"">
  url = the canonical URL for the address
  if (typeof history.replaceState === 'function') { // check html5 functionality support
    data = {dummy:true};
    history.replaceState(data,'',url);
  }
</script>
}}}
"	mark-k
Future Releases	23084	Replace the use of the $more global with a filter		General	3.5	normal	normal	Awaiting Review	enhancement	new		2012-12-30T09:35:31Z	2012-12-30T09:35:31Z	Globals are evil is a good enough reason, but this global is also very poorly documented http://codex.wordpress.org/Customizing_the_Read_More#How_to_use_Read_More_in_Pages claims that it can have negative value while it is being used as boolean in the code.	mark-k
Future Releases	22329	Retina Gravatars		General		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-10-31T05:18:14Z	2013-02-12T23:54:12Z	"Mentioned by Matt in #21019 

Should be a simple matter of changing get_avatar() in pluggable.php so that the requested size is twice the display size."	miqrogroove
Future Releases	11113	Return 410 Gone HTTP response for deleted posts/pages		General	2.9	normal	normal	Future Release	enhancement	new		2009-11-10T03:46:06Z	2011-01-20T06:24:15Z	"Deleted content should be treated differently from content that never existed. WordPress could be enhanced by returning a 410 Gone response to requests for posts or pages that have been deleted.

As I currently envision the solution, bits of old content (like a slug) would have to remain in the database after deletion.

Using WordPress 2.8.5; could not find any references to this in pre-existing Trac tickets in Core."	voyagerfan5761
Future Releases	13169	Return Dynamic Sidebars with get_dynamic_sidebar		General		normal	normal	Future Release	enhancement	new		2010-04-28T18:07:28Z	2010-04-28T18:15:02Z	"Currently there is no available function to return the contents of a dynamic sidebar. The following code enables developers to return and assign the contents of a dynamic sidebar to a variable within their code.

{{{
function get_dynamic_sidebar($index = 1) 
{
	$sidebar_contents = """";
	ob_start();
	dynamic_sidebar($index);
	$sidebar_contents = ob_get_contents();
	ob_end_clean();
	return $sidebar_contents;
}
}}}
"	w3prodigy
Future Releases	20066	SImplify the functionality of script_concat_settings() and remove the globals		General		normal	normal	Future Release	enhancement	new		2012-02-18T06:53:01Z	2012-04-18T20:47:02Z	As discussed in the comments on #20055, script_concat_settings() should be split into couple of simple functions that only check the constants and the 'can_compress_scripts' server option.	azaozz
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	23183	Single Page Application/OData API		General		normal	normal	Awaiting Review	enhancement	new		2013-01-11T18:15:34Z	2013-01-11T22:45:13Z	I am interested in helping out. Are there any plans to move to a Single Page Application model. I know this would take a lot of work as we would have to code a secure Web API into the core (I would go with standard OData service API) but as mobile devices become more critical to web success WordPress needs to find a way to minimize requests and allow for occasionally connected solutions. I know this would be for major release 4 or possibly even 5 depending on the impact to plugin developers but it make a noticeable difference on the scalability of wordpress.	cportwood
Future Releases	14366	Standardize e-mail, email text		General	3.0	normal	minor	Future Release	enhancement	new		2010-07-20T19:19:02Z	2012-12-15T12:53:35Z	"!WordPress uses ""e-mail"" and ""email"" pretty interchangeably for site text, comments, and mail messages. In some cases both forms of the electronic-mail term are used on the same error message!

This patch replaces all instances of ""email"" in !WordPress text with ""e-mail"" instead. The electronic-mail abbreviation of ""e-mail"" is the current [http://www.apstylebook.com/ AP Stylebook] recommendation. Electronic-mail translates well."	niallkennedy
Future Releases	18321	Stop minimizing CSS files and add a simple regexp in load-scripts.php to remove comments when concatenating		General		normal	normal	Future Release	enhancement	new		2011-08-03T17:31:18Z	2011-08-08T09:01:05Z	As the title, differences in gzipped .dev.css and .css files are minimal. If we remove comments on the fly in load-scripts.php (has to be very fast regexp) we wouldn't need to pre-minimize css files.	azaozz
Future Releases	16578	TinyMCE plugins are not loaded as .dev.js when SCRIPT_DEBUG is enabled		General	3.1	normal	minor	Awaiting Review	enhancement	new		2011-02-17T06:58:15Z	2011-02-17T13:31:40Z	In trunk, when SCRIPT_DEBUG is enabled, TinyMCE does not load plugins using  `.dev.js` scripts. It would be nice if it did.	solarissmoke
Future Releases	20203	To return 404 page when user request not existing category and existing at once (in URL)		General	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-03-08T14:45:04Z	2012-06-13T10:45:59Z	"I have category 'category1' with posts in it. I want to get posts from 'caegory1' and not existing category 'not_existing'.
if I use URL like 'http://mysite.com/category/category1+notexisting' I get normal archive page but this is a page without post because there are no posts in 'category1' and 'not_exists' at once.
But maybe it is better to return 404 page? Because it produces additional duplicate pages for search engines like google."	egorpromo
Future Releases	20153	Track Plugin actions/history		General		normal	minor	Awaiting Review	enhancement	new		2012-03-02T14:58:50Z	2012-03-02T14:58:50Z	"It would be great if WP could track any activity around plugins, eg. install, activate, disable, update, delete.

Seeing as plugins are most often the causes of problems with WP, it would be good to know which was the last plugin activated, or updated, particularly on sites with many plugins.

For example, I'm currently troubleshooting a problem which may be due to a plugin I recently updated, however I have no idea which one it could be, and disabling/re-enabling all plugins is not really the best solution.

A fairly simple nice-to-have that would greatly aid troubleshooting."	SecGen
Future Releases	14108	Unify registration between single site and network configurations		General	3.0	normal	normal	Future Release	enhancement	new		2010-06-26T22:14:40Z	2010-10-28T05:32:20Z	"The registration processes in 3.0 differ between single site registration and network signup. We should look at unifying the registration process. One way we could do this is

- keep the existing registration process for single sites
- in a network, users register first using the same process as single sites
- in a network, once registration is complete, direct the new user to the site creation page (which could be somewhere in the dashboard) where they could create their site

There are also several open tickets related to issues with the network signup process:

#13827
#12022
#12030
#12032

(There may be more.) We could clean up/eliminate these in process. I'd like to see this included in the discussions once we get closer to the 3.1 dev cycle.

"	wpmuguru
Future Releases	18893	Update and enhance the basic browser detection to include smart phones and tablets/pads		General		normal	normal	Future Release	enhancement	new		2011-10-09T19:26:19Z	2011-10-10T17:00:05Z	As the title. We need to keep the basic $is_this, $is_that globals for back-compat but can introduce another global that would hold all needed info about the current web browser, device, versions, etc.	azaozz
Future Releases	12267	Upgrade loop objects to provide identical presentational interfaces		General		normal	normal	Future Release	enhancement	new		2010-02-18T00:19:24Z	2012-07-19T08:47:14Z	"Usually wpdb returns rows as stdClass objects. We are used to getting properties from these objects, e.g. $post->ID or $comment->comment_ID, but this class has no methods. As used, the stdClass object is only a syntactic alternative to the array.

As long as we're already using objects, let's have some more useful classes. I propose post and comment classes that implement common interfaces, and classes that extend these for special post_types and comment_types, and filters to allow plugins to use their own classes at instantiation time.

Without actually using PHP5 interface syntax, the idea is to have identical methods to get things from objects in the loop. For example, one common method would be ```url()```. The same method would work on every kind of compatible object, be it a post, page, attachment, comment, trackback, or pingback, although the underlying logic for getting the URL may differ for each.

```<a href=""<?php print esc_attr($post->url()); ?>"">```

It would simplify templates while allowing various object types in loops, not just posts, and give us an opportunity to clean up a lot of the underlying template tag logic (e.g. global $authordata), and give plugins and themes new ways to modify output.

This stemmed from my work on search. I wanted a way to keep the template simple while adding support for different object types in the loop. I figured that it wouldn't hurt anything to upgrade the classes because the way of accessing properties would be unchanged."	andy
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	16612	WordPress should return nocache headers for requests with comment cookies		General		normal	normal	Awaiting Review	enhancement	new		2011-02-21T22:45:21Z	2011-11-16T00:51:57Z	"Most themes, when displaying the comment form, change the HTML to pre-fill username, email address, and website when comment cookies are received in the HTTP request.  Since the response does not have explicit nocache headers, per RFC2616 (http://www.ietf.org/rfc/rfc2616.txt) intermediate caches can use heuristics to determine the cache TTL for the response.  Since there is 0 freshness data in the response, it is not really possible to perform good heuristics, but in practice, caches will assign a default TTL to this type of response.  The result is that private information input by user A when submitting a comment can be returned to user B when making a request for the same URL.  

To protect ourselves against this, we should call nocache_headers() when comment cookies are sent and the comment form is being displayed.  Alternatively, we can send nocache headers for all requests with comment cookies regardless of the comment form being displayed or not (probably easier and maybe safer).

http://humboldtherald.wordpress.com/2011/01/27/gremlins/ is a story likely caused by an aggressive cache and the lack of nocache headers."	barry
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	24325	[wp-includes/load.php] LINE 270: ini_set should be verify before call		General		normal	minor	Awaiting Review	enhancement	new		2013-05-12T10:48:31Z	2013-05-17T12:54:09Z	"Block @2 should be encapsulate in @1 if.

Most of hosting disable ini_set function and this will resolve some users frustration about multiple junk line of logs or error display.

This is my first report, so I apologize if something is wrong.

@1
{{{
if (function_exists('ini_set')) {
 @2 CODE
}
}}}



@2
{{{
if ( WP_DEBUG_DISPLAY )
   ini_set( 'display_errors', 1 );
elseif ( null !== WP_DEBUG_DISPLAY )
   ini_set( 'display_errors', 0 );

if ( WP_DEBUG_LOG ) {
   ini_set( 'log_errors', 1 );
   ini_set( 'error_log', WP_CONTENT_DIR . '/debug.log' );
}
}}}
"	teo.cojo
Future Releases	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
Future Releases	22141	add_submenu_page file callback		General	3.4.2	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-10-09T16:11:11Z	2012-10-09T18:07:03Z	"Under the recommendation of the community I have decided to file a track regarding add_submenu_page. It currently allows for a callback function in which a dev could include a file but how about allowing add_submenu_page an argument to include a file in replacement of a callback function? This would remove several lines of code and clean up many developers functions.php files as well as custom admin page files.

Thanks for listening and I hope I can help.
-Ben"	BenRacicot
Future Releases	10975	comment form nonce		General		normal	normal	Future Release	enhancement	new		2009-10-19T06:49:16Z	2010-10-06T20:09:02Z	"This adds a nonce to public comment forms, via the comment_form action.
"	tellyworth
Future Releases	24597	get_{$adjacent}_post_sort filter should have post type parameter		General		normal	normal	Awaiting Review	enhancement	new		2013-06-18T17:25:30Z	2013-06-18T17:25:30Z	"In case a user doesn't want to change the sort order for every post type, the post type should be passed as an extra parameter.  The post type is already a variable is already passed in the preceding post_where filter.

{{{
$sort  = apply_filters( ""get_{$adjacent}_post_sort"", ""ORDER BY p.post_date $order LIMIT 1"" );
}}}

should be updated with:

{{{
$sort  = apply_filters( ""get_{$adjacent}_post_sort"", ""ORDER BY p.post_date $order LIMIT 1"", $post->post_type );
}}}



in wp-includes/link-template.php"	helgatheviking
Future Releases	18705	home_url() and is_home() with a static front page		General		normal	normal	Awaiting Review	enhancement	new		2011-09-19T16:16:25Z	2012-12-02T00:05:20Z	"When you have a static front page, home_url() points to the front page while is_home() detects the posts page.

This is confusing and counter intuitive (especially because in the dashboard the page set as home is referred to as the posts page. The word ""Home"" is never used on the client side).

Rename
is_home() => is_posts_page()
home_url() => front_page_url()

Add
posts_page_url()"	crrobi01
Future Releases	22531	integrate fetch_json($url)		General		normal	normal	Awaiting Review	enhancement	reopened	close	2012-11-21T19:21:54Z	2013-06-17T08:15:36Z	as we have fetch_feed() function, it will be great to have fetch_json() function too, to download a json file and decode into an array.	alexvorn2
Future Releases	24284	is_multi_author() should query by specific post type and status		General		normal	normal	Awaiting Review	enhancement	new		2013-05-08T08:18:58Z	2013-05-08T10:38:18Z	"Current is_multi_author() function only checks by the 'post' post-type and 'publish' post-status..

I think the function should be able to query by custom-post-type and custom-post-status"	alex-ye
Future Releases	16375	is_tax() and get_taxonomy_template() support for post formats		General		normal	normal	Future Release	enhancement	new	dev-feedback	2011-01-26T12:03:03Z	2011-02-03T14:38:29Z	"Two things it seemed we forgot.

Currently you'd need to use is_tax() as a conditional tag for post formats. This is ugly, as it looks like this:

`is_tax('post_format', 'post-format-aside');`

Ideally, that slug should be internal. So we need a `is_post_format()` conditional tag. That's probably a lame name (most is_* functions are ambigious), and perhaps someone has a better idea.

Additionally, get_taxonomy_template() currently looks for `taxonomy-$taxonomy-$term.php`. That turns into `taxonomy-post_format-post-format-aside.php`. A simple check can allow us to instead (or in addition to) look for `taxonomy-post_format-aside.php`."	nacin
Future Releases	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
Future Releases	20144	make posts without title or without main text more comfortable		General		normal	normal	Awaiting Review	enhancement	new		2012-02-29T17:55:15Z	2012-02-29T17:55:15Z	"make posts without title or without main text more comfortable. as i know posts without main text is even not possible. if user creates post without title, it is hard to find in dashboard post list!

this enhancement would allow to use wordpress as microblog."	qdinar
Future Releases	10296	scheduled unpublishing / post expiration		General		low	minor	Future Release	enhancement	new		2009-06-29T06:02:33Z	2010-12-21T11:40:21Z	Is there any particular blog-philosophical reason why this isn't yet possible in the core version while scheduled publishing has been a longstanding feature? As usual with such issues, client requested WP, but wants features that aren't easily supported in WP. There's a plugin called post-expirator (http://homeworker-directory.com/blog/how-to-make-your-wordpress-posts-and-wordpress-pages-auto-expire-on-a-chosen-time-or-date-with-post-expirator/) that does this in a way, but given WP's apparent increased use as a CMS I think this should be a core feature.	youngmicroserf
Future Releases	15222	show_option_all_included for wp_dropdown_categories		General	3.0.1	normal	normal	Awaiting Review	enhancement	new		2010-10-26T12:50:15Z	2010-10-26T12:51:32Z	"this little addition lets user have an option which allows searching in all categories included in dropdown only. put it below handling of show_option_all option in wp_dropdown_categories


		if($show_option_all_included)
		{
			$show_option_all = apply_filters( 'list_cats', $show_option_all_included );
			$selected = ( '0' === strval($r['selected']) ) ? "" selected='selected'"" : '';
			$vals = '';
			foreach($categories as $cat)
				$vals .= $cat->term_id.',';
			$vals = substr($vals, 0, -1);
			$output .= ""\t<option value='$vals'$selected>$show_option_all</option>\n"";
		}"	roxaz
Future Releases	14670	sunrise.php in single site installations		General		normal	normal	Future Release	enhancement	reopened	close	2010-08-22T19:17:54Z	2012-02-21T02:18:29Z	Let's make sunrise.php work regardless of is_multisite().	nacin
Future Releases	21153	supporting protocol-relative urls		General	3.3.2	normal	normal	Awaiting Review	enhancement	new		2012-07-04T10:04:09Z	2012-07-04T11:04:29Z	"changing http:// and https:// generated links to // links would easily add support for hosting a site both under http and https easily

one place I've found this to be changed is in wp-includes/link-template.php around line 2006

the first if could be changed to:

$url = str_replace( ""https://"", ""//"", $url)
$url = str_replace( ""http://"", ""//"", $url)"	nagyv
Future Releases	22069	unify function naming convention get_ vs. the_		General	3.4.2	normal	normal	Awaiting Review	enhancement	new		2012-10-01T10:24:15Z	2012-10-01T10:24:15Z	"even after about 400 custom wordpress instalation i always got problem remembering the proper name of many functions, if they are returning the content or echoing it.

Most of the functions got get_something() and the_something() but some functions got get_the_something() (e.g. get_the_post_thumbnail) and some got the_something(echo=false) or something(echo=true) etc.

It would be nice if we would consolidate the naming convention (IMO get_ and the_ would be the best) and make current functions obsolete."	thomask
Future Releases	21599	wp-admin post-screen: Make metabox visibility filterable		General	3.4.1	normal	minor	Awaiting Review	enhancement	new		2012-08-15T19:10:46Z	2012-09-25T17:57:10Z	We are using wp as a cms and we want to influence the visibility options our users see. Right now, that part is hardcoded in wp-admin/includes/meta-boxes.php. We would appreciate a filter to influence the visibility options. I'd be willing to provide a patch, if I get a positive feedback from a core dev.	pampfelimetten
Future Releases	16437	wp_category_checklist should have name parameter		General	3.0.4	normal	minor	Awaiting Review	enhancement	new	close	2011-02-01T19:48:31Z	2011-12-14T23:12:37Z	"I found [http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/template.php#L64 wp_category_checklist] is useful for creating my plugin/theme settings options. Unfortunately, it's currently don't have name parameter, the name is statically defined as '''post_category''' in the ''Walker_Category_Checklist'' default walker.

[[BR]]
''wp_category_checklist( $post_id = 0, $descendants_and_self = 0, $selected_cats = false, $popular_cats = false, $walker = null, $checked_ontop = true )''

[[BR]]
where it should be something like[[BR]]

''wp_category_checklist( $post_id = 0, $descendants_and_self = 0, $selected_cats = false, $popular_cats = false, $walker = null, $checked_ontop = true, $name='post_category' )''

So we don't need to create a new walker just to change the name.
Thank you."	takien
Future Releases	19135	wp_get_archives() needs a hook/filter		General		normal	normal	Awaiting Review	enhancement	new	dev-feedback	2011-11-03T22:12:19Z	2011-11-05T20:20:01Z	"I would expect that it would have one. It was proposed at one point: #2329

Consider the case where I want to add `rel=""nofollow""` to links in my archive:


{{{
function nofollow($string) {
    $dom = DOMDocument::loadXML($string);
    $list = $dom->getElementsByTagName('a');
    foreach($list as $a) {
        if (!$a->hasAttribute('rel')) {
            $a->setAttribute('rel', 'nofollow');
        }
    }
    return $dom->saveHTML();
}
ob_start();
wp_get_archives('type=monthly&limit=12');
echo nofollow(ob_get_clean());
}}}


That seems really ugly, especially since I already use the nofollow function in other places using `apply_filter`;

A more elegant way:
{{{
function wrap($string, $tag) {
    return ""<$tag>$string</$tag>"";
}
function nofollow($string) {
    $dom = DOMDocument::loadXML($string);
    $list = $dom->getElementsByTagName('a');
    foreach($list as $a) {
        if (!$a->hasAttribute('rel')) {
            $a->setAttribute('rel', 'nofollow');
        }
    }
    return $dom->saveHTML();
}
add_filter('wp_get_archives', 'wrap', 'ul');
add_filter('wp_get_archives', 'nofollow');
wp_get_archives('type=monthly&limit=12');
}}}"	LeviMorrison
Future Releases	18814	wp_redirect wont allow arrays to be sent in query string		General	3.2.1	normal	normal	Awaiting Review	enhancement	new		2011-09-29T14:27:38Z	2011-10-03T17:04:52Z	"
The pluggable function wp-redirect will not allow arrays to be sent in a query string.  

ie: http://www.example.com/?array[]=first&array[]=second&array[]=last

The brackets are stripped out when the URL is sanitized and it becomes:

http://www.example.com/?array=first&array=second&array=last

This removes the ability to pass the array."	jacksplay
Future Releases	14364	"""Now"" button for current date in update post published date and time"		General	3.0	normal	normal	Future Release	feature request	new		2010-07-20T15:16:00Z	2010-10-28T10:05:40Z	"It would be very convenient to have a button called ""Now"" in ""Edit post"" window in ""Published on: date @ time"" section. 

Google likes to know when old posts gets updated. So it is recommended to update post ""published on:"" date when post content is updated. When a user wants to update publishing time and date of a post, he must click ""Edit"", then manually enter year, month, day, hour and minute of current date and time and then click ""Update post"". It is quite slow and dull process but it could be automated easily with a new button.

It would be very nice to have a button called ""Now"" which should automatically fill in year, month, day, hour and minute fields with values of current date and time. 

Whenever a user updates post publishing date and time, the date and time that he/she usually enters is current date and time. The ""Now"" button would be a big time saver for users who update their posts."	dovydas
Future Releases	20194	Add Description meta to General Settings		General	3.3	normal	minor	Awaiting Review	feature request	new		2012-03-07T20:59:05Z	2012-03-17T13:50:40Z	"Add a description field to General Settings b/c these days with themes doing all kinds of kooky things, the automatic excerpt is often not representative of the site content.  All the SEO-lovers will be happy, searchers will get more accurate results, and it's a nice end-user feature without high overhead.

Could have sworn I made a ticket like this once before, but can't find it in search, so if anyone remembers it/is better at searching trac than I just was, go ahead and close this as duplicate."	jane
Future Releases	21375	Add Filter for next_posts_link/prev_posts_link label		General		normal	minor	Awaiting Review	feature request	new		2012-07-25T14:56:47Z	2012-07-26T17:06:56Z	"There is currently a filter 'next_posts_link_attributes' that allows plugins to add/modify classes/rel/etc to the links.  However, the actual label that is displayed for the link is not accessible through this.

I think that the $label variable in function get_next_posts_link should be run through a filter to allow it to be modified by plugins.

For example, a plugin that adds a custom post type of Apple might want these links to say Next Apples or Previous Apples, or if a plugin changes the ordering of posts, it might want to change 'Earlier' type labels that many themes use to better reflect the new ordering system"	MadtownLems
Future Releases	22249	Add ability to set or remove attributes on enqueued scripts and styles.		General		normal	normal	Awaiting Review	feature request	new	dev-feedback	2012-10-21T23:29:13Z	2013-03-26T22:18:25Z	"I think it should be easier to customize the loading of scripts and styles (easier to customize the markup generated by the script/style system). Proposed solutions:

'''Solution 1:''' Allow `wp_enqueue_script`, `wp_enqueue_style`, `wp_register_script`, `wp_register_style` to accept an array of attributes as the `$src` parameter. For example:

{{{
wp_enqueue_script( 'my-plugin', array(
    'src' => 'http://example.com/js/app.js'
    'defer' => ''
    'data-my-plugin' => 'custom data attr value'
), array('jquery'), null, true );
}}}

'''Solution 2:''' Add a filter before the markup is generated that allows devs to filter the attributes while they are in array format. For example:

{{{
add_filter('script_loader_attrs', function ($attrs, $handle) {
    unset ( $attrs['type'] );
    'my-plugin' === $handle and $attrs['data-my-plugin'] = 'plugin data';
    $attrs['src'] = remove_query_arg( $attrs['src'] );
    return $attrs;
}, 12, 2);
}}}
In class.wp-scripts.php it might look something like:

{{{
$attrs = (array) apply_filters('script_loader_attrs', $attrs, $handle);
}}}

and/or:

{{{
$attrs = (array) apply_filters(""{$handle}_script_loader_attrs"", $attrs );
}}}

----

I imagine that solution '''2''' would be easier to implement than '''1''', and '''2''' allows for themes/plugins to modify scripts/styles w/o re-registering resources.

The key feature of both solutions is the ability to modify the attrs while in array format. There are other ways that one could achieve the same results, but the array is '''by far the cleanest'''. Dirty alternatives include: 
* Use `preg_replace()` on the markup after it is generated (see #22245)
* Use output buffers and PHP's DOMElement interface
* Filter away the ""print_scripts_array"" and regenerate the markupmanually.)"	ryanve
Future Releases	17298	"Adding optional ""fieldname_base"" parameter to touch_time() function would allow plugin authors to reuse this code"		General		normal	trivial	Awaiting Review	feature request	new		2011-05-01T20:50:42Z	2012-02-03T15:56:52Z	"I didn't see any discussion of this over the years, and wondered if this was a feature that other people would like to see added:

In a couple projects, I've had to recreate a date entry form very similar to the one generated by the `touch_time()` function in wp-admin/includes/template.php. This function could be modified very easily to be reusable in plugins.

The simplest way of doing this, in my opinion, is to accept an optional fifth parameter for a fieldname base string.

Current output of the function:

{{{

<select id=""mm"" name=""mm"" tabindex=""4"">
// options
</select>
// etc
}}}

If this could be modified by a plugin to output something like this:

{{{

<select id=""eventstartdate_mm"" name=""eventstartdate[mm]"" tabindex=""4"">
// options
</select>
// etc
}}}

...it would be very useful. Would improve standardization of UI elements between core and plugins.

Of course, the entire template.php file is A Big Mess. Not sure if we should be messing around in there too much.

 "	goldenapples
Future Releases	10846	"Automatically add XFN and rel=""external"" to post/page/comment links"		General	2.8.4	normal	minor	Future Release	feature request	new		2009-09-24T20:07:11Z	2010-01-04T13:02:11Z	"Links created in ""Links"" in the admin should have their XFN data appended in a rel attribute. Kinda like the [http://wordpress.org/extend/plugins/auto-xfn-ify/ Auto XFN-ify] plugin.

But more importantly (and simpler), if a link goes out to a domain different from the one hosting wordpress, rel=""external"" should be added."	prometh
Future Releases	12865	Better support for beta/staging		General		normal	normal	Future Release	feature request	reopened		2010-04-06T06:40:40Z	2013-06-03T17:55:01Z	Currently it is very difficult to maintain a beta / staging version of your wordpress site. As wordpress grows in popularity and is used on websites that would like to minimize downtime a beta/staging setup in addition to a production or main setup would be ideal. If one tries to do this now, you can attempt to copy the whole database over to the beta or staging setup which will result in links on the beta/staging version going to the production/main url's. This makes it relatively unusable. Ideally there would be some solution where developers can decide for their beta/staging site to download data from their production/main server every day or at will which will allow them to keep things updated and allow for them to test with their most recent content which can be useful. If this synchronization can occur without the previous problems and other problems that occur with simply copying the entire production database that would be wonderful!	mnolin
Future Releases	17478	Disable Comments for Pages / Disable Comments for Pages Site-Wide		General	3.1.2	normal	normal	Awaiting Review	feature request	new		2011-05-17T19:04:25Z	2011-11-08T16:23:44Z	"Ladies and gentlemen, 

it's been suggested on the Forum that I start a new ticket here. I think it's a good idea. 

Here's a couple of suggestions that I believe if implemented would greatly improve WordPress functionality and popularity:

1) Make the Display Widget  for pages visible by default, the way it was before the WordPress 3.0. Many non-blog WordPress website owners, and many bloggers, want the comments for pages disabled, but have no idea how to do that, because the Discussion checkbox in the Screen Options panel for Pages  is deselected by default. As a result, most people new to WP 3 have no idea that Discussion Widget even exists, and have trouble disabling comments on pages. 

Disabling such comments is very necessary in many situations. For example, a page that includes only a contact form, shouldn't have comments. Most WordPress users do not need their portfolios, or their ""About"" pages commented – and so on. 

2) Create the checkbox that would allow to toggle all comments (old and new) comments for all pages with one click – and a separate checkbox that would allow to toggle all comments (old and new) for all posts – site-wide. 

Many WordPress based business websites have hundreds of pages, and it would save a lot of time if the owner or designer could just disable the comments by deselecting one checkbox. I do realize it can be easily done by commenting out the comments in the code, but wouldn't it be nicer to have it as a checkbox option? 

Some of the owners of such sites want to have a blog on their site, too - and want to have comments as a traditional part of blog functionality. That's what comments for pages and posts should be toggle-able site-wide independently from each other. 

For best experience, the post comments should also have a toggle checkbox. Some owners may want to disable comments for all posts site-wide, too. 

To see where this request is coming from, please Google ""disable comments for pages wordpress"" and you will see that the issue does cause quite a bit of confusion. 

Also please see this thread of the WordPress support forum about: http://wordpress.org/support/topic/disable-comments-for-page-option/

I hope this suggestion helps to improve WordPress – already the greatest open source CMS platform.

Best regards, 

Dimitri Vorontzov
 "	Dimitri Vorontzov
Future Releases	20523	Disable autoloader when using class_exists()		General	3.3.1	normal	normal	Awaiting Review	feature request	new		2012-04-23T10:08:32Z	2012-05-16T01:07:04Z	"A couple of files inside the /wp-includes/pomo directory use class_exists() the wrong way, for example in /wp-includes/pomo/entry.php :
{{{
if ( !class_exists( 'Translation_Entry') ):
}}}

It should be:
{{{
if ( !class_exists( 'Translation_Entry', false) ):
}}}

The second parameter 'false' disables autoloading. This is important because I'm integrating some WP functions into another existing website which already comes with an Autoloader for some classes = confusion.

This should be easy to fix. Thanks :)
"	michael.heuberger
Future Releases	11549	Enable loading of the WordPress environment from external php script		General		normal	minor	Future Release	feature request	new	close	2009-12-21T19:54:33Z	2009-12-28T12:26:44Z	"For some integration projects, it is useful to load the WordPress environment from an external php script. This can be done by including wp-load.php
Afterwards all the WordPress functions can be used.

This is only possible if wp-load.php is included from the global scope. If it is included from inside a function, it will fail. This limitation makes it difficult to integrate WordPress with other projects.

wp-load.php fails because of the use of global objects and assign by reference. A simple solution would be to declare $wpdb, $wp_widget_factory, $_wp_deprecated_widgets_callbacks for global in wp-settings.php
The creation of WP_Widget_Factory in wp-settings.php needs to be changed from
$wp_widget_factory =& new WP_Widget_Factory();
to
$wp_widget_factory = new WP_Widget_Factory();

The syntax for creation of WP_Widget_Factory should be conditioned by the PHP version, to maintain backwards compatibility with PHP 4.
"	mp2300
Future Releases	19628	FEATURE REQUEST: std deviation option for wp_tag_cloud		General	3.3	normal	minor	Awaiting Review	feature request	new	dev-feedback	2011-12-21T04:16:22Z	2012-01-21T10:55:36Z	"Feature Request

Add a std deviation, logarithmic, or other non-linear algorithm for generating tag cloud sizes...  I have a sample set containing approximately 500 tags, with two tags which fall in the 100 posts range, whereas most tags end up with less than 20.  I would still like the two tags to show up, and to show up the largest, and a simple std deviation (66% show up in 1 std dev, 96% or so in the 2nd, etc) or logarithmic algorigm for calculating tag element sizes, based on the sample set."	bhoogterp
Future Releases	21002	Feature request: wp_link_pages() needs support for formatting the current page		General		normal	normal	Awaiting Review	feature request	reopened		2012-06-17T19:09:51Z	2013-01-18T02:27:18Z	"To follow up my previous feature request #21001, it would be super to see a way to style/format the current page, because it could look different compared to links to other pages (for example "">> Page % <<""). An option called currentpagelink seems fitting."	archon810
Future Releases	23285	Implement an AMD JavaScript loader in WordPress		General		normal	normal	Awaiting Review	feature request	new		2013-01-24T14:28:47Z	2013-01-25T07:04:55Z	"AMD = Asynchronous Module Definition

See comment: http://core.trac.wordpress.org/ticket/22896#comment:29

I think this is a must for the future viability of WordPress and plugins written for it.

Multiple versions of JavaScript libraries are a fact of life and we have to deal with it somehow.

If WordPress provides the framework for the use of multiple versions of JavaScript libraries then a lot of the problems we see with WordPress now will be a thing of the past.

This represents a major re-think of the current WordPress JavaScript loading paradigm, but I think it is necessary and would be well worth it.

I'm not a terribly advanced developer, and there might be better solutions out there or others to come, but for now, I think this is the way to go.

Example:

http://requirejs.org/docs/why.html

http://requirejs.org/docs/whyamd.html

https://github.com/amdjs/amdjs-api/wiki/AMD

It does not have to be RequireJS, but it seems the most mature and popular of the implementations.

From the unminified jQuery source:
{{{
// Expose jQuery as an AMD module, but only for AMD loaders that
// understand the issues with loading multiple versions of jQuery
// in a page that all might call define(). The loader will indicate
// they have special allowances for multiple jQuery versions by
// specifying define.amd.jQuery = true. Register as a named module,
// since jQuery can be concatenated with other files that may use define,
// but not use a proper concatenation script that understands anonymous
// AMD modules. A named AMD is safest and most robust way to register.
// Lowercase jquery is used because AMD module names are derived from
// file names, and jQuery is normally delivered in a lowercase file name.
// Do this after creating the global so that if an AMD module wants to call
// noConflict to hide this version of jQuery, it will work.
if ( typeof define === ""function"" && define.amd && define.amd.jQuery ) {
	define( ""jquery"", [], function () { return jQuery; } );
}
}}}

Note: '''multiple versions of jQuery'''"	auniquename
Future Releases	21300	Implement autoloader compatible with PSR-0 for plugins and themes		General		normal	normal	Awaiting Review	feature request	new		2012-07-17T21:15:45Z	2012-09-11T02:20:09Z	"To provide more compatibility with other frameworks, it would be great if WordPress implemented an autoloader compatible with PSR-0. Plugins and themes could then register namespaces or prefixes with the autoloader.

I believe this could be implemented without any BC breaks.

Details of the PSR-0 standard:
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md"	dave1010
Future Releases	20492	Improve submit_button()		General	3.4	low	normal	Awaiting Review	feature request	new		2012-04-19T20:40:10Z	2012-04-19T21:39:51Z	"The `submit_button()` function takes five arguments and calling it ends up being very messy.

Example [comment:ticket:20490:3 given by Scribu]:
> It makes for very unreadable code. For example, when I see this:
> 
> {{{
> submit_button( $args['label_submit'], 'button', 'submit', false, array( 'id' => $args['id_submit'] ) )
> }}}
> 
> I have no idea what that `false` parameter is for, without looking up the defition for submit_button().
> 
> Plus, it's not that much shorter than writing the HTML by hand, which is clear as day:
> 
> {{{
> <input name=""submit"" type=""submit"" id=""<?php echo esc_attr( $args['id_submit'] ); ?>"" value=""<?php echo esc_attr( $args['label_submit'] ); ?>"" />
> }}}

Let's change this so it accepts a `$text` parameter for the button text and an `$attributes` parameter for everything else.

Patch coming up."	johnbillion
Future Releases	14373	In-editor image downsizing uses HTML resizing instead of actual resize		General		normal	normal	Future Release	feature request	new		2010-07-21T05:30:44Z	2010-10-28T10:06:47Z	"This comes as a suggestion from Google, who wants to help publishing platforms deliver content faster.

When you use the in-editor image downsizing functionality (the percentage slider), it does an HTML downsize. This can lead to bigger image requests than are necessary. An actual resize for local images would result in a more efficient load."	markjaquith
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	16509	Offer remote install-script as installer option		General		normal	normal	Awaiting Review	feature request	new		2011-02-09T22:01:35Z	2011-10-03T23:03:55Z	"I've just tried this script

http://instantinstall.org/

and I wondered if it weren't a useful addition to have an officially supported remote install script for WP. So people could download the script instead of the entire package, upload it to their servers and let them do the heavy lifting. This would be particularly useful for people who regularly set up WP for clients.

Having a wp.org supported script would be great for people who are weary of using third party code."	youngmicroserf
Future Releases	17834	Quick Edit of Hierarchal Terms		General		normal	normal	Awaiting Review	feature request	new		2011-06-18T12:47:23Z	2011-09-10T01:41:21Z	Would be nice if the Quick Edit function for hierarchal terms included the ability to change the parent. In fact, you could pretty much eliminate the Edit function altogether by doing this.	DragonFlyEye
Future Releases	21644	Should contributors be allowed to edit their posts once scheduled?		General	3.4.1	normal	normal	Awaiting Review	feature request	new		2012-08-20T21:36:55Z	2013-01-29T19:42:14Z	"
This may not be a ""bug"" per-se,but seems to have a lot of negative consequences so I'll give it a shot.

According to the rules:  A contributor can edit their own Posts - irrespective of who scheduled it.
http://codex.wordpress.org/Roles_and_Capabilities#Contributor

This creates problems for large publications where there is an editor who makes changes to posts and then schedules them, sometimes a couple days in advance.

As it stands now, a contributor can still log in after that process is done which means unexpected changes and shenanigans might take place.

Wouldn't it make more sense for a contributor to lose editing privileges as soon as something is no longer in draft modea?

Just my two cents.


"	nickaster
Future Releases	20844	Specify titles using <!-- nextpage -->		General		normal	normal	Awaiting Review	feature request	new		2012-06-05T09:49:51Z	2012-06-19T23:05:04Z	"Hi,

I'm planning to code a plugin but maybe you're going to code it into WP core, so I prefer to ask before.

The idea is to modify <!-- nextpage --> code in order to give a title to every page, also better in SEO to have an url like www.wordpress.org/2012/my-article and www.wordpress.org/2012/my-article/conclusion/ instead of www.wordpress.org/2012/my-article/2/.

Maybe is possible to modify it this way: <!-- nextpage['Conclusion'] -->

It's different from subpages because it will be usable on every post type, not even on pages, and you will create just one post, not more.

Last but not least you could have a page selector with titles not page numbers.

Thanks :)"	sgr33n
Future Releases	11229	Theme & Plugin Search Box		General		normal	normal	Future Release	feature request	new		2009-11-22T19:59:40Z	2010-01-14T00:36:07Z	"One thing I think would reduce mouse clicks is the ability to search for a new theme from the ""Manage Themes"" page. It could be a quick search, as the ""Add new themes"" page gives you better control and various parameters to search.

This is also relevant in the plugins area, you can search for existing plugins from the ""Manage Plugins"" page but you cannot do a quick search for ""NEW"" plugins. Again, useful and minimizes a mouse click."	dremeda
Future Releases	17525	There should be a datetime_format option to specify whether the date or the time comes first		General		normal	normal	Awaiting Review	feature request	new		2011-05-20T20:09:11Z	2011-05-20T20:09:11Z	"As a theme author it would be very useful to have a global option for formatting a full datetime (and a the_datetime() function too).

Sometimes datetimes are formatted ""$date $time"", sometimes it's ""$time $date"", sometimes it's even ""$date at $time"".

I think there should be an option for this in the general settings alongside the date and time format options."	holizz
Future Releases	19904	Trim Leading and Trailing White Space in a Post Title		General	3.3.1	normal	normal	Awaiting Review	feature request	new		2012-01-26T23:37:15Z	2012-01-27T00:55:01Z	"In working with clients today I realized that they were copying and pasting post titles but including a leading space in it by accident.  Because of this the orderby feature of the query wasn't appearing to work.  Turns out it was but the spaces where all correct so it was messing with the query.  

I think it would make sense that on a title field of a post/ page that any leading whitespaces and any trailing white spaces should be trimmed off.

something like 


{{{
trim($post_title);
}}}


"	greenspeakmedia
Future Releases	20531	Version No. removed from theme name in themes		General	3.4	normal	minor	Awaiting Review	feature request	new		2012-04-24T11:12:54Z	2012-04-25T09:06:55Z	"The version no. of themes is removed in 3.4 from the themes page. There was a direct display of theme version no. in 3.3 and was a great help for developers with lots of theme with different versions. But now we have to click on Details to see the version number, which is just a bit time consuming. Hope you would consider my request. 

Thanks
Sanam"	kcssm
Future Releases	13040	author.php doesn't recognize custom_post_type posts written by user		General		normal	normal	Future Release	feature request	new		2010-04-18T04:01:46Z	2010-04-24T00:22:30Z	"Working on nightly WP3.0. - custom theme, but, tested with TwentyTen as well and got same result. Not entirely sure if this is a bug or if it is intended behavior, but, the author template does not recognize posts of a custom post type. It will return a 404 if there are no ""post"" post_types and only ""custom"" post_types available to load. I thought it might be worth mentioning as well that I feel really strongly that there should be an archivalish-""post_type"" template along with the single-""post_type"" template. I have been struggling with the lack of one and have had to fall back on creating a page template that pulls in an archival type list via custom post type query, but, we all know how the paging issue is with that, and it seems like it would just plug right in to the logic of archive.php, or even index.php pulling in all ""post"" type posts by default. Why not let custom post types have their own ""index.php""? that pulls in all of it's post types by default by simply making a file called ""post_type"".php. I made that sound way easier than it probably would be, but, you get the point. Just a thought."	10sexyapples
Future Releases	10676	current-cat-ancestor in wp_list_categories		General	2.8.5	normal	normal	Future Release	feature request	new		2009-08-24T14:37:40Z	2009-11-20T06:36:49Z	The wp_list_categories should apply current-cat-ancestor like wp_list_pages not just current-cat-parent to the closest parent	spathon
Future Releases	21171	jQuery Events for Metaboxes		General		normal	minor	Awaiting Review	feature request	new		2012-07-05T21:35:47Z	2012-07-06T01:14:52Z	"Currently, when a plugin adds a metabox with complex objects (like TinyMCE, Maps, CodeMirror etc) care must be taken to refresh the objects when the elements are moved (including hidden/shown).

After some digging, I've found that this seems to works in most cases:
{{{
var context = ""#custom_meta_box_id"";
$( '#adv-settings' ).on( 'click', context + '-hide, ', refresh );
$( context ).on( 'click', '.hndle, .handlediv', refresh );
	
$('.meta-box-sortables').bind( ""sortstop"", refresh );
}}}
which isn't terrible, but seems fragile if core changes in the future, and there should just be a better way :-)

Two ideas from dev chat are triggering custom events or the (coming soon) ""js actions"" which would be more robust (like php actions)."	WraithKenny
Future Releases	20660	wp_get_attachment_url() ignores filter for unrecognized IDs		General	3.3.2	normal	minor	Awaiting Review	feature request	new		2012-05-11T16:49:29Z	2012-05-11T20:54:53Z	"wp_get_attachment_url() fails to invoke its filters when it encounters an unrecognized post ID.  It would be helpful to allow a filter to deal with the situation.

The plugin NextGEN Gallery uses image IDs like ""ngg-1"", while WP's image IDs are integers.  A filter could deal with the situation.

wp_get_attachment_url() begins like this:


{{{
$post_id = (int) $post_id;
if ( !$post =& get_post( $post_id ) )
  return false;
}}}


Obviously, a nonstandard post ID will ignore the filters.  If the filters were invoked, nonstandard IDs can be dealt with as desired by themes or plugins.

The filter should be given a ""false"" value instead of $url, and the original $post_id value (before forcing to (int)).  If existing filters are already dealing with null or empty URLs, they can handle this situation.

Suggestion:

{{{
$post_id_original = $post_id;
$post_id = (int) $post_id;
if ( !$post =& get_post( $post_id ) )
  $url = apply_filters( 'wp_get_attachment_url', false, $post_id_original );

  if ( empty( $url ) )
     return false;

  return $url;
}}}
"	RoamFree
Future Releases	21107	wp_register_resource		General		normal	normal	Awaiting Review	feature request	new		2012-06-28T20:38:31Z	2012-06-29T09:15:34Z	"

Building on the concept of wp_register_script and wp_register_style I would love to see something more general for requiring resources with dependencies.  Many times certain scripts require certain styles to be included and vice versa.  This could also extend to other resource types as well.  


Let's use a basic example of some certain script creatively called Script-1.  That Script-1 may have certain scripts and styles or other item on which it is dependent, let’s call them Script-1-A,Script-1-B and Style-1-A, Style-1-B.  When you register the script you can of course specify other dependent scripts, but not the dependent styles, or other resource.  Of course you can register the styles separately.  It may seem trivial that you can then just register Script-1-A, Script-1-B and register Style-1-A, Style-1-B and then wp_enqueue_script (Script-1,array(Script-1-A, Script-1-B)) and wp_enqueue_style(Style-1-A), wp_enqueue_style(Style-1-A)  separately.  Now let's say you have Script-2 that depends on Script-1.  When you call wp_enqueue_script(Script-2) you also have to remember to call wp_enqueue_style(Style-1-A) and wp_enqueue_style(Style-1-B).  As the levels of dependency increase or if something changes it gets a lot more difficult to maintain.  


My example above only focused on styles and scripts but could apply to other resources such as fonts and/or images that you would like to manage using the flexibility of the WordPress queueing and  actions/hooks systems. Sure you could have scripts call the styles themselves but then those styles would not be processed through wordpress and therefore might not take advantage of combining, compressing, caching systems you might have in place in addition to the ability to deregister and change certain items in child themes/skins as easily.

I have a system setup to run hundreds of sites with a core theme that provides common structure, style, scripts and a host of other functionality.  Then I have an array of child themes geared towards certain types of sites.  Those child themes each can have an unlimited number of skins.  The skins can all introduce new functionality and build on the functionalities, styles, scripts, etc of the child theme which builds upon the core theme.  This is one of the many cases where being able to just call the single wp_enqueue_resource would greatly help, especially when things change. 

Implementation: To implement for just scripts and styles to get started you could make a new “Resources” queue in which each resource could have a list of resources and type.  When you enqueue a resource it could call wp_enqueue_script and wp_enqueue_style.  Now we would have to add the ability to add a placeholder or null type of item in wp_register_script and wp_register_queue. Because looking at the example I laid out above you would do something like this:



Class Resource might either contain and array of generic resources or could have separate styles/scripts.  There are obviously flexibility and performance implications of both methods.

Here is some very rough pseudocode:

{{{
wp_register_resource(‘Resource-1’,
  array(
    ‘script’=>array(
      ‘handle’=>‘Script-1’,
      ‘src’=>‘Script-1-URL’,
      ‘deps’=>array(’Script-1-A’,’Script-1-B’),
      ‘ver’=>’’)
    ‘style=>array(
      ‘handle’=>‘Style-1’,
      ‘src’=>‘ Style-1-URL’,
      ‘deps’=> array(Style-1-A’, Style -1-B’),
      ‘ver’=>’’,
      ‘media’=>’’)
  )
)
}}}

do not call wp_register_style/ wp_register_script upon registering of the resource and wait until this resources or resource requiring this resource is enqueued.  This way the style and script are not enqueued separate from the resource and therefore each other since they are dependent on each other.  It would however register the resource in the resource queue.

{{{
wp_enqueue_resource(‘Resource-1’) would:
wp_enqueue _script(‘Resource-1’, ‘Script-1-URL’, array(’Script-1-A’,’Script-1-B’));
wp_enqueue _style(‘Resource-1’, ‘Style-1-URL’, array(Style-1-A’, Style-1-B’));
}}}

2a
//wp_register_resource($handle, $resources=array(),$deps=array())

{{{
wp_register_resource(‘Resource-2’,
  array(
    ‘script’=>array(
      ‘handle’=>‘Script-2’,
      ‘src’=>‘Script-2-URL’,
      ‘deps’=>array(’Script-2-deps’)
      ‘ver’=>’’)
    ‘style=>array(
      ‘handle’=>‘Style-1’,
      ‘src’=>’’,
      ‘deps’=>array(’’)’,
      ‘ver’=>’’,
      ‘media’=>’’)
  ),
  array(‘Resource-1’)
);
}}}

{{{
wp_enqueue_resource(‘Resource-2’) would:
wp_register_script(‘Resource-1’,’Scipt-1-URL’……)
wp_register_style(‘Resource-1’,’Style-1-URL’……)
wp_enqueue_script(‘Resource-2’, ‘Script-1-URL’, array(‘Resource-1’,’Script-1-A’,’Script-1-B’))
wp_enqueue_style(‘Resource-2’, ‘’, array(‘Resource-1’))
}}}


`wp_deenqueue_resource(‘Resource-2’)` would take dequeue it’s scripts and dependent scripts/styles (assuming those dependent scripts and styles were not enqueued elsewhere)


There are the issues to work out on whether a resource could specify multiple scripts/styles or whether it should just be zero/one of each that listed others as dependencies.  Either way can work, just depends on what community thinks."	gruvii
Future Releases	24591	WordPress Updated: Previous Quotes No Longer Display as Italic Text		Graphic Design	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-06-17T21:13:14Z	2013-06-17T21:24:04Z	"The quotes no longer display fancy Italic text like they did automatically on default before, check here, it's the first post under ""New Beta3 -Updated"":

http://gage.x10.mx/bugs/
----
Remember that since this is a new nightly build, there needs to be more stuff fixed."	Gage Morgan
Future Releases	16158	3.0.4 Upgrade failed on localhost testbed, successful on public site		HTTP	3.0.1	normal	normal	Future Release	defect (bug)	new	dev-feedback	2011-01-08T21:03:55Z	2011-01-09T14:15:17Z	"Running: 3.0.1, Ubuntu, Apache

I'm still looking at this but wanted to report it while I have a break.

I got the holiday notice to upgrade to 3.0.4.  When I did an auto-upgrade on my local testbed (http://localhost:9090/wp/wp-admin/update-core.php), WP reported that I have latest version.  Plugin upgrades work fine.  The auto upgrade was successful on my public sites.  I have WP_DEBUG, etc. on for my local testbed and no errors were reported.  I have upgraded my local testbed this way in the past, definitely for 3.0.1.

Below is a debug dump I hack in the WP_HTTP->request call coming from wp_version_check.  I pasted the URL use into the browser bar it returned the correct information.  Called from wordpress localhost, api.wordpress.com returns a HTML document with the <title>Page not found</title> and a bunch of info about wordpress.


{{{
[08-Jan-2011 20:42:48] URL='http://api.wordpress.org/core/version-check/1.5/?version=3.0.1&php=5.3.2-1ubuntu4.5&locale=en_US&mysql=5.0.83&local_package=&blogs=1&users=2&multisite_enabled=0'
[08-Jan-2011 20:42:48] r=array (
  'method' => 'GET',
  'timeout' => 3,
  'redirection' => 5,
  'httpversion' => '1.0',
  'user-agent' => 'WordPress/3.0.1; http://localhost:9090/wp/',
  'blocking' => true,
  'headers' => 
  array (
    'wp_install' => 'http://localhost:9090/wp/',
    'wp_blog' => 'http://localhost:9090/wp/',
    'Accept-Encoding' => 'deflate;q=1.0, compress;q=0.5',
  ),
  'cookies' => 
  array (
  ),
  'body' => NULL,
  'compress' => false,
  'decompress' => true,
  'sslverify' => true,
  'ssl' => false,
  'local' => false,
)
}}}


So two problems:

1) If the local site core check fails, it assumes what it is running is the most current.  There is no indication that the core check failed.  It seems like the ""Page Not Found"" page returned from api.wordpress.org should be displayed. See #16156, #16094 for similar issues.

2) What in the request is causing the HTTP get to fail?  I think it must something in the header information.  BUT, it USED to work.  Is the server behaving differently?"	dturvene
Future Releases	24201	Error in RegEx for proxy excluded URL in function send_through_proxy		HTTP	3.1	normal	normal	Awaiting Review	defect (bug)	new		2013-04-26T13:13:37Z	2013-04-26T13:51:27Z	"Dear WordPress Team,

I've detected a bug in the function send_through_proxy in the class WP_HTTP_Proxy. The coded regex for wildcarded domains only works for subdomains containing characters (a-zA-Z0-9) and . (dot) but not for subdomains containing characters (a-zA-Z0-9) and - (dash). 

File: wp-includes/class-http.php around line 1411 

Example:
{{{
define(WP_PROXY_BYPASS_HOSTS, '*.example.com');
}}}
foo.bar.example.com will not use proxy.
foo-bar.example.com will use proxy.

POSSIBLE SOLUTION: 
Change the line 1411 from 
{{{
     $wildcard_regex[] = str_replace('\*', '[\w.]+?', preg_quote($host, '/'));
}}}
to
{{{
     $wildcard_regex[] = str_replace('\*', '[\w.-]+?', preg_quote($host, '/'));
}}}

Yours,
Erich Lerch"	erich1978
Future Releases	17010	Inconsistent handling of HTTP response codes		HTTP	3.1	normal	normal	Awaiting Review	defect (bug)	new	dev-feedback	2011-04-01T00:00:13Z	2011-04-06T00:20:04Z	"I noticed during some testing to see what would happen if a server returned a 404 when streaming to a file,and found some inconsistent handling of response codes between transports.

The below test checks to see if the transport returns a WP_Error or if it returns an actual response. If the second column is an integer matching the first column then the transport returned a response, if the second column is 'wp_error' then the transport returned WP_Error for that response code.

STREAMS:
{{{
100 => 100
101 => 101
102 => 102
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => 400
401 => 401
402 => 402
403 => 403
404 => 404
405 => 405
406 => 406
407 => 407
408 => 408
409 => 409
410 => 410
411 => 411
412 => 412
413 => 413
414 => 414
415 => 415
416 => 416
417 => 417
422 => 422
423 => 423
424 => 424
426 => 426
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}

FSOCKOPEN:
{{{
100 => 100
101 => 101
102 => 102
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => wp_error
401 => wp_error
402 => wp_error
403 => wp_error
404 => wp_error
405 => wp_error
406 => wp_error
407 => wp_error
408 => wp_error
409 => wp_error
410 => wp_error
411 => wp_error
412 => wp_error
413 => wp_error
414 => wp_error
415 => wp_error
416 => wp_error
417 => wp_error
422 => wp_error
423 => wp_error
424 => wp_error
426 => wp_error
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}

EXTHTTP:
{{{
100 => wp_error
101 => wp_error
102 => wp_error
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => 400
401 => 401
402 => 402
403 => 403
404 => 404
405 => 405
406 => 406
407 => 407
408 => 408
409 => 409
410 => 410
411 => 411
412 => 412
413 => 413
414 => 414
415 => 415
416 => 416
417 => 417
422 => 422
423 => 423
424 => 424
426 => 426
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}

CURL:
{{{
100 => wp_error
101 => wp_error
102 => wp_error
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => 400
401 => 401
402 => 402
403 => 403
404 => 404
405 => 405
406 => 406
407 => 407
408 => 408
409 => 409
410 => 410
411 => 411
412 => 412
413 => 413
414 => 414
415 => 415
416 => 416
417 => 417
422 => 422
423 => 423
424 => 424
426 => 426
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}

We need to define when we want to return a WP_Error, if ever.  I am thinking that returning a WP_Error is not very useful if we get a response from the server.  The response codes tested were obtained from get_status_header_desc()."	sivel
Future Releases	21182	WP_HTTP_Cookie doesn't handle the default conditions for the 'domain' and 'path' field correctly.		HTTP		low	minor	Awaiting Review	defect (bug)	new		2012-07-07T04:34:45Z	2012-07-07T04:34:45Z	"WP_HTTP_Cookie currently handles ""simple"" cookies in exactly the same way they're received, that is, it only fills in the details that the set-cookie header contained.

However, some fields are optional, and as a result of this, the [http://www.ietf.org/rfc/rfc2109.txt rfc for state management] specifies a set of default values for certain fields:
{{{
4.3.1  Interpreting Set-Cookie

   The user agent keeps separate track of state information that arrives
   via Set-Cookie response headers from each origin server (as
   distinguished by name or IP address and port).  The user agent
   applies these defaults for optional attributes that are missing:

   VersionDefaults to ""old cookie"" behavior as originally specified by
          Netscape.  See the HISTORICAL section.

   Domain Defaults to the request-host.  (Note that there is no dot at
          the beginning of request-host.)

   Max-AgeThe default behavior is to discard the cookie when the user
          agent exits.

   Path   Defaults to the path of the request URL that generated the
          Set-Cookie response, up to, but not including, the
          right-most /.

   Secure If absent, the user agent may send the cookie over an
          insecure channel.
}}}

We currently don't do anything special for Secure cookies (From what I can see), but we also need to handle the 'domain' and 'path' field defaults better, as currently they remain at the default null if nothing is passed. This can result in domains passing the WP_HTTP_Cookie::test() method to a different domain or path than they were issued on.

Example cookie values (and WP_HTTP_Cookie representations) which can trigger this:
{{{
PHPSESSID=ros1liponkqip23k9le0hhmp31; path=/' (length=44)
test=1341632838; expires=Sat, 07-Jul-2012 04:47:18 GMT
array (size=2)
  0 => 
    object(WP_Http_Cookie)[87]
      public 'name' => string 'PHPSESSID' (length=9)
      public 'value' => string 'ros1liponkqip23k9le0hhmp31' (length=26)
      public 'expires' => null
      public 'path' => string '/' (length=1)
      public 'domain' => null
  1 => 
    object(WP_Http_Cookie)[86]
      public 'name' => string 'test' (length=4)
      public 'value' => string '1341632838' (length=10)
      public 'expires' => int 1341636438
      public 'path' => null
      public 'domain' => null
}}}

This is not a issue for WordPress core, but could affect plugins who do anything special with Cookies."	dd32
Future Releases	24182	WP_Http_Fsockopen fails when requesting an IP based URL with an explicit Host header		HTTP	trunk	normal	normal	Awaiting Review	defect (bug)	new		2013-04-24T22:39:29Z	2013-04-24T22:52:18Z	"When requesting a resource with a IP based URL and an explicitly set Host header fsockopen fails.

wp_remote_post():
{{{
$url = http://72.233.69.89/1.1/verify-key
$args = Array
(
    [body] => key=xxxxxxxxxxxx&blog=http%3A%2F%2Ffriedcell.si%2Foutbreak
    [headers] => Array
        (
            [Content-Type] => application/x-www-form-urlencoded; charset=UTF-8
            [Host] => rest.akismet.com
            [User-Agent] => WordPress/3.5.1 | Akismet/2.5.7
        )

    [httpversion] => 1.0
    [timeout] => 15
)
}}}
WP_Http_Fsockopen $strHeaders just before [http://core.trac.wordpress.org/browser/trunk/wp-includes/class-http.php#L729 fwrite]:
{{{
POST /1.1/verify-key HTTP/1.0
Host: 72.233.69.89
User-agent: WordPress/3.5.1 | Akismet/2.5.7
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Host: rest.akismet.com
Accept-Encoding: deflate;q=1.0, compress;q=0.5
Content-Length: 58

key=xxxxxxxxxxxx&blog=http%3A%2F%2Ffriedcell.si%2Foutbreak
}}}
The request fails as the first Host header is used.

When $arrURL!['host'] is an IP and there is a Host header in $r!['headers'], the Host header should not be added from the URL (http://core.trac.wordpress.org/browser/trunk/wp-includes/class-http.php#L706) so that the explicitly specified Host header is used."	friedcell
Future Releases	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
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	21446	plugins using curl with IPV6 enabled servers		HTTP	3.4.1	normal	normal	Awaiting Review	enhancement	new	close	2012-08-01T21:46:28Z	2012-08-09T10:41:24Z	"
plugins using curl give problems on servers having both IPV4 and IPV6 network interfaces running. Basically the performance is poor because curl is timing out on the IPv6 address..  The workaround is:

add line:
curl_setopt( $handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4);
in ../wp-includes/class-http.php

Why not have this set as default?
"	mippie32
Future Releases	19737	"""What's New"" screen confusing for minor updates"		Help/About	3.3	normal	normal	Awaiting Review	defect (bug)	new		2012-01-04T17:49:14Z	2013-01-22T01:34:46Z	"As [http://www.wptavern.com/wordpress-3-3-1-fixes-security-exploit reported on WPTavern], when you ugprade to 3.3.1, the ""What's New"" screen makes it seem like all the new features were introduced in 3.3.1 and not 3.3.

We should add a header below the short summary to the effect of ""New features introduced in 3.3""."	scribu
Future Releases	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
Future Releases	24567	Add help to media modals		Help/About	3.5	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2013-06-12T08:06:29Z	2013-06-12T16:52:29Z	They are far from simple screens but there is no help available for them.	mark-k
Future Releases	22305	Credits Page Should Include more than 'just' people who commit a patch		Help/About		normal	normal	Awaiting Review	enhancement	new		2012-10-29T16:28:32Z	2013-02-01T02:09:12Z	"If you want to find how contributes to core, it's easy, but everyone else is unlisted.

Right now, unless the person who commits a patch remembers to 'props', the person who submits a ticket, or leads to a great discussion that drives the code to a solution in the comments, are never mentioned. This drives a wedge between coders and non-coders, as some people can help but they just may not be super coders.

Proposals:

1) When pulling a list of 'everyone who helped' for the credits page, also pull a list of all IDs who commented in the tickets that were commited and list as 'Also Contributed...'

2) In 'Recent Rockstars' (which is a manually culled list anyway), pull in the active awesome people in support, documentation, codex, manuals, training, and WordCamps (for example). Include people in UI who contribute screenshots/design/wireframes that drive changes.


People who contributed to this ticket:

* ryanimel
* saracannon
* brandondove
* theandystratton
* tomwillmot
* SiobhanP (aka raggedrobins)
* ryan duff
* Lisa Sabin-Wilson
* js_zao
* vegageek
* andrea_r
* ipstenu

If I got your logins wrong, sorry."	Ipstenu
Future Releases	21583	Improve discoverability and visual design of Screen Options and Help Panels		Help/About		normal	normal	Future Release	enhancement	new	early	2012-08-14T22:34:05Z	2012-11-03T05:36:33Z	"The Screen Options and Help panels are not very discoverable and, in part because of this, aren't very helpful to our users.

Here are the problems with them right now:

* Most users are blind to these tabs.
* The labels and positioning give little indication as to what these tabs actually do.
* For a lot of users, Help is not that helpful.
*They’re position in the admin creates yet another point of navigation for users to be aware of (and per #1, most of them aren’t).
* The very wide container for text makes a lot of the help text difficult to read.

Here are some proposals to improve the design and discoverability of these tabs (related images and mockups are here: http://make.wordpress.org/ui/2012/08/06/we-did-some-brainstorming-at-dev-day-today/) :
* Adding icons to these tabs would (hopefully) both make these tabs more visible and give a better indication as to what these tabs too.
* Moving these to the right side of the toolbar would give even more context to what these do, as they would be grouped with other user-specific settings.
* (6) The toolbar dropdown would allow for a slimmer content area for better readability.
* (7) The slimmer content area would let us make screen options read like a list for better scannability.
* (4/5) Putting the gear on the upper right would standardise with several other web apps (Twitter, etc).

Related: #21326"	chexee
Future Releases	20842	Buttons are not on the same line when saving a post as pending (RTL)		I18N	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-06-04T23:58:11Z	2012-09-08T22:55:52Z	Please check attachment.	rasheed
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	19980	Localized oEmbed providers		I18N		normal	normal	Future Release	defect (bug)	new		2012-02-06T23:27:32Z	2012-05-02T19:26:03Z	"Follow-up from #19601.

Some localizations might want to add their own oEmbed provider, perhaps a service widely used by users in their country or those who speak their language, despite us never hearing of it.

Right now, Bulgarian and Chinese add some, and Russian would consider it. [http://core.trac.wordpress.org/ticket/19601#comment:11 ref] Others, if shown the opportunity, will also likely want to add some.

We need to come up with a decent solution for handling these. Perhaps it is a switch() on get_locale() in WP_oEmbed."	nacin
Future Releases	22172	Localized strings not applied in notification email		I18N	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-10-12T12:02:28Z	2012-10-12T16:51:59Z	"After user registration and activation (multisite), administrator receive email (function wpmu_signup_user_notification() in wp-includes/ms-functions.php). But content of this email is not translated even if localization file contains translated strings.

{{{
New User: %1s\n
Remote IP: %2s\n
\n
Disable these notifications: %3s
}}}

Email subject is localized, but content not. I am not sure about the cause of this problem..."	pavelevap
Future Releases	21139	Month format in Publish box		I18N	3.4	normal	normal	Awaiting Review	defect (bug)	new		2012-07-02T18:47:26Z	2012-07-02T20:03:24Z	"New translatable month format was introduced in r19820.

Problems:

1) Month numbers are not localized. Czech does not use numbers with format 01, 02, etc. I can remove month numbers by ""not translating"" them, but it is not the best solution.

2) How should be strings ""May_May_abbreviation"" translated in the right way? I found that some languages uses for example ""Kvě_Květen_abbreviation"" translation and others only ""Kvě"". Translators are probably afraid of removing ""_May_abbreviation"" part because they do not want to broke anything even if there is preg_replace function following. I do not understand why there has to be the whole ""May_May_abbreviation"" original string? Also explanation for translators (three-letter abbreviation of the month) is not exact, because we can use 2 (better for Czech) or any other number of characters."	pavelevap
Future Releases	20882	Remove strings related to Akismet from WP localization files		I18N	2.0	normal	normal	Awaiting Review	defect (bug)	new		2012-06-07T20:10:36Z	2012-06-26T03:14:15Z	"There were several tickets (#19832, #19597) related to this issue, but we had to miss it somehow for 3.4.

Main purpose of this ticket is removing all strings related to Akismet from localization files. All strings (about 110) are loaded (mainly on frontend) even if Akismet is not active. Akismet can have its own localization file."	pavelevap
Future Releases	20881	Show code references in inherited localization files		I18N		normal	normal	WordPress.org	defect (bug)	new		2012-06-07T20:01:31Z	2012-06-07T20:10:16Z	"For example string ""Invalid post type"" is used several times - on frontend and also in admin. But this string is only in frontend localization file, because this file is also loaded on admin side. That is correct, no need to duplicate strings in different files. But translators do not see code references related to admin file and it can leads to context problems during translation.

It could be very helpfull to modify makepot.php to add related code references to generated .pot files.

Related example: #20809"	pavelevap
Future Releases	19950	Support the Uyghur translation		I18N		lowest	normal	Future Release	defect (bug)	new		2012-02-02T23:23:02Z	2012-06-15T04:17:25Z	"The Uyghur translation (ug_CN) bends over backwards to be compatible with WordPress. Because there is so much going on here, I need to pull it out into its own ticket.

Given the complexities here (I will post a diff shortly), and because they compose about 1/10th of one percent of non-English downloads, I don't see this happening for 3.4."	nacin
Future Releases	20883	Translating all plugin headers?		I18N	2.6	normal	normal	Awaiting Review	defect (bug)	new		2012-06-07T20:20:34Z	2012-11-07T13:40:32Z	"I am really not sure if translators should be able to localize Author, Author URI or Plugin name? Description is very helpfull, but why translating strings like ""Matt Mullenweg"" or ""http://ma.tt/"" which are in current admin localization file?

Related: #19597"	pavelevap
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	21616	add-textdomain doesn't conform to WP coding standards		I18N		normal	normal	WordPress.org	defect (bug)	reopened		2012-08-17T03:07:19Z	2012-08-17T21:37:50Z	I used add-textdomain.php from http://i18n.svn.wordpress.org/tools/trunk on my plugin code, but it does not include a space before the closing parenthesis of the gettext function call it alters, which violates http://codex.wordpress.org/WordPress_Coding_Standards#Space_Usage	groovecoder
Future Releases	23056	date_i18n() does not localize dateformat 'r'		I18N	1.5	normal	normal	Awaiting Review	defect (bug)	new		2012-12-26T02:47:11Z	2012-12-26T04:32:58Z	"The weekday and month strings in a date being formatted with the 'r' format character are not being localized.

I've looked at the [http://core.trac.wordpress.org/browser/trunk/wp-includes/functions.php trunk code] and it looks like the 'r' case is not being considered at all in the [http://codex.wordpress.org/Function_Reference/date_i18n date_i18n()] function.


This bug is very easy to reproduce:
{{{
print ( date_i18n( 'r', 972144067 ) );
}}}

Expected output for language Dutch:[[BR]]
''za, 21 okt 2000 16:01:07 +0200''

Received output:[[BR]]
''Sat, 21 Oct 2000 16:01:07 +0000''



== Potential patch: ==

A bit of a hacky patch would go along the lines of:

{{{
if( !function_exists( 'patch_date_i18n' ) ) :
add_filter( 'date_i18n', 'patch_date_i18n', 10, 4 );
function patch_date_i18n( $formatted_date, $req_format, $timestamp, $gmt ) {

	if( $req_format !== 'r' )
		return $formatted_date;

	global $wp_locale;
	$datefunc = $gmt? 'gmdate' : 'date';

	$find = array (
		$datefunc( 'M', $timestamp ),
		$datefunc( 'D', $timestamp ),
	);
	$replace = array(
		$wp_locale->get_month_abbrev( $wp_locale->get_month( $datefunc( 'm', $timestamp ) ) ),
		$wp_locale->get_weekday_abbrev( $wp_locale->get_weekday( $datefunc( 'w', $timestamp ) ) ),
	);
	return str_replace( $find, $replace, $formatted_date );
}
endif;
}}}

Hope this helps. Would be great if this could be fixed.

Smile,
Juliette
"	jrf
Future Releases	21444	update msgid-bugs-address for plugins in makepot.php		I18N		normal	normal	WordPress.org	defect (bug)	new		2012-08-01T20:09:09Z	2012-08-01T20:16:12Z	"The msgid-bugs-address for plugins in makepot.php is outdated.  References ""/tag/"" instead of ""/support/plugin/""."	convissor
Future Releases	22557	"""Trash"" should be a name"		I18N	3.4.2	normal	normal	Awaiting Review	enhancement	new	close	2012-11-23T15:56:48Z	2012-12-19T04:39:57Z	"Hi there,

Not sure if this happens to other languages than pt_BR, but the string ''trash'' sometimes works bad when not as a name.

I would like to suggest to keep the word as a name and avoinding to flex it such ''Trash it, transhing'' etc, there is no need to singular and plural for it, I find silly ""Trashes"" in content tables since there is a counter next to the label.

That's all!"	Dianakc
Future Releases	19760	Allow localization of language names in multisite		I18N	3.3.1	normal	normal	Awaiting Review	enhancement	new		2012-01-06T13:17:13Z	2012-11-22T03:45:37Z	"There is Site Language settings in multisite (General Options). But all available languages are in English, so there is English, Czech, etc. But when I switch to Czech language, there is still only Czech and not ""Čeština"". I am not sure if there is need to translate all languages, but there should be localized at least selected language (or all available languages).

It is caused by function format_code_lang() in ms.php (line 463) where are all language names hardcoded in English."	pavelevap
Future Releases	23721	Better control of textdomains.		I18N		normal	normal	Awaiting Review	enhancement	new		2013-03-08T07:23:45Z	2013-03-08T13:19:37Z	"At the current state , loading a text domain is done by the plugin/theme author , and leaves no control to the user / other devs to intervene with this process. we are left to the mercy and good will of the original author .

It would be a good thing to create some HOOK or ACTION that will allow a user to override this somehow.

At the very least (and maybe it should be a different ticket) a function that will return all available $domain names and paths should be made available (currently no way of retrieving that but parsing the $i18n global)

Example : If a user need a  plugin/ theme that does not have a translation for my desired language , or a BAD translation (or no translation at all) the user then creates it´s OWN translation, and by dropping it inside wp-content/languages folder , that translation will be loaded instead of the one supplied (or not supplied ) with the original plugin / theme .

Current state : If a user loads a translation to the original plugin folder for translations, it will be deleted upon first update .

"	krembo99
Future Releases	20739	Improve Excerpt generation for non-english locales		I18N	3.4	normal	normal	Future Release	enhancement	new		2012-05-23T21:09:45Z	2012-05-30T13:58:18Z	"This is a follow on from #16079 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 known issues see the comments on the previous ticket."	westi
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	20491	Introduce some JavaScript i18n functions		I18N		normal	normal	Awaiting Review	enhancement	new		2012-04-19T18:50:24Z	2012-04-19T21:55:22Z	"There's JavaScript code dotted around core that handles i18n in JavaScript (for example, localised thousands separators in the pending comment count). We should bring this together into a wpL10n JavaScript library that can be reused by plugins.

I've done some work on this and I'll get a patch up in the next day or so."	johnbillion
Future Releases	19716	Marking buttons and names in text		I18N	3.3	normal	normal	Awaiting Review	enhancement	new		2012-01-03T13:37:18Z	2012-07-11T13:43:51Z	"There is no united way to mention buttons, tabs, names etc in texts. 

Sometimes there are quotes around button name:

{{{
If you would like to see more themes to choose from, click on the &#8220;Install Themes&#8221; tab
}}}

Sometimes not:

{{{
You must click the Save Changes button at the bottom
}}}

Maybe there should be any rules? For users it could be better to see button names someway highlighted (quotes, strong, etc) and everytime it would be clear that it is mentioned button..."	pavelevap
Future Releases	22225	WordPress does not localize ordinal suffixes in dates		I18N	3.4.2	normal	normal	Awaiting Review	enhancement	new	dev-feedback	2012-10-19T08:39:08Z	2012-12-26T01:48:11Z	"In wp-includes/functions.php function date_i18n(), elements like month, month abbreviation, weekday etc.. are localized but not the ordinal suffixes (e.g. st, nd, rt, th)

effect: when using the ordinal suffixes for dates 

e.g. 
{{{
<?php the_time('F jS, Y'); ?>
}}}
 
on translated/localized page page, the month name is translated (F) but the ordinal suffix no.

Not browser/OS/environment dependent."	mihaimihai
Future Releases	23794	load_plugin_textdomain fails if plugin is loaded from mu-plugins		I18N	3.5.1	normal	minor	Future Release	enhancement	reopened		2013-03-16T09:48:38Z	2013-05-23T10:20:00Z	"load_plugin_textdomain is realative to WP_PLUGIN_DIR, so it fails to load localization files if plugin keeps them in its directory. 

The function should check if is called from mu-plugins and use WP_MUPLUGIN_DIR in that case.

I can fix this in my own plugin by adding '../mu-lugins/' like this:

{{{

  load_plugin_textdomain( 'tiny_tribuna', false, '../mu-plugins/'.dirname( plugin_basename( __FILE__ ) ) . '/languages/');
}}}
 

but this is not a good option for other plugins.
"	ideag
Future Releases	17181	IIS 7.5 Wordpress MU ms-files.php not streaming mp3 files correctly		IIS	3.1	normal	normal	Awaiting Review	defect (bug)	new		2011-04-19T18:29:49Z	2011-07-25T15:13:15Z	"I think there is an issue with IIS and compression. 

I have two MP3s, one is around 7MB and the other around 2MB. I can ""download to folder"" for both and that works fine, but if I play in the browser the 7MB version cut off after 30seconds (I tried this on multiple MP3s larger than 5MB). I thought this had something to do with the ""Transfer-Encoding	chunked"" header. Upon further investigation I found that to disable this, I just had to specify the Content-length, which is explicitly disabled for IIS in ms-files.php (line 42). I commented out that line and now everything is working fine. I'm sure there was a reason for it, but I am not sure what for."	jacobm21
Future Releases	18988	"On install, IIS web.config missing setting for ""index.php"" as default page type"		IIS	3.2.1	normal	normal	Awaiting Review	defect (bug)	new		2011-10-18T17:50:05Z	2011-11-15T08:51:42Z	"If WordPress is installed in the root directory (e.g., www.example.com) on a server not pre-configured for PHP, ""index.php"" will not be a default page name on the server.  This leads to 404 errors when requesting the homepage (e.g., www.example.com).

A simple fix is to update the web.config for the WordPress install to add this:

<?xml version=""1.0"" encoding=""UTF-8""?>
<configuration>
    <system.webServer>
        <defaultDocument>
            <files>
                <add value=""index.php"" />
            </files>
        </defaultDocument>
        <rewrite>
            <rules>
                <rule name=""Main Rule"" stopProcessing=""true"">
                    <match url="".*"" />
                    <conditions logicalGrouping=""MatchAll"">
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsFile"" negate=""true"" />
                        <add input=""{REQUEST_FILENAME}"" matchType=""IsDirectory"" negate=""true"" />
                    </conditions>
                    <action type=""Rewrite"" url=""index.php/{R:0}"" />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>


"	scdetailer
Future Releases	12322	Blog import fails to generate reduced-size images		Import		normal	normal	WordPress.org	defect (bug)	new	close	2010-02-21T17:14:59Z	2012-02-14T16:25:41Z	"I just imported from http://daveabrahams.wordpress.com (go ahead, try it yourself if you like) and chose to ""Import Attachments.""  The only images from the original site that show up in the result are those that were originally displayed with size-full.  The others need to be regenerated by inserting them freshly. "	daveabrahams
Future Releases	21163	Blogger Importer Invalid Tokens		Import		normal	normal	WordPress.org	defect (bug)	new		2012-07-05T11:53:00Z	2012-10-13T19:30:04Z	"When the users clicks on the authorise button google responds with an invalid token error. This is obviously a bit puzzling for the users.

See http://wordpress.org/support/topic/plugin-blogger-importer-invalid-token

The problem seems to be that the form with the authorise button is actually passing blank tokens.

I can't reproduce the problem but I've reproduced their symptoms by switching the URL in get_oauth_link to a non existant one. This returns blank tokens to the form. If you then submit that form you get the invalid token error.

Although this following patch is not actually a fix, we can report the error properly with a change to get_oauth_link and greet and hence it will be easier to diagnose issues.

{{{
       // Shows the welcome screen and the magic auth link.
        function greet()
        {
            $next_url = get_option('siteurl') . '/wp-admin/index.php?import=blogger&amp;noheader=true';
            $auth_url = $this->get_oauth_link();
            $title = __('Import Blogger', 'blogger-importer');
            $welcome = __('Howdy! This importer allows you to import posts and comments from your Blogger account into your WordPress site.', 'blogger-importer');
            $prereqs = __('To use this importer, you must have a Google account and an upgraded (New, was Beta) blog hosted on blogspot.com or a custom domain (not FTP).', 'blogger-importer');
            $stepone = __('The first thing you need to do is tell Blogger to let WordPress access your account. You will be sent back here after providing authorization.', 'blogger-importer');
            $auth = esc_attr__('Authorize', 'blogger-importer');
            $errormsg = __('Error occurred getting OAuth tokens from Google', 'blogger-importer')

            echo ""
		<div class='wrap'>
		"" . screen_icon() . ""
		<h2>$title</h2>
		<p>$welcome</p><p>$prereqs</p><p>$stepone</p>"";
        
            if (!is_wp_error($auth_url)) {
		    echo ""<form action='{$auth_url['url']}' method='get'>
				<p class='submit' style='text-align:left;'>
					<input type='submit' class='button' value='$auth' />
					<input type='hidden' name='oauth_token' value='{$auth_url['oauth_token']}' />
					<input type='hidden' name='oauth_callback' value='{$auth_url['oauth_callback']}' />
				</p>
			</form>
		</div>\n"";
            }
            else {
                    echo $errormsg;
                    echo '<pre>
                    '.$auth_url->get_error_message().'
                    </pre>' ;
            }
        }

        function get_oauth_link()
        {
            // Establish an Blogger_OAuth consumer
            $base_url = get_option('siteurl') . '/wp-admin';
            $request_token_endpoint = 'https://www.google.com/accounts/OAuthGetRequestToken';
            $authorize_endpoint = 'https://www.google.com/accounts/OAuthAuthorizeToken';

            $test_consumer = new Blogger_OAuthConsumer('anonymous', 'anonymous', null); // anonymous is a google thing to allow non-registered apps to work

            //prepare to get request token
            $sig_method = new Blogger_OAuthSignatureMethod_HMAC_SHA1();
            $parsed = parse_url($request_token_endpoint);
            $params = array('callback' => $base_url, 'scope' => 'http://www.blogger.com/feeds/', 'xoauth_displayname' => 'WordPress');

            $req_req = Blogger_OAuthRequest::from_consumer_and_token($test_consumer, null, ""GET"", $request_token_endpoint, $params);
            $req_req->sign_request($sig_method, $test_consumer, null);

            // go get the request tokens from Google
            $req_response = wp_remote_get($req_req->to_url(), array('sslverify' => false));
            if (is_wp_error($req_response))
            {
                return $req_response;
            }
            $req_token = wp_remote_retrieve_body($req_response);

            // parse the tokens
            parse_str($req_token, $tokens);

            $oauth_token = $tokens['oauth_token'];
            $oauth_token_secret = $tokens['oauth_token_secret'];

            $callback_url = ""$base_url/index.php?import=blogger&noheader=true&token=$oauth_token&token_secret=$oauth_token_secret"";

            return array('url' => $authorize_endpoint, 'oauth_token' => $oauth_token, 'oauth_callback' => $callback_url);
        }
}}}

p.s. Sorry I've still not mastered DIFF!"	Workshopshed
Future Releases	8578	Blogger import incorrectly reports saved user information		Import		normal	normal	WordPress.org	defect (bug)	new		2008-12-11T16:53:52Z	2011-09-16T03:52:31Z	"I installed a fresh copy of WordPress 2.7 and was importing content from a Blogger site.  Before beginning to import, the page claimed that Blogger account information was saved in the database and that I could restart the process.  Even after pressing the ""Clear account information"" button, the message still appeared."	covert215
Future Releases	6369	Blogger importer inefficient handling of data		Import		normal	normal	WordPress.org	defect (bug)	new		2008-03-24T03:58:47Z	2013-04-08T17:04:48Z	If the import dataset is large, the Blogger importer can store huge amounts of data in the blogger_importer option.  It then updates this data over and over throughout the import. If MySQL logging (binary or query) is enabled, this can result in a large amount of data being written to disk, potentially filling up the partition rather quickly.  On WordPress.com, I have seen an import write 100MB of binary logs every 2 min.  Andy's suggestion is that we split up the data from the import rather than store it in one option.  This would allow us to manipulate it more granularly and prevent the huge updates from happening.	barry
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	23482	Fix improper use of comment_exists() in some importers		Import		normal	normal	WordPress.org	defect (bug)	new		2013-02-15T18:49:18Z	2013-02-15T18:49:18Z	"Background: #20494

DotClear Importer and TextPattern Importer treat the returned comment post ID as a comment ID: [[BR]]
http://plugins.trac.wordpress.org/browser/dotclear-importer/trunk/dotclear-importer.php#L416 [[BR]]
http://plugins.trac.wordpress.org/browser/textpattern-importer/trunk/textpattern-importer.php#L429"	SergeyBiryukov
Future Releases	16445	Fix incompatibilities with IDs greater than 2^31		Import	3.1	normal	normal	Future Release	defect (bug)	new		2011-02-03T01:03:24Z	2012-12-10T12:57:11Z	"For various reasons, things go bad when you get a post ID greater than 2^31^. When we're importing content and there's an existing ID, I suggest we ignore it if possible if it's too big.

Tumblr2WordPress for example maintains the Tumblr IDs and causes problems in WordPress."	Viper007Bond
Future Releases	16420	Flawed Blogger import, no details		Import	3.1	normal	normal	WordPress.org	defect (bug)	new		2011-01-31T05:44:08Z	2012-10-13T19:08:52Z	Did a Blogger import, showed as finished when it had imported 625/626 posts and 685/685comments. Did not give any indication as to why one post was not imported, which one it was, anything. Gah. Need to put in a feedback mechanism for this type of situation. 	jane
Future Releases	21859	Import blog and media library is not working		Import	3.4.2	normal	normal	Awaiting Review	defect (bug)	new		2012-09-10T08:02:25Z	2012-09-28T15:42:33Z	"Hi,
I have problems (due to hosting php timeout) to import all my blog at once.
I tried doing it by months, but it's also not working. Blog posts are imported, but nothing of the media library is imported.

I can describe too what happens when trying to import everything at once. I've just 200 photos and every 90 secs the connection is reseted trying to import them. If you try to retry using browser, photos begin to duplicate, or triplicate, or more...
After all this, then you finish, there is no attachments related to their post.

I've tried importing by months, which would not spend more than 60 secs importing photos, but then the photos are not imported.

Please, fix the import/export by months or by splitting files every 10 post (or configurable).
I would suggest too to allow any mechanism to import photos first, doing it in groups of 20 (or by configuration) and later, after that, importing post and attaching files to each post.


I set it as critical as moving a blog it's impossible without a huge amount of work. 

I could try to help debugging if needed.

Version 3.4.1 is also affected.
Thanks and regards"	don_ousian
Future Releases	24221	Importer doesn't import properly		Import	3.5	normal	normal	WordPress.org	defect (bug)	new		2013-04-29T12:03:24Z	2013-04-29T12:13:19Z	"This is what [Tools > Export] generated:
{{{
	<item>
		<title>Example</title>
		<link>http://example.com/?page_id=4477</link>
		<pubDate>Sun, 03 Feb 2013 12:10:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		<guid isPermaLink=""false"">http://example.com/?page_id=4477</guid>
		<description></description>
		<content:encoded><![CDATA[something at the beginning

<div class=""container"" style=""padding: 3em 0 0 0; margin: 0 0 3em 0; background-color: rgba(195, 195, 195, 0.15);"">
	<h2>Heading</h2>
	<p>Paragraph</p>
</div>

something in the end]]></content:encoded>
		<excerpt:encoded><![CDATA[]]></excerpt:encoded>
		<wp:post_id>4477</wp:post_id>
		<wp:post_date>2013-02-03 12:10:10</wp:post_date>
		<wp:post_date_gmt>2013-02-03 12:10:10</wp:post_date_gmt>
		<wp:comment_status>closed</wp:comment_status>
		<wp:ping_status>closed</wp:ping_status>
		[...]
	</item>
}}}

And now, when I try to import that (exactly in unmodified form) it strips 

{{{
style=""padding: 3em 0 0 0; margin: 0 0 3em 0; background-color: rgba(195, 195, 195, 0.15);""
}}} 

part in some places but not all (I guess this is important)!

And it doesn't strip it when I go to [Pages > Example] and switch to ""Visual"" editor or update the page. It is imported this way (already wrong).

I'm absolutely sure that this happens, tested several times and I can't find an error or explanation.

Export file: UNIX, UTF-8 w/o BOM.

Importer Version: 0.6
Plugin URL: http://wordpress.org/extend/plugins/wordpress-importer/

I've seen a couple of issues related to ""update_post_meta"" that is stripping quotation marks etc. Maybe this is related.

Installation: WPMU (unfiltered_html is probably disabled because it's non-super-admin blog)."	Looimaster
Future Releases	9678	Importing of plain RSS looses descriptions with xml:lang		Import	2.7.1	normal	normal	WordPress.org	defect (bug)	new	reporter-feedback	2009-04-29T08:24:49Z	2012-09-09T22:19:29Z	"When importing from a generic RSS feed the import function looses <description> if there is an xml:lang attribute. The imported posts will be empty.

xml:lang is a valid attribute for description to denote the language used in the article."	dr_touch
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	5842	LJ import gets time zone wrong		Import		normal	normal	WordPress.org	defect (bug)	new	close	2008-02-13T18:17:09Z	2011-09-16T03:55:09Z	LJ's export format has all dates in GMT, but the wordpress LJ importer treats them as local time.  	novalis_dt
Future Releases	16183	MT Importer doesn't honor default article comment settings		Import	3.0.4	normal	normal	WordPress.org	defect (bug)	new		2011-01-10T23:00:38Z	2011-01-11T23:22:45Z	"I have a blog on a network that has '''Allow people to post comments on new articles''' and '''Allow link notifications from other blogs (pingbacks and trackbacks.)''' unchecked in '''wp-admin/options-discussion.php'''. The intent is to disable comments and trackbacks, and I can confirm this is happening for new posts when I do '''Post''' > '''Add New'''.

However, the MT Importer doesn't honor this configuration. All imported MT posts have comments enabled."	novasource
Future Releases	16147	MT Importer truncates double vertical spaces, munging paragraphs together		Import	3.2.1	normal	major	WordPress.org	defect (bug)	reopened		2011-01-07T22:25:47Z	2011-08-24T06:20:05Z	"Movable Type 3.x-era exports don't use '''<p>''' tags. Like TinyMCE (and WordPress), a '''<p>''' in final rendered code is represented by two '''\n'''s in a row.

The importer strips out double '''\n'''s and replaces with a single '''\n'''. This causes paragraphs to lose their distinction upon import.

It does this because the '''$line''' variable was created by '''$line = $this->fgets($handle)''' (line 339). Then '''$line = trim($line)''' (line 340) strips out several characters, including '''\n'''.

Lines 455 and 456 add back the '''\n''' ''except'' on blank lines:
{{{
   if( !empty($line) )
   $line .= ""\n"";
}}}

So if a '''$line''' was nothing but a '''\n''', it's stripped by the '''trim''' function and becomes a 0 character line. Then the '''if( !empty($line) )''' declines to add back a '''\n'''.

Somehow this needs to be altered so that successive '''\n'''s aren't stripped. Otherwise paragraphs get vertically munged together."	novasource
Future Releases	18602	Media Library imported, but all items Unattached		Import	3.2.1	normal	normal	WordPress.org	defect (bug)	new	reporter-feedback	2011-09-06T10:10:18Z	2013-06-14T17:25:54Z	"Export XML file from one site, import into another site. By checking ""Download and import file attachments"", files from wp-content/uploads are downloaded correctly to the new site, and added to Media Library. However all items in the Media Library are now ""Unattached"", and for example posts using [gallery] are broken on the new site. "	awallin
Future Releases	9820	Multiple newlines stripped from within MT import files		Import	2.7.1	normal	normal	WordPress.org	defect (bug)	new		2009-05-14T11:03:43Z	2012-05-24T22:33:01Z	"When I imported entries from my old MT blog into a new Wordpress install, I expected my multiple newlines to be preserved.  This is because MT uses them to form paragraphs; the Markdown or Text Control plugins can do the same in Wordpress, but either way, if you strip them out, you get a huge bundle of text which is difficult to read.

The problem appears to be in the wp-admin/import/mt.php file, which ignores blank lines regardless of context.  If a newline were added in the event of a blank line when the context was body, comment, extended or excerpt, the newlines would be preserved.  The attached patch fixes this."	IndigoJo
Future Releases	10259	Problem with dotclear import		Import	2.8	normal	normal	WordPress.org	defect (bug)	new	reporter-feedback	2009-06-24T09:34:07Z	2011-09-16T03:55:46Z	"To the point translation:

Dotclear categories are imported but not assigned to the posts. 

----

Bonjour,
>
>>
>
>> Ayant souhaité le passage de mon blog dotclear en wordpress, j’ai 
>> donc
>
>> utilisé votre module d’import dans l’interface d’administration.
>
>> J’ai rencontré le problème suivant :
>
>> -          les catégories des mes billets étaient bien importées
>
>> mais n’étaient pas liées à ces derniers.
>
>>
>
>> J’ai donc contacté votre staff par l’intermédiaire de votre site mais
>
>> sans succès.
>
>>
>
>> J’ai du coup développé un petit fichier php pour résoudre mon
>
>> problème.
>> Les versions utilisées pour mon développement :
>
>> -          WORDPRESS 2.8
>
>> -          DOTCLEAR 1.2.7.1

"	latour.alain@…
Future Releases	23465	WXR importer does not import posts if a post with the same title is in the trash		Import		normal	normal	Awaiting Review	defect (bug)	new		2013-02-13T07:11:29Z	2013-04-22T03:12:42Z	"1. export a WXR file with some/all posts
2. send posts to trash
3. import the file generated at step 1.
4. for each post there is a message that the post already exist

If something is in the trash it should be handled as if it doesn't exist.

"	mark-k
Future Releases	23464	WXR importer: Creating new user to import to sucks, should be fixed or removed		Import		normal	normal	Awaiting Review	defect (bug)	new		2013-02-13T07:05:33Z	2013-02-13T07:05:33Z	"When importing WXR you are prompted to assign a user to which of the existing users the imported content will be assigned, but it is also possible to provide a name of a new user which will be created and the content then will be associated with it. 

The new user functionality sucks
1. No email or password is required therefor the user for a while is missing data which is assumed to always exist for a user. In the end of the import there is a small notice about updating the user data, but it gets lost in all the output being generated during import

2. Processing does not stop if user creation had failed (I used hebrew characters for user name) and the imported content is assigned to the current user. WTF?

"	mark-k
Future Releases	22082	WordPress Import Tool looses the complete category hierachical structure		Import	3.4.2	normal	normal	WordPress.org	defect (bug)	new		2012-10-03T01:53:05Z	2012-10-05T13:49:54Z	"I have exported from my local laptop wordpress installation the posts I had. They have the following structure with categories:


{{{
language  --> main category, parent
- source language   --> for example AF
-- target language  --> for example AFAR for Africans to Arabics
--- lessons
----- lesson 1      --> up to 100 lessons entries 
-- next target language
}}}

and so on

this complete structure is lost after import - they are all changed to parent categories no single child category.
I will attach the export file."	christian_gnoth
Future Releases	16404	WordPress Importer fails to import images		Import	3.0.4	normal	normal	WordPress.org	defect (bug)	new	reporter-feedback	2011-01-29T00:42:28Z	2012-09-10T10:13:44Z	"WordPress Importer fails to import images and update image src urls when download and import file attachments is checked.

WordPress MS with images in a post via Media using WP image mapping, e.g. image url: http://site.domainname.com/files/2011/01/myimage.jpg
Fails to download, import and update image src url. All image src urls remain intact from the old domain name.

If you change the image source to specific directory rather than the WP uploads directory: e.g. image url:
http://site.domainname.com/images/myimage.jpg
Images are downloaded and imported to media but it fails to update image src url in posts. All image src urls in posts remain intact from the old domain name.

I tested this on clean install of WP 3.0.4 MultiSite with TwentyTen theme and no other plugins activated."	wlpdrpat
Future Releases	12286	bug and fix when importing from Movable Type		Import		normal	normal	WordPress.org	defect (bug)	new		2010-02-19T13:26:59Z	2010-10-30T18:44:11Z	"I'm running WP Mu 2.9.1.1 and had a problem importing a Movable Type blog to WP and found a fix (sort of).

Symptom: When importing a blog from Movable Type to a blog in WP, you are asked to assign (or map) WP authors to MT authors. But, it turns out that the first author on the list is assigned to all posts. The other authors selected are neglected. Therefore, all of the posts end up belonging to one author.

Fix: I found the problem in wp-admin/import/mt.php. Specifically, ""$mtnames"" is not properly populated with authors from MT. So, I changed the code in function get_authors_from_post() as follows:

function get_authors_from_post() {
$formnames = array ();
$selectnames = array ();
$this->mtnames = $this->get_mt_authors();

I just added the last line shown above and then finally the import properly assings authors as intended.
(There might be a better place to put the last line, however.)
"	leyburn888
Future Releases	10260	problem img links after import dotclear		Import	2.8	normal	normal	WordPress.org	defect (bug)	new	reporter-feedback	2009-06-24T09:48:17Z	2012-09-10T09:43:28Z	"J'ai développé un fichier PHP pour changer le chemin des images car dans un billet, le chemin était celui du blog dotclear après l'import dans wordpress

---

Translation:

I wrote a php file that changes the image links in posts after a dotclear import. The posts were imported with references to their dotclear location."	latour.alain@…
Future Releases	4611	Dotclear importer for WP 2.3: flatimport		Import	2.3	low	minor	WordPress.org	enhancement	new		2007-07-11T13:37:57Z	2011-08-04T10:30:33Z	"This importer import '''posts''' (''users,