__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter Next Release 16567 Can't create categories with different names but similar slugs on Edit Post screen Administration 3.0.5 normal normal 3.6 defect (bug) new needs-unit-tests 2011-02-15T18:29:10Z 2013-01-09T23:38:54Z "We run a blog that deals with programming languages. Today we were creating a post concerning the C programming language and attempted to create a new category for it, called ""C"" (just one character). This angered WordPress; it appeared to create a superfluous ""Uncategorized"" category, but it wound up not actually creating any categories for the post. I've attached a screenie so you can see what this looks like after I attempt to create the category. If it's for some reason forbidden to create categories comprised of a single character, maybe a validation error message of some kind would be in order?" jeffreymcmanus Next Release 7392 Don't create new autosave revision if nothing has changed yet westi Autosave 2.6 normal minor 3.6 defect (bug) reopened has-patch 2008-07-23T22:03:39Z 2013-05-09T15:22:06Z "I noticed that simply loading and saving a post creates a new revision. This seems rather dumb to me. Could we not load the post up, compare it with the revision, and not create a whole new revision if nothing changed (ignoring post save time, of course)? Discuss." Otto42 Next Release 14773 Error in slug parsing leads to unlimited URLs for the same article = duplicate content Canonical normal normal 3.6 defect (bug) assigned has-patch 2010-09-03T14:20:45Z 2013-04-11T03:30:30Z "an example says more than 1000 words: right url: http://ahmongwoman.wordpress.com/2010/09/02/i-am-not-hmong-and-i-dont-speak-spanish/ wrong urls: http://ahmongwoman.wordpress.com/2010/09/02/i-am-not------hmong-and-i-dont-speak-spanish/ http://ahmongwoman.wordpress.com/2010/09/02/i----am-not-hmong-and-i-dont-speak-spanish/ http://ahmongwoman.wordpress.com/2010/09/02/i-am-not-----hmong-and-i-------dont-speak---------spanish/ Problem: Wordpress returns the article with HTTP status code 200 for the wrong URLs. This is a serious issue for people regarding search engine optimization (duplicate content). Expected results: Wordpress returns HTTP Status code 301 with Location-Header and right URL to the client." thermoman Next Release 14856 Add an $args parameter to comment_text filter Comments normal normal 3.6 enhancement new has-patch 2010-09-12T12:20:06Z 2013-05-04T23:25:53Z "When using the {{{comment_text}}} filter, there are times when the context provided by {{{$args}}} would be extremely useful. For example to know the depth of the commen. I propose adding an additional parameter for {{{comment_text}}} to add the {{{$args}}}. I've incorporated the proposed {{{$comment_ID}}} parameter from #14261, which looks to add a {{{$comment_id}}} parameter to the same filter, in the hope that this is helpful... let me know if not and I'll refactor. I've included a small plugin to demo the use and prove the new parameters are working, and the diff for a small tweak to Twenty Ten v1.1 which is needed to use this plugin with that theme." simonwheatley Next Release 14601 wp_new_comment method doesn't allow passed in values for IP and user-agent Comments 3.0.1 normal normal 3.6 enhancement new has-patch 2010-08-12T14:20:21Z 2013-05-04T12:03:02Z "In a scenario where you have a client that receives comments from the internet and pre-processes those comments before feeding them into wordpress through xmlrpc the ip and user-agent of the commenting internet user gets lost because there is no way of passing those values into the wp_new_comment function. `$_SERVER['REMOTE_ADDR']` and `$_SERVER['HTTP_USER_AGENT']` are hard-coded, which in the above mentioned scenario will always have the IP and user-agent from the client that feeds the comments into wp through xmlrpc. The attached patch will used passed in values and only fall back to `$_SERVER['REMOTE_ADDR']` and `$_SERVER['HTTP_USER_AGENT']` if not passed in." mrutz Next Release 17767 Anonymous comments can break comments RSS feed westi* Feeds 3.2 normal normal 3.6 defect (bug) accepted has-patch 2011-06-11T11:30:34Z 2013-01-13T23:54:50Z "dc:creator and description elements should not be parsed. Author field that can break RSS: {{{ Аз се казвам Веселин Николов, това е едно много дълго име }}} Comment text that can break RSS: {{{ &ndash; }}} (and most of the $allowedentitynames)" dzver Next Release 17375 Serialzed option values broken for classes and strings on unserialize for C and S markjaquith General 3.1 normal normal 3.6 defect (bug) reviewing has-patch 2011-05-11T11:42:09Z 2013-01-14T01:06:27Z "Wordpress has a feature build in to store arrays and objects into option values. This is done by transparently serializing on storing and unserialize on retrieving. The implementation is broken. Wordpress is unable to unserialize serialized option values if they contain a serialized representation of classes implementing the [http://www.php.net/manual/en/class.serializable.php PHP serializeable interface] (C instead of O). This is because the is_serialized() does not recorgnize that type of value." hakre Next Release 17262 wp_get_attachment_thumb_file is always false Media 3.0 normal normal 3.6 defect (bug) new has-patch 2011-04-27T18:36:19Z 2013-05-05T03:33:40Z The issue is that on line 3863 we always search for `$imagedata['thumb']` and it never exists. Instead we have `$imagedata['thumbnail']`. This always exists. lonnylot Next Release 13822 Menu items that get unpublished still appear nacin Menus 3.0 normal normal 3.6 defect (bug) reopened has-patch 2010-06-10T16:30:12Z 2013-03-21T14:53:47Z "We need to properly account for menu items linked to unpublished/pending post type objects. My thought is they should probably be hidden from the frontend with an indication on the backend (like ""(Pending)"") that they are are unpublished/pending. We need to properly handle private posts too." nacin Next Release 14975 Nav-menu system does not always run titles through 'the_title' filter. Menus normal normal 3.6 enhancement new commit 2010-09-27T15:19:48Z 2013-05-04T23:41:26Z I am using the qTranslate plugin that uses the 'the_title' filter to parse its multilingual content (separated with comment tags). All titles are parsed well except for the titles appearing in the menu system's meta boxes; It seems this is because nav-menu functions don't run the titles through this filter. Goldfrapper Next Release 15907 inconsistent handling of plugin_folder in get_plugins() Plugins normal normal 3.6 defect (bug) new has-patch 2010-12-20T03:35:16Z 2013-05-05T00:25:18Z "If you pass the name of a folder to get_plugins, it needs to have a leading slash which then stores the plugin list from that folder in {{{$wp_plugins['/folder-name']}}}. Secondly, the plugin file/path does not include folder-name passed to get_plugins, so the returned data has to have the {{{'folder-name/'}}} added to the key of each plugin's information before it can be used throughout WP. The code I'm currently using to work around the issue is {{{ $my_plugins = get_plugins( '/extra' ); $extra = array(); if( !empty( $my_plugins ) ) { foreach( $my_plugins as $k => $v ) $extra['extra/' . $k] = $v; } }}} related #15906" wpmuguru Next Release 16843 wp_unique_post_slug() doesn't check pagination base when CPT has archive Post Types 3.1 normal minor 3.6 defect (bug) new has-patch 2011-03-13T06:22:22Z 2013-01-14T00:12:14Z Title says it all. scribu Next Release 16834 UI problem in Permalinks SubPanel (on RTL sites) ramiy RTL 3.1 normal normal 3.6 enhancement reopened has-patch 2011-03-11T15:15:12Z 2013-05-18T07:11:57Z "hi, i want to report a UI problem in RTL sites, on the Settings->Permalinks SubPanel. See the Attached screenshots." ramiy Next Release 14578 Default User Role isn't checked against defined roles, causing unexpected resets to Administrator garyc40 Role/Capability 3.0.1 normal major 3.6 defect (bug) assigned has-patch 2010-08-10T10:00:29Z 2013-01-13T23:00:20Z "Take these steps: 1. Activate a plugin that creates role on activation. For example, it calls ""add_role( 'photo_uploader', 'Photo Uploader', array( 'read') );""[[BR]] 2. In General Settings, set the Default User Role to this new role, 'Photo Uploader'.[[BR]] 3. Deactivate the plugin, removing the roles: ""remove_role( 'photo_uploader');""[[BR]] 4. In General Settings, the Default User Role now displays 'Administrator'. (In the database, it still says 'photo_uploader'.)[[BR]] 5. When creating a new user (as admin), the role dropdown-box now displays 'Administrator' as role for this new user. This new user _will_ have role 'Administrator' if an unsuspecting admin does not explicitly alter the role in the dropdown-box.[[BR]] This way, an unsuspecting adminstrator might accidentally create new admins for his blog. I have also tested this for new users registering themselves. Fortunately, they are assigned the role 'None', not 'Administrator'. Greetings, Ivo van der Linden[[BR]] (employee of LaQuSo @ Eindhoven University of Technology)" Ivolution Next Release 15264 Deleting a term shared across taxonomies deletes all associated nav menus. garyc40 Taxonomy 3.0.1 normal major 3.6 defect (bug) assigned has-patch 2010-10-31T08:01:32Z 2013-01-12T05:44:21Z "Using other taxonomies since WP 2.3 in [http://wordpress.org/extend/plugins/xili-dictionary/ plugin xili-dictionary] , I just discover that now (since WP. 3.0) when deleting a term of his taxonomy, ''a menu item can disappear''. '''In which conditions ?''' When the term (i.e. news) is shared by taxonomy category and the plugin taxonomy named dictionary ? After deep tests (thanks to the night when time changes from summer to winter time), I can also reproduce it in current conditions : when a term is shared between taxonomies category and post_tag : If you delete the tag (i.e my test), if a category 'my test' exists and was active inside a navigation menu : the nav menu item disappear (unpleasant). The cause of this unexpected erasing, was the action hook ''delete_term'' at end of '''wp_delete_term''' function and precisely the default filter ''_wp_delete_tax_menu_item''. The add_action in default-filter.php (line 233) don't pass the 3 parameters and the function (menu-nav.php line 700) don't verify if it is possible to delete the menu item (as well done for term in other taxonomies in wp_delete_term itself) by testing the params and the taxonomy of the menu item content. Today workaround in plugins using new taxonomies : remove filter before deleting a term on concerned taxonomies and add it after. Hope that explanations were explicit. Best regards " michelwppi Next Release 16705 "Unclear wording: ""An administrator must always approve the comment """ Text Changes 3.1 normal normal 3.6 defect (bug) new commit 2011-02-28T21:22:12Z 2013-05-05T01:04:18Z "I'm not certain if I should classify this as a bug or as a need to revise wording in the options menu, or if I should put in a feature request for a refined option... ...but... If, under Settings->Discussion you have ""An administrator must always approve the comment"" checked, if the author of the post receiving the comment has the ""edit_comment"" capability, they will receive an email notification to moderate the comment in the queue. After viewing the wp_notify_moderator function for 3.1 in pluggable.php (and comparing it to 3.0.5's version) I can see this functionality seems to be coded in by design. What's confusing is that the option reads ""An administrator must always approve the comment"" and it's difficult to discern if that means the user role of ""Administrator"" or anyone who can be an ""administrator"" of the comments. It's also hard to tell from the reading of the option text whether or not this means that the function is implemented incorrectly, or if the option is simply poorly worded. In either case, it would be useful to be able to have more granular control over who is getting these email notifications for comment moderation. Failing that, if the ""An administrator must always approve the comment"" is checked, that should mean that only users with the ""Administrator"" role should be able to approve the comment. ...depending on what the expected behavior of this functionality is meant to be." joe.woidpress Next Release 13239 Filter locate_template template_names variable Themes 3.0 normal normal 3.6 enhancement reopened has-patch 2010-05-03T21:43:05Z 2013-05-04T11:09:25Z "I recently encountered a situation where it would be very helpful to supply alternate template file locations; however, this cannot be accomplished as the locate_template function is being used and that function's arguments are not filterable. So, I created a patch that adds the filter. This patch adds two filters: locate_template and locate_template-TEMPLATENAME. This allows for both general and specific filtering. The following example shows how this could be used to modify the location of a BuddyPress template file. {{{ function filter_member_header_template( $template ) { return dirname( __FILE__ ) . '/buddypress/members/single/member-header.php'; } add_filter( 'locate_template-members/single/member-header.php', 'filter_member_header_template' ); }}} While the value of this example is debatable as BuddyPress could be updated to support alternate template locations, the value of the patch itself is high. This opens up a new ability for plugins to modify template file locations, giving plugins a hook into the content rendering process without requiring themes to be modified." chrisbliss18 Next Release 20101 Can't use 'show_admin_bar' filter with conditional tags nacin Toolbar normal normal 3.6 defect (bug) reopened commit 2012-02-22T19:10:11Z 2013-04-22T22:10:49Z "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 Next Release 16057 download_url() error checking fails to notice that the file wasnt correctly witten to disk Upgrade/Install 3.0 normal normal 3.6 defect (bug) new has-patch 2011-01-01T01:36:51Z 2013-01-21T23:45:37Z "When upgrading/installing plugins, themes and WordPress download_url() is called to download the package to a temporary file. At present, the return value of fwrite() is not checked, the result can be that the file is not written to disk correctly and subsequently, the Zip extraction fails. This appears as if it can be caused by the user running out of disk space, as seen here: http://erisds.co.uk/wordpress/wordpress-automatic-upgrades-one-of-the-pitfalls I'm attaching a patch which appears to fix it for me, however, As I do not have a setup where I can enforce a quota I cannot test the saving of the file without fudging the return value of fwrite() to something lower than expected." dd32 Future Releases 14565 After Category Quick Edit Update Parent Category Dropdown Administration 3.0.1 normal trivial Future Release defect (bug) new has-patch 2010-08-08T22:07:45Z 2010-12-26T23:09:36Z "On a clean install I went to Posts -> Categories and used Quick Edit to rename 'Uncategorized' to 'Rename-Test' I then went to create a new Category using the form on the left and the Parent drop down still lists 'Uncategorized'. Should this be updated without have to reload the page?" Dempsey Future Releases 10422 Answering to comment from Dashboard does not update Dashboard statistics Administration 2.8.1 normal normal Future Release defect (bug) new has-patch 2009-07-16T05:18:48Z 2012-09-17T19:50:52Z "Hi there, there is a short statistics ""Right now/At a Glance"" box in Dashboard, containing number of posts, pages, comments etc. There is also a box with list of most recent comments in the Dashboard. If a user answers to a comment in this ""Recent comments"" box in Dashboard, which uses AJAX, so it does not reload the whole page, it creates a new comment, but the number of comments in the ""Right now"" box is not updated. I know this is not a critical bug, but it would be really nice if it works. Take care, Honza P.S.: As there is no ""Dashboard"" component in the Trac, I did not know whether to assign it to Administration or Comments component. I put it into Administration, if you think it better suits to Comments or any other component, please feel free to change it." honza.skypala Future Releases 19206 Improve internal admin menu code Administration 3.3 normal normal Future Release defect (bug) new has-patch 2011-11-08T17:53:44Z 2011-11-09T16:27:02Z "The internal admin menu code is both hard to read and filled with several unnecessary branches. This makes maintaining the code quite difficult. A few uses of list and smarter branching can considerably improve _wp_menu_output. Patch attached. Let's revisit this when we branch for 3.4." koopersmith Future Releases 14949 Login gives false assurance of having logged out filosofo Administration 3.1 normal normal Future Release defect (bug) new has-patch 2010-09-23T10:39:34Z 2012-09-20T22:02:19Z "If you visit `wp-login.php?loggedout=true` while logged in, WordPress falsely tells you that ""You are now logged out."" This is a problem because it could lead you to think, e.g., that a public computer is no longer authenticated with access to your WP admin. Patch redirects a still-authenticated user back to the admin from the login page if she requests the above page without actually having logged out." filosofo Future Releases 13655 Login/Install/User Edit should stripslashes() $_POST data Administration 3.0 normal normal Future Release defect (bug) new has-patch 2010-05-31T11:33:17Z 2010-11-13T08:05:36Z "Following on from #13654 All Login/Registration/Install/User Edit functionality should stripslash $_POST data. At present, it seems that we do not stripslash at all. For existing user passwords, we should migrate passwords to their non-stripslashed versions: [5/31/10 6:34:11 AM] Mark Jaquith: We could migrate people.[[BR]] [5/31/10 6:34:13 AM] Dion (dd32): Perhaps oughta just add proper stripslashing in 3.1, and add back-compat to change password from non-stripslashed to stripslashed.. similar to the md5->phpass implementation..[[BR]] [5/31/10 6:35:13 AM] Mark Jaquith: Yep. If the PW doesn't match, addslashes() and compare again. If that matches, set the new PW hash. Right?[[BR]] [5/31/10 6:35:19 AM] Dion (dd32): yep " dd32 Future Releases 24149 Set RTL body class for iframes Administration normal minor Future Release defect (bug) new commit 2013-04-21T03:57:06Z 2013-04-22T06:36:02Z "iframe_header() sets the current locale string in the body class, but not the RTL flag. Please add this. This came up in MP6 development, where MP6 does not (at this moment) rely on a separate rtl stylesheet like in the current admin CSS, but instead relies more on the body having .rtl set." mitchoyoshitaka Future Releases 9296 Settings API & Permalink Settings Page Bug jfarthing84 Administration 2.7.1 normal major Future Release defect (bug) reopened has-patch 2009-03-07T05:33:55Z 2013-04-22T20:58:19Z Although there is a hook in the options-permalink.php to insert custom settings, it does not actually save any custom setting which is added to that page. Instead of posting to options.php like all the other options pages, it posts to itself and only handles the form data which is built into the wordpress core. It should be implemented on that page to also store custom settings that may be hooked onto that page. jfarthing84 Future Releases 19247 Add post type and taxonomy to admin body class Administration 3.3 normal normal Awaiting Review enhancement new has-patch 2011-11-15T08:19:35Z 2013-04-14T10:03:13Z I often have a need for targetted CSS selectors based on the current screen's post type (eg. to hide unwanted UI elements), so I usually end up adding `post-type-{$post_type}` with the `admin_body_class` filter. It'd be nice if this was in core. johnbillion Future Releases 8420 Disable error redirects when in DOING_AJAX kapeels* Administration 2.7 low minor Future Release enhancement accepted has-patch 2008-11-29T00:28:10Z 2010-11-28T11:30:25Z If a DB/install error occurs in admin during ajax requests (like autosave), the response shouldn't return the whole redirected page, see $ATT (admin-ajax-install-trigger.png). If something goes awry and we're DOING_AJAX, an error message that could fit inline would be better. janbrasna Future Releases 15865 Make it easy to disable options / user settings westi Administration normal normal Future Release enhancement new has-patch 2010-12-17T17:52:29Z 2013-01-21T04:12:48Z "We have a wonderful option white listing system. The one thing it doesn't support is hiding the ui of core options if you don't want them changed. We should have a generic way of doing this." westi Future Releases 8592 Private Pages not listed in the Parent dropdown nacin Administration 2.7 normal major Future Release enhancement reopened commit 2008-12-12T16:22:24Z 2013-02-28T12:51:59Z "Private pages are not available as a choice in the Parent dropdown of the Attributes module. You should be able to create a hierarchy of private pages if you want to. Tested with r10194." mtdewvirus Future Releases 6286 "Proposed changes to ""E-mail me whenever"" Discussion Options" Administration 2.5 normal normal Future Release enhancement new has-patch 2008-03-18T19:14:55Z 2013-01-13T20:40:03Z "WRT the ""E-mail me whenever"" options on the Discussion options page: [[Image(http://img132.imageshack.us/img132/4215/picture1vf1.png)]] 1. For ""a comment is helf for moderation,"" the ""me"" is ambiguous. It should specify that it means the blog admin e-mail address. 1. For ""anyone posts a comment,"" again, ""me"" is ambiguous. In this case ""me"" means the author of the post. The comment notification setting is personal, and therefore should be set in the profile options (where it can retain the ""me""). Some authors may want e-mail notification, others might not." markjaquith Future Releases 17906 Refactor submit box code Administration normal normal Future Release enhancement new has-patch 2011-06-27T13:27:34Z 2011-06-28T16:01:10Z "The code for the post submit metabox is a mess. It should be cleaned up, so that changes such as #17028 can be done more easily. Will post a patch shortly." scribu Future Releases 16774 Remember list view/excerpt view setting Administration 3.1 normal normal Awaiting Review enhancement new has-patch 2011-03-06T13:37:18Z 2012-07-03T19:43:23Z I love the new excerpt view, except that the next time I go to the Articles page, it shows me the list view again. The selected view should be retained as a setting. texttheater Future Releases 17884 Remove redundant checks in settings API functions Administration normal minor Awaiting Review enhancement new has-patch 2011-06-24T20:20:44Z 2013-01-03T19:25:30Z "There are several isset() checks in some settings fields functions that are meant to prevent notices, but they're simply unnecessary. PHP doesn't emit notices in those cases." scribu Future Releases 18788 Remove redundant type attributes from script and style tags Administration 3.3 normal normal Future Release enhancement new has-patch 2011-09-27T06:54:02Z 2013-04-15T10:28:35Z "Now that the admin is using the HTML5 doctype everywhere, the `type=""text/javascript""` and `type=""text/css""` attributes on script and style tags are unnecessary (if they weren't anyway), and I think they can be safely removed to trim a few hundred bytes from core. Should be a simple search and replace exercise." solarissmoke 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 18710 post_deleted_messages filter nacin* Administration normal normal Future Release enhancement accepted has-patch 2011-09-19T21:19:21Z 2012-06-11T13:05:21Z It would be nice to be able to updated post deleted messages like you can through the post_updated_messages filter. jgadbois Future Releases 15384 wp-login.php refactor Administration normal normal Future Release enhancement new 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 18179 WP_Meta_Box Administration normal normal Future Release feature request new has-patch 2011-07-20T01:05:50Z 2013-03-08T16:31:47Z "Ryan, Nacin, and I would like to see a Meta Box class in 3.3. Let's make it happen. Attached is a first pass (in plugin form, for ease). It provides a basic API and supports multiple instances. Instances are stored in a static meta box registry, which should require minimal interaction. Keep in mind that meta boxes are not just registered on CPT pages — they are also used on the dashboard, in menus, and in custom UIs. The parent class should be suitable for each of these cases. I think we should move caps to the main Meta Box class (and allow subclasses/instances to specify/override the cap through $args), and also provide $args to enable/disable any checks we perform before saving (e.g. autosave, etc). It would also be interesting to integrate this with the proposed metadata API improvements. See #15066 for prior discussion." koopersmith Future Releases 20729 Improve Admin Colors CSS enqueuing Appearance 3.1 normal normal Future Release defect (bug) new 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 20733 Theme customizer doesn't order sections based on order added Appearance 3.4 normal normal Future Release defect (bug) new 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 21785 Add header image uploads with cropping to the customizer Appearance 3.4 normal normal Future Release task (blessed) new 2012-09-04T04:56:41Z 2013-04-26T01:08:30Z 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 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 16993 wp-mail.php doesn't account for half-hour and quarter-hour timezones. Blog by Email 3.1 normal trivial Future Release defect (bug) new has-patch 2011-03-29T06:55:06Z 2012-11-07T22:14:58Z "To reproduce the problem, install Wordpress and set it to post by email. Send a post from an email address which is configured to use a half-hour or quarter-hour timezone (like Afghanistan, +0430). wp-mail.php calculates the timezone by multiplying the timezone offset by 36. This works fine for whole-hour timezones (Pacific Time -0800, -800 * 36 = -28800 seconds). For half-hour and quarter-hour time zones this does not work (Afghanistan +0430, 430 * 36 = 15480, should be 16200). The reason this happens is because an hour has 60 minutes as opposed to 100 minutes. 430 / 100 = 4.3 hours, not 4.5 hours. 450 * 36 result in 16200 minutes, but timezones are represented as hours and minutes, not fractional hours. This results in posts that are posted via email from a half-hour or quarter-hour timezone to be posted in the future or in the past from when it was actually posted." neoscrib Future Releases 24128 Twenty Eleven: add postMessage support for header_textcolor Bundled Theme normal normal Future Release enhancement new has-patch 2013-04-18T17:43:32Z 2013-04-23T16:53:14Z Similar to Twenty Twelve and Twenty Thirteen, this would add immediate visual feedback in the Theme Customizer UI when header text is hidden, or its color value changes. lancewillett Future Releases 20875 Introduce wp_cache_get_multi() Cache normal normal Future Release enhancement new has-patch 2012-06-07T13:56:28Z 2013-04-16T17:12:29Z "Both options (see #10274) and themes (see #20103) could benefit from a cache backend that implements get_multi(). For options, this means we can use individual keys. For both themes and options, we'd be able to make fast multiple gets. Both APC and Memcached (but not Memcache) implement multiple-get. A fallback would be looping over get(). Separately, as this would be a new function we use in core, we probably need to start doing some kind of versioning for drop-ins like db.php and object-cache.php." nacin Future Releases 15565 More context for clean_post_cache() Cache 3.1 normal normal Future Release enhancement new has-patch 2010-11-24T17:41:07Z 2012-10-17T14:21:18Z "I'd like more context to be available when the clean_post_cache hook is run. Scenario: I have a plugin caches the post_IDs of most post queries that go through WP_Query. Invalidating that cache is done via the clean_post_cache hook, but requires a bunch of fragile hacks to prevent cache invalidation for things like comment inserts, which update the post's comment_count (which could, in theory, affect a WP_Query, but that's another story). Option 1: Add extra actions to provide context. This is the simpler option. Patch 1 does this for the above scenario. Option 2: Add an optional context parameter to clean_post_cache(). This is more general, but I can't think of anyplace else WordPress uses as similar approach. Patch two." mdawaffe Future Releases 23327 Cache incrementors for get_bookmarks() Cache 3.5.1 normal normal Future Release task (blessed) new 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 15256 ?cat=## permalinks do not redirect when category is a parent Canonical 3.0.1 high normal Future Release defect (bug) reopened needs-unit-tests 2010-10-30T05:44:18Z 2013-02-25T13:08:53Z "One of my plugin users reported this while using dropdowns to display his categories: http://wordpress.org/support/topic/plugin-my-category-order-multiple-widget-support-broken I was able to duplicate it on my own site in 3.0.1. Any category that has children displayed in the dropdown will redirect to /?cat=## instead of the the friendly /category-name permalink when selected. Select any other category or one of the children and they redirect correctly. Any thoughts?" froman118 Future Releases 10935 WP_Query and is_day() bug ryan Canonical 2.8.4 normal normal Future Release defect (bug) new commit 2009-10-09T05:05:24Z 2013-05-07T20:31:05Z "When you configure Wordpress with permalinks such as /%year%/%month% and even /%year%/%month%/%day/ there is a failure when you request URLs like /2009/10/58, because it's still generating the query to the database (AND YEAR(wp_posts.post_date)='2009' AND MONTH(wp_posts.post_date)='10' AND DAYOFMONTH(wp_posts.post_date)='58'). Also, is_day() returns true, when it should be returning false. As adding a post with that date is nearly impossible trough the wordpress admin or the database, no posts will be found, so Wordpress will show ""No page found"", but with HTTP status 200 OK, not 404 Not Found. I think it's important to validate the day on the applicacion side, so for some ideas to work correctly under WP (like take advantage of sticky posts and show all post for the month in day requests), and most importantly to save those wasted mysql queries. Of course I could validate the day using a filter, but that is not the general idea!" raliste Future Releases 12456 Canonical URL redirect issue with post_id/postname permalink structure dd32* Canonical 2.9.2 normal normal Future Release enhancement accepted tested 2010-03-02T14:06:38Z 2013-05-16T12:31:07Z "The issue: Using /%post_id%/%postname%/ as permalink structure, Most canonical redirects work fine, except: domain.com/post_id/ brings you to the post but does not redirect to the canonical domain.com/post_id/postname/ Additional info: The above permalink structure conforms to best practice as described in the codex: http://codex.wordpress.org/Using_Permalinks#Structure_Tags Therefore I figured this was a bug, given the attention given to redirecting to the canonical url ""So to avoid confusing search engines and to consolidate your rankings for your content, there should only be one URL for a resource."" http://markjaquith.wordpress.com/2007/09/25/wordpress-23-canonical-urls/ " Frank.Prendergast Future Releases 10543 Incorrect (non-UTF-8) character handling in tag's name and slug westi* Charset 2.8.2 normal normal Future Release defect (bug) accepted needs-unit-tests 2009-08-04T05:26:11Z 2010-11-13T01:15:40Z "Incorrect (non-UTF-8) character tag's name and slug are handled in different way: name is truncated on 1st such character, and in slug they are just removed (no truncation). WP should handle both in the same way - drop invalid characters, instead of truncation. I found this issue recently. One of the Polish programs for adding posts to the Wordpresses does not encode tags in UTF-8 - it left them in ISO-8859-2. I notified author of this bug. Unfortunately there are many copies around, so it may take a long time before everyone upgrade." sirzooro Future Releases 18007 is_serialized trouble for multibytes encoding Charset 3.2 normal normal Future Release defect (bug) new has-patch 2011-07-06T16:51:52Z 2013-04-10T12:47:42Z "Possible bug in the ''is_serialized'' function, in a multibytes environment : == Context == * ''utf-8'' encoded database fields * auto overlaoding singlebyte functions from conf (see http://www.php.net/manual/en/mbstring.overload.php) Retrieving an option from the database, the ''get_option'' function try to deserialize it. == Bug scenario == * the ''strlen'' call is actually a ''mb_strlen'' one * the ''$length'' var is the number of characters (not bytes) * using {{{ $data[$length-1] }}} don't retrieve the last char but one before, it's actual position is undefined, depending on the other content of the string * this ''$lastc'' is not '';'' or ''}'' * the string is understood has not serialized == Patch proposal == here is a fix i made to make it work with multibytes string : Not tested it for single bytes, but there is no reason for it to not work. {{{ --- a/wp-includes/functions.php +++ b/wp-includes/functions.php @@ -256,7 +256,7 @@ function is_serialized( $data ) { return false; if ( ':' !== $data[1] ) return false; - $lastc = $data[$length-1]; + $lastc = substr($data, -1); if ( ';' !== $lastc && '}' !== $lastc ) return false; $token = $data[0]; }}} " challet Future Releases 16134 Check capabilities/role before adding comment links to email Comments 3.0.4 normal normal Future Release defect (bug) new has-patch 2011-01-07T10:23:06Z 2011-02-19T20:35:22Z "Currently the Trash it, Delete it, Spam it are added to comment notifcation emails, which are sent to the author. However, the author may have had their role changed down to a lower-role (or had capability removed) since they wrote the post, and no longer would have permissions to use the links added to the email. It may also be the case that a subscriber user was assigned as the Post Author (perhaps as a sort of Guest Author) for a post, and never had the permissions to use those links. Can some sort of check be added, before these links be added to the email?" GaryJ Future Releases 14711 Indexes for comment_author_email and user_id Comments 3.0 normal normal Future Release defect (bug) new 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 11286 Normal User Input Causes Status 500 Comments 2.8.4 normal normal Future Release defect (bug) new commit 2009-11-30T21:45:04Z 2012-11-26T22:20:40Z "To reproduce: Click the Submit Comment button on any post with no other input. Expected Result: Status 200 or 403 with feedback to user. Actual Result: Status 500 with feedback to user. Status 500 means the server is at fault for an unexpected error condition, which is not the case here. It is the incorrect response to send, and it is alarming to see it show up in a server log without an error message. Patch should be ready shortly..." miqrogroove Future Releases 761 Add hook to conditionally disable comment notifications [w/ patch] matt Comments 1.2.2 normal normal Future Release enhancement reopened has-patch 2005-01-27T07:42:58Z 2012-11-07T07:56:15Z E-mail notifications for posted comments are controlled by the 'comments_notify' setting. E-mail notifications for comments needing modification are controlled by the 'moderation_notify' setting. Each is an all or nothing setting, i.e. if 'on', ALL post authors will receive notifications when appropriate. AFAIK, there isn't a clean way for a plugin to insert itself into the notification process. coffee2code Future Releases 13820 AJAX update the comment bubbles on edit-comments.php Comments 3.0 normal normal Future Release task (blessed) assigned has-patch 2010-06-10T13:45:27Z 2012-03-08T01:58:35Z "We update the bubble in the Comments admin menu item. We should also update the counts in the ""In Response To"" bubbles, as well as the bubble color." matt Future Releases 21870 @ error control operator hides fatal error on mysql_fetch_object Database 1.5 normal normal Future Release defect (bug) new has-patch 2012-09-11T14:59:36Z 2012-11-07T19:49:19Z "I ran a get_posts() query that took me a while to track down to the @ error control operator on the mysql_fetch_object call (see wp-db.php:1219 in trunk), therefore PHP was silently die'ing on me because of a memory limit error. I'm curious as to what use cases there are for the error control operator to be used here. In my case, I want to see these errors and fix my code accordingly, or tailor my query to the memory constraints, or rethink my data relations in the database. " ericlewis Future Releases 15004 Missing index on signups table pento Database normal normal Future Release defect (bug) assigned commit 2010-10-01T03:48:25Z 2013-05-07T17:36:17Z "{{{ wp-includes/ms-functions.php:590: $signup = $wpdb->get_row( $wpdb->prepare(""SELECT * FROM $wpdb->signups WHERE user_email = %s"", $user_email) ); wp-includes/ms-functions.php:595: $wpdb->query( $wpdb->prepare(""DELETE FROM $wpdb->signups WHERE user_email = %s"", $user_email) ); }}} But there is no index on user_email in the signups table. Makes these queries perform a full table scan which is slow when you have lots of signups. Attached patch adds the index but I can't figure out how schema upgrades on MS-specific tables ever get run after the initial activation of MS mode and table creation. " barry Future Releases 12257 wpdb Scales Badly Due to Unnecessary Copies of All Query Results ryan Database normal critical Future Release defect (bug) reopened 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 15499 Add an index for get_lastpostmodified query Database 3.0.1 normal normal Future Release enhancement new dev-feedback 2010-11-19T18:20:31Z 2012-12-04T21:50:27Z "I had a friend (Jools Wills) look over a WordPress site recently, to get a fresh view on what might be optimised, and he noticed a query which might benefit from an additional index on ```WP_Posts```. The query ```SELECT post_modified_gmt FROM $wpdb->posts WHERE post_status = 'publish' AND post_type = 'post' ORDER BY post_modified_gmt DESC LIMIT 1``` in ```get_lastpostmodified``` is run for last modified date in GMT, and currently doesn't use an index. This SQL is run whenever certain types of feed are requested as far as I can see. We added ```CREATE INDEX type_status_modified ON wp_posts (post_type, post_status, post_modified_gmt);``` and ```CREATE INDEX type_status_modified_no_id ON wp_posts (post_type, post_status, post_date_gmt);``` and the query runs a lot faster now. The following timings were taken running the first query (```post_modified_gmt```) on a 36,362 row posts table. Note that it doesn't use filesort after the index has been added. ''Before:'' {{{ mysql> EXPLAIN SELECT post_modified_gmt FROM slgr_posts WHERE post_status = 'publish' AND post_type = 'post' ORDER BY post_modified_gmt DESC LIMIT 1; +----+-------------+------------+------+------------------+------------------+---------+-------------+-------+-----------------------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +----+-------------+------------+------+------------------+------------------+---------+-------------+-------+-----------------------------+ | 1 | SIMPLE | slgr_posts | ref | type_status_date | type_status_date | 124 | const,const | 24718 | Using where; Using filesort | +----+-------------+------------+------+------------------+------------------+---------+-------------+-------+-----------------------------+ 1 row in set (0.03 sec) }}} * 0.21290683746338ms * 0.25690102577209ms * 0.230553150177ms * 0.2274341583252ms * 0.23083996772766ms ''After:'' {{{ mysql> EXPLAIN SELECT post_modified_gmt FROM slgr_posts WHERE post_status = 'publish' AND post_type = 'post' ORDER BY post_modified_gmt DESC LIMIT 1; +----+-------------+------------+------+---------------------------------------+----------------------+---------+-------------+-------+-------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +----+-------------+------------+------+---------------------------------------+----------------------+---------+-------------+-------+-------------+ | 1 | SIMPLE | slgr_posts | ref | type_status_date,type_status_modified | type_status_modified | 124 | const,const | 24718 | Using where | +----+-------------+------------+------+---------------------------------------+----------------------+---------+-------------+-------+-------------+ 1 row in set (0.00 sec) }}} * 0.00082707405090332ms * 0.00072288513183594ms * 0.00074386596679688ms * 0.00066494941711426ms * 0.00066208839416504ms In ```get_lastpostmodified``` both these queries are run, so the total savings in my case on a quiet server are nearly 0.5 seconds... worth having, I reckon. I've not created a patch for schema changes before, but I think the only place the change would need to go would be ```scheme.php```? Suggested patch attached." simonwheatley Future Releases 20316 Garbage collect transients Database normal normal Future Release enhancement new dev-feedback 2012-03-28T22:04:35Z 2013-05-14T15:57:57Z "Per an IRC discussion and long-considered changes: * In wp_scheduled_delete(), look for expired transients and purge them. * On DB upgrade, purge all transients, regardless of expiration. (This should probably happen on auto-update as well, but let's let that part slide for now, as DB upgrade will run on all major releases these days.) We should only do this if ! $_wp_using_ext_object_cache." nacin Future Releases 19019 Reduce duplication in $wpdb Database normal minor Future Release enhancement new commit 2011-10-20T21:16:00Z 2013-04-22T19:53:27Z "Currently, update(), insert() and soon delete() [see #18948] use the same code to generate the WHERE clause. It should be moved into a helper method." scribu Future Releases 5932 "wpdb should reconnect and retry query when ""MySQL server has gone away""" pento Database 3.0 normal normal Future Release enhancement assigned has-patch 2008-02-20T08:17:01Z 2012-11-07T06:15:56Z "Using 2.3.3, here are the type of errors that crop up in error_log everyday. {{{ [25-Jan-2008 08:37:35] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = '0' WHERE option_name = 'doing_cron' [25-Jan-2008 09:23:19] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = '0' WHERE option_name = 'doing_cron' [26-Jan-2008 00:03:54] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = '0' WHERE option_name = 'doing_cron' [26-Jan-2008 00:04:29] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_pingme' LIMIT 1 [26-Jan-2008 00:04:29] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_encloseme' LIMIT 1 [26-Jan-2008 00:04:29] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = 'publish' [26-Jan-2008 00:05:09] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_pingme' LIMIT 1 [26-Jan-2008 00:05:09] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_encloseme' LIMIT 1 [26-Jan-2008 00:05:09] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = 'publish' [26-Jan-2008 00:05:47] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_pingme' LIMIT 1 [26-Jan-2008 00:05:47] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_encloseme' LIMIT 1 [26-Jan-2008 00:05:47] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = 'publish' ................. }}} " dtc Future Releases 17391 Alternative color schemes and theme settings in editor styles azaozz Editor 3.2 normal trivial Future Release defect (bug) assigned 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 16077 Placement of link popup in full-size visual editor when browser window is resized garyc40 Editor 3.1 normal normal Future Release defect (bug) assigned has-patch 2011-01-02T19:47:30Z 2013-01-22T16:54:13Z "To recreate: Writing a post in the full-window view of the visual editor, click the link popup. While popup open, resize browser window to be smaller. Link popup stays in original location, even if the window gets small enough to cut it off. You can move the link popup by dragging the top bar. If you do this, then the link popup will stay in the new place b/c our save state stuff, even when you're writing in the regular size visual editor. Preferred UX: if browser window resizes, have link popup recenter itself in the overlay. " jane Future Releases 8368 Scheduling post time behavior and language refinements garyc40 Editor 2.7 low minor Future Release enhancement assigned 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 23630 Simplify the DFW implementation Editor normal normal Future Release enhancement new 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 20903 Exporter gets stuck in a loop a loop/break in the category hierarchy westi Export 3.1 normal normal Future Release defect (bug) new has-patch 2012-06-11T11:26:07Z 2012-06-12T08:13:02Z "Ideally it should be impossible for a loop/incorrect parentage in a category hierarchy to exist. But sometimes they do. If one does exist then {{{export_wp()}}} gets stuck :( It gets stuck in this code: {{{ // put categories in order with no child going before its parent while ( $cat = array_shift( $categories ) ) { if ( $cat->parent == 0 || isset( $cats[$cat->parent] ) ) $cats[$cat->term_id] = $cat; else $categories[] = $cat; } }}} Similar to #20635 but different." westi Future Releases 19307 "Need ability to export ""All content"" but limited to date range" Export 3.1 normal normal Future Release enhancement new 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 19549 Please remove X-Mailer from class-phpmailer westi External Libraries 3.3 normal minor Future Release enhancement assigned dev-feedback 2011-12-14T20:37:14Z 2012-06-02T13:32:25Z "It is nobody's business what software I am using to send mail, or what version number it is. Providing version numbers of server-side packages to strangers is an unnecessary security exposure. With each update to WordPress, I apply this patch. I would appreciate it if you would either include this patch yourselves, or provide a hook where I can do this myself without modifying the source. {{{ --- wp-includes/class-phpmailer.php 5 Jul 2011 20:53:19 -0000 1.3 +++ wp-includes/class-phpmailer.php 14 Dec 2011 19:43:32 -0000 @@ -1129,8 +1129,8 @@ } else { $result .= sprintf(""Message-ID: <%s@%s>%s"", $uniq_id, $this->ServerHostname(), $this->LE); } -// jwz: no. $result .= $this->HeaderLine('X-Priority', $this->Priority); -// jwz: no. $result .= $this->HeaderLine('X-Mailer', 'PHPMailer (phpmailer.sourceforge.net) [version ' . $this->Version . ']'); + $result .= $this->HeaderLine('X-Priority', $this->Priority); + $result .= $this->HeaderLine('X-Mailer', 'PHPMailer '.$this->Version.' (phpmailer.sourceforge.net)'); if($this->ConfirmReadingTo != '') { $result .= $this->HeaderLine('Disposition-Notification-To', '<' . trim($this->ConfirmReadingTo) . '>'); }}}" jwz Future Releases 10984 If content uses the nextpage tag then only the first page is shown in feeds Feeds 2.8.4 normal normal Future Release defect (bug) new dev-feedback 2009-10-20T11:03:11Z 2012-08-27T17:40:40Z "If content uses the nextpage tag then only the first page is shown in feeds if the ""full text"" option is selected in ""Settings > Reading > Show Full Text (in feed)"". No links are displayed to read the full content and no indication is given in the feed that it isn't the full content. I think the behaviour should be to ignore pagination in feeds which are set to ""full text"". I have attached a patch which alters the behaviour of the_content() so that if it is used in the context of a feed it concatenates the pages to form the full content and returns that." simonwheatley Future Releases 13066 Last-Modified headers for individual comment feeds are incorrect jgci* Feeds 3.0 low normal Future Release defect (bug) accepted dev-feedback 2010-04-21T07:32:34Z 2010-11-28T16:18:31Z "The WP::send_headers function currently uses get_lastcommentmodified() to set the Last-Modified header for all comment feeds. This is a problem when used for individual post comment feeds. The function gets the last modified comment across all blog posts. That means that every time a comment is posted anywhere, the Last-Modified header for ALL comment feeds is refreshed. Issues: 1. This is technically incorrect, since only the global comment feed and one specific post's comment feed have changed with the last comment (not all possible comment feeds); and 2. It means that If-Modified-Since requests for other post comment feeds will not receive a 304 response when they should do (since their content hasn't changed). On blogs with many posts and many comment feeds, this will have a large impact on bandwidth because lots of requests will receive 200 responses where 304's would have done, just because a comment was posted on some other post. If I've understood the flow correctly, $wp_query hasn't been fully set up at the time this function is called, so changing this behaviour would require some change in the flow of things (e.g., the handling of last modified headers for feeds moves into the do_feed() function). But doing so would mean that Last-Modified headers are correct/meaningful and that many more 304 responses can be served. Any thoughts?" solarissmoke Future Releases 14493 do_enclose() can ping the same URL many times, can't filter URLs to ping nacin* Feeds 3.0.1 normal normal Future Release enhancement accepted has-patch 2010-07-31T18:52:01Z 2012-11-07T09:14:47Z "If the same URL is included in a post several times, do_enclose() can check that URL for inclusion as a possible enclosure several times. Additionally, there's no way to filter what URLs do_enclose() should ping for possible inclusion as enclosures. Attached adds an array_unique() call to do_enclose(). Attached adds a {{{do_action_ref_array( 'pre_enclose', array( &$post_links, &$pung ) )}}} hook to allow filtration of URLs to ping. (Matches the pre_ping hook.) do_enclose() has several more problems this patch addresses. 1. Correct non-functional DELETE FROM postmeta query (bad use of wpdb::prepare()). 2. Use like_escape() in several LIKE queries. 3. Add an {{{apply_filters( 'enclosure_mime_types', array( 'video', 'audio' ) )}}} hook. 4. Currently do_enclose() doesn't allow root URLs as enclosures (e.g. http://example.com/), only URLs with a non-trivial path or query. Move that functionality to the new pre_enclose filter. 5. Efficiency improvements in conditional logic. 6. Clean up code by reducing control structure nesting depth." mdawaffe Future Releases 4539 Abbreviated year followed by punctuation or markup doesn't texturize jmstacey Formatting 2.5 low normal Future Release defect (bug) reopened has-patch 2007-06-26T03:36:36Z 2012-12-17T14:49:10Z "An abbreviated year followed by punctuation or markup doesn't texturize properly. e.g. (Bruce Sterling, '97) is texturized as (Bruce Sterling, ‘97) when the apostrophe should be texturized as ’ e.g.
  • Casino Royale '06
    • is texturized as
  • Casino Royale, ‘06
    • when the apostrophe should be texturized as ’" pah2 Future Releases 10823 Bad handling of ampersand in post titles Formatting 2.8.4 normal minor Future Release defect (bug) new has-patch 2009-09-21T10:59:50Z 2013-01-23T22:12:06Z "Titles with ampersand (&) are not correctly handled:[[BR]] 1/ the_title_attribute() doesn't transform & to & causing XHTML validation errors[[BR]] 2/ titles with & followed by ; generate truncated post name (slug) e.g. ""Test this & believe ; what ?"" => ""test-this-what""" Commeuneimage Future Releases 15367 WordPress strips multiple line breaks inside of 
     tags	garyc40	Formatting	3.1	normal	normal	Future Release	defect (bug)	assigned	has-patch	2010-11-10T01:39:33Z	2012-09-12T19:49:52Z	"Write a post:

{{{

    This


is




a
test.

    
}}}

You end up with this:

{{{

    This

is

a
test.

    
}}}

Probably related to `wpautop()` I imagine."	Viper007Bond
Future Releases	10041	like_escape() should escape backslashes too		Formatting	2.8	high	normal	Future Release	defect (bug)	reopened	has-patch	2009-06-05T11:18:16Z	2013-04-16T17:04:06Z	"The like_escape() function doesn't escape backslashes.

source:trunk/wp-includes/formatting.php@11518#L2260
{{{
	return str_replace(array(""%"", ""_""), array(""\\%"", ""\\_""), $text);
}}}
should be ...
{{{
	return str_replace(array(""\\"", ""%"", ""_""), array(""\\\\"", ""\\%"", ""\\_""), $text);
}}}
or simply ...
{{{
	return addcslashes($text, '%_');
}}}

Considering multi-byte characters ...
{{{
	if (function_exists('mb_ereg_replace')) {
		$text = mb_ereg_replace('\\\\', '\\\\', $text);
		$text = mb_ereg_replace('%', '\\%', $text);
		$text = mb_ereg_replace('_', '\\_', $text);
		return $text;
	} else {
		return addcslashes($text, '%_');
	}
}}}"	miau_jp
Future Releases	14050	shortcode_unautop() should also remove the 
     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 `
    ` tags as well as adding a `
    ` tag after the shortcode. We then use `shortcode_unautop()` to remove the `
    ` tags, but the `
    ` 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 `
    `

I'm not a regex expert so someone should probably double check my patch, but it seems to work for me."	aaroncampbell
Future Releases	15657	wp_strip_all_tags causes paragraphs to run together		Formatting	2.9	normal	normal	Future Release	defect (bug)	new	needs-unit-tests	2010-12-03T06:05:40Z	2011-12-27T20:49:30Z	"If a post contains HTML like ""foo
    bar"", the RSS feed ends up with the text ""foobar"" instead of the more appropriate ""foo bar"" or even ""foo\n\nbar"".

Here is a simple patch to wp-includes/formatting.php that fixes this: basically, convert 
    , 
     and certain similar tags to newlines before calling the PHP-builtin strip_tags() function.
"	jwz
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.

{{{

    
  
    
    
      Once
I saw it here, I instantly knew what I wanted. I love my new woven wood
shades.
    
      - Ginny Good    		
    
    
      

    
}}}

gets formatted as:

{{{

 style=""width: 120px; height: 92px; text-align: left; margin-left: auto; margin-right: auto;""
    
 border=""1"" cellpadding=""7"" cellspacing=""2"">
    


Once
    
I saw it here, I instantly knew what I wanted. I love my new woven wood
    
shades.

    
      - Ginny Good




}}}

"	Denis-de-Bernardy
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		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:

{{{

    WP IZ ASSUM
    
}}}

Browser will get: 

{{{

    WP IZ ASSUM
    
}}}

All seems to be fine! Now get rid of unnecessary div.

Create article with following HTML:

{{{
WP IZ ASSUM
}}}

Browser will get: 

{{{

    WP IZ ASSUM
    
}}}

Dunno why there is extra 
     but who cares. All seems to be OK.

Create article with following HTML:

{{{

    WP IZ ASSUM

    
}}}

Browser will get:

{{{

    WP IZ ASSUM
    

    
}}}

Now isn't that cool? But check what is even cooler!

Create article with following HTML:

{{{

    WP IZ ASSUM

    NO IT'S BUGGY AS HELL
    

    
}}}

Browser will get:
{{{

    WP IZ ASSUM
    

    NO IT’S BUGGY AS HELL
    

    
}}}

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	20771	esc_url() instead of esc_html() in wp_nonce_url()	SergeyBiryukov	Formatting	3.4	normal	normal	Future Release	enhancement	reopened	dev-feedback	2012-05-29T06:21:37Z	2013-03-18T19:44:48Z	"The `wp_nonce_url()` function currently uses `esc_html()` in its output, which doesn't really seem to be the appropriate escaping function since it's generating a URL.

Attached patch changes the output to use `esc_url()`"	jkudish
Future Releases	13340	wpautop breaks inline MathMl		Formatting	2.9.2	normal	normal	Future Release	enhancement	new	needs-unit-tests	2010-05-11T14:04:58Z	2012-04-07T01:41:16Z	"wpautop treats inline <math> tags as block; they in fact may be placed block or inline, with their flow model dependent on the mode or CSS display property.

Trivial to fix; just needs someone to commit the change. Remove ""|math"" from $allblocks in file wp-includes/formatting.php. math tags on their own will be wrapped in a paragraph, which is fine.

As a very convenient enhancement, please replace on line 210:

{{{
     if ($br) {
-        $pee = preg_replace_callback('/<(script|style). ....
+        $pee = preg_replace_callback('/<(script|style|math) ...
}}}

to prevent MathML being polluted with breaks (current required workaround people are using is to have the whole block on one line, which is very messy to edit)."	nicholaswilson
Future Releases	13821	Changing visibility to password-protected without entering a password does not warn user	kapeels*	General		normal	normal	Future Release	defect (bug)	accepted	has-patch	2010-06-10T13:48:48Z	2012-10-01T17:42:25Z	"Tested on r15182.

If the status of a post is set to Password Protected, and a password is not specified before the user clicks the OK button in visibility and then either publishes, saves, or updates the post, no warning is given to the user that not setting a password forces the post or page to remain Public.

In fact, if updating a post, and this is the only change made, the success message (1) for updating the post appears instead, even though no change was made to the post.

If the post was previously published as Private, and switched to Password Protected without entering a password, then saved, the post switches to Public on save instead of remaining Private.

Either a failure message upon updating or a warning to the user before saving should be displayed to the user to remind them that they didn't properly set a password.

To reproduce the last case above:

1. Create a post. Publish it as Private.
2. Edit the post. Change the visibility to Password Protected, but do not enter a password. Click OK.
3. Update the post.
4. The post visibility will be changed to Public."	markel
Future Releases	15963	Don't try to add orphaned pages' parents' slugs to the page URL		General	3.1	normal	normal	Future Release	defect (bug)	new	dev-feedback	2010-12-23T11:08:55Z	2012-09-19T22:31:20Z	"If a page becomes orphaned---in other words, if a page points to a parent object that doesn't exist any more---`get_page_uri()` doesn't sanity check that the parent object actually exists.

Patch does the check without any extra work, by moving stuff around."	filosofo
Future Releases	19120	Interim login needs some work	azaozz	General		normal	normal	Future Release	defect (bug)	assigned		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	20569	We need addslashes_deep()		General	3.4	normal	major	Future Release	defect (bug)	new	has-patch	2012-04-29T08:08:28Z	2012-09-02T03:15:55Z	"
I don't imagine anyone still feels that having `update_metadata()` call `stripslashes_deep()` is still the Right Thing to do, but I understand why removing it is basically impossible for backward compatibility reasons.

That said, !WordPress as a platform does not currently provide a way for this data to be stored accurately as a meta value:

{{{
$data = array(
	'Check me out, I have backslashes \\'
);
update_post_meta($post->ID, 'my_key', $data);
}}}

I'm not saying that this is a great deal better from a code purity standpoint:

{{{
$data = array(
	'Check me out, I have backslashes \\'
);
update_post_meta($post->ID, 'my_key', addslashes_deep($data));
}}}

but it's at least explainable.

Telling people they have to do something like this:

{{{
$data = array(
	'Check me out, I have backslashes \\'
);
$slashed_data = array();
foreach ($data as $item) {
	$slashed_data[] = addslashes($item);
}
update_post_meta($post->ID, 'my_key', $slashed_data);
}}}

or this:

{{{
if (!function_exists('addslashes_deep')) {
/**
 * Navigates through an array and adds slashes to the values.
 *
 * If an array is passed, the array_map() function causes a callback to pass the
 * value back to the function. Slashes will be added to this value.
 *
 * @since 3.4.0? (oh please, oh please, oh please)
 *
 * @param array|string $value The array or string to be slashed.
 * @return array|string Slashed array (or string in the callback).
 */
function addslashes_deep($value) {
	if ( is_array($value) ) {
		$value = array_map('addslashes_deep', $value);
	} elseif ( is_object($value) ) {
		$vars = get_object_vars( $value );
		foreach ($vars as $key=>$data) {
			$value->{$key} = addslashes_deep( $data );
		}
	} else {
		$value = addslashes($value);
	}

	return $value;
}
}

$data = array(
	'Check me out, I have backslashes \\'
);
update_post_meta($post->ID, 'my_key', addslashes_deep($data));
}}}

is just indefensible.

FWIW, @rboren created this function as [http://core.trac.wordpress.org/attachment/ticket/12402/12402.2.diff part of a patch] a couple of years back (#12402), but it hasn't landed yet. Pretty please can we get just this bit in for 3.4?"	alexkingorg
Future Releases	17923	add_query_arg() should encode values		General	3.2	normal	normal	Future Release	defect (bug)	new	has-patch	2011-06-28T22:55:50Z	2013-02-26T14:08:52Z	"One (or me at least) would expect that the result of

{{{
add_query_arg( 'foobar', 'this&that', 'index.php' )
}}}

would be

{{{
index.php?foobar=this%26that
}}}

since the whole purpose of the function is to build a URL. However the actual result is

{{{
index.php?foobar=this&that
}}}

You're asking to the function to create a URL in which `foobar` is `this&that` but instead it creates a URL in which `foobar` is set to only `this`. You shouldn't have to pre-encode values -- the function should take care of it for you.

The function to ""blame"" for this is our `build_query()` which for some reason does not encode by default.

Semi-related: #16943"	Viper007Bond
Future Releases	16221	admin bar hover class toggle adds whitespace	koopersmith*	General	3.1	low	normal	Future Release	defect (bug)	accepted	close	2011-01-13T22:32:25Z	2012-12-13T19:52:17Z	"Every time I mouseover and mouseout an admin bar item, its class attribute gets longer.

Seen in Chrome while inspecting elements in the admin bar."	andy
Future Releases	22781	setUserSetting cannot handle hyphens		General	2.7	normal	normal	Future Release	defect (bug)	new		2012-12-06T06:18:39Z	2012-12-06T18:25:43Z	"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	22487	Adding priority to settings sections.		General		normal	normal	Awaiting Review	enhancement	new	has-patch	2012-11-17T09:08:34Z	2013-02-05T10:35:14Z	"Currently there is no way (at least that I could find) to specify the order of settings sections on a settings page (for example, a theme options page). Use case: a child theme adding a settings section to the parent theme's ""Theme Options"" page has no way of specifying where on the page the new section should be placed.

I've modified the add_settings_section() function to allow for a priority to be set (much like when adding sections to the theme customizer). I also added `uasort($wp_settings_sections[$page], 'compare_priority');` to the do_settings_section() function, where 'compare_priority' is a slightly modified version of the compare function used to set the priority of the theme customizer sections. The patch is based on version 3.4.2, but I'd be happy to make another for the development version if that would help.

This is my first patch submitted, so please let me know if I need to do anything differently. Thanks!"	alexmansfield
Future Releases	21466	Allow post password cookie expiry to be customized		General	3.4.1	lowest	minor	Future Release	enhancement	new	has-patch	2012-08-04T20:52:35Z	2013-04-16T11:23:29Z	"It'd be nice if you could customize the expiry time for the post password cookie that is set in `wp-login.php?action=postpass`.

The only solution right now is [https://gist.github.com/3259814 pretty ugly]."	Viper007Bond
Future Releases	18954	Automatically whitelist screen options added via add_screen_option()		General		normal	normal	Future Release	enhancement	new		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	14305	Display file for localized versions as Drop-in	nacin	General		normal	normal	Future Release	enhancement	reviewing	has-patch	2010-07-14T09:08:03Z	2011-03-26T08:37:42Z	Localization teams can use special files (for example cs_CZ.php) to handle special problems. This file should be shown on Plugins page, probably as Drop-in, I guess...	pavelevap
Future Releases	22405	Easier expression of file sizes and other data amounts		General	3.5	normal	normal	Future Release	enhancement	new	has-patch	2012-11-10T08:42:05Z	2012-11-18T11:10:49Z	"In the spirit of #20987 writing {{{64 * 1024 * 1024 * 1024 * 1024}}} isn't very readable and cool.

Here is a patch, which adds a couple of constants like {{{KB_IN_BYTES}}}, {{{MB_IN_BYTES}}}, etc."	nbachiyski
Future Releases	22400	Remove all, or at least most, uses of extract() within WordPress		General	3.4.2	normal	normal	Future Release	enhancement	new		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	7394	Search: order results by relevance		General	2.6	normal	normal	Future Release	enhancement	assigned	has-patch	2008-07-24T02:54:18Z	2013-05-14T12:42:59Z	"I have 35 pages in my WordPress install.  My ""About"" page is on '''the second page of results''' when I search for ""about""

We should put hits on the title first in the results list.

I'm open to suggestions for possible technical implementations."	markjaquith
Future Releases	16118	Support for wp_enqueue_style with negative conditional comments		General	3.0.4	normal	normal	Future Release	enhancement	new	dev-feedback	2011-01-06T06:18:40Z	2012-12-13T21:38:49Z	"Please refer to #10891. It refers to the support for conditional comments using the global variable, wp_styles.

I have noticed that if you pass a negative conditional comment, however, this breaks. E.g. Let's say you have a lot of CSS3 rules, which don't apply to IE. You would not include that CSS:

{{{



}}}

I know that IE9 supports CSS3, but I am using the above for illustrative purposes. One would expect that to include the conditional comment above you would do this between the register and the enqueue commands:

{{{
$GLOBALS['wp_styles']->add_data('my-handle', 'conditional', '!IE');
}}}

If you add a conditional tag to wp_styles, however, the generated markup is incorrect:

{{{

}}}

Note the missing --> after [if !IE]>, and