A Sandbox » Page not found

`, `

` 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,12718,Better structure for admin menu,,Plugins,,normal,normal,Future Release,enhancement,reopened,dev-feedback,2010-03-26T01:05:37Z,2013-05-13T16:17:03Z,"Currently, the global $menu variable is one big linear array: {{{ $menu = array( [2] => array('Dashboard', ... [4] => array('', 'read', 'separator1', ...), [5] => array('Posts', ...) ... ) }}} To allow plugins to add a menu item at the end of a group, we use a bunch of additional global variables that remember the last element in each group. Also, we use arbitrary numeric indexes to specify the order of the items, instead of being able to position items relative to one another. It's all very low level. Things would be a lot easier if we had an actual API for manipulating the menu items.",scribu Future Releases,22316,Plugin Dependencies (Yet Another Plugin Dependencies Ticket),,Plugins,3.4.2,normal,normal,Awaiting Review,enhancement,new,dev-feedback,2012-10-30T16:30:46Z,2013-05-13T16:19:17Z,"''Previously: #10190 #11308 #13296 and I'm sure many more'' It's been a few years since we looked at plugin dependencies and this still seems to be a feature people really, really want, especially for shared functionality that isn't a plugin in itself. For example a PHP library that isn't popular enough to be in core but is popular enough to be bundled in multiple plugins. A bunch of us sat down and talked about this at this year's WordPress Community Summit and there was a lot of enthusiasm for this type of functionality. We didn't know about the existing tickets at the time but the general summary of what we came up with was this: * Plugins list WP.org slugs of their dependencies in their `readme.txt`, or perhaps better their plugin's header. * When you go to install a plugin via the plugin directory UI in the admin area, the WP.org API returns a list of dependencies along with the data about the plugin being installed. WP would say like ""these following dependencies will also be installed"". This means it's seamless to the user -- they install a plugin and the other plugin(s) that are needed get installed too. * No versioning support. It's too complicated and what if one plugin wants an older version of a dependency than another plugin does? If your plugin is listing another as a dependency, then it's your job to make sure it stays compatible with the latest version of the dependency. On the flip side, hopefully plugins that get listed as dependencies are made to be forwards and backwards compatible. * Probably not allowing the disabling of plugins that are dependencies while their dependents are active. This seems better than disabling the dependents when the dependency is disabled (""why did Foo get disabled? I only disabled Bar!""). * On plugin re-activation or on activation of a plugin uploaded via FTP, make sure it's dependencies are already installed. If not, offer to install them. If installed but disabled, just enable them for the user. So while the previous tickets were closed as `wontfix` in the past, I think this is worth taking another look at. A lot of planning and thought will be required though to get this right.",Viper007Bond Future Releases,22917,Allow Live Updating of User & Site number in Multisite network dashboard 'Right Now' meta box,,Multisite,3.5,normal,normal,Future Release,enhancement,new,dev-feedback,2012-12-13T14:54:48Z,2013-05-14T12:40:17Z,"Wordpress installation don’t show the correct number of users and sites correctly registered in the site. Please see images for reference: - https://dl.dropbox.com/u/7531173/mu/Only1Site1User.png - https://dl.dropbox.com/u/7531173/mu/UsersNumber.png - https://dl.dropbox.com/u/7531173/mu/UsersSites%20.png",vmaia 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,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,12295,More support to customize user profile edit page,nacin*,Users,3.0,normal,normal,Future Release,enhancement,accepted,dev-feedback,2010-02-19T21:14:01Z,2013-05-15T12:02:10Z,"Right now I can edit the contact methods via the user_contactmethods filter, but I can not modify or remove the Personal Options or the Name Options. I want to keep the interface as simple as possible for my users, and I don't think that they need to edit this settings at all. If wp wants to be a cms, it should give me control over this aspect as well. At least, give me custom css-ids, so I can remove it via css!",pampfelimetten Future Releases,21256,"New theme feature - add_theme_support( 'content-width', $defaults )",,Themes,3.4.1,normal,normal,Awaiting Review,feature request,new,dev-feedback,2012-07-13T10:08:34Z,2013-05-15T15:49:42Z,"Themes use '''$content_width''' variable to set the content area width, they use: {{{ if ( ! isset( $content_width ) ) $content_width = 500; }}} This method has two flaws, it's not flexible and it does not support different sizes for different post-types. WordPress has to make the content-width to be a builtin theme feature using '''add_theme_support()''', and make it more flexible and easy to update. I want to update this value using the Theme Customizer rather editing the function.php file. The code needs to be easy to set and to support CPT, some thing like this: {{{ $defaults = array( 'post' => '500', 'page' => '500', 'attachment' => '650', 'artist' => '300', 'movie' => '400' ); add_theme_support( 'content-width', $defaults ); }}} Just an idea for 3.5.",ramiy Future Releases,23951,Add filter to all sidebar widget content,,Widgets,,normal,normal,Awaiting Review,enhancement,new,dev-feedback,2013-04-05T18:53:20Z,2013-05-15T21:40:41Z,"I'm looking for opinions of other people here before proposing an approach for this. What I'm missing, as far as widgets are concerned, is a filter for changing widget content. I would suggest something along the lines of a filter for the content in WP_Widget's display_callback method. Using this, small changes could be made to widgets while still maintaining upgradability when the plugin, core or theme updates the widget — something that is not the case when extending the widget and overriding the widget method.",Jesper800 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,22115,Further Simplifying errors,,Database,3.4.2,normal,normal,Future Release,enhancement,new,dev-feedback,2012-10-06T11:32:15Z,2013-05-16T11:55:15Z,"tracking errors while making API's and cron jobs, is a tad difficult. from the latest wordpress pack, '''''/includes/wp-db.php''''' {{{ function query( $query ) { ... ... if ( defined( 'SAVEQUERIES' ) && SAVEQUERIES ) $this->queries[] = array( $query, $this->timer_stop(), $this->get_caller() ); // If there is an error then take note of it.. if ( $this->last_error = mysql_error( $this->dbh ) ) { $this->print_error(); return false; } ... ... }}} if we change the above to simply {{{ // If there is an error then take note of it.. $this->last_error = ''; if ( $this->last_error = mysql_error( $this->dbh ) ) $this->print_error(); if ( defined( 'SAVEQUERIES' ) && SAVEQUERIES ) $this->queries[] = array( $query, $this->timer_stop(), $this->get_caller(), $this->last_error ); // If there is an error then take note of it.. if ( ! empty( $this->last_error ) ) return false; }}} then we have all required info in the array queries, for use later. may it be wp_footer, or for a plugin as debug info.",msolution Future Releases,14761,unregister_post_type(),,Post Types,2.9,lowest,normal,Future Release,enhancement,new,dev-feedback,2010-09-02T12:00:17Z,2013-05-16T20:42:09Z,"Two use cases: 1. Remove a core post type. Means that the admin menus should respond in kind, though certain aspects of core like query/rewrite might not like this. Not the main use case regardless. 2. Removing a post type of another plugin, or potentially more likely, a parent theme. Example barebones function: http://wordpress.pastebin.com/VexHkgig Related, unregister_taxonomy() #11058 and unregister_taxonomy_for_object_type(): #14482",nacin Next Release,23205,New Media Uploader slow for sites with many images,,Media,3.5,normal,normal,3.6,enhancement,new,dev-feedback,2013-01-15T17:17:02Z,2013-05-17T08:11:21Z,"The new media uploader added in 3.5 looks very nice. Unfortunately, its functionality is worse for sites with thousands of images. I think this can be combated by allowing us to select the ""Upload Files"" page as our default after clicking ""Add Media,"" and rather than ""All Media Items"" be the page it jumps to after the image is uploaded, instead have it jump to ""Uploaded to this Post."" Is there any way the WordPress team can make this default? Or add the option to make it default? It's made posting on my site 10 times more annoying, especially for those posts with 40-50 images. And I'm sure there are others who feel the same.",salromano Future Releases,24354,get_cat_id() fails with category names containing ampersand,,Taxonomy,3.5.1,normal,normal,Awaiting Review,defect (bug),new,dev-feedback,2013-05-17T08:25:08Z,2013-05-17T10:07:10Z,"{{{ echo get_cat_id('News'); results in 3 (as expected); echo get_cat_id('Test OtherName'); results in 8 (as expected); echo get_cat_id('Test&OtherName'); Results in 0 echo get_cat_id('News & Media'); Results in 0 }}} All the category names were created in the Category Edit page, category names were copied from the text box directly into the code to allow no formatting issues. I tracked the code to get_term_by and I think the ampersand in category name screws up possibly after being added into the prepared SQL statement. ",Kenshino Next Release,24202,Self-explanatory argument values for new media functions,,Media,trunk,high,major,3.6,enhancement,new,dev-feedback,2013-04-26T13:14:52Z,2013-05-17T19:43:58Z,"We've introduced a bunch of functions, some with a relatively long list of arguments, which accept booleans: {{{ function get_content_media( $type, &$content, $html = true, $remove = false, $limit = 0 ) function get_embedded_media( $type, &$content, $remove = false, $limit = 0 ) function get_content_audio( &$content, $html = true, $remove = false ) function get_embedded_audio( &$content, $remove = false ) function get_content_video( &$content, $html = true, $remove = false ) function get_embedded_video( &$content, $remove = false ) function get_content_images( &$content, $html = true, $remove = false, $limit = 0 ) function get_content_image( &$content, $html = true, $remove = false ) function get_content_galleries( &$content, $html = true, $remove = false, $limit = 0 ) function get_post_galleries( $post_id = 0, $html = true ) function get_post_gallery( $post_id = 0, $html = true ) function get_content_chat( &$content, $remove = false ) function get_content_quote( &$content, $remove = false, $replace = '' ) function get_content_url( &$content, $remove = false ) }}} I wonder if we can convert them to use arrays instead for future-proof changes, or at least switch from booleans to self-explanatory values, per our [http://make.wordpress.org/core/handbook/coding-standards/php/#self-explanatory-flag-values-for-function-arguments coding standards]. Otherwise, we might fall into a trap of `submit_button()`: #20492. ",SergeyBiryukov Future Releases,24368,Renaming feature for wp-includes,,Filesystem,3.5.1,normal,normal,Awaiting Review,feature request,new,dev-feedback,2013-05-19T18:24:16Z,2013-05-20T06:37:10Z,"Currently it is possible to rename wp-content to anything you want. WordPress has a definition built in for wp-includes, that is WPINC, however, this definition isn't used in about 15 - 16 core files preventing it from being changed (For example, some CSS doesn't load for the admin bar). I have added the files that I have changed to allow this to work, to work add a definition for WPINC to wp-config with the name of your wp-includes folder without and slashes. Without the definition it just uses the standard wp-includes.",JoeIzzard Future Releases,21663,Use PDO for MySQL queries when PDO is available,,Database,3.5,normal,normal,Future Release,task (blessed),new,dev-feedback,2012-08-22T21:02:28Z,2013-05-20T22:21:49Z,"the mysql_* functions are officially deprecated for PHP 5.4 and will begin throwing E_DEPRECATED errors in the next version of PHP. http://marc.info/?l=php-internals&m=131031747409271&w=2 Wordpress should use PDO by default, but fall back to mysql_* when PDO is not present. See also: #11622 for last year's discussion.",scottconnerly Future Releases,14877,Ability to create exclusive custom taxonomies,nacin,Taxonomy,,normal,minor,Future Release,feature request,reviewing,dev-feedback,2010-09-15T14:08:25Z,2013-05-21T14:20:30Z,"Custom taxonomies should have the option of toggling exclusivity, meaning the user should only be able to select one term at a time. Currently, developers wishing to implement an exclusive custom taxonomy (and thus would prefer radio buttons rather than check boxes on the add/edit post pages) must remove the existing taxonomy meta box completely and build their own, simply to change the input type. This not only duplicates code and development effort, but has the potential to create security vulnerabilities when plugin developers stray from best practices, for example, when recreating the AJAX add term functionality. Exclusive taxonomies are not uncommon in every day life and are even more common when one thinks about typical custom post type implementations (e.g., students->school year, employee->department, car->color, ice cream->flavor). While the best implementation is uncertain, I propose the function register_taxonomy accept an optional 'exclusive' argument (similar to 'hierarchical') that would change the check boxes within the taxonomy meta box to radio buttons and would handle the POST accordingly.",benbalter Future Releases,15337,fix get_attachment_template() to pass templates array,,Template,2.0,normal,normal,Future Release,defect (bug),new,dev-feedback,2010-11-08T02:28:51Z,2013-05-21T19:59:33Z,"get_attachment_template() currently queries for a number of templates based on the mime-type of the attachment. It does so by checking each one individually, and returning as soon as it finds one. It should instead build an array of templates, and pass the entire array to get_query_template(). patch attached.",willnorris Future Releases,19038,"Menu Items aren't deleting on page being trashed, only when deleted",,Menus,3.2.1,normal,normal,Awaiting Review,defect (bug),new,dev-feedback,2011-10-24T17:38:44Z,2013-05-21T22:25:46Z,The linked menu item for a page isn't removed when the page is trashed. ,jeremyatignition Future Releases,22558,Attachment term counts feels/are inaccurate,,Media,,normal,normal,Awaiting Review,defect (bug),new,dev-feedback,2012-11-23T16:21:26Z,2013-05-22T16:47:59Z,"For posts: * Assign a term to a post, save as draft. Term count returns 0. * Publish the post. Term count returns 1. * Change post status back to draft. Term count returns 0. For attachments: * Upload an image, assign a term. Term count returns 0. * Create a new post and insert the image in a published post. Term count returns 0. * Create a new post, use the insert media modal and upload an image. Then go the the media edit screen and assign a term to the image. Term count returns 1. * Change the post status back to draft. Term count returns 1. * Upload an image, assign a term, attach the attachment to a published post. Term count returns 0. The default term update callback is `_update_post_term_count`. The function includes a special case for attachments, that's the reason why we have the 1 in step 3. IMO the term count for attachments shouldn't rely on the parent post status. We should just force `_update_generic_term_count`. Also noted here: comment:ticket:21391:41",ocean90 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 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 Next Release,18650,Make archives and categories widgets dropdown ada compliant,,Accessibility,3.2.1,normal,major,3.6,enhancement,new,dev-feedback,2011-09-13T00:12:37Z,2013-05-22T21:00:44Z,"Conditionally add the tag for the archives and categories widgets so they are ada compliant. http://webaim.org/techniques/forms/controls",jlevandowski Future Releases,16055,Only fire 'Site Wide Only' plugin header deprecated notice if the plugin is activated,,Plugins,3.0,normal,normal,Future Release,defect (bug),new,dev-feedback,2010-12-31T23:13:56Z,2013-05-23T00:04:45Z,Apparently it can be fired on a deactivated plugin. That's annoying and confusing.,nacin Future Releases,24392,Customizer: Display section descriptions like sidebar descriptions,,Appearance,,normal,normal,Awaiting Review,enhancement,new,dev-feedback,2013-05-22T22:05:58Z,2013-05-23T07:07:05Z,"When adding a section to the Customizer, it offers the possibility to add a description of this section. Currently this description gets output as in a title attribute to the h3 headline of this section - and is completely hidden and gone. :( Or did you know we have a four line description of the navigation section? It would be awesome if we could move that more in the user's view, maybe like how we currently do it for widget sidebars?",obenland Future Releases,16953,Allow symlinked plugins,,Plugins,,normal,normal,Future Release,enhancement,assigned,dev-feedback,2011-03-23T20:46:27Z,2013-05-23T18:55:39Z,"There are many scenarios where one would like to have a plugin's folder symlinked to another location. A couple of these scenarios are described in #13550. However, when using symlinks, code such as this fails: {{{plugins_url( 'script.js', __FILE__ );}}} This happens because {{{__FILE__}}} resolves to the real path, which confuses plugin_basename(). The most simple and most flexible solution is to add a filter to plugin_basename(), leaving individual devs to handle symlinked paths, depending on their environment.",scribu Future Releases,24400,Allow custom template selection for custom post types,,Post Types,3.5.1,normal,normal,Awaiting Review,enhancement,new,dev-feedback,2013-05-23T19:33:42Z,2013-05-23T19:33:42Z,"Is there any reason we don't allow custom post types to have custom ""page"" templates?",jfarthing84 Next Release,24402,Menus accordion should be auto-expanded for no-js,,Menus,trunk,high,normal,3.6,defect (bug),new,dev-feedback,2013-05-23T20:03:55Z,2013-05-23T20:04:43Z,"If you visit the Nav Menus UI with javascript turned off, there's no way to expand the accordion sections for adding items. We should auto-expand the accordion for no-js.",DrewAPicture Next Release,24307,Twenty Thirteen: display issues if gallery images are smaller than 300x300,,Bundled Theme,trunk,normal,normal,3.6,defect (bug),new,close,2013-05-10T18:02:53Z,2013-05-23T20:46:09Z,"WordPress 3.6-beta2-24227 Browser: Only tested on Firefox 20 Gallery excerpts on the home page are magnified. Also missing captions on both excerpt and gallery page. This may be addressed by #23584 ""closed defect (bug) (fixed) Twenty Thirteen: Gallery captions are hidden"" but I'm not sure if captions were still meant to be hidden or displayed. On the gallery page the centered images look out of place. Much better to displayed them from the left side as done for 2012. See attached files for screenshots. Also attached 2012 gallery screenshot for comparison which is the same on both the excerpt and the gallery page. Andy Bruin",professor99 Future Releases,12702,Enable sticky post checkbox for custom post type Publish metabox,,Post Types,,normal,normal,Awaiting Review,feature request,reopened,dev-feedback,2010-03-25T05:27:30Z,2013-05-23T22:11:43Z,"When a custom post type is created, there is no checkbox to mark it as a ""Sticky"" post. In meta-boxes.php there is a check: if ($post_type == 'post'): endif; Can this be removed?",phlux0r Future Releases,23912,Add Composer package description,,General,3.5,normal,trivial,Awaiting Review,feature request,new,dev-feedback,2013-03-30T20:44:16Z,2013-05-24T08:50:56Z,"WordPress, as software download, lacks machine-readable source of meta information about it. For PHP projects de-facto standard for such is Composer via `composer.json` file in project root. While WP currently doesn't use or need Composer dependency functionality, it will help provide information to developers and improve WP usage ''as'' dependency in projects that make use of Composer. Suggested `composer.json` draft: {{{ { ""name"" : ""wordpress/wordpress"", ""description"" : ""WordPress is web software you can use to create a beautiful website or blog."", ""keywords"" : [""blog"", ""cms""], ""homepage"" : ""http://wordpress.org/"", ""license"" : ""GPL-2.0+"", ""authors"" : [ { ""name"" : ""WordPress Community"", ""homepage"": ""http://wordpress.org/about/"" } ], ""support"" : { ""issues"": ""http://core.trac.wordpress.org/"", ""forum"" : ""http://wordpress.org/support/"", ""wiki"" : ""http://codex.wordpress.org/"", ""irc"" : ""irc://irc.freenode.net/wordpress"", ""source"": ""http://core.trac.wordpress.org/browser"" }, ""require"" : { ""php"": "">=5.2.4"" } } }}} ",Rarst

"" . $args['title'] . ""

Static menu name