ticket summary owner component _version priority severity milestone type _status _created modified _description _reporter keywords 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 gci needs-testing needs-patch 15729 Better UX after supplying incorrect information to setup-config kapeels* Upgrade/Install low normal Future Release defect (bug) accepted 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 gci has-patch 3.2-early 13392 Image editor UX could be more straightforward Media 3.0 normal normal Future Release enhancement new 2010-05-14T13:54:06Z 2013-02-08T17:15:27Z "The image editor introduced in v2.9 (?) is pretty handy, but I believe the UI needs to be straightforward. Here's some issues which I see, as a starter for discussion, and hopefully later I'll be able to make some quick wireframes to suggest improvements and so everyone can have something to get hating. The overarching issue is that the UI seems confused when it comes to committing the action you've just taken, for example: * To scale an image, you commit the action with a button labelled ""Scale"". * To commit a crop you have to click the crop icon button, which looks like a tool selection button (ala Photoshop) rather than something which commits the change. * The Save button is disabled most of the time, for reasons which are unclear, but it's not super obviously styled as disabled. Separately from the problems of committing actions, the ""Apply changes to"" panel is kind of stuck down to the right and it's not clear at which points it's having an effect. There are no messages back to the user to confirm whether actions have or haven't been taken. " simonwheatley needs-ui gci close 15448 wp_mail() sets Content-Type header twice for multipart emails nacin Mail normal normal Future Release enhancement reviewing 2010-11-17T12:15:04Z 2013-05-16T12:09:18Z "When trying to send emails via `wp_mail()` with a Content-Type of multipart/alternative, the Content-Type header will be set with `$phpmailer->ContentType`, and again with `$phpmailer->AddCustomHeader()`, which causes two Content-Type headers in the email: {{{ Content-Type: multipart/alternative; boundary=""example_boundary"" Content-Type: multipart/alternative; charset="""" }}} This appears to cause errors in Outlook, as there is no boundary on the latter. The cause of this is `PHPMailer::GetMailMIME()`, as it does not know that the email is a multipart email. The easiest way to achieve this appears to be to simply allow the user to set the AltBody via `wp_mail()`. In order to achieve backwards compatibility, `wp_mail()` should work out which part is the text/plain one and which is the text/html one based on the boundary. I'll be working on a patch for this." rmccue gci has-patch westi-likes needs-refresh 7652 Merge all atom parsers rmccue Import normal normal WordPress.org enhancement closed 2008-08-30T20:56:29Z 2012-10-31T20:53:09Z "Currently we have two Atom Parsers. One for the Blogger Importer and one for our APP implementation. We need to only have one!" westi has-patch needs-review gci westi-likes 14847 Update featured image data in WXR import Import normal normal WordPress.org enhancement closed 2010-09-11T16:29:33Z 2011-02-02T13:45:08Z "WordPress export files currently do not contain information on featured image selection. Users moving a WordPress blog from one location to another have to manually re-select featured images for every post once the import is completed." markel has-patch gci 13821 Changing visibility to password-protected without entering a password does not warn user kapeels* General normal normal Future Release defect (bug) accepted 2010-06-10T13:48:48Z 2012-10-01T17:42:25Z "Tested on r15182. If the status of a post is set to Password Protected, and a password is not specified before the user clicks the OK button in visibility and then either publishes, saves, or updates the post, no warning is given to the user that not setting a password forces the post or page to remain Public. In fact, if updating a post, and this is the only change made, the success message (1) for updating the post appears instead, even though no change was made to the post. If the post was previously published as Private, and switched to Password Protected without entering a password, then saved, the post switches to Public on save instead of remaining Private. Either a failure message upon updating or a warning to the user before saving should be displayed to the user to remind them that they didn't properly set a password. To reproduce the last case above: 1. Create a post. Publish it as Private. 2. Edit the post. Change the visibility to Password Protected, but do not enter a password. Click OK. 3. Update the post. 4. The post visibility will be changed to Public." markel ux-feedback has-patch gci 3.2-early needs-refresh 14288 Category RSS feeds in querystring format return wrong feed MarkJaquith General 3.0 low normal 3.1 defect (bug) closed 2010-07-12T21:08:29Z 2010-12-14T19:47:12Z "In WordPress 3, using category specific RSS feeds in query string format as shown the first example here: [http://codex.wordpress.org/WordPress_Feeds#Categories_and_Tags]. WordPress returns the general site RSS feed. For example:[[BR]] [http://mirmillo.com/?cat=9&feed=rss2][[BR]] [http://ryan.boren.me/?cat=1517&feed=rss2] Returns the main site feed no matter which feed format you are using. " mirmillo needs-patch gci 14305 Display file for localized versions as Drop-in nacin General normal normal Future Release enhancement reviewing 2010-07-14T09:08:03Z 2011-03-26T08:37:42Z Localization teams can use special files (for example cs_CZ.php) to handle special problems. This file should be shown on Plugins page, probably as Drop-in, I guess... pavelevap has-patch 3.2-early gci 13066 Last-Modified headers for individual comment feeds are incorrect jgci* Feeds 3.0 low normal Future Release defect (bug) accepted 2010-04-21T07:32:34Z 2010-11-28T16:18:31Z "The WP::send_headers function currently uses get_lastcommentmodified() to set the Last-Modified header for all comment feeds. This is a problem when used for individual post comment feeds. The function gets the last modified comment across all blog posts. That means that every time a comment is posted anywhere, the Last-Modified header for ALL comment feeds is refreshed. Issues: 1. This is technically incorrect, since only the global comment feed and one specific post's comment feed have changed with the last comment (not all possible comment feeds); and 2. It means that If-Modified-Since requests for other post comment feeds will not receive a 304 response when they should do (since their content hasn't changed). On blogs with many posts and many comment feeds, this will have a large impact on bandwidth because lots of requests will receive 200 responses where 304's would have done, just because a comment was posted on some other post. If I've understood the flow correctly, $wp_query hasn't been fully set up at the time this function is called, so changing this behaviour would require some change in the flow of things (e.g., the handling of last modified headers for feeds moves into the do_feed() function). But doing so would mean that Last-Modified headers are correct/meaningful and that many more 304 responses can be served. Any thoughts?" solarissmoke dev-feedback gci has-patch 3.2-early 10660 Time zone suggester based on nascent WordPress.org API call rmccue Date/Time 2.8.4 normal normal Future Release feature request assigned 2009-08-20T05:59:42Z 2013-02-19T19:00:38Z "The attached patch uses a new API call to http://api.wordpress.org/core/ip-to-zoneinfo/1.0/ to retrieve a suggested time zone based on client (not server) IP address. A button is added next to the existing dropdown list of time zones providing the option to ""Suggest a time zone"". This calls the API using an AJAX/JSONP request which then auto-selects a time zone for the user from the dropdown. Visual feedback is via a spinner when fetching and then a text response. Additionally the Date and Time settings have been split out to a new settings page. Related ticket: #10324" sambauers has-patch gci 8420 Disable error redirects when in DOING_AJAX kapeels* Administration 2.7 low minor Future Release enhancement accepted 2008-11-29T00:28:10Z 2010-11-28T11:30:25Z If a DB/install error occurs in admin during ajax requests (like autosave), the response shouldn't return the whole redirected page, see $ATT (admin-ajax-install-trigger.png). If something goes awry and we're DOING_AJAX, an error message that could fit inline would be better. janbrasna has-patch 3.2-early gci 15926 Give header and background images alt tags Accessibility 3.0 normal minor Awaiting Review defect (bug) assigned 2010-12-20T22:16:12Z 2013-01-11T11:42:52Z "''Section 1194.22 Web-based Internet information and applications: (a) A text equivalent for every non-text element shall be provided (e.g., via ""alt"", ""longdesc"", or in element content).'' To meet accessibility guidelines, the header images and backgrounds (when supported by a theme) need to be given user-editable alt tags." jane gci has-patch ux-feedback