__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter Next Release 23216 "Create ""WP Heartbeat"" API" Administration normal normal 3.6 task (blessed) new needs-docs 2013-01-16T20:41:50Z 2013-06-05T03:15:22Z "The purpose of this API is to simulate bidirectional connection between the browser and the server. Initially it will be used for autosave, post locking and log-in expiration warning while a user is writing or editing. The idea is to have a relatively simple API that sends XHR requests to the server every 15 seconds and triggers events (or callbacks) on receiving data. Other components would be able to ""hitch a ride"" or get notified about another user's activities. In the future this can be used to block simultaneous editing of widgets and menus or any other tasks that require regular updates from the server." azaozz Next Release 23220 Extend autosave to use the browser's local storage in addition to saving to the server Autosave normal normal 3.6 task (blessed) new 2013-01-16T22:33:43Z 2013-06-09T00:45:02Z "There are several types of local (DOM) storage in the modern browsers. Most suitable is the `localStorage` as it's persistent and supported in all browsers back to IE8. The idea is to save the content in local storage every 10 seconds and push to the server every two minutes. When the server responds and there are no errors, we empty the local storage and start again. The local storage will also be emptied when the user saves the post. Then every time the user visits the admin we can check if the local storage is not empty and offer to recover from there or show a revision diff. " azaozz Next Release 24452 Extract Post Formats UI from Core Post Formats trunk highest omg bbq blocker 3.6 task (blessed) new 2013-05-29T20:44:16Z 2013-06-18T23:31:21Z "Per: http://make.wordpress.org/core/2013/05/29/post-formats-ui-is-exiting-core-will-live-as-a-plugin/ This is a tracking ticket for implementing the removal of post formats UI." markjaquith Next Release 24425 Revisions cleanup Revisions trunk high normal 3.6 task (blessed) new 2013-05-25T20:47:40Z 2013-06-16T15:18:45Z "I'm looking over Revisions with Nacin and Koop. We think it needs a general cleanup, on the JS side, and for the Ajax endpoint. Tracking that on this ticket. This might run into some other tickets, but I didn't want to hijack them: #24056 #24346 #24388" markjaquith Future Releases 9445 All Input Tags are not Section 508 Compliance Accessibility 2.7 normal normal Future Release task (blessed) reopened 2009-04-02T18:58:32Z 2012-10-09T20:14:56Z "Not all of the input tags within the Wordpress admin console are section 508 compliant (http://www.section508.gov/). We have scanned the application using compliance software and found many instances where input tags (checkbox, text, textarea, file, radio, etc..) are missing the required label or alt text. (There are many instances where it IS compliant.) We (developers at a government agency) have the ability to make the changes, but some of the decisions for which exact text to put in the labels and alt text should probably be decided by a more dedicated Wordpress developer. Please contact me if you want our help or input. We believe that the software is extremely close to 100% compliance. Bringing it to 100% would be a huge deal for government agencies wh are trying to get approval to install and run Wordpress internally and externally." dmo7 Future Releases 9698 WordPress back end is not accessible Accessibility 2.8 normal major Future Release task (blessed) new 2009-05-01T18:15:41Z 2012-02-20T20:50:25Z "The WordPress back end violates several WCAG accessibility guidelines, so it cannot be considered accessible to people with disabilities. Guidelines: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/ Not being an accessibility expert, I am not sure of all of the violations. But guideline 6.3 states ""Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page."" This means that you should be able to do all functions in the WP back end with JavaScript disabled. As of 2.8-bleeding [11148], there are several things you cannot do with JavaScript disabled: 1) Upload and attach media to a post. You can upload media in the Media section, but the media upload section of the post edit screen is missing without JS, and I see no way to attach it to a post. 2) Add tags to a post or change which tags are on a post. The tags section is totally blank without JavaScript. (It could at least have the default plain-text field that is there behind the scenes and hidden). " jhodgdon Future Releases 16379 "Better UI for doing ""Page on Front""" Administration 3.1 normal normal Future Release task (blessed) new 2011-01-26T19:47:25Z 2013-03-14T15:20:33Z "[[Image(http://grab.by/grabs/132427e6c1166ed3e4d8214959b9568a.png)]] This is the existing ""Page on Front"" UI. The process is as follows: 1. Create a ""Front"" Page 2. Create a ""Blog"" Page 3. Select the ""Front"" Page in the ""Front Page"" dropdown 4. Select the ""Blog"" Page in the ""Blog Page"" dropdown. 1 and 3 make sense. If you want a page on front, then you obviously need to create a page to live there, along with its content, and then designate it. But the ""Blog"" page is just a dummy. It's sole purpose is to create and maintain a URL for your blog. So why not just have something like this? Blog URL: http://example.com/ {input box} If a page exists in the URL they type, it gets used. If not, we create one on the fly as a dummy. This seems a more natural way of doing it. You don't care about the dummy page — you just want to choose an appropriate URL for your blog." markjaquith Future Releases 18655 Responsive Admin for Small Screen Devices Administration normal normal Future Release task (blessed) new 2011-09-13T18:44:16Z 2013-01-03T06:24:12Z Working off of #18198 - Making the admin respond to small devices, phones, etc. saracannon Future Releases 16339 pushState Test Case Administration normal normal Future Release task (blessed) new 2011-01-22T06:30:41Z 2011-01-27T09:42:50Z "This isn't a useful bit of code, just a test case to ground future pushState work for 3.2. Or be ignored by future pushState work for 3.2 :) Attached is a test case for determining browser behavior when using pushState. The numbered links use AJAX and pushState. The ""Other"" link is a real (non-AJAX) link to an external site. If the state of the page is refreshed via AJAX, you'll see a var_dump( $_POST ). If the state of the page is refreshed by a page refresh, you won't. An example of something this test says is broken in Safari 5.0.3 (6533.19.4): 1. Load the page (state = 0: pageload) 2. click ""One"" (state = 1: ajax) 3. click ""Two"" (state = 2: ajax) 4. click ""Three"" (state = 3: ajax) 5. click ""Other"" (state = external site: pageload) 6. go Back in browser history (state = 3: ajax or just history?) 7. go Back (state = 2: ajax or just history?) 8. go Back (state = 1: ajax or just history?) 9. go Back (state = 0: ajax). Everything is fine up to this point, though it's odd we do an AJAX request to get here. 10. refresh the page once, either by CTRL-R or by hitting enter in the URL bar (state = 3: ajax). That's wrong. What happened? Why are we here? 11. refresh the page a second time (state = 0: pageload). As expected. An example of something the test says is broken in Chrome10.0.642.2 dev: 1. Do pretty much anything. Chrome Dev fires a popState event on the first page load. It could be a badly written test, or a badly written implementation of push/popState handling, or both. These are the kinds of scenarios we'll need to test, though." mdawaffe Future Releases 21785 Add header image uploads with cropping to the customizer Appearance 3.4 normal normal Future Release task (blessed) new early 2012-09-04T04:56:41Z 2013-05-22T10:06:20Z See #21355 for an explanation for why header image uploads (sans cropping) was removed from the 3.4 branch. This ticket is about adding it back, with a crop step, to ensure proper support. nacin Future Releases 23327 Cache incrementors for get_bookmarks() Cache 3.5.1 normal normal Future Release task (blessed) new early 2013-01-30T18:24:08Z 2013-04-16T17:11:33Z "Make use of a caching incrementor and store queries in individual cache buckets to avoid memory exhaustion. Pattern this after #23167, which does the same thing for get_pages(). See #23173 for an explanation of the motivation behind this." ryan Future Releases 23173 Don't cache arrays of query results in a single cache bucket Cache 3.5 normal normal Future Release task (blessed) new 2013-01-10T19:05:17Z 2013-04-16T17:10:11Z We have started using one cache bucket per query with passive invalidation controlled through a last_changed incrementor. See #22024 for an example. We also need to do this with get_pages(), wp_get_archives(), and elsewhere. On wordpress.com we have hacked some of these into separate buckets because saving multiple queries per cache bucket results in huge buckets. We have seen 72MB get_pages caches. Let's finally clean this up for good. Some of the last_changed work done for #22176 can be used here. ryan Future Releases 22981 Tweets import plugin tracking ticket PeteMall* Plugins high normal WordPress.org task (blessed) accepted 2012-12-17T18:43:42Z 2013-05-28T20:55:01Z "This ticket is to track the development of a plugin that can import tweets from a downloaded twitter.com archive. Presumably, such a plugin would be added to the importers list on wp-admin/import.php. Trac is best when it is used to discuss implementation. If you want to discuss the general idea, please do so on [http://make.wordpress.org/core/2012/12/16/antsy-for-3-6-to-start-and-need-a/ make/core]. Some initial thoughts on implementation: * It should use the JSON-formatted data that comes with a downloaded tweet archive. The importer should take the entire zip, extract it, and loop through the monthly files. Anything more is an unnecessary burden on the user. * The plugin should import the tweet as actual content. A filter is good idea, if someone wishes to toggle this to instead insert links to tweets (and thus rely on oEmbed). It should also store the JSON-serialized array of data (directly from 1.1 of Twitter's API) in postmeta. * It should import posts as a post format. Status makes the most sense; 'link' could also work for links, then there's also 'aside'. The post format to use should be filterable on a tweet-by-tweet basis. The post type to use should be filterable, as a 'tweet' type may be desired. * It should handle importing an archive over an existing archive, by looking for the existing tweet (probably IDs as a meta key). I don't think deleted tweets should be removed in this process, though. * Remember that tweet IDs are going to be bigger than 32-bit integers, so they must be treated as strings, and we should not try to set a post ID as we might with other importers. This importer should be tested on a 32-bit environment. Beyond that, there are other ""nice to haves"" that would likely be left to plugins of this plugin, given they are beyond the standard role of an importer. Beau Lebens, for example, has done some/all of this already: * Tagging based on hashtags, and a separate mentions and/or in-reply-to taxonomy. * Filtering over raw (no-HTML) content to add things like links to hashtags, links in tweets, etc., on display, rather than doing all of this on save. (Should a hashtag link go to the internal tag, or to twitter.com? Maybe the internal tag's description links to twitter.com?) * A cron to import new tweets using the same importing methods. One thing I will suggest: decisions, not options. Note I said ""filter"" a bunch of times, but never the word ""option."" Not that there won't be a need for any user decision here, but we should make a plugin that works well for the common use cases, and leave the rest to other enterprising developers. Side note: I am working on acquiring a namespace for the Twitter importer in the wordpress.org plugin repository." nacin Future Releases 10787 Email administrators that an update is available for core|plugins|themes dd32 Upgrade/Install 2.9 normal normal Future Release task (blessed) reopened early 2009-09-15T08:44:47Z 2012-12-03T23:50:09Z "Inspired by the recent 'email notifications for updates' plugins discussion on wp-hackers/other forums, I'd like to propose the functionality actually be included in core. I'm thinking of a daily email (Or perhaps, even when WordPress does the update checks) that says along the lines of: {{{ WordPress would like to notify you that you have 3 updates available: WordPress 2.9.1 Plugin: Super Plugin 4 Theme: My Theme }}} Only email when the updates havn't changed since last email. Core potential? Or leave it for plugin material?" dd32 Future Releases 11303 XMLRPC (and APP) APIs should expose all Post/Page/Comment management functionality westi XML-RPC 2.9 normal normal Future Release task (blessed) assigned close 2009-12-01T22:26:01Z 2010-09-23T20:34:55Z "In #11243 we hid the trash status from {{{wp.getPages()}}} we also hide it for pages (and comments I guess). Really these apis should be fully featured to allow clients to support the new things the api does. We should revert the change made for trash for 2.9 and promote the fact that clients should be graceful when using these apis so as to cope when we introduce new features. We also need to review the need for extra apis to allow trashing/untrashing of posts/pages/comments etc." westi Future Releases 22104 High contrast admin colour scheme Accessibility normal normal Awaiting Review feature request new 2012-10-04T17:35:54Z 2012-11-20T16:57:21Z "We should consider bundling a high contrast admin colour scheme with WordPress to aid accessibility for the visually impaired. Some discussion on this has taken place previously on IRC but nothing much beyond that. Some potential points of discussion: * Is anyone in the [http://make.wordpress.org/accessibility/ WordPress accessibility group] an expert on accessibility for the visually impaired? Can we get someone on board for some expert guidance? * Is an admin colour scheme sufficient? Would any JavaScript need altering too? If so, would an admin colour scheme suffice as a starting point? Related: * [http://www.timobrienphotos.com/2009/03/hich-contrast-admin-color-scheme-for-wordpress/ A high contrast admin theme plugin] * [http://wordpress.org/support/topic/admin-color-scheme Support forum discussing admin theme for visually impaired user] * [http://wordpress.org/extend/plugins/easy-admin-color-schemes/ Easy Admin Colour Schemes plugin]" johnbillion Future Releases 24119 A uniform approach to Plugins / Themes settings Administration 3.5.1 normal normal Awaiting Review feature request new 2013-04-18T07:28:14Z 2013-04-26T22:16:55Z "Yesterday [https://irclogs.wordpress.org/chanlog.php?channel=wordpress&day=2013-04-17&sort=asc#m2987650 in IRC] (#!WordPress), we had a conversation about rules that would help make plugins and themes easier to use, which in turn would make !WordPress easier to use. There isn't a rule or guideline whether a plugin should make a tab or link under settings or if it even has to do any of the above. We all agreed that all plugins should have a link under settings. If the plugin enhances a different part of the site, the settings page could just tell you where the plugin feature is located. We also agreed that themes should put features like a static front page under customize like most already do, though I heard Responsive doesn't. I was told it puts static front page under settings. If it is a theme feature, then logically you should be able to at least find a link to where the features are under themes. Implementing general rules for plugins and themes would make !WordPress easier to use. Does anyone else agree? " ryansatterfield Future Releases 21925 Ability to upload multiple .zip files to install in bulk Administration normal normal Awaiting Review feature request new 2012-09-19T12:40:09Z 2013-06-14T17:38:01Z "It'd be nice to have a drag-and-drop or similar functionality to the Media Uploader to be able to select 5, 10, 17 plugins/themes to upload several .zip files at a time. Of course, if a folder already exists or if you upload a theme .zip to the plugins page or something like that, then display the appropriate error(s). Otherwise, display the success notification per install." cliffpaulick Future Releases 12801 Add Info link to plugins management screen Administration 3.0 normal normal Future Release feature request new 2010-04-01T19:08:40Z 2013-01-22T01:40:01Z "Related to #11050 but instead of the search results, on the regular plugins.php screen. Add ""Info"" link to left of Activate/Deactivate action links, which brings in the tabbed info from the repo. If not from the repo, link does not appear." jane Future Releases 24511 Backend function for retrieving post row actions. Administration normal minor Awaiting Review feature request new 2013-06-06T10:27:15Z 2013-06-07T12:02:42Z "For the cases where post titles are not supported for custom post types, but the user may want the quick action links to exist on their edit.php page table rows on hover. All it would take would be to move the current code into a callable function and would probably only need to accept a post ID. Could then be called using something like {{{get_post_row_actions($post_id)}}}. It would return the string of links seen normally below the title on hover." Nessworthy Future Releases 12273 Better support for sites with LOTS of pages Administration 2.7 normal normal Future Release feature request new 2010-02-18T15:10:02Z 2011-04-18T14:41:23Z "The default page listing is inadequate for sites utilise Pages as their main content type. An option to collapse the page listing and hide ""all"" sub-pages (only showing top-level) would dramatically improve the UI making it easier to find pages within the WordPress structure. '''Example:''' ''Current Page View'' {{{ Page 1 -SubPage 1.1 --SubSubPage 1.1.1 --SubSubPage 1.1.2 -SubPage 1.2 -SubPage 1.3 Page 2 -SubPage 2.1 -SubPage 2.2 --SubSubPage 2.2.1 --SubSubPage 2.2.2 }}} ''Proposed Page View'' ''Default View'' {{{ Page 1 [+] (< click to expand) Page 2 [+] }}} ''Expanded View'' {{{ Page 1 [-] -SubPage 1.1 [+] (< click to expand) -SubPage 1.2 -SubPage 1.3 Page 2 [+] }}} ''...'' {{{ Page 1 [-] -SubPage 1.1 [-] --SubSubPage 1.1.1 --SubSubPage 1.1.2 (> no further levels) -SubPage 1.2 -SubPage 1.3 Page 2 [+] }}} " mkjones Future Releases 20013 Clean Up Touch UI for Left NavMenu / Flyouts Administration 3.3.1 normal normal Future Release feature request new reporter-feedback 2012-02-10T16:30:50Z 2013-01-22T15:24:19Z While the flyout is mostly usable in it’s current state, it is not as intuitive as it needs to be for the best user experience. They are ineffective at best on the Kindle Fire’s Silk Browser, but work pretty well on the iPad. We need to examine all target devices to ensure interactivity is supported cross-device. georgestephanis Future Releases 22862 Consider a CSS preprocessor Administration normal normal Awaiting Review feature request new 2012-12-11T22:01:36Z 2013-01-16T10:33:34Z "The WordPress admin UI CSS is woefully doomed to a life of inadequacy unless we can amenably agree to use technology already available to build a better future for us and our children. I propose the introduction of SASS for the WordPress admin styling. SASS is a CSS pre-processor that allows us to write DRY, structured, lightweight CSS. In terms of licensing, SASS is GPL-compatible, licensed under the MIT license. '''Why use SASS over LESS?''' The answer is simple. SASS is easier to learn and easier to use because it follows the conventions of CSS at its core. In addition, for developers itching to contribute, there are some extremely useful and easy-to-follow reference docs for SASS, making it easy to set up your local development environment and build websites. '''What are the advantages?''' The biggest advantage is that we can write less CSS and offer advanced features for theming the WordPress Admin UI. Developers can more easily reskin the WordPress admin. Another major benefit is that SASS offers the use of variables within our stylesheets. For our purposes, these variables can be used to calculate layout widths, generate color schemes, font sizes, etc. Another simple advantage is the fact that we can combine all our CSS styles into a single stylesheet, saving precious HTTP requests. In addition, we can easily minify generated CSS files in bundled versions of WordPress, saving file size and killing unnecessary white space, thus decreasing load times of the admin even further. '''What are the disadvantages?''' Developers will need to install Ruby and SASS in order to modify styles for the WordPress Admin. For plugin authors, we should write admin UI CSS in such a way that it is easily overridden with a custom CSS file. In addition, developers would need to learn SASS if they are going to work directly on the styles for the WordPress admin. For the most part, once you've got the idea of variables, mix-ins, and the structure - you're ready to rock. Last, but not least, when SASS files are modified, they would need to be compiled and committed to Core every time they change. So instead of pushing a single CSS file, you would be pushing potentially many SCSS files and a generated CSS file. '''In Summary''' SASS is a great way to reduce code overhead by adhering to DRY principles and will improve performance and modularity in the WordPress admin, which is a top priority." chriswallace Future Releases 20301 Enable media library access from blogroll Administration 3.3.1 normal normal Awaiting Review feature request new 2012-03-25T08:50:37Z 2012-03-25T17:10:03Z "Currently WordPress doesn't give you the option to easily add images from your WordPress plugin to your blogroll items (links). I just released a plugin to do that (http://wordpress.org/extend/plugins/blogroll-media-library-image/) and was told this would be a good one to add to core. I would love to add a diff-file, but I have no idea how to do this." illutic Future Releases 24313 Filter Columns by View Administration normal normal Awaiting Review feature request new 2013-05-11T01:18:56Z 2013-05-11T14:12:54Z "After searching extensively for a way to do this, and discussing this with fellow WordPress developers, I believe I have found a feature that should be added to WordPress. When you make a new custom post type, if you have WordPress register a UI for it, it outputs a screen named ""All XXXX's"". Within these, WordPress automatically adds filters. So let's say I've registered a CPT called Downloads. So I can now use the built in UI for Downloads and filter the page to show just pending downloads, or just published downloads, for instance. However, the issue becomes what if you want to display a column for some views, but not others. For instance, if Downloads has a column called ""Sales"" where the number of sales of that particular download is stored, it makes no sense to show that column on Pending Downloads (since they can't have sales before being published). Currently, at least after days of trying to find a way of doing this, there is no way to do this for the tables registered by WordPress. If I make my own List_Table, then I can do this. However, there should be a way of adding columns based on filter, so that a developer who adds a column programmatically can go: {{{ if($view != pending){ // register sales column } }}} Feel free to correct me if I've overlooked a method of doing this. -Chris" chriscct7 Future Releases 18848 Filter post listing screen by post parent johnbillion Administration 3.3 normal normal Awaiting Review feature request assigned 2011-10-03T16:19:10Z 2011-10-03T18:56:58Z "It's not possible to filter a post listing screen by post_parent. This would be super handy for hierarchical post types (eg. Pages) where you may have several levels of hierarchy and want to view only the descendants of a particular page. I'm not sure that we need a UI (eg. dropdown menu) for it, but a working URL query var would be great. I made an attempt at patching this a while ago using the child_of parameter but it got complicated quite quickly, so I'm putting it out there as a feature request in case anyone feels like tackling it." johnbillion Future Releases 13516 Hide JS-only widgets on dashboard is no JS Administration 3.0 normal normal Future Release feature request new 2010-05-24T13:16:42Z 2011-12-24T16:16:41Z "We hide screen options and help; we should also hide these widgets instead of displaying by default with the 'you need JS' message. Affected modules: QuickPress, Incoming Links, Plugins, WordPress Development Blog, Other WordPress News. We should display an additional module for no-JS people that lets them know that their WordPress install would be even more awesome with JavaScript, and list out some of the features they would gain access to with JS enabled. " jane Future Releases 22056 Integrate a list of notices for newbie users Administration 3.4.2 normal normal Awaiting Review feature request new dev-feedback 2012-09-30T14:39:40Z 2012-10-02T18:21:13Z "Integrate a list of possible warnings and notices for the power-user (admin) if some problems or security thread occur, or to check if the site was infected with viruses and malicious .php files... Example: - Notice: GD Graphics Library is not installed, install this so the images could be resized - Notice: Your site is not giving search engines the right to index the site, please consider changing the settings. - Warning: An unknown file mail.php is in the site main directory, please check if you are not infected. - Notice: Your site files permissions are set to 777, please change to 644 or 640, your site is in a security thread. - Notice: Upload folder is not writable, please change permission to 755 for the upload dir. - Notice: Please use a caching file plugin to make your site load faster than ever. " alexvorn2 Future Releases 15289 Make it easier for a non-standard URL to be used to access wp-admin Administration 3.1 normal normal Future Release feature request new dev-feedback 2010-11-02T13:27:05Z 2013-02-07T21:51:15Z "For some sites it is vital that the admin be accessible via a path other than {{{/wp-admin/}}}. Clients sometimes require this because it is easier for their users. Also, it is useful if replacing another CMS with WordPress for the root of the admin to have the same URL, although this can be partially fixed with a redirect. Even when not ''required'' per se, some of us prefer to use a different URL to access the admin because it is more intuitive for our users to use something like {{{/admin/}}} instead of {{{/wp-admin/}}}. To be clear: I am not suggesting renaming the wp-admin directory, nor am I suggesting adding an option in the UI to change the path. Rather, I am suggesting that small tweaks be ade to make it easier for power-users to enable the use of a different URL to access the admin area. I suggest making the following changes : '''1.''' Use relative urls within the admin where possible without affecting standard installations. '''2.''' Allow power-users to add a constant to wp-config.php to change the path of the admin for those links which have to be absolute. I don't think there is much work involved and I am happy to do it. Core devs have in the past stated that the user of alternative urls to access the admin is 'not supported', but it is unclear whether this simply means that it doesn't work at the present time or that the core team is opposed to allowing it to happen.[[BR]] If the latter is the case, I would appreciate an explanation - I'm sure there is a good reason if that is the case, but I can't for the life of me think what it could be. ;)" caesarsgrunt Future Releases 14676 Moderation email option is confusing, limited Administration normal normal Future Release feature request reopened 2010-08-23T17:06:23Z 2012-05-22T00:53:20Z "The setting is ""E-mail me whenever a comment is held for moderation"" but in that sentence ""me"" is inaccurate; moderation emails are sent to admin_email. ""Email the admin ($admin_email) whenever"" would be accurate. Here's a related question: Why not send moderation emails to post authors?" andy Future Releases 9057 "Need ""restore defaults"" buttons on all admin screens" Administration 2.7 normal normal Future Release feature request new 2009-02-06T08:50:30Z 2011-07-08T15:06:31Z "Need ""restore defaults"" buttons on all admin screen items, else once you change something, there's no way to get it back to whatever the default was, or find out even, short of a total reinstall. Includes ""screen options"" items too. " jidanni Future Releases 12004 Select Sidebar when adding Posts/Pages Administration 3.0 normal normal Future Release feature request new 2010-01-25T13:26:16Z 2010-01-25T23:28:01Z "Hey all, I think it would be a cool feature to be able to create sidebars in WP, and then when creating a page you can choose that specific sidebar. I think that this can be accomplished by using the ''Parent'' page technique of selecting if the Page has a Parent and if so which one. Can we develop an option to choose a Sidebar created in the Widgets panel? Cheers, Aron ps: if my help is needed ( im good at design, not coding ) please contact me: info@zipyourmix.com ;)!" lsddesign Future Releases 11972 Sort View Post/Pages by Column Administration 3.0 normal normal Future Release feature request new 2010-01-21T21:46:27Z 2010-03-21T01:51:40Z Recently I discovered in WPMU in Site Admin options, you can sort for instance Site Admin->Blogs by last activity date. That is a very handy feature, and certainly would useful for a site with hundreds of nested pages. To be able to sort that list by date, rather than just title would be useful, as it sorts by title of the parent page, and finding a 3rd level child can be difficult to say the least. The search feature is lacking but that is for another ticket. Likewise, sorting posts by category, author, etc could be useful. Since the functionality seems to already be there for sorting these type columns, and the code's been moved in already, I'd think it'd be a nominal change. I simply don't know what direction these menus are going yet to offer a working suggestion. Just wanted to get my 2¢ in before it's too late. miklb Future Releases 23575 Standard UI Classes and Functions Administration 3.5 normal normal Awaiting Review feature request new 2013-02-21T09:09:27Z 2013-02-22T02:31:55Z "It would be nice if wordpress allowed you to use the Post UI natively in my plugins, at the moment I've had to write a few classes for my Plugin Framework that mimic the Publish Metabox and Tabbed Metabox. As there is simply no easy way to do this at the moment, I think there should also be a better way of registering hidden menus. I have to jump through loads of hoops just to do this. " jscampbell.05 Future Releases 17460 WP Updates througth SSH Script bugdev Administration 3.2 normal normal Awaiting Review feature request new dev-feedback 2011-05-16T19:57:14Z 2011-05-16T20:45:56Z "The current WP Update engine is very unsecure, because if there is a webserver issue or a connection timeout, memory overflow, connection issue than the wordpress update is corruptes. More secure the update will be if we can do/execute a php script or ssh script througth the terminal, what also gives advanced informations about update errors ect." bugdev Future Releases 22734 do_action-post_edit_form_tag Administration 3.4.2 normal normal Awaiting Review feature request new reporter-feedback 2012-12-04T18:01:27Z 2013-06-06T12:23:56Z "Possible to add an action on the form for adding media. {{{ File : /wp-admin/media.php Line : 115 }}} {{{
}}} to {{{ > }}}" bems78 Future Releases 21455 HiDPI (retina) theme custom backgrounds Otto42 Appearance normal normal Future Release feature request assigned 2012-08-02T17:07:06Z 2012-09-15T05:22:40Z "We should support HiDPI custom backgrounds. This will be a bit easier than custom headers, #21389, as we can do a media query in _custom_background_cb(). Worth noting that we will still need to solve some aspect of retina uploads, #21038." nacin Future Releases 21389 Retina theme custom headers Otto42 Appearance normal normal Future Release feature request assigned 2012-07-25T19:40:56Z 2013-06-14T15:56:11Z We should support retina custom headers. Not sure how — ideas welcome. nacin Future Releases 21666 Theme customizer reset Appearance 3.4.2 normal normal Awaiting Review feature request new 2012-08-23T10:09:49Z 2013-05-18T13:13:22Z "It would be useful to be able to reset the settings to the defaults as specified in the add_setting() class method when setting up each setting. These could be reset on a section by section basis and/or for ALL settings." dgwyer Future Releases 24514 Collaborative theme development Bundled Theme normal normal Awaiting Review feature request new 2013-06-06T11:19:20Z 2013-06-06T11:19:20Z "It would be very interesting if, for the next theme (Twenty Fourteen), all the development process (desing, early decisions, etc.) will take place on trac (or github, for example). It will be a way for designer/developers to interact and, above all, a great learning tool." gorgoglionemeister Future Releases 20025 Add a filter for post types when viewing list of comments in the backend Comments 3.3.1 normal normal Awaiting Review feature request new 2012-02-12T14:03:49Z 2012-02-12T14:38:23Z Filtering comments based on post type nprasath002 Future Releases 12223 Adding a titles to comment levels with the walker class Comments normal normal Future Release feature request new 2010-02-14T11:20:07Z 2010-02-14T17:52:36Z "Hi Everyone! This is only my second post here, and my first feature request, so please excuse me if I have duplicated something or my solution is completely unsuitable. I am experimenting with the CMS capabilities of Wordpress, especially the enhanced post_type GUI in the new 3.0 alpha release. While building a sort of Yahoo Answers type platform, I wanted to have 1st level comments as answers to a question (a post), and 2nd level comments as comments on the answer (1st level comments). I wanted to label comments on an answer as ""comments"", but this is not really possible to do, to my knowledge, using ""wp_list_comments"". I created my own function for wp_list_comments so I didn't have to modify Wordpress core, in order to get at the walker class at the bottom of wp_list_comments. I wanted to use start_lvl to add a title for comment level 2. However, start_lvl in ""class Walker_Comment extends Walker"" will only let you change the list type to ""ul"", ""ol"" or ""div"". My idea is to add an argument which would allow you to add a title, along with specifying it's heading (or surrounding tag). As I said, I am not an expert on Wordpress coding standards, so the following code may be completely off. {{{ /** * @see Walker::start_lvl() * @since unknown * * @param string $output Passed by reference. Used to append additional content. * @param int $depth Depth of comment. * @param array $args Uses 'style' argument for type of HTML list. * @param array $args Uses 'title' argument for title text. * @param array $args Uses 'title_heading' argument for title text heading level. */ function start_lvl(&$output, $depth, $args) { $GLOBALS['comment_depth'] = $depth + 1; switch ( $args['style'] ) { case 'div': break; case 'ol': echo ""
    \n""; break; default: case 'ul': echo ""