ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter 21977 Allow 0, NULL and empty string values for 'parent'. XML-RPC normal normal Future Release defect (bug) new dev-feedback 2012-09-23T18:28:04Z 2012-11-07T21:51:29Z We must allow 0, NULL and empty string values for 'parent' in wp_newTerm and wp_editTerm sam2kb 17541 Blogger-XMLPRC API does not work with Multisite/SSL/DMZ combination westi* XML-RPC 3.2 normal major Future Release defect (bug) accepted has-patch 2011-05-23T07:26:29Z 2012-12-14T23:12:02Z "I have the following setup: My WordPress Blogs (multisite) are set up behind a firewall that exposes the public address via SSL. Inside my DMZ I'm only using HTTP, so that's what WordPress sees. When I now try to access the blogger.getUsersBlogs XMLPRC-API, I get an empty result back. I analyzed the WordPress source code and found out that the blogger.getUsersBlogs method in the file wp-includes\class-wp-xmlrpc-server.php uses another XMLRPC call to the wp.getUsersBlogs method in case of the multisite. I further checked and found out that this appears to be the only case in which WordPress executes a remote call itself to sevice the request. I then replaced the logic in _multisite_getUsersBlogs with the multisite part from wp_getUsersBlogs and it worked. I aso found an issue that might be related: http://core.trac.wordpress.org/ticket/16402 But since the source code in the trunk still uses the regular IXR_Client, I'm not sure if this would fix the issue. I attached my fix as a patch, but it's not refactored to remove code duplication since I don't have a dev-environment set up for WordPress. Michael" michael_k 12939 Counterpart to content_save_pre hook not called when getting post content via API josephscott XML-RPC 2.9.2 normal normal Future Release defect (bug) reviewing dev-feedback 2010-04-09T13:53:57Z 2011-04-05T08:50:45Z "When a post is submitted either through the web editor interface or from an API call to newPost or editPost, the content of the post is inevitably passed through the content_save_pre filter. And when a post is opened for editing in the web editor, the content is passed through filters such as the_editor_content and content_edit_pre. However, when a post is fetched for editing via XMLRPC API calls such as getPost or getRecentPosts, the content_edit_pre filter is never reached. This leads to a situation where whatever massaging of the content that a plugin may peform on the way into the database is not reversed on the way back out, for clients of the API. A concrete example of this problem is with the popular Syntax Highlighter Evolved: http://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/ This plugin performs encoding of the post content before it is stored in the database, and it counts on being able to decode that content by adding filters to hooks such as the_editor_content. However, none of these filters are reached via the API, leading to ""corrupted content"" when users try to edit posts from API clients such as the iPhone WordPress app, or my desktop editor, MarsEdit. (My previous bug report #10802 exhibits the same symptoms of this bug, but this is a different cause). In summary: 1. WordPress needs to establish a clear, baseline hooks for massaging content before it is saved to the database, and for un-massaging the content on the way out of the database. Currently there seems to be uncertainty about which hooks need to be overridden and under what circumstances. It seems to me that content_save_pre and content_edit_pre are probably good candidates for this. 2. Whatever hooks are established as the guarantees need to be applied once and only once in both the web-based editing scenario, and in the API editing scenario. I think that having a well documented pair of hooks for this purpose that works identically in the web editing and API editing cases will do a lot to ensure correct behavior when plugins are installed that massage content, and will make it easy for plugin developers to ""do the right thing"" without relying on hooks that are specific only to the web editor, or to the API. " redsweater 20070 Deprecate Blogger XML-RPC Methods XML-RPC 3.3.1 normal minor Awaiting Review defect (bug) new dev-feedback 2012-02-18T18:32:26Z 2012-02-18T18:32:58Z "The XML-RPC API supports the legacy Blogger API methods, but these methods have apparently not been very well tested or maintained. Given that the `wp.*` XML-RPC namespace now covers everything that the Blogger API does, I suggest the blogger methods be officially deprecated with an eye towards removing them in a future version. At the very least, the MetaWeblog API should be used by clients instead, as it was explicitly designed to enhance and supersede the Blogger API." maxcutler 14452 Duplicate check for comments: Inappropriate errorhandling for xmlrpc XML-RPC 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-29T08:44:34Z 2012-06-23T22:48:28Z The duplicate check for comments just dies in case a dulicate is detected(see wp-includes/comment.php around line 550). This ends up with a html page delivered in any cases. When accessing through xmlrpc this leads to the problem that this html page is send back to the xmlrpc client instead of a proper xmlrpc formated message. mrutz 16980 Empty Values are ignored by class-ixr.php XML-RPC 3.1 normal major Awaiting Review defect (bug) new dev-feedback 2011-03-27T12:34:47Z 2011-05-25T05:19:53Z "I tried to fix the following bug #10599 Found out when you send and empty value via xmlrpc it converts it to null value. Say you send and array of arguments for mw_editpost, set {{{ $content_struct[mt_keywords] = ''; }}} IXR client passes a null value instead of an empty value. In mw_post method consider this statement {{{ $tags_input = isset( $content_struct[mt_keywords] ) ? $content_struct[mt_keywords] : null; }}} Even if you send an empty value this statement fails because {{{ $content_struct[mt_keywords] }}} is set to null by IXR client." nprasath002 21098 Out of memory errors in XML-RPC XML-RPC 3.4 normal major Awaiting Review defect (bug) new dev-feedback 2012-06-28T13:48:53Z 2012-09-23T19:43:33Z "Since WPiOS 3.0 and WordPress 3.4 we're getting a lot of ""Out of Memory"" reports on XML-RPC. See http://ios.forums.wordpress.org/topic/couldnt-sync-posts-after-update-to-300 XML-RPC clients have no idea of the memory available, and even if they did it'd be hard to translate that to ""how many items can I request"" Some ideas: * Can we try raising the memory limit on xmlrpc.php, or at least for system.multicall? * Setting limits on the number of items returned if we can predict that they're going to need too much memory. Currently asking for the latest 100 comments can trigger an out of memory error in some hosts. * Fail more gracefully: return an XML-RPC error instead of a HTTP 500 Internal Server Error * Any hints on debugging where memory is going and if there are any leaks?" koke 10699 Password Expose Bug in XML-RPC Debugging ryan XML-RPC normal normal Future Release defect (bug) new close 2009-08-29T01:46:43Z 2012-09-17T06:20:27Z "Though this may not effect many users, I was testing something through xmlrpc with logging enabled and came across something that might create a security problem. If xmlrpc logging is enabled WP logs the password from the request struct in an unencrypted format. Now I understand that not many will open up xmlrpc logging on production blogs, could it be possible that WP just strikes out the password before logging it to the file as it is always the third param so easy to do that, this is because people who might have xmlrpc logging enabled may not change the default log filename and location so anyone can simply run a robot to check for http://blogurl.com/xmlrpc.log and farm passwords (now this may not affect blogs that have WP installed in root since it writes to ../xmlrpc.log, so essentially outside the www access dir, but blogs with WP installed in sub directories will be affected). Don't know how critical this is as users have to manually edit the file to enable xmlrpc logging so it might be a non critical bug." keithdsouza 24280 Privilege check in mt_publishPost XML-RPC 3.0.3 normal normal Awaiting Review defect (bug) new 2013-05-07T17:58:02Z 2013-05-07T23:59:08Z "The mt_publishPost function requires both the publish_posts and edit_post privileges to publish a post. Elsewhere, the publish_posts privilege is sufficient to publish a post." fgauthier 23017 Support for fatal errors on XML-RPC XML-RPC 3.5 normal normal Awaiting Review defect (bug) new has-patch 2012-12-20T11:24:27Z 2013-03-19T11:22:13Z "Similar to #16748, when a fatal error occurs, PHP will output some HTML code which at best is confusing for XML-RPC clients. Using the `shutdown` action, we could die more gracefully and return a XML-RPC formatted error" koke 17920 Unnecessary code in wp.getPage XML-RPC 3.2 normal minor Awaiting Review defect (bug) new dev-feedback 2011-06-28T16:33:00Z 2012-06-24T20:22:32Z Pages Does not have categories nprasath002 10764 XML- RPC, blogger_editPost, Publish Status not working josephscott XML-RPC normal normal Future Release defect (bug) new dev-feedback 2009-09-10T00:58:09Z 2012-06-23T20:39:22Z "In the blogger_editPost function in xmlrpc.php is not working properly. Currently you cannot change publish status. It looks like we are missing a line of code. {{{ $post_status = ($publish) ? 'publish' : 'draft'; }}} When I inserted this line into the function before the {{{ $postdata = compact('ID', 'post_content', 'post_title', 'post_category', 'post_status', 'post_excerpt'); }}} I was able to gain control of the publish status. " bobby_drk 20630 XML-RPC Extending documentation for methods called with a single param XML-RPC normal normal Awaiting Review defect (bug) new needs-docs 2012-05-07T18:47:46Z 2012-05-07T19:06:01Z "When an XML-RPC method is called with a single parameter, the method will receive the value directly instead of receiving an array with a single value. This seems to be intended, though unexpected, behavior. The documentation should be updated to mention this. The related code is inside IXR_Server->call()." scott.gonzalez 22936 XML-RPC WordPress api setOption double escapes args XML-RPC normal major Awaiting Review defect (bug) new 2012-12-14T13:46:35Z 2012-12-15T15:31:10Z "Parts of the xml-rpc wordpress api are not usable, as they doublequote strings. e.g. `Munich's` becomes `Munich\\'s`. wp.setOptions($args) escpapes all args and calls update_option() which is then calling mysql_real_escape_string(), leading to a double escaping. To solve this options should not be escaped in wp-setOptions() function. Here the callStack showing the 2nd escaping: {{{ wp-includes/wp-db.php.wpdb->_real_escape:884 wp-includes/wp-db.php.wpdb->escape_by_ref:950 wp-includes/wp-db.php.array_walk:0 wp-includes/wp-db.php.wpdb->prepare:1003 wp-includes/wp-db.php.wpdb->update:1365 wp-includes/option.php.update_option:258 }}}" jachzen 16985 XML-RPC endpoint set the datetime when saving a Draft XML-RPC 3.1 normal normal Future Release defect (bug) new needs-unit-tests 2011-03-28T13:33:46Z 2012-06-24T00:15:12Z "When uploading a draft post from one of the WordPress mobile apps the post date is set to the current time/date, even if the datetime field is not specified on the client request. This could cause issues, because when you change the post status to ""publish"" it will be published using the date set during the first upload. On the web dashboard if you do not set the post datetime explicitly, it is not set and hitting publish will then populate the datetime field with the current time. The same happens if you start a draft on the web and then you publish it using any mobile apps. details here: http://ios.trac.wordpress.org/ticket/826" daniloercoli 12518 XML-RPC newMediaObject should try to work out mime-type if not supplied josephscott XML-RPC normal normal Future Release defect (bug) new has-patch 2010-03-04T22:00:03Z 2010-03-07T10:10:18Z "At least one XML-RPC client (MaStory on Maemo) does not set the type parameter on uploaded objects. This means we don't create appropriate thumbnails correctly. Given some clients are on fairly low-power, simple devices, it's probably worth Wordpress attempting to determine the mime-type, especially as functions calls we /already/ make on attachments will give us that information already for the common-case of image uploads." jonquark 17981 XML-RPC wp.getComments should work for non-admins XML-RPC 3.2 normal normal Awaiting Review defect (bug) new commit 2011-07-04T22:23:03Z 2012-03-08T13:35:11Z "Right now, if the caller doesn't have the moderate_comments permission, the XML-RPC call returns a 401 error. A more graceful alternative would be to return the approved comments. The user may not be able to moderate, but still should be able to read/reply" koke 21292 XML-RPC: wp_upload_bits should act like wp_handle_upload westi XML-RPC 3.0 normal normal Future Release defect (bug) assigned has-patch 2012-07-17T07:01:23Z 2013-05-07T11:37:28Z "At this moment there isn't a check for file size when uploading an image through the XML-RPC. The reason is that the method wp_upload_bits is used. This only checks it does is if the file size is to big for a network installation. The function check_upload_size() is something what you want except that it will use wp_die() if there is an error like this. The function is used as a filter: wp_handle_upload_prefilter. Which only get applied in the function wp_handle_upload. We should probably change check_upload_size() a bit so it doesn't use wp_die() but does it somewhere else. related: #6559 and #21085" markoheijnen 18681 XMLRPC wp.getPageList and auto-draft pages broken dates XML-RPC 3.2.1 normal major Awaiting Review defect (bug) new has-patch 2011-09-16T08:18:20Z 2011-09-16T09:41:26Z "XMLRPC wp.getPageList method returns all pages, including auto-draft ones. auto-draft pages have post_date_gmt date as '0000-00-00 00:00:00', resulting in invalid dates in XMLRPC reply. {{{ date_created_gmt -0001113TT0::0::00 }}} Remove auto-drafts from wp.getPageList method or fix post_date_gmt somehow." skithund 17382 XMLRPC wp_getUsersBlogs Scalability XML-RPC 3.0.1 normal normal Awaiting Review defect (bug) new 2011-05-11T20:32:15Z 2012-05-13T16:16:46Z "If there is a root blog with many sub blogs on it and a user that is an admin on each sub blog, then when the when the XML RPC method wp_getUsersBlogs() is called it does not scale very well. My PHP memory_limit setting was 128MB, and the XML RPC request died when a user was a member of 230+ blogs. I noticed that the number of queries made to the database for a single user that has many blogs that they are an admin is very high. Affected line: http://core.trac.wordpress.org/browser/tags/3.0.1/xmlrpc.php#L443 I don't know exactly how the code would have to change so I am not providing a patch." bmorneau 15072 blogger.getRecentPosts drops backslashes XML-RPC 3.1 normal normal Future Release defect (bug) new has-patch 2010-10-08T16:25:05Z 2011-01-13T09:08:01Z "I have posts on my site containing fragments like: {{{ [latex]\neg r(a,b)[/latex] }}} But when I pull them down using emacs weblogger-mode, the backslash is always missing. I edebug'ed way down into the bowels of the code and looked at the raw data arriving in the process buffer, and it was missing the backslash, so I'm pretty certain this is a WP bug and not something in emacs or weblogger-mode. Weblogger-mode is using the blogger API. I tried several other clients, and they seemed to work, but I assume they're using a different protocol (e.g. atom)." daveabrahams 18998 date/time handling in xml-rpc assumes GMT value XML-RPC 3.2.1 normal normal Awaiting Review defect (bug) new 2011-10-19T08:09:16Z 2012-01-04T17:43:57Z "When trying to set post publication times via XML-RPC I noticed that the dateCreated value was assumed to be GMT. one section of code: {{{ // Do some timestamp voodoo if ( !empty( $content_struct['date_created_gmt'] ) ) $dateCreated = str_replace( 'Z', '', $content_struct['date_created_gmt']->getIso() ) . 'Z'; // We know this is supposed to be GMT, so we're going to slap that Z on there by force elseif ( !empty( $content_struct['dateCreated']) ) $dateCreated = $content_struct['dateCreated']->getIso(); if ( !empty( $dateCreated ) ) { $post_date = get_date_from_gmt(iso8601_to_datetime($dateCreated)); $post_date_gmt = iso8601_to_datetime($dateCreated, 'GMT'); } else { $post_date = current_time('mysql'); $post_date_gmt = current_time('mysql', 1); } }}} in the following part: {{{ if ( !empty( $dateCreated ) ) { $post_date = get_date_from_gmt(iso8601_to_datetime($dateCreated)); $post_date_gmt = iso8601_to_datetime($dateCreated, 'GMT'); } else { }}} $post_date is set to GMT (get_date_from_gmt()) value of $dateCreated (assuming it's GMT) and then $post_date_gmt is set to GMT ... this forces both values to be identical and assumed to be GMT. this also breaks the ability to set the timezone in the value of dateCreated even though the ISO8061 spec allows it. I've attached a patch to class-wp-xmlrpc-server.php which appears to fix this problem and allows future published posts to publish properly at the expected date/time. to duplicate, use an XML-RPC client (I'm using a Perl script) to add a new post and set the dateCreated to a dateTime.iso8061 entity with the value of '20111019T19:05:00+0900' (or something equivlent for your timezone which would be easy to identify as an incorrect value if so.) the publish date of the new post will be the GMT value. A workaround would be to do all the GMT conversion in the client prior to sending via XML-RPC, but that would make it seem that dateCreated and date_created_gmt will always be duplicate. I've included a patch in case this wasn't an intentional design decision. " alien8 3052 pingback_ping() function displays wrong content in pingback-display in some occurances josephscott XML-RPC 2.0.4 normal normal Future Release defect (bug) reviewing close 2006-08-19T13:41:52Z 2010-04-30T02:29:11Z "If the blog uses a template where the post-meta-data like the trackback-link and such is wrapped in a ""div"" tag but not in a ""p"" tag, the pingback will incorrectly display the content surrounding the meta-data-links, not the content of the pinging post. if there is a ""related posts"" navigation on the page (possible with the [http://www.neato.co.nz/ultimate-tag-warrior/ ultimate-tag-warrior] plugin), or any other links inside the page that link to other posts from the same blog (even the ''next post'', ''previous post'' links), pingbacks will display the content around the first of these links, not the contents around the ""pinging"" link inside the post. '''Possible fix:''' on line 1192 in xmlrpc.php: {{{$linea = preg_replace( “/ < (h1|h2|h3|h4|h5|h6|p|th|td|li|dt|dd|pre|caption|input|textarea|button|body)[^>]*>/”, “\n\n”, $linea );}}} the ""div"" tag is not recognized. changing that to: {{{$linea = preg_replace( “/ < (h1|h2|h3|h4|h5|h6|p|th|td|li|dt|dd|pre|caption|input|textarea|button|body|div)[^>]*>/”, “\n\n”, $linea );}}} fixed the problems for my blog. Frankly I'm not that ""deep"" into regular expressions to fully understand what's going on inside the pingback_ping() function - but after inserting ""div"" to the line above my pingbacks display the correct excerpt of the pinging post, which they failed to do before. " webrocker 17270 strip_tags function in XML RPC needs replacing with regex XML-RPC 3.1 normal normal Awaiting Review defect (bug) new 2011-04-28T16:32:46Z 2011-04-28T16:32:46Z "I've been working on a plugin that works with pingbacks, and I have come across a problem with a line in class-wp-xmlrpc-server.php which uses strip_tags. (line 3422 in WP 3.1): $linea = strip_tags( $linea, '' ); // just keep the tag we need For some reason this function is not working properly at all on some templates (or that is the way it seems) and instead of returning all the tags is cutting a lot of them out, making it seem to the server like there is no target link in the source URI, and thus returning a pingback fault 17 unnecessarily. And this means a large percentage of genuine pingbacks are failing without the user even knowing about it! I suspect the function is having trouble with plugins that insert javascript near the header of the page, though it could be otherwise, as I have done a test to see what is left after this line is run, it returns some garbled javascript, no links at all from the post content (where the source links actually were), and then the menu links. I have included a workaround in my new plugin: http://wordpress.org/extend/plugins/pingchecker/ Basically it does a regex match for links in your content, then echoes them in a hidden div in the footer, making it much easier for the strip_tags function to actually find them. It works pretty well so I'm not fussed myself, but I thought it worth writing about.. This line really needs to be replaced with the regex match in the actual server code for future WordPress users too. I don't know regex myself, but I used sample code I found here (http://regexadvice.com/forums/thread/48395.aspx) for this regex expression, which seems to work really well. In any case, strip_tags is not doing a reliable job at this and needs replacing. Hopefully this finds its way to the right person able to fix this. Thanks!" majick777 23020 wp.getPageList should act like wp.getPages XML-RPC 2.2 normal minor Awaiting Review defect (bug) new has-patch 2012-12-20T13:47:13Z 2012-12-30T15:07:53Z "I know that wp.getPageList is obsolete, but I think it should act like wp.getPages At the moment wp.getPageList returns even the trashed pages and doesn't return the status of the page. The weird behavior i've seen with wp.getPageList on a third-party client is shown below: - Refresh the pages list. - The Page 'A' is in the list. - Select the page 'A' and delete it. - Refresh the pages list and the page is still there. Doh!" daniloercoli 17604 wp.uploadFile overwrite doesn't work XML-RPC 3.2 normal normal Future Release defect (bug) new has-patch 2011-05-29T10:27:21Z 2012-11-08T01:52:09Z "Removing the following lines from the function ''mw_newMediaObject'' file ''class-wp-xmlrpc-server.php'' solves the problem: {{{ $filename = preg_replace('/^wpid\d+-/', '', $name); $name = ""wpid{$old_file->ID}-{$filename}""; }}} Why are these lines there anyway? overwrite is overwrite. This, presumably, bug exists in WP 3.1 too." M66B 20986 xmlrpc.php should return http 405 for get requests (and not 200) XML-RPC normal normal Awaiting Review defect (bug) new has-patch 2012-06-16T06:39:12Z 2012-06-19T17:01:09Z "{{{ $ curl -v http://raphaelhertzog.com/xmlrpc.php [...] > GET /xmlrpc.php HTTP/1.1 < HTTP/1.1 200 OK [...] XML-RPC server accepts POST requests only. }}} The error returned should be reflected in the HTTP return code: it should return HTTP 405 (Method not allowed) instead of 200 (OK). This has been originally reported in the Debian bug tracking system: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598124" rhertzog 5461 Add ability to set description for XML-RPC file uploads XML-RPC 2.3.1 normal normal Future Release enhancement new 2007-12-12T22:36:17Z 2009-06-13T03:01:40Z It's been suggested that we provide a way to populate the description field for file uploads. This is something that we could add to the wp.uploadFile method. josephscott 20026 Adding a post_type filter in wp.getComments westi XML-RPC normal normal Future Release enhancement reviewing needs-unit-tests 2012-02-12T15:48:53Z 2012-08-05T19:45:16Z This will be usefull when with the new custom post type support in XMLRPC nprasath002 10514 Allow plugins to advertise its XML APIs in RSD josephscott XML-RPC normal normal Future Release enhancement new has-patch 2009-07-29T17:02:39Z 2012-06-21T20:53:14Z It will be nice if plugins could advertise its APIs in RSD. sirzooro 5725 Auto-convert Contributor's new post to draft josephscott XML-RPC 2.3.2 normal minor Future Release enhancement new has-patch 2008-01-27T05:04:01Z 2009-11-17T15:17:16Z "Currently, wp-app.php implementation honors client-supplied app:draft element. If a contributor submits a new Atom entry without app:draft element set to 'yes', it rejects the request. [Current Response][[BR]] 401 Unauthorized[[BR]] ""Sorry, you do not have the right to edit/publish new posts."" Imagine when a contributor forgets to set app:draft to 'yes' and submits a new post. By reading the error message, the contributor may mistakenly think that he is not allowed to submit posts at all. A proposed workaround has been submitted as ticket #5723. There is an alternate proposal:[[BR]] rather than rejecting the request, server may ignore client-supplied app:draft element and always treats a contributor's new post as draft. Based on [http://tools.ietf.org/html//rfc5023#section-13.1.1 RFC5023 Section 13.1.1], server may ignore client-supplied app:draft element." toydi 21085 Better XML-RPC media handling XML-RPC 2.3 normal normal Future Release enhancement new dev-feedback 2012-06-26T22:40:22Z 2012-10-10T16:23:23Z "In 3.4 there was a lot of improvements. For 3.5 I would like to see some major improvement in wp.uploadFile and metaWeblog.newMediaObject. At this moment you can't insert a description, alternate text or caption. ( #5461/#18684 ). Also the file can't be attached to a post ( #13917 ). The overwrite functionality also doesn't work ( #17604 ). Not sure why this exists since WordPress itself doesn't do this. Also the current way isn't how WordPress does it internally. wp_handle_upload() doesn't get used (#6559). There is also going on something wrong with mime types ( #12518 ). Also the work from 3.4 should be implemented ( #6430 ). Last thing is that WordPress normally also looks at the EXIF information. At this moment the XML-RPC also doesn't do that ( #18087 ) rarely related: #12493 - filter for wp_upload_bits" markoheijnen 22540 Drilling categories for relevant posts via XML-RPC XML-RPC 3.4.2 normal major Awaiting Review enhancement new 2012-11-22T16:46:52Z 2012-11-23T22:17:25Z "Hello WordPress, Requirement for us was to drill down the category relevant posts, and I have implemented the solution using xmlrpc for the .net env using c#. The trouble is there is no available option to filter using category for the posts. So I have done following changes, please recommend if we can do any better to avoid the override of the change may be by upgrading the next version with it from WordPress version natively. Describing the basic nitty-gritty with in : After doing some cross referencing I was able to figure out adding following code shouldn't harm : 1: With in LLN#1374 function wp_getPosts( $args ) I added the filter option for category as follows on LN#1410 {{{ if ( isset( $filter['category'] ) ) $query['category'] = $filter['category']; }}} I have done few tests and seems to be working fine, just its expects the categoryId to drill the category relevant posts for me. I wonder if you could integrate this from WordPress. 2: Our second requirement was to get out of the box wpautop for the content, so we don't need to worry about adding

tags. hence the another change of code I had integrated with in the file is as following : with in protected function _prepare_post( $post, $fields ) on LN#624 , I had added the wpautop call to surrounds to post_content as in follows : {{{ 'post_content' => wpautop($post['post_content']), }}} Please guide or suggest how to avoid the override when upgrading the WordPress, one option is WordPress integrate these changes out of the box and until that we keep an eye and on ever upgrade keep doing the change. Please feel free to reach me with any possible suggestions. Regards, Nidhi" nidhi.patel 23446 Expose 'login_url' and 'admin_url' via XML-RPC XML-RPC 3.5 normal normal Awaiting Review enhancement new has-patch 2013-02-11T10:41:14Z 2013-04-01T09:28:14Z "To show the preview of 'private'/'draft'/'pending review' posts we need to authenticate to WordPress by using the login form, and the redirect_to parameter. Sometime the URL of the login form cannot be guessed by replacing xmlrpc.php with wp-login.php :) We have the same issue for the URL of the admin dashboard. " daniloercoli 18087 Extend mw_newMediaObject to include EXIF data XML-RPC 3.2 normal minor Awaiting Review enhancement new 2011-07-12T19:24:09Z 2012-06-24T20:42:07Z "Would it be possible to include the exif transfer when using mw_newMediaObject function via XMLRPC? Currently the image gets transfered into library but Title, Caption field remains blank. I checked the uploaded file and it carries the exif, so it does not get striped in the process." MYSTERYouse 12493 Filter $bits in wp_upload_bits() josephscott XML-RPC 3.0 normal normal Future Release enhancement new has-patch 2010-03-03T05:25:51Z 2012-10-18T07:42:35Z "It'd be nice if there was a filter on `$bits` in `wp_upload_bits()` to allow plugins to modify uploads coming in from XML-RPC. Resizing, watermarking, etc. are all example uses for this filter. Since it's a simple filter, perhaps it could be slipped into 3.0." Viper007Bond 21398 Live preview of new post/page via XML-RPC for mobile clients. XML-RPC normal normal Future Release enhancement new 2012-07-27T10:13:47Z 2012-09-16T19:58:49Z "We'd like to have the possibilty to load the 'live preview' for a post/page you're writing on a mobile client. (New post not already ""synched"" with the server, or post edited within the mobile app). The only solution that I can see at the moment is the following: - Upload the post/page to the server with the status set to 'Draft'. - Load the permalink of the post. - Open the post in a webview by using the WP login form and the redirect_to parameter. " daniloercoli 21497 Make uploads on XML-RPC resumable XML-RPC normal minor Awaiting Review enhancement new has-patch 2012-08-06T02:48:56Z 2012-08-06T20:06:06Z In order to play nicely with unreliable internet connections (ie, mobile, conference wifi) it would be nice to be able to resume uploads over the XML-RPC API. pento 22497 Post type should be able to show on mobile apps XML-RPC normal normal Awaiting Review enhancement new has-patch 2012-11-18T18:48:58Z 2012-11-20T11:40:24Z "Currently the mobile apps only show Post and Pages. Part of the reason is that the apps can't know if the post type is worth showing in the apps since it's heavily based on several meta-boxes. I think this is a nice add-on for developers to make that decision. The patch is really simple and is just adding a extra parameter to register post type." markoheijnen 18731 The XML-RPC Endpoint filename is hardcoded in the code (aka: my Host Blocks XML-RPC Access!) XML-RPC 3.2 high major Future Release enhancement new has-patch 2011-09-21T10:56:26Z 2012-12-29T20:48:32Z "It's impossible to rename the file 'xmlrpc.php' to something different (for eg when your hosting provider blocks the access to the xmlrpc.php file) since the prefix ""xmlrpc.php"" is hardcoded within the src code. You can rename the file but the XML-RPC call wp.getUsersBlog always returns the hardcoded URL. Same issue for the pingback link and the EditURI link. We pubblished a plugin that should help users for the time being: http://wordpress.org/extend/plugins/rename-xml-rpc/" daniloercoli 6430 WordPress 2.5 xmlrpc should return image thumbnail URLs in wp.uploadFile jonquark* XML-RPC 2.5 normal normal Future Release enhancement accepted dev-feedback 2008-03-28T05:51:57Z 2012-06-23T19:59:51Z "The xmlrpc call for wp.uploadFile (aliased to mw_newMediaObject) currently returns the URL of the uploaded file only. In WordPress 2.5, thumbnail files are automatically created. The xmlrpc API should provide a way to get the URLs of the thumbnail files, preferably in the returned hash from the wp.uploadFile call. That is, wp.uploadFile currently returns url = ""http://myhost/wp/wp-content/uploads/2008/03/myImage.jpg"". In addition, it should return ""thumbnailSmallUrl = ..."" and ""thumbnailMediumUrl = ..."". (I'm not sure if this would break MetaWeblog compatibility.) Background: WordPress 2.5 now automatically creates thumbnail images for uploaded image files according to the (maximum) sizes specified in the Miscellaneous settings page. When resizing, the aspect ratio is maintained, and the filenames are named for the exact size of the image. For example, if I upload: dsc-0151.jpg Using the default thumbnail settings of 150x150 and 300x300, these files will be created: dsc-0151-300x199.jpg dsc-0151-150x150.jpg Note that the first filename for the medium thumbnail is called ""300x199"" not ""300x300"". It's thus difficult to guess the new thumbnail filename for the default settings. Since these settings are user configurable, it's currently impossible for an xmlrpc client to guess the URLs of the thumbnails. " mlossos 23866 Wordpress xmlrpc wp_getPosts filter for slug XML-RPC 3.4 normal normal Awaiting Review enhancement new dev-feedback 2013-03-26T20:09:31Z 2013-03-26T22:29:43Z "When using the Wordpress xmlrpc, it is sometimes very useful to get posts based off of slugs rather than post id. A use case for this would be synchronizing or migrating two Wordpress sites with the same posts, but with different databases and post ID's. " SunWaves 21386 XML-RPC needs a user permission method XML-RPC normal normal Future Release enhancement new 2012-07-25T18:33:24Z 2012-11-23T20:42:43Z "At this moment when calling a XML-RPC method you will receive a error when the user can't do that method. What would be better if there is a way an app can retrieve the user permissions and act on that without the need to call the method." markoheijnen 5310 XMLRPC interface should expose mechanism for listing and deleting media resources josephscott XML-RPC 2.3.1 normal normal Future Release enhancement new 2007-11-02T21:34:24Z 2009-10-25T10:05:07Z "Right now the XMLRPC interface supports the ""newMediaObject"" mechanism that is part of the MetaWeblog API, but lacks any method for inspecting or otherwise manipulating media objects. I think to support a richer remote client experience, the XLMRPC interface should support at least a method for listing the media objects that have been previously uploaded (similar to what appears in the ""Browse"" tab of the wp-admin post editor), and for deleting a media asset that is present. " redsweater 18684 XMLRPC metaWeblog.newMediaObject doesn't have possibility for setting excerpt/content XML-RPC 3.2.1 normal normal Awaiting Review enhancement new has-patch 2011-09-16T12:10:20Z 2012-09-23T19:30:22Z XMLRPC metaWeblog.newMediaObject method only sets empty content for attachment and doesn't have possibility for setting excerpt and/or content for attachments. skithund 20662 private post can be sticky via quickedit XML-RPC 3.4 normal normal Awaiting Review enhancement new dev-feedback 2012-05-12T08:37:27Z 2012-06-24T22:13:17Z "While preparing translations to 3.4 I came across http://core.trac.wordpress.org/browser/trunk/wp-includes/class-wp-xmlrpc-server.php#L908 This indicates that a private post cannot be marked as sticky. - however it is quite possible to mark a private post as sticky while using quickedit. Solution proposal, remove sticky tickbox on quickedit if post is private. Or if this is only related to the XMLRPC, fix the returnmessage to a warning ""a private post will only be visible to you, so sticky might not make any sense"". I'm thinking.. ""either its possible or its not, the logic should be the same"" " maxemil 23099 Add JSON-RPC support using existing XML-RPC methods XML-RPC 3.5 normal normal Future Release feature request new needs-unit-tests 2013-01-02T01:22:37Z 2013-04-22T21:18:54Z Many people have expressed interest in a JSON API for WordPress core. Until a full REST API can be implemented, the existing XML-RPC method implementations can be re-used by wrapping them in JSON-RPC serialization/de-serialization logic. maxcutler 13835 XLM-RPC API should return commentmeta values josephscott XML-RPC 2.9 low minor Future Release feature request reopened has-patch 2010-06-10T23:28:58Z 2011-03-25T06:55:24Z "This ticket is a follow up on my Twitter and subsequently email conversation with Joseph Scott (josephscott) about the new commentmeta table in WordPress 2.9 and the XML-RPC API. We use the plugin Feature Comments (http://wpprogrammer.com/feature-comments-wordpress-plugin/) for hiding or featuring certain comments. The plugin stores either a value of 'Buried' or 'Featured' in the commentmeta table and uses these values to append a css class to comment_class. I'd love to retrieve these commentmeta values (buried/features) through the XML-RPC API (which we use) with wp.GetComment or wp.GetComments, so we're able to programmatically hide or feature these comments in our own iPhone app. Please note this is a specific example, but my request should I no way be seen as a private request. I think the commentmeta in 2.9 was a great addition for stuff like Twitter usernames, mood, gender, and so forth. I hope we're able to retrieve these values programmaticaly through the API as well." djr 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 21293 Add bbPress as a flavor option to WordPress Showcase WordPress.org site normal normal WordPress.org defect (bug) new 2012-07-17T08:29:13Z 2012-07-17T12:02:44Z "First discussed here: http://bbpress.org/forums/topic/bbpress-content-re-organization/#post-114999 The bbPress 2 plugin is now quite mature and gaining traction. There are some outstanding sites using bbPress 2 well worth showcasing already, such as [http://devpress.com/forums/ devpress.com/forums]. It's high time the WordPress showcase site received a ""bbPress"" flavor to accommodate great looking forum sites." Sadr 19583 Android honeycomb browser gets detected as old version of Safari nacin WordPress.org site 3.3 normal normal WordPress.org defect (bug) reviewing 2011-12-17T01:30:29Z 2013-03-16T16:55:18Z "Reported by a friend of mine (see image attachment). User agent string is: {{{ Mozilla/5.0 (Linux; U; Android 3.2; en-us; A500 Build/HTJ85B) AppleWebKit/534.13 (KHTML, like Gecko) Version/4.0 Safari/534.13 }}} " Viper007Bond 22242 Automatically set the email for the trac account after logging in WordPress.org site normal normal WordPress.org defect (bug) new 2012-10-21T15:51:07Z 2012-10-21T15:51:07Z "The trac installs use the credentials from wordpress.org. However, after you log in, you need to set your email address manually to get notifications from trac. I think we'd have a lot less tickets with 'reporter-feedback' hanging around if the email address was automatically populated after a user first logged into trac." scribu 14622 Be more specific with ideas WordPress.org site normal normal WordPress.org defect (bug) new 2010-08-16T10:46:03Z 2010-08-16T10:54:44Z "In the current ideas section Ideas often get closed for not being core ideas. However, there's not really an explicit indication that the ideas should be for WordPress core. For example, some folk post ideas for WordPress.org (as a site). I realise Ideas is due for overhaul anyway, but in the mean time it'd be good to have just a one-liner in the blurb to explain more specifically the purpose of ""Ideas"". Either that, or add a content section for ideas for ""WordPress.org site"" as we have on here." mrmist 23335 Bizarre sorting while browsing WordPress themes and plugins WordPress.org site normal normal WordPress.org defect (bug) new 2013-01-31T05:01:52Z 2013-04-05T15:21:54Z "Currently, there's some fuzzy logic while sorting plugins and themes. Sorting by popularity seems to be reset I'm guessing on every major WP version update, which I guess is fair, in which case the problem is just missing the proper description of the sort option. However, while sorting by rating, nothing really makes sense of the bizarre sort order there. ( [http://wordpress.org/extend/themes/browse/top-rated Top Rated Themes] ) Even while searching for a keyword, and sorting by ""rating,"" the [http://wordpress.org/extend/plugins/search.php?q=slideshow&sort=top-rated bizarre sorting ensues]. WordPress.org should be a shining example of what WordPress can do, and nail it. " ericlewis 22506 Bogus Last-Modified Header on Forum Feeds WordPress.org site normal major WordPress.org defect (bug) new 2012-11-19T15:45:46Z 2012-11-19T15:59:19Z "In troubleshooting RSS problems, I found that all of the plugin support feeds are responding with {{{ Last-Modified: Tue, 16 Oct 2012 14:09:51 GMT }}}" miqrogroove 18281 Browse Happy API detection bugs WordPress.org site normal normal WordPress.org defect (bug) new has-patch 2011-07-28T14:26:52Z 2012-09-28T16:03:01Z "A few bugs we've noticed with the Browse Happy API so far: 1. Mobile versions need to be labeled as such. Specifically, Mobile Safari, Opera Mini, and the Galaxy tablet, I believe. This should mean that the browser doesn't match with our list of five. 2. For IE, we need to be looking at the Trident version numbers. Problem is, IE9 might be using a compatibility UA, which means it would get identified as IE7. Trident/5.0 is IE9, Trident/4.0 is using IE8. I think the architecture of the API code needs some love. It served its purpose, but it's a bit inflexible for expansion. (See the Kindle hack and such.) I'm going to open source this code onto http://code.svn.wordpress.org. It would be fantastic if some people can contribute to it and make it the best possible." nacin 22523 Can't Open Menu on iPad WordPress.org site normal normal WordPress.org defect (bug) reopened 2012-11-21T09:34:49Z 2012-11-21T11:59:47Z "To reproduce: 1. Go to http://make.wordpress.org/core/ 1. Click ""Get Involved"" What Should Happen: Menu should open. What it Does: Reloads current page. Found in Safari iOS 6.0.1" miqrogroove 17595 Cannot subscribe by email to some tags on wp.org Otto42 WordPress.org site normal normal WordPress.org defect (bug) assigned 2011-05-28T04:34:29Z 2011-05-28T05:24:18Z "To reproduce: - Visit http://wordpress.org/tags/disable-comments when logged in - Click on ""Subscribe to Emails for this Tag"" After reload the link should now read ""Unubscribe to Emails for this Tag"", but it hasn't changed, and the user does not receive emails. The problem appears to be when people use tags that include a space, i.e., ""disable comments"". " solarissmoke 17487 Codepage issue with the wp.org Credits API westi* WordPress.org site normal normal WordPress.org defect (bug) accepted 2011-05-18T10:28:47Z 2012-11-22T03:34:06Z "I was playing with my profile page at wp.org and changed the Name field from: {{{demetris}}} to: {{{demetris (Δημήτρης Κίκιζας)}}} What the API returns for that is: {{{demetris (???????? ???????)}}} It seems the API returns its results in ISO 8859-1. Can we change that to UTF-8? " demetris 20041 "Disable ""Priority"" and ""Severity"" fields for new users" WordPress.org site normal normal WordPress.org defect (bug) new 2012-02-14T13:04:53Z 2012-02-18T19:14:30Z "When a new user comes to report an issue in trac, they always seem to overestimate the severity of their problem. I guess this is normal human psychology, but it makes the field less useful for everyone else. So, I propose that only bug gardeners be allowed to set these fields, similar to how the milestone field works." scribu 21035 Encoding problem on my profile page? WordPress.org site normal normal WordPress.org defect (bug) new 2012-06-21T12:30:42Z 2012-08-10T18:18:31Z "Please see my profile page: http://profiles.wordpress.org/pavelevap. I made several plugins with non-English names. And these names are broken on profile page..." pavelevap 22450 Extend Theme previews doesn't stay on same theme when using IE10 or IE9 in Windows 8 WordPress.org site normal normal WordPress.org defect (bug) new 2012-11-14T19:29:29Z 2012-11-18T15:19:19Z "Originally reported in the forums: http://wordpress.org/support/topic/theme-twenty-twelve-single-post-preview-in-ie10 Extend Theme previews doesn't stay on same theme when using IE10 or IE9 in Windows 8, after clicking from index to a single post view. '''What I expected to happen:'''[[BR]] To continue previewing the same theme when I click around in the preview. '''What actually happened:'''[[BR]] The theme changes to Twenty Eleven after clicking '''To repeat:''' 1. Open http://wordpress.org/extend/themes/twentytwelve 2. Click green Preview button 3. Once in the preview, click into a single post 4. See the theme change to Twenty Eleven Notes: - Breaks in both IE9 and IE10 with Windows 8; does not happen in other browsers like Chrome or Firefox; works fine in IE9 in Windows 7. - Happens with any theme on Extend (tested with Twenty Twelve and Esquire) - Example URL: http://wp-themes.com/twentytwelve?TB_iframe=true&width=1033&height=612 - Loading wp-themes.com directly (not in the lightbox) works as expected" lancewillett 23072 Forums should use title to show a hint about accesskeys for , etc. WordPress.org site normal normal WordPress.org defect (bug) new 2012-12-28T21:56:47Z 2012-12-28T22:02:10Z "WordPress.org forums should use the HTML title="""" attribute to give users a hint that there are keyboard shortcuts that will help their writing process. That hint would be displayed when users hover their mouse over the , and other buttons. Current HTML for the button: {{{ }}} A more user-friendly alternative: {{{ }}}" Daedalon 21793 Incorrect parsing of readme files for plugins on wordpress.org WordPress.org site normal normal WordPress.org defect (bug) new 2012-09-04T22:47:36Z 2012-09-06T23:07:00Z "When wordpress.org parses plugin readme files, it changes URLs in the form www.site.com to links, and adds http:// to the text displayed. That's good and proper. However, it's not helpful when this happens in a code block. For example, see the first and third code block of this readme - http://wordpress.org/extend/plugins/sitepush/installation/ The readme validator shows the same behaviour. The parser should not do any URL parsing in code blocks." markauk 23822 Invalid Plugin Contributors JSON from WP.org Plugin API WordPress.org site normal normal WordPress.org defect (bug) new 2013-03-19T23:41:46Z 2013-03-20T05:39:59Z "Under some rare conditions, some plugins can break the plugin API with invalid JSON, specifically in regards to the list of contributors returned. This is likely because of the string encoding used to either parse or store the values returned from the plugin file headers. Basically though, it results in using a null name for a JSON object member where there absolutely needs to be a string. For example, the ""Aaaaah Lek Lek"" plugin (aaaaaaah-lek-lek) returns the following JSON: {{{ { ""name"": ""Aaaaah Lek Lek"", ""slug"": ""aaaaaaah-lek-lek"", ""version"": ""1.0"", ""author"": ""Valério Souza<\/a>"", ""author_profile"": ""http:\/\/profiles.wordpress.org\/valeriosza"", ""contributors"": { null: """" }, ""requires"": ""3.0.1"", ""tested"": ""3.5.1"", ""compatibility"": [ ], ""rating"": 0, ""num_ratings"": 0, ""downloaded"": 20, ""last_updated"": ""2013-03-12"", ""added"": ""2013-03-12"", ""homepage"": ""http:\/\/valeriosouza.com.br"", ""sections"": { ""description"": ""

Coloque a frase da música LekLek em seu WordPress, dentro do painel administrativo.<\/p>"", ""installation"": ""

Siga para Instalar<\/p>\n\n

    \n
  1. Faça Upload aaaaaaah-lek-lek<\/code> para a pasta \/wp-content\/plugins\/<\/code><\/li>\n
  2. Ative no menu 'Plugins' no seu WordPress<\/li>\n<\/ol>"", ""changelog"": ""

    1.0<\/h4>\n\n
      \n
    • Lançada Versão 1.<\/li>\n<\/ul>"", ""faq"": ""

      What about foo bar?<\/h4>"", ""other_notes"": ""

      Arbitrary section<\/h3>"" }, ""short_description"": ""Coloque o Lek Lek no seu WordPress"", ""download_link"": ""http:\/\/downloads.wordpress.org\/plugin\/aaaaaaah-lek-lek.zip"", ""tags"": { ""frases"": ""frases"", ""leklek"": ""leklek"" } } }}} JSONLint comes back with: {{{ Parse error on line 7: ...ibutors"": { null: """" }, ----------------------^ Expecting 'STRING', '}' }}} These plugin details come from these files: * http://plugins.svn.wordpress.org/aaaaaaah-lek-lek/trunk/readme.txt * http://plugins.svn.wordpress.org/aaaaaaah-lek-lek/trunk/leklek.php (it mentions a stable tag, but there are no actual tags) You might also notice that Extend is unable to display these details correctly either: http://wordpress.org/extend/plugins/aaaaaaah-lek-lek/" bpetty 17138 Link to plugin URI on plugins on wordpress.org WordPress.org site normal minor WordPress.org defect (bug) new 2011-04-15T04:44:10Z 2011-08-17T23:23:49Z "The link to the Plugin URI seems to have disappeared from plugin pages on the WordPress Plugin Directory. The donations link still appears (when present). Be nice to get it back." johnbillion 22811 Make WordPress.org's links use http or https by auto-detection WordPress.org site normal normal WordPress.org defect (bug) new 2012-12-07T15:27:04Z 2013-04-15T15:34:43Z "WordPress.org's links are hardcoded to use the http protocol despite the pages also being viewable using https (which is great). This causes unwanted hassle with eg. bookmarks, showing which pages were or were not visited and so forth. An example of the steps to reproduce: 1. Go to a https URL (eg. https://wordpress.org/extend/plugins/search.php?q= with the search string appended after the ""="", this being the only way to search on WordPress.org via https as all the forms redirect to http). 2. Type anything in any of the search forms. -> A warning is shown that you're being redirected to an unencrypted page. OR 3. Go to a https URL (eg. https://wordpress.org/extend/plugins/types/ ). 4. Bookmark the page. Imagine a few months happening before the next step. 5. Click the Description tab (when browsing normally you'd click another tab in between but it's not a necessary step here). 6. You're now on a page that you haven't bookmarked. Bookmark it, because you like this page and don't remember having bookmarked a rather identical page months ago. 7. You end up having multiple bookmarks for the same pages. The fix for all these is rather easy on paper: have all links on wordpress.org that point to wordpress.org automatically use the protocol used for loading the page currently being viewed. Start with having forms' targets use this, then navigational links, and later consider either auto-converting links in page contents (eg. plugin descriptions) or mentioning the possibility of using `://` links for this next to editors." Daedalon 23379 Make it possible to update localization files through subversion again, or provide a standalone mo/po file download WordPress.org site normal normal WordPress.org defect (bug) new 2013-02-04T04:57:40Z 2013-02-04T08:38:15Z "Hi, I wrote a script here a couple years ago to update the core WordPress application through subversion, coz I am tired of tracking my own modifications (if there is any) https://github.com/timdream/wp-script However, starting v3.3.1, I am not be able to update mo/po files through wordpress-i18n svn repo. According to the localization site here https://tw.wordpress.org/, I would have to export the files through GlotPress myself. That leave me two choices with my script: 1. Hack my way through GlotPress, curl the GET requests to download the l10n files. The script would have to figure out 3.5.1 comes from 3.5.x first, and zh_TW -> zh-tw. 2. Download http://tw.wordpress.org/latest-zh_TW.tar.gz, extract and discard everything except the language directory. Neither approach is optimal. So I would like to propose some possible approaches here: A. Export the po/mo files back to subversion. I think this must have been discussed somewhere with people against it. B. Provide latest-zh_TW-language.tar.gz package. I am not aware of whether (B) is already exist or not, nor I am aware of where the packaging script is being maintained. If the script is somewhere publicly available through subversion, I am more than happy to provide a patch to it. Until then, I would probably need to find some time to implement (1) in shell script :-/ Thank you for reading the bug report. " timdream 22525 Marking duplicates on Trac without a ticket number improperly resolves the ticket nacin WordPress.org site normal normal WordPress.org defect (bug) assigned 2012-11-21T11:38:50Z 2012-12-02T16:39:39Z For some reason, the last ticket I submitted closed itself when I tried to reply to it. Looking for a Trac bug now. miqrogroove 23256 Mitigate Plugins SVN Exponential Storage Growth WordPress.org site normal major WordPress.org defect (bug) new 2013-01-21T23:41:56Z 2013-02-03T21:02:40Z "We all know Subversion is terribly inefficient with storage compared to most modern version control systems, however I've noticed a pretty serious problem that goes way beyond this in the plugins SVN repo. Please forgive me if some details are slightly off as obviously anything running WP.org infrastructure is mostly a black box that no-one outside of Automattic or Audrey has any insight into (and I'm lucky to have found this problem in the first place). If you take a look at the attached graph, you can see that the plugins repository is growing exponentially by disk usage regardless of what rate commits are coming in (but that has always been growing too, making this worse). I am assuming the repository is using FSFS, though this is actually still a problem if it were using BDB. All SVN repositories suffer from this weakness if used the same way the plugins SVN repo is being used. The problem is that every SVN commit stores off node IDs of every sibling node of every parent node of all nodes that have changed in that revision. This means that a single commit to `/myplugin/trunk/readme.txt` contains references to all files and directories (and their related revision) in the `/myplugin/trunk` directory, the references to the `branches`, `tags`, and `trunk` nodes in `/myplugin`, and finally references to every directory in the root node (`/`) which means every single plugin in the repository. Since the root node is related to any changed node in every single commit, and the list of plugins is constantly growing, this means that even though the repository is somewhere around 450GB right now, the actual data in the repo, including the full history, is only about 30GB. You can confirm with a simple dump of the repository. The other 420GB or so is entirely wasted space by SVN overhead. If nothing is done in the next two years, the SVN repository is expected to double in size to about 900GB, and it’s performance will quickly degrade as the server takes longer to read revisions and the filesystem cache can no longer be used (which I suspect is already the case now). Another four years, and we could be looking at a 2TB Subversion repository with every single commit being required to write about 8MB to disk even if it's a one line change. I know that any solution to this is going to take years to fully implement mostly because I believe this is going to require plugin SVN URLs to change during a migration at some point most likely. However, at the least, we should be heading up this problem by getting new plugin submissions started in their own repository rather than creating new directories for them in the current plugins SVN repo. This would at least stop the exponential growth of the plugins repository, extending it's lifespan significantly." bpetty 23712 My browser is NOT out of date WordPress.org site normal minor WordPress.org defect (bug) new 2013-03-07T15:42:29Z 2013-03-09T23:36:13Z "Hello. I'm running Win7 64bit with Firefox 19.0. When I log in my wordpress site admin panel an orange box pops up saying I should update my browser. The operating system and the browser are completely updated." assenoff 16524 No documentation (not possible?) to add plugins to Trac WordPress.org site normal normal WordPress.org defect (bug) new 2011-02-10T19:58:05Z 2012-09-13T20:21:30Z "When developing a plugin, it's normal to set up a bug-tracker of some sort. I have found no documentation on how to do this using THIS bug tracker: trac. I've noticed that SOME plugins have support here, but nobody I've talked to knows how to get their custom plugins added to this bug tracker, which means that most of the plugins in the repository have no official bug tracking in place. That's a huge disservice to the community because only a fraction of those developers have the wherewithal to set up their own bug trackers. This ticket is to request: 1. Access to trac for all plugin developers 2. Thorough documentation on how to get this set up for any new plugin authored 3. Ideally, incorporate this in a standardized way for all plugins so the authors don't have to do any extra footwork." fireproofsocks 19635 Non-ASCII chars in user name changed to question marks after sending new plugin request WordPress.org site normal normal WordPress.org defect (bug) new 2011-12-21T13:52:47Z 2012-08-10T18:12:55Z "I have just sent request to add new plugin to repository, and found that some chars in my name were changed to question marks: {{{ WordPress Plugins » Requests user-ranks from Daniel Fru?y?ski (sirzooro) [plugin] }}} Should be: {{{ WordPress Plugins » Requests user-ranks from Daniel Frużyński (sirzooro) [plugin] }}}" sirzooro 18231 Opera Mini being reported as out of date nacin WordPress.org site 3.2.1 normal normal WordPress.org defect (bug) assigned 2011-07-24T05:14:23Z 2012-09-28T16:05:28Z "From http://wordpress.org/support/topic/latest-opera-mini-flagged-as-old-version-of-opera?replies=1 I use the latest Opera Mini for Symbian v 6.1.25570 for access to my WordPress.org blogs from my mobile phone. It works well for comment moderation, minor edits to posts and upgrading plugins. Since upgrading to WP 3.2.1 I've been seeing ""It looks like you're using an old version of Opera.."" on my Dashboard. This message is incorrect as I AM running the latest version of Opera Mini. It's only a minor annoyance but it would be nice if it was fixed." Ipstenu 22533 Plugin Rating stars is incorrect WordPress.org site low minor WordPress.org defect (bug) new 2012-11-21T23:04:07Z 2012-11-21T23:27:52Z "The stars rating doesn't reflect the average rating correctly. For example: http://wordpress.org/extend/plugins/automatic-updater/ At the time of reporting, there were 13 ratings: 9*5, 3*4, 1*1, for an average of 4.46, shown correctly in the text as ""4.5 out of 5 stars"". The star rating doesn't seem to be using the same number, however - it should be 89.2% (or 90%, if it uses the rounded up ""4.5"" as the rating), but is showing as 82%." pento 21550 Plugin changelog truncation can break WordPress.org site layout WordPress.org site normal normal WordPress.org defect (bug) new 2012-08-11T16:32:59Z 2012-08-11T16:35:41Z "WordPress.org appears to truncate plugin changelogs after a certain number of characters. However, if the truncation occurs in an inconvenient place -- such as the middle of an HTML tag -- it can cause browser rendering issues in other parts of the page. For example, on the [http://wordpress.org/extend/plugins/seo-ultimate/changelog/ changelog page] for my plugin SEO Ultimate, the plugin page sidebar is currently showing up below the changelog ([http://img405.imageshack.us/img405/7557/brokenchangelogscreen.png screenshot]). This is because the changelog is being truncated in the middle of an
    • tag, apparently leading my browser (Chrome) to fail to recognize a closing tag: {{{ }}} I would suggest that the easiest and perhaps best solution would be simply to stop truncating plugin changelogs. Layout breakage possibilities aside, I would prefer it if my plugin's changelog were not cut off after a certain point." JohnLamansky 23411 Plugin images are sent with wrong Content-Type WordPress.org site normal normal WordPress.org defect (bug) new 2013-02-07T09:26:46Z 2013-02-07T10:01:38Z "Some images are sent with the Content-Type `application/octet-stream`. Example: http://s-plugins.wordpress.org/buddypress/assets/screenshot-1.gif?rev=626668 {{{ HTTP/1.1 200 OK Accept-Ranges: bytes Content-Type: application/octet-stream Date: Thu, 07 Feb 2013 09:18:48 GMT ETag: ""626668//buddypress/assets/screenshot-1.gif"" Last-Modified: Sun, 18 Nov 2012 17:27:41 GMT Server: ECS (fcn/419A) X-Cache: HIT Content-Length: 11248 }}} Linked from http://wordpress.org/extend/plugins/buddypress/screenshots/ Each time I want to load the pure image I get a download dialog in my browser." toscho 22288 Plugin package is old version when upgrading plugin shortly after release WordPress.org site normal normal WordPress.org defect (bug) new 2012-10-26T15:39:49Z 2012-11-14T11:16:13Z "The past few times I have done plugin releases, I have noticed an issue with the wrong plugin package being downloaded. For example, I release a new version of a plugin via SVN. The plugin update appears on .org, and the download link downloads the new version. The update also appears in a WordPress install shortly after (assuming transients are deleted for the fastest way to get the update to show). If I then Upgrade the plugin from the, WordPress install the Upgrader Skin does the usual Downloading Plugin... and the package (zip) that is shown to be downloading is the previous version. Of course, it does download the previous version and again shows an update is available. After about 5-10 minutes this usually fixes it's self. I don't know how the .org side of things work, is it possible that the updated version will show up, but whatever is responsible for getting the latest package is relying on a different cache or something? " joehoyle 17709 RTL for the Support Forum theme on the international sites WordPress.org site normal normal WordPress.org defect (bug) new 2011-06-06T15:57:51Z 2011-09-07T00:06:17Z "The RTL styles for the support forums are incomplete. I don't have access to the original files to make a patch, but these fixes should be all that's needed: {{{ #pages a:after, #pages span:after { content: &quot;\200F&quot;; } #pagebody table.widefat th { text-align: right; } #pagebody ol#thread { list-style: none; } #footer iframe, #footer p { float: left; } #footer h6 { float: right; } }}} " RanYanivHartstein 20179 Redirect visitors from plugin admin URL to plugin URL if user not admin WordPress.org site normal normal WordPress.org defect (bug) new 2012-03-05T17:58:47Z 2012-04-05T18:33:02Z "The WordPress plugin directory features an ""admin/"" path relative to each plugin. If I am logged-in to WordPress.org and associated with the plugin slug I'll see a few helpful links and utilities. If I have no mapped relationship to the plugin I see the plugin homepage. I'd like to redirect visitors to ""extend/plugins/{slug}/admin/"" to ""extend/plugins/{slug}/"" if they do not have an admin relationship to the given plugin. Example: I visit a plugin page either logged out or logged in without any association with the plugin. http://wordpress.org/extend/plugins/akismet/admin/ Response should be a redirect to: http://wordpress.org/extend/plugins/akismet/ Right now the response is the same content as the plugin homepage." niallkennedy 22106 SVN Notify emails don't support UTF-8 WordPress.org site normal minor WordPress.org defect (bug) new 2012-10-05T06:30:42Z 2012-10-05T06:38:07Z "If there are UTF-8 characters in the changelog, they are shown as UTF-8 numerical codes, instead of the appropriate character. For example, see this change: http://plugins.trac.wordpress.org/changeset/608203/automatic-updater Compared to the attached email screenshot." pento 23410 Screenshots behaviour not same between /assets and /tags/xxx WordPress.org site normal normal WordPress.org defect (bug) new 2013-02-07T06:04:23Z 2013-02-17T04:32:27Z "Plugins screenshots have differing behaviour whether stored in /assets or /tags/xxxx folders in plugin SVN repository. * /tags/xxxx => scaled images with links to source images * /assets => scaled images without links Also, when loading a plugin for the first time recently, the screenshots didn't appear until after I added them to the /assets folder. I suspect something has changed there, as I had read that screenshots should fallback to stable tag/trunk folder. Examples: * [http://wordpress.org/extend/plugins/gravity-forms-dps-pxpay/screenshots/ Gravity Forms DPS PxPay] has /assets folder, screenshots don't link * [http://wordpress.org/extend/plugins/gravityforms-eway/screenshots/ Gravity Forms eWAY] has no /assets folder, screenshots link to source images" webaware 22809 Support Pale Moon browser in out-of-date dashboard widget WordPress.org site normal normal WordPress.org defect (bug) new 2012-12-07T14:28:40Z 2012-12-08T12:44:00Z "The ""Your browser is out of date!"" notification in WordPress dashboard is shown erroneusly for Pale Moon users. Pale Moon is the most popular optimized version of Firefox, and its version numbering scheme runs a bit different from the mainstream Firefox. The current version of Pale Moon http://www.palemoon.org/ is 15.3.2, which is just as up-to-date as Firefox 17.0.1. Summary of the issues: 1. The version check should be done against Pale Moon version number instead of Firefox version number. 2. The text and links should refer to update Pale Moon instead of Firefox." Daedalon 19011 Support forum topics with Cyrillic titles cannot be found via Google WordPress.org site normal major WordPress.org defect (bug) new 2011-10-20T02:22:19Z 2011-12-23T04:25:14Z "None of the topics with Cyrillic titles on ru.forums.wordpress.org can be found via Google. Topics with Latin slugs are indexed properly. Same for the other forums in Cyrillic (bg.forums.wordpress.org and sr.forums.wordpress.org). This wasn't a big issue three years ago when there were just a few posts, but now that more and more questions are asked and answered each day, it's hard for users to find previous topics and solutions. [http://lists.automattic.com/pipermail/wp-forums/2011-February/006773.html According to Otto], there's no `robots.txt` or anything else blocking Google from indexing them. This is probably a Google bug, but I've tried to ask on their Help forum, and no one replied. My guess is this has to do with 4th-level domains currently used for localized support forums. In this case, wouldn't it be possible to switch from `ru.forums.wordpress.org` to `ru.wordpress.org/support/`, similarly to English support forums?" SergeyBiryukov 23485 Theme Preview on Extend starts in the middle of the page WordPress.org site normal normal WordPress.org defect (bug) new 2013-02-16T10:39:50Z 2013-03-05T16:02:50Z "The theme preview iframe is positioned at 50% from top, the lower 50% are invisible. Tested in Chrome, Firefox and Opera, all up-to-date. Clicking ''Inspect Element'' in any of these browsers makes the iframe jump to the correct position, so I cannot provide more details, sorry. " toscho 18097 Themes update-check should check parent/child WordPress.org site normal normal WordPress.org defect (bug) new 2011-07-13T10:19:33Z 2011-07-21T02:49:14Z "A child theme by the name of Commune gets served the updates of a parent theme. We should only serve an update to a theme if it's a child or parent, appropriately. For child themes, we should also confirm the parent." nacin 22770 Tweak Browse Happy so it doesn't jump the gun with out-of-date browser messages WordPress.org site normal normal WordPress.org defect (bug) new 2012-12-06T01:28:44Z 2012-12-06T06:44:20Z "Browse Happy is a useful tool for encouraging WordPress users to keep their browsers current. However, sometimes Browse Happy jumps the gun. For instance, on GNU/Linux distributions like Ubuntu, users can choose to install Chromium directly from the repository (as opposed to downloading Chrome from Google's site). Chromium, when installed this way, is kept up to date by the operating system's package management tool, not manually. Users receive notifications from their operating system prompting them to upgrade when new versions of the browser are available. It makes no sense to show a Chromium user a ""your browser is out of date"" message when their browser is, in fact, up to date - as provided by their distribution. Unfortunately, that is what it happening now. Similarly, Microsoft has not yet released Internet Explorer 10 for Windows 7, so it is not appropriate to tell users of IE9 that their browser is out of date. IE10 is available for Windows 7, but only as a release preview - similar to a WordPress release candidate. We wouldn't prompt users to upgrade their production WordPress installations to a release candidate, so why is Browse Happy telling Windows 7 IE users to upgrade to IE10 when the final version of IE10 has yet to be released? Browse Happy should be tweaked so it does not jump the gun with out-of-date browser messages before browsers are really out of date. Users should only get a prompt to upgrade if there is in fact a newer version of their web browser available to them that is out of beta and suitable for production use." avcascade 20615 Unknown error when running plugins_api() with invalid slug WordPress.org site normal normal WordPress.org defect (bug) new 2012-05-05T14:59:07Z 2012-05-05T15:40:35Z "Input: {{{ $api = plugins_api( 'plugin_information', array( 'slug' => 'doesnt-exist' ) ); var_dump( $api ); }}} Expected result: {{{ WP_Error Object ( [errors] => Array ( [invalid_slug] => Array ( [0] => Invalid plugin slug. ) ) [error_data] => Array ( [invalid_slug] => 404; ) ) }}} Actual result: {{{ WP_Error Object ( [errors] => Array ( [plugins_api_failed] => Array ( [0] => An unknown error occurred during the API request. ) ) [error_data] => Array ( [plugins_api_failed] => N; ) ) }}} PS: I have no idea what that 'N' is supposed to represent." scribu 21991 Username input placeholder text cut off WordPress.org site normal normal WordPress.org defect (bug) new 2012-09-25T08:18:21Z 2012-09-25T08:18:21Z "On wordpress.org I'm invited to log in using my ""Username or em""." johnbillion 21542 WP.org notifications don't support UTF-8 WordPress.org site normal normal WordPress.org defect (bug) new 2012-08-10T18:10:09Z 2012-08-10T18:12:51Z See the screenshot. SergeyBiryukov 23989 Wonky download button on plugin support forums WordPress.org site normal normal WordPress.org defect (bug) new 2013-04-08T15:27:57Z 2013-04-08T18:21:06Z "On the 'Support' tab for any plugin in the wordpress.org plugin repo, the Download button is a bit wonky. [[Image(http://i.imgur.com/5gctAEO.png)]]" johnbillion 15366 WordPress Development Blog feed can't redirect WordPress.org site high normal WordPress.org defect (bug) reopened 2010-11-09T21:13:42Z 2011-02-17T22:39:16Z "The RSS feed doesn't know to follow the redirects. We'll need to restore a feed at /development/feed/ -- rewrite instead of redirect." nacin 24005 WordPress.org search field looks broken in Opera WordPress.org site normal minor WordPress.org defect (bug) new 2013-04-09T13:07:58Z 2013-04-09T13:13:08Z This is how it looks in Opera 12.15, Win8, x64 (see attach) seezer 18773 Wordpress codex pass word problems WordPress.org site 3.3 normal normal WordPress.org defect (bug) new 2011-09-25T21:55:07Z 2011-09-26T10:14:38Z "Ok this is the third time I've tried to post this here- I've split the pass word up because I thought that some bit may be preventing this from being posted thinking that I'm revealing sensitive data. I set my pass word to a strong one with brackets, double quotes and a semicolon in it. This worked for the forums and the trac but not for the codex (wouldn't let me in). " volcanicpixels 19432 [SITE] Belguim IP shows only French version? WordPress.org site normal minor WordPress.org defect (bug) new 2011-12-03T10:59:37Z 2011-12-04T10:46:52Z "When a Belgium IP address goes to the English version of the WP.org site I shows that WordPress is also in French. But we have also Dutch & German in this country. So I was thinking: why not display the message as follows: 'click here if you want WordPress in another language' and this takes you to a page where all languages are listed. That way a user that is at holidays in China easily find his French or German version." jonezjea 18981 erroneous pie graph in plugins repository WordPress.org site 3.2.1 normal normal WordPress.org defect (bug) new 2011-10-18T06:43:00Z 2012-06-21T12:26:06Z "In plugins repository of wordpress.org: Since more than a week, pie graph of statistic are erroneous... Only one part, very old version targeted ! What happens ? one example in our seven list and other more : http://wordpress.org/extend/plugins/xili-language/stats/ " michelwppi 17095 format or validate author url from api.wordpress.org WordPress.org site normal normal WordPress.org defect (bug) reopened 2011-04-09T16:44:13Z 2011-04-09T18:04:56Z "The author url from api.wordpress.org does not seem to do full format checking. Not apparent in browsers since they will understand malformed urls but is a problem when outputting elsewhere. Example: {{{ Stanislav Gunčaga]]> }}} " wycks 23958 http://wordpress.org/showcase/ is broken for retina WordPress.org site normal normal WordPress.org defect (bug) new 2013-04-06T12:19:26Z 2013-04-06T12:19:26Z "First time I do see an image but when whole page is loaded the image is ""File not found"". Only Quartz is showing up in the slider." markoheijnen 11905 trac spam ryan WordPress.org site normal normal WordPress.org defect (bug) reopened 2010-01-15T13:05:08Z 2013-04-21T09:15:45Z http://core.trac.wordpress.org/ticket/9534#comment:7 scribu 23034 wordpress-sources is not up to date nacin WordPress.org site normal normal WordPress.org defect (bug) assigned 2012-12-21T08:16:31Z 2013-01-10T06:55:04Z "It would be nice if you could include as part of your standard release workflow a step that ensures that http://code.trac.wordpress.org/browser/wordpress-sources is up-to-date. For instance WP 3.5 ships JQuery 1.8.3 but the above repository only contains the source for version 1.8.1. JQuery UI is at 1.9.2 while the above repository only contains 1.8.23." rhertzog 13576 wordpress.org themes list, sidebar broken in IE7 ryan WordPress.org site normal normal WordPress.org defect (bug) new 2010-05-27T14:49:20Z 2012-08-10T18:25:26Z "wordpress.org themes list the sidebar in IE7/IE8 is displayed AFTER the themes, Firefox ok." maurizio04 22440 "Add ""app"" to the .org intro paragraph." WordPress.org site normal minor WordPress.org enhancement new dev-feedback 2012-11-14T11:26:45Z 2013-03-20T13:58:18Z "I'd like to propose that we change the .org intro paragraph from: {{{ WordPress is web software you can use to create a beautiful website or blog. We like to say that WordPress is both free and priceless at the same time. }}} To: {{{ WordPress is web software you can use to create a beautiful app, website or blog. We like to say that WordPress is both free and priceless at the same time. }}} WordPress is being used to build web apps, see [http://wordpress.tv/2012/08/06/matt-mullenweg-state-of-the-word-2012/ Matt's WPSF 2012 keynote]. I also spoke to @matt about this at WPCS, he seemed to liked the idea." willmot 23704 Add a field onto WordPress.org support forums for plugin version number WordPress.org site normal normal WordPress.org enhancement new 2013-03-06T06:17:31Z 2013-03-14T00:57:15Z "WordPress.org support forums ask the user to specify the version of WordPress they are using. In plugin-specific support forums such as http://wordpress.org/support/plugin/events-manager there should also be a field for the plugin version number. Like the WordPress version number, this should be a dropdown list, for which the values should be available in the WordPress.org database. This way plugin authors don't need to ask the user for that version, which speeds up the resolution of support tickets and saves the plugin authors' time, letting them concentrate more on creating and improving the plugins." Daedalon 12696 Add ordering support to plugins_api() when filtered on tag or search term ryan WordPress.org site normal normal WordPress.org enhancement new 2010-03-24T23:05:09Z 2011-06-07T14:49:00Z "It would be awesome if you could pass an ordering parameter to plugins_api() that would allow you to return a list of filtered plugins in a specific order. I'd love to be able to use the API to return a list of the most popular / newest / recently updated plugins on the repo that contain the tag ""buddypress"". Something like this would be awesome: {{{ $plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'page' => 1, 'order' => 'popular' ); }}} Even better, also allow search filtering: {{{ $plugins = plugins_api( 'query_plugins', array( 'tag' => 'buddypress', 'search' => 'album', 'page' => 1, 'order' => 'popular' ); }}} I'd be happy to implement this if I can get access to the API source on WordPress.org." apeatling 22297 Add support to request topics through the WordPress API WordPress.org site normal normal WordPress.org enhancement new 2012-10-27T20:39:24Z 2012-10-27T20:39:24Z There is a RSS feed for getting the latest topics but that's not really handy since you have no clue what the information is behind it like if the topic has been resolved. What can be handy if you want to have an overview of all the not resolved topics of all your plugins markoheijnen 22416 Add updated time to Plugin API WordPress.org site normal normal WordPress.org enhancement new dev-feedback 2012-11-12T00:21:27Z 2012-11-12T09:50:22Z "This ticket is directed at @Otto42 Per recent discussion (Nov 6), a separate '''last_updated_time''' field should get added to the plugin API. Having a separate field, instead of appending time to the existing ""last_updated"" date, would prevent possible compatibility issues. Example API response: http://api.wordpress.org/plugins/info/1.0/akismet.json" logikal16 24295 Allow ReadMe to support in-document links WordPress.org site normal normal WordPress.org enhancement new 2013-05-09T10:30:34Z 2013-05-11T17:20:35Z "The current Plugin [http://wordpress.org/extend/plugins/about/readme.txt ReadMe files] use MarkDown syntax and over time these can contain a great deal of information for users, for example in the FAQs. The length of these sections sometimes makes finding the part you need a case of trawling through the entire document or searching for words in the browser window and hoping you are using the same vocabulary as the ReadMe author. I think a useful enhancement would be to add the capability to define in-document links to allow for things like a table of contents at the top of the FAQ section. Currently you can create a link in such a table like this: {{{ [FAQ 1](#1) }}} But I cannot find a way to create the linked section later in the document as any HTML, name or id parameters seem to get stripped out. If this is already possible, please can you tell me how to accomplish this and accept my apologies from opening a ticket." MattyRob 21628 Attach image(s) to WordPress.org support topics/replies WordPress.org site normal normal WordPress.org enhancement new 2012-08-18T22:27:29Z 2012-08-19T22:28:27Z The ability to upload images to a support reply or topic would assist in describing issues and solutions. Sure, a user could link to an externally sourced image, however that's another step in the process. ericlewis 23160 Better 404 page for WordPress.org WordPress.org site normal minor WordPress.org enhancement new 2013-01-09T20:10:23Z 2013-01-09T20:13:01Z "Right now, if you get a 404 on wp.org, there isn't really much. example: [http://wordpress.org/howabouta404] I'd suggest at the minimum changing the wording away from 'no posts' to 'no pages', and potentially adding links to commonly accessed areas, such as 'Were you looking for a plugin, theme, blah blah?' In the side bar, there is also a 'Categories' section, that always displays 'No categories', maybe remove that as well?" bradparbs 24145 Confirm page close when writing on WordPress.org forums WordPress.org site normal normal WordPress.org enhancement new 2013-04-20T20:03:15Z 2013-04-20T22:28:18Z "When writing on WordPress.org forums, sometimes long and well thought-out replies are lost due to accidental page closing. This causes countless amounts of work lost within the WordPress community. There should be a confirmation dialog to prevent accidental page closing after user has entered something in the new post form." Daedalon 16779 Ignore capitalization during login WordPress.org site normal minor WordPress.org enhancement new 2011-03-06T21:07:43Z 2011-07-22T09:16:23Z "The login box at wp.org seems to be case sensitive. In my case if I type ""bandonrandon"" it returns with ""user not registered"" but if I type ""BandonRandon"" I am able to login. However, it seems that ""bandonrandon"" is also connected to my account and isn't available for registration. My thoughts on this are to maybe ignore the case of the user when they login to the site. The same can be said for plugins. If my name is ""bandonrandon"" in the plugin readme my gravatar is not shown but if it's ""BandonRandon"" my gravatar is shown. " bandonrandon 20318 Introduce a Usage section to the Plugins API WordPress.org site normal normal WordPress.org enhancement new 2012-03-29T07:05:20Z 2012-03-29T13:25:50Z "I quite often find a need for a 'Usage' section in my plugin's readme file. I usually place this within the 'Installation' section ([http://wordpress.org/extend/plugins/user-switching/installation/ example]), but I've seen other plugins that include full usage instructions in the main description, in the FAQs, or in the 'Other Notes' section. It would be nice if there was a top level readme section for Usage which showed up as a tab on the WordPress.org Plugin Directory." johnbillion 15783 JavaScript Coding Standards koopersmith WordPress.org site normal trivial WordPress.org enhancement assigned 2010-12-12T10:56:05Z 2013-04-11T13:36:22Z "Following up on scribu's and azaozz's comments in #15650, would a JavaScript Coding Standards page on the Codex (equivalent to http://codex.wordpress.org/WordPress_Coding_Standards and http://codex.wordpress.org/CSS_Coding_Standards) be useful? It would not only include the usual code formatting, whitespace, brace position, semi-colon requirements etc, but also clarify on which code patterns are preferable for performance, both for the specific dependency library, and those that will give the smallest file when minified. Another idea might be to introduce a file docblock that outlines which JS library or other file dependencies the current file has. Some references: * http://javascript.crockford.com/code.html * http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml * http://drupal.org/node/172169 " GamajoTech 18682 "Make ""WordPress is also available in..."" string translatable" WordPress.org site normal normal WordPress.org enhancement new 2011-09-16T10:34:02Z 2011-09-16T10:34:02Z "Currently the links to local sites displayed on !WordPress.org for international visitors are partly English, partly translated: !WordPress is also available in Русский.[[BR]] !WordPress support forums are also available in Русский. For better user experience, we should allow l10n teams to translate these strings in Rosetta. Due to different grammatical cases, the language name would probably need a separate context for these links." SergeyBiryukov 22343 Make some better theme preview test data WordPress.org site normal trivial WordPress.org enhancement new 2012-11-02T01:19:46Z 2013-04-06T19:04:22Z "[[http://i.imgur.com/Vdb8y.jpg]] Surely something '''new''' can be done here." wycks 23002 Maybe a little styling? WordPress.org site normal normal WordPress.org enhancement new 2012-12-19T11:25:29Z 2012-12-19T11:49:23Z "Hi, The fields in registration page http://wordpress.org/support/register.php are without style. Maybe a little styling for the fields? Now not are very nice..." j.conti 11898 Pagination For Browse Source in Plugin Trac ryan WordPress.org site normal normal WordPress.org enhancement new 2010-01-14T23:42:38Z 2010-01-15T16:53:59Z "When you view Browse Source in Plugin Trac it lists 7,000 plugins. This take a long time to load and isn't readable. This page needs pagination or something else.[[BR]] [[BR]] Related: http://trac.edgewall.org/ticket/6101[[BR]] [[BR]] This was talked about breifly during the dev meeting on January 14th, 2010: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2010-01-14#m56068" dancole 17917 Profile pages should include activity on local forums as well WordPress.org site 3.2 normal normal WordPress.org enhancement reopened 2011-06-28T07:43:21Z 2012-12-07T10:18:46Z "Since WordPress 3.2 is going to show a link to the profile pages of the various contributors and translators, it seems only fair for that profile page to reflect the activity of those translators on the local forums as well. Currently if you go to my profile page for example http://profiles.wordpress.org/users/DeFries/ you will only see some forum activity on the international forum. Most of my activity is done however on the Dutch Forum ( http://nl.forums.wordpress.org ). Something you can see on the profile page of the Dutch forum itself: http://nl.forums.wordpress.org/profile/defries For starters, it would be a better suit if the first mentioned profile url shows all of the users activity on the forums, but having both reflect the same would be a warm welcome. Having the two merged could even be a better solution. I'll leave that up to you guys." defries 24165 Re-skinning Trac 1.0 WordPress.org site high minor WordPress.org enhancement new 2013-04-23T15:50:47Z 2013-05-17T01:06:13Z "As part of a datacenter migration, Trac was updated to 1.0, which has a new UI featuring rounded corners, gradients, drop shadows; and fieldsets with rounded corners, gradients, and drop shadows. Let's update http://wordpress.org/style/trac/wp-trac.css?2 to replace all of the ugly and to fix some of our custom styling broken with the upgrade. We went from Trac 0.12.4 to 1.0. Here's a diff of the relevant CSS/JS/images: http://trac.edgewall.org/changeset?old_path=%2Ftags%2Ftrac-0.12.4%2Ftrac%2Fhtdocs&old=11784&new_path=%2Ftags%2Ftrac-1.0%2Ftrac%2Fhtdocs&new=11784" nacin 23346 Remove rate limiting for plugin authors on their own support topics WordPress.org site normal normal WordPress.org enhancement new 2013-01-31T18:46:41Z 2013-02-05T01:42:56Z I frequently get the 'slow down' message on the support forums when responding to support threads for my plugin - can the limit not be lifted when posting to topics tagged with a plugin that I am author of. volcanicpixels 18915 Reverse priority colors in Trac WordPress.org site normal normal WordPress.org enhancement new 2011-10-12T12:53:01Z 2012-09-02T17:05:06Z Each ticket on list has assigned color - from red for ones with lowest priority, to blue for ones with highest priority. This is a bit unintuitive, because red color usually means warning or something bad. Please change these colors to follow that common approach. sirzooro 15417 Search by Author on Install Plugins - requires inside knowledge WordPress.org site 3.0.1 normal normal WordPress.org enhancement new 2010-11-13T17:07:49Z 2011-02-19T01:19:08Z "If you search for plugins to install by author - say for example - Justin Tadlock - or - Tadlock - you get no results. If you are aware that ""GreenShady"" is Justin Tadlock - you get a long list of plugins (as you should) all listed as by ""Justin Tadlock"" This seems broken. " transom 22424 Search support threads for a particular theme/plugin WordPress.org site normal major WordPress.org enhancement new 2012-11-12T19:09:45Z 2012-11-12T19:12:55Z "A lot of duplicate support threads for themes/plugins could be avoided if users had a way to search through existing threads only for that particular theme/plugin. For example, when I'm on http://wordpress.org/support/theme/p2 there could be a search box at the top that would only look through those topics." scribu 14087 Set up team to evaluate web-hosting providers for WP.org recommendations WordPress.org site normal normal WordPress.org enhancement new 2010-06-25T13:47:32Z 2010-07-17T14:39:18Z "The problem is simple to describe: When setting up a CMS-based website, two of the most critical—if not the two most critical—decisions are: * publishing platform * web host For the first you can pick at random among the best-known offerings and you won’t go much wrong. (Or you can pick the most popular one, and, in most cases, you will have made the best choice! :-D) But the second is different — or so my little experience tells me: Fame and familiarity do not seem to be directly correlated with quality in the case of shared web-hosting, which is the best type of hosting for the majority of WP users. And that’s unfortunate, because bad web hosting can ruin the experience of web publishing. In addition, evaluting web hosts is not easy for a single individual, even for individuals who have the technical understanding, because it takes time and also money. We, the people involved with WordPress development, are in a better position to offer some insight into the problem: We are many, we have collective knowledge, and also collective experience. So, here is my idea: * Set up a team * Set up a set of criteria * Start evaluating services for a period of two or three months * Publish the final recommendations on the WP.org page (along with the criteria used) What do you think?" demetris 20284 "Show ""Bug Reporting Tips"" when people post in plugin forums" WordPress.org site normal minor WordPress.org enhancement new 2012-03-22T20:49:43Z 2012-03-22T21:25:35Z "The vast majority of forum posts to plugin forums are bug reports, and most are from people who aren't very familiar with what information is required to actually deal with such a report reasonably. I had to laugh when I started opening this ticket, because I am presented with what I'd love to see on wordpress.org! I tweaked it a little to make sense for the situation: -------------- REPORTING BUGS Are you using the latest release of the plugin, or the latest development/trunk version? If neither, please stop here and update first. What steps should be taken to consistently reproduce the problem? In case it's relevant to the issue, what is the expected output? What did you see instead? Does the problem occur even when you deactivate all plugins and use the default theme? Please provide any additional information that you think we'd find useful. (OS and browser for UI defects, server environment for crashes, etc.) " MadtownLems 16880 Suggestion: login links on all pages WordPress.org site normal normal WordPress.org enhancement new 2011-03-17T19:25:47Z 2011-03-18T20:05:47Z "My wife is (finally) getting to work with WordPress at her job. As a relative newcomer to *really* digging into WP, she's hitting on a couple of things that I tend to just gloss over and ignore. One of them was this: She wanted to log in to wordpress.org, but had forgotten her password. She did a password reset, and of course, afterward, she wanted to go back and manually reset her password to something she'd remember. So she went to the main wordpress.org homepage, only to find that there's no login link or any other indication of where one might go to change your password. Of course, *we* know that you can get those links from the Support forum or the Extend area, but for her, it was not immediately obvious. I just thought I'd suggest that the login block should appear on all pages of the site, not just on a few select ones." dougal 17505 Trac is too liberal in sending out e-mail updates on issues WordPress.org site normal normal WordPress.org enhancement new 2011-05-19T09:25:43Z 2011-05-19T14:06:04Z Something relatively minor that's been bugging me for a long time: Commenting on a Trac issue or adding oneself to the CC list should not send an e-mail to that user, or at least not by default. Suppressing such e-mail for self-made changes is the default on other bug reporting systems (e.g. JIRA), and it would be great if we could make it the default for WP Trac as well. sbressler 20002 Update plugins_api to accept multiple slugs when querying 'plugin_information' WordPress.org site normal normal WordPress.org enhancement new 2012-02-09T18:06:35Z 2012-11-14T11:12:07Z "When querying plugins_api() with 'plugin_information', the second argument takes a parameter 'slug' on which to find the plugin. Please may the API be updated to optionally accept an array of slugs, so that you can query for multiple plugins in the same HTTP request? " DJPaul 24066 Version field in Trac's New Ticket form inappropriate for WordPress.org site tickets WordPress.org site normal minor WordPress.org enhancement new 2013-04-12T18:29:32Z 2013-04-14T03:02:55Z "WordPress.org site bugs are not related to WordPress versions. After selecting ""WordPress.org site"" as a component on the Create New Ticket form in Trac, the version field should be either hidden or disabled." Daedalon 18033 WordPress.org Support Forums Mobile Theme WordPress.org site normal normal WordPress.org enhancement new 2011-07-08T05:57:50Z 2011-07-08T13:45:42Z "I mentioned this on Twitter earlier today and Nacin replied that if I coded something up he'd be happy to deploy it. So here is a ticket to discuss the possible mobile theme for the support forums. Theme could be released later on as well with bbPress possibly?" JarretC 16425 automatically search for similar tickets WordPress.org site normal normal WordPress.org enhancement new 2011-01-31T19:47:20Z 2011-02-16T08:18:10Z "I just submitted my first bug report to jQuery today. They use trac too, but they added a couple of things to the ticket creation page which I think would be pretty useful here too: * ~~big red notice: ""Are you in the right place?""~~ * automatically search for similar tickets before pressing submit See http://bugs.jquery.com/newticket" scribu 23764 "Add ""works for this version"" to the plugin review form" WordPress.org site normal normal WordPress.org feature request new 2013-03-14T00:56:30Z 2013-04-04T04:49:05Z "It would be nice if users could select whether a plugin ""works"" for their selected !WordPress version in the plugin review form. Obviously, the main ""Does it work? form"" would stay on the main areas of the plugin page, but this would, I think, help balance the reviews:works stats for many plugins. This would also be related to #23704." DrewAPicture 21387 Add a CodeURI field to plugin file header WordPress.org site normal trivial WordPress.org feature request new 2012-07-25T19:33:28Z 2012-07-25T19:38:48Z "I would like to make it easier for developers not associated with a plugin to contribute modified versions. The plugins SVN has grown to a size where it's no longer possible for a member of the WordPress community to create a new ticket and select a plugin from ""component"" to patch and improve software. Some plugins manage code on a site such as GitHub and commit a release into the plugins SVN. I might use [http://wordpress.org/extend/plugins/wp-super-cache/ WP Super Cache] in my WordPress installation, one of 3.5 million installs using the plugin. I modify the plugin and would like to share my changes. 1. Try creating a [http://plugins.trac.wordpress.org/newticket new ticket in Plugins Trac]. The plugin is not listed as an available component. 1. Find the Plugin URI. If not WordPress.org look around on the author's site for links to another repo. 1. Search GitHub for the developer(s) and/or project 1. Email the developer(s) if they have a contact email listed Give up? File header currently includes a [http://codex.wordpress.org/File_Header#Plugin Plugin URI] which commonly points to the WP.org plugin page for the plugin or sometimes to a webpage on the developer's site. I could overload ""Donate"" to encourage code donations instead of monetary donations but that could be confusing. I'd like to provide a explicit code URI field to encourage outside contributions of modifications in the GPL spirit." niallkennedy 23982 Add array of screenshots to the Plugins API WordPress.org site normal normal WordPress.org feature request new 2013-04-07T20:31:16Z 2013-04-07T20:31:16Z The response to the `plugin_information` method of the Plugins API includes a formatted list (in a `
        ` tag) of the plugin's screenshots. It'd be good if the response also included an element containing a plain array of the screenshot URLs. johnbillion 23981 Add donate link to the Plugins API WordPress.org site normal normal WordPress.org feature request new 2013-04-07T20:28:46Z 2013-04-08T01:29:16Z The response to the `plugin_information' method of the Plugins API doesn't include an element for the donate link. It'd be good to get this in there for completeness. johnbillion 24065 Allow previewing posts in WordPress.org support forums WordPress.org site normal normal WordPress.org feature request new 2013-04-12T18:17:31Z 2013-04-12T20:47:26Z "WordPress allows previewing posts before publishing everywhere else except on WordPress.org support forums. Preview functionality should be added there as well. Ideally the preview would be shown next to the editor so users can spot and correct mistakes without reloading the page, just like when commenting here in Trac." Daedalon 23950 Company recognition WordPress.org site normal minor Awaiting Review feature request new dev-feedback 2013-04-05T15:13:24Z 2013-04-09T17:04:30Z "My company, and many others, have a policy of sponsoring WordPress community contribution, core and otherwise, by strongly encouraging employees to participate during paid company hours. I want to open a discussion on how this company contribution could be recognised, while not allowing ""corporates"" to take over the credits page on each release. * Would greater recognition encourage your company to foster contribution? * Should companies contributing employee time to WordPress, particularly core contributions, be recognised? * How should companies be recognised? * What are the pros and cons for the WordPress project in allowing this kind of recognition? This follows a [https://twitter.com/jenmylo/status/320144575266160640 Twitter conversation] re showing company names in the WordPress credits page, and Nacin's suggestion to open this discussion." simonwheatley 16589 Localized version stats nacin* WordPress.org site normal normal WordPress.org feature request accepted 2011-02-18T08:52:48Z 2012-04-29T15:57:20Z "There have been some discussions on localized version stats: * http://lists.automattic.com/pipermail/wp-polyglots/2009-November/003812.html * http://lists.automattic.com/pipermail/wp-polyglots/2009-December/003868.html * http://lists.automattic.com/pipermail/wp-polyglots/2010-July/004859.html * http://wppolyglots.wordpress.com/2010/12/01/ive-found-some-discussions-about-local-2/ * http://wppolyglots.wordpress.com/2010/08/18/i-am-having-some-problems-with-site-stat/ (related) Many translators would agree that it would be nice to have them back." SergeyBiryukov 23720 Make it obvious that by default support for plugin and themes in the repository is not guaranteed WordPress.org site normal minor WordPress.org feature request new 2013-03-08T07:10:13Z 2013-03-08T15:24:09Z "Or even better, people should assume it doesn't exist. This follows the discussion here http://tommcfarlin.com/upgrade-wordpress/ I know it is possible to add a text to that effect in the readme.txt file, but it is not the same, and you can't expect plugin authors to release new versions just to reflect the change in their available time. Alternatively support policy should have a tab of its own on the plugin's page. In addition, there should be a way to contact someone that will provide paid support for the plugin. By default it should be the plugin's author, but it might be a good idea for other people to be able to provide this kind of service as well." mark-k 12475 Method to prune/leave feedback in Kvetch ryan WordPress.org site normal normal WordPress.org feature request new 2010-03-02T17:12:25Z 2010-03-02T17:12:25Z "I just saw two items about how it would be nice if upgrades were easier and if there was an automatic upgrader, and it got me thinking that there's no way to leave feedback or flag it if you're logged in. It would be nice if there was some way to either leave feedback for when a Kvetch is no longer ""valid"" (for lack of a better term) because something has been implemented to address it, or to flag it for someone else to look at it and decide that it should be removed. This could also be useful if a spam item was displayed, or if an offensive message was left." ninjaWR 22736 Outdated plugins marked as 'Works' for the current version should show in search results WordPress.org site normal normal WordPress.org feature request new 2012-12-04T18:11:57Z 2013-01-06T02:35:09Z "When a plugin hasn't been updated in over 2 years, it gets the ""this is outdated"" message on WP.org and it no longer shows up in plugin search results from the Dashboard. But if the plugin is marked as ""Works"" for the current version - even though it hasn't been updated in 2 years - we should make it so it shows up in search results." DrewAPicture 19884 Unable to sort themes by language WordPress.org site normal major WordPress.org feature request reopened 2012-01-24T13:21:34Z 2012-03-06T19:23:33Z "I can't filter themes by language in themes site. If I want theme in Hebrew (and rtl) I can't search its in the site. So I had to look for it on other websites that may contain malicious code. read: http://n2b.org/archives/2316 (Hebrew)." hatul 12336 WP.org Profiles - Trac Replies are not reported ryan WordPress.org site normal normal WordPress.org feature request new 2010-02-22T19:02:51Z 2010-02-22T19:08:48Z Since WP.org Profiles already has forum post creations and replies, and Trac ticket creations, it makes sense to add the Trac replies as well. archon810 12313 WP.org Profiles should add an RSS feed ryan WordPress.org site normal normal WordPress.org feature request new 2010-02-21T01:01:52Z 2010-02-22T19:09:21Z "I'm not sure where to report feature requests for WP.org Profiles so I'll do it here. Considering the Profiles page http://profiles.wordpress.org/archon810 includes the Trac activity (unlike http://wordpress.org/support/profile/276841 which doesn't, though, it's also useful because it does include replies by others to my favorite topics), it'd be awesome to have an RSS feed for this Profile activity so that it can be used in someone's RSS reader or in my FriendFeed or Lifestream. This may be a BuddyPress request, but since WP.org uses it, I'd say this ticket has merit either way." archon810 11378 "Add ""Remove"" link to Widget instances which moves them to ""Inactive"" area" azaozz Widgets 2.9 low minor Future Release defect (bug) new 2009-12-10T08:53:43Z 2010-03-22T23:21:04Z "Per comments on #10379, we should have a ""Remove"" link on Widget instances that moves them to the inactive area." markjaquith 19945 Bug in ../wp-includes/widgets.php Barti112 Widgets 3.3.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-02-02T08:22:34Z 2012-07-05T14:21:33Z "in this file there are at some places the following code: $widget = array_merge($widget, $options); it is possible that $options is not an array and i become a php-warning. i think better is to check the arrays before you use this function: if(is_array($widget) && is_array($options)){ $widget = array_merge($widget, $options); } " Barti112 23934 Calling sidebar two times, widgets have the same ID Widgets normal normal Awaiting Review defect (bug) new 2013-04-04T14:03:50Z 2013-04-16T00:20:26Z "If we call in the Twenty Thirteen the function of the sidebar {{{ }}} then the widgets ids from each sidebars are the same. " alexvorn2 21061 Can't drag an opened widget to other widget area Widgets 3.4 normal normal Awaiting Review defect (bug) new dev-feedback 2012-06-24T19:43:44Z 2012-06-24T19:43:44Z "the placeholder does not appear and the option to drag the opened widget is not possible, to fix this: to auto-close the widget before drag event (sortable) or add option to accept opened widgets http://wpimpact.com/wp-content/uploads/2012/06/Untitled-5.png" alexvorn2 21396 Categories widget reports categories without posts when they have custom posts Widgets 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-27T02:36:46Z 2012-07-27T04:27:26Z "This problem may be related to #14084, but this report is specific to the behaviour of the Categories Widget. - Create a custom post type eg. ""Products"" - Create a category eg. ""Photographs"" - Add some posts of type Products, assign them to category Photographs - go to the blog page and the Categories widget lists Photographs as a category - click on Photographs - the ""Nothing Found"" post is shown. There are no normal posts of category Photographs, but the widget lists a category that returns nothing. I would have expected the widget not to list a category that has no normal posts. " pkwooster 12722 Concurrent editing of widgets azaozz Widgets normal normal Future Release defect (bug) new has-patch 2010-03-26T18:07:46Z 2013-04-25T05:39:22Z When two admin users edit widgets at the same time which ever one saves last wins. I think we'd need something like the post edit lock to be able warn users when someone else is already editing widgets. josephscott 21046 "Dashboard ""Right Now"" widget hook should be right_now_end, not rightnow_end" Widgets 3.4 normal minor Awaiting Review defect (bug) new 2012-06-22T07:35:20Z 2012-06-22T07:35:20Z "In /wp-admin/includes/dashboard.php , the following callback is used: {{{ do_action( 'rightnow_end' ); }}} However, [http://codex.wordpress.org/Plugin_API/Action_Reference#Dashboard_.22Right_Now.22_Widget_Actions the documentation] and logic (for consistency with `right_now_content_table_end`, `right_now_table_end`, etc) would tell us that the hook should actually be called `right_now_end`." schreifels 21287 Fix Widgets Helper position on start event - sortable Widgets 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-16T09:33:24Z 2012-12-13T12:31:33Z "the widget helper moves (jumpes) to the left, to the parent left position... in Firefox this is not a bug but in chrome it does. please take a look in the screenshot, the helper jumped to the left.... http://wpimpact.com/wp-content/uploads/2012/07/Untitled-2.png I tried to use the : {{{ ui.helper.css('left', ui.placeholder.position().left) }}} code but chrome does not set a placeholder position, I don't know why, maybe a chrome bug or in jQuery. " alexvorn2 11160 Inconsistancies in Naming and Using Sidebar Names and IDs. azaozz Widgets 2.9 normal normal Future Release defect (bug) new needs-unit-tests 2009-11-17T12:58:55Z 2012-11-22T03:18:21Z "register_sidebar() allows more sidebar names and IDs to be registered than dynamic_sidebar() recognizes as valid names and IDs. For example, register_sidebar() allows me to name a side bar ""1"" with a id of ""first"". I don't know why anyone would choose those values, but register_sidebar() allows it [1]. {{{ register_sidebar( array('name' => 1, id => 'first') ); }}} dynamic_sidebar() will not be able to find the sidebar given its name (1). {{{ if ( is_int($index) ) { $index = ""sidebar-$index""; /// 1 becomes 'sidebar-1' ... }}} The main problem is that dynamic_sidebar() is trying to process both IDs and names through the same variable ($index) while register_sidebar() separates the two with an array ( array('name' => 'Top', 'id' => 'sidebar-1' ). According to the in-line docs for dynamic_sidebar(): It is confusing for the $index parameter, but just know that it should just work. When you register the sidebar in the theme, you will use the same name for this function or ""Pay no heed to the man behind the curtain."" Just accept it as an oddity of WordPress sidebar register and display. It does ""just work"" if you never use your own sidebar IDs. I started looking at this because I wanted to use is_active_sidebar() which tests to see if a dynamic_sidebar() has anything in it. There is no get_dynamic_sidebar(). dynamic_sidebar() sends everything to the browser or returns false. {{{ register_sidebar( array('name' => 'Top') ); // id defaults to ""sidebar-1"" ... if ( is_active_sidebar('Top') ) dynamic_sidebar('Top'); }}} Which fails because is_active_sidebar() just completely skips over searching for an id to go with a name. To get it to work you need to know when it was registered. Not something theme authors and designers are going to follow easily. There's a ticket to fix this: [http://core.trac.wordpress.org/ticket/10440 #10440] {{{ if ( is_active_sidebar(1) ) dynamic_sidebar('Top'); }}} Like dynamic_sidebar(), is_active_sidebar() converts 1 to ""sidebar-1"". Unlike dynamic_sidebar() it assumes everything is entered as an id. unregister_sidebar() assumes its parameter (incorrectly named $name, not $id) is an id. But it wants a literal id, like ""sidebar-1"". unregister_sidebar(1) unregisters a sidebar with an id of 1, while dynamic_sidebar(1) tries to display a sidebar with an id of ""sidebar-1"". === Widgets (Admin Page) === The dynamic_sidebar() function is used by the Widgets management page. So, it is possible to create a sidebar with register_sidebar() that dynamic_sidebar() cannot find. You can populate it with drag and drop [2] and not have it appear on the web site. == After Patch == If committed, this patch would remove the need for tickets [http://core.trac.wordpress.org/ticket/10440 #10440] and [http://core.trac.wordpress.org/ticket/10956 #10956]. It changes the current argument behavior of unregister_sidebar(), but doesn't break backward compatibility. It allows is_active_sidebar(), unregister_sidebar() and dynamic_sidebar() all point to the same sidebar. === Before === These all refer to the same sidebar: {{{ is_active_sidebar(1); unregister_sidebar('sidebar-1'); dynamic_sidebar('Sidebar Top'); }}} In an admittedly contrived case, dynamic_sidebar() would silently fail to allow this sidebar to show: {{{ register_sidebar( array('name'=>'Sidebar Top', 'id' => 1) ); }}} === After === These all refer to the same sidebar (the first two would have broken before the patch): {{{ is_active_sidebar('Sidebar Top'); unregister_sidebar('Sidebar Top'); dynamic_sidebar('Sidebar Top'); }}} After the patch this shows fine: {{{ register_sidebar( array('name'=>'Sidebar Top', 'id' => 1) ); }}} After the patch it is possible to force an argument to be only a name or only an id: {{{ is_active_sidebar(array( 'name' => 'Sidebar Top' )); unregister_sidebar(array( 'name' => 'Sidebar Top' )); dynamic_sidebar(array( 'id' => 1 )); }}} === Notes === [1] register_sidebar() allows the user to override the default setting of: 'id' => ""sidebar-$i"", [2] When you refresh the Widgets management page the widgets will disappear from the sidebar. They are still attached to a sidebar, but dynamic_sidebar() cannot see the sidebar." CharlesClarkson 19309 Instantiating any widget with checkboxes defaulted on don't transfer as checked only in IE9. Widgets 3.2.1 normal minor Awaiting Review defect (bug) new 2011-11-21T02:26:30Z 2011-12-14T19:47:57Z "In the Links widget, the first two checkboxes are checked by default if using IE8, FireFox or Webkit. If you use IE9, the first two checkboxes will not be checked after you drop the fresh widget instance into a widgetized region of the template or the inactive widgets region. This appears to be an incompatibility between IE9 and a JS library used for copying the data. I do see the proper checked=""checked"" parameter in the source code of the primary instance and all saved instances. It just doesn't instantiate that parameter in the drag and drop action. A community plugin we developed also exposes this IE9 / JS library bug: http://wordpress.org/extend/plugins/becounted/ I found a developer discussion and possible fix related to a non WP application here: https://github.com/SteveSanderson/knockout/issues/89 Thank you!" beautomated 20770 Introduce AJAX response message Widgets 3.4 normal minor Awaiting Review defect (bug) new has-patch 2012-05-29T02:34:09Z 2012-07-05T23:45:10Z "when clicking on Save button of a widget, a error should appear if the user is logged out. So after clicking the button the wpspin animated images disappears and nothing happens. This can be a problem if the current user think he is logged in and he is not, the settings just will not be saved. Sometimes the server is not working. Need to adjust the javascript code and php: in php we can use die function : die('1') or die('success'); in javascript something like this: {{{ $.post(ajaxurl, data, function(response){ if (response === 'success') {} else { alert('Fail to save'); } }); }}} http://wpimpact.com/wp-content/uploads/2012/05/Untitled-4.png " alexvorn2 22253 Keep widget areas (and widgets) expanded upon page refresh in admin Widgets 3.4.2 normal normal Awaiting Review defect (bug) new 2012-10-22T11:02:10Z 2012-10-22T11:02:10Z "This is a minor annoyance but noticeable one. Every time you reload the Appearance -> Widgets admin page, the widget areas (and widgets) currently expanded become closed when the page is refreshed." dgwyer 8910 Limit the RSS widget from using its own url Widgets 2.8 high major Future Release defect (bug) reopened 2009-01-21T19:40:59Z 2012-02-06T08:15:20Z "'''NOTE:''' Copied from [http://trac.mu.wordpress.org/ticket/852] since 'This is really a WP issue, not strictly MU. Can you open a ticket in WP's trac?' I admit that this is not a well conceived thought but I wanted to throw it out. There's some discussion on the premium site about individual blogs using their rss widgets to display their own feeds. This of course causes issues with an unnecessary rss feed pull as well as old data since the feeds are cached. May I suggest a check to see if the inputted RSS feed matches the individual blog's own rss feed, kick it out with an error and suggesting to the user that they use the Latest Posts widget instead? Marking this as 2.8 as it's not a high priority. " webmaestro 19695 Links widget does not generate width or height attributes when showing an image Widgets 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2011-12-30T07:10:48Z 2011-12-31T07:41:57Z "It's a best practice to include width and height attributes in image tags to prevent reflows when the browser renders the page. Both PageSpeed and YSlow include rules that measure this. {{{_walk_bookmarks()}}} in {{{/wp-includes/bookmark-template.php}}} does support adding images to the output of the Links widget. However, it doesn't output the width or height attributes. It is possible to size images with CSS instead of by tag attributes (and PageSpeed rules consider this acceptable). But it doesn't seem ideal to force users to set dimensions in CSS, when the Link edit page doesn't accept CSS directly. Plus, I think it's best to have all the meta info about something in one place, not to set an image in a WP link, and then the dimensions in a theme's CSS file." mbijon 12342 New widget option after calling register_widget creating empty widget azaozz Widgets 2.9.2 normal normal Future Release defect (bug) new dev-feedback 2010-02-23T00:36:39Z 2010-11-13T07:45:48Z "After I register a new widget class that has never been registered before, navigate to the widgets.php admin page and allow the option to be created automatically. The option value looks like this as serialized data: {{{ a:2:{i:2;a:0:{}s:12:""_multiwidget"";i:1;} }}} As you can see there is an empty widget in there for some reason. Basically the unserialized option value looks like the following as an array: {{{ array( '2' => array(), _multiwidget => 1 ); }}} This is odd behavior since the first multi number has always started at 2, but with that previous array in there it starts at 3, and randomly which is what irks me. i can't seem to find when it happens or a pattern, so naturally this feels like a bug. As this does not seem to break anything with the core functionality of WordPress, I would say this is normal priority. What this does do is pose many questions for those of us that dive deep into the Widget API, where our plugins and the functionality of them are dependent on how these things work. My widget plugin is quite large, and I need to know if I can depend on the first multi number of a widget when the class is first registered. If this is not a bug, and normal functionality, I apologize, and would like to ask for a heads up on the subject. Thank You, Jim Isaacs" jimisaacs 22010 RSS Widget with hardcoded icon and style Widgets normal normal Awaiting Review defect (bug) new 2012-09-26T22:13:58Z 2012-09-26T22:13:58Z "Standard RSS Widget outputs hardcoded icon and oldschool inline style=""border:0"" e.g. {{{ }}} this makes it hard to style (even more that the parent anchor has the same css class as following title, so you can't even hide it without some css3 only magic (:first) IMO this part of WP_INC/default-widgets.php row 766-777 {{{ $icon = includes_url('images/rss.png'); if ( $title ) $title = ""RSS $title""; }}} + line 764 should be replaced by standard way e.g. {{{ $title = apply_filters( 'widget_title', empty( $instance['title'] ) ? __( 'RSS' ) : $instance['title'], $instance, $this->id_base ); }}} so when someone wants to output there an icon, he could simply with the widget_title filter" thomask 15060 Removing title on widget doesn't modify in-widget-title span Widgets normal normal Future Release defect (bug) new has-patch 2010-10-07T17:09:22Z 2011-01-13T07:38:41Z "In the widget editor, widgets with titles have this title shown in the widget editor container title. For example: {{{ Text: Sample Widget }}} When a widget is first modified and saved, adding a title will cause this widget editor container title to update via JS to reflect the title update. Subsequent modifications of the title will also be reflected. However, if the title is removed, the previous title will remain. Looking at the code shows that the in-widget-title span that holds this widget editor container title is only updated if the title value is not empty. This is easily tested by adding a Text widget, giving it a title, clicking Save, confirming that the title is reflected in the container, removing the title, and clicking Save again. The supplied patch modifies the JS that handles this process and causes it to always update the in-widget-title span, even when the title entry is empty or missing." chrisbliss18 17453 Some default widgets break XHTML pages Widgets 3.1.2 normal major Awaiting Review defect (bug) new has-patch 2011-05-16T10:47:49Z 2011-05-16T10:47:49Z Some default widgets use HTML named character references, which breaks webpages when served as application/xhtml+xml. peaceablewhale 19846 Specify 'primary' sidebar, so widgets land in correct sidebar when changing themes Widgets 3.3.1 normal normal Awaiting Review defect (bug) new 2012-01-16T21:49:42Z 2012-06-25T19:58:19Z "With the improvements to widget handling in 3.3, the widgets in a previous theme's sidebar are transferred to your current theme's sidebar. But there's no way to specify which sidebar should receive them. For example, when you activate the Genesis theme it has three widget areas: - Header Right - Primary Sidebar - Secondary Sidebar If you install a fresh copy of WP and then activate Genesis, the Header Right widget area is populated with the 6 default widgets ( http://twitpic.com/8618x5 ). It's definitely not ideal for new users unfamiliar with this. It would be great if there were some way to specify a primary sidebar when registering it, and that's the one the default widgets flow into. {{{ register_sidebar( array( 'name' => 'Primary Sidebar', 'id' => 'primary-sidebar', 'primary' => true ); register_sidebar( array( 'name' => 'Secondary Sidebar', 'id' => 'secondary-sidebar' ); // Default: 'primary' => false }}} There might be better ways to handle this, but I think it should be done in WP core. If it's up to the themes to solve, we'll have to use solutions like this: https://gist.github.com/1623202" billerickson 16773 Unescaped preg_match breaks with PHP 5.3 Namespaced Widget Classes. Widgets 3.1 normal minor Awaiting Review defect (bug) new has-patch 2011-03-06T13:31:25Z 2012-11-28T17:05:18Z "In file '''/wp-admin/includes/widgets.php''' at line '''118''' in function '''next_widget_id_number''' we have: {{{ preg_match( '/' . $id_base . '-([0-9]+)$/', $widget_id, $matches ) }}} It generates very ugly warnings ''for Namespaced Widget Classes'' as it should cuorrectly be: {{{ preg_match( '/' . preg_quote($id_base, '/') . '-([0-9]+)$/', $widget_id, $matches ) }}} Thanks. '''PS''': ''I think you should do a whole sanity check regarding use of Namespaces and Closures. I'm currently switching completely to PHP 5.3 style and I'll keep you updated if I find other... problems.''" 5ubliminal 14686 Widget Instance Form Update Bug Widgets 3.0.1 normal normal Future Release defect (bug) new has-patch 2010-08-24T21:13:23Z 2013-04-02T10:57:57Z "Hi. When dragging and dropping a widget into a sidebar the widget form doesn't get properly updated, unless you manually press the ""Save"" button. However the widget instance data is saved (you can see the widget in the frontend even if you don't press 'save'). This problem is noticeable when you're developing a widget and want to display some widget options in the form based on the widget's location or position. You can't do this because '''$widget->id''' or '''$widget->number''' appear to be initialized within the form() function only after you press Save... I can provide the code of a test widget if necessary " digitalnature 18446 Widget removes fields w/ default HTML on initial save in IE8 and 9 Widgets 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-08-16T15:51:02Z 2011-08-17T02:43:18Z "Weird problem, testd in IE8/9, Chrome, and Firefox. If you have a widget, with HTML in the default value, IE8/9 will remove the field entirely. However, if you then paste the HTML back into the field and save, it works fine. This ONLY happens after the initial drag/drop then save of the widget. It even happens if you drag/drop the widget, change the field and click save. Example Plugin: http://wordpress.org/extend/plugins/ft-calendar/ Widget: Upcoming Events Widget The Event Template (event_template) is set by default to: {{{ %TITLE% }}} The event_template source for the Available Widget is: {{{ }}} The event_template source for the widget after it is dragged to a widget area is: {{{ }}} The source for the widget after it is first saved is: {{{ }}} I setup a test to output $new_instance and $old_instance during the ""update"" process. Step 1: Moving widget from Available Widgets to Widget Area (in IE): {{{ NEW INSTANCE: Array ( [title] => [date] => [number_of] => 1 [date_types] => Month [limit] => 0 [timeformat] => g:i a [dateformat] => jS [date_template] => %DATE% [monthformat] => F Y [month_template] => %MONTH% ) OLD INSTANCE: Array ( ) }}} Step 2: Saving widget in Widget Area: {{{ NEW INSTANCE: Array ( [title] => [date] => [number_of] => 1 [date_types] => Month [limit] => 0 [timeformat] => g:i a [dateformat] => jS [date_template] => %DATE% [monthformat] => F Y [month_template] => %MONTH% ) OLD INSTANCE: Array ( [title] => [show_rss_feed] => off [show_ical_feed] => off [date] => [span] => +1 Month [number_of] => 1 [date_types] => Month [calendars] => [limit] => 0 [dateformat] => jS [timeformat] => g:i a [monthformat] => F Y [event_template] => [date_template] => %DATE% [month_template] => %MONTH% [hide_duplicates] => ) }}} Step 3: Pasting HTML code back into Event Template and saving Widget: {{{ NEW INSTANCE: Array ( [title] => [date] => [number_of] => 1 [date_types] => Month [limit] => 0 [timeformat] => g:i a [dateformat] => jS [date_template] => %DATE% [monthformat] => F Y [month_template] => %MONTH% [event_template] => %TITLE% (%TIME%) ) OLD INSTANCE: Array ( [title] => [show_rss_feed] => off [show_ical_feed] => off [date] => [span] => +1 Month [number_of] => 1 [date_types] => Month [calendars] => [limit] => 0 [dateformat] => jS [timeformat] => g:i a [monthformat] => F Y [event_template] => [date_template] => %DATE% [month_template] => %MONTH% [hide_duplicates] => ) }}} Here is a screenr showing the problem not working in IE9 and working in Chrome: http://www.screenr.com/mkhs " layotte 23909 Widgets Settings Loaded When No-Needed Widgets 3.5.1 normal normal Awaiting Review defect (bug) new 2013-03-30T16:02:05Z 2013-04-03T19:21:32Z "Hi, This ticket about the performance in the back-end interface . WordPress run query to get the active widgets settings in every page even in the dashboard ! , This makes the site admin slow especially when the site have many widgets ! You can use '''Debug Bar''' & '''Debug Bar Extender''' plugins to check the queries ." alex-ye 19444 Widgets page stale when pressing the Back button Widgets normal normal Awaiting Review defect (bug) new 2011-12-04T18:14:26Z 2011-12-05T16:54:31Z "For several versions of Wordpress (maybe all of them), I've noticed that the Widgets page can be loaded from cache: [[Image(http://img51.imageshack.us/img51/725/pictureen.png)]] I'm not sure why this is happening, when the page is first loaded headers are sent including `no-cache, must revalidate, max-age=0`, all of which seems to be done correctly: [[Image(http://img703.imageshack.us/img703/4526/screenshotwithshadow.png)]] However, if I load the widgets page, make a change to the order of the widgets, then navigate to another page, and then use the back arrow to go back to the widgets page, a cached version of the widgets page (pre-change) is loaded. This can be especially troublesome if you spend a lot of time making changes and adding and removing widgets, or widget content, then go back to the page and make another change before you realize that the cached page is loaded, because it will overwrite all the changes that you had just previously spent so much effort on. One possible solution would be to load all the widgets with AJAX if javascript is available, or possibly re-check that the correct widgets are in place with AJAX after the page loads (and use Javascript to reload the page again if they are not). The latter method would also enable the page to be loaded using standard methods if Javascript was not enabled." willshouse 22116 bug in dynamic_sidebar function Widgets 3.4.2 normal normal Future Release defect (bug) new has-patch 2012-10-06T12:19:48Z 2013-05-21T19:46:58Z "In the dynamic_sidebar function is for displaying the right sidebar, by id, but in the code it is searched by name: {{{ function dynamic_sidebar($index = 1) { global $wp_registered_sidebars, $wp_registered_widgets; if ( is_int($index) ) { $index = ""sidebar-$index""; } else { $index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $index ) { $index = $key; break; } } } }}} must be changed to : {{{ function dynamic_sidebar($index = 1) { global $wp_registered_sidebars, $wp_registered_widgets; if ( is_int($index) ) { $index = ""sidebar-$index""; } else { $index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['id']) == $index ) { $index = $key; break; } } } }}} " alexvorn2 24283 is_active_widget() incorrect logic Widgets normal normal Awaiting Review defect (bug) new 2013-05-08T07:07:41Z 2013-05-08T08:08:37Z "`is_active_widget()` only returns 'true' only if widget used inside sidebar. But there is a provision to use widget directly using `the_widget()` function. I believe there is a need of alter the logic of just checking inside sidebars." valllabh 23423 sanitize_title() in dynamic_sidebar() restricts the use of specific characters for sidebar IDs Widgets 2.2 normal normal Awaiting Review defect (bug) new 2013-02-08T13:25:00Z 2013-02-19T05:20:42Z "In the dynamic_sidebar() function in wp-includes/widgets.php uses sanitize_title() on the given index when it looks for a sidebar with a name that matches the index. After that it leaves the index value sanitized making it impossible to use characters not allowed by sanitize_title() in a sidebar ID. By not overwriting the given index value with the sanitized version it would still be possible to use any character for the ID. To achieve this, lines 847-853 {{{ $index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $index ) { $index = $key; break; } } }}} should be replaced with {{{ $sanitized_index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $sanitized_index ) { $index = $key; break; } } }}}" paulvandermeijs 19450 the_widget won't replace the widget class if not using the default sidebar arguments Widgets 3.2.1 normal minor Future Release defect (bug) new has-patch 2011-12-05T21:29:41Z 2012-04-27T19:31:04Z " When using the_widget(), the $before_widget argument only receives the widget class if using the default sidebar arguments... on lines 1129 - 1130 of wp-includes/widgets.php (wp 3.3 rc 1) {{{ $before_widget = sprintf('
        ', $widget_obj->widget_options['classname'] ); $default_args = array( 'before_widget' => $before_widget, 'after_widget' => ""
        "", 'before_title' => '

        ', 'after_title' => '

        ' ); $args = wp_parse_args($args, $default_args); }}} could be replaced by: {{{ $default_args = array( 'before_widget' => '
        ', 'after_widget' => ""
        "", 'before_title' => '

        ', 'after_title' => '

        ' ); $args = wp_parse_pargs($args, $default_args); $args['before_widget'] = sprintf($args['before_widget'], $widget_obj->widget_options['classname']); }}} " Felipelavinz 14876 wp_get_sidebars_widgets() assumes that widgets are enabled Widgets lowest minor Future Release defect (bug) reopened 2010-09-15T02:05:43Z 2010-12-04T09:34:28Z "When a theme does not have any sidebars defined, wp_get_sidebars_widgets() will return the database option anyway. This reveals a bug where a theme that does not have any widgets may still get the recent comments CSS injected into it. is_active_widget() is returning true because that widget was active when the sidebar option was last used." nacin 19709 Add 'before_sidebar' and 'after_sidebar' attributes to register_sidebar() Widgets 3.3 normal normal Awaiting Review enhancement new 2012-01-01T19:30:15Z 2012-01-01T19:30:15Z "Whilst experimenting with some code recently I needed to have each widget area wrapped inside a container with the widget id as the container CSS class/id. If used in a theme this widget area container usually has to be hard coded. This is the case for Twenty Ten, and Twenty Eleven. It occurred to me that it would be very useful to have an extra couple of attributes available in register_sidebar() such as 'before_sidebar' and 'after_sidebar' so that developers have a consistent way to automatically add a wrapper to each widget area. It would be additionally useful if you could do something like this to add the widget area id as the wrapper CSS class/id as required: `'before_sidebar' => '
        '` `'after_sidebar' => '
        '` or `'before_sidebar' => '
        '` `'after_sidebar' => '
        '` If this feature is considered then I'm not sure whether 'before_sidebar' or 'before_widget_area' is a better choice for the attribute name." dgwyer 19675 Add a jQuery triggers to the widget save action Widgets 3.3 normal major Awaiting Review enhancement new 2011-12-27T18:02:52Z 2011-12-28T01:59:14Z "Line 241 (widgets.dev.js): {{{ $(document).trigger('saved_widget); }}} or something... This way we could nicely hook our own js on that ""saved_widget"" event, instead of stuffing our js inside the widget form function. This is relevant for all events created by WordPress in the administration area, not just widget-save. Think of it like ""add_action"" for javascript..." digitalnature 16648 Add actions/filters to wp_widget_rss_output Widgets 3.1 normal normal Awaiting Review enhancement new dev-feedback 2011-02-24T18:03:40Z 2011-02-24T19:20:26Z "There is no way to filter/modify output of the function wp_widget_rss_output contained in [http://core.trac.wordpress.org/browser/trunk/wp-includes/default-widgets.php default-widgets.php] It would be nice to be able to filter the `` tags so that attributes such as `class=` or `rel=` can be added." dangayle 10976 Add before_content and after_content to widget options azaozz Widgets normal normal Future Release enhancement reopened dev-feedback 2009-10-19T08:17:10Z 2012-10-01T11:26:58Z "Hi, I'd like to request adding a two new parameters to the widget array for easier customization when creating themes. Parameters are : before_content and after_content (naming can be different) Basicaly we have now before_widget, after_widget, before_title and after_title and it's working great, but if while creating a theme you'd like to add more complexity to the graphics surrounding widget you have to add more divs etc. to make it work and look great, and if you got some divs or anything else between title and content you got a problem. Sure you can put the code in the after_title and it will work, but what in case if someone will decide to leave the title empty ? Your widget lacks code and your theme messes up. Please consider it! :)" newkind 5770 Add extra options for default tag-cloud widget Widgets 2.5 low minor Future Release enhancement reopened has-patch 2008-02-05T12:03:18Z 2009-10-13T21:59:19Z "The default tag cloud widget only allows changing the title that appears above the tag cloud in the sidebar. This patch allows use of more configurable options in wp_tag_cloud(), ie smallest, largest, unit, number, format, orderby, order." AndrewFrazier 20127 Add filter in dynamic_sidebar() to modify sidebar index andrewryno Widgets 3.3.1 normal normal Awaiting Review enhancement new has-patch 2012-02-27T00:06:06Z 2012-02-27T00:06:06Z Use case: changing sidebars depending on the page/post/etc loaded through a plugin. Nothing too complex, just no way to do it. There is a filter dynamic_sidebar_params but that isn't called until later on in the function after the widgets have been collected for that sidebar. andrewryno 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 20788 Add widget instance argument to widget_links_args filter Widgets 3.3.2 normal normal Awaiting Review enhancement new dev-feedback 2012-05-30T09:07:13Z 2012-09-13T09:25:07Z "Using the `widget_links_args` filter (used in the default Links Widget class) as it is right now is a bit useless because one does not have access to the widget instance that applies the filter. Widget instance may contain custom variables set by custom fields that may have been added to the widget form by plugins or themes using other filters. Being able to access widget instance from within the filter function gives developers lots of possibilities to customize the widget. My suggestion is simple: add `$instance` argument to the `widget_links_args` filter, like this (wp-includes/default-widget.php line 113): {{{ wp_list_bookmarks(apply_filters('widget_links_args', array( 'title_before' => $before_title, 'title_after' => $after_title, 'category_before' => $before_widget, 'category_after' => $after_widget, 'show_images' => $show_images, 'show_description' => $show_description, 'show_name' => $show_name, 'show_rating' => $show_rating, 'category' => $category, 'class' => 'linkcat widget' ), $instance )); }}}" ragulka 20790 Add widget_title filter to Links Widget Widgets 3.3.2 normal major Awaiting Review enhancement new dev-feedback 2012-05-30T09:23:29Z 2012-05-30T09:24:39Z "Currently the Links Widget is the only default widget that doesn't support the widget_title filter. This is inconsistent and creates problems when plugin or theme authors want to filter widget titles - every other widget's title get's filtered, but not the Links WIdget. Right now, displaying widget title is basically delegated to the wp_list_bookmarks function. While this works, I suggest that this should be changed to be more consistent with other widgets - displaying widget title should really be the widget class job, not wp_list_bookmarks. It should work with the existing wp_list_bookmarks function by specifying the categorize argument to be false." ragulka 13019 Allow multiple category widget dropdowns azaozz Widgets 3.0 low minor Future Release enhancement new has-patch 2010-04-15T18:13:31Z 2010-10-30T19:30:13Z "Although this may be a somewhat trivial and silly use of category widgets, currently placing two category widgets onto the same page with the dropdown option set results in having duplicate javascript and duplicative identified select boxes. Whilst the instance of each widget is unique, the select boxes displayed at not given unique IDs or Names, resulting in valid markup, and resulting in only the secondary select box operating correctly. The JS var gets redeclared by the duplicative script, which gives precedence to the second dropdown. One use case would be a page that lists long archives and shows a jump menu at both the top and bottom of the page. This would have to be done directly in the template due to the widget restrictions at present. I am attaching a patch that adds a static counter into the category widget function, and gives each dropdown a unique identifier ID/Name, allowing simultaneous use of several category dropdowns, the JS function is updated appropriately to. Code tested on IE7 and FF3, functionality remains the same as the original code, minus the limitation mentioned above. Feedback is appreciated, and please do re-tag if necessary." t31os_ 18671 Allow themes to set default widgets Widgets 3.3 normal normal Awaiting Review enhancement new 2011-09-15T06:52:41Z 2012-09-16T13:24:25Z "Rather than having to use a hard-coded fallback HTML sidebar, it'd be cool if a theme could set up default widgets. #17979 will somewhat remove the need for this but it could still be useful." Viper007Bond 12219 Comments on attachments don't appear in Recent Comments Widget azaozz Widgets 2.9.1 normal normal Future Release enhancement new has-patch 2010-02-13T12:41:39Z 2010-05-04T15:58:26Z "Comments on attachments don't appear in Recent Comments Widget. This is the same in 2.9.1 (and probably many other previous versions) and the patch will work with the older version as well." tfnab 19838 Don't display before_title and after_title if title is empty in widgets Widgets normal minor Awaiting Review enhancement new has-patch 2012-01-15T19:56:56Z 2012-01-15T23:34:30Z "Hi it's not necessary displaying before/after_title if $title is empty Example: wp-calendar don't have a title, so don't display $before_title and $after_title Solution suggestion: return false if filter widget_title notices that $title is empty Thank you" Xarem 21485 Exclude current post from Recent Posts widget Widgets normal normal Awaiting Review enhancement new has-patch 2012-08-05T23:16:56Z 2012-08-11T21:13:08Z "Checking demo site - http://twentytwelvedemo.wordpress.com/ If you visit any recent post like this one - http://twentytwelvedemo.wordpress.com/2012/03/28/road-trips/ The recent post widget on right sidebar include this post in recent 5 post. We could just exclude present post from the loop using code like this {{{ 5, ""orderby""=>""post_date"", ""post__not_in""=>array($post->ID) ); $posts = get_posts($args); foreach($posts as $post) { setup_postdata($post); ?> }}} Most theme has it. If you are already in a post which is among recent 5, no point of showing it in the loop. " Asif2BD 16613 Extend Widget API to allow sidebar/widget manipulation Widgets 3.1 low normal Awaiting Review enhancement new dev-feedback 2011-02-21T22:55:17Z 2013-01-21T17:27:26Z "There is currently no easy way to add a widget to a sidebar using code. We should add methods of doing this. A good example usage of such an API could be when a new theme is activated, it could add it's custom widgets to it's sidebar. API should provide support for adding widget X to sidebar Y (or even just the first sidebar) along with setting some options for the widget and where in the sidebar to add it (top vs. bottom)." Viper007Bond 20542 Extend register_widget to allow passing params as second argument codearachnid Widgets 3.4 normal normal Future Release enhancement new 2012-04-25T11:56:19Z 2012-05-15T20:24:50Z "I ran into an issue recently where I needed to make multiple calls of `register_widget('my_custom_class');` on the same class and have multiple unique widgets registered. The problem I ran into is that every time the same class is called it will overwrite the last instance of the same class during the widget constructor request `parent::__construct('unique_id', 'widget title');` This does not allow for reuse of the same class to instantiate multiple widgets. I found that if I were to extend the register method in WP_Widget_Factory to pass through arguments into the extended WP_Widget constructor that I can reuse the same class for multiple widget registations. I am working out the logic to implement this directly into /wp-includes/widgets.php for future functionality improvement." codearachnid 19587 JavaScript hooks for widgets Widgets normal normal Awaiting Review enhancement new 2011-12-17T15:39:56Z 2012-07-05T21:27:15Z "Hi, When a new widget is added to the sidebar, the javascript does not load for that widget. for example, if I just installed a plugin like iCalendar Events Widget or live countdown timer (bare with me, it's not the plugin that's faulty and I'll tell you why) and after installation I want to add it to the sidebar, I go to the widgets area under prefferences and drag and drop it. '''The bug is this:''' untill I refresh the page, the jquery won't work for anything in that widget. Both of the plugins mentioned above have a datepicker (from jquery-ui-core) popup that shows once a textbox or button is clicked. if the widget has just been added, the jquery that's supposed to run and show the calendars does not work until the page is refreshed. I received a ""not working"" status because of this and people complained that my plugin (live countdown timer) is broken. On further investigation, I found out that it was because !WordPress is not loading the javascript when first adding the widget in the sidebar and a refresh is required." ciprian_vb 14132 Login widget using wp_login_form(); function azizur Widgets 3.1 normal normal Future Release enhancement assigned has-patch 2010-06-28T18:51:07Z 2011-01-08T22:52:03Z "In wordpress 3.0 we added the [http://codex.wordpress.org/Function_Reference/wp_login_form wp_login_form();] function. But if a blog owners don't know PHP he can't add a login form to his blog. Adding a widget (that uses this function) will make it easyer for users to do this. " ramiy 21165 Make categories widget work with custom taxonomies Widgets normal normal Future Release enhancement new has-patch 2012-07-05T14:15:13Z 2013-05-02T14:17:27Z "The tag cloud widget already has a taxonomy dropdown. We should add one for the categories widget as well." scribu 16173 Make the Calendar widget support custom post types GautamGupta* Widgets 3.1 normal normal Future Release enhancement accepted 2011-01-10T05:35:22Z 2011-09-22T02:14:00Z The Calendar widget should have support for custom post types (much like how the tag cloud widget supports custom taxonomies) so that the plugins could just have `supports => array( ... 'calendar' ... )` and the calendar would display that post type in the option box (this is just an example, used in the patch I'm gonna attach, we may use some other arg, of course). GautamGupta 16581 Meta widget: properly redirect user after logging in / out Widgets 3.1 normal normal Awaiting Review enhancement new 2011-02-17T19:20:11Z 2011-02-18T02:11:07Z "Inside Meta widget, there's a login link. However, the href attribute doesn't contain a redirection query argument. So, there's a usability problem when someone is reading a post and want to comment, but can't because he's not logged in (and the blog requires logging in to comment). After logging in using the link inside Meta widget, the user is redirected to the admin area, instead of to the post he was reading. It would be a few clicks too many to go back to the post to comment. The same thing can be applied to the Log out link (when the user's currently logged in). Instead of showing the blank `wp-login.php` form, he should be redirected back to the page where he clicked the link." garyc40 20988 Open a closed sidebar box and enable droppable/sortable in it when you hover a draggable available widget over it ldebrouwer Widgets 3.4 normal normal Awaiting Review enhancement new 2012-06-16T10:27:24Z 2012-06-16T11:00:29Z "At the moment you have to explicitly open a sidebar box to allow it to except available widgets. In my humble opinion this is bad UX and the sidebar box should expand automatically when being hovered over with a draggable and it should accept the draggable to it's containing droppable/sortable as well. The obstacles to overcome: - Since the draggable in most cases overlaps the sidebar box when dragging over it ( unless you move really quickly ) it's hard to register a 'mouseenter'. This could be solved by setting the 'cursorAt' option for the draggable. - Opening a sidebar box is trivial but activating the droppable/sortable only seems to kick in when the draggable has been released." ldebrouwer 13524 Open closed widget areas when dragging onto them Widgets 3.0 low minor Future Release enhancement new has-patch 2010-05-24T18:48:17Z 2012-01-06T01:34:18Z Right now if you start dragging a widget in the widget admin and drag it over a closed widget area, you have to let go once, open up the widget area, then drag again. Make it so closed widget areas open up when you drag things onto them, perhaps after a slight (500ms?) delay. mitchoyoshitaka 10457 Parse shortcodes in text widgets by default westi Widgets 2.8 normal normal Future Release enhancement reopened 2009-07-21T11:27:06Z 2012-03-28T20:10:31Z Currently, shortcodes are only parsed within post content. It would, to my mind, be a nice enhancement to allow them to be parsed from within text widgets as well. The implementation is trivial, so the only real question is what problems this might throw up. ionfish 23012 Refresh the code for the default widgets Viper007Bond* Widgets 3.5 low minor Future Release enhancement accepted 2012-12-20T01:49:37Z 2012-12-21T21:28:45Z "The default widgets serve as examples for many people to make new widgets. We should make sure they're up to date in terms of coding standards and best practices. There's many places where this is not the case. A few examples: * `$instance['text'] = stripslashes( wp_filter_post_kses( addslashes($new_instance['text']) ) );` * `$text = esc_textarea($instance['text']);` rather than at output Also tons and tons of formatting issues. I'll volunteer to take this on." Viper007Bond 23520 Rename sidebars to something more appropriate Widgets normal normal Awaiting Review enhancement new 2013-02-19T08:38:12Z 2013-02-19T13:43:59Z "The things that we put widgets into are no longer just sidebars. Maybe they never were just sidebars. Widgets go into areas that can literally be displayed anywhere within themes. Proposal: rename ""Sidebars"" to ""Widget Areas"". Discuss." johnbillion 20180 Should wrap all links in a div Widgets normal normal Awaiting Review enhancement new 2012-03-05T19:43:51Z 2012-03-06T02:28:10Z "The links widget creates a separate div for every category. This does not allow to style all categories at once. Please wrap all links into one more level of div." porton 23083 Tag balancing for text widgets Widgets normal normal Awaiting Review enhancement new has-patch 2012-12-30T09:11:18Z 2013-01-29T20:58:48Z "Based on inspecting the code it looks like tag balancing is not applied to th content of the text widget. IMO people are more likely to produce broken HTML when adding HTML in a text widget then when writing post, but tag balancing is done only for posts and comments (in which HTML is rarely used)." mark-k 16125 Tag cloud widget: hide dropdown when there's only one taxonomy GautamGupta* Widgets 3.1 normal normal Future Release enhancement accepted dev-feedback 2011-01-06T18:56:09Z 2012-05-07T16:20:55Z "~~We should use `get_taxonomies()` instead of `get_object_taxonomies()`. Attaching a patch.~~ [20285] When there's only one taxonomy to select from, we shouldn't show the dropdown at all. " GautamGupta 23120 There should be indication that widget settings have been saved Widgets 3.5 normal normal Future Release enhancement new has-patch 2013-01-04T16:28:05Z 2013-05-14T12:45:51Z "There's currently no confirmation that adding a widget or changes to a widget have been saved. In some cases(fast hosting and a solid internet connection) the changes are saved so quickly the spinner is barely on the screen at all. I think a best course of action would be to have the word ""Saved"" appear briefly after the spinner goes away. Or perhaps a check mark as that doesn't need to be translated. Related post on make.wordpress.org: http://make.wordpress.org/ui/2013/01/02/this-morning-i-ran-2-users-through-some/" jacopo.vip 10364 Usability problem on the Widgets admin interface azaozz Widgets high minor Awaiting Review enhancement reopened has-patch 2009-07-09T04:48:56Z 2012-12-30T16:03:45Z "On the widgets page, when I have lots of widgets available it's a nightmare to drag and drop one by one on the intended sidebar. I have to scroll down and up the page while keeping the mouse button pressed. When someone is using a Notebook and no mouse it's really a pain. And with all that netbooks today it's even worse. What I think could be done: just put a toggle button (like the dashboard widgets) on each widget and when someone press this toggle button it opens a menu with some links like: add to sidebar 1, add to sidebar 2,... This would really be a usability improvement since it's not usable the way it is now. And off course the drag and drop doesn't need to be replaced. People should be able to use it either way. If you have a big monitor, go for drag and drop since you should be able to view all your available widgets on multiple columns without the need to scroll down the page. Otherwise just click the toggle and Add to sidebar." vteixeira 24040 "Use ""posts"" instead of ""topics"" (in tagcloud tooltips)" Widgets normal minor Awaiting Review enhancement new 2013-04-11T01:56:36Z 2013-04-11T06:30:42Z "Hello, I suggest use ''post(s)'' instead of ''topic(s)'' [http://core.trac.wordpress.org/browser/trunk/wp-includes/category-template.php#L563 here]. ""Topics"" is very related to forums (bbPress), while ""Posts"" are more general term I think? Thanks" Dianakc 15550 WP_Nav_Menu_Widget needs a filter for args Widgets 3.1 normal normal Future Release enhancement new 2010-11-23T21:48:57Z 2011-01-13T08:34:07Z "I have a very common need to change the walker of a menu printed by WP_Nav_Menu_Widget. The only way to do this is by injecting a new walker on the args array. By so, I propose changing '''default-widgets.php''': {{{ function widget($args, $instance) { // Get menu $nav_menu = wp_get_nav_menu_object( $instance['nav_menu'] ); if ( !$nav_menu ) return; $instance['title'] = apply_filters('widget_title', $instance['title'], $instance, $this->id_base); echo $args['before_widget']; if ( !empty($instance['title']) ) echo $args['before_title'] . $instance['title'] . $args['after_title']; wp_nav_menu( array( 'fallback_cb' => '', 'menu' => $nav_menu ) ); echo $args['after_widget']; } }}} To: {{{ function widget($args, $instance) { // Filter for args $args = apply_filters('nav_manu_widget_args', $args); // Get menu $nav_menu = wp_get_nav_menu_object( $instance['nav_menu'] ); if ( !$nav_menu ) return; $instance['title'] = apply_filters('widget_title', $instance['title'], $instance, $this->id_base); echo $args['before_widget']; if ( !empty($instance['title']) ) echo $args['before_title'] . $instance['title'] . $args['after_title']; wp_nav_menu( array( 'fallback_cb' => '', 'menu' => $nav_menu ) ); echo $args['after_widget']; } }}} " brodock 12354 WP_WidgetArea class Widgets normal normal Future Release enhancement assigned dev-feedback 2010-02-23T22:02:48Z 2010-06-25T17:19:31Z "After a short discussion involving the state of the Widget API within another ticket's comments, it was proposed to me to create new ticket on this subject. The idea is that in updating the Widget API, like the WP_Widget class, widget areas will have a similar registry structure. In my opinion though, I believe that for backwards compatibility it should be integrated but remain separate from the current API for controlling sidebars, also like the WP_Widget class. In the previous discussion, I said that a possibility could be creating a WP_WidgetArea class, and a WP_WidgetArea_Factory class to register and unregister them. After some thought though, I believe this is pretty much unnecessary. What is a widget? - It is a GUI module with a client-side and administrative view, wrapping how to control, use, and display data. It is a form of MVC, and that's basically it! That being realized, I don't see a problem with adding one more default widget to the core: WP_WidgetArea extends WP_Widget This will allow dynamic generation of widget areas. Implementing how to edit these areas within the current interface is another story, though I have a kind of hacked logic I am unhappy with working in a released plugin of mine. In the future, using widgets for widget areas will eventually depreciate the entire sidebar API. It would only depend on one global area to add and pull widgets from (the theme... cough...). Also, with custom post types now becoming more prevalent, and this is just my imagination talking, widgets could become another form of the post object: post_type = widget" jimisaacs 11387 Walker Widget System ShaneF* Widgets normal normal Future Release enhancement accepted needs-docs 2009-12-10T16:56:00Z 2011-01-08T19:34:01Z "This is a new system for Widgets. The design for this system is based on the fact that every theme is different. Currently the widget system does not care about one theme. It will still output it's own formating structure based on it's design and then bassed on a messy 'register_sidebar' arguments wrap that data inside one another. The idea behind a Walker Widget system is that instead of the Widget outputing the data, it send it to a Walker where it assigns the relevant information and the theme's ""Widget Design"" class holds how Widget boxes are created based on the values pushed through the walker. For example in my theme functions.php file: {{{ class Walker_Widget_Rabbit extends Walker_Widget { function start_widget($args, &$output) { // @todo Updated with the correct vars. $output .= do_action('sidebar_before_module', $id); $output .= do_action('sidebar_before_module_' . $id); $output .= sprintf( ""
        "", $args['widget_id'], $args['classname'] ); } function title_widget($args, &$output) { $output .= ""

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

        ""; /* if ((bool) $this->get_option('scrolling') && $scroll['enabled']) { printf(__(""navi:         prev / next""), $scroll['key'], $scroll['key']); } */ } function content_widget($args, &$output) { $output .= ""
        "" . $this->content_style($args, $args['output']) . ""
        ""; } function content_style($args, $output) { /* * Here I am going to figure out how we are going to wrap most content * and detirme if the information is scrolled information. */ $style = $args['style']; switch ($style) { case 'none': $style = $output; break; default: $style = ""
          "" . $output . ""
        ""; } return $style; } function content_scroll($args, $area = 'top') { // @todo
        and
        } function end_widget($args, &$output) { $output .= ""
        ""; // @todo Updated with the correct vars. $output .= do_action('sidebar_after_module', $id); $output .= do_action('sidebar_after_module_' . $id); } } }}} This also allows users to manipulate the data/design even further once they get it from the widget. I have tested this on the default theme of WordPress with the all 12 of the built in WordPress widgets and they act/look just like if it was hardcoded into the system itself. " ShaneF 16443 We need a way to programmatically tell if we are in a sidebar Widgets 2.2 normal normal Future Release enhancement new 2011-02-02T20:10:28Z 2012-04-24T13:21:16Z There is currently no way to tell if you are in_a_sidebar or doing a widget which makes me a sad stallman lookalike. jorbin 19159 When Inactive Widgets list gets long it is hard to clear cdog* Widgets 3.3 normal minor Future Release enhancement accepted has-patch 2011-11-05T09:48:59Z 2012-12-30T12:03:38Z "If you have a lot of inactive widgets it can be really hard manual labour to remove them all. It would be much nicer if there was a delete all button like this plugin adds http://wordpress.org/extend/plugins/remove-inactive-widgets/" westi 23328 While editing widgets in accessibility mode the position can be indicated by widget titles instead of numbers Widgets normal normal Awaiting Review enhancement new 2013-01-30T18:32:33Z 2013-03-04T20:06:35Z "Guess it title says it all. Right now you need to figure out the position you want the widget to be at and try remember it while editing the widget. I suggest to change the text text of the position column header from ""position"" to ""position after"" and use labels in the drop down 1 => ""top"" 2 => top widget title 3 => second widget title[[BR]] etc" mark-k 14466 Widget position uses footer position styling koopersmith Widgets 3.0 normal normal Future Release enhancement reopened 2010-07-30T08:13:12Z 2012-11-07T22:35:08Z "Hi, If you add a widget position called Footer with id footer, it has exactly the same id as the footer of the whole admin and because of that the widget position uses the styling from admin footer ie. bigger padding, italic font, darker background. Please see the attached pic. newkind" newkind 24008 Widgets title improvement Widgets normal normal Awaiting Review enhancement new 2013-04-09T18:12:17Z 2013-04-09T18:12:17Z "we have now: {{{ $title = apply_filters( 'widget_title', empty( $instance['title'] ) ? __( 'Categories' ) : $instance['title'], $instance, $this->id_base ); }}} why not to use? {{{ $title = apply_filters( 'widget_title', empty( $instance['title'] ) ? $this->name : $instance['title'], $instance, $this->id_base ); }}} " alexvorn2 17201 dynamic_sidebar performance Widgets 3.1 normal normal Awaiting Review enhancement new dev-feedback 2011-04-21T07:48:22Z 2011-06-29T12:04:49Z "I've got a few dynamic sidebars (say 6 or 7) and the dynamic_sidebar function spends 1/4 of a second only calling sanitize_title. See the piece of code on wp-includes/widgets.php: {{{ if ( is_int($index) ) { $index = ""sidebar-$index""; } else { $index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $index ) { $index = $key; break; } } } }}} That's occurs evenf if you provide an id, and not the sidebar name. We could avoid that by checking before trying to use the sidebar name if a sidebar exists with that id. Like so... {{{ if ( is_int($index) ) { $index = ""sidebar-$index""; } elseif ( empty($wp_registered_sidebars[$index]) || !array_key_exists($index, $sidebars_widgets) || !is_array($sidebars_widgets[$index]) || empty($sidebars_widgets[$index]) ) { $index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $index ) { $index = $key; break; } } } }}}" mrubiolvn 22436 escape recent posts widget post titles Widgets normal normal Awaiting Review enhancement new has-patch 2012-11-14T02:45:27Z 2012-11-14T09:08:13Z "The recent posts widget escapes the title attribute but does not escape element text. Add an esc_html wrapper to post title values to escape before output. Example post title: Post about < stuff >" niallkennedy 12133 get_field_id() and get_field_name() break when passed a name in array format azaozz Widgets 2.9.1 normal minor Future Release enhancement new 2010-02-05T02:17:10Z 2013-01-21T23:13:01Z "`get_field_name()` and `get_field_id()` are member functions of the widget API which generate the names and ids for fields on the widget admin screen. A custom widget cannot use an array format name with this function. For example, 'myfield[]' or 'myfield![3]' is a valid name for an input field, but this name cannot be passed to `get_field_name()` as the function will strip right square brackets from the name. Patch upcoming when I find the time." johnbillion 19912 Add Widget Groups and Locations Widgets 3.3.1 normal normal Future Release feature request new 2012-01-28T04:54:13Z 2012-04-24T17:00:42Z "Currently, if a widget cannot be properly matched to a sidebar when switching themes, it is moved to the ""Inactive widgets"" section (debated for quite a while here: #17979). With the addition of the planned appearance improvements, it would be nice if we could let the user manipulate widgets as a group. Instead of trying to be too clever, we can let the user review where the widgets are positioned in their theme. Conceptually, this is very similar to how nav menu locations currently operate. Menu items are grouped in menus (created by the user), which can be assigned to menu locations (created by the theme). Likewise, widgets would be organized into groups (created by the user), and could be assigned to widget locations (created by the theme). Currently, ""widget areas"" are on double-duty — they act as both ""widget groups"" and ""widget locations"". I think the first step is to add the concept of ""widget groups"" into the current API and turn the existing ""widget areas"" into locations mapped to these groups. If we're looking to compartmentalize the patches, these initial changes could initially be added without modifying the widgets UI. Instead, we could temporarily link a widget group to a widget area behind the scenes. That said, the benefits could only be fully realized with a few tweaks to the widgets UI." koopersmith 23008 Add a Hook To Hide Inactive Widgets Widgets 3.5 normal minor Awaiting Review feature request new dev-feedback 2012-12-19T19:59:12Z 2012-12-19T20:21:09Z "Hello, This is my first feature request so hopefully I'm going through the process correctly. Onto the request... Adding a hook to remove or hide the Inactive Widgets sidebar on the WordPress Admin Widgets page would be very useful for developers who don't use the area and want to be able to hide it for better UX. If this is approved I would love to submit a patch. :)" BFTrick 20791 Add tolerance: 'pointer' option to widgets Widgets 3.3.2 normal normal Awaiting Review feature request reopened dev-feedback 2012-05-30T11:26:20Z 2012-12-15T16:48:03Z "I made a conclusion that it's more easy to sort the widgets in a sidebar if is with tolerance: 'pointer' option enabled... please consider adding this to sortable function of the widgets. " alexvorn2 20596 Adding more actions to a widget Widgets normal normal Awaiting Review feature request new dev-feedback 2012-05-02T00:14:28Z 2012-05-02T05:45:48Z "On the Widget UI, there is a ""Close"" button, aside with the ""Delete"" button, and I that developers should have a way to add more of those. For exemple, I would see as a good use case when you have a way of previewing the widget. Because right now the only way is by JS which is kinda of lame. Thanks," webord 16109 Preview wigdets before publish Widgets 3.1 normal normal Future Release feature request new 2011-01-05T13:26:50Z 2012-05-02T16:11:45Z "Why isn't this possible yet? Before publishing a widget that you can preview it. That way you can get the right settings out without first needing to publish it for the whole site viewers. A preview would be very nice before publishing a wigdet like editting a post..." JonezJeA 18466 Reorganizing Widget Areas Widgets normal minor Awaiting Review feature request new 2011-08-18T00:18:17Z 2012-02-06T15:56:29Z "The widget-area boxes should be draggable as a whole. Meaning the user should be able to drag and drop the area boxes up and down as a way to rearrange the areas. Sometimes I want to move the entire area's contents to a different area, and the best way would just be to drag the box to a different position in the vertical order." audiobahn 15645 Refactor widgets.dev.css Widgets 3.1 normal normal Future Release task (blessed) new has-patch 2010-12-02T12:21:33Z 2012-12-24T07:05:58Z Standard refactor of widgets.dev.css to be much more awesome. See #14770 JohnONolan 13919 $pagenow / vars.php refactoring / Move $pagenow generation into it's own function Warnings/Notices 3.0 normal normal Future Release defect (bug) new close 2010-06-16T14:03:48Z 2011-03-23T19:35:07Z "In {{{wp-include/vars.php}}} an unset variable is passed by referecence to {{{preg_match()}}} in mutliple places. The same code-fragment where that problem is located does poisen the globale variable table with temporary variables as well. To prevent these problems, the variable needs to be set prior to be passed to preg_match and the code fragment needs to be refactored in it's own function. This might be helpful a bit as well when we start to free the codebase from hardencoded {{{/wp-admin/}}} admin directory definitions." hakre 23296 3.6 - Edit Post, Invalid implode after Core-Update Warnings/Notices normal normal Awaiting Review defect (bug) new reporter-feedback 2013-01-25T23:48:51Z 2013-01-26T11:51:16Z "'''Error:''' implode(): Invalid arguments passed The implode function have invalid Arguments. '''URL:''' /wp-admin/edit.php [[BR]]'''HTTP referrer:''' http://adrean-test.eatserver.nl/wp-admin/update-core.php '''FIX (wp-includes/compat.php - Line 32):''' {{{ return ($chars ? implode( '', $chars ) : array()); }}} '''Stacktrace:''' {{{ in implode called at /www/htdocs-test/wp-includes/compat.php (32) in _mb_substr called at /www/htdocs-test/wp-includes/compat.php (18) in mb_substr called at /www/htdocs-test/wp-includes/formatting.php (3096) in wp_html_excerpt called at /www/htdocs-test/wp-includes/admin-bar.php (230) in wp_admin_bar_site_menu called at ? (?) in call_user_func_array called at /www/htdocs-test/wp-includes/plugin.php (487) in do_action_ref_array called at /www/htdocs-test/wp-includes/admin-bar.php (58) in wp_admin_bar_render called at ? (?) in call_user_func_array called at /www/htdocs-test/wp-includes/plugin.php (406) in do_action called at /www/htdocs-test/wp-admin/admin-header.php (113) in require_once called at /www/htdocs-test/wp-admin/edit.php (220) }}}" hovida 15394 "Ancient ""Are you sure you want to do this"" now confusing" Warnings/Notices 3.1 normal trivial Future Release defect (bug) new early 2010-11-11T21:51:26Z 2012-09-15T00:14:05Z "The default failing nonce message did not pass the wife test. Asking ""Are you sure you want to do this?"" now that there is no longer ""OK"" and ""Cancel"" buttons is confusing and my wife just asked me ""How do I tell I'm sure?"" Not sure about the best wording, I took the same approach as Twitter's expired OAuth token links with a message that does not let user think there is something to confirm." ozh 23032 Call get_page_hierarchy without passing by reference in wp-includes/rewrite.php page_uri_index Warnings/Notices 3.0 normal minor Future Release defect (bug) new has-patch 2012-12-21T01:06:13Z 2013-05-16T12:38:59Z " PHP Strict Standards: Only variables should be passed by reference in wp-includes/rewrite.php on line 825 Due to &$pages in the function declaration. {{{ function get_page_hierarchy( &$pages, $page_id = 0 ) }}} Instead of calling get_page_hierarchy with the full $wpdb->get_results as the arg, save the get_results to a variable and pass that to get_page_hierarchy. {{{ $pages = $wpdb->get_results(...) $posts = get_page_hierarchy( $pages ); }}} " Askapache 22587 Cast image sizes to array before looping Warnings/Notices 3.3 normal normal Awaiting Review defect (bug) new has-patch 2012-11-25T22:02:49Z 2012-11-27T05:11:01Z "If someone doesn't filter the `image_size_names_choose` filter correctly, or uses some helper function like `__return_false` if they don't want to display any image sizes, a warning is thrown. The `$sizes` var should be cast to an array before looping to avoid this warning." griffinjt 23416 Form handlers assume $_POST elements will be strings Warnings/Notices 3.5.1 normal normal Awaiting Review defect (bug) new 2013-02-07T19:26:18Z 2013-02-08T16:59:16Z "I'm running Wordpress 3.5.1 on PHP 5.3. This example is from lines 50-53 of wp-comments-post.php: {{{ $comment_author = ( isset($_POST['author']) ) ? trim(strip_tags($_POST['author'])) : null; $comment_author_email = ( isset($_POST['email']) ) ? trim($_POST['email']) : null; $comment_author_url = ( isset($_POST['url']) ) ? trim($_POST['url']) : null; $comment_content = ( isset($_POST['comment']) ) ? trim($_POST['comment']) : null; }}} The issue is that If your post data contains something like: {{{ author[]=foo&author[]=bar }}} or {{{ comment[]=foo }}} Then the corresponding values in $_POST will be arrays, not strings, causing an E_WARNING. There seem to be a number of other places where $_POST data is passed directly to PHP string functions as well, causing potential warnings. These should be handled gracefully by checking the type of the element being grabbed from $_POST first: {{{ $comment_author = ( isset($_POST['author']) && is_string($_POST['author']) ) ? trim(strip_tags($_POST['author'])) : null; $comment_author_email = ( isset($_POST['email']) && is_string($_POST['email']) ) ? trim($_POST['email']) : null; $comment_author_url = ( isset($_POST['url']) && is_string($_POST['url']) ) ? trim($_POST['url']) : null; $comment_content = ( isset($_POST['comment']) && is_string($_POST['comment']) ) ? trim($_POST['comment']) : null; }}}" tabacco 20793 Illegal string offset 'public' in wpmu_create_blog() Warnings/Notices 3.0 normal normal Future Release defect (bug) new has-patch 2012-05-30T16:18:53Z 2012-05-30T16:18:53Z "If $meta is not passed and left as default empty string then: {{{ update_option( 'blog_public', (int)$meta['public'] ); }}} will throw a notice." duck_ 17328 In User Profile, Undefined property: WP_User::$rich_editing line 189 user-edit Warnings/Notices 3.2 normal normal Awaiting Review defect (bug) reopened has-patch 2011-05-05T05:00:24Z 2011-05-23T08:29:51Z "Notice: Undefined property: WP_User::$rich_editing in C:\web\wpbeta\wp\wp-admin\user-edit.php on line 189 />" anmari 19706 NOTICE: wp-admin/includes/post.php:834 - Illegal member variable name Warnings/Notices 3.3 low normal Awaiting Review defect (bug) new close 2012-01-01T00:30:43Z 2012-04-30T15:32:28Z "Received this notice: {{{NOTICE: wp-admin/includes/post.php:834 - Illegal member variable name}}} Traced it to this in {{{wp_count_posts()}}}: {{{ $count = $wpdb->get_results( $wpdb->prepare( $query, $type ), ARRAY_A ); $stats = array(); foreach ( get_post_stati() as $state ) $stats[$state] = 0; foreach ( (array) $count as $row ) $stats[$row['post_status']] = $row['num_posts']; $stats = (object) $stats; }}} Apparently I have a post with a post status of a blank string. So that gets set to an array key, and then is cast to an object. WP doesn't like that. Proposed: {{{ foreach ( (array) $count as $row ) { if ( !empty( $row['post_status'] ) ) $stats[$row['post_status']] = $row['num_posts']; } }}} Just discard empty post_status rows." markjaquith 21031 Orphaned comments emit debug notices in dashboard and comments lists Warnings/Notices normal normal Awaiting Review defect (bug) new has-patch 2012-06-21T04:11:54Z 2012-06-21T07:19:14Z "map_meta_cap is not prepared to handle missing or invalid post ID's. To duplicate this, delete a post from the posts table without deleting its attached comments, then visit the admin dashboard with the recent comments widget visible. The comments list table exhibits a similar issue, where the $post global is assumed to be set and valid. This isn't something that happens naturally in WordPress core, but is something plugins are able to do directly to the database, which results in orphaned comments. The attached patches only suppress debug notices PHP spits out, and does not directly address the issue of what to do with orphaned comments, should a plugin choose to do this." johnjamesjacoby 23406 Some notices messages which can maybe fixed Warnings/Notices 3.5.1 normal trivial Awaiting Review defect (bug) new 2013-02-06T17:59:55Z 2013-02-06T18:07:32Z "Hi, I use wordpress multisite on my own cms and I notice there are many notice messages when I load WP (include($wppath.""includes/wp.inc.php"") : 1) Declaration of Walker_Category::start_el() should be compatible with that of Walker::start_el()) in /wp-includes/category-template.php line 902 2) Declaration of WP_Scripts::set_group() should be compatible with that of WP_Dependencies::set_group()) in wp-includes/class.wp-scripts.php 3) Declaration of Walker_Nav_Menu::start_el() should be compatible with that of Walker::start_el()) in wp-includes/nav-menu-template.php 4) is_a(): Deprecated. Please use the instanceof operator) dans le fichier wp-includes/capabilities.php Hope it helps Regards, Alexandre" uniterre 16651 Warnings on dashboard: Notice: Trying to get property of non-object in wp-includes/capabilities.php Warnings/Notices 3.0 normal normal Awaiting Review defect (bug) reopened 2011-02-24T19:27:46Z 2012-12-20T08:59:34Z "I just upgraded a local install to 3.1 and have the debug mode on. Now, on the dashboard the ""Recent Comments"" box is filled with notices. I will attach a screen-shot of the notices. Though this doesn't show when debug mode is off, I have to assume that something isn't working with all of these warnings." grandslambert 23428 comments_open causes PHP notice in certain cases Warnings/Notices 2.5 normal normal Awaiting Review defect (bug) new has-patch 2013-02-08T21:51:39Z 2013-02-10T15:59:50Z when `comments_open()` is called for a non-existant post (either a bad ID, or no ID passed and called from a non-single page), a PHP notice is caused. Ideally, plugins shouldn't be doing this, but a simple null check in `comments_open()` fixes the problem. willnorris 18730 media_sideload_image() doesn't handle dynamic image url's well Warnings/Notices 2.9 normal normal Awaiting Review defect (bug) new has-patch 2011-09-21T10:49:11Z 2012-08-23T20:17:02Z "Example URL: http://www.tumblr.com/photo/1280/10464566223/1/tumblr_lrum2xzkpC1r3z8e3 As a result, the preg_match() for the file extension fails and issues a notice (no file extension in that url, although the redirection location does have). The handling of a download failure also seems hairy, upon failure, it still attempts further importing before loading - I haven't looked into that too far." dd32 14893 wp_inactive_widgets sidebar forgotten, then does notice in /wp-admin/widgets.php Warnings/Notices 3.0.1 normal normal Future Release defect (bug) new has-patch 2010-09-18T07:24:45Z 2011-01-13T04:31:00Z "The 'wp_inactive_widgets' is not initalized but used later on. Can be fixed easily by adding it while the array get's initialized." hakre 22239 wp_ob_end_flush_all() tries to destroy non-destroyable output buffers Warnings/Notices normal normal Awaiting Review defect (bug) new 2012-10-21T03:20:47Z 2012-10-21T03:28:19Z "`wp_ob_end_flush_all()` currently tries to flush & destroy every PHP Output buffer that is enabled on the current installation. However, not every type of PHP Output buffer can be destroyed, which will cause a PHP Notice when attempts to do so are made. An example of this is PHP extensions such as New Relic, or PHP output buffers created with the `$erase` flag set to false in `ob_start()` An example is when New Relic is installed on a host, also [https://newrelic.com/docs/php/php-agent-faq#rum-obclean see New Relics FAQ entry] on the issue. {{{ ( ! ) Notice: ob_end_flush(): failed to send buffer of New Relic auto-RUM (1) in ../trunk/wp-includes/functions.php on line 2641 Call Stack # Time Memory Function Location 1 0.8510 4328360 shutdown_action_hook( ) ../load.php:0 2 0.8510 4328440 do_action( ) ../load.php:556 3 0.8510 4329856 call_user_func_array ( ) ../plugin.php:406 4 0.8510 4329888 wp_ob_end_flush_all( ) ../plugin.php:406 5 0.8511 4330064 ob_end_flush ( ) ../functions.php:2641 }}} Somewhat similar to #18239 I'm not sure of what the ideal solution for this would be for !WordPress, but wanted to record the issue being known." dd32 13874 "Add package argument to ""_deprecated_function"" function" westi* Warnings/Notices normal normal Future Release enhancement accepted has-patch 2010-06-13T23:48:37Z 2013-05-14T13:27:25Z "Got to thinking it would be nice if plugins could use the _deprecated_ API by passing a ""$package"" argument to separate themselves from WP core, and so this patch was born. " johnjamesjacoby 16698 Better Table field value upgrade check (minor) Warnings/Notices 3.1 normal minor Awaiting Review enhancement new reporter-feedback 2011-02-28T10:31:06Z 2011-03-04T12:48:04Z "line 1463 on /wp-admin/includes/upgrades.php is {{{ preg_match(""|"".$tablefield->Field."" ([^ ]*( unsigned)?)|i"",$cfields[strtolower($tablefield->Field)], $matches); $fieldtype = $matches[1]; }}} There is no check IF a $matches is found. If there is no match found an error will be displayed 'undefined index 1'. An Error message could be added here. Can happen : if the sql code contains no spaces between the fieldname and the type it will generate the not found [1]. " cogmios 23062 Issue warnings for deprecated and wrong behavior in pre-release builds Warnings/Notices normal normal Future Release enhancement new 2012-12-27T16:51:05Z 2013-05-16T11:56:07Z "Coming out of #22873 and the [https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2012-12-12&sort=asc#m518273 associated development chat]: _doing_it_wrong(), _deprecated_argument(), _deprecated_file(), and _deprecated_function() should issue an E_USER_WARNING up to and including RC1, and an E_USER_NOTICE otherwise." nacin 20213 Pagination fails silently when mysql.trace_mode is on Warnings/Notices 3.4 normal normal Awaiting Review enhancement new 2012-03-10T16:06:15Z 2012-03-10T16:06:15Z "A sysadmin left enabled '''mysql.trace_mode''' on php.ini without me knowing about it, and I spent hours trying to find out why the '''next_posts_link''' wasn't showing up. This is very hard to debug, because * it fails silently, with no error to look for * it's hard to repro on a dev server, which may not have the same php.ini settings as in staging/prod (ideally should, but rare for 99% of devs) Other people had this same issue: * ""[http://wordpress.org/support/topic/page-navi-not-working-with-mysql-5134-amp-php-529 No error, it's just not working]"" * ""[http://wordpress.org/support/topic/archives-not-showing-nextprev-windows-only-crazy Am I going crazy]""? * Trace_mode defaulted to ""on"" in [http://stackoverflow.com/a/869957/128329 this guy's] install (!). I've read through #18536, #10469 and related issues, hoping that usage of SQL_CALC_FOUND_ROWS would be removed, but it seems to be still there, in trunk. So I guess a ""fix"" for this would be to check for trace_mode and, if enabled, notify admin users on the wp-admin dashboard. Meanwhile, I've added a note about this on the [http://codex.wordpress.org/Function_Reference/next_posts_link next_posts_link] page. " ManuelRazzari 5669 Provide single logging functions to replace logIO(), debug_fwrite() etc. Warnings/Notices 2.3.2 low minor Future Release enhancement new 2008-01-14T20:43:34Z 2011-03-31T08:42:45Z "I'm looking at writing a logging infrastructure so that logIO() and debug_fwrite() can be consolidated into a single plugin replacable function (giving potential expansion into MySQL or syslog logging). I hope to follow this up with calls to the same function so administrative access can leave an audit trail. " pishmishy 22342 "WP_DEBUG ""undefined index"" notices in get_metadata() for empty arrays" Warnings/Notices 3.1 normal minor Awaiting Review enhancement new dev-feedback 2012-11-01T22:10:42Z 2012-11-13T01:29:41Z "When the WP_DEBUG constant is set, calling get_metadata() in /wp-includes/meta.php with $single==true can cause ""undefined index"" notices when the meta data value is an empty array. As null is an acceptable return value for this function, silencing the notice with @ will remove noise when debugging without the overhead of checking the array length or that the 0 index isset()." doublesharp 19291 Widgets move to Inactive after clearing all widgets from sidebars Warnings/Notices 3.3 normal normal Future Release enhancement new early 2011-11-18T15:49:18Z 2011-11-23T22:44:56Z "Jane reported in IRC that a theme switch dropped her widgets to Inactive. > Jane: test site had 2010 as theme, with some widgets. activated 2011 on themes.php. Refreshed itself to themes.php?activated=true and showed alert message "" New theme activated. This theme supports widgets, please visit the widgets settings screen to configure them."" Go to widgets screen, widgets in primary sidebar in 2010 are not in sidebar, no widgets live anymore > Jane: switch back to 2010, same message appears on themes.php?activated=true and 2010 sidebar comes back [http://core.trac.wordpress.org/ticket/19091#comment:11 Reproduced by ocean90]. I was able to repeat the reported issue one only one specific case. This only happens if you remove *all* widgets from all sidebars. Then add widgets back to sidebar(s). Then, switch back to a previously activated theme. - It doesn't happen if you leave at least one widget in place in a sidebar - It doesn't happen if you switch to a new theme (not previously activated) Looks like we can solve it by the ""lost"" widget check just puts any old widgets into Inactive. We should orphan those, too. To fix: If widgets registered but not in the new theme's sidebar, orphan it. See #17979, #19091, #19092." lancewillett 23767 remove_menu_page: Check for existing menu items Warnings/Notices 3.5 normal normal Awaiting Review enhancement new close 2013-03-14T13:32:47Z 2013-03-16T17:56:37Z "This error appears in my error log: ''PHP Warning: Invalid argument supplied for foreach() in /www/htdocs/wp-admin/includes/plugin.php on line 1290'' The if-empty patch is attached. " sergej.mueller 18368 Add CSS Class Info to post_updated_messages array/filter Warnings/Notices 3.2.1 normal minor Awaiting Review feature request new dev-feedback 2011-08-10T12:50:18Z 2011-08-11T23:38:17Z "When saving a post, not all messages displayed on the screen are ""success"" messages. Some are errors or warnings. Therefore, it would be nice to have the ability to modify the CSS class that's applied to the notice message. In order to support backwards-compatibility, I would suggest allowing the array that's built using the post_updated_messages filter to support strings (which would be the message text by itself) or arrays (which would include one item for the message text and one item for the message class). If a string is found, that string is assigned as the message text. If an array is found, the first item is assigned as the message text and the second item is assigned as the message class. If a message class is not defined, the CSS class of 'updated' is used; if it is found, the specified CSS class is used. I've attached a patch for wp-admin/edit-form-advanced.php showing basically what I'm proposing. In this case, if an array is sent as the value of one of the messages, that array is expected to use the keys ""message"" and ""class""; but it could certainly be edited just to use numeric keys if that might make more sense." cgrymala 22712 Admin using deprecated valign attribute Validation 3.4.2 normal normal Future Release defect (bug) new has-patch 2012-12-04T06:54:10Z 2013-01-18T23:38:46Z "Hi, I noticed when I validated one of my plugins' admin pages, I received approx. 40 error messages regarding the use of ""v-align:top;"" within the css structure. (Please see attached screenshot) Is there a way to use a different css to target these elements instead of the deprecated v-align usage? Thanks!" josh401 16135 Invalid markup in administration pages Validation 3.1 normal minor Future Release defect (bug) new has-patch 2011-01-07T10:31:38Z 2011-02-09T16:37:53Z There still remain (related to #15287) some trivial validation errors in pages in wp-admin. I have attached two tiny patches that fix some of them. wahgnube 15204 JavaScript Validation should trim values and set focus on invalid field Validation 3.1 normal normal Future Release defect (bug) assigned has-patch 2010-10-24T15:46:28Z 2011-01-13T21:09:02Z "If invalid fields are found after validation, focus should be placed on the first invalid field. Field values should be trimmed to check for truly empty values. Also worth noting, the (mostly same) validateForm is located in both common.js and wpAjax.js." batmoo 18395 Non-URL GUIDs are stripped on post update Validation 3.2.1 normal normal Awaiting Review defect (bug) new 2011-08-13T18:31:48Z 2011-08-13T23:12:02Z "The post guid is run through several filters before the post is saved. the esc_url_raw() call will end up setting a GUID to an empty string if the GUID does not begin with a known/accepted protocol. If a plugin/etc. wants to use the GUID column to store an external ID for an item brought in from another system (say a Flickr photo ID), then updating a post that has the Flickr ID as its GUID through the WP admin will end up setting the GUID for that post to ''. This would need to be changed if the move was made to UUIDs for GUID values as well. Related: #6492. A very basic patch for this specific issue is attached, but a larger discussion around how this should work is likely needed. Related: #18315" alexkingorg 14376 "admin post.php fails html validation due to use of ""["" in name/id/for of hidden custom fields" Validation 3.0 lowest normal Future Release defect (bug) new 2010-07-21T07:37:54Z 2012-12-25T16:11:48Z "Post.php is causing many many html validation errors due to hidden screen reader text for post meta fields mainly. Not a major problem, but annoying when attempting to validate admin plugin code. eg: {{{ character ""["" is not allowed in the value of attribute ""id"" character ""["" is not allowed in the value of attribute ""for"" }}} ""["" are allowed in the name attribute. So perhaps one could simply strip them out them for the 'id' and the 'for'? Other failed validation messages that occur a lot and appear to be wp generated code: - ID ""_ajax_nonce"" already defined - reference to non-existent ID ""metakeyselect"" " anmari 21164 wp_customize_support_script support for XHTML themes Validation 3.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-07-05T13:31:15Z 2012-11-07T08:53:41Z The script just needs wrapping in a CDATA section for XHTML themes. needle 23165 Admin validation errors on form nonce element IDs (_wpnonce) Validation normal normal Awaiting Review enhancement new has-patch 2013-01-10T02:25:17Z 2013-04-03T03:21:53Z "The `wp_nonce_field()` method has a design flaw in that the `name` parameter is optional, but its default value (""_wpnonce"") is used for the field element `id`. This wouldn't be bad if only one form is used on each page, but that is rarely the case in the admin panel. Currently, this only results in harmless HTML validation errors in admin, and in very rare situations (depending on plugins installed), can result in javascript scope-related issues breaking forms. This is an issue that keeps being reported and fixed several times (see #5962, #6564, r14737 from #13383, and the latest [http://core.trac.wordpress.org/ticket/22712#comment:11 #22712]) by simply specifying the name in all locations that don't at the time in core. There's at least three different approaches that I can see where we could prevent this from popping back up in the future and encourage better coding habits. == A: Require the Name Parameter == The most obvious approach is to simply adds a `_doing_it_wrong()` call (though it could just be `_deprecated_argument()` instead) for any calls to `wp_nonce_field()` that don't specify the `name` parameter, forcing everyone to give nonce fields unique IDs (and names). A side-effect of this change is that it will also warn developers they are doing it wrong if they use `wp_nonce_field()` without the (also currently optional) `action` parameter, which is actually a good thing since the docs already warn that this is a security hole. There are 46 locations in core that would need updated with this change that make this mistake, and the fix for each of them with this change is exactly the same as what every other commit to fix this problem has always done: just specify the `name` to give a unique ID. The downside to this approach is that this pushes for an immediate change not only to all calls to `wp_nonce_field()`, but also their corresponding `check_admin_referer()` calls (to update the changed field name) in a single WP release, and considering how frequently it's called this way in core, I don't even have to look at plugins to see how often it happens there (it's going to be too many to count). This approach still results in an explicitly named ID that really doesn't need to be on the field in the first place in most locations. I gave this approach a shot anyway, and started on a patch just to see how much work it would be at least in core, but I started to find a few locations that could benefit from unique IDs, but similar field names. I also found myself already spending hours updating and testing just 9 of the 46 locations (unit tests don't cover this stuff) where I was forced to make changes to IDs that would be best left alone for now. I have attached this unfinished patch anyway if anyone is curious to see how it works, what it does, and to see what kinds of changes it ends up requiring. It's still possible to just pass ""_wpnonce"" as the `name` with this change, so the rest of the locations could simply use that to progressively work towards unique IDs, but I just don't see this as a good solution overall, and it seems like a lot of work for very little gain on a minor issue. == B: Use Action for ID or Remove ID Entirely == Another option might be to remove ID entirely, or use (and require) the action parameter as the ID. This would improve results with unique IDs fixing most locations where `wp_nonce_field()` is used without requiring a change to each one individually for most uses (except for nonces used with ajax calls). All locations in core at least use `action` already, so the case for using `action` as ID instead seems better than using `name`. Unfortunately, either removing or using the action parameter for ID (changing the ID) would obviously break a few plugins that made the mistake of relying on the default `_wpnonce` (or the current `name` value) value for `id` from within JavaScript code for existing form endpoints. In the WP.org plugin repo, this appears to happen in the following plugins (searching up through plugins starting with 'r') for forms using the default value: {{{ automatic-youtube-video-posts buddypress buddypress-backwards-compatibility canalblog-importer community-submitted-news eyes-only-plus facepress-ii globalfeed lazyest-gallery lazyest-maps maven-member pagely-reseller-management pluginbuddy-yourls post-event2 qtranslate-separate-comments repostus ... }}} There's likely way more plugins that post to core forms using a non-default `name` that would break though as well, and even though I think ID should have never been added to the nonce field attributes and was never necessary in the first place, compatibility rules would need to be broken if this approach was used. This of course means this option is most likely not really an option at all. == C: Use an Option Array Parameter in Place of Name == To keep this concise, this last approach basically involves changing `wp_nonce_field()` to: {{{ function wp_nonce_field( $options = array() ) { ... } }}} The `options` parameter is a standard arguments array used with `wp_parse_args()`. This accomplishes not just one, but two different goals. First, if `$options` is not an array or the method was called with anything other than 1 parameter, we know this is an older call that needs to use the `name` parameter for both `name` and `id`, using `func_get_args()` for the original arguments, and can do so for full 100% backwards compatibility. Second, unrelated to this issue, the function has been refactored to adhere to coding standards in regards to [http://codex.wordpress.org/WordPress_Coding_Standards#Self-Explanatory_Flag_Values_for_Function_Arguments self-explanatory flag values] as far as the `referrer` and `echo` options are concerned. The `options` array can then be made to accept the following settings: - action: The same unique name included in the nonce hash as is the case now. - name: The field name (and *only* used for the name attribute). (Default: ""_wpnonce"") - id: The field ID if this really is still desired, and can even be different than the name, but by default, the field won't have an ID at all. - referrer: Whether to set the referer field for validation. (Default: true) - echo: Whether to display or return hidden form field. (Default: true) The only downside here is that each `wp_nonce_field()` call will be more verbose in most cases, especially if they do need to use an ID. For example, this: {{{ wp_nonce_field('add-tag', '_wpnonce_add-tag'); }}} Will now become this: {{{ wp_nonce_field( array( 'action' => 'add-tag', 'name' => '_wpnonce_add-tag' ) ); }}} I see plenty of benefits to this last solution though, and it requires very few changes up front, so I think it comes down to this approach ultimately. Please see attached patch." bpetty 15058 Validate option and transient name lengths Validation 3.1 normal normal Future Release enhancement new needs-unit-tests 2010-10-07T15:37:46Z 2013-05-17T15:52:23Z "The option_name column in the options table holds up to 64 characters yet there aren't any length checks to ensure that the length isn't exceeded. This leads to all sorts of odd behavior as the name will be truncated to fit, saving the option but not allowing it to be retrieved with the same name. This issue affects all uses of the options system. A particular annoyance is transients. A transient that doesn't expire has a max name length of 53 characters yet a transient that does expire has a max name length of 45 characters. When attempting to save an expiring transient of name length between 46 and 53 characters, the transient will store but will be deleted before being used when get_transient is called due to the missing _transient_timeout_ option (since it was too long). The core issues are that the functions don't return any type of failure condition on names that are too long and no warning is created. So, I've created a patch that addresses both of these issues. The patch shows an example of how option and transient name length validation can be added. In order to allow users to modify the option_name column length, a new constant, WP_OPTION_LENGTH, is created with a default value of 64. This constant is checked for all length validation. This is simply an example of how I'd like the validation to function. I'm not attached to the wording of the warnings or the name of the constant." chrisbliss18 22409 add multiple selected options support to selected() function Validation 3.4.2 normal minor Awaiting Review enhancement new 2012-11-10T23:31:57Z 2012-11-10T23:36:10Z "The current {{{selected()}}} function returns ''selected=""selected""'' if two strings match, but does not correctly handle arrays that result from select options that have ''multiple=""multiple""'' enabled (it just checks the first item in the array by forcing a string type). I suggest either adding correct handling of arrays or alternatively adding a separate {{{multiselected()}}} function to handle this situation. This could be accomplished by altering the current {{{__checked_selected_helper()}}} function to this: {{{ function __checked_selected_helper( $helper, $current, $echo, $type ) { if( is_array( $helper ) && in_array( $current, $helper, true ) ) $result = "" $type='$type'""; elseif ( (string) $helper === (string) $current ) $result = "" $type='$type'""; else $result = ''; if ( $echo ) echo $result; return $result; } }}} I've just added the first 2 lines and changed the first {{{if}}} to an {{{elseif}}}." bitacre 21140 """Display name publicly as"" setting not set until a change is made in the setting" nickharambee Users 3.4 normal normal Awaiting Review defect (bug) new has-patch 2012-07-02T21:29:48Z 2012-07-02T22:37:46Z "I have found this issue with several users that I have set up on my site. The default value for ""Display name publicly as"" is the first name of the user when creating a new user, or at least that is what shows in the ""Display name publicly as"" drop-down menu. However, when creating a new user, the full name, i.e. the first and last name is what displays publicly. In order to get only the first name to display publicly I need to set the ""Display name publicly as"" option to another option, save changes, and then reset it to just the first name, and save changes again. Surely, if it is the first name that shows in the drop-down menu, it should be the first name that actually displays publicly, without having to go through this rather strange process? I am using the latest version of Buddypress (1.5.6) as well as several other plugins. I have not tried disabling all of these." nickharambee 15636 """New User Default Role"" dropdown should order by privilege level" Users 3.0.2 normal normal Future Release defect (bug) reopened 2010-12-01T22:10:32Z 2013-01-22T15:17:49Z "The '''New User Default Role''' dropdown at '''wp-admin/options-general.php''' is in spiffy random order: * Subscriber * Administrator * Editor * Author * Contributor This UI bug suggests that '''Subscriber''' and '''Contributor''' are the opposite poles of privilege levels. In fact, they are successive steps in increasing privilege. Also, it doesn't make sense to put the least and greatest privileges, '''Subscriber''' and '''Administrator''', next to each other. Please let proximity and position serve their purpose: order this dropdown by level of access, starting with the least access: * Subscriber * Contributor * Author * Editor * Administrator" novasource 22993 Admin - users without a role are difficult to find Users 3.5 normal normal Awaiting Review defect (bug) new 2012-12-18T17:32:21Z 2012-12-20T06:21:38Z "There doesn't appear to be a filter to display users *without* a role (see the screenshot). The ideal solution would be to add a filter for ""None"". [http://i.imgur.com/3S5pH.png]" logikal16 18658 Allow apostrophe in email validation Users 3.2.1 normal normal Awaiting Review defect (bug) reopened has-patch 2011-09-14T09:23:38Z 2012-07-20T23:54:05Z "When the is_email function checks the format of a supplied email, it errors when it finds an apostrophe in the local part of the email address. Many valid emails use apostrophe's, and as such this should be accomodated in the validation." swinhoe 18039 Allow apostrophes in email addresses when accounts are added via Dashboard Users 3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2011-07-08T16:36:55Z 2013-04-02T09:54:29Z "See #4616. Currently it's not possible to add a user with an apostrophe in his email address in any of the following ways: - Dashboard > Add User (non-MS) - Dashboard > Add User > Add Existing User (MS) - Dashboard > Add User > Add New User (MS) With existing users, you get a 'user not found' error. Otherwise you get an error about invalid email addresses. This is inconsistent with WP's basic email address behavior, which allows apostrophes in email addresses. For the most part, the problem is simply that the value of 'email' in the $_POST data must be stripslashed. In a few cases, adjustments had to be made to the way that email addresses are escaped, to allow for the ' character (see esc_email()). See attached patch." boonebgorges 16788 Ampersands in e-mail address become invalid Users 3.0.5 normal major Awaiting Review defect (bug) new dev-feedback 2011-03-07T20:01:38Z 2012-09-19T17:46:32Z "When an e-mail address contains an ampersand, WordPress improperly escapes the ampersand invalidating the e-mail address. Example: h&f@domain.com becomes h&amp@domain.com First of all, the proper HTML entity for ""&"" is '''&'''. Where did the extra '''amp''' come from? Also, an ampersand is a valid character in an e-mail address and should not be escaped. Escaping it could be a completely different e-mail address. I have not dug into the code to find out where this is happening but I'd assume in '''sanitize_email()'''." jfarthing84 16484 "Attempting to add user with username ""0"" gives fatal error" Users 3.1 lowest minor Future Release defect (bug) new has-patch 2011-02-07T19:45:17Z 2012-09-19T22:31:51Z "Create a new user. Use the number 0 as the username. Receive this error: > Catchable fatal error: Object of class WP_Error could not be converted to string in /Users/mark/Sites/wp/wp-includes/formatting.php on line 2818" markjaquith 22311 "Cannot login when my loginname contains an ""|"" character" Users normal normal Awaiting Review defect (bug) new close 2012-10-30T13:06:13Z 2012-10-31T01:09:24Z "Hello, Cannot login when my loginname contains an ""|"" character, for example: Sent|el or P|ng|n Can you fix his ? Other systems like phpBB3 have no problems with such usernames ! " radek2212 12720 Delete user and hook confusion when deleting users in Multisite Users 3.0 normal normal Future Release defect (bug) new 2010-03-26T12:42:59Z 2010-06-23T17:24:58Z "Currently: The hook ''wpmu_delete_user'' fires when deleting user in Super Admin->Users. The hook ''remove_user_from_blog'' when deleting user under site Users->Authors & Users. In standard WP: The hook ''delete_user'' is called when deleting users it should be the same in MultiSite when deleting from Super Admin->Users. Or add new hooks and deprecate previous. ''delete_user_from_network'' for when deleting a user totally. ''delete_user_from_site'' for when deleting a user from a specific site. This is hook also then fires in non-MultiSite mode since that then corresponds to one site." andreasnrb 15001 Duplication and incompatibilities in register_new_user() and wp_insert_user() Users 3.0.1 normal normal Future Release defect (bug) new has-patch 2010-09-30T19:16:11Z 2012-09-08T20:39:13Z "As a result of [12778], the commit of a patch that was part of #11644 (the MU-merge ticket), `wp_insert_user()` was modified to introduce user verification checks. The addition of these checks also introduced a number of duplications and incompatibilities between it and `register_new_user()`. (Bear in mind that `register_new_user()` calls `wp_create_user()` which calls `wp_insert_user()`.) These issues include: * Duplication (both run-time execution and code): both functions perform `username_exists()` and `email_exists()` checks. Ideally, we should only perform each check once, and from a single piece of code. * Whereas both functions perform `username_exists()` and `email_exists()` checks, `register_new_user()` performs more checks (empty_username, invalid_username, empty_email, invalid_email). If the former 2 are being checked, all 6 criteria should be checked. * `wp_insert_user()` can now return a WP_Error object, but `register_new_user()` can't handle it (I reported this in #14290) * `register_new_user()` generates a new generic error if `wp_create_user()` (via `wp_insert_user()`) returns an error (assuming proper patch #14290), rather than passing along the more specific error it was told about If an error is returned by `wp_create_user()`, `register_new_user()` throws a generic 'registerfail' error (`'ERROR: Couldn’t register you... please contact the webmaster !'`). However, most likely it received a more informative WP_Error object. * `register_new_user()` allows errors to be suppressed via filters, but `wp_insert_user()` does not `register_new_user()` has the filter 'registration_errors' which allows plugins to suppress any encountered errors. Having done so, `register_new_users()`'s subsequent call to `wp_create_user()` can generate an error (of the type already suppressed) which is then un-suppressable. This renders the 'registration_errors' filter useless for the username_exists and email_exists errors (and possibly other in the future). ---- These different issues may warrant separate tickets, but cumulatively I think they point to the need to refactor `register_new_user()` and `wp_insert_user()` to be more efficient and compatible. This is a rare instance where I don't include an immediate patch for a ticket, but I wanted to get it out there and see if we can try and get these fixed for 3.1. " coffee2code 16001 Invited Users Can Disappear in MS Users 3.0 normal major Future Release defect (bug) new has-patch 2010-12-27T22:37:15Z 2013-04-22T21:56:32Z "Steps to reproduce: * In ''Site Admin'', go to Users > Add New * Add a new user * You get a message to the effect of, said user needs to respond to an invitation. Now the user has disappeared. There's no way for a super admin or anybody to search for that user and add her directly, or delete her, or anything like that. If the user doesn't get the email, she's out of luck: that username and email are now reserved for ""a couple of days.""" filosofo 17793 No explanation on invalid characters on registration form Users 2.1 normal trivial Awaiting Review defect (bug) new has-patch 2011-06-14T08:46:22Z 2012-10-15T19:49:57Z "When a user tries to register with a username containing special characters (e.g. accented letters), WP shows an error message saying ""This username is invalid because it uses illegal characters. Please enter a valid username."". However, this doesn't really help the user because the message does not explain how to fix the problem, i.e. which characters are allowed. Please consider adding a brief listing of allowed characters." molnarm 15498 Notice: Trying to get property of non-object in wp-admin/edit-form-advanced.php on line 281 Users 3.3.2 normal normal Future Release defect (bug) reopened has-patch 2010-11-19T17:40:39Z 2012-06-11T10:58:05Z The problem seems to arise from the fact that when users are imported their old IDs aren't mapped to their new IDs, so then $last_user = get_userdata($last_id) is trying to look up a user that doesn't exist. wpdavis 13569 Odd edge case with shared user tables and custom admin username during install Users lowest trivial Future Release defect (bug) new 2010-05-27T06:06:43Z 2010-11-13T08:04:31Z "1. In install 1, run install.php and use a custom username (NOT called 'admin') and set the e-mail to email@example.com. 2. In install 2, before installing, set up shared user tables with install 1. Then run the installer. You won't have the ability to choose usernames (that's expected). Use the *same* email. 3. Click ""Install."" You'll get hit with a WP_Error object. What's happening? The logic in wp_install() is to do a username_exists() against the username passed to it. If the user exists, it assumes that you're using shared user tables. Problem is, wp_install() is passed 'admin' from install.php (as that's the default, and you don't see the fields when custom user tables are setup), while your user is not called 'admin'. The e-mail address is already being used for another user however, so it is creating 'admin' and is failing on the duplicate e-mail address. If the email address doesn't match any user, I imagine you'd instead get an 'admin' user in your second install, which you could promptly delete. I see no problem with that, as the alternatives are to pick which user should become an admin. So, the fix would be to change username_exists() and the logic that follows, and instead match the e-mail address with an existing user, and make that user the new administrator. If no user with that email exists, we create an admin user and they can tough it out. I do not feel this is a blocker at all. The symptoms I am seeing should be the same in 2.9.2 if you removed the admin user in install 1, then proceeded to share user tables with install 2 before installing. It'd be nice to at least prevent the fatal error and allow the install to finish, however. I do want to get to it in 3.0 if I can, since we now are allowing custom admin names. That said, setting to 3.1." nacin 18360 One of the links in the Password Reset Mail is wrong lizhenry Users 3.2.1 normal normal Awaiting Review defect (bug) assigned has-patch 2011-08-09T15:55:04Z 2012-12-11T00:27:19Z "Hi, just a quick note: if {{{FORCE_SSL_ADMIN}}} has been set to true, a password reset-mail could include the wrong protocol for the site-url while the password-reset-link is correct. - I didn't test it with a blog-network, though. In other words I have both, ''WordPress address (URL)'' and ''Site address (URL)'' set to use the http protocol and in the mail the site-link points to https. greetz, Berny" neoxx 18771 Reset Password link generation Users 3.2.1 normal normal Awaiting Review defect (bug) new close 2011-09-25T16:30:42Z 2011-10-02T16:20:23Z "I have been having problems with the login following a reset password. A user click the ""forgotten password"" link and then after receiving the email clicks the link in the email to reset their password submits their new password gets a message that says ""You have successfully reset your passoword. Log in"" The link for login is not being generated correctly which is causing them to get a ""Invalid Key"" error. Here is what I have dont to temporarily resolve the issue: in wp-login.php I modified the following lines of code: changed Line 207: {{{ if ( empty($key) ) { }}} to this: {{{ if ( empty($key) || preg_match('/[^a-z0-9]/i',$key) != 0) { }}} Removing special characters from the key that gets emailed to the users when they click the ""forgotten password"" link on the login page. Commented out Line 444: {{{ login_header(__('Password Reset'), '

        ' . __('Your password has been reset.') . ' ' . __('Log in') . '

        '); }}} then slightly modified it removing the login link from the message {{{ login_header(__('Password Reset'), '

        ' . __('Your password has been reset.') . '

        '); }}} This change forces the user to return to the homepage before logging in again and then they dont get the ""invalid key"" error. It would be nice if there were a more permenant fix for this issue that wouldn't get lost when we update the next time." binaryweb 17370 Screen options and meta box settings can lose per-blog meta box positions Users 3.1.2 normal normal Awaiting Review defect (bug) new 2011-05-10T21:13:37Z 2011-08-04T21:13:59Z "User preferences for admin interface appearance of the Dashboard and the Edit/Add New pages are stored in per-user options in wp_usermeta: closedpostboxes_$page, metaboxhidden_$page, meta-box-order_$page, and screen_layout_$page, where $page is one of 'post', 'page', or 'dashboard'. Users can customize the order of the Dashboard and editing meta boxes to better suit their workflow using the drag-and-drop AJAX interface to move the meta boxes into ordered columns and the Screen Options tab to show and hide the boxes. Many plugins add custom meta boxes to the Edit/Add New Post page. In a multisite installation, with different plugins active on different blogs, users who rearrange an Add New Post page on a blog with a custom meta box and then rearrange it on a different blog without that meta box will lose the position of the custom meta box. Blogs can have different features and workflows implemented, and having per user options for the appearance instead of per user, per blog options limits the ability of a user to customize the interface. The expected behavior for moving things around is that it changes on one blog, not on all blogs." jmdodd 16833 Signup mechanism shortens usernames without warning Users 3.0 normal normal Future Release defect (bug) new has-patch 2011-03-11T15:09:23Z 2012-08-29T23:40:31Z "When a user signs up for an account on a wordpress blog, if their chosen username is longer than the limit, wordpress chops of the end of the username, without warning the user, and without offering the user the opportunity to choose again. Steps to reproduce: Go to a wordpress blog, sign up with a long username, and read the confirmation email. An example: forum.xbmc.org, which has a limit of 15 characters." hughcharlesparker 18995 Superfluous check in WP_Users_List_Table::display_rows() Users 3.2.1 normal normal Awaiting Review defect (bug) new has-patch 2011-10-19T01:21:11Z 2012-08-05T22:25:26Z "Specifically, this one: {{{ if ( is_multisite() && empty( $role ) ) continue; }}} It seems to have been a misguided attempt to fix something that should have been (and currently is) handled at the SQL level: #12711" scribu 20271 Un-marked up text in the Add Users admin section for multi-site Users 3.3.1 normal normal Awaiting Review defect (bug) new has-patch 2012-03-21T15:17:35Z 2013-01-22T15:21:36Z "When looking at the page for adding a new user on a multi-site setup, the top option is to add an existing user. This text: ""Enter the email address or username of an existing user on this network to invite them to this site. That person will be sent an email asking them to confirm the invite."" has no html markup around it. Immediately above it is an h3 tag. The text should have a

        around it at the very least. My goal here is actually hide the whole section with css for some roles, but I have no way to refer to it." topher1kenobe 18499 User count / roles inconsistency if roles no longer exist but users still do Users 3.2.1 normal minor Awaiting Review defect (bug) new 2011-08-23T13:53:43Z 2011-09-10T09:29:54Z "The count_users logic (from line 833 onwards in wp-includes/user.php) is based on user roles. If the roles were created by a theme or plugin which is then deactivated, wordpress loses count of the users, but still lists them. The behaviour is confusing and inconsistent. See attached screenshot. 1) the user count total at the top (all) ignores the users with no 'active' role, however users are all listed (the users are shown as 'no role' in the list) 2) the old roles are shown in the dropdown selection however are not listed in the totals Suggestions: 1) the total user count should at the very least be correct wrt to the list. 2) Perhaps a total of 'no role' users could/should be shown (since the users are listed anyway ?) 3) If the old roles are shown in the dropdown, perhaps they should be flagged as inactive in some way?" anmari 22367 "Usernames with ""@"" char are assumed email addresses, causing incorrect look-up in several places" Users normal normal Awaiting Review defect (bug) new has-patch 2012-11-06T00:45:19Z 2013-01-10T10:57:23Z "'''Problem''' Usernames containing the ""@"" character are mistakenly assumed to be email addresses when: * wp-login.php - Resetting passwords * /wp-admin/user-new.php - Adding an existing user to a site, in multisite * /wp-includes/user.php - Searching for a user ---- '''Duplicate''' * Create a user with the login ""@testing"" * Verify the account, etc... '''Bug in Search''' * Visit: wp-admin/network/users.php - attempt to search for: ""@testing"" * Result: no users found * What should happen: find the user '''Bug in Add New''' * Visit: wp-admin/wp-admin/user-new.php - attempt to add: ""@testing"" * Result: no users found * What should happen: add the user '''Bug in Reset Password''' * Visit: wp-login.php - attempt to reset password for: ""@testing"" * Result: retrieve_password() accidentally succeeds, because strpos() check returns 0, which is the correct position of the ""@"" character. If the username was ""testing@"" this test would fail ---- '''Solution''' The attached patch fixes these bugs by using is_email() instead of an strpos() for an @ character." johnjamesjacoby 11959 Value Truncation Still Unchecked in registration.php Users normal normal Future Release defect (bug) new 2010-01-20T22:59:50Z 2010-11-13T07:38:28Z Functions such as username_exists() fail to perform sanity checks against the storage schema. As a result, it is possible to register multiple users with the same username, if the length is greater than or equal to the username field size. Only the first user can login, however anyone re-registering that username can impersonate the first user to reset their password. miqrogroove 17723 WP Signon from external resource/php code Users 3.1.3 normal normal Awaiting Review defect (bug) new 2011-06-07T23:30:50Z 2011-06-07T23:30:50Z "Wordpress has a lot of different functions available in the codec, such as the wp_signon. The code to login a user from within the wordpress folder looks like: {{{ $creds = array(); $creds['user_login'] = $username; $creds['user_password'] = $password; $creds['remember'] = true; $user = wp_signon( $creds, false ); wp_set_current_user($user->ID); }}} If this is done outside of the wordpress user folder, by including the wp-config.php file {{{ including the wp-config, like the following: global $wpdb; define('WP_USE_THEMES', false); require_once '/path/to/www/blog/wp-config.php'; wp(); }}} then the cookies aren't created successfully and you can't properly login/logout a user. There are a log of constants that set this up, yet the cookies aren't set properly, you are missing the wordpress_logged_in_COOKIEHASH essential cookie. Such flexible function should work properly " TeckniX 14855 WP_User misses values for some default properties (nickname, rich_editing) Users 3.1 normal normal Future Release defect (bug) new has-patch 2010-09-12T12:16:22Z 2011-12-13T00:04:15Z "WP_User is expected to have default properties like last_name, ID etc. At least two of them are missing in the class definition: 1. nickname 2. rich_editing The attached patch adds them. /wp-admin/user-edit.php does Warnings / Notices if the properties are not set. This is the case for users in the database that have not set these fields as meta data." hakre 20043 WP_User missing magic __unset() method Users normal normal Future Release defect (bug) new has-patch 2012-02-14T19:58:37Z 2013-05-14T13:37:27Z "When the magic methods were put into WP_User in 3.3, !__unset() was skipped. This has the result of unset( $user_data->$foo ); not actually doing anything. Patched against r19926." johnjamesjacoby 24255 WP_User::__set doesn't persist custom fields as it claims Users 3.3 normal normal Awaiting Review defect (bug) new 2013-05-03T03:17:42Z 2013-05-06T11:42:01Z "Looking through `WP_User` in version 3.5.1 (verified against svn trunk too), the magic methods {{{ __get }}} and {{{ __set }}} supposedly read and write from custom fields, per their comment blocks. {{{ /** * Magic method for accessing custom fields * * @since 3.3.0 */ function __get( $key ) { // ... /** * Magic method for setting custom fields * * @since 3.3.0 */ function __set( $key, $value ) { // ... }}} And sure enough, if you look through the method bodies {{{ __get }}} will make a call to {{{ get_user_meta }}} {{{ $value = get_user_meta( $this->ID, $key, true ); }}} However reading through the body of {{{ __set }}}, it never calls {{{ add_user_meta }}} or {{{ update_user_meta }}}, but has the misleading comment that it's ""for setting custom fields..."". Seems to me like it's missing a critical line: {{{ update_user_meta($this->ID, $key, $value); }}} Am I missing something, or is this a bug?" quickshiftin 20824 current_user_can() bug with Super Admin Users 3.3.2 normal normal Awaiting Review defect (bug) reopened 2012-06-04T10:55:53Z 2012-11-28T23:15:06Z "If the logged in user is a super admin this returns true; {{{ if (current_user_can('contributor')) echo 'current user is a contributor'; }}} Normally it should return false as it does for administrator, author, editor and subscriber account types. I spotted this while working in my localhost Multisite install then figured it doesn't work in the live standalone version! " abdessamad idrissi 17381 display_name is not updated if javascript is disabled Users 3.2 normal normal Awaiting Review defect (bug) new 2011-05-11T19:29:37Z 2011-05-11T19:29:37Z "If one has javascript disabled the display name is not updated if the users changes his name. Also plugins that provide user credentials and update the users entry in the database can not determine the users display_name setting. The display_name field should only hold a reference to the style how the name is displayed. That way no javascript would be needed to set the display_name and also plugins can change the users credentials without producing inconsistency or forcing a style for the display name." elmll 9873 enforce a consistent home and siteurl www. pref Users 2.8 normal normal Future Release defect (bug) new has-patch 2009-05-19T12:36:11Z 2012-04-20T12:56:02Z "Seen on a few sites. home and siteurl with inconsistent www prefs prevents the admin user's cookie from getting picked up properly, upon logging in. code I currently use to prevent the issue is this: {{{ add_action('login_head', 'fix_www_pref'); function fix_www_pref() { $home_url = get_option('home'); $site_url = get_option('siteurl'); $home_www = strpos($home_url, '://www.') !== false; $site_www = strpos($site_url, '://www.') !== false; if ( $home_www != $site_www ) { if ( $home_www ) $site_url = str_replace('://', '://www.', $site_url); else $site_url = str_replace('://www.', '://', $site_url); update_option('site_url', $site_url); } } # fix_www_pref() }}} there's probably a better way and a better location for this." Denis-de-Bernardy 23228 get_users() cannot include AND exclude Users 3.5 normal normal Awaiting Review defect (bug) new reporter-feedback 2013-01-17T22:45:51Z 2013-01-19T03:56:22Z "The codex describes the parameters for get_users() as an array of options, so it seems like you can set an array of includes and an array of excludes. But the code looks like it can only do one or the other. It would be a simple fix. Lines 521-527 in wp-includes/user.php {{{ if ( !empty( $qv['include'] ) ) { $ids = implode( ',', wp_parse_id_list( $qv['include'] ) ); $this->query_where .= "" AND $wpdb->users.ID IN ($ids)""; } elseif ( !empty($qv['exclude']) ) { $ids = implode( ',', wp_parse_id_list( $qv['exclude'] ) ); $this->query_where .= "" AND $wpdb->users.ID NOT IN ($ids)""; } }}} To fix, change the elseif to its own if: {{{ if ( !empty( $qv['include'] ) ) { $ids = implode( ',', wp_parse_id_list( $qv['include'] ) ); $this->query_where .= "" AND $wpdb->users.ID IN ($ids)""; } if ( !empty($qv['exclude']) ) { $ids = implode( ',', wp_parse_id_list( $qv['exclude'] ) ); $this->query_where .= "" AND $wpdb->users.ID NOT IN ($ids)""; } }}} Thanks for the consideration." dlim_vernier 23609 get_users() causes a huge number of SQL queries causing 500 server errors Users normal normal Future Release defect (bug) new 2013-02-25T20:56:12Z 2013-05-20T12:04:44Z "Hey, get_users() function causes a 500 server error if no arguments are passed, that is all user information is trying to be read. On my website with over 50k users, it causes ~15k SQL queries (checked using general query log). Atleast one plugin I know of uses get_users() without arguments (Events-manager). This causes the plugin to cause 500 server errors. Ideally, if no arguments are passed, only a select * from {prefix}_users should be issued instead of 15k separate queries. Here's a part from query log which shows individual SQL queries are being made: {{{ 59 Query SELECT wp_users.* FROM wp_users WHERE 1=1 ORDER BY user_login ASC 130226 2:13:11 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (26901) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (43704) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (43674) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (41395) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (41684) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (38434) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (36368) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (24303) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (44830) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (23256) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (44818) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (18293) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (20351) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (28186) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (26348) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (32837) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (21992) 59 Query SELECT user_id, meta_key, meta_value FROM wp_usermeta WHERE user_id IN (45162) }}}" dpacmittal 20095 get_users() doesn't allow hyphens in meta_key parameter Users 3.3.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-02-22T02:29:04Z 2012-02-22T20:01:27Z "When retrieving users with the get_users() function, the meta_key parameter does not work if the key contains a hyphen (dash). For example: {{{ $members = get_users(array( 'meta_key' => 'job-seeking', 'meta_value' => 1, ) ); }}} That will result in no members being found, even though at least one user with a meta_key of ""job-seeking"" with a value of 1 does exist. This, however, will work: {{{ $members = get_users(array( 'meta_key' => 'job_seeking', 'meta_value' => 1, ) ); }}}" mordauk 15115 if filter show_password_field is set to false, you cannot add new users Users 3.0.1 normal minor Future Release defect (bug) new has-patch 2010-10-13T23:49:57Z 2011-01-13T21:42:56Z "Steps to reproduce: 1. add_filter('show_password_fields', false); 2. Try to add a new user, after entering the data you get the error message ""ERROR: Please enter your password.""." pampfelimetten 14290 register_new_user() can't handle WP_Error result from wp_create_user() Users 3.0 normal normal Future Release defect (bug) new has-patch 2010-07-12T21:29:42Z 2011-04-28T14:48:26Z "register_new_user() in wp-login.php does not properly handle a WP_Error object, which is the potential return value from its call to wp_create_user(). wp_create_user() is basically a pass-through to wp_insert_user(). As a result of [12778], the commit of a patch that was part of #11644 (the MU-merge ticket), new checks were added to wp_insert_user() which changed the potential behavior of the function to return a WP_Error object. register_new_user() can thus fail with a FATAL error: {{{ Notice: Object of class WP_Error could not be converted to int in /Users/scott/Sites/wp30.dev/wp-includes/functions.php on line 3150 Catchable fatal error: Object of class WP_Error could not be converted to string in /Users/scott/Sites/wp30.dev/wp-includes/formatting.php on line 2782 }}} Currently it is not likely the above situation would be tripped. But this is only because register_new_user() and wp_insert_user() perform almost identical error checks (the former does more, actually). However, the errors generated in register_new_user() can all be suppressed by plugins via the 'registration_errors' hook. However, some those same error checks will then be performed in wp_insert_user() and thus return a WP_Error (without a way to suppress those). Related issues aside, the fact of the matter is that wp_create_user() can return a WP_Error object and register_new_user() can't handle it. The fix is simple and attached. " coffee2code 15642 user-new input fields stretch to the edge of the screen JohnONolan Users 3.1 normal normal Future Release defect (bug) assigned 2010-12-02T09:01:05Z 2010-12-02T11:59:22Z They shouldn't. nacin 14767 wp_create_user() does not check for a valid email address Users 3.0.1 normal normal Future Release defect (bug) new has-patch 2010-09-02T21:38:23Z 2010-12-01T19:04:25Z "When creating a new user an invalid email address (for example user@) will result in a zero-length string in the email field of the users table. If another new user is subsequently created with another invalid email address the error returned is ""This email address is already registered."" It would be better for wp_create_user() to check if a valid email address has been given and return a more descriptive error. I attach a patch file for wp-includes/registration.php to include this functionality." mrwiblog 21495 wp_insert_user allows a user to be created with empty passwords Users normal minor Awaiting Review defect (bug) new 2012-08-06T02:10:00Z 2012-08-06T02:10:00Z "While looking at the different files where user information is created, I noticed that there are some differences between wp_insert_user(programmatic creation of users) and edit_user (called from the admin). wp_insert_user assumes that a user_pass parameter is included, which creates a user with no password. " ancawonka 14308 wp_insert_user in 3.0 is not backwards compatible Users 3.0 normal normal Future Release defect (bug) reopened has-patch 2010-07-14T21:32:40Z 2010-12-08T19:20:34Z "Prior to WP3.0 the function wp_insert_user would always return an integer or falsy on failure. In 3.0 this function can return either an integer, or an instance of WP_Error. This behavior is not backwards compatible and can result in bad results. A function that expects an integer return value will treat this WP_Error instance as an integer, which results in a '1'. This is the id of the administrator, resulting in possible corruption of the admin account. In particular, calling wp_update_user() with this WP_Error value will cast the error to (int) and operate on the administrator. First line of wp_update_user: $ID = (int) $userdata['ID']; Possible resolutions: best: don't return WP_Error from wp_insert_user - this is not backwards compatible. otherwise: check for is_wp_error() in wp_update_user(), and every other function that takes a user id. " ahupp 23498 wp_list_authors ignores 'exclude_admin' arg when admin account has a display_name other then 'admin' Users 3.1 normal normal Awaiting Review defect (bug) new 2013-02-18T09:37:59Z 2013-02-18T19:03:38Z "Line 293 of author-template.php should be changed from: {{{ if ( $exclude_admin && 'admin' == $author->display_name ) }}} to: {{{ if ( $exclude_admin && 'admin' == $author->user_login ) }}} Thanks." raphaabreu 20845 "wp_set_current_user( null, ""name"") does not work when $current_user is already 0" Users 3.3.2 normal normal Awaiting Review defect (bug) new 2012-06-05T13:11:53Z 2012-06-05T16:10:58Z "According to the documentation for wp_set_current_user() you can Set $id to null and specify a name if you do not know a user's ID. This does not work when the current user has already been set to anonymous ( ID = 0 ) since the following test returns true. if ( isset( $current_user ) && ( $current_user instanceof WP_User ) && ( $id == $current_user->ID ) ) { The last part of the test should be corrected to && ($id === $current_user->ID) ) which will ensure that the test fails when the $id parameter is null, which will allow the rest of the pluggable function to continue and set the current user to the specified $name. This is similar to #19769. Note: the change in 3.4 has not fixed this particular problem." bobbingwide 23005 wp_update_user breaks if ID not set Users 3.5 normal normal Awaiting Review defect (bug) new 2012-12-19T15:18:42Z 2012-12-19T15:47:58Z "Passing an array of userdata to wp_update_user (first_name, last_name, user_email, user_login). If ID is not in the array, then a PHP Fatal Error is triggered: [19-Dec-2012 15:03:16 UTC] PHP Fatal error: Call to a member function to_array() on a non-object in [..]/web/content/wp-includes/user.php on line 1456 The codex for wp_update_user (http://codex.wordpress.org/Function_Reference/wp_update_user) does state ""If $userdata does not contain an 'ID' key, then a new user will be created and the new user's ID will be returned."", which makes me think this might be a new bug." actionnerd 9640 wp_update_user() blindly calls add_magic_quotes(), even on objects Users 2.8 normal normal Future Release defect (bug) reopened dev-feedback 2009-04-24T18:14:53Z 2011-10-12T05:41:40Z "If there's an object stored in usermeta, then the call to add_magic_quotes() will lead to an error in wpdb::escape(): {{{ Catchable fatal error: Object of class stdClass could not be converted to string in /web/ven/wp-includes/wp-db.php on line 472 }}} http://core.trac.wordpress.org/browser/trunk/wp-includes/registration.php See also #9638. The two problems are related, but probably need to be solved independently. " misterbisson 9170 """jQuerify"" adding a new user..." Users normal normal Future Release enhancement new close 2009-02-18T23:11:58Z 2011-02-12T04:43:57Z "After adding a new user it's confusing that only that user is displayed in the table. It always takes me a couple seconds before I realize that it's just showing the new user. It seems it would be more efficient to show all of the users and just have the new row highlighted with jQuery. (I can code this if needed.)" aaron_guitar 21314 Add password reset key expiration Users 3.4.1 normal minor Awaiting Review enhancement new has-patch 2012-07-19T11:30:19Z 2012-07-20T09:59:31Z "Password reset using correct user_activation_key is currently possible forever. Attached is a patch which clears newly created user_activation_key after one week." skithund 22921 Allow get_users() to return array of values via 'fields' parameter Users 3.5 normal normal Future Release enhancement new has-patch 2012-12-13T17:39:24Z 2013-05-16T11:54:18Z "Currently, the `'fields'` parameter in the arguments array for `get_users()` only accepts either an array of user data fields, or the string `'all'`. Both of these options cause `get_users()` to return an array of object comprised of the specified user data. Passing any other string value to `'fields'` causes `get_users()` to return an array of user IDs. Per the Codex: > Array of objects, '''except when fields specifies a single field to be returned, then an array of values is returned'''. If fields is set to all_with_meta, it will return an array of WP_User objects. This statement appears to be untrue, but would be incredibly useful if it were true. Patch adds this functionality to `get_users()`. Potentially related: #18581" chipbennett 17326 Allow new user registrations to be moderated Users 3.1 normal normal Awaiting Review enhancement new 2011-05-05T04:29:10Z 2011-05-05T16:02:57Z "'''Summary''' When registration is open, have the option to require manual approval of user accounts before they are granted default role status. '''Details / Suggested Implementation''' Create a new user role (""Moderated""?) which for all intents and purposes is the same as ""Subscriber"" (`read` capabilities). If opted into, user moderation would assign new users this new role. Administrators would be able to see these users listed under the Users list and click an approve link which would change their role to the default user role (as per the General Settings). This would also make it easier for plugins to implement private blogs while having open user registration. See also: #12030" Viper007Bond 5918 Allow non-ASCII usernames Users 2.3.3 normal normal Future Release enhancement new has-patch 2008-02-19T11:35:20Z 2013-01-19T08:05:21Z "Hello ... I can't make New username with arabic characters ... who i can apply an arabic characters in usernams ? Thank you ..." marshosh 24193 Anti brute force protection Users 3.5.1 normal normal Awaiting Review enhancement new close 2013-04-25T18:07:41Z 2013-04-25T21:46:00Z "To protect against hacking should be added to the login form protection from brute force. Now the password can enter an unlimited number of times. It is necessary to limit the number of login attempts. For example, some variants: 1) Captcha after three unsuccessful attempts 2) Temporary inability to login after three unsuccessful attempts 3) something else " MAzZY 12340 Assign Certain Categories/Taxonomies To Site Authors Users 3.0 normal normal Future Release enhancement new dev-feedback 2010-02-22T23:15:41Z 2010-02-22T23:58:17Z "We all know that WP is more like a CMS compared to just a piece of blogging software, and when it comes to having multiple authors, this is when this enhancement would really shine! :) If it doesn't make 3.0, then I'd hope 3.1 anyway? So basically when you add another user, or alter a users account, the option will be there to check the boxes of whatever category and/or any taxonomies that particular person will be allowed to have posts published in. That's the plan anyway!" markmcwilliams 8296 Auto generate password for new user jamierumbelow Users normal normal Future Release enhancement new 2008-11-20T16:25:53Z 2012-07-26T15:46:14Z It would be nice to have a button that generates a random password to use when you're creating a new user account in the admin section AaronCampbell 23857 Delete User Should Delete Comments Users 3.5.1 normal normal Awaiting Review enhancement new 2013-03-25T07:10:55Z 2013-04-02T04:53:31Z The delete user function should also delete that user's comments or attribute that users comments to the person specified. That way, deletion of accounts goes a lot smoother. jamcat22 19615 Deprecate get_currentuserinfo() Users normal normal Awaiting Review enhancement new has-patch 2011-12-19T20:23:28Z 2011-12-20T18:49:45Z "{{{get_currentuserinfo()}}} is a pluggable function that encourages an ugly pattern in theme files: {{{ global $userdata; get_currentuserinfo(); }}} It can easily be replaced with this: {{{ $current_user = wp_get_current_user(); }}}" scribu 11297 Don't email the admin when he creates a user from the backend Users 2.9 low minor Future Release enhancement new 2009-12-01T12:05:31Z 2011-01-08T18:57:43Z "I just created the user myself. I already know I did it. I don't need to be told again. Emails should only be sent to the admin when a user registers themselves (if that is enabled). They shouldn't be sent when the admin manually creates a new user." caesarsgrunt 13339 Hook on ms-users.php Users normal normal Future Release enhancement new 2010-05-11T11:45:37Z 2010-05-17T15:14:25Z "On WP 3.0 it is possible to add new users as Super Admin, but they do not really assign each instance. So it would be useful when creating the user, if you have a selection of instances that are created and then selecting one with the checkbox where the user should get access. Maybe it is possible to add a hook for add own fields, similar the possibilies on user-edit.php for profile fields." bueltge 12393 Hooks to enable custom login without editing core files Users 2.9.2 low normal Future Release enhancement new 2010-02-26T21:01:06Z 2010-04-23T18:32:10Z "One of the basic features of wordpress is to avoid having users edit core files. It is impossible to properly customise wp-login without manually editing the file directly - not good for upgrades! Need to make login_header function pluggable or add a do_action hook before the tag Need to add a login_footer. In fact what is required was highlighted in #4478 complete with diff file. This was marked as resolved BUT IT WAS NOT! I agree it might be a duplicate of issue #9682 BUT the underlying issue of being able to overwrite the login-header function WAS **NOT** solved. (see recent support forum requests #252094 and #333994) The solution MUST allow a replacement of login header (and even better also a replacement of the tags from the switch statement with a login_footer function which could also be overrided - pluggable). Thanks. In an ideal world need to re-open #4478 to ensure accurate resolution. Thanks" sleepuser 23373 Limiting get_users() results by meta value with LIKE wildcards Users 3.5 normal normal Awaiting Review enhancement new has-patch 2013-02-03T03:07:03Z 2013-02-03T06:56:27Z "I want to limit the results returned by get_users() to a subset of the users based on some criteria that will be stored in the User Meta table (e.g. all users whose first name begins with M). Here arr the args I am passing to get_users(): {{{ ( [include] => [exclude] => [fields] => all_with_meta [meta_key] => last_name [meta_value] => M% [meta_compare] => LIKE ) }}} This is the query the WordPress constructs for me: {{{ [01-Feb-2013 16:01:08 UTC] WP_User_Query Object ( [query_vars] => Array ( [blog_id] => 1 [role] => [meta_key] => last_name [meta_value] => M% [meta_compare] => LIKE [include] => [exclude] => [search] => [search_columns] => Array ( ) [orderby] => login [order] => ASC [offset] => [number] => [count_total] => [fields] => all_with_meta [who] => ) [results] => Array ( ) [total_users] => 0 [query_fields] => wp_users.ID [query_from] => FROM wp_users INNER JOIN wp_usermeta ON (wp_users.ID = wp_usermeta.user_id) [query_where] => WHERE 1=1 AND ( (wp_usermeta.meta_key = 'last_name' AND CAST(wp_usermeta.meta_value AS CHAR) LIKE '%M\\%%') ) [query_orderby] => ORDER BY user_login ASC [query_limit] => }}} ---- As you can see, the LIKE clause is escaped and wrapped with SQL wildcard operators. I can't figure out how to prevent this from happening as what I want is ""LIKE 'M%'"" to be my actually query. Andrew Nacin wp@andrewnacin.com via lists.automattic.com 11:24 am (1 day ago) to wp-hackers Currently, ""LIKE"" prepends and appends wildcards, as in %term%. We could add ""%LIKE"" and ""LIKE%"", though that would not help with the situation where you want LIKE taken literally, potentially without % wildcards at all. (Such as using _ as a single-character wildcard, or looking for case insensitive matching.) Probably the best way to add to this API would be to allow for a 'like_escape' => false; that would accept your value as provided. If you'd like to submit a ticket (and patch), this can definitely find its way into 3.6. Nacin ---- I have prepared a patch to meta.php which allows escaped LIKE and NOT LIKE meta compares to work properly. " mpwalsh8 19821 Make wp_validate_auth_cookie() filterable Users 3.3.1 normal normal Awaiting Review enhancement new has-patch 2012-01-13T09:30:35Z 2012-06-19T16:26:18Z "When WordPress loads, it does not call the same functions as when login form is submitted - instead it uses different ones to validate that authentication cookie is present and valid. Call stack is as follows: {{{ settings.php WP::init() wp_get_current_user() get_currentuserinfo() wp_validate_auth_cookie() }}} When plugin wants to validate some extra things (e.g. decide if user can login by checking user meta), the only way is to replace one of functions defined in pluggable.php - `wp_validate_auth_cookie()` seems to be a good candidate for this. Unfortunately this can be done only once, so now it is impossible to use few plugins which wants to do some extra checks at the same time. Therefore I propose to extend the `wp_validate_auth_cookie()` function by adding `validate_auth_cookie` filter to it - see attached patch. It will allow to hook into the cookie validation process, without the need to replace pluggable function." sirzooro 18132 Misleading message when deleting a user with no sites Users normal trivial Awaiting Review enhancement new has-patch 2011-07-15T17:53:14Z 2011-07-15T18:41:43Z "In multisite, when deleting a user with no sites, the following message appears: Transfer or delete posts and links before deleting users. This is a confusing message because there are no posts or links to transfer/delete. The message should be changed to something else." danielbachhuber 21730 More modular and reusable email validation functions Users normal normal Awaiting Review enhancement new dev-feedback 2012-08-29T16:04:04Z 2012-08-29T19:56:12Z "Email validation, especially as it's handled in Multisite (most of which is verbatim from MU), is pretty messy. We have some functions like `is_email_address_unsafe()` for checking banned domains, but we don't have a parallel function for checking against limited_email_domains. There are no filters outside of `wpmu_validate_user_signup`, which means that if you want to use email validation outside of the normal MS registration workflow and want to tweak the way that it works (see eg #15706, #20459), you pretty much have to roll your own. And there's no single function that a plugin like BuddyPress can use to do all relevant email checks in one fell swoop. The attached patch suggests the following changes: - Put the limited_email_domains check into a function, `is_email_address_allowed()`. - Put filters on the output of this new function as well as `is_email_address_unsafe()`. - Introduce function wp_validate_email_address(), which wraps the following four checks: is_email(), email_exists(), is_email_address_allowed(), is_email_address_unsafe(). - Rearranges `wpmu_validate_user_signup()` a bit so that all email checks (as opposed to username checks) happen together. I'm not married to anything in this particular implementation (the way that wp_validate_email_address() sends back error messages is not particularly beautiful, but I didn't want to introduce a ton of overhead), but I would really like to see some sort of treatment along these lines, to make things more modular and reusable. If something like this gets approved by the devs, I would like to further suggest the following: - Give a similar treatment to username validation - Move the generic validation functions out of ms-functions.php (with function_exists() checks on the MS-specific stuff) I'm happy to work more on this kind of patch, but didn't want to go too far in case it's a non-starter for some reason." boonebgorges 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 12960 Number of posts on the Users page should include drafts and pending review Users 2.9.2 normal normal Future Release enhancement new has-patch 2010-04-11T02:35:03Z 2010-10-27T11:26:31Z "The numbers of posts on the Users page currently only include published posts, which I think is not good enough. For example, I have a contributor who has only written a few drafts and submitted a few articles for review. If I decide to delete him and base my decision on what I see on the Users page, I would probably just go with the ""Delete the user and all his posts"" option, which would delete more than I would expect." archon810 23057 Pass $reassign in the delete_user hook Users 3.5 normal normal Awaiting Review enhancement new has-patch 2012-12-26T05:42:00Z 2012-12-26T06:21:14Z "File: wp-admin\includes\user.php In the wp_delete_user function, there are 2 do_action hooks - do_action('delete_user', $id); - do_action('deleted_user', $id); The $reassign variable should also be passed along. We can then decide what to do when the admin delete a user by ""Delete all posts"" or ""Attribute all posts to: XYZ""." genkisan 22328 Pass reset password URI to retrieve_password_message filter Users 2.8 normal normal Awaiting Review enhancement new has-patch 2012-10-30T23:34:17Z 2012-10-31T11:24:10Z "The arguments for the retrieve_password_message filter are the message itself and the reset key. However the URI requires the user login as well in order to be valid, thus we cannot regenerate the password reset link without it. Proposed solution - pass the reset URI instead of just the key." ejdanderson 18399 Password Strength Meter should usually mark passwords that contain password as weak Users normal normal Awaiting Review enhancement new close 2011-08-13T23:41:11Z 2012-08-15T23:22:51Z "Password (in human and l337 form) is a horrible password. Unless a password is really long, we should mark passwords that contain 'password' as weak. Test Case : password123 returns Strong" jorbin 18743 Persistent redirect_to For Login, Registration, and Lost Password Users 3.3 normal normal Awaiting Review enhancement new 2011-09-22T07:04:39Z 2013-02-19T13:50:21Z "Currently, if redirect_to is passed in to the login screen and then a user clicks Register or Lost Password, the redirect_to gets lost. I think that the redirect_to should be persistent and honored whether the user logs in, registers or gets a lost password. I've written a hacky filter to do this, but I think this ought to be included in the core. Here's what I did: {{{ //Keep redirect_to in URL add_filter('site_url', 'foxyshop_add_registration_redirect', 5); function foxyshop_add_registration_redirect($path) { if ((strpos($path, ""action=register"") !== false || strpos($path, ""action=lostpassword"") !== false) && isset($_REQUEST['redirect_to'])) return $path . '&redirect_to='.urlencode($_REQUEST['redirect_to']); if (substr($path, strlen($path)-12) == ""wp-login.php"" && isset($_REQUEST['redirect_to'])) return $path . '?redirect_to='.urlencode($_REQUEST['redirect_to']); return $path; } }}} (I know 3.3 is in freeze now, but there wasn't another version option)" sparkweb 24273 Provide a way for Theme/Plugin developers to get a list of user contact methods Users normal normal Awaiting Review enhancement new has-patch 2013-05-06T16:15:54Z 2013-05-07T16:02:40Z "When templating an author page it is useful to be able to provide a list of social media links. There's great support for adding custom links using the user_contactmethods filter, but there's no public way to get a list of those contact methods without the user's other info mixed in. There is a private function _wp_get_user_contactmethods(), that does this. Why not make it public? " johnnyb 23413 Provide query result data to custom user columns Users normal normal Awaiting Review enhancement new has-patch 2013-02-07T15:22:53Z 2013-02-16T19:25:01Z "When the filter manage_users_custom_column is triggered, it sends an empty string for the value field. Since it's easy enough to extend the WP_User_Query with extra fields, it would be good to have those fields passed through if they exist to save having to requery the database with the user_id parameter to get the data. I have attached a patch to show what I mean." JohnC28 23368 Random order for wp_user_query Users 3.5 normal normal Awaiting Review enhancement new dev-feedback 2013-02-02T09:24:40Z 2013-02-02T15:42:14Z "Unlike the '''wp_query''', '''wp_user_query misses''' the order by random option. This option is necessary when you have a lot of users and we want to show only some of them randomly in a widget or anywhere on the blog. It would be great to have this option in the next wp release." gandham 16470 Require confirmation on email change Users 3.0 normal normal Awaiting Review enhancement new 2011-02-06T12:07:11Z 2011-02-06T19:06:19Z "When a new user is registered for a site, the e-mail he provides gets easily confirmed. But immediately after that, the new member can visit his profile and is able to change his e-mail to anything. Regardless of whether it is done on purpose or the user enters a wrong e-mail by mistake, the admin cannot contact the member, should he has to for any reason. The e-mail address is of great importance in such cases and I don't think that's a rare need! I've had the impression that WP was not offering this feature, but then I realised that the code lies in core, though restricted to multisite installations. I find it quite difficult to understand why. There might seem to be a relation to #13717, but what I propose hereby is just giving the admin of a single-site installation the '''option''' to activate e-mail change confirmation. I think the implementation would only require a few changes in wp-admin/user-edit.php, making send_confirmation_on_profile_email() available outside of wp-admin/includes/ms.php and adding an option in Settings. Why would we have to hack the core or consider a plugin for something almost already offered in core? That's why I describe the ticket as ""enhancement"", not ""feature request""." linuxologos 16235 Site Welcome Email sent without regard to noconfirmation flag Users 3.1 normal normal Future Release enhancement new has-patch 2011-01-14T19:18:34Z 2011-09-15T23:31:22Z "In multisite and the super_admin adds a new user to a site, if the user is new to the network, WP sends out the welcome email (but not the confirmation of being added to the site) In my client's use case, they were looking for the SBD (silent but deadly) mode, as in no email at all should go out. The language implies there is ""no"" notification but the welcome email belies that language. if even the welcome email should be disabled, then in wp-admin/user-new.php (around line 108) adding `add_filter('wpmu_welcome_user_notification', ''__return_false');` would kill the new user notification from wpmu_activate_signup() (a few lines later) " transom 20221 Skip Confirmation Email option only visible to Super Admins Users 3.4 normal normal Awaiting Review enhancement new dev-feedback 2012-03-12T20:08:13Z 2012-11-22T03:52:17Z "When adding a new user in WordPress Multisite, the ""Skip Confirmation Email"" option is only available to Super Admins. If you enable the ""Add New Users"" featured for site admins, they'll have the ability to create new users under Users > Add New. However the ""Skip Confirmation Email"" option is hidden because they are not a Super Admin. Super Admins and Admins should have the ability to enable this option when adding new users. " williamsba1 17179 Sort user by metadata value Users 3.1 normal minor Awaiting Review enhancement new has-patch 2011-04-19T16:11:57Z 2011-04-19T16:11:57Z "It would be nice to sort users by metadata value, the way it works for posts. For instance: {{{ #!php $users = get_users(array( 'orderby' => 'meta_value_num', 'order' => 'DESC', 'meta_key' => 'score', )); }}} Therefore it needs to add the lines below at line 436 of file wp-includes/user.php: {{{ #!php } elseif( (!empty($qv['meta_key'])) && ( 'meta_value' == $qv['orderby']) ) { $orderby = ""$wpdb->usermeta.meta_value""; } elseif( (!empty($qv['meta_key'])) && ( 'meta_value_num' == $qv['orderby']) ) { $orderby = ""$wpdb->usermeta.meta_value+0""; }}}" ziofix 16318 The reset password process could be clarified Users 3.1 normal normal Future Release enhancement assigned early 2011-01-20T16:27:57Z 2013-01-22T16:51:08Z "I find the process of resetting a user password confusing, and sI guess I am not the only one. Here is why: The fist screen in this process is almost ok: [http://snapplr.com/mbtp] only the text on the button is confusing as users won’t “get a new password” but are going to input a new password (I guess this is an heritage of the past procedure). The second screen is where most users get lost: [http://snapplr.com/811w] I think that the login form should not be visible here as it gets the user’s focus, so they do not see the text above telling them to check their mailbox and do not know what to type here. I know that changes are planned in the reset password process, but these two relatively small changes could make the process a lot easier to follow for users." paolal 24088 Update get_users_drafts() to support custom post types Users 3.5.1 normal normal Awaiting Review enhancement new 2013-04-15T11:17:52Z 2013-04-15T11:17:52Z Currently get_users_drafts() access drafts of 'post' type only. Would be useful if it could support custom post types as well. navjotjsingh 21744 WP_User_Query does not support post type Users 3.4.1 normal normal Awaiting Review enhancement new has-patch 2012-08-31T00:13:59Z 2012-12-22T07:46:03Z "unfortunately WP_User_Query only support 'post' right now. i've attached my modified user.php" AliMH 22212 WP_User_Query( array('role' => $role) ) should accept array or not return anything if array Users normal normal Awaiting Review enhancement reopened needs-unit-tests 2012-10-17T12:37:43Z 2013-03-26T22:52:38Z "I got a small problem with WP_User_Query - i wanted to find users from more then one roles to send them e-mail, so i did {{{ $role = array('role-1','role-2); $wp_user_search = WP_User_Query( array('role' => $role) ); $users = $wp_user_search->get_results() foreach ($user) ... send wp_mail }}} problem is, that role param accepts only string. It would not be a problem if it would return nothing, problem was, that it actually returns ALL users, so i have send my author-only emails to all thousands users in database :-( I know that it is my fault, that i have to read documentation, but i thought, that it works as other wp queries, so if the parame do not fit, it throws error, but it does not." thomask 6405 When deleting users without any links/posts, don't ask to whom they should be reattributed rajnikmit* Users 2.7 normal normal Future Release enhancement accepted has-patch 2008-03-27T01:01:15Z 2013-03-09T12:34:39Z When deleting a user, it asks to whom their links/posts should be reattributed (or if they should be deleted). We can skip this screen if they don't have any links or posts. markjaquith 21982 check wp_authenticate_cookie Users 3.4.2 normal normal Awaiting Review enhancement new has-patch 2012-09-24T06:45:56Z 2012-09-24T06:45:56Z "I am analyzing the authentication system wordpress, caught my atension the function logic `wp_authenticate_cookie` in (`wp-includes/user.php`) and decided to make a very small change. >I made a file of changes: > https://gist.github.com/3774628" fitorec 21043 is_user_logged_in() returns true even if user is not logged in Users 3.4 normal normal Awaiting Review enhancement new dev-feedback 2012-06-21T20:40:13Z 2012-06-21T20:56:54Z "If you have {{{wp_set_current_user()}}}, then {{{is_user_logged_in()}}} will always return true. This goes against my understanding of the role of wp_set_current_user() especially as explained by the documentation: ""Some WordPress functionality is based on the current user and not based on the signed in user. Therefore, it opens the ability to edit and perform actions on users who aren't signed in."" But then we look at {{{is_user_logged_in()}}} and it just says - can we {{{get_current_user()}}}? Suddenly wp_set_current_user is looking like wp_switch_logged_in_user(), which I doubt is the intent of that function. " TomAuger 16860 "map_meta_cap use ""manage_network_users"" instead of is_super_admin for edit_users" Users normal minor Awaiting Review enhancement new 2011-03-15T18:45:07Z 2011-03-15T20:54:07Z "I find that for a multi-site setup, the ability to edit users is inconsistent. there is a capability called ""manage_network_users"", but this cap if given to ""regular"" admin's does not give them the power to edit users. The current code in map_meta_cap in wp-includes/capabilities.php is: {{{ case 'edit_users': // If multisite these caps are allowed only for super admins. if ( is_multisite() && !is_super_admin( $user_id ) ) $caps[] = 'do_not_allow'; }}} removing any flexibility, I would suggest having this based on the ""manage_network_users"" capability, giving us much more flexibility in terms of assigning power to control user administration." sboisvert 23430 sanitize_user() disallows + in usernames causes problem for email as username Users 3.5.1 normal minor Awaiting Review enhancement new has-patch 2013-02-09T08:48:31Z 2013-02-10T15:39:20Z "I want to use email addresses as usernames which seems to work fine, except sanitize_user() doesn't allow a + in the username and my email addresses have + in them. Google/gmail allows one to use a + modifier on emails like so: user+admin@gmail.com, user+editor@gmail.com, user+author@gmail.com, etc... I often use this to get around WordPress's requirement for unique email addresses but it's also intended for and useful in filtering: user+blog1@gmail.com, user+blog2@gmail.com, etc... Is there a reason we can't allow +'s in usernames or could it be moved to the strict case only? See formatting.php:892 " jb510 22310 wp_insert_user bit ilogical with rich_editing Users normal normal Awaiting Review enhancement new 2012-10-30T09:08:56Z 2012-10-30T12:21:17Z "when you do wp_insert_user with rich_editing = TRUE it actually set rich_editing to ""1"" what is then interpreted as FALSE. I know (after searching why it does not work for me), that for actually setting true you need to set rich_editing to empty value, but anyway i think it is not optimal" thomask 17219 Add Existing User - E-mail Notification ( /wp-admin/user-new.php ) Users normal normal Awaiting Review feature request new reporter-feedback 2011-04-22T21:10:17Z 2011-08-07T22:04:12Z "When adding an existing user to a site, we click ""Skip Confirmation Email Add the user without sending them a confirmation email"" to add the user immediately to the site. We've noticed that there is no notification that the user has been added to a new site. Could email notification upon adding existing user be considered? Thanks!" chaos1 12032 Additional Option of Site Admin -> Options -> Allow new Registrations. kallumamaji Users 3.0 normal normal Future Release feature request reviewing 2010-01-26T00:29:42Z 2011-12-29T09:29:57Z "MU Trac Ticket: http://trac.mu.wordpress.org/ticket/799 Right now the 4 options are: Disabled - noone can register a new account or blog Enabled - blogs and user accounts can be enabled (at the same time as the request) Only User Account - Only a user account can be created. Only Logged in User - Cannot create a user account but those who can log in can create a blog. Need a 5th option for Create User Account and Allow blog creation if logged in. With the 5th option it will allow new registrations., but only allow them to request a new blog if they are a valid online user after registration. " wpmuguru 14644 Administrator should be able to change usernames Users normal normal Awaiting Review feature request reopened dev-feedback 2010-08-19T13:57:38Z 2013-04-14T19:26:57Z "I can't think of any reason why administrators shouldn't be able to change usernames. I do this occasionally (via SQL) and find that it causes no problems whatsoever (that I've noticed)." holizz 9568 Allow users to log in using their email address Users 2.8 high major Future Release feature request assigned has-patch 2009-04-17T17:11:28Z 2013-04-11T03:50:35Z "I've been looking into a few tickets and adding patches to things that were potentially problematic when implementing a membership plugin (#1626, #4170, #9563, #9564). The general idea being twofold: to avoid duplicate users at all costs -- because it's a bloody mess to merge users in a billing system. I'm about to embark on a mid-sized patch that renders the WP username field optional. This is a natural next step from #9563 and #9564. Users could then be allowed to specify an email only, when registering. And they could use their email to login -- in addition to their username if they specified one." Denis-de-Bernardy 16911 Member profile management (WP vs BP) Users 3.1 normal normal Future Release feature request reopened 2011-03-21T02:46:09Z 2011-04-15T09:42:50Z "One thing that continuously bugs me in WP is the user management/profile fields, particularly with BP added. A lot has been done in the past releases, but there is apparently still no easy way to quickly customize user profiles and signup forms accordingly beyond the contact methods (without a plugin). Also, the parallel existence of WP profiles and the BuddyPress X-profiles seems redundant and is confusing, in my opinion. User management/Profiles as such aren't only a feature of a social layer. I believe this should be a core feature, not a plugin-feature... " youngmicroserf 12682 Multiple password reset messages dd32* Users 2.9.2 normal normal Future Release feature request accepted 2010-03-23T15:51:01Z 2011-01-07T00:15:50Z "There's a security flaw mentioned in #10006: an attacker can bother users with password reset messages. The problem was reported on Russian support forums by the user receiving hundreds of such messages on his email address. He managed to solve it himself. He also proposed to introduce some kind of timeout for password resetting. Is it possible?" SergeyBiryukov 14460 New Permission for no_user_edit so users with edit_users can't edit it Users 3.0 normal major Future Release feature request new has-patch 2010-07-29T23:28:18Z 2011-12-24T20:23:31Z "I recently experienced a problem where I have an administrator role with full access and a site administrator role with most access including the ability add, edit, and delete users. However, I don't want the Site Administrator to be able to delete users of the role Administrator. The change I'm proposing is a new permission or marker which states that if enabled, this user can't be changed by another user who isn't the same role. If possible, I might try to add the patch myself. This is a fairly important issue which would is interfering with WordPress' use as a content management system, and the only work around I've found is to edit core file." brandon.wamboldt 22624 New current_user_has_role function to work for roles like current_user_can does for caps Users normal normal Awaiting Review feature request new 2012-11-28T22:11:49Z 2012-11-28T23:14:31Z "current_user_can( 'capability' ) is great, but it would save some code and be more reliable if we had something like this for roles as a global function that's easy to get at: current_user_role( 'editor' ) would return true if the user has the editor role, false if they weren't. I'll work on a patch for this when I get a moment, this is just here to remind me and let others know what I'm thinking." sc0ttkclark 22114 Propagating password on change Users 3.4.2 normal normal Awaiting Review feature request new close 2012-10-06T08:30:47Z 2012-10-08T04:54:45Z "After creating an account or changing profile information, it is possible to intercept the changed data in a hook. However, this is not possible for the cleartext psasword, and this is a useful feature especially when propagating a password change over different accounts spanning across different systems (in contexts such as updating the password for phpBB, Prestashop, or any PAM thingie when the WordPress password is changed). Since this feature is by no means possible to implement without core hacks, I am submitting a patch to include this feature in the WP core. This patch proves useful if we are to integrate other software bricks without having to implement SSO using WordPress' architecture. In my context, I need to be able to log-in through WordPress or directly through the business specific back-end. Proposed patch is attached." ChloeD 12461 "Resend Pass to users from ""admin > users""-list" Users 2.9.2 normal normal Future Release feature request new 2010-03-02T15:23:32Z 2010-03-02T17:34:01Z "In some of my projects i got the case, that i have to resend the password to some of my users (in this cases WP is used as a CMS). So i needed a possibility to resend (better would be: reset) the pass. Currently i'm stuck with a custom admin-UI on a template-page that contains a list of users (each in a row). Currently i got the follwing (in a custom list/table of users) for each user at the end of the -row: {{{ $user_login = isset($_POST['user_login']) ? stripslashes($_POST['user_login']) : ''; echo 'ID . ';user_pass;' . $wpdb->users . '"">' . '

        ' . 'user_login . '"" size=""15"" tabindex=""10"" />' . '' . '
        ' . ''; }}} This makes it possible to resend the wp_mail to ask the user to reset the pass. I'm not the best at php, so i couldn't achieve any sort of bulk managing this, so i set the target to blank. I hope this function get's into the user-quickmenu. As i stated before: It would be great if you could reset the pass, so the user get's a new pass in an instant." F J Kaiser 21128 Sort Users by Sites Users 3.4 normal major Awaiting Review feature request new 2012-07-01T18:10:12Z 2012-07-01T18:57:16Z In wp-admin/network/users.php please add the option to sort users by site name. jsaf 12705 Suggest add new filter to wp_insert_user() Users normal normal Future Release feature request new 2010-03-25T13:59:20Z 2010-03-26T00:46:48Z "Now, there is no way to change new registration workflow. When every attribute is valid, user registration is approved. I want to add filter to interrupt this workflow to wp_insert_user(). Such as: // in registration.php line 105 $userdata = apply_filter(filter_name, $userdata) if( !$userdata ) return I want to use this filter to interrupt normal registration flow." nkucyd@… 16020 Upload custom avatar for user in Dashboard nacin Users normal minor Future Release feature request reviewing dev-feedback 2010-12-29T08:07:53Z 2013-01-29T20:18:15Z It would be nice to be able to upload a custom avatar for a user in the WordPress Dashboard rather than making each user sign up for a Gravatar account and upload the image to that account. computerwiz908 8911 Use $WP_User as the standard unit of user information jeremyclarke Users normal normal Future Release feature request new 2009-01-21T19:51:14Z 2011-08-04T23:15:43Z "Right now much of the core code and most plugins use the old get_userdata() function to fetch information about users. This works okay for most cases but fails to take advantage of the new $WP_User object type. Using the objects makes the user information much more powerful because you can immediately call methods like $user->has_cap('edit_posts') without messing around. It also just makes sense, and not using the pretty object is silly. In some places, like edit-user.php, where more functionality is needed there are functions like get_user_to_edit() that make use of the $WP_User object. I think that WP should clearly move towards always using the modeled object version rather than the straight db version in all places, and encourage plugin authors to do the same. Luckily the $WP_User wrapper uses get_userinfo to fetch its data and rewrites all the elements into its first level, so effectively the resulting object from $WP_User has all the same data as get_userinfo() and thus deprecates perfectly in all situations. My proposal would be to create a new wrapper function to be used instead of get_userinfo(): {{{ get_user($id, $name = '') }}} This would just initiate the object and return it, similar to get_post. It's also fits much better in the overall naming conventions of wp with friends like get_term. If possible, it might also be good to move the actual database sql from the get_userdata() function into the $WP_User object definition somewhere, that way its all in one place. Looking at it now it also seems like the whole _fill_user() function thing could be done more elegantly to explain itself and the cache better. [problem: pluggable.php has get_userdata(), which complicates things] Finally, since get_userdata() currently calls _fill_user() every time then fetches all meta_value/key's for the user, wouldn't it be faster to make just one db call that fetches the row from wp_users AND the values from the usermeta table? If you are checking 30 users on your page for some reason (say, a twitter style list of your authors in the sidebar) that would save 30 database connections, which makes a difference no matter what! [probably should be in another ticket, but it would also be great to have access to a global function get_users() that fetched a set of users (say, active ones or a specific role) all at once based on criteria like get_terms() or get_posts(), it would save time if you are getting many users and if it added them all to the cache after fetching it would probably be a lot faster than checking each user individually] I'm very interested in feedback. I'll try to work on a patch at some point soon (mental note: before 2.8 feature freeze)" jeremyclarke 14412 User Registration via Templates Users 3.0 normal normal Future Release feature request new 2010-07-25T00:21:41Z 2010-08-03T00:35:36Z "To improve the vast multitude of WP installtions that utilize member registrations, I suggest and implore the development team to improve user registration via templates. The reasons are as follows: - More secure - More flexible - Better customization options - Better integration I was prompted by this post: http://www.cozmoslabs.com/2010/05/31/wordpress-user-registration-template-and-custom-user-profile-fields/ the development of Hooks and Filters has made it relatively easy to make such improvements system-wide." GuruXL 23045 WP_User_Query features Users normal normal Awaiting Review feature request new 2012-12-22T06:14:45Z 2013-02-02T11:20:46Z WP_User_Query does not updated recently and due to more use of wordpress as CMS needs of custom query per users increased, WP_User_Query lack post type support(i add a ticket for it #21744) lack taxonomy/multiple taxonomies query and alot others, maybe its time to update WP_User_Query like WP_Query. it's really a need for common works these days. AliMH 20606 orderby rand param does not work with either WP_User_Query or get_users Users 3.2.1 normal normal Awaiting Review feature request new 2012-05-02T22:12:34Z 2012-05-15T19:20:21Z "Using WordPress 3.2.1 {{{ $contributors = get_users(array('role' => 'contributor', 'orderby' => 'rand', 'number' => 3)); }}} {{{ $wp_user_search = new WP_User_Query(array('role' => 'contributor', 'orderby' => 'rand', 'number' => 3)); $contributors = $wp_user_search->get_results(); }}}" kjmeath 11344 'Show' link doesn't appear for about 10s after 'Crunching' is finished. Upload 2.9 normal minor Future Release defect (bug) new has-patch 2009-12-06T12:48:23Z 2011-02-06T07:24:00Z "After uploading an image, the 'Show' link doesn't appear for about 10s after 'Crunching' is finished. Firefox 2.5.5, WP r12320 (but applies to all versions)." caesarsgrunt 5953 Absolute upload_path fails tellyworth Upload normal normal Future Release defect (bug) reopened 2008-02-22T05:39:43Z 2009-11-20T20:03:34Z "1. On Options/Misc, enter ""/tmp/foo/bar"" as a value for the upload path setting. 2. Write a new post and attach an image. Expected: the image file should be stored as /tmp/foo/bar/2008/02/file.jpg or similar. Actual: a 'tmp/foo/bar' subdirectory is created within ABSPATH (if that's possible) and the file is stored there. Both the filesystem path and URL path just append '/tmp/foo/bar', so you get 'ABSPATH//tmp/foo/bar/2008/02/file.jpg' and 'http://example.com//tmp/foo/bar/2008/02/file.jpg' An absolute upload_path should probably be rejected unless you also specify an upload_url_path, because there's no way to know what URL corresponds to an arbitrary filesystem path. " tellyworth 22363 Accents in attachment filenames should be sanitized Upload 3.4 normal normal Future Release defect (bug) new has-patch 2012-11-05T15:51:12Z 2013-05-21T19:52:34Z "There is an inconsistency in the way WP is sanitizing post slugs and attachment filenames. Sanitizing the post slugs is a Good Thing(tm) for non-english users who use diacritics in their post titles. Example: If I write a post with the title ""Moiré patterns"", the actual page slug will be: ""moire-patterns"". The space is replaced with a hyphen, the ""é"" becomes ""e"". Even if I try to change the slug manually into ""moiré"", WP won't let me (for my own good, since that URL would break in lesser capable browsers). For some reason, WP doesn't apply that error-correction to attachment filenames. Example: If I attach a file named ""moiré pattern.png"", it gets renamed into ""moiré-pattern.png"". We can see that the space (and some other forbidden characters) are corrected by `sanitize_file_name()`, but diacritics such as ""é"" or ""ä"" are left as they are. Currently, most modern browsers are capable of displaying files with diacritics, but some of them still fail (most prominently, Safari). For the sake of cross-browser compatibility, attachment filenames should benefit from the same safety measures that we apply for the post slugs (I guess that's the `remove_accents()` function)." tar.gz 16820 Browser uploader in media library shows no error information Upload 3.1 normal minor Awaiting Review defect (bug) new dev-feedback 2011-03-10T11:45:54Z 2011-03-11T04:53:19Z "In `wp-admin/media-new.php`, if you use the browser uploader, you get no information about errors. For example if the file you upload is too large, you just get redirected to the media library with the message ""Error saving media attachment."" Not very helpful - and also inconsistent - because if you do exactly the same thing using the pop-up image editor (i.e., select ""Add an Image"" from the Upload/Insert menu while editing a post), then you do get useful error information. I propose that if there are errors, the user should not be redirected to the Media Library. Instead Wordpress should wp_die telling them what went wrong." solarissmoke 22150 Customizer: Remove Image doesn't remove from Media Library Upload 3.4 normal minor Awaiting Review defect (bug) new 2012-10-10T05:35:15Z 2012-11-10T07:58:22Z "After uploading an image using the Theme Customizer, a ""Remove Image"" link appears - this seems to imply that clicking it will cause the image to be deleted entirely, rather than just hidden from the current view. " pento 20330 Differences between creating folders for plugins and uploaded media (problem with safe_mode) Upload 3.3.1 normal normal Awaiting Review defect (bug) new 2012-03-30T10:27:56Z 2012-04-04T16:26:08Z "After installing 3.2.1 (into subdirectory test) there is missing URL path in menu Media - Store uploads in this folder. But nevermind, I am not sure if this is a bug or expected? I tried to update Akismet automatically, no problem (only FTP credentials required). I tried to install new plugin automatically, also no problem. Directories are created, plugins installed. But when I try to upload some media files, there is following error: {{{ ""Testing-picture-50g.jpg"" has failed to upload due to an error The uploaded file could not be moved to /data/www/h/domain.cz/public_html/test/wp-content/uploads. }}} When I look at ""uploads"" directory - there is CHMOD 775, but I ""Cannot change attributes of remote files!"" When I delete this folder and create it manually, then everything works. But it is not possible to organize media into month- and year-based folders, because they are not working when created automatically by WordPress. And I suppose there is some kind of problem in the way how creating folders for uploading media works. Yes, hosting is limited with safe_mode, but why creating folders and installing plugins works without problem and creating folders for uploaded media does not work? We had several reports from different users about problems with uploading media and this is the only clue I could find. Maybe there is something which was fixed for updating processes, but not for uploading media (especially for creating directories). Any idea? Also automatic upgrade to WP 3.3.1 works well. But in 3.3.1 there is probably a bug, because picture is not uploaded, but there is no Error reported (as in 3.2.1). It looks like media file is uploaded, but only media post is created and file is not uploaded (there is no thumbnail (only icon of missing picture). I suppose, that users should be notified what is going on here? Summary in the end: 1) In WP 3.3.1 there is no error for users after unsuccessfull media upload and there should be (regression from 3.2.1). 2) There are different ways to create folders for updating/installing plugins and creating folders for media uploads and the second way does not work when safe_mode is on." pavelevap 11946 Ensure image MIME type matches extension Viper007Bond Upload 3.0 normal minor Future Release defect (bug) reopened needs-refresh 2010-01-19T08:02:17Z 2012-07-26T22:55:00Z "Take a bitmap (BMP) and rename it to `.png`. WordPress will say it's an `image/png` everywhere you look. This can cause issues if you're trying to manipulate it (thumbnail it, etc.). We should either fix the extension or reject it." Viper007Bond 23188 Hardcoded relative url 'async-upload.php' in plupload/handlers.js Upload 3.5 normal normal Awaiting Review defect (bug) new 2013-01-12T11:47:48Z 2013-01-14T08:19:23Z "On line 127 in plupload/handlers.js you can find relative path to 'async-upload.php'. It rather should use wpUploaderInit.url (or something like that), so you could use WP Plupload in front-end for example or with your custom uploading scripts. Now you can write your custom uploader script and provide it via wpUploaderInit, but on that line in handlers.js it is ignored (and if you run it in front-end, bad request to ./async-upload.php is made)." drozdz 12532 Image Upload Does Not Display Errors Upload 2.9.2 normal normal Future Release defect (bug) new reporter-feedback 2010-03-06T15:56:36Z 2010-11-13T07:49:17Z "This has been a long standing problem for me. I am having problems with uploaded images and am unable to properly troubleshoot because the image upload feature does not display errors. The root problem is that the image upload feature does not display error messages. The symptoms are that thumbnail images are not being generated and my theme (AutoFocus) cannot display EXIF data for images. I have switched to the default theme, disabled plugins and performed other troubleshooting activities (http://wordpress.org/support/topic/164999?replies=1). Scenario: I am uploading a 800x600 143KB color JPEG image. The Flash upload tool shows the status bar going to 100%, Crunching... and then stops once the bar clears itself and the ""Save all changes button"" appears. Nothing else happens. No image thumbnail is displayed, no image information (titles and descriptions) is displayed. When I close out the 'Add an Image' window and reopen it I can see the image in the Gallery but there are no resized images available (thumbnail, medium, large) and the full size dimension is listed as 0x0. When I choose to Edit Image I get the error ""Image data does not exist. Please re-upload the image."" I repeat the upload process using the browser upload method. Once the image is uploaded the 'Add an Image' window is cleared and is left blank. Closing the window and going into the Gallery yields the same results as the Flash method above. WordPress 2.9.2 General * OS: Linux * Server: Apache/2.2.3 (Red Hat) * Hostname: blog.radian.net * IP:Port: 76.12.173.65:80 * Document Root: /vservers/h77483wp/htdocs PHP * v5.1.6 * GD: bundled (2.0.28 compatible) * Magic Quotes GPC: Off * Memory Limit: 16.0 MiB * Max Upload Size: 30.0 MiB MYSQL * v5.0.77 * Maximum No. Connections: 100 * Maximum Packet Size: 1,024.0 KiB * Data Disk Usage: 3.8 MiB * Index Disk Usage: 283.0 KiB I will attach a ZIP file with the image in question (other images have the same problem) as well as images of the upload windows and WP administration panels. " drgdc 20936 Image upload - HTTP error Upload 3.3.2 normal major Awaiting Review defect (bug) new 2012-06-13T08:40:59Z 2012-06-13T21:24:05Z "Unable to upload some type of images, because crunching error. Reproducation: Try to upload attached png image (SC20120611-160917.png), to wordpress site (3.3.2). I try it all of my wp sites, and fresh installation (without plugins). The upload progress aborted (HTTP error). If you convert the png file to jpg, the upload and crunching was succeed (there is no configuration errors i think). I try some workarounds too, but doesn't help (this is not an individual problem i think): http://wordpress.org/support/topic/http-error-on-image-upload-still http://wordpress.org/support/topic/flash-uploader-logs-out-during-crunching-phase?replies=19 This error affected 3rd party tools (like android wordpress app). " voji 17547 Image upload issues - Size reported as 0x0 Upload 3.1.2 normal critical Awaiting Review defect (bug) new dev-feedback 2011-05-24T08:27:21Z 2012-05-16T17:35:28Z "When I upload any image of any size to my wordpress installation the image uploads fine, but the size is reported as 0x0 and has only one option of inserting it as a full-sized image! Further inspection of this issue has led me to believe that it lays with wordpress not inserting the correct (if any) meta data for the attachment into the database. As you can see in the image below, the meta data is present and this image shows all options of inserting the image in the post at all sizes specified in the WordPress media settings panel. http://www.millerswebsite.co.uk/images/meta%20data.jpg But as you can clearly see from the image below, when the meta data is missing it shows you can't post the image at any size except full which is stated as 0x0px - Clearly something is wrong! http://www.millerswebsite.co.uk/images/no%20size.jpg Many people have had and are still having this issue since 2.5. There are quite a few forum threads relating to it with not a single word from anyone from WordPress. Several tickets have been submitted to the WordPress Trac system with the issues going unresolved. This is a major problem and many people have reported it, yet nothing seems to have been done. Sources : http://core.trac.wordpress.org/ticket/12532 http://wordpress.org/support/topic/cant-adjust-media-file-size-since-upgrading-to-27 http://wordpress.org/support/topic/images-upload-fine-but-wp-shows-0x0-size http://wordpress.org/support/topic/add-image-size-only-allows-fullsize-with-0x0-dimensions http://wordpress.org/support/topic/image-upload-in-wp-28-with-translation If any solution exists to this problem, please let me know, I have been searching for weeks now to no avail. When I talk about solutions, I do not mean using plugins to ""regenerate thumbnails""! Yes I know this works, but it does not solve the problem as its only a temporary fix. Plus it needs to regenerate the images every time you upload a new image. Side note : I have tried a completely new installation of WordPress with and with out plugins on a completely different database. I have uploaded and re-uploaded the WordPress files also. This is the type of image I am uploading. I took it on my Nikon D3100 and compressed to 80% @ 960x768 which makes it 83KB so it's not exceeding any upload limits and I am still having problems. http://www.millerswebsite.co.uk/images/wordpress/DSC_2165.jpg My host claims it is not their fault and they have recompiled apache and php for me, the php memory limit is also set to 128mb and file upload size is limited to 8mb. A phpinfo() can be seen here : http://www.millerswebsite.co.uk/info.php My original complaint can be seen on the forums here : http://wordpress.org/support/topic/image-upload-issues-size-reported-as-0x0?replies=10" David_Miller 13659 Incorrect permissions created by wp_mkdir_p() when safe mode is used Upload 2.9.2 normal normal Future Release defect (bug) new reporter-feedback 2010-05-31T16:38:00Z 2010-09-23T18:06:56Z "When safe mode and sgid directories are used, the function wp_mkdir_p() frim wp-includes/functions.php will failed to create to create a directory with correct permissions. How to test the problem on wp_mkdir_p() function: - Create a directory, set the permission to 02777 - Put the file named poc.php in this directory - safe_mode is on, safe_mode_gid is on - php (apache) is run by a user other than the file owner - call the poc.php script via an url Result: Sub-directory /1/2/3/4/ hasn't been created due to safe mode restriction. Explanation: Any file or directory created in a sgid directory inherits the group owner. When safe mode is used, chmod() cannot set the SUID, SGID and sticky bits and the chmod() calls will remove the expected permission. Patchs: There is a least two possibilities: * Don't call chmod at all (Need to check if non Unix system, Windows, is affected). * Don't call chmod if safe_mode is enable and sgid permission is present" cgrenier 13765 It's unclear why a max upload size limit is set Upload 3.0 normal normal Future Release defect (bug) new 2010-06-07T13:39:17Z 2010-11-13T08:06:49Z "When you reach your allowance for file uploads in a multisite environment, it's not clear why WP will advertise a tiny upload size limit. For instance, if you can upload up to 10MB of files, with a 2M file size limit, and you've already uploaded 9MB, WP will erroneously report that you can upload up to a 1MB file. This can lead a multisite newbie to look into php ini files and the like, in order to identify which obscure setting is messing things up, instead of heading straight to the multisite options. Instead, WP should report that the maximum file size is 2MB, and highlight in a follow-up line that only 1MB is available until the quota is reached." Denis-de-Bernardy 23895 Max upload size 0 when post_max_size = 0 Upload 3.5.1 normal normal Awaiting Review defect (bug) new 2013-03-29T15:01:32Z 2013-03-29T16:00:11Z "As a convention, post_max_size can be set to 0 to disable any limitation on max post size. Quote from php.ini: {{{ ; Maximum size of POST data that PHP will accept. ; Its value may be 0 to disable the limit. It is ignored if POST data reading ; is disabled through enable_post_data_reading. ; http://php.net/post-max-size }}} WordPress does not take this into account in wp-admin/includes/template.php " moscar09 15655 Media Upload form does not pass tab name nacin Upload 3.0.2 normal normal Future Release defect (bug) reviewing 2010-12-03T00:00:01Z 2011-11-22T16:52:58Z "The Media Upload form has an error (wp-admin/includes/media.php line !#1538). It is not passing the tab name, which hinders adding actions based on which Upload tab is selected. Error: Get param 'tab' is being set to 'type' which is incorrect. {{{ $form_action_url = admin_url(""media-upload.php?type=$type&tab=type&post_id=$post_id""); }}} Fix: To top of function add: {{{ global $tab; }}} Change the form action URL (line !#1538) to: {{{ $form_action_url = admin_url(""media-upload.php?type=$type&tab=$tab&post_id=$post_id""); }}} This change also impacts function media_upload_type_url_form (line !#1591). Same fix applies." jackcrosby 18474 Misleading error message when theme ZIP exceeds post_max_size Upload 3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2011-08-18T16:16:03Z 2011-08-23T22:46:14Z "''post_max_size'' is 32MB, now try to uploading a 40MB big ZIP. You will get the ''Are you sure you want to do this? Please try again.'' message. But ''try again'' will not help. Notice: ''Warning: POST Content-Length of 47774864 bytes exceeds the limit of 33554432 bytes in Unknown on line 0''" ocean90 22403 Prevent default browser behavior with Plupload disallowed file extensions Upload 3.3 low minor Future Release defect (bug) new 2012-11-10T05:42:05Z 2012-11-11T14:16:31Z See #22149. When Plupload is set to accept only certain file types, the drag event falls back to the browser's default behavior. That means HTML files replace the entire viewport, ZIP files get re-downloaded, etc. Ideally, our own handlers intercept such a drag event and prevents anything else from happening. nacin 6768 Punctuation can break photo uploads Upload 2.5 normal normal Future Release defect (bug) new 2008-04-18T08:22:58Z 2009-11-23T21:22:50Z "I'm doing a lot of photo uploads, and I came across a file I named 'Taking a picture of me?.JPG' - I'm using Mac OS X, so a filename containing a question mark is legal. I don't have Windows running right now, but I'm pretty sure it's disallowed there. Anyway, I tried uploading this picture, and although the image uploader accepted it, and the progress bar completed, it never built a thumbnail for the picture (see attachment 1). The image is absent when viewing the gallery on a WordPress page, but when browsing the media library, it seems to know the item exists (see attachment 2). I blurred out my path information, because that's apparently a good idea. Renaming the file to 'Taking a picture of me.JPG' allowed it to upload without any issues. I'm using Safari 3.1.1 on Mac OS X 10.5.2. Am hosted with Dreamhost. Let me know if I can supply any more details. :) Thanks!" flammable 16191 Uploaded files with quote marks in the filename are undisplayable in MS Upload normal normal Future Release defect (bug) reopened dev-feedback 2011-01-11T19:28:49Z 2011-01-14T03:17:05Z "If you upload a file with quote marks in the filename, e.g. `""Test"".jpg`, WordPress records the filename as `%22test%22.jpg` but the file is called `""Test"".jpg` (on 'nix-like systems anyway) so is undisplayable. I'm unsure about the implications (security and otherwise) of my suggested patch (attached), so please give feedback. (I guess the other approach would be to retain the url-encoded characters and ensure that the file is named with the URL encoded version of the filename.)" simonwheatley 19374 Uploader uses wrong path when inserting images Upload normal normal Awaiting Review defect (bug) new has-patch 2011-11-27T23:09:36Z 2011-12-19T19:55:20Z "== Issue: == I recently had someone whose WordPress install I take care of tell me that when they went to upload images, they weren't being shown. At the time, she was using a svn copy that hadn't been svn up'd in a few weeks. I noticed that the uploads were being stored in the right location, but the uploader was using the default `wp-content/uploads` location when it inserted it into the post, causing the images to not show up. I just confirmed that this still exists in r19456. It happens with all plugins deactivated and on the default theme. == To replicate: == 1. On the options-media.php, change the upload path to something of your choosing. For mine, I chose `/usr/home/user/domains/my-domain.com/public_html/wp-content/my-uploads/` 2. If needed, created the folder and adjust permissions. 3. Create a new page/post, upload an image, and insert it into the post. Take note of the address, it should be wrong according to the newly set upload path. 4. On the server, check the new location, as well as wp-content/uploads. The file will be in the new location (as expected), and not in wp-content/uploads." ryanmurphy 8754 Uploading images whose dimensions are greater than the maximum size allowed fail to generate thumbnails and no error/failure message is displayed. Upload 2.7 normal normal Future Release defect (bug) reopened 2008-12-30T02:50:09Z 2011-08-05T08:31:26Z "The process of uploading images that have dimensions (physical size) greater than the maximum size allowed by the global setting will fail part way through the process without an error or failure message being displayed. Example: Uploading a JPEG image with a width of 625 pixels and height of 938 pixels. This physical size is greater than the maximum size allowed by the default WordPress configuration. When uploading such an image using the ""Add an Image"" panel the the Flash uploader will stop with the upload progress bar at 100% and displaying ""Crunching…"". The Browser uploader will return a blank ""Add an Image"" panel display. In both cases the images are uploaded to the appropriate directory on the server and appear when the post's media gallery is refreshed. Thumbnail images are not generated for these uploads. It appears the failure is before or during thumbnail generation. Note: The maximum image dimension allowed for upload is not the same as the Administration > Setting > Media > Large Size: Max Width and Max Height settings. In my case these settings are both set at 1024 pixels (above the size of the image I am working with). It appears this control panel setting only impacts the HTML image tag attributes for posts, so as not to break the visual design with images that are wider than a layout allows. Now you may ask what is the default maximum dimension for uploaded images. Unfortunately I cannot find my notes on where exactly the setting is in the WordPress code (it has no Web GUI access that I am aware of). I had changed this setting once to work around this problem and hoped 2.7 would have fixed the issue. It is a pain to track down as the location of this setting has changed over time as it moved to different files and functions with each new version of WordPress. My understanding is that this maximum image dimension setting was set to prevent images over 3 megapixels from being uploaded since those are really big and readers shouldn't have to deal with such images. This is old thinking from before broadband and photo blogs took off. See: http://lorelle.wordpress.com/2007/03/28/wordpress-thumbnail-size-limit-hack/ I think the default limit should be raised, but that would be a feature request. This ticket is to have error messages displayed. " DRGDC 12756 WPMU does not handle files with two or more dots in the filename wpmuguru Upload 2.9.2 normal minor Future Release defect (bug) reopened has-patch 2010-03-29T07:23:50Z 2012-11-03T22:59:51Z "* WPMU does download images that have two or more dots in the file name > E.g., One..jpg One...jpg One....jpg rewrites do work (checked) * this is clearly a WP issue: > /wp-content/blogs.php ... $file = BLOGUPLOADDIR . str_replace( '..', '', $_GET[ 'file' ] ); if ( !is_file( $file ) ) { status_header( 404 ); die('404 — File not found.'); } ... > WPMU removes two dots!!! > workaround: $file = BLOGUPLOADDIR . $_GET[ 'file' ]; // name.ly: workaround for files with two or more dots tested and works fine " Namely 23363 When uploading batches of photos oversized photos fail silently Upload 3.5.1 normal normal Awaiting Review defect (bug) new 2013-02-02T01:52:42Z 2013-02-02T03:28:47Z "Summary: When uploading a batch of photos as part of a gallery, some of which are larger than the maximum allowable, the photos under the maximum size upload successfully while the photos that are too large fail silently. Steps to Reproduce: 1. On a post or page, click ""Add Media"" button 2. Click ""Create Gallery"" and ""Upload Files"" 3. Click ""Select Files"" and select several files, some of which are larger than the maximum allowable file size, and some which are smaller 4. Press select Expected Results: Either no files upload (as some are to large to upload) or the files small enough to upload upload successfully (as is the current case) ''and'' an error is displayed stating which photos cannot be uploaded and why. Actual Results: Only the photos that are small enough to be uploaded upload successfully while the photos that are too large fail to upload with no explanation, before, during, or after the upload process. Browser: Safari 6.0.2 on Mac OS" davidwillmore 17812 "media_upload_form_handler runs twice when editing attachment from ""From Computer"" media upload tab (browser uploader)" Upload 3.1.3 normal normal Awaiting Review defect (bug) new has-patch 2011-06-15T18:48:58Z 2012-08-05T22:14:25Z "After uploading a new media item ""From Computer"" using the browser uploader, you are presented with a form to edit its fields. Clicking ""Save all changes"" from this form causes {{{media_upload_form_handler}}} to run, then {{{media_upload_gallery}}} (presumably to redirect to the gallery tab), which then causes {{{media_upload_form_handler}}} to run again. This can cause problems for {{{edit_attachment}}} actions that only run once and alter the posts table row for that attachment (since the subsequent {{{media_upload_form_handler}}} could overwrite whatever changes were made in the action if they don't match whats in {{{$_POST}}}). If the only reason {{{media_upload_gallery}}} is being called from the other type upload handler is to redirect to the gallery tab.. perhaps this patch is a better approach." jeffstieler 15955 move_uploaded_file mangles non-ascii characters on Windows platforms Upload 2.0 normal normal Awaiting Review defect (bug) new 2010-12-22T22:15:46Z 2013-02-23T00:46:30Z "The `sanitize_file_name` function is not filtering alot of character entities like the degree symbol, this results in invalid media item paths, see the attached images. wp-includes/formatting - Line 677 {{{ $special_chars = array(""?"", ""["", ""]"", ""/"", ""\\"", ""="", ""<"", "">"", "":"", "";"", "","", ""'"", ""\"""", ""&"", ""$"", ""#"", ""*"", ""("", "")"", ""|"", ""~"", ""`"", ""!"", ""{"", ""}"", chr(0)); }}} This array is not dealing with invalid entities that could be used in a filename, and the regular expression further down is not catching these either. wp-includes/formatting - Line 700 {{{ if ( preg_match(""/^[a-zA-Z]{2,5}\d?$/"", $part) ) { }}} See attached images, i used 4 varying names with unusual entities in them(each a copy of a sample jpg image). Using a filter on the valid chars array results in the extension getting stripped off but the file still makes it through the upload routine however(which is worrying). I'm no file validation expert, so i'm not sure if this is a critical problem(marked as normal), i'll leave this for you chaps to decide. '''NOTE:''' Ignore my hostname in the screenies, it's a 3.0.3 installation, i'm just lazy with updating my virtual host settings. See screenshots for steps to reproduce(just create a file with some dodgy character entities and upload it basically)." t31os_ 15924 Add 'media_default_link_type' option to parallel 'image_default_link_type' Upload normal minor Future Release enhancement new dev-feedback 2010-12-20T21:12:12Z 2012-01-26T15:30:55Z "It is often recommended that site owners change the 'image_default_link_type' option to ""none"" if they don't plan on linking to full size images often from their posts. The problem is that this also affects the default link type for other media (uploaded zip files, pdfs, etc.) Adding an additional option for 'media_default_link_type' which behaves in the same way would get around this problem. " goldenapples 16518 Add Media/File description improvements for multi-selections feature Upload normal normal Future Release enhancement new has-patch 2011-02-10T17:24:13Z 2011-11-10T18:33:28Z "This was suggested to us for WordPress.com by a coworker at Automattic and we realized this could actually be a worthy core improvement. {{{ Would it be possible to add some wording to the Add Media screen in WP.com blogs to tip users off that they can upload multiple images at once by holding down CTRL in Windows or CMD on a Mac? Stumbled upon this nifty feature myself today under the category of “here goes nothing, let’s see if this works.” }}} Opening the ticket until I can add a patch (or someone else does)." stephdau 19121 Add filter to wp_unique_filename Upload 3.3 normal major Awaiting Review enhancement new has-patch 2011-11-02T23:02:15Z 2012-08-02T13:19:10Z "Add a filter to wp_unique_filename so it can be modified if necessary. Currently in wp_handle_upload I am trying to use FTP to put the file elsewhere. Since I can can't use an FTP protocol with move_uploaded_file, I can't just use the upload_dir filter to change the upload directory. I need to be able to change the unique name directly (so I can look on my FTP server) and then later on I'll handle the move. There is no way to access this (you can't just affect overrides or anything like that) without completely rebuilding large portions of the uploader. With this one minor hook added, the flexibility becomes much greater." xazure 13500 Add support for XML in allowed extensions and mime types Upload normal minor Future Release enhancement new 2010-05-22T17:48:24Z 2012-07-26T19:42:19Z "As with #12849, please add CSV and XML types to wp_ext2type() or get_allowed_mime_types() in functions.php. The patch I use on my local install of Wordpress is: {{{ --- wp-includes/functions.php~ Wed Dec 23 19:38:49 2009 +++ wp-includes/functions.php Wed Dec 30 16:09:13 2009 @@ -2324,6 +2324,10 @@ 'odc' => 'application/vnd.oasis.opendocument.chart', 'odb' => 'application/vnd.oasis.opendocument.database', 'odf' => 'application/vnd.oasis.opendocument.formula', + 'py' => 'application/python', + 'xml' => 'text/xml', + 'csv' => 'text/csv', ) ); } }}} " fazalmajid 6814 Async media crunching koopersmith Upload 2.5 normal normal Future Release enhancement assigned 2008-04-23T00:19:05Z 2012-10-22T16:09:26Z "The upload part of the new multi-uploader is pretty nice now, but it blocks on the ""crunching"" phase, which can sometimes take 20-60 seconds, I assume to create medium thumbnails and such. The crunching part of the upload should not block the next file beginning the upload process, it should happen asynchronously with the rest of the process." matt 9257 EXIF GPS data Upload 2.7 normal normal Future Release enhancement new has-patch 2009-03-01T19:30:17Z 2009-11-20T20:33:48Z "Attached patch adds GPS longitude and latitude to image meta data. Changed: wp_read_image_metadata function (file: wp-admin/includes/image.php). It complies with exif standard: [http://www.exif.org/Exif2-2.PDF] (page 46) Commented on wp-hackers list: [http://comox.textdrive.com/pipermail/wp-hackers/2009-March/025093.html]" B-Scan 14137 EXIF tag DateTimeDigitized not always present Upload 3.0 normal minor Future Release enhancement new has-patch 2010-06-29T00:47:59Z 2011-01-16T03:48:07Z "Shooting images with my Nokia N900 will only fill in EXIF data for ""DateTimeOriginal"", not the tag ""DateTimeDigitized"" which Wordpress solely uses. Grabbing data from DateTime and/or DateTimeOriginal would increase the amounts of correct EXIF date data collected when uploading images. Attaching sample original image from my camera. CLI tool 'exif' when grep:ed with 'Date' outputs the following for the attached image: {{{ Date and Time |2010:06:25 15:47:14 Date and Time (origi|2010:06:25 15:47:14 }}} 'exif --list-tags *jpg|grep Date' results in the following (* meaning data exists): {{{ 0x0132 Date and Time * - - - - 0x9003 Date and Time (original) - - * - - 0x9004 Date and Time (digitized) - - - - - }}} wp-admin/includes/image.php has the function which retrieves this metadata." MMN-o 15697 File upload support for OpenXPS / Microsoft XPS filetype (oxps / xps, alternative to PDF) kapeels Upload 3.1 normal minor Future Release enhancement assigned dev-feedback 2010-12-06T00:37:38Z 2010-12-11T10:06:08Z "OpenXPS / XPS (XML Paper Specification) is a document file type similar to PDF, originally created by Microsoft but now an open standard, ECMA-388. If you allow uploads of PDF, you should allow uploads of this competing format. More details on the file type: http://en.wikipedia.org/wiki/Open_XML_Paper_Specification This is a very simple change, similar to Ticket #8194 / Changeset 9662. 1. In /trunk/wp-includes/functions.php, function wp_ext2type (line ~2355): add 'oxps' and 'xps' after the 'pdf' entry as 'document' types. 2. In /trunk/wp-includes/functions.php, function get_allowed_mime_types (line ~2475): add (after 'pdf') the MIME type for 'oxps' as 'application/oxps', and 'xps' as 'application/vnd.ms-xpsdocument'. " sgryphon 6379 Image Insert section is confusing, not properly separated from Image Editing markjaquith* Upload 2.5 normal normal Future Release enhancement accepted 2008-03-25T06:29:59Z 2010-10-28T08:21:47Z "This whole section: [[Image(http://img339.imageshack.us/img339/7967/picture1td7.png)]] ... is related to inserting that individual photo into the post, but it is slammed together with photo settings that you can change and save. We really need to demarcate the ""Insert Image into Post"" section better. Other issues: * ""None"" alignment radio button is not selected by default. * The Link URL section is incredibly confusing. At first I thought that was where you could edit the filename. * Pressing input buttons to make your link URL selection is unnatural." markjaquith 21083 JS-based feature detection we can use server-side Upload normal normal Future Release enhancement new 2012-06-26T20:46:07Z 2012-10-17T22:31:00Z "In #20923 we added initial support for browser-based uploads in iOS 6, by detecting the user agent. This is a good stopgap, but we can do better. We should implement a simple API that allows for us to do JS-based detection for mobile devices. We can use this for touch support, general upload ability, drag-drop upload ability, customizer support, and anything else that we can best detect in JS but that we need in order to make decisions in PHP. We could probably model parts of it on how the user settings API works — leveraging cookies, but without the DB backend. A function could then return a value from the cookie if set, and otherwise, it'd use the default value passed to it." nacin 7634 Need a way to cancel an upload edit Upload 2.7 normal major Future Release enhancement reopened 2008-08-28T21:51:18Z 2013-01-09T20:11:49Z When you click a media upload, you have to either save it, or use the back button in the browser. Feels like a dead end. markjaquith 24251 Reconsider SVG inclusion to get_allowed_mime_types Upload normal minor Awaiting Review enhancement new dev-feedback 2013-05-02T19:36:57Z 2013-05-02T20:21:21Z "There are some who think SVG should be included in core as an allowed mime type. Makes fine enough sense to me, since there is a good argument for it, and we have support for WordPerfect documents...so there's that. Related: #20990" JustinSainton 14459 Rotate Full Size Images on Upload azaozz Upload 3.0 normal normal Future Release enhancement reviewing 2010-07-29T23:16:17Z 2013-01-06T08:52:07Z "It may be worth a revisit to #7042. Some mobile devices that use WordPress for Android are not capturing images in the correct orientation, instead they are writing the EXIF orientation to the image instead (which is a standard method these days). In wp-android and other external clients that offer full size image upload, these images will not be rotated correctly upon upload. Since most mobile users are on the go with no access to the wp-admin area to rotate the images themselves, it would work best if the image was rotated for them automatically. Hopefully there's a solution that wouldn't strip the EXIF data, some way to copy the EXIF data before rotating, then save it back again?" mrroundhill 8234 Users with upload_files capability should be able to edit and delete uploaded files without having the edit_post/delete_post capability Upload 2.7 low minor Future Release enhancement new 2008-11-15T22:17:14Z 2009-11-20T20:31:07Z Users with upload_files capability are able to upload files but can't edit/delete his/her own uploaded files without having the edit_post/delete_post capability. Users capable to upload files should also be capable to edit/delete their own uploaded files. olethomas 20437 WP Upgrader filter to allow plugins to upload to existing directory Upload 3.3.1 normal normal Awaiting Review enhancement new has-patch 2012-04-13T16:52:30Z 2012-06-01T01:24:12Z "Our plugin for WP uses various elements of the WP upgrader class to manage plugins for our plugin. ;) This has worked great except when we went to extend it further and allow uploading of plugins through the WP Upgrader class much like you can with WP plugins. The issue is that currently, the WP Upgrader class is coded to expect the upload destination to be empty - EXCEPT if the upload destination (the base directory) is one of these hard coded locations: in_array( $destination, array(ABSPATH, WP_CONTENT_DIR, WP_PLUGIN_DIR, WP_CONTENT_DIR . '/themes') ) So since our plugin storage location is not one of those, it fails since there may already be some plugins there. Sure would be nice if that array of locations that does not have to be empty (the important base dirs which allow dropping down a directory level)... a simple filter would accomplish this... Hope its not too late in 4.3 for a simple filter..." usermrpapa 19227 clicking the pinkynail/title in the media-upload.php library tab does not show the full media info. Upload 3.3 normal normal Awaiting Review enhancement new 2011-11-10T20:30:35Z 2011-11-10T20:31:40Z "I am using the latest nightly build. I am not sure if this is supposed to work this way, but it does have the 'toggle' class and UX wise it should I think. Steps to reproduce: 1: Open a post/create a new post 2: Click the Upload/insert media button. 3: in the media iframe click 'Media Library' 4: Click on an 'pinkynail' or title in the list Nothing happens. I would expect clicking the 'pinkynail' or title to activate the same 'toggle' as the 'show' link does as we read left to right, our eyes are drawn to the image and we are generally choosing an image here, so our instinct is to click that. Plus this is how it works in the 'full' (i.e. non-iframe) version. It could also do with css to make the cursor 'pointer'. Tested in latest versions of Chrome and Firefox in Windows 7" davidosullivan 7491 thumbnail creation fails silently Upload normal normal Future Release enhancement new 2008-08-09T19:16:19Z 2010-03-06T16:13:08Z "When thumbnail creation fails, it fails silently, with no indication why it fails. That is a real pain in the ass if you're trying to debug. Frankly, I assumed for months that thumbnailing just wasn't implemented yet- it was only because I noticed that it does work on ma.tt that I even went back and tried to debug the situation. I'm still not succeeding in actually getting the thumbnailing working, for what it is worth- extensive googling suggested I should install libgd, which I've now done, but no helpful errors from wordpress means I'm just back at square one in terms of figuring out why it is breaking. There are no other directly pertinent bugs, but #7039 and #1952 mention instances of silent failure being a problem and #2794 has a (now bitrotted) patch creating an error reporting system. " tieguy 23686 wp_handle_(upload|sideload) have a lot of copy-pasted code from each other Upload trunk normal normal Awaiting Review enhancement new 2013-03-04T11:27:35Z 2013-03-04T17:49:36Z A huge part of those two functions is the same. It needs to be refactored, so that they share the code. nbachiyski 19770 Implement browser-side resizing with Plupload Upload 3.3 normal normal Awaiting Review feature request new 2012-01-07T16:07:51Z 2012-09-01T06:10:23Z "#19174 removed the browser-side image resizing due to browser inconsistencies. We should fix it and reintroduce the feature. A little related: #14459" johnbillion 7580 Use Exif description to autofill the caption Upload 2.6 high normal Future Release feature request new 2008-08-23T06:26:39Z 2011-11-19T19:58:35Z "Hello, I test a lot of softwares to create a Exif description for my pictures. Like ""Exif Farm"" or other kind of this softwares. But When I Upload this picure in wp 2.6 the description will not show! but i have some picture from the web, and when i upload them, wordpress show the description of it automatically in description Box! like this picture: http://www.hinhxinh.com/data/media/8/Beijing_Olympic_2008_-___075.jpg and show description on it correctly: http://i33.tinypic.com/2yyqk1t.jpg Please tell me: the problem is from Wp, Or My software is not original? '''So What should i do to show Description Exif Data in wp Correctly?'''" mrmax 16884 URL generation in setup-config's get_bloginfo() Upgrade/Install 3.1 normal normal Future Release defect new dev-feedback 2011-03-18T11:49:08Z 2012-06-02T19:12:24Z "See [http://php.net/manual/en/function.str-replace.php str_replace()] Replacing some string with something in an **empty string** is obviously bogus." hakre 19781 All update processes should be within an iframe Upgrade/Install normal normal Future Release defect (bug) new has-patch 2012-01-09T00:16:20Z 2012-03-18T06:25:08Z "Currently some of the update processes run within iframes, others don't. We should standardise on all within an iframe. Running inside the iframe has the advantage that the footer of the page is loaded, and therefor, the Toolbar will load, rather than the page appearing half-loaded for certain upgrade/install processes. Currently, Processes which run inside iframes are Bulk updates, Singular updates load directly. ~~We should also investigate a iframe overlay that contains a ""Working.. please wait"" graphic that clears once the content of the iframe starts loading, This should help ease the pain of not being sure if the update process has started on servers that force gzip (and as a result, provide no user feedback until the process is complete) - See #18525 and #18239 for examlples of that~~ see #19783" dd32 16817 All updates have been completed Upgrade/Install 3.1 normal normal Awaiting Review defect (bug) new has-patch 2011-03-10T09:41:22Z 2011-03-10T11:17:23Z "I tried to update 12 plugins at once, one of them ended with red error message ""An error occurred while updating PLUGIN_NAME: Could not remove the old plugin."" But in the end of Update page is message ""All updates have been completed."" And that is not right, because one plugin was not updated." pavelevap 23113 Automatic notice of new localized version missing Upgrade/Install 3.5 normal major WordPress.org defect (bug) new 2013-01-03T21:47:44Z 2013-02-02T08:19:13Z There was standard behaviour, that users could upgrade quickly to the latest WordPress version and when localized version was ready and released, notice about new localized version appeared in administration. But some users found that it was changed (in 3.5 or maybe 3.4) and when they upgrade to English version, they are not noticed about new Czech version in the future which is annoying. I tried it on some websites and it is true. I am not sure, if it is wanted change (but does not make sense for me) or bug (regression)? pavelevap 10884 Available plugin update count disappears after updating plugin dd32* Upgrade/Install 2.8.4 normal normal Future Release defect (bug) accepted dev-feedback 2009-10-01T18:25:59Z 2011-04-03T10:52:00Z "When there are any available plugin updates, WP displays number of them next to ""Plugins"" item in menu. However when you have more than one update available and update one plugin, it disappears. Steps to reproduce:[[BR]] - make sure you have more than one plugin with update available (WP should count of them in menu);[[BR]] - go to the Plugin page and click on Autoupdate link for plugin;[[BR]] - when update page will load completely, click on provided link to return to plugin list. Expected result: WP displays new number of available updates next to Plugins menu.[[BR]] Actual result: nothing is displayed. Note: I tested this for inactive plugins only." sirzooro 20263 Backticks in dbDelta cause warning and actually causes a query to alter all columns and indexes to run even if none have changed Upgrade/Install 1.5 normal minor Awaiting Review defect (bug) new has-patch 2012-03-20T16:11:18Z 2012-09-01T20:13:24Z "Backticks in a CREATE TABLE in a dbDelta call are causing the below warning, and running a query to alter all columns and indexes with backticks even if they haven't changed: Notice: Undefined offset: 1 in /home/backuptechnology/public_html/wp-admin/includes/upgrade.php on line 1544 Seems this started a long long time ago after this was fixed: http://core.trac.wordpress.org/ticket/8014 Seems there is a match on line 1587 of WordPress 3.3.1 wp-admin/includes/upgrade.php: {{{ // For every field in the table foreach ($tablefields as $tablefield) { // If the table field exists in the field array... if (array_key_exists(strtolower($tablefield->Field), $cfields)) { // Get the field type from the query preg_match(""|"".$tablefield->Field."" ([^ ]*( unsigned)?)|i"", $cfields[strtolower($tablefield->Field)], $matches); }}} The preg_match bit is what fails to match because it is looking for ""fieldname"" instead of ""`fieldname`"". So this is where the warning occurs, and why it assumes the type of the field is wrong. This means the previous patch 3 years ago probably meant when you have backticks in your CREATE TABLE, when you run dbDelta it actually runs an ALTER TABLE for every single column in the table, and then an ALTER TABLE ADD INDEX / PRIMARY for every single KEY and PRIMARY (there's more than just the above code that needs adjusting), causing duplicate key errors, but ignored. Guess it kinda works though... Also seems during the DESCRIBE it doesn't use backticks so if someone has a table with a reserved name (stupid I know) it would break dbDelta completely, but that's me digressing I just think getting rid of the warnings for CREATE TABLES with backticks will be good. But explains why my plugin takes a few seconds to activate hahaha. :-) I'll provide a patch at some point this week or next unless someone has already done so." Driskell 15729 Better UX after supplying incorrect information to setup-config kapeels* Upgrade/Install low normal Future Release defect (bug) accepted has-patch 2010-12-08T07:19:24Z 2010-12-23T02:42:49Z "In #15682 I added a 'Try Again' button to step 2 of setup-config.php if the credentials were incorrect. The button is a simple link with a `javascript:history.go(-1)` hack. This should instead be a form with hidden values that submits back to setup-config.php?step=1, and fills out the form so they can try again. Additional enhancement: If the prefix is malformed (can only contain letters, numbers and underscores), we do a wp_die(). We should again have a form with a 'Try Again' button that returns them. As an added bonus, incorrect credentials should be filled out (for reference) but marked as incorrect and potentially with the focus set on that field. Only caveat I can think of: This will require the use of esc_attr(), which we don't have access to yet. Not sure how to solve that without reverting to htmlspecialchars() with some extra work." nacin 16150 Create post format terms on upgrade Upgrade/Install 3.1 normal normal Future Release defect (bug) new 2011-01-08T00:06:07Z 2011-01-08T04:57:09Z #16149 Creates a Standard post format term on save, but it might also be nice to have all our known post format terms created and associated with the taxonomy on upgrade. Could save us trouble down the road to have all of them defined and in the DB. markjaquith 10596 Error when uploading zip package with parent and child themes Upgrade/Install 2.8.3 normal normal Future Release defect (bug) assigned 2009-08-12T11:12:29Z 2012-01-06T12:30:14Z "There's an error when you try to install a package containing parent and couple of child themes using zip package upload from the admin dashboard. For example i got a 1 big directory called test_template which contains 1 folder test_parent and 3 folders test_child1, test_child2, test_child3. If i upload test_template directory using ftp everything's ok, but when i try to use theme uploader and zip package test_template.zip i get an error caused by not finding a style.css file inside of the test_template directory ... but when i add a style.css file to that directory installation goes fine but templates aren't working till i use ftp and delete that file from that directory. It's troublesome if someone is giving his templates to other users." newkind 17999 Failure to Update Notification Persists After Manual Upgrade Upgrade/Install 3.2 normal normal Awaiting Review defect (bug) new 2011-07-05T20:30:08Z 2013-01-13T16:42:27Z "This has been around for a few versions. When an update fails, if the user updates or upgrades manually and WordPress lists the updated version in the Administration Panels, the failure to update notification persists. I've sat through four or five updates with the failure notice on every panel, including WordPress 3.2, on several sites." Lorelle 12031 Install do not check the magic_quote_sybase status dd32 Upgrade/Install normal normal Future Release defect (bug) reopened 2010-01-26T00:27:25Z 2012-11-01T20:09:16Z "MU Trac Ticket: http://trac.mu.wordpress.org/ticket/981 Just try to install on a server that it's magic_quote_sybase is on (okay for Oracle, but fatal for mysql) . It failed to update the wp-config.php and didn't set correctly the .htaccess. " wpmuguru 20652 Install plugins with FTP upload, virtual subdomain, bad base dir? dd32 Upgrade/Install 3.3.2 normal normal Future Release defect (bug) reopened needs-unit-tests 2012-05-10T12:02:48Z 2013-05-21T19:58:48Z "Hi anybody! I have problem with install plugins with FTP module in WP. Everything show as OK, but plugin directory is bad. I have subdomain sub.something.com - this is virtual subdomain from mod_rewrite dirs are /www/something.com/something.com[[BR]] /www/something.com/sub.something.com - here is WP installation, subdomain is virtual from rewrite in httpd.conf After install - WP say everything OK - but one thing is bad.[[BR]] Upload is in bad directory - plugin I can found in[[BR]] /www/something.com/something.com/plugins[[BR]] no in /www/something.com/sub.something.com/plugins[[BR]] Is here some way to fix it automatticaly or I can must edit config and basedir of ftp? Why is here this bug? Thank you ! Pavel " rajcz 17387 Issue with wp_theme_update_row() setting $details_url Upgrade/Install 3.1.2 normal normal Awaiting Review defect (bug) new 2011-05-12T09:15:44Z 2011-05-12T09:15:44Z "I'm building my own theme auto update script and everything was working perfectly, until I ran into a weird bug. When you're running WordPress in Multisite the $details_url for themes with an update available is set differently than when running WordPress in single site mode. In single site mode the details url is set inside the theme_update_available() function found in this file /wp-admin/includes/theme.php. It uses the returned 'url' like so. {{{ $details_url = add_query_arg(array('TB_iframe' => 'true', 'width' => 1024, 'height' => 800), $update['url']); }}} However, in Multisite the url is built completely different. It uses the wp_theme_update_row() function in the /wp-admin/includes/update.php file like so. {{{ $details_url = self_admin_url(""theme-install.php?tab=theme-information&theme=$theme_key&TB_iframe=true&width=600&height=400""); }}} I'm not exactly sure what the best approach would be to fixing this. I know there is a reason why the url is set like that but without a way to change it for my personal themes (i.e. filter or something) I'm stuck with a broken details screen in Multisite. I did just add a filter to test it and was successful in fixing the issue, but not sure how to proceed from here. {{{ $details_url = apply_filters( 'network_details_url', self_admin_url(""theme-install.php?tab=theme-information&theme=$theme_key&TB_iframe=true&width=600&height=400""), $theme_key, $theme ); }}} Thanks for any help you can give me. Cheers! Derek Herman" valendesigns 15440 PCLZIP_ERR_BAD_FORMAT (-10) : Invalid archive structure during plugin update Upgrade/Install 3.0.1 low normal Future Release defect (bug) new 2010-11-16T15:53:13Z 2011-04-03T13:15:03Z "Currently, as part of our JW Player plugin we include several player skins so that users can customize the look of the JW Player. These skins are packaged as zip archives. For a while now we've been getting reports from our users having difficulty performing the automated update/install. These users are receiving a PCLZIP error which claims the plugin archive is invalid. From looking at the source code I see that WordPress first attempts to use the ZipArchive PHP module to unzip plugin packages. This always works for users updating our plugin. If this is not available it then uses a fallback library called PCLZIP. After some experimentation, it seems that PCLZIP has difficulty unzipping archives that contain archives. Is this a known issue from your experience? If so, is there a workaround other than removing the zip skins from our plugin package?" LongTail Video 22287 Plugin in another plugin folder causes Activate link to be wrong on Download Upgrade/Install 3.4 normal normal Awaiting Review defect (bug) new 2012-10-26T15:30:52Z 2012-11-13T01:41:05Z "I am not sure if shipping a plugin within another plugin is officially supported, but there is an inconsistency between the activate links in the Manage Plugins page, and the Activate Plugin on the Plugin Downloaded success page. This is because on the Manage Plugins page, the `get_plugins()` is going to scan the plugins dir and all dirs within it, however, on the Upgrade page, it calls `get_plugins()` specifying the plugin dir as the base (see https://github.com/WordPress/WordPress/blob/master/wp-admin/includes/class-wp-upgrader.php#L579) That will cause the ""embedded"" plugin to be picked up, and if it's alphabetically above the main plugin file (presumably) see code comment "" //Assume the requested plugin is the first in the list""" joehoyle 14401 Unable to locate WordPress Content directory (wp-content). Upgrade/Install 3.0 normal normal Awaiting Review defect (bug) reopened reporter-feedback 2010-07-23T15:56:19Z 2011-08-14T01:58:27Z "Hi, I encounter this message on one server during plugin install: ""Unable to locate WordPress Content directory (wp-content)."" PHP Version 5.2.0-8+etch1 Another info from Core Control plugin: Direct Not Available SSH2 Not Available PHP FTP Extension Available PHP FTP Sockets Available ABSPATH: /home/www/domain.eu/subdomains/www/ WP_CONTENT_DIR /home/www/domain.eu/subdomains/www/wp-content WP_PLUGIN_DIR /home/www/domain.eu/subdomains/www/wp-content/plugins DOCUMENT_ROOT (from phpinfo) /home/www/domain.eu/subdomains/www I tried some hacks in wp-config.php, but I was not successfull. When I tried ftpsockets, following error appears: Warning: socket_last_error() expects parameter 1 to be resource, null given in /home/www/domain.eu/subdomains/www/wp-admin/includes/class-ftp-sockets.php on line 59 When I tried direct, following error appears: Downloading install package from http://downloads.wordpress.org/plugin/wp-memory-usage.zip… Unpacking the package Could not create directory. /home/www/domain.eu/subdomains/www/wp-content/upgrade/wp-memory-usage.tmp" pavelevap 15101 Update Message Reduces User Orientation reg. WordPress Version Upgrade/Install 3.1 normal normal Future Release defect (bug) new 2010-10-12T12:06:13Z 2011-01-13T20:51:27Z "This is a usability issue many customers are telling me: When there is a WordPress update message, the current version is not prominent any longer. Normally the current version is displayed in the admin's footer. If there is a (very promintent ""on top"") update message, this version information get's hidden in footer as well. The only place where a user can find the current version is in some dashboard widget. That location is hard to find. And that location is hard to describe on the phone, e.g. in support. I suggest to restore the current version display in the footer, because a footer is very easy to find and to describe by phone. Additionally the update message on top should display the current version number as well. Something Like There is a new version available, you're currently running (should be 65%-70% of the width in english text of a 1024 width screen (970 or so viewport size) to allow this to be translated w/o consuming too much of the screen real estate)." hakre 14465 Update Plugins Hangs while displaying 'updating' Upgrade/Install 3.0.1 normal normal Future Release defect (bug) new 2010-07-30T07:45:17Z 2012-06-28T14:49:09Z "Hi, Whenever I try to update a plugin the update plugins screen hangs indefinetly. Example message while this is happening would be- ""The update process is starting. This process may take awhile on some hosts, so please be patient. Enabling Maintenance mode… Updating Plugin Link Library (1/1)"" The plugin ulitmately gets updated if I wait a minute or two but this page never refreshes. I am running WP 3.0.1 but this happend on 3.0.0 as well. My host is running MySQL 5.0.90-community PHP 5.2.13 and my browser is IE8." jamesfed 13071 Update bubble appears only at the second load dd32 Upgrade/Install 3.0 normal normal Future Release defect (bug) new 2010-04-21T15:51:25Z 2011-04-03T10:54:48Z "Change the version of a plugin and go directly to ''wp-admin/update-core.php'' page.[[BR]] You will see the plugin update in the list but the bubbles on the menu appears only after a reload. " ocean90 15731 Updating multiple plugins at once throws FTP error and leaves wp in maintenance mode Upgrade/Install 3.0.2 normal normal Future Release defect (bug) new 2010-12-08T10:01:19Z 2010-12-11T13:29:57Z "[[Image(http://img.skitch.com/20101208-pc3k6gej2piiewts246qrwwt18.jpg)]] The ftp error seems related to my iptables config and not a wp bug {{{ LOG all -- anywhere anywhere limit: avg 5/min burst 5 LOG level debug prefix `iptables denied: ' }}} But after the fail, I'm stuck with ""Briefly unavailable for scheduled maintenance. Check back in a minute.""" koke 18286 Upgrade script to fix non-unique page GUIDs Upgrade/Install 3.2.1 normal major Awaiting Review defect (bug) new has-patch 2011-07-28T23:07:19Z 2011-08-02T17:22:28Z "There were versions of WordPress prior to 3.1 that created non-unique GUIDs in the posts table. http://core.trac.wordpress.org/ticket/15041 This bug is fixed, but the bad data persists in many WP installs. Attached is a proof-of-concept plugin that could be included in the WordPress upgrade process to clean up these GUIDs. In the interim, I'll probably release this as a plugin as we've got some folks using tools we built that need this fix ASAP." alexkingorg 13875 Upgrading from pre-2.3.0 yields database errors Upgrade/Install 2.9.2 normal normal Future Release defect (bug) new 2010-06-14T00:01:56Z 2010-10-28T01:51:56Z "When upgrading a 2.2.3 to 3.0-rc3 using wp-admin/upgrade.php, three database errors appear signaling that delete_site_transient() misfunctions, as a column value for option_description is not given (in a way, this is #4921 again). The upgrade script should either a) give a default value to that column or b) delete it earlier in the upgrade process. --8<-- (error msgs follow) WordPress database error: [Field 'option_description' doesn't have a default value] INSERT INTO `options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_doing_cron', '1276472580', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`) WordPress database error: [Field 'option_description' doesn't have a default value] INSERT INTO `options` (`option_name`, `option_value`, `autoload`) VALUES ('_site_transient_timeout_theme_roots', '1276479782', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`) WordPress database error: [Field 'option_description' doesn't have a default value] INSERT INTO `options` (`option_name`, `option_value`, `autoload`) VALUES ('_site_transient_theme_roots', 'a:2:{s:15:\""philippus-do-de\"";s:7:\""/themes\"";s:9:\""twentyten\"";s:7:\""/themes\"";}', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`) " tinne 22840 Uploading an existing plugin saves the zip in media library Upgrade/Install 3.4.2 normal normal Awaiting Review defect (bug) new 2012-12-09T19:35:25Z 2012-12-10T14:01:45Z "Action: Install the same plugin twice. Expected behavior: Second time, plugin should fail and not install. Actual Behavior: Install fails, but the plugin's .zip shows in the Media Library. (Shows in Site #1 on Multisite) This ''is not'' a 3.5 regression, same things happens in 3.4.2" Ipstenu 17680 "Using ""update automatically"" can destroy a theme in a Windows environment" Upgrade/Install normal major Future Release defect (bug) new has-patch 2011-06-03T22:33:18Z 2011-06-04T05:44:39Z "If there are any locked files or files in use, Update Automatically destroys the theme. I've experienced this three different ways: 1. The machine is really slow to delete the original theme dir, when the update is moved into the themes dir, an error occurs: ""Could not create directory"". The theme is now gone. 1. If there are any locked files in the outdated theme (e.g. SVN), all the files except the locked one will be deleted. Upgrader bails and you're left with a broken/empty theme. 1. If any of the files are in use, all files inside the theme will be deleted but the file system will throw an error. The updater bails with an empty theme directory. Steps to duplicate: 1. On a Win hosted install, open the twentyten theme directory 1. Edit stylesheet, change version to 1.0 1. Open screenshot.png in paint 1. In the wp-admin, upgrade the theme 1. Sad times (screenshot attached) Proposed solution is to try to rename the old theme first. Provides two benefits: 1. Have a backup of original theme if something breaks mid-way 2. Never left with a broken site Note: all the more reasons why one should not use Windows :/ but I have no choice. " blurback 22076 WP Upgrader: update_bulk_plugins_complete_actions and update_bulk_theme_complete_actions should pass information about all plugins/themes to the filter Upgrade/Install 3.0 normal normal Awaiting Review defect (bug) new 2012-10-02T07:56:19Z 2012-10-05T23:10:07Z "In class-wp-upgrader.php, line 1214 there is this line: {{{ $update_actions = apply_filters('update_plugin_complete_actions', $update_actions, $this->plugin); }}} When adding a filter to it like this: {{{ add_filter('update_bulk_plugins_complete_actions','test_filter',99,2); function test_filter( $update_actions, $plugins ) { echo print_r( $plugins, 1); return $update_actions; } }}} Only the last updated plugin info will be printed. However, it should contain information about all the plugins that were updated (since we are dealing with a bulk upgrade here)." ragulka 5117 WordPress (plugin) updates do not warn about unknown plugins matt Upgrade/Install 2.6 normal normal Future Release defect (bug) new 2007-09-30T11:34:17Z 2009-09-02T20:29:29Z "The WordPress plugin update system does not notify the user if it could not find updates for a subset of plugins. That is, if the user has installed plugins not hosted with WordPress, they are not notified that new versions were ''not'' actually checked for. This can lead the user to believe that all of their plugins are up-to-date when they are not. Fixing this will require both the server-side and the client to be updated. The WordPress update API will need to return data on which plugins it does not recognize as being hosted, and the WordPress installation will need to render that information so that the user understands which of his/her plugins are ''not'' automatically checked." Quandary 17439 Wordpress Database Update reports errors but says it's successfull Upgrade/Install 3.2 normal normal Awaiting Review defect (bug) new 2011-05-15T09:23:30Z 2011-05-15T14:36:43Z "I just updated my database on current HEAD of trunk by pressing the button while WP told be to do so. I got an error reported: ---- '''WordPress database error:''' [Out of range value adjusted for column 'post_parent' at row 4] `ALTER TABLE wp_posts CHANGE COLUMN post_parent post_parent bigint(20) unsigned NOT NULL default '0'` ---- However right beneath of it, I was greeted with: ---- '''Update Complete''' Your WordPress database has been successfully updated! ---- First of all I ask myself if I can trust that message as an error has been reported. Then this looks like that the update is not compatbile with my MySQL server which is 5.0.19 and matching the [wordpress system requirements on the webpage](http://wordpress.org/about/requirements/) (which seems to be out of date for trunk, but, well 5.0 is required according to version.php). Related: #3112 " hakre 20069 Wordpress upgrade process removed executable bits on .php files and so broke Wordpress Upgrade/Install 3.3.1 normal major Awaiting Review defect (bug) new close 2012-02-18T12:55:48Z 2012-02-20T13:05:11Z "I just upgraded from 3.2 to 3.3.1 on my shared hosting box (hosted by http://www.mythic-beasts.com). This uses suexec, and so .php scripts need to have executable permissions otherwise it won't execute them. I am told that many secure multi-user setups work like this. My original install had the PHP scripts set as executable, but I did the upgrade (via the web GUI) and suddenly I got 500 Server Errors everywhere. I had to chmod all .php files back to executable before my blog would work again. Wordpress should check the permissions on .php files before upgrading and preserve them across the upgrade. Gerv" gerv 18169 [15491] prevents to plug into the update API Upgrade/Install 3.1 normal normal Awaiting Review defect (bug) new has-patch 2011-07-19T09:13:49Z 2011-08-24T00:21:04Z "I'm a bit late to the party, but I've only noted now that changeset [15491] introduced a subtle change to the WP API, which prevents to readily plug into the update API: Prior to it, the sequence went something like this: {{{ $args = array(...); // set using a filter $api = themes_api('query_themes', $args); if ( is_wp_error($api) ) wp_die($api); display_themes($api->themes, $api->info['page'], $api->info['pages']); }}} It now goes like this: {{{ switch ($tab) { case ...: // valid case $args = array(...); // relevant args break; $args = false; // this is new. a filter should be present here... } if (!$args) return; // the 'query_themes' hook is no longer useful $api = themes_api('query_themes', $args); if ( is_wp_error($api) ) wp_die($api); display_themes($api->themes, $api->info['page'], $api->info['pages']); }}} I used to use a hook in there to add a tab in the installer. The stab is still around, and is as far as I can tell part of it is still working, but it no longer seems possible to display the results using the normal API." Denis-de-Bernardy 16057 download_url() error checking fails to notice that the file wasnt correctly witten to disk Upgrade/Install 3.0 normal normal Future Release defect (bug) new has-patch 2011-01-01T01:36:51Z 2013-05-21T19:49:09Z "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 23487 is_blog_installed gives errorneus result on moved database Upgrade/Install 3.0 normal trivial Awaiting Review defect (bug) new 2013-02-16T13:11:37Z 2013-02-16T13:31:48Z "I resently moved my blogs to a new database, but when I tried it out, on of the blogs wanted a new install. Of course I did not want to do an install and overwrite my blog. I indirectly found the reason in is_blog_installed, which suppresses database errors. Thus I did not see this error. SELECT command denied to user 'techblog'@'localhost' for table 'wp_options' Of course it was my fault, but I virtually had to take the wordpress code apart to find out why my migration failed. Of course this is not a big problem on new installs, but very likely to happen on moving databases. " Kjeld Flarup 11009 screenshots of plugins from wordpress.org load over http instead of https when FORCE_SSL_ADMIN is enabled Upgrade/Install 2.9 normal normal Future Release defect (bug) new dev-feedback 2009-10-23T02:30:21Z 2010-02-05T13:52:39Z "1. Enabled FORCE_SSL_ADMIN in Wordpress on an appropriate host. 2. Use default settings in Internet Explorer 8. 3. Go to the plugin installation page. 4. Choose a plugin from wordpress.org to install. Actual Result: You get a mixed mode warning because the screenshots and possibly other content loaded from wordpress.org are loaded over http instead of https. Expected Result: Screenshots are loaded over https so that content is not mixed." brantgurga 16156 update-core is oblivious to api.wp.org being unreachable Upgrade/Install normal normal Future Release defect (bug) new dev-feedback 2011-01-08T09:51:38Z 2011-04-04T07:46:30Z "A server running 3.0.4 had trouble reaching *.wordpress.org for some unknown reason. (This wasn't during the brief api.wp.org outage, and it worked otherwise.) Problem is, update-core was completely oblivious to this. It's even worse when running 3.1, because the 'Check Again' button will refresh the page and tell you we last checked for updates *just now*. Try Again or Check Again should reflect that the API is unreachable when this can be determined. Claiming that we checked for updates is also really lame, so we should see if the transient tells us how long it's been since the last one. Side note, the plugin install et al. HTTP error messages are rather cryptic, and we should also make those more user friendly." nacin 22881 upgrade fails when disk space is exhausted due to quotas Upgrade/Install 3.4.2 normal normal Awaiting Review defect (bug) new 2012-12-12T11:38:41Z 2012-12-12T11:38:41Z "The upgrade from wordpress 3.4.2 to 3.5 failed due to a disk space limitation: {{{ Downloading update from http://wordpress.org/wordpress-3.5-new-bundled.zip… Unpacking the update… The package could not be installed.: PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature Installation Failed }}} A similar bug occurs if the space for the files themselves is exhausted. On the same installation, functions.php was truncated at 112k, leaving the installation in a non-functional state. This kind of behaviour can be avoided with an upgrade function of the form: {{{ # test for 64k free disk space ... dd if=/dev/zero of=biggish-test-file bs=1024 count=64 && rm biggish-test-file && wget -O - http://wordpress.org/latest.tar.gz | tar -zvx --strip-components=1 }}} Streaming the download imposes no additional disk space requirements for the intermediate .zip file, but does require a change in the extraction code. Streaming an update cannot be done with zip files, since the index is at the end. ZIP files have to be complete, since the tag is at the end. 'tar' files are more suitable for streaming." list2010@… 18239 wp_ob_end_flush_all() hangs the output buffering, during plugin update/install Upgrade/Install 3.2.1 normal minor Awaiting Review defect (bug) new 2011-07-25T07:52:03Z 2012-10-26T15:59:20Z "Symptom: During plugin update process, the screen displays ""Downloading {plugin}"" then appears to hang. System: Apache2 on LinuxMint-11 I traced the fault to the following function: send_message() in /wp-admin/includes/misc.php this function writes out the message, then tries to flush the buffers by calling wp_ob_end_flush_all() the mechanism of the ob_flush is to repeatedly call ob_end_flush until there is no more levels. On the default configuration of LinuxMint / Debian, zlib.output_compression is ON, and this interferes with ob_end_flush Based on notes from php.net, ob flushing is not necessary. SOLUTION: 1) Either change php.ini to set zlib.output_compression to OFF, or 2) shortcircuit the wp_ob_end_flush_all() by adding an immediate return to the first line. RECOMMENDATION: In future versions of Wordpress, the interaction between ob and zlib should be studied carefully to derive the most universal solution. " mamborambo 23269 .maintenance location issue on symlinked install Upgrade/Install 3.5 normal normal Awaiting Review enhancement new 2013-01-22T21:57:11Z 2013-01-22T21:57:11Z "I've started to symlink some of our WordPress installs using a folder structure as follows: .htaccess index.php wp -> /var/www/wordpress/WordPress-latest wp-config.php wp-content The wp folder is a symlink to either the latest version of WordPress, trunk or a specific version and the WordPress core files are all read only by the web server (WordPress core file installs are taken care of by Chef) I thought creating a .maintenance file in the root or the wp-content folder would trigger maintenance mode but it looks like the .maintenance file is only detected if it lives in the same folder as the WordPress core files ($wp_filesystem->abspath()) which is read only so it's never going to be created there. Having a shared core codebase even if I did override the write only permissions and set a .maintenance file in the WordPress directory that would mean every single site using that codebase would go into maintenance mode. (which sometimes might be useful since wordpress-latest might need updating) What about having WordPress look for the .maintenance file in the directory above similar to what we can do with the wp-config.php file? This would then mean with a symlinked install and shared codebase you could trigger .maintenance mode for a single install or all installs using the codebase. Or relocating the .maintenance file into the wp-content folder. This is after all where most web servers usually have write permission and where created files are meant to go." WPsites 5235 Add Pre-flight checks to install pishmishy* Upgrade/Install normal normal Future Release enhancement accepted dev-feedback 2007-10-19T17:37:56Z 2010-01-05T21:10:24Z "It would be nice for the installer to do some pre-flight checks and warn the users of things that will stop WordPress working (either completely or partially) Candidates for the pre-flight checks: * Functions which may be disabled - See #3014 * Memory limit #5235 " westi 13983 Add Update Network action link after updating Upgrade/Install 3.0 normal normal Future Release enhancement new 2010-06-18T20:49:58Z 2010-10-28T09:39:56Z "After updating an installation with MultiSite enabled, one of the following should happen : (a) There should be an action link to '''Update Network''' as well as or instead of the one to '''Go to Dashboard'''. (b) The Update Network process should be part of the Update process" caesarsgrunt 19783 "Add a ""Processing..."" overlay to update iframes" Upgrade/Install normal normal Awaiting Review enhancement new 2012-01-09T04:42:06Z 2012-01-09T04:47:46Z "On the back of #19781, i thought i'd raise this: > We should also investigate a iframe overlay that contains a ""Working.. please wait"" graphic that clears once the content of the iframe starts loading, This should help ease the pain of not being sure if the update process has started on servers that force gzip (and as a result, provide no user feedback until the process is complete) - See #18525 and #18239 for examlples of that Fast partial build updates don't experience this problem, but branch-to-branch updates can take awhile on some hosts, it'd be a nicer user experience for those users affected by the above." dd32 22378 Add ability to hijack plugin install/upgrade downloads Upgrade/Install 3.4 normal normal Awaiting Review enhancement new has-patch 2012-11-07T13:00:18Z 2012-11-13T01:09:22Z "'''Problem''' Many plugins have their own updating system. For paid plugins, this can involve sending authentication/authorization headers. At the moment, to implement this, certain parts of the plugin upgrader system have to be duplicated to replace parts of the system, such as the downloading method. In addition, the package download URL has to be a valid URL. Some systems may wish to use alternate URLs apart from HTTP/FTP-based URLs. The code for this is shared between the single plugin upgrader and the bulk plugin upgrader. While the upgrader class can be replaced fairly easily with existing filters for single plugins, it's not possible to do this for the bulk upgrader (especially when multiple systems want to do this), requiring falling back to a low-level filter like `http_request_args`, ensuring that one only hooks in after the `admin_action_update-selected` action has failed. '''Solution''' Add a filter to hijack the download system before it can act at all. This allows replacing the entire downloading system, with the only requirement being to return a valid package filename. This filter will work across both the single and bulk upgraders, ensuring consistency in the approach. Patch attached. Related: #22377, #22129" rmccue 22377 Add filter to wp_update_plugins() Upgrade/Install 3.4 low minor Awaiting Review enhancement new has-patch 2012-11-07T12:01:26Z 2012-12-10T21:04:41Z "'''Background''' Certain plugins (paid plugins, etc) may not wish to use WordPress' built-in upgrading functionality. As such, they may implement their own update checking code. WordPress' code runs every 12 hours via wp-cron, so hooking into the native system for checking would be the best way to avoid duplicating tonnes of code. '''Problem''' Currently, filtering this result is somewhat unintuitive. There are no filters in `wp_update_plugins()` to filter the result of the API call, so you have to fall back to `pre_set_site_transient_update_plugins`. WordPress, however, sets this transient twice, [https://core.trac.wordpress.org/browser/trunk/wp-includes/update.php?rev=21996#L193 once before updating] ""to prevent multiple blocking requests if request hangs"" and then once afterwards with the actual result. This is only a minor inconvenience, but it appears to be somewhat fragile. Ensuring that a plugin's custom code doesn't run on the first `set_transient()` requires setting a flag, and this is prone to breaking if `wp_update_plugins()` changes internally. '''Solution''' Introduce a new filter to change the API result before saving. This filter should only run once, with the actual result of the API call. Patch attached." rmccue 13922 Add links to GUU from plugins and themes screens Upgrade/Install normal normal Future Release enhancement new has-patch 2010-06-16T16:39:07Z 2012-12-24T04:34:33Z "[[BR]] Let's pimp the GUU (Dashboard > Updates) by having links to it from the plugins and themes screens so people who've missed it can see there's a single place to update everything. Woo!" jane 16398 Add new updated_core hook upon successfully updating WordPress core Upgrade/Install 3.0.4 normal normal Awaiting Review enhancement new has-patch 2011-01-28T19:52:50Z 2011-02-01T09:17:16Z "wp-admin/includes/update-core.php requesting the addition of a hook of some type (filter or action) for post-upgrade actions." scottconnerly 20074 Attempt MD5 checksum verification in upgrader if available Upgrade/Install 2.8 normal normal Future Release enhancement new dev-feedback 2012-02-19T06:06:24Z 2013-02-02T07:17:28Z "In #19928 the Content-MD5 header was added for downloads of WP releases. We had discussed performing MD5 verification, in the past, and now that we can do it without an extra HTTP request, it is somewhat more feasible. If we add the Content-MD5 header for themes and plugins, this should work for them as well. The patch will also give us access to the full HTTP API response array from download_url(), if specified." sivel 7965 Database upgrade complete message should be an admin notice Upgrade/Install normal normal Future Release enhancement new has-patch 2008-10-25T18:53:28Z 2012-07-26T09:02:37Z When a database upgrade is complete we should just take you to the page you wanted to see and should an upgrade_complete admin notice instead of requiring another button click westi 16216 Hide core updater if running an svn checkout Upgrade/Install normal normal Future Release enhancement new has-patch 2011-01-13T07:26:33Z 2011-05-12T03:39:48Z The logic with this patch is if you are running an svn checkout, do not display the core updater code and instead display a reminder. johnjamesjacoby 16492 Improvements to the Wordpress Update Process Upgrade/Install 3.0.5 normal normal Awaiting Review enhancement new 2011-02-08T16:45:48Z 2011-07-17T21:54:10Z "I've some suggestions on how to improve the update process (usability). I guess its not enough for separate tickets so I'm filing them together. * When updating Wordpress, a plugin or a theme, I'm being asked for the password to the FTP server. You should add a note there that the password won't be stored in the database. I guess many/some users are uncomfortable with storing their FTP password in the database and won't use the ""update tool"" for this reason. * Rename the button ""Update Automatically"" to ""Update Wordpress"". ""Update Automatically"" sound like ""Update now and update automatically in the future when a new Wordpress (and also plugin/theme?) version is available."" This should make the button's function a little bit clearer. " manski 12671 Installer page doesn't check if MySQL tables were created successfully Upgrade/Install 2.9.2 normal normal Future Release enhancement assigned 2010-03-22T17:47:33Z 2012-07-02T16:54:02Z "When running the web-based setup script - My Mysql user didn't have create permissions so no tables were created but the message (underneath all the MySQL errors) said setup was successful. I think it would be worth doing a check for no MySQL errors before proclaiming the installation a success." thedotproduct 14028 Maintenance mode nag persists after successful upgrade Upgrade/Install 3.0 normal normal Future Release enhancement new has-patch 2010-06-21T18:27:55Z 2011-01-16T00:05:29Z "A number of forum users are reporting that the maintenance nag ""An automated WordPress update has failed to complete"" etc.. persists after failed auto-updates even if they then successfully perform manual updates. Looks like something is leaving $upgrading set." mrmist 14393 Maintenance mode overkill. Please refine usage of it Upgrade/Install normal normal Future Release enhancement new 2010-07-22T22:12:14Z 2010-11-23T21:16:35Z "Though many tickets have been posted about the Maintenance Mode not resolving, I think that the problem is on a different level. It is unacceptable that even a failed upgrade of an inactive theme can break a complete Site or even Network. Case in point: I just followed the upgrade alert for an inactive theme, hosted on the WordPRess theme repository. (Apparently it had an error (Incompatible Archive. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature.) But the point is, this should not have put the entire network in maintenance mode for 10 minutes. Maybe a check can be done for plugins, themes etc: if they are active, then maintenance mode can be used (though I am definitely not a fan of it anyway)." bike 9679 Move Plugin/Theme deletion to new WP_Upgrader class DD32 Upgrade/Install 2.8 normal normal Future Release enhancement new 2009-04-29T08:51:55Z 2009-05-10T21:16:43Z Expansion off #7875, The plugin/Theme deletions should be also handled by the Upgrader class. DD32 22205 Plugin updater - Optimize API Request Upgrade/Install 3.4 normal normal Awaiting Review enhancement new has-patch 2012-10-16T15:45:27Z 2012-11-13T01:24:42Z "When checking for plugin updates, the POST to api.wordpress.org includes ALL information about each plugin (e.g. Description, Name, Title, Author, etc). This is unnecessary. This patch strips out non-essential data from the array returned by get_plugins(). wp-includes/update.php:146" logikal16 24078 Remove 'admin' as default username in install Upgrade/Install 3.5 normal normal Future Release enhancement new commit 2013-04-13T19:07:29Z 2013-05-05T21:06:45Z "The installation process populates the username field with 'admin' by default. Many/most users probably leave it as-is, making them more vulnerable to brute force attacks that look out for ""admin"" usernames. Seems a pretty easy improvement to specify no default username, and force the user to choose one themselves. " chrisrudzki 21874 Remove unused functions in wp-admin/includes/update.php Upgrade/Install 2.8 normal minor Awaiting Review enhancement new has-patch 2012-09-12T05:13:06Z 2012-09-12T10:22:52Z Just noticed these two functions, `wp_update_plugin()` and `wp_update_theme()`, which aren't used anywhere in core, and haven't been for a very long time far as I can tell. Looks like redundant code. solarissmoke 24081 Simplifying the 5 minute setup Upgrade/Install normal normal Awaiting Review enhancement new dev-feedback 2013-04-14T05:22:53Z 2013-04-14T06:14:21Z I decided to simplify the five minute setup. I teach a beginners class for WordPress, since it was badly needed and people usually get really confused when it asks for a database name and username. Please add onto my quickly written tutorial.php and let me know if you would be interested in putting it as a link in the five minute setup. ryansatterfield 17451 Unify plugin update notices and include changelog data nacin* Upgrade/Install normal normal Future Release enhancement accepted 2011-05-16T09:23:25Z 2013-01-16T00:27:00Z "Currently the after_plugin_row hook is only used on plugins.php which is used by the Changelogger plugin to show plugin changelogs inline. If the hook is also added to the bottom of list_plugin_updates in update_core.php then changelogs could also be displayed on that page too. It's only a single line change so not sure how/if it's worth me attaching a patch for this?" dempsey 18577 Updates and downloads should be signed or delivered securely Upgrade/Install normal normal Awaiting Review enhancement new dev-feedback 2011-09-03T01:23:16Z 2011-09-03T12:05:36Z "All channels for downloading Wordpress installations and plugins (e.g. from downloads.wordpress.org) should either be signed or delivered securely (e.g. via SSL) to mitigate man-in-the-middle attacks. Such attacks can lead to arbitrary code execution. It appears that currently, downloads and automatic updates are neither signed nor delivered securely." wplid 4027 Upgrade function don't do ANY error checking whatsoever Upgrade/Install 2.1.2 normal normal Future Release enhancement new 2007-03-25T12:58:51Z 2009-06-14T13:43:39Z "When I upgraded from 2.0.5 to 2.1.2, there was an error in my MySQL privileges, so the ALTER TABLE commands failed: {{{ WordPress database error: [ALTER command denied to user 'aasmunds'@'localhost' for table 'wp_categories'] ALTER TABLE wp_categories ADD COLUMN link_count bigint(20) NOT NULL default '0' WordPress database error: [ALTER command denied to user 'aasmunds'@'localhost' for table 'wp_categories'] ALTER TABLE wp_categories ADD COLUMN posts_private tinyint(1) NOT NULL default '0' WordPress database error: [ALTER command denied to user 'aasmunds'@'localhost' for table 'wp_categories'] ALTER TABLE wp_categories ADD COLUMN links_private tinyint(1) NOT NULL default '0' }}} There were also a lot of secondary errors due to the above failed commands. However, the upgrade.php script still claimed that all was well: {{{ There's actually only one step. So if you see this, you're done. Have fun! }}} It would be more helpful if WP would detect the MySQL errors and actually say that something went wrong and must be fixed, instead of saying that all is well even though there were heaps of errors. This only happens once: If I run the upgrade.php script again, it just says 'all is well' without any errors, so the MySQL commands that would fail are not run again. However, the database is still broken. It would be better if WP discovered that an upgrade failed, and set a flag somewhere that said 'this upgrade must be run again'. See also http://wordpress.org/support/topic/111398?replies=2 " skjaeve 11093 allow instalation customisation - code included and tested sorich87* Upgrade/Install 2.9.1 normal minor Future Release enhancement accepted has-patch 2009-11-07T14:34:40Z 2010-07-28T08:20:56Z "Current Wordpress can have own instalation using instal.php file in /wp-content folder. The problem is, that this file can ovewrite only wp_install a wp_install_default functions, which are run AFTER both whole setup-config.php and install.php files were run. So e.g. it is not possible to add own logo to the instalation script, own input for e.g. predefining blog description ... I have made very small changes to the install.php file a) add if ( !function_exists( ... ) ) before all (2) functions in this file b) create 'check_blog_installed' function as enclosure for part with blog checking with !function_exist check again, so it can be also owerwritten c) create step_0, step_1, step_2 functions, and adding content of code parts run when $step = 0 or 1 or 2, again with !function_exist, so every step can be simply ovewritten d) create display_footer with !function_exist check and move footer to it, so even footer can be overwritten. I have made no other functions to install.php (even i think it should be revised because of not so nice code as other wordpress) because i think it should be next step the functions i have created should not be a problem, as they are only in scope of instal.php file" thomask 11733 do a sanity check when conduction upgrades Upgrade/Install 2.9 normal normal Future Release enhancement new 2010-01-06T00:42:24Z 2010-02-18T10:51:33Z "In the FTP transports, and possibly in the SSH transport, we should look into conducting a quick sanity check after WP transfers a file during upgrades. This would be in the event that a network problem occurs during the upload. Depending on how robust we want it, it could be as simplistic as checking the file's size, or as complex as using md5_file()." Denis-de-Bernardy 18826 wp_maintenance() expiration time needs to be filterable Upgrade/Install 3.3 normal normal Awaiting Review enhancement new dev-feedback 2011-09-30T15:09:16Z 2011-10-01T01:23:22Z ".maintenance files expire after 10 minutes if something goes wrong. 10 minutes is a long time, when most upgrading operations are attempted and fail within 20-60 seconds. I propose three things: 1. changing the default expiration to 5 minutes (300 seconds) 2. Adding a filter to allow plugins and themes to filter this time to increase/decrease it 3. Also, while I was in there, it seems prudent to attempt to delete the file if it has expired. The only argument I could see against this is that possibly it might be expensive if the file can not be deleted and wp attempts to delete the file on every page load. So I can take or leave 3 (and 2), but #2 I think is really important." jaredh123 9757 Allow Plugin/Theme updates from a uploaded .zip file. Upgrade/Install 2.8 low normal Future Release feature request new dev-feedback 2009-05-08T00:17:07Z 2011-06-06T03:02:12Z "Plugin administration lacks of an update possibility by uploading zip files. This feature is only half-done in 2.7, you can only upload plugins as zip to install them, not to update them. Zip file uploads should be treated the same as the other install/update possibilities like remote. #9708 provides a testcase that can be used to test such am update by zip. currently a over-upload in the install page does throw an error that the directory already exists: {{{ * Dashboard * * Posts Posts o Edit o Add New o Post Tags o Categories * Media Media o Library o Add New * Links Links o Edit o Add New o Link Categories * Pages Pages o Edit o Add New * Comments 0 * * Appearance Appearance o Themes o Widgets o Editor o Add New Themes o Custom Header * Plugins 0 Plugins 0 o Installed o Add New o Editor * Users Users o Authors & Users o Add New o Your Profile * Tools Tools o Tools o Import o Export o Upgrade * Settings Settings o General o Writing o Reading o Discussion o Media o Privacy o Permalinks o Miscellaneous * Help Documentation Support Forums Help Installing Plugin from uploaded file: 9708-plugin-testcase-9708-plugin-a-v-0.2.zip Unpacking the package. Installing the plugin. Destination folder already exists. [...]worpress-trunk/wp-content/plugins/9708-plugin-testcase/ Plugin Install Failed. }}} " hakre 14781 Allow upload of PHP files as plugin Upgrade/Install normal normal Future Release feature request new dev-feedback 2010-09-04T13:28:06Z 2011-10-15T13:24:46Z Currently allowed are only ZIP packages. Plugins that consist of a single PHP file are not supported. It would be handy if uploading a single PHP file is an option. hakre 15738 Automate Security Releases Upgrade/Install normal trivial Future Release feature request new dev-feedback 2010-12-08T21:11:49Z 2012-12-03T23:27:46Z "When security releases are published, several less tech-savvy users might neglect to update in fear of breaking their site. In reality, security/maintenance releases don't change the core API and shouldn't break anything*. We should have an option (disabled by default) that allows these X.X.1-style security updates to happen in the background. This will keep sites updated and secure and (hopefully) prevent the inevitable ""I wanted to wait to install 3.0.2 and someone hacked my site while I was waiting"" support requests. The option should be disabled by default, but when users are on the update screen they should see an option to ""install security releases automatically."" Major releases should always require an explicit action from the user to update the site as they can break themes and plug-ins and could potentially update database schema. * Except in the rare occasion where a developer hacks core." ericmann 22704 Automatic Core Updates pento Upgrade/Install 3.5 normal normal Awaiting Review feature request assigned dev-feedback 2012-12-03T22:05:04Z 2013-01-14T18:12:02Z "It's time to think about automatic updates for WordPress Core. Plugins and Themes are a totally different ball game, so it's probably best to leave them for the moment. Currently, I'm thinking it would be a good idea to release this in stages (some of which may be combined, just spelling them out): - SVN updates in trunk installs - SVN updates in branch installs - Opt-in updates in stable installs - Opt-out updates in fresh installs - Opt-out updates in all installs - Remove option for opting out I'd like to see SVN updates go into 3.6 early, so we can quickly get a good idea of compatibility issues that we're likely to run into when we get to beta. Finally, are there any features we should be looking at adding to the upgrader for this? More sanity checking, notifications, other?" pento 16491 Automatically backup database before updating Upgrade/Install 3.0.5 normal normal Awaiting Review feature request new dev-feedback 2011-02-08T16:45:15Z 2011-03-25T13:38:49Z "Currently when updating Wordpress or its plugins/themes there's a message at the top of the page, reading that the user should backup its database. This ""update tool"" would be so much more useful, if it could backup the database automatically before updating. I'm not so sure why one would need to backup the files so this step could most likely be skipped." manski 10476 Option to export .zip backup before auto upgrade of wp/plugins Upgrade/Install 2.9 normal normal Future Release feature request assigned 2009-07-24T17:53:14Z 2012-01-06T23:18:05Z "Has there been any discussion on an option to export WP and plugin files in a zip before the auto upgrade process begins for either? The upgrade process is so easy now most users don't take proper backups first. I'd be glad to work on a patch file, but wanted to get thoughts on this feature first?" williamsba1 15977 Send the Locale in Plugin/Theme Update Check Requests nacin* Upgrade/Install 3.1 normal normal Future Release feature request accepted early 2010-12-25T20:59:43Z 2013-01-22T00:00:56Z "Currently, we send locale (and other information about installation) only in wp_version_check and not in wp_update_plugins and wp_update_themes. Since we still don't know how system for plugins/themes localization will work, I propose that we send this from 3.1. Why? As said above, there is no definitive agreement on how will localization system work, but it is possible that system wont require changes in core, ie. be same or similar to one I [http://wppolyglots.wordpress.com/2010/12/10/proposal-for-plugins-localization-system/ suggested] over at Polyglots. In that case localization system will be made independently what means that it'll can start working before 3.2 version. If we don't send locale for plugins/themes, we will need to wait for 3.2 even though that wont be significant change. In theory, plugin/theme developers could also benefit if alongside locales, we would send all information we send in wp_version_check and later show them as are plugin versions shown now. I know that is very late for this change but issue with plugin localization tool has been ignored for a very long time as I described in my post mentioned above in more detail." dimadin 10989 Show changelog for core upgrade nacin* Upgrade/Install normal minor Future Release feature request accepted 2009-10-21T01:36:14Z 2011-11-15T01:53:20Z "When clicking on the admin notice that there is an update available, it would be interesting to see a short changelog with a link to the complete changelog of the upgrade besides the two download buttons Example with the 2.8.5. Show on the page: The headline changes in this release are: * A fix for the Trackback Denial-of-Service attack that is currently being seen. * Removal of areas within the code where php code in variables was evaluated. * Switched the file upload functionality to be whitelisted for all users including Admins. * Retiring of the two importers of Tag data from old plugins. More info : http://wordpress.org/development/2009/10/wordpress-2-8-5-hardening-release/" petervanderdoes 18201 Verify updates with md5 checks Upgrade/Install low normal Future Release feature request new 2011-07-21T21:18:07Z 2012-12-03T23:50:16Z "Before an update, we should verify core files with a list of md5s, returned through the API. We should do this in order to determine whether we can safely do a partial build, or if we should just copy over everything. During the update, we can avoid copying over any files that are up to date, as verified by md5 results beforehand. This should save a number of FTP calls, in particular. After the update, we should md5 files we've copied over, and see if anything went wrong, and try again if necessary. Unfortunately we don't always know why updates fail, so we're going to need to test the hell out of this and see what kinds of cases we can cover. (Maybe it's time for error reporting back to WP.org?) Any other thoughts?" nacin 10666 When an upgrade borks, There needs to be an ability to rollback Upgrade/Install normal normal Future Release feature request new 2009-08-20T21:46:58Z 2010-02-15T01:48:44Z When an upgrade borks, there should be a simple script that allow you to rollback to the previous version. It should be mostly separate from the admin interface and allow for the restoration of both a database and the files associated with the previous version. jorbin 19207 dbdelta supporting foreign key Upgrade/Install 3.2.1 normal normal Awaiting Review feature request new 2011-11-08T19:10:44Z 2012-07-02T09:54:41Z Is there a plan to include support for foreign key inside dbdelta function? manutdotcom 20947 feature request: one-click update for core, themes and plugins (all in one) Upgrade/Install normal normal Awaiting Review feature request new dev-feedback 2012-06-13T22:48:50Z 2012-06-13T22:49:28Z I'd love to have the one-click update be truly one-click so that you can click once and update core, themes and plugins all at once as opposed to having to initiate three different updates. jkudish 18289 Direct link to plugin installation should have admin chrome nacin Upgrade/Install normal normal Future Release task (blessed) reviewing has-patch 2011-07-29T06:02:19Z 2011-11-10T19:05:23Z "We should be able to provide a direct link to the page to install a plugin, based on the plugin's slug. This does it: wp-admin/plugin-install.php?tab=plugin-information&plugin=log-deprecated-notices. However, there's no admin chrome, no real indication which site you're on, and no name of the plugin. If we're not loading that page inside an iframe request, it needs the admin around it, as well as a heading. Probably new styling too. This would serve as a replacement for [http://coveredwebservices.com/wp-plugin-install/ Jaquith's bookmarklet], which broke in 3.2 (frame busting), as well as allow us to integrate a link on extend/plugins for plugin installation. Related, #16923, which is now closed." nacin 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 18200 Language Packs nacin* Upgrade/Install normal normal Future Release task (blessed) accepted has-patch 2011-07-21T21:09:28Z 2013-04-04T21:10:54Z "Implement language packs for core, plugins, and themes. Inspiration and code can hopefully be derived from the corresponding GSoC project. This will require quite a bit of work in GlotPress, on api.wordpress.org, and in core. I will take point, but assistance will be needed. A number of decisions will need to be made. I will begin designing a document for what exactly needs to be done over the next week." nacin 23685 Explicitly globalize version variables Unit Tests trunk normal normal Awaiting Review defect (bug) new has-patch 2013-03-04T11:00:09Z 2013-03-04T17:24:03Z "When WordPress is loaded in a function (e.g. unit tests) the variables initialized at the top level aren't globals, but we expect them to be. For example, if in a unit test there is no way to access `$wp_version`. Neither via `$wp_version` (it's not in the same scope), not via `$GLOBALS['wp_version']` (it's not a global). To fix that we need to explicitly make the version variables global. See #17749." nbachiyski 24173 Unit tests: Support subdirectory multisite installs Unit Tests normal normal Awaiting Review defect (bug) new has-patch 2013-04-24T05:57:49Z 2013-04-24T09:06:15Z "I have unit tests set up at: localhost/wordpress-tests/ And have set: `define( 'WP_TESTS_MULTISITE', true );` However, currently, unit testing doesn't support subdirectory multisite installs. It fails when installing multisite. Attached patch addresses this and introduces a new constant called `'WP_TESTS_PATH'`. If this is set in `wp-tests-config.php`, this will make sure that PHPUnit can install WP for subdirectory multisite installs." r-a-y 23531 Separate tests into unit / integration / ... directories Unit Tests trunk normal normal Awaiting Review enhancement new 2013-02-19T15:51:16Z 2013-02-19T15:51:16Z "To improve the speed how tests can be run - especially the unit-tests - I suggest to divide tests into sub-directories, for example: ''unit'' - for unit tests[[BR]] ''integration'' - for integration tests[[BR]] ''functional'' - for functional tests Right now all tests are roughly labeled as ""Unit-Tests"" even they are not unit-tests per-se, e.g. some of them interacting with the database or the file-system. Background: [http://stackoverflow.com/q/4904096/367456 What's the difference between unit, functional, acceptance, and integration tests?]" hakre 23532 Sync Tests Repository on Github Unit Tests normal normal WordPress.org enhancement new 2013-02-19T15:56:53Z 2013-04-18T13:31:26Z "Like with Wordpress, the tests should be synched as well with a git repository under https://github.com/WordPress/ Especially after taking in https://github.com/nb/wordpress-tests" hakre 20175 """Trash"" should not be a bulk action when user can't delete a post at all" Trash 3.3.1 normal normal Awaiting Review defect (bug) new has-patch 2012-03-04T15:20:19Z 2013-01-09T03:55:37Z "When a user can't delete posts at all for a certain post type the bulk action to delete posts is useless. Not sure if the following check is correct: {{{ if ( current_user_can( $post_type_object->cap->delete_post ) ) { if ( $this->is_trash || !EMPTY_TRASH_DAYS ) $actions['delete'] = __( 'Delete Permanently' ); else $actions['trash'] = __( 'Move to Trash' ); } }}} Maybe the edit/restore functionality should have some similar check" markoheijnen 19826 Error behavior for deleting trashed posts is different for Bulk Delete versus Empty Trash Trash 3.1.2 normal minor Awaiting Review defect (bug) new dev-feedback 2012-01-13T18:38:00Z 2012-06-19T19:34:42Z "Bug testing a custom blog build, but I may have located a bug with core (wp-die) Trash error messages. Background: *The blog has different users, with different roles. *Issue occurs on trash page of a custom post type (post status = trash .../edit.php?post_status=trash&post_type=subject) *Trash contains posts by both an admin role (who can add/edit/delete all custom posts) and an author role (who can add/edit/delete his/her own posts). *Logged in as an author. *Using Capability Manager Plug-in. (Tested bug without plugin too) *Issue is specific to behavior after normal WP-error is thrown. Issue: Same WP error. Two different behaviors. Different functionality occurs between using the Bulk Actions (Delete Permanently) > ""Apply"" button and the ""Empty Trash"" button, after a normal WP error is thrown. In the first case (Bulk Actions > Apply [1a below]), after I return from the error page and refresh the Trash page, all of the selected author pages have been deleted. No admin pages have been deleted. In the second case (""Empty Trash"" [1b below]), after I return from the error page and refresh the Trash page, all of the selected author pages have NOT been deleted. No admin pages have been deleted. Behavior: 1a. When I am logged in as an author and I highlight posts by both author and admin, and I attempt to delete using Bulk Actions (Delete Per.) > ""Apply"", I receive the WordPress error ""You are not allowed to delete this item."" ///After I return from the error page and refresh the Trash page, all of the selected author pages have been deleted. No admin pages have been deleted. 1b. When I am logged in as an author and I highlight posts by both author and admin, and I attempt to delete using ""Empty Trash"" button, I receive the WordPress error ""You are not allowed to delete this item."" ///I return from the error page and refresh the Trash page, all of the selected author pages have NOT been deleted. No admin pages have been deleted. returning to the Trash page. Tested both scenarios. 1. I hit back on the browser, and return to the Trash page. I refresh the page. 2. Move to a different WP admin page, not the Trash page, then return to the Trash page. Question, because the same text/error is thrown for both buttons, why is the functionality different? Both single functions seem appropriate, however, having both functions exist together instead of picking one behavior seems problematic." jpbellona 22350 Restored Drafts Shouldn't Have a Publication Date Trash 3.4.2 normal normal Awaiting Review defect (bug) new 2012-11-03T00:07:39Z 2013-01-19T00:00:40Z "After creating a draft, trashing it, and then restoring it, the post editor shows a ""Publish on"" date as though it were a scheduled post, and the Date value in the list of all posts will be wrong after further editing (e.g. ""3 hours ago, Last Modified"")." miqrogroove 12826 AJAX trash posts Trash 2.9 normal normal Future Release enhancement new has-patch 2010-04-03T02:57:06Z 2012-12-20T23:57:15Z "Add AJAX to trash posts, like comment moderation. From GSoC ideas list: >Add AJAX Paging to Admin Screens. Something we've never gotten around to is adding AJAX paging to the list-type screens (edit.php, etc). Currently, getting to the next page of items means a screen refresh. For this project, add ajax paging to all the list-type screens in the WordPress admin. We have all the underlying PHP, but it needs some JavaScript love." meheranandk 23022 Always set posts to draft status when untrashing Trash 2.9 normal normal Awaiting Review enhancement new dev-feedback 2012-12-20T15:00:43Z 2013-01-16T05:51:21Z "In some situations it is bad when trashed posts immediately go live after being untrashed. Such as: * A published post is found to have libellous/wrong/other_bad content in it * Admin trashes the post * Admin wants to edit the post and republish it without the bad things * Admin cannot do this without republishing the bad things, which they cannot do. I appreciate that the user should have unpublished the post rather than trashing it but people don't always think clearly in these situations, and once you're in it, you can't get out -- your options are to republish, permanently delete, or leave the post in limbo. I did wonder if it would be better to make trashed posts viewable/editable in the admin but that felt like a pretty big move, and one that would make the status of a trashed post much less clear and rather ambiguous. So, the attached patch sets all untrashed posts to draft status, rather than restoring their original status, which was the only other thing I could think of. (Definitely happy to debate alternative solutions)" harrym 11863 Trashed items interfere with page/post slug generation Trash 2.9 normal normal Future Release enhancement reopened 2010-01-11T12:40:38Z 2012-09-23T19:10:06Z "Create a static page called test. Trash it. Create a new static page called test. It'll want to use the slug ""test-2"" instead of the expected ""test"". This is extremely confusing for non-technically oriented users." Denis-de-Bernardy 22660 "Admin bar in multisite: mobile tap on ""My Sites"" dropdown in back-end doesn't work" Toolbar 3.4.2 normal normal Awaiting Review defect (bug) new 2012-11-30T20:40:17Z 2012-12-21T00:33:39Z "Quick steps here to reproduce an issue where the ""My Sites"" dropdown (multisite networks) will drop down and show the ""Network Admin"" link and the list of your sites. But, clicking on a site (to expand and see ""Dashboard"", ""New Post"", etc.) does not happen. Tapping the blog name just closes the dropdown. I'm not sure what's different but I can consistently reproduce this when in the admin back-end (but works OK on front-end admin bar when viewing a site): From /wp-admin/ on a mobile device (tested on iOS 6, iPhone 5, iPad) with a multisite network: 1. Tap ""My Sites"" in admin bar 2. See ""Network Admin"" and list of sites below 3. Tap one one of the site names Expected: Site name expands to show ""Dashboard"", ""New Post"", etc. (same behavior as front-end when viewing site). Screenshot: http://d.pr/i/reOi Actual: Tapping site name simply closes the ""My Sites"" dropdown, does not browse anywhere nor expand menu" devinreams 22247 "Ensure post ID evaluates to true before adding ""Edit post"" tab in admin bar" Toolbar 3.1 normal normal Awaiting Review defect (bug) new has-patch 2012-10-21T20:45:27Z 2012-11-13T01:37:13Z "This patch checks that a post has an ID set before adding an ""Edit post"" link in the admin bar on the front-end for individual post pages and static pages. This can be helpful for plugins that choose to create a ""fake"" page that does not exist in the database, and set their ID to ""0."" An example of such a fake page can be seen on my [http://wordpress.org/extend/plugins/on-the-fly-youtube-embeds/ On The Fly YouTube Embeds] plugin which borrows a lot of code from Scott Sherrill-Mix's blog post: [http://scott.sherrillmix.com/blog/blogger/creating-a-better-fake-post-with-a-wordpress-plugin/ Creating a (Better) Fake Post with a WordPress Plugin]" Joe Anzalone 23496 Front-end admin toolbar dropdowns inaccessible on Chrome/Android Toolbar 3.5 normal normal Awaiting Review defect (bug) new 2013-02-17T23:45:36Z 2013-02-17T23:46:04Z "The dropdown menus that appear on the first touch of admin toolbar menus with sub-items are inaccessible because the top level menu URL is triggered. Steps to reproduce: 1. Visit the front-end of your website using Chrome on Android. 2. Click an admin toolbar menu item that has sub-items, eg. the Add New menu, the site name menu or your user profile menu. 3. The sub-menu is triggered, but the browser also immediately navigates to the URL of the top level menu item. The issue doesn't occur when using these menus in the admin area. Tested using Chrome 18 on Android 4.2. Theme is TwentyTwelve." johnbillion 15317 My Sites limited to 23 sites on Admin Bar Toolbar 3.1 low normal Future Release defect (bug) new has-patch 2010-11-04T13:35:21Z 2012-08-26T08:16:23Z "I have a test site with 25 sites. I can only access 23 from the My Sites tab on the admin bar. (This is a minor bug, but I hadn't seen it mentioned.) Ron I'm using latest trunk." ronbme 23371 Subdir front-end Toolbar bug on first login Toolbar 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2013-02-02T22:36:59Z 2013-02-04T20:17:25Z "In an obscure set of circumstances, I encountered a small bug where the Toolbar doesn't display on the front-end of a subdirectory install on the first login where the site URL points to the root domain. `show_admin_bar_front` is rightly set to true both on first and second+ logins, but the Toolbar doesn't display on the front-end. The js isn't even being loaded. I can reproduce this all the way back to 3.3. To reproduce: 1. Install a fresh copy of !WordPress in a subdirectory. 2. Login. 3. Change site url to point to the main domain. 4. Visit the front-end, observe the Toolbar isn't displayed. 5. Logout. 6. Login again. 7. Re-visit the front-end, observe the Toolbar now displays as expected. I'm unable to trace back what's causing the Toolbar not to be displayed after the initial login. Maybe we should just force the user to login again after changing the site url." DrewAPicture 19380 There is no way to specify placement of a new menu item in the Admin Bar Toolbar 3.3 normal minor Future Release defect (bug) new 2011-11-28T14:38:12Z 2011-11-28T17:16:46Z "I recently opened ticket #19371 and scribu has added a fantastic and simple solution to be able to modify existing menu items. The only problem, however, is that it is impossible to control placement of a new menu item. For example, if I wanted to add a class on the ""wp-logo"" menu item, I would use the method specified in #19371 to remove it, modify it, and add it back. {{{ add_action( 'admin_bar_menu', function( $admin_bar ) { $node = $admin_bar->remove_menu( 'wp-logo' ); $node['meta']['class'] = 'foo'; $admin_bar->add_menu( $node ); }, 99 ); }}} The only problem is that it would put the menu item at the far right of the other menu items. I could then remove and re-add all the other menu items. However I don't think there is a way to get a list of all the top level menu items from within the admin bar class, so you would have to know the ID of each one from a print_r debug of the object and hard code the items in. This would break if a plugin added a menu item that wasn't in the hard coded list. My thoughts would be either add a parameter to the add_menu() function such as priority, which could be boolean and cause the item to be added with array_unshift() instead of the current method, or a parameter that would be be for the id to ""add before menu item x"" , or just a method that would return a list of ids of the root menu items. ps: I don't really need to add a CSS class to the wp-logo menu item, but this is the far-left-most item and I thought it would make the best example." willshouse 22505 Toolbar dropdowns don't hide on front end on tap away Toolbar 3.4.2 normal normal Awaiting Review defect (bug) new 2012-11-19T14:46:03Z 2012-12-01T21:12:52Z "In the wp-admin pages I can open the Howdy or New menus and tap away to close them. In the front end admin bar, the menu stays open until navigating to a new page. Found on 3.5-beta3-22637 using iPad3 iOS 6.0.1." miqrogroove 18556 Toolbar dropdowns when dragging items drecodeam* Toolbar 3.2.1 normal normal Awaiting Review defect (bug) accepted has-patch 2011-08-31T19:15:17Z 2013-01-22T01:17:35Z "When dragging metaboxes, widgets, menu items, etc to the top of the window in order to scroll to drop the item on a portion of the UI that's above the viewing window, the toolbar interferes and produces dropdowns, etc. If dragging an item, can we disable toolbar actions? " chexee 22519 iPad toolbar location Toolbar normal normal Awaiting Review defect (bug) new 2012-11-20T17:45:44Z 2013-04-15T15:34:13Z "The toolbar moves after using quick edit on a post or page. Also the customizer button look strange on iPad. Steps to reproduce 1: Click quick edit on a post 2: Click ""Allow Pings"" 3: Now the admin toolbar should be be lower on page. (I was able to reproduce 4/5 tries)" MikeHansenMe 19541 wp_admin_bar_new_content_menu does not respect menu_position nacin* Toolbar 3.1 normal normal Future Release defect (bug) accepted has-patch 2011-12-14T02:19:30Z 2012-11-07T22:01:32Z "'''What is happening:''' When registering a custom post type, you can specify the position in the left-hand admin menu by using 'menu_position' to move it up or down in the list. However, the admin bar ""new content"" list does not use this same order, instead it will always display ""Post"", ""Media"", ""Link"", ""Page"" (in that order) before any custom post. '''What should be happening:''' The admin bar ""new content"" list should respect the menu_position attribute." davistobias 19979 Load jQuery on the front end for logged-in users Toolbar normal normal Future Release enhancement new 2012-02-06T22:43:32Z 2012-02-06T22:43:32Z "This will let us simplify the toolbar JS and improve user experience: hoverIntent, additions by plugins that require jQuery, etc. jQuery can be loaded in two different ways: - Directly, by enqueueing it with script_loader and then adding `wpjq = jQuery.noConflict(true);` where `true` means other version of jQuery will be left with the globals. - By outputting some JS at the very end of 'wp_footer'. This JS would be able to check whether jQuery is already loaded and if not, load it by appending a `