Example

` and `` elements. Originally reported in [http://wordpress.org/support/topic/gists-look-crazy-with-twenty-twelve this thread] and on wp.com. Example: http://themebuster.wordpress.net/gist-test/" obenland 14791 Twenty Ten Theme - Better Link Highlighting Bundled Theme normal normal WordPress.org enhancement new 2010-09-07T10:18:19Z 2012-09-27T13:42:49Z mainly changing the state of text decoration(underline/none). This aids users that tab through links on a page identify where they are. elfin 14792 Twenty Ten Theme - gallery changes Bundled Theme normal normal WordPress.org enhancement new 2010-09-07T10:22:33Z 2012-09-27T13:42:52Z With reference to #14791 those changes will produce an ugly 10px wide border in red on focus/hover etc. This patch does fix this, at the expensive of top/bottom margins. This therefore may need an additional patch before it can be applied. elfin 15385 Use get_template_part() for post formats in Twenty Ten Bundled Theme normal normal WordPress.org enhancement new 2010-11-11T13:36:47Z 2013-02-19T04:25:57Z "Let's encourage some standardization in themes by giving Twenty Ten the following: {{{ get_template_part( 'post-format', 'aside' ); get_template_part( 'post-format', 'gallery' ); }}} We'll leave the default in loop.php, I'm thinking, though we could also use post-format-default. I'm going to comment on #14746 that I think, if post formats are supported, then 'default' should always be supported and should be enforced as the default, even if nothing is stored yet for that post." nacin 19065 Please provide original javascript files (.dev.js) for all minified files nacin General normal normal WordPress.org defect (bug) reopened 2011-10-27T10:18:57Z 2012-06-15T09:01:46Z "Please provide original javascript files (.dev.js) for all minified files. This is not only useful for debugging, it's also a requirement of some free software distributions like Debian (cf the bug report that prompted all this: http://bugs.debian.org/646729). Missing files that I noted are (relative to wp-includes/js): {{{ crop/cropper.dev.js jquery/jquery.dev.js jquery/jquery.query.dev.js jquery/jquery.schedule.dev.js jquery/jquery.serialize-object.dev.js jquery/ui/*.dev.js (all *.js files are minified) plupload/plupload.*.dev.js (all plupload.*.js files are minified) swfupload/swfupload-all.dev.js tinymce/tiny_mce.dev.js tinymce/tiny_mce_popup.dev.js tinymce/plugins/*/editor_plugin.dev.js (all plugins except the WP ones) tinymce/themes/advanced/editor_template.js tinymce/wp-tinymce.dev.js.gz swfobject.dev.js }}} I'm not really sure about swfupload/swfupload-all.js, if it's swfupload.js + the 4 plugins minified, then it's ok I guess. But it would be nice to have it documented. tinymce/wp-tinymce.dev.js.gz is probably also generated from something else but I could not figure out what. It would be nice to document how and when to regenerate it. I can help to dig out the required files if it helps. Ideally the build process of wordpress would include a way to regenerate automatically the minified files from the corresponding .dev.js file." rhertzog 18249 Rosetta needs a facelift ryanimel* I18N normal normal WordPress.org defect (bug) accepted has-patch 2011-07-25T20:47:35Z 2013-04-09T19:21:07Z This is a Trac ticket for http://make.wordpress.org/ui/2011/07/25/small-design-project-rosetta/. nacin 20881 Show code references in inherited localization files I18N normal normal WordPress.org defect (bug) new 2012-06-07T20:01:31Z 2012-06-07T20:10:16Z "For example string ""Invalid post type"" is used several times - on frontend and also in admin. But this string is only in frontend localization file, because this file is also loaded on admin side. That is correct, no need to duplicate strings in different files. But translators do not see code references related to admin file and it can leads to context problems during translation. It could be very helpfull to modify makepot.php to add related code references to generated .pot files. Related example: #20809" pavelevap 21616 add-textdomain doesn't conform to WP coding standards I18N normal normal WordPress.org defect (bug) reopened 2012-08-17T03:07:19Z 2012-08-17T21:37:50Z I used add-textdomain.php from http://i18n.svn.wordpress.org/tools/trunk on my plugin code, but it does not include a space before the closing parenthesis of the gettext function call it alters, which violates http://codex.wordpress.org/WordPress_Coding_Standards#Space_Usage groovecoder 21444 update msgid-bugs-address for plugins in makepot.php I18N normal normal WordPress.org defect (bug) new 2012-08-01T20:09:09Z 2012-08-01T20:16:12Z "The msgid-bugs-address for plugins in makepot.php is outdated. References ""/tag/"" instead of ""/support/plugin/""." convissor 12322 Blog import fails to generate reduced-size images Import normal normal WordPress.org defect (bug) new close 2010-02-21T17:14:59Z 2012-02-14T16:25:41Z "I just imported from http://daveabrahams.wordpress.com (go ahead, try it yourself if you like) and chose to ""Import Attachments."" The only images from the original site that show up in the result are those that were originally displayed with size-full. The others need to be regenerated by inserting them freshly. " daveabrahams 21023 Blogger Importer Draft Status not processed correctly Import 3.4 normal normal WordPress.org defect (bug) new has-patch 2012-06-20T09:48:55Z 2012-06-20T14:57:20Z "The blogger importer is loading all drafts posts as published and/or scheduled. This is caused by an incorrect schema used in blogger-importer-blogitem.php. The correct schema is as follows {{{ define('SIMPLEPIE_NAMESPACE_ATOMPUB', 'http://purl.org/atom/app#'); }}} Ref: * http://wordpress.org/support/topic/plugin-blogger-importer-blogger-draft-status-changed-to-published-in-wp * https://developers.google.com/blogger/docs/1.0/reference#DraftEntries" Workshopshed 21163 Blogger Importer Invalid Tokens Import normal normal WordPress.org defect (bug) new 2012-07-05T11:53:00Z 2012-10-13T19:30:04Z "When the users clicks on the authorise button google responds with an invalid token error. This is obviously a bit puzzling for the users. See http://wordpress.org/support/topic/plugin-blogger-importer-invalid-token The problem seems to be that the form with the authorise button is actually passing blank tokens. I can't reproduce the problem but I've reproduced their symptoms by switching the URL in get_oauth_link to a non existant one. This returns blank tokens to the form. If you then submit that form you get the invalid token error. Although this following patch is not actually a fix, we can report the error properly with a change to get_oauth_link and greet and hence it will be easier to diagnose issues. {{{ // Shows the welcome screen and the magic auth link. function greet() { $next_url = get_option('siteurl') . '/wp-admin/index.php?import=blogger&noheader=true'; $auth_url = $this->get_oauth_link(); $title = __('Import Blogger', 'blogger-importer'); $welcome = __('Howdy! This importer allows you to import posts and comments from your Blogger account into your WordPress site.', 'blogger-importer'); $prereqs = __('To use this importer, you must have a Google account and an upgraded (New, was Beta) blog hosted on blogspot.com or a custom domain (not FTP).', 'blogger-importer'); $stepone = __('The first thing you need to do is tell Blogger to let WordPress access your account. You will be sent back here after providing authorization.', 'blogger-importer'); $auth = esc_attr__('Authorize', 'blogger-importer'); $errormsg = __('Error occurred getting OAuth tokens from Google', 'blogger-importer') echo ""

"" . screen_icon() . ""

$title

$welcome

$prereqs

$stepone

""; if (!is_wp_error($auth_url)) { echo ""

\n""; } else { echo $errormsg; echo '

                    '.$auth_url->get_error_message().'

' ; } } function get_oauth_link() { // Establish an Blogger_OAuth consumer $base_url = get_option('siteurl') . '/wp-admin'; $request_token_endpoint = 'https://www.google.com/accounts/OAuthGetRequestToken'; $authorize_endpoint = 'https://www.google.com/accounts/OAuthAuthorizeToken'; $test_consumer = new Blogger_OAuthConsumer('anonymous', 'anonymous', null); // anonymous is a google thing to allow non-registered apps to work //prepare to get request token $sig_method = new Blogger_OAuthSignatureMethod_HMAC_SHA1(); $parsed = parse_url($request_token_endpoint); $params = array('callback' => $base_url, 'scope' => 'http://www.blogger.com/feeds/', 'xoauth_displayname' => 'WordPress'); $req_req = Blogger_OAuthRequest::from_consumer_and_token($test_consumer, null, ""GET"", $request_token_endpoint, $params); $req_req->sign_request($sig_method, $test_consumer, null); // go get the request tokens from Google $req_response = wp_remote_get($req_req->to_url(), array('sslverify' => false)); if (is_wp_error($req_response)) { return $req_response; } $req_token = wp_remote_retrieve_body($req_response); // parse the tokens parse_str($req_token, $tokens); $oauth_token = $tokens['oauth_token']; $oauth_token_secret = $tokens['oauth_token_secret']; $callback_url = ""$base_url/index.php?import=blogger&noheader=true&token=$oauth_token&token_secret=$oauth_token_secret""; return array('url' => $authorize_endpoint, 'oauth_token' => $oauth_token, 'oauth_callback' => $callback_url); } }}} p.s. Sorry I've still not mastered DIFF!" Workshopshed 8578 Blogger import incorrectly reports saved user information Import normal normal WordPress.org defect (bug) new 2008-12-11T16:53:52Z 2011-09-16T03:52:31Z "I installed a fresh copy of WordPress 2.7 and was importing content from a Blogger site. Before beginning to import, the page claimed that Blogger account information was saved in the database and that I could restart the process. Even after pressing the ""Clear account information"" button, the message still appeared." covert215 6369 Blogger importer inefficient handling of data Import normal normal WordPress.org defect (bug) new 2008-03-24T03:58:47Z 2013-04-08T17:04:48Z If the import dataset is large, the Blogger importer can store huge amounts of data in the blogger_importer option. It then updates this data over and over throughout the import. If MySQL logging (binary or query) is enabled, this can result in a large amount of data being written to disk, potentially filling up the partition rather quickly. On WordPress.com, I have seen an import write 100MB of binary logs every 2 min. Andy's suggestion is that we split up the data from the import rather than store it in one option. This would allow us to manipulate it more granularly and prevent the huge updates from happening. barry 15034 DotClear Importer doesn't work with DotClear version 2.2.x Import normal normal WordPress.org defect (bug) new has-patch 2010-10-05T00:28:01Z 2011-01-13T06:33:10Z This was reported to me by Benjamin GIGON. He has provided a patch, but I am not able/unsure how to test it. briancolinger 23482 Fix improper use of comment_exists() in some importers Import normal normal WordPress.org defect (bug) new 2013-02-15T18:49:18Z 2013-02-15T18:49:18Z "Background: #20494 DotClear Importer and TextPattern Importer treat the returned comment post ID as a comment ID: [[BR]] http://plugins.trac.wordpress.org/browser/dotclear-importer/trunk/dotclear-importer.php#L416 [[BR]] http://plugins.trac.wordpress.org/browser/textpattern-importer/trunk/textpattern-importer.php#L429" SergeyBiryukov 16420 Flawed Blogger import, no details Import 3.1 normal normal WordPress.org defect (bug) new 2011-01-31T05:44:08Z 2012-10-13T19:08:52Z Did a Blogger import, showed as finished when it had imported 625/626 posts and 685/685comments. Did not give any indication as to why one post was not imported, which one it was, anything. Gah. Need to put in a feedback mechanism for this type of situation. jane 16012 Importer descriptions i18n nacin* Import 3.1 normal normal WordPress.org defect (bug) accepted has-patch 2010-12-28T18:41:00Z 2012-06-13T19:07:36Z "At first I've tried to create a ticket on http://plugins.trac.wordpress.org/, but none of the importers are present in the Component dropdown. So I've decided to try it here. As [http://wppolyglots.wordpress.com/2010/12/28/hello-another-string-which-i-couldnt/ noted by Rasheed Bydousi on WP Polyglots], importer descriptions are displayed in English. The problem is that `register_importer()` function is called before the language file is loaded. I've created patches for all the importers. I've also changed `init` action to `admin_init`, which seems to have more sense in this case." SergeyBiryukov 24221 Importer doesn't import properly Import 3.5 normal normal WordPress.org defect (bug) new 2013-04-29T12:03:24Z 2013-04-29T12:13:19Z "This is what [Tools > Export] generated: {{{ Example http://example.com/?page_id=4477 Sun, 03 Feb 2013 12:10:10 +0000 admin http://example.com/?page_id=4477

Heading

Paragraph

something in the end]]> 4477 2013-02-03 12:10:10 2013-02-03 12:10:10 closed closed [...] }}} And now, when I try to import that (exactly in unmodified form) it strips {{{ style=""padding: 3em 0 0 0; margin: 0 0 3em 0; background-color: rgba(195, 195, 195, 0.15);"" }}} part in some places but not all (I guess this is important)! And it doesn't strip it when I go to [Pages > Example] and switch to ""Visual"" editor or update the page. It is imported this way (already wrong). I'm absolutely sure that this happens, tested several times and I can't find an error or explanation. Export file: UNIX, UTF-8 w/o BOM. Importer Version: 0.6 Plugin URL: http://wordpress.org/extend/plugins/wordpress-importer/ I've seen a couple of issues related to ""update_post_meta"" that is stripping quotation marks etc. Maybe this is related. Installation: WPMU (unfiltered_html is probably disabled because it's non-super-admin blog)." Looimaster 12036 "Importing from wordpress exported file renders ""Remote file is incorrect size"" because file cache" Import 2.8.6 normal normal WordPress.org defect (bug) new dev-feedback 2010-01-26T14:43:08Z 2010-10-18T16:49:10Z "Hi, I haven't confirmed this on other platforms, but my OS X machine seem to have an issue when downloading media content from a third party during an import of an wordpress.xml. And by quickly searching the net it seems other people have the same issue. I've re-run the same import several times and it seem because the file was not flushed it may not have been updated with the file correct size. So even thought all bytes was written, the filesize($upload['file']) is not the same. When thinking about the issue I found the check ridiculously and removed it. Importing then works and all media images are downloaded properly. Previously maybe 50% received the error. I've attached my proposed diff." stelund 9678 Importing of plain RSS looses descriptions with xml:lang Import 2.7.1 normal normal WordPress.org defect (bug) new reporter-feedback 2009-04-29T08:24:49Z 2012-09-09T22:19:29Z "When importing from a generic RSS feed the import function looses if there is an xml:lang attribute. The imported posts will be empty. xml:lang is a valid attribute for description to denote the language used in the article." dr_touch 21007 Importing omits backslashes Import normal normal WordPress.org defect (bug) new has-patch 2012-06-18T08:11:16Z 2012-06-18T12:10:13Z If you try to import a previously-exported post containing backslashes, those backslashes will be omitted during the import process. SeMeKh 17191 Importing the same content duplicates your custom menus duck_ Import 3.1 normal minor WordPress.org defect (bug) reviewing 2011-04-20T15:03:40Z 2012-09-12T03:47:39Z "When I import from one site to another, the importer will notify you if you have duplicate posts but will not import them, as expected, but it does duplicate your custom menu's. I'm not sure if this is the desired result." zanematthew 19764 Invalid JSON in custom fields meta value after export Import 3.3.1 normal normal WordPress.org defect (bug) new 2012-01-06T17:13:07Z 2012-09-10T10:12:22Z "Hey there, I exported a working copy of my online WordPress site to a local copy and noticed that the code gets changed; The backslash is removed which causes the json format to be invalide. Original code in the custom fields meta {{{ {""videos"":{""0"":""""}} }}} Becomes in the local site after import {{{ {""videos"":{""0"":""""}} }}} " abdessamad idrissi 5842 LJ import gets time zone wrong Import normal normal WordPress.org defect (bug) new close 2008-02-13T18:17:09Z 2011-09-16T03:55:09Z LJ's export format has all dates in GMT, but the wordpress LJ importer treats them as local time. novalis_dt 15760 "LiveJournal Importer mishandles some and expressions" westi Import normal normal WordPress.org defect (bug) assigned 2010-12-10T04:45:17Z 2011-02-19T18:52:42Z "There is a note on plugins.trac ticket 1231 that says this should be handled in core.trac instead, so I'm cross-posting it here. The patch and ticket were originally added by a-bishop: http://plugins.trac.wordpress.org/ticket/1231 Reproduction steps: 1. Create a LiveJournal? entry that has in it. Note that this is XML-ish 2. Try to use the livejournal-importer on this post. Bug The gets ignored because the regular expression is too strict. I've attached a patch that makes LiveJournal? Importer recognize the XML-ish version. Patch:[[BR]] http://plugins.trac.wordpress.org/attachment/ticket/1231/livejournal-importer.patch" designsimply 12885 LiveJournal importer uses GMT date/time as local date/time Import normal normal WordPress.org defect (bug) new has-patch 2010-04-07T02:07:25Z 2011-01-26T10:29:09Z "The LiveJournal importer takes a comment's date/timestamp, which is in GMT, and inserts it into the database as the comment's local date/timestamp. In my timezone (U.S. Central, DST), a comment posted at 12:00pm local time (5:00pm GMT) will be imported to the database as having been posted at 5:00pm local time (10:00pm GMT). I've attached a patch that I've successfully tested on Wordpress 2.9.2, and it appears to be easily ported to trunk. One caveat: it appears that there are two timezone settings in the Wordpress database (timezone_string and gmt_offset), but as my database has no value for gmt_offset, I don't know if I need to account for that, nor can I test that." kurtmckee 16183 MT Importer doesn't honor default article comment settings Import 3.0.4 normal normal WordPress.org defect (bug) new 2011-01-10T23:00:38Z 2011-01-11T23:22:45Z "I have a blog on a network that has '''Allow people to post comments on new articles''' and '''Allow link notifications from other blogs (pingbacks and trackbacks.)''' unchecked in '''wp-admin/options-discussion.php'''. The intent is to disable comments and trackbacks, and I can confirm this is happening for new posts when I do '''Post''' > '''Add New'''. However, the MT Importer doesn't honor this configuration. All imported MT posts have comments enabled." novasource 16147 MT Importer truncates double vertical spaces, munging paragraphs together Import 3.2.1 normal major WordPress.org defect (bug) reopened 2011-01-07T22:25:47Z 2011-08-24T06:20:05Z "Movable Type 3.x-era exports don't use '''

''' tags. Like TinyMCE (and WordPress), a '''

''' in final rendered code is represented by two '''\n'''s in a row. The importer strips out double '''\n'''s and replaces with a single '''\n'''. This causes paragraphs to lose their distinction upon import. It does this because the '''$line''' variable was created by '''$line = $this->fgets($handle)''' (line 339). Then '''$line = trim($line)''' (line 340) strips out several characters, including '''\n'''. Lines 455 and 456 add back the '''\n''' ''except'' on blank lines: {{{ if( !empty($line) ) $line .= ""\n""; }}} So if a '''$line''' was nothing but a '''\n''', it's stripped by the '''trim''' function and becomes a 0 character line. Then the '''if( !empty($line) )''' declines to add back a '''\n'''. Somehow this needs to be altered so that successive '''\n'''s aren't stripped. Otherwise paragraphs get vertically munged together." novasource 18602 Media Library imported, but all items Unattached Import 3.2.1 normal normal WordPress.org defect (bug) new reporter-feedback 2011-09-06T10:10:18Z 2012-09-10T10:15:41Z "Export XML file from one site, import into another site. By checking ""Download and import file attachments"", files from wp-content/uploads are downloaded correctly to the new site, and added to Media Library. However all items in the Media Library are now ""Unattached"", and for example posts using [gallery] are broken on the new site. " awallin 22171 Merge Blogger Importer description strings Import normal normal WordPress.org defect (bug) new has-patch 2012-10-12T00:47:35Z 2012-10-15T06:37:57Z "In Blogger Importer 0.4, the description strings were: * ""Import posts, comments, tags, and attachments from a Blogger blog."" [[BR]] http://plugins.trac.wordpress.org/browser/blogger-importer/tags/0.4/blogger-importer.php#L5 * ""Import posts, comments, and users from a Blogger blog."" [[BR]] http://plugins.trac.wordpress.org/browser/blogger-importer/tags/0.4/blogger-importer.php#L914 In Blogger Importer 0.5: * ""Import posts, comments and tags from a Blogger blog and migrate authors to Wordpress users."" [[BR]] http://plugins.trac.wordpress.org/browser/blogger-importer/tags/0.5/blogger-importer.php#L5 * ""Import categories, posts and comments then maps users from a Blogger blog."" [[BR]] http://plugins.trac.wordpress.org/browser/blogger-importer/tags/0.5/blogger-importer.php#L1026 The core still says: * ""Install the Blogger importer to import posts, comments, and users from a Blogger blog."" [[BR]] http://core.trac.wordpress.org/browser/tags/3.4.2/wp-admin/import.php#L35 I guess we should merge the strings or at least fix the capital P." SergeyBiryukov 9820 Multiple newlines stripped from within MT import files Import 2.7.1 normal normal WordPress.org defect (bug) new 2009-05-14T11:03:43Z 2012-05-24T22:33:01Z "When I imported entries from my old MT blog into a new Wordpress install, I expected my multiple newlines to be preserved. This is because MT uses them to form paragraphs; the Markdown or Text Control plugins can do the same in Wordpress, but either way, if you strip them out, you get a huge bundle of text which is difficult to read. The problem appears to be in the wp-admin/import/mt.php file, which ignores blank lines regardless of context. If a newline were added in the event of a blank line when the context was body, comment, extended or excerpt, the newlines would be preserved. The attached patch fixes this." IndigoJo 10947 Problem on import codes on mt.php script Edgar Gabaldi Import 2.8.4 normal normal WordPress.org defect (bug) new 2009-10-12T16:59:13Z 2012-05-24T22:33:11Z "I'm having trouble making the import of a file exported by CMS Movable Type. All posts, categories, comments, users are imported correctly. The problem is that there are blocks of code in posts with the tag that are not being imported." edgabaldi 10259 Problem with dotclear import Import 2.8 normal normal WordPress.org defect (bug) new reporter-feedback 2009-06-24T09:34:07Z 2011-09-16T03:55:46Z "To the point translation: Dotclear categories are imported but not assigned to the posts. ---- Bonjour, > >> > >> Ayant souhaité le passage de mon blog dotclear en wordpress, j’ai >> donc > >> utilisé votre module d’import dans l’interface d’administration. > >> J’ai rencontré le problème suivant : > >> - les catégories des mes billets étaient bien importées > >> mais n’étaient pas liées à ces derniers. > >> > >> J’ai donc contacté votre staff par l’intermédiaire de votre site mais > >> sans succès. > >> > >> J’ai du coup développé un petit fichier php pour résoudre mon > >> problème. >> Les versions utilisées pour mon développement : > >> - WORDPRESS 2.8 > >> - DOTCLEAR 1.2.7.1 " latour.alain@… 6269 RSS Import Doesn't Properly Strip CDATA Tags Import 2.3.3 low minor WordPress.org defect (bug) new dev-feedback 2008-03-18T00:58:13Z 2012-09-10T16:37:33Z "When importing an RSS feed that uses the tag as opposed to , I noticed that WP's RSS import doesn't strip the CDATA tags as it does for the . =========Code Lines (83-87)=============== {{{ if (!$post_content) { // This is for feeds that put content in description preg_match('|(.*?)|is', $post, $post_content); $post_content = $wpdb->escape($this->unhtmlentities(trim($post_content[1]))); } }}} ===================================== I tweaked the code to solve the problem (see below) ==========Tweaked Code=============== {{{ if (!$post_content) { // This is for feeds that put content in description preg_match('|(.*?)|is', $post, $post_content); $post_content = str_replace(array (''), '',$wpdb->escape($this->unhtmlentities(trim($post_content[1])))); } }}} ====================================== I'd be happy to submit a patch, except I'm not quite that savvy yet. It would be great it someone could incorporate it. Thanks." sweetdeal 13313 "WP import: ""Upload file and import"" should be deactivated until a filename is entered" Import 3.0 low minor WordPress.org defect (bug) new has-patch 2010-05-09T22:10:55Z 2012-10-31T16:15:09Z "WP import: ""Upload file and import"" should be deactivated until a filename is entered ENV: WP trunk 3.0-beta2-14526 [[br]] Mac OS / Firefox 3.6.3 == Additional Details == Same issue with wp-admin/media-new.php (browser upload) " lloydbudd 22082 WordPress Import Tool looses the complete category hierachical structure Import 3.4.2 normal normal WordPress.org defect (bug) new 2012-10-03T01:53:05Z 2012-10-05T13:49:54Z "I have exported from my local laptop wordpress installation the posts I had. They have the following structure with categories: {{{ language --> main category, parent - source language --> for example AF -- target language --> for example AFAR for Africans to Arabics --- lessons ----- lesson 1 --> up to 100 lessons entries -- next target language }}} and so on this complete structure is lost after import - they are all changed to parent categories no single child category. I will attach the export file." christian_gnoth 21597 WordPress Importer $base_url index failed Import 3.4.1 normal minor WordPress.org defect (bug) new has-patch 2012-08-15T18:30:11Z 2012-09-10T10:03:12Z "When XRS file without the site url tag is imported, it throws a notice. This patch allow people to upload hand-made and not-attached-to-any-site XRS file. I came across creating a XRS file to import names of cities from Portugal to a specific custom taxonomy to some sites. This can reflect the necessity of this patch." lightningspirit 24373 WordPress Importer - Strict Standards compatibility Import trunk normal normal WordPress.org defect (bug) new 2013-05-20T19:02:00Z 2013-05-24T15:51:40Z "I am seeing the following errors on wp-admin/import.php, running 3.6-beta3-24300 and PHP 5.4.7, in my single and multisite test installs: '''Strict Standards:''' Redefining already defined constructor for class WXR_Parser_Regex in xxxxx\wp-content\plugins\wordpress-importer\parsers.php on line 408 '''Strict Standards:''' Declaration of WP_Import::bump_request_timeout() should be compatible with WP_Importer::bump_request_timeout($val) in xxxxx\wp-content\plugins\wordpress-importer\wordpress-importer.php on line 38 " kpdesign 16404 WordPress Importer fails to import images Import 3.0.4 normal normal WordPress.org defect (bug) new reporter-feedback 2011-01-29T00:42:28Z 2012-09-10T10:13:44Z "WordPress Importer fails to import images and update image src urls when download and import file attachments is checked. WordPress MS with images in a post via Media using WP image mapping, e.g. image url: http://site.domainname.com/files/2011/01/myimage.jpg Fails to download, import and update image src url. All image src urls remain intact from the old domain name. If you change the image source to specific directory rather than the WP uploads directory: e.g. image url: http://site.domainname.com/images/myimage.jpg Images are downloaded and imported to media but it fails to update image src url in posts. All image src urls in posts remain intact from the old domain name. I tested this on clean install of WP 3.0.4 MultiSite with TwentyTen theme and no other plugins activated." wlpdrpat 23276 WordPress Importer: Update existing navs instead of new Import normal normal WordPress.org defect (bug) new has-patch 2013-01-23T17:00:06Z 2013-01-25T02:41:23Z "A possible solution (reuses logic present in the code): {{{ $menu_item_db_id = (int) $item['post_id']; $original_object = get_post( $menu_item_db_id ); if ( is_null( $original_object ) ) { $post_parent = (int) $item['post_parent']; if ( $post_parent ) { // if we already know the parent, map it to the new local ID if ( isset( $this->processed_posts[$post_parent] ) ) { $post_parent = $this->processed_posts[$post_parent]; // otherwise record the parent for later } else { $this->post_orphans[intval($post['post_id'])] = $post_parent; $post_parent = 0; } } // map the post author $author = sanitize_user( $item['post_author'], true ); if ( isset( $this->author_mapping[$author] ) ) $author = $this->author_mapping[$author]; else $author = (int) get_current_user_id(); $postdata = array( 'import_id' => $item['post_id'], 'post_author' => $author, 'post_date' => $item['post_date'], 'post_date_gmt' => $item['post_date_gmt'], 'post_content' => $item['post_content'], 'post_excerpt' => $item['post_excerpt'], 'post_title' => $item['post_title'], 'post_status' => $item['status'], 'post_name' => $item['post_name'], 'comment_status' => $item['comment_status'], 'ping_status' => $item['ping_status'], 'guid' => $item['guid'], 'post_parent' => $post_parent, 'menu_order' => $item['menu_order'], 'post_type' => $item['post_type'], 'post_password' => $item['post_password'] ); $menu_item_db_id = wp_insert_post( $postdata, true ); if ( is_wp_error( $menu_item_db_id ) ) { $post_type_object = get_post_type_object( $item['post_type'] ); printf( __( 'Failed to import %s “%s”', 'wordpress-importer' ), $post_type_object->labels->singular_name, esc_html($item['post_title']) ); if ( defined('IMPORT_DEBUG') && IMPORT_DEBUG ) echo ': ' . $post_id->get_error_message(); echo '
'; } } $id = wp_update_nav_menu_item( $menu_id, $menu_item_db_id, $args ); }}}" WraithKenny 23275 WordPress Importer: line-ending mismatch corrupts serialized meta Import normal normal WordPress.org defect (bug) new has-patch 2013-01-23T16:56:04Z 2013-01-25T02:36:14Z "A possible solution: {{{ if ( $key ) { // export gets meta straight from the DB so could have a serialized string if ( ! $value ) $value = maybe_unserialize( $meta['value'] ); // Occationally, line-endings break unserialize() if ( empty( $value ) ) // Try normalizing... $value = maybe_unserialize( str_replace( array(""\r\n"", ""\r"", ""\n""), ""\r\n"", $meta['value'] ) ); if ( empty( $value ) ) // Adjust string length if needed $value = maybe_unserialize( preg_replace( // e flag deprecated in PHP 5.5.0 I think '!s:(\d+):""(.*?)"";!se', ""'s:'.strlen('$2').':\""$2\"";'"", $meta['value'] ) ); add_post_meta( $post_id, $key, $value ); do_action( 'import_post_meta', $post_id, $key, $value ); // if the post has a featured image, take note of this in case of remap if ( '_thumbnail_id' == $key ) $this->featured_images[$post_id] = (int) $value; } }}}" WraithKenny 12286 bug and fix when importing from Movable Type Import normal normal WordPress.org defect (bug) new 2010-02-19T13:26:59Z 2010-10-30T18:44:11Z "I'm running WP Mu 2.9.1.1 and had a problem importing a Movable Type blog to WP and found a fix (sort of). Symptom: When importing a blog from Movable Type to a blog in WP, you are asked to assign (or map) WP authors to MT authors. But, it turns out that the first author on the list is assigned to all posts. The other authors selected are neglected. Therefore, all of the posts end up belonging to one author. Fix: I found the problem in wp-admin/import/mt.php. Specifically, ""$mtnames"" is not properly populated with authors from MT. So, I changed the code in function get_authors_from_post() as follows: function get_authors_from_post() { $formnames = array (); $selectnames = array (); $this->mtnames = $this->get_mt_authors(); I just added the last line shown above and then finally the import properly assings authors as intended. (There might be a better place to put the last line, however.) " leyburn888 8877 dotclear import don't set the post category westi* Import low normal WordPress.org defect (bug) accepted 2009-01-17T22:05:20Z 2012-05-24T22:32:57Z "when importing from dotclear, all the posts are set only to the default category. i think the problem is due to the fact that wp_set_post_categories do nothing if we pass it only one category (don't know why...) ( in /wp-admin/import/dotclear.php, line 479 ) {{{ // Make Post-to-Category associations $cats = array(); $category1 = get_category_by_slug($post_cat_name); $category1 = $category1->term_id; }}} should be {{{ // Make Post-to-Category associations $cats = array(get_option('default_category')); $category1 = get_category_by_slug($post_cat_name); $category1 = $category1->term_id; }}} " olivM 15586 movabletype-importer, trivial: fix no index upload_type warning Import 3.1 low minor WordPress.org defect (bug) new has-patch 2010-11-26T00:43:46Z 2010-12-11T14:06:54Z "movabletype-importer, trivial: fix no index upload_type warning ENV: http://plugins.svn.wordpress.org/movabletype-importer/trunk r315664" lloydbudd 10260 problem img links after import dotclear Import 2.8 normal normal WordPress.org defect (bug) new reporter-feedback 2009-06-24T09:48:17Z 2012-09-10T09:43:28Z "J'ai développé un fichier PHP pour changer le chemin des images car dans un billet, le chemin était celui du blog dotclear après l'import dans wordpress --- Translation: I wrote a php file that changes the image links in posts after a dotclear import. The posts were imported with references to their dotclear location." latour.alain@… 15217 wp importer trunk regression: no longer accepts gz files duck_ Import 3.1 normal normal WordPress.org defect (bug) reopened 2010-10-26T04:16:21Z 2010-10-26T18:41:24Z "wordpress-importer trunk r304267 no longer accepts gzipped WXR files. This is a regression from the current wordpress-importer importer, v0.2 . == Actual Results == ""Sorry, there has been an error. There was an error when reading this WXR file"" == Environment == WordPress Trunk r14360 (3.1-alpha) [[br]] wordpress-importer trunk [http://plugins.trac.wordpress.org/browser/wordpress-importer/trunk r304267] == Additional Details == Relates to #15197 ""WXR export/import umbrella ticket"" I notice that same error message ""There was an error when reading this WXR file"" is in two parts of the source. It might be better to make each error message more unique and add additional details." lloydbudd 4010 Add Image Importing to the Blogger Importer Workshopshed Import normal normal WordPress.org enhancement reopened 2007-03-21T20:21:28Z 2013-04-09T15:59:14Z The new blogger importer currently does a great job of bringing the blog over to WP, but it leaves the images associated with the blog on blogger.com and/or blogspot.com. This violates blogger's TOS and risks having the user's image links blocked by blogger. This change will move those images (using the WP image upload facility, of course) to the user's blog and fix the links as the import is done. clwill 4555 Better Typepad / MT Import - Atompub importer lloydbudd Import 2.3 normal minor WordPress.org enhancement new 2007-06-28T03:16:12Z 2011-09-15T17:17:07Z "Typepad in particular does some really funky things with permalinks. They often have no relation to anything in the title, and none of their ""slug"" information is contained in their standard export, so there is literally no way to redirect those links. It is possible to create a custom Typepad template that includes the needed information, and modify the WP importer to parse the extra info into slugs. Right now this is a hack, we should make this more intuitive." matt 21913 Detecting MIME Types in WXR Files Import 3.4.2 normal normal WordPress.org enhancement new dev-feedback 2012-09-17T21:09:07Z 2012-10-10T21:46:11Z "In the process of creating a service to convert TypePad data to WXR formatted files, we've encountered some unique problems with TypePad data. Namely, many TypePad files are saved without file extensions, which prevents the existing importer from importing those files into the wp-content/uploads folder. In order to import and rename these otherwise ignored files, we've created a patch for the WordPress importer that does the following: 1. If there is an attachment in the WXR and the importer is not able to determine the file type from the file name (ie missing extension), the patched version will make a light (body-less) request to the web server where the file is hosted for information we can use about the file. The things we're interested in are file type, size, and filename. 2. If the importer is processing an attachment under the above situation, and it is able to determine the file type, then it will rewrite the local version of the file to have the appropriate file extension. This is a simple bit of code, but it makes a huge difference as TypePad saves without file extensions quite regularly. We've attached our patch and a sample WXR file from ragsgupta.com, the Brightcove co-founder's blog." ReadyMadeWeb 4611 Dotclear importer for WP 2.3: flatimport Import 2.3 low minor WordPress.org enhancement new 2007-07-11T13:37:57Z 2011-08-04T10:30:33Z "This importer import '''posts''' (''users, comments, tags, categories''), '''links''' (''categories'') into WordPress 2.3 from a Dotclear '''export flat file'''. A restart procedure allows the import of big blogs. It's the importer for a Dotclear 2 blog. It imports also from a Dotclear 1.2.x blog (note that the embedded Dotclear importer imports from Dotclear 1 only). Download the [http://cvie.free.fr/public/flatimport.zip] ; a tutorial is embedded with the flatimport.php script." albaran 8455 Enhance usability in Wordpress Import - preselecting matching authors tott Import normal normal WordPress.org enhancement new 2008-12-02T09:27:03Z 2012-09-10T10:21:11Z To increase usability in wordpress imports, especially for imports with many users or imports that are rerun a preselection of authors would increase usability. tott 8984 Import ... default author Import 2.7 normal normal WordPress.org enhancement new 2009-01-28T23:40:11Z 2012-09-10T10:00:15Z "Suggest import.html contain an optional default author entry box (numeric or alpha lookup). The entry here would become the default author if a valid post_author is not found in the imported posts. This default author would apply to all posts that are part of the import. I am told WordPress import does allow for a author during import. I know RSS does not. To be determined is if this default author should override valid author data - I would think it would. An advanced feature would be to allow both a number author_ID or the friendly string-based author name to be entered and import.php would try to determine if the friendly name is unique. If not present a list of friendly names along with their blogs and allow the user to select the specific author. " oregondean 7644 Import Movable Type data using AtomPub. westi* Import normal normal WordPress.org enhancement accepted close 2008-08-29T20:33:52Z 2011-09-15T17:17:13Z This is a split ticket from #7543. This includes the latest Movable Type portion of the code. cavemonkey50 7543 Import TypePad data using AtomPub. westi* Import normal normal WordPress.org enhancement accepted needs-review 2008-08-19T02:44:26Z 2011-09-15T17:17:11Z "First off, I want to mention that TypePad updated their AtomPub server a few days ago, and their server does not seem to be sending comments. With a little luck, my current code should work fine once that server starts functioning again, but for the time being I would highly recommend not committing this into core. Instead, I'm hoping people can look over the code and offer suggestions for improvement, test results, etc. While the Summer of Code is officially over today, I will be working on this until the job is done. Alright, now to what this is. As some of you may know, I've been working on an Atom Publishing Protocol ([http://www.rfc-editor.org/rfc/rfc5023.txt RFC 5023]) based importer this summer for the Google Summer of Code. The diff attached is the latest version of my work. The advantages of using the Atom Publishing Protocol are as follows: * Nothing has to be done in the old blogging software to prepare for import (no export files, etc). Users just enter their blog URL, username, and password and the importer grabs all of the data using AtomPub. * More data is imported compared to the old importers, especially with TypePad. Post slugs, comments, trackbacks, tags, categories, excerpts, etc are all imported. Everything used for posts in MT/TypePad is imported using AtomPub. * The Atom Publishing Protocol is an established standard. With the exceptions of tag additions (which don't necessarily need updates), the importer should not have to be changed and should continue working well into the future. I should mention there is one drawback to using the Atom Publishing Protocol. For the time being, it appears pages can not be retrieved using AtomPub. They were retrievable a few weeks ago, and I'm currently talking with Six Apart to see what happened. I would greatly appreciate any and all feedback. Let me know your suggestions, and I'll be happy to incorporate them." cavemonkey50 22988 Import blogger site from its exported XML file Import normal normal WordPress.org enhancement new 2012-12-18T05:45:07Z 2013-01-22T18:52:34Z I saw that wordpress.com has an option to do that. mark-k 22041 Importer dies silently when multisite upload limit is reached Import normal normal WordPress.org enhancement new 2012-09-28T17:58:57Z 2012-09-28T18:03:31Z "The scenario: You're importing a WXR file into a site on a multisite network and the WXR includes a number of large attachments. For whatever reason, the upload capacity for each site is set at 100MB. If the upload capacity is reached during the import process, the import will look like it's hanging forever. Instead, it would be nice to show an alert that the upload capacity was reached or similar." danielbachhuber 7061 RSS import should store as excerpt if is present Import 2.5.1 normal normal WordPress.org enhancement new 2008-05-29T11:47:32Z 2012-09-10T09:45:24Z Currently the tag is only used as content if no tag is found. koke 16294 Remote WXR Import duck_ Import normal normal WordPress.org enhancement reviewing 2011-01-19T01:02:00Z 2012-09-10T10:19:03Z The attached patch allows a user to submit a URL pointing to a WXR import file, rather then uploading it. The purpose of this is to allow people to import a WXR file that is larger then their server's max_upload_size/max_post_size php.ini settings. belaraka 5678 Respectfully strip newlines in some importers hansengel* Import 2.5 normal normal WordPress.org enhancement accepted 2008-01-16T11:20:02Z 2012-09-10T09:44:42Z "Filing this as an enhancement because it could do with some discussion and insight from wiser and more experienced heads before being labelled ""defect"". :-) I noticed while helping some users import their blogs that importers of HTML content (such as the RSS importer) don't tidy up superfluous newlines in the import format, which results in unnecessary {{{
}}} elements after {{{wpautop()}}} filtering for display. They turn up in the editor too, which reinforces the problem. I've adapted one of the filter functions to strip superfluous newlines, and changed my RSS importer to use it. The results have been warmly welcomed by users, who no longer have to clean up their imported blog content. ;-) {{{strip_newlines()}}} should probably go into {{{wp-includes/formatting.php}}}, if there isn't already a function that already serves this purpose. I couldn't find one, so I adapted this. Given that similar HTML block/inline-savvy string-replacement code exists in other formatting functions, perhaps there's an opportunity for some refactoring here? I feel kind of silly proposing a function that is almost entirely duplicated from other code in the core. I've used it immediately before the ""Clean up content"" section in {{{wp-admin/import/rss.php}}}'s {{{get_posts()}}}, and in an Advogato importer that I've written (which also uses HTML as the content format). {{{ function strip_newlines($text) { // Respectfully strip unnecessary newlines $textarr = preg_split(""/(<[^>]+>)/Us"", $text, -1, PREG_SPLIT_DELIM_CAPTURE); $stop = count($textarr); $skip = false; $output = ''; // loop stuff for ($ci = 0; $ci < $stop; $ci++) { $curl = $textarr[$ci]; if (! $skip && isset($curl{0}) && '<' != $curl{0}) { // If it's not a tag $curl = preg_replace('/[\n\r]+/', ' ', $curl); } elseif (strpos($curl, ' tags and removes all but the first one * Provides the SWFUploader for the uploading files (impacts Blogware, MovableType/TypePad, RSS and WordPress importers as well) * Adds some user-friendly instructions on how to export from LJ properly * Removes the use of /e in preg_replace() for {{{livejournal.php}}} as detailed in #8689 * Adds the title of the post to the output in the RSS importer as well (since all the others do that) This patch was developed based on r10331" beaulebens 15219 WordPress importer UX/UI review Import normal normal WordPress.org enhancement new 2010-10-26T09:22:52Z 2012-07-23T19:08:41Z "The newly improved WordPress WXR importer needs some UX love to improve it further! A few things that I know need improving: '''Results and feedback''' Currently you will either see ""All done. Have fun!"" or a list of errors and ""All done. Have fun!"". Clearly this isn't really enough information. The old importer listed every single item being imported and associated errors, which I thought was too much information for a large import. My thoughts was to do something like show the red error message block if any errors occur and have a JS enabled link in this to show a more detailed list of items that were not imported, followed by a table of results displaying the number of succeses, failures and skips (for content already present) for each of the separate sets of data imported. '''Error strings''' These need to be useful, there's not much point in saying something went wrong but not giving enough information to diagnose the real issue. They also need to be displayed well (see above), an example of a weird one is trying to import a WXR 1.0 file with an author with a display name non-[a-zA-Z]. '''Other'''[[BR]] The fix for #13627 needs to be done properly. The role a new user will be imported as is now being displayed but I don't think it's prominent enough yet. You'll see that it's mentioned on step two when choosing how authors will be imported, but if you're someone like me who often only skims instructions it is pretty easy to miss. Maybe some bold/highlighting and another reminder on the final screen? Anything else people notice as not clear enough when giving the importer a test." duck_ 19225 WordPress-Importer : Perform less database queries when backfilling attachment urls duck_ Import normal normal WordPress.org enhancement assigned has-patch 2011-11-10T12:36:42Z 2011-11-11T08:20:11Z "The current backfill_attachment_urls() approach causes a REPLACE query for each attachment url. This can cause the invalidation of a lot of data and also cause MySQL replication lag in some cases. The attached patch will make sure to bundle these requests and perform only maximum of one db update per post. " tott 3398 import data from Geeklog Import normal critical WordPress.org enhancement reopened 2006-11-28T05:19:12Z 2011-10-03T08:16:00Z "I recently converted my blog from geeklog to wordpress, and wound up converting the existing TextPattern importer to be able to pull data directly from a Geeklog database and import it to Wordpress. The importer is incomplete, but usable, and currently imports categories, users, posts, and comments. It pretty much does what I needed it to do, and I'm sure someone else can make use of it, and possibly clean it up better." justdave 12578 import from movable type doesn't import tags or basename Import 3.0 normal normal WordPress.org enhancement assigned has-patch 2010-03-11T00:58:46Z 2010-10-30T18:44:26Z The current movable type import script doesn't import tags from movable type and it doesn't import the basename (movable type's version of the post_name, which is necessary for a seemless transition). Adding support for importing these two important bits is not terribly difficult and I'm working on improving the import script to aid in my own upcoming migration. I'll attach a patch against the trunk. stevecrozz 7695 Blogger Importer Should Allow User Creation on the fly Import normal normal WordPress.org feature request new 2008-09-05T19:30:47Z 2012-07-13T07:01:14Z See MT importer as an example. Otherwise, users need to be created prior to the import to map to other users other than admin. technosailor 16460 Category/tag converter should support all public taxonomies Import 3.0 normal normal WordPress.org feature request new has-patch 2011-02-05T04:56:39Z 2013-01-17T17:09:40Z The category to tag converter should let you convert terms to custom taxonomies, if any are defined. I'm attaching a rewrite of the plugin based on 1.5.2, which included support for post formats. sillybean 16148 MT Importer should match usernames Import normal normal WordPress.org feature request reopened 2011-01-07T22:27:29Z 2012-09-10T10:21:14Z If I have a blog that already has a user with ID '''XYZ''', and my Movable Type import has a blog post with author with ID '''XYZ''', then the '''Assign Authors''' page in the import wizard should automatically match them by default. novasource 13928 WP.org plugin update notifications should consider plugin slug Plugins normal normal WordPress.org defect (bug) new 2010-06-16T21:25:30Z 2013-01-29T22:58:24Z "I have a plugin named ""Events Calendar."" The actual plugin file and directory is `filosofo-event-calendar/filosofo-event-calendar.php`. However, I get update notifications for it for [http://wordpress.org/extend/plugins/events-calendar/ this plugin], even though its file is `events-calendar/events-calendar.php` Everything else--author name, description, and URL--differs as well. WP.org update notifications should be smart enough to distinguish between plugins with different file structures, at least." filosofo 23318 Plugins Admin Showing Details for Wrong Plugin Plugins normal normal WordPress.org enhancement new dev-feedback 2013-01-29T22:41:54Z 2013-04-05T02:00:19Z "I just set up a new site with some plugins, none of them activated yet. The plugins screen says: ""There is a new version of Google XML Sitemaps available. View version 4.1 details or update now."" I know for a fact there is no such version of this plugin. When I click details link, it tells me to install some other plugin called page-list?!" miqrogroove 21763 Add Support To Pass An Array Of Plugins To The Plugin Info API Plugins 3.4.1 normal normal WordPress.org feature request new 2012-09-01T03:14:42Z 2012-09-01T11:13:54Z "https://api.wordpress.org/plugins/info/1.0/ Currently only allows one plugin to be passed in a request to get the relevant information back. However, the update check API allows an array of plugins to be passed. I'm requesting the same functionality be added to the info API and not just for developer use, but for consistancy." crypticmauler 14209 "Authentication data check button for ""Post via e-mail""" Plugins normal normal WordPress.org feature request new 2010-07-06T13:05:00Z 2010-10-28T06:36:59Z "Allowing the user to check the ""Post via e-mail"" POP3 data in Settings->Writing ""on the fly"" seems like a nice enhancement. A simple AJAX button would be a significant improvement compared to the current solution. " wojtek.szkutnik 21284 Better New Plugin Filtering Plugins normal normal WordPress.org feature request new 2012-07-15T17:24:24Z 2012-07-18T15:04:03Z "Currently trying to sort through available plugins by searching is quite laborious since there is no way to filter out things you don't want - such as plugins that haven't been tested with your version, haven't been updated in 100+ days, have a really low rating, etc. I'm constantly surprised at how many plugins i have to go through before i can even find one that is compatible with at least WP two versions ago much less the current one. You should be able to filter on: Tested with current version, Rating of X+, Download at least XX, and so on to make it easier to find something you want. And then column sorting after then by date added, date updated, rating, etc." cbesett 15514 Category/Tag Converter should include Post Format conversions Plugins normal normal WordPress.org feature request new 2010-11-20T03:13:53Z 2013-01-17T17:10:01Z "The category/tag converter should include the ability to convert categories or tags to post formats. The converter in general needs a pretty serious UI or code cleanup, so if anyone wants to own this, that would be awesome, and I will assist." nacin 22981 Tweets import plugin tracking ticket PeteMall* Plugins high normal WordPress.org task (blessed) accepted 2012-12-17T18:43:42Z 2013-03-29T14:04:16Z "This ticket is to track the development of a plugin that can import tweets from a downloaded twitter.com archive. Presumably, such a plugin would be added to the importers list on wp-admin/import.php. Trac is best when it is used to discuss implementation. If you want to discuss the general idea, please do so on [http://make.wordpress.org/core/2012/12/16/antsy-for-3-6-to-start-and-need-a/ make/core]. Some initial thoughts on implementation: * It should use the JSON-formatted data that comes with a downloaded tweet archive. The importer should take the entire zip, extract it, and loop through the monthly files. Anything more is an unnecessary burden on the user. * The plugin should import the tweet as actual content. A filter is good idea, if someone wishes to toggle this to instead insert links to tweets (and thus rely on oEmbed). It should also store the JSON-serialized array of data (directly from 1.1 of Twitter's API) in postmeta. * It should import posts as a post format. Status makes the most sense; 'link' could also work for links, then there's also 'aside'. The post format to use should be filterable on a tweet-by-tweet basis. The post type to use should be filterable, as a 'tweet' type may be desired. * It should handle importing an archive over an existing archive, by looking for the existing tweet (probably IDs as a meta key). I don't think deleted tweets should be removed in this process, though. * Remember that tweet IDs are going to be bigger than 32-bit integers, so they must be treated as strings, and we should not try to set a post ID as we might with other importers. This importer should be tested on a 32-bit environment. Beyond that, there are other ""nice to haves"" that would likely be left to plugins of this plugin, given they are beyond the standard role of an importer. Beau Lebens, for example, has done some/all of this already: * Tagging based on hashtags, and a separate mentions and/or in-reply-to taxonomy. * Filtering over raw (no-HTML) content to add things like links to hashtags, links in tweets, etc., on display, rather than doing all of this on save. (Should a hashtag link go to the internal tag, or to twitter.com? Maybe the internal tag's description links to twitter.com?) * A cron to import new tweets using the same importing methods. One thing I will suggest: decisions, not options. Note I said ""filter"" a bunch of times, but never the word ""option."" Not that there won't be a need for any user decision here, but we should make a plugin that works well for the common use cases, and leave the rest to other enterprising developers. Side note: I am working on acquiring a namespace for the Twitter importer in the wordpress.org plugin repository." nacin 10149 A floating image added in a comment results in a weird layout in the default theme iandstewart Themes 2.8 low minor WordPress.org defect (bug) assigned 2009-06-13T22:33:19Z 2010-10-30T18:36:03Z I'd have suggested a

or something in the default theme, but the bug is actually located within wp_list_comments(). Denis-de-Bernardy 11178 Fix for poor sidebar CSS in Kubrick theme iandstewart Themes 2.9 normal normal WordPress.org defect (bug) assigned has-patch 2009-11-18T22:04:40Z 2010-06-14T22:01:25Z "Rather than using a float to push the sidebar alongside the content area, Kubrick floats the content area and then uses a left-margin of 545 pixels to shove the sidebar over. This causes float and clear CSS rules to produce very odd results in the sidebar. The attached patch changes the #sidebar left-margin from 545px to 50px and adds ""float: left"". A site running the patched version of Kubrick has been tested in IE 6-8 and the latest versions of Firefox, Opera, Chrome, and Safari. All the browsers rendered the sidebar in the same position as before the patch with the exception of also fixing the float/clear problem." chrisbliss18 14179 Theme asking to update (theme with same name on WordPress.org) Themes normal normal WordPress.org defect (bug) new 2010-07-03T08:34:02Z 2013-01-29T22:58:53Z "I have a theme with a certain name, but there is a theme with the same name in the WordPress themes directory. So now my theme keeps showing an update message. Proposed solutions: 1. Add unique hash to each uploaded theme in the themes directory. This way even if someone has a home-grown theme which happens to have the same name, but are not going to upload it to the themes directory, there won't be a conflict. (You could change the name of the theme, but who is to say someone won't upload a theme that also has that name.) 2. Add more fields to the updater check such as author, and date/ time created. This could mean though that theme authors would always have to add this during theme creation, and know why they are doing this. Possibly adding a extra complicating step in WordPress theme design. Otherwise at some point they or their client could start getting a update message for their theme. " design_dolphin 7625 """Customize Header"" page visual corrections [patch]" Themes 2.7 low minor WordPress.org enhancement new 2008-08-28T10:44:50Z 2011-02-07T12:23:07Z "I prepare patch which make this page a little bit nicer. Advanced options are now under colorpicker buttons not ""Update Header"" button. Visualisation: http://img28.picoodle.com/data/img28/3/8/28/f_TestBlog825m_2edd713.png Patch tested on WordPress blog (latest rev.)." Simek 16868 Add WordPress Required Version and Tested Up To Version for themes Themes 3.1 normal normal WordPress.org enhancement new has-patch 2011-03-16T20:04:27Z 2012-07-09T15:47:25Z "The premise of this idea is for Theme authors to be able to add a reference to the version of WordPress their Theme requires to work correctly; and, the version of WordPress the Theme has been tested up to. This idea comes from the the plugin readme.txt file and some of the data that is expected to be found there. Once implemented, further enhancements to the Appearance tab in the Administration Panels can be added to better inform end-users on the compatibility of the Theme with their current WordPress installation." cais 4518 Nested

, 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
Faça Upload aaaaaaah-lek-lek<\/code> para a pasta \/wp-content\/plugins\/<\/code><\/li>\n
Ative no menu 'Plugins' no seu WordPress<\/li>\n<\/ol>"", ""changelog"": ""1.0<\/h4>\n\n\nLanç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: "\200F"; } #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 24397 Embiggen the linked WordPress og:image Otto42 WordPress.org site normal normal WordPress.org enhancement assigned 2013-05-23T18:14:33Z 2013-05-23T18:42:00Z "Looks like !WordPress.org blog posts currently use [http://wordpress.org/about/images/logo-blue/blue-l.png a 150x150 px image] as an Open Graph protocol image to sexify shared links on Facebook, Twitter, Windows 8, LinkedIn, etc. Facebook has a minimum image dimension requirement of 200x200 px to optimize for selecting an image that works in a variety of display scenarios including HiDPI. Current image is under that minimum dimension. Facebook supports an image up to 5 MB in filesize. Twitter supports up to 1 MB in filesize. Bump up the size of the default [http://wordpress.org/about/logos/ WordPress logo] used as an og:image on !WordPress.org blog and elsewhere to something huge (ideally > 1500x1500 px) for maximized display opportunities for !WordPress.org link summaries displayed on other sites. Example URL: http://wordpress.org/news/2013/04/save-the-date-may-27/" niallkennedy 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" nacin* WordPress.org site normal normal WordPress.org enhancement accepted 2011-09-16T10:34:02Z 2013-05-25T16:45:50Z "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 close 2013-04-12T18:29:32Z 2013-05-24T16:00:04Z "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 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 16103 Blue Admin theme doesn't have enough contrast Accessibility 3.1 normal normal Future Release defect (bug) new has-patch 2011-01-05T03:51:32Z 2013-05-14T13:21:17Z "The beautiful blue theme has a few parts that lack sufficient contrast to be useable by someone with color deficiencies. Specific parts to follow. See attached screen shots to get a better idea. Highlighted areas lack contrast. " jorbin 22682 Close Button Breaks in Customizer After Refresh Accessibility 3.5 low minor Future Release defect (bug) new 2012-12-02T17:10:01Z 2012-12-04T04:43:17Z "Steps to reproduce (keyboard only): 1. Open the theme customizer. 1. Tab past the top buttons. 1. Press F5. 1. Now try to use the Close or Cancel button. Expected result: Should be able to Close or Cancel. Actual result: The button can still be clicked, but it is broken for keyboard usage. Found in 3.5-RC2-22961 using Chrome 23 and WinXP." miqrogroove 12825 Largest minimum text size in FF prefs makes admin display terrible Accessibility 2.9.2 normal normal Future Release defect (bug) new dev-feedback 2010-04-02T22:25:59Z 2013-01-20T18:04:36Z "The backend looks great in FF if a user zooms, as long as they don't zoom text only. However, some visually disabled people use the Firefox preference for minimum font size instead, because doing full zoom means lots of horizontal scrolling. Is there anyway to make it so that a large minimum text size wouldn't be so terrible-looking? To reproduce: in FF, go to Preferences, Content, Advanced Fonts, select 24 for minimum size. Look at the admin; eek! (In comparison, zooming to that size looks very pretty, but requires horizontal scrolling). Gmail does it decently, so I thought it was worth asking, but I know that there may be technical reasons that we can't make it happen. Would just like to know what those are if so, so I can explain to users who ask about it. If we *can* make it happen, that would be sweet. " jane 16433 Extend function to optionally include commenter name in comment_reply_link merty* Accessibility 3.0.4 low normal Future Release enhancement accepted has-patch 2011-02-01T16:27:45Z 2011-09-12T12:05:09Z "Screen readers recognize links and make them searchable. Unique names facilitate that search. Links need to have unique names that are descriptive and make sense when read out of context. WordPress allows users to set the text they want to display on the comment_reply_link but then this text is repeated for every comment on a post. WCAG Checkpoint 13.1 says: Clearly identify the target of each link. [Priority 2] For improved accessibility it is far better to have the comment_reply_link include the commenter name. ""Reply to Tom Thumb"" and ideally, include a title on the link that includes both the commenter name and comment number. Users should have the option to filter for their custom text and to include (or not include) the commenter name. At the moment, anyone who wants to present an accessible front-end cannot use threaded comments unless they are prepared to generate masses of the same, generic, unhelpful link. " Elpie 9445 All Input Tags are not Section 508 Compliance Accessibility 2.7 normal normal Future Release task (blessed) reopened 2009-04-02T18:58:32Z 2012-10-09T20:14:56Z "Not all of the input tags within the Wordpress admin console are section 508 compliant (http://www.section508.gov/). We have scanned the application using compliance software and found many instances where input tags (checkbox, text, textarea, file, radio, etc..) are missing the required label or alt text. (There are many instances where it IS compliant.) We (developers at a government agency) have the ability to make the changes, but some of the decisions for which exact text to put in the labels and alt text should probably be decided by a more dedicated Wordpress developer. Please contact me if you want our help or input. We believe that the software is extremely close to 100% compliance. Bringing it to 100% would be a huge deal for government agencies wh are trying to get approval to install and run Wordpress internally and externally." dmo7 9698 WordPress back end is not accessible Accessibility 2.8 normal major Future Release task (blessed) new 2009-05-01T18:15:41Z 2012-02-20T20:50:25Z "The WordPress back end violates several WCAG accessibility guidelines, so it cannot be considered accessible to people with disabilities. Guidelines: http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/ Not being an accessibility expert, I am not sure of all of the violations. But guideline 6.3 states ""Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page."" This means that you should be able to do all functions in the WP back end with JavaScript disabled. As of 2.8-bleeding [11148], there are several things you cannot do with JavaScript disabled: 1) Upload and attach media to a post. You can upload media in the Media section, but the media upload section of the post edit screen is missing without JS, and I see no way to attach it to a post. 2) Add tags to a post or change which tags are on a post. The tags section is totally blank without JavaScript. (It could at least have the default plain-text field that is there behind the scenes and hidden). " jhodgdon 15827 AJAX paging breaks badly when json_encode can't encode Administration 3.1 normal normal Future Release defect (bug) assigned has-patch 2010-12-15T14:27:33Z 2011-02-11T07:20:32Z "If json_encode can't encode a response for some reason you get no feedback at all except for a blank list. This seems most likely to trigger with invalid UTF8 sequences in spam comments. With non-ajax paging you at least get all the comments displayed even if you do get a lot of ??? for the bad chars Example Error seen: {{{ [15-Dec-2010 14:18:38] Warning: json_encode() [function.json-encode]: Invalid UTF-8 sequence in argument in /home/wpdev/public_html/wp-admin/includes/class-wp-list-table.php on line 839 [ }}}" westi 13972 Add new category link - capability check needed Administration 3.0 normal minor Future Release defect (bug) new has-patch 2010-06-18T09:01:43Z 2012-06-29T18:18:58Z "/wp-admin/link-add.php If user doesn´t have ""manage_categories"" capability, add new link page, will show ""add new category"" link and form, it should be hidden. " wjm 14565 After Category Quick Edit Update Parent Category Dropdown Administration 3.0.1 normal trivial Future Release defect (bug) new has-patch 2010-08-08T22:07:45Z 2010-12-26T23:09:36Z "On a clean install I went to Posts -> Categories and used Quick Edit to rename 'Uncategorized' to 'Rename-Test' I then went to create a new Category using the form on the left and the Parent drop down still lists 'Uncategorized'. Should this be updated without have to reload the page?" Dempsey 13218 Allow to specify name of drop-in which is not a plugin nacin Administration 3.0 normal normal Future Release defect (bug) reviewing 2010-05-02T21:14:23Z 2011-04-07T03:49:48Z As I mentioned in #11861, plugin DB Cache Reloaded have two files: one main plugin file, and another used as `wp-content/db.php` drop-in. I would like to provide name for the drop-in file, but now the only way is to use the `Plugin Name:` header. Unfortunately when I do this, drop-in file bundled with plugin appears on plugin list. Therefore I need new header, which could I use to specify drop-in name, without that unwanted side effect. sirzooro 10422 Answering to comment from Dashboard does not update Dashboard statistics Administration 2.8.1 normal normal Future Release defect (bug) new has-patch 2009-07-16T05:18:48Z 2012-09-17T19:50:52Z "Hi there, there is a short statistics ""Right now/At a Glance"" box in Dashboard, containing number of posts, pages, comments etc. There is also a box with list of most recent comments in the Dashboard. If a user answers to a comment in this ""Recent comments"" box in Dashboard, which uses AJAX, so it does not reload the whole page, it creates a new comment, but the number of comments in the ""Right now"" box is not updated. I know this is not a critical bug, but it would be really nice if it works. Take care, Honza P.S.: As there is no ""Dashboard"" component in the Trac, I did not know whether to assign it to Administration or Comments component. I put it into Administration, if you think it better suits to Comments or any other component, please feel free to change it." honza.skypala 16946 Bug between CPT menu_position and add_object_page() Administration 3.1 normal normal Future Release defect (bug) reviewing 2011-03-23T10:11:12Z 2012-07-20T13:49:29Z I write a demo plugin for describe the bug. See attachment. momo360modena 10762 Bulk editing creates invalid URIs Administration 2.8.4 normal normal Future Release defect (bug) assigned 2009-09-09T16:53:30Z 2013-05-12T10:27:16Z They simply get too long for example if you move 999 posts to trash. It might be helpfull to switch to the post form method. hakre 15761 Bulk editing on posts without Javascript enabled results in the post being set to draft garyc40 Administration 2.9 normal normal Future Release defect (bug) assigned needs-refresh 2010-12-10T09:03:35Z 2011-06-09T19:49:56Z "Currently, Bulk editing is available without JavaScript being enabled. The result of attempting to edit a post, is a redirect back to the posts page with the post being marked as a draft. No UI is offered for bulk editing. This behaviour exists in trunk, 3.0, and 2.9 from my testing (havn't tested earlier versions). The Bulk editing screen appears to work without Javascript for modification submittal, so it's possible that a non-js version would be possible." dd32 16793 Bulk inline post edit doesn't show categories or tags if the CPT doesn't support titles Administration normal normal Future Release defect (bug) reopened has-patch 2011-03-07T23:24:56Z 2011-05-22T17:04:59Z "1. Register a CPT that doesn't support titles: {{{ add_action( 'init', function() { register_post_type( 'foo', array( 'show_ui' => true, 'label' => 'Foo', 'supports' => array( 'editor' ), 'taxonomies' => array( 'category', 'post_tag' ) ) ); } ); }}} 2. Create a 'foo' post. 3. Go to wp-admin/edit.php?post_type=foo and choose the 'Edit' bulk action. Expected behaviour: shows the category checkbox list and the tag textarea. Actual behaviour: only the status dropdown is shown. " scribu 15784 Contributors can't easily view others' posts in a certain term Administration 3.0 normal normal Future Release defect (bug) new reporter-feedback 2010-12-12T11:38:39Z 2012-02-10T15:01:16Z "As a contributor, the default tab is 'Me', not 'All'. But you can go to 'All' and see a list of all posts. At that time, you can also search for posts, and filter by category, date, etc. Those all work fine. You can also filter by category or tag by clicking a term in those columns, but this doesn't work -- all_posts=1 gets removed, and you end up seeing the 'Me' tab again. You can manually append all_posts=1, but there's no way to actually filter by term viewing all posts via the UI. Interestingly, the author query var works. That'd be bad if it didn't. But it doesn't append all_posts=1, so it's done internally." nacin 18563 Disallowing editing of .php files in the plugin editor blocks access to allowable extensions Administration 2.8 normal minor Future Release defect (bug) new 2011-09-01T04:12:29Z 2011-11-02T00:06:47Z "By using the editable_extensions filter, a user can disallow the editing of php files (more accurately: files with a php extension...) {{{ add_filter( 'editable_extensions', 'disallow_php_file_editing' ); function disallow_php_file_editing( $editable_extensions ) { unset( $editable_extensions[0] ); return $editable_extensions; } }}} However, the file selected when first clicking on the Editor link in the menu is always a php file, so the user is given the ""Files of this type are not editable"" wp_die() message without being presented with a chance to select a file with a different/allowable extension." trepmal 16475 Displaying submenus in custom taxonomy of active parent Administration 3.1 normal normal Future Release defect (bug) new has-patch 2011-02-07T02:26:20Z 2011-07-22T09:27:13Z In a hierarchical taxonomy, if a top level item in the hierarchy is selected when editing a post, after save that item's orphaned children and grandchildren will also show as top level items. It flattens the hierarchy. nick4fake 17916 Enqueued styles are only printed on login_footer in wp-login.php Administration 3.2 normal normal Future Release defect (bug) reopened 2011-06-28T00:29:48Z 2012-11-05T19:19:34Z "In my plugin I have this include: wp_register_style(""cimy_uef_register"", $cuef_css_webpath.""/cimy_uef_register.css"", false, false); now independently where and when I use the above css, even if I never enqueue or print it... it basically forces the admin panel to be always left instead of the right. In particular it changes the admin panel menu #adminmenu to stick to the left, also other little things. The question is: why this happens even if the CSS is not included at all? Browsing the documentation quickly on that function I didn't find anything useful, please help me." Cimmo 15659 Entity escaping needed for comments list table Administration normal normal Future Release defect (bug) new has-patch 2010-12-03T07:05:52Z 2011-02-14T06:32:02Z "Perhaps only as a result of the fact that the URL will be truncated for display, it is possible that URLs will have entities in URLs such as & truncated, thereby creating a non-well-formed entity for application/xhtml+xml . The following patch fixes it (quotation escaping is not needed since this is element content). This is an easy fix which I hope can be applied given that its lack breaks reviewing the important comments editing page. Thanks." brettz95 17607 Google blog search API shutdown westi Administration 3.2 normal normal Future Release defect (bug) assigned has-patch 2011-05-29T11:21:19Z 2012-10-11T23:13:54Z "I have done a search and can't see that this has already been reported. On the wordpresss dashboard the 'incoming link search' uses google blog search API. Google has announced that this api is being shutdown as of effect 26 May 2011 (http://code.google.com/apis/blogsearch/). It will continue to work but with limited functionality (due to their deprecation policy). I therefore suggest that this be removed or use a different API." jcnetsys 19206 Improve internal admin menu code Administration 3.3 normal normal Future Release defect (bug) new has-patch 2011-11-08T17:53:44Z 2011-11-09T16:27:02Z "The internal admin menu code is both hard to read and filled with several unnecessary branches. This makes maintaining the code quite difficult. A few uses of list and smarter branching can considerably improve _wp_menu_output. Patch attached. Let's revisit this when we branch for 3.4." koopersmith 12789 Inconsistent left or right margins on admin screens Administration low minor Future Release defect (bug) new 2010-04-01T02:46:07Z 2012-12-06T06:06:53Z There are a couple of admin screens where the screen icon is not aligned to the left of the content. scribu 16972 Input type radio losts its checked focus when metabox is dragged azaozz Administration 3.0 normal normal Future Release defect (bug) reviewing has-patch 2011-03-26T14:16:05Z 2012-11-07T21:31:46Z "This happens when I use a radio button in a metabox. Once I try to drag it to different position or just drag and let it go the checked focus is lost. (in code it of course still remain checked, but visually not) Bug not happens with other fields I tested (checkboxes, inputs, textareas)" depi 18449 List Table Factory Needs to be Pluggable Administration 3.1 normal normal Future Release defect (bug) new 2011-08-16T19:51:33Z 2012-03-31T08:34:37Z "Better design planning should have been considered for http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/list-table.php function _get_list_table() is identical to an object factory pattern, which would make more sense as a static member of WP_List_Table. In other words... {{{ $wp_list_table = _get_list_table('WP_Terms_List_Table'); }}} ... which looks simple, is actually confusing because it would be more intuitive if written as ... {{{ $wp_list_table = WP_List_Table::factory('Terms'); }}} Further, the factory hasn't offered any extensibility. Locking edit-tags.php against WP_Terms_List_Table makes it unusable for custom taxonomies that need a custom UI. Despite all of the great API improvements for taxonomies, this case still necessitates duplicating the entire category editing UI within a plugin just to tweak a table column or a link path. Please adjust the ticket Type and Component as necessary. It could be a taxonomy design flaw or an administration enhancement, depending how you look at it." miqrogroove 14949 Login gives false assurance of having logged out filosofo Administration 3.1 normal normal Future Release defect (bug) new has-patch 2010-09-23T10:39:34Z 2012-09-20T22:02:19Z "If you visit `wp-login.php?loggedout=true` while logged in, WordPress falsely tells you that ""You are now logged out."" This is a problem because it could lead you to think, e.g., that a public computer is no longer authenticated with access to your WP admin. Patch redirects a still-authenticated user back to the admin from the login page if she requests the above page without actually having logged out." filosofo 13655 Login/Install/User Edit should stripslashes() $_POST data Administration 3.0 normal normal Future Release defect (bug) new has-patch 2010-05-31T11:33:17Z 2010-11-13T08:05:36Z "Following on from #13654 All Login/Registration/Install/User Edit functionality should stripslash $_POST data. At present, it seems that we do not stripslash at all. For existing user passwords, we should migrate passwords to their non-stripslashed versions: [5/31/10 6:34:11 AM] Mark Jaquith: We could migrate people.[[BR]] [5/31/10 6:34:13 AM] Dion (dd32): Perhaps oughta just add proper stripslashing in 3.1, and add back-compat to change password from non-stripslashed to stripslashed.. similar to the md5->phpass implementation..[[BR]] [5/31/10 6:35:13 AM] Mark Jaquith: Yep. If the PW doesn't match, addslashes() and compare again. If that matches, set the new PW hash. Right?[[BR]] [5/31/10 6:35:19 AM] Dion (dd32): yep " dd32 18724 Non functioning 'paged' input on theme/plugin search Administration 3.1 normal minor Future Release defect (bug) new has-patch 2011-09-20T13:09:04Z 2011-11-08T20:56:31Z "In the WordPress Admin -> Install Themes -> Search ... The page number input is not functional. Same for plugin search." kurtpayne 16683 Nonce failure error message causes a warning, and also ugly error. Administration 3.1 normal normal Future Release defect (bug) new has-patch 2011-02-27T04:05:15Z 2011-02-27T07:25:36Z "{{{ ( ! ) Notice: Undefined offset: 4 in C:\www\wordpress-commit\wp-includes\functions.php on line 2624 Call Stack # Time Memory Function Location 1 0.1991 455408 {main}( ) ..\options-permalink.php:0 2 15.8632 23506944 check_admin_referer( ) ..\options-permalink.php:69 3 15.8637 23507168 wp_nonce_ays( ) ..\pluggable.php:839 4 15.8638 23507240 wp_explain_nonce( ) ..\functions.php:2657 Your attempt to change your permalink structure to: has failed. }}} I left the permalink page open for a few hours, and just went to update it. Upon clicking update, I was given the above error (see attached jpeg). It feels pretty clunky and average to have a simple text like that. The warning looks to be caused by the nonce error not being set possibly.." dd32 16162 Pagination and sorting reset after bulk media deletion Administration 3.1 normal normal Future Release defect (bug) reopened 2011-01-09T11:43:33Z 2011-10-27T06:23:48Z When doing Bulk Deletes on paginated Media Library, after performing the delete, I'm back on page 1 regardless on which page I've been before. hakre 18974 Plugin table IDs can collide with core IDs Administration 3.3 low minor Future Release defect (bug) new 2011-10-17T23:14:04Z 2012-01-05T05:33:52Z "Go to Plugins > Add New and install my ""Local Time"" plugin. Go to Plugins > Installed Plugins. My plugin's details will show up in italics. This is because the table row is given the ID `local-time` (my plugin's slug) and core has this CSS: {{{ #utc-time, #local-time { padding-left: 25px; font-style: italic; font-family: sans-serif; } }}} https://core.trac.wordpress.org/browser/tags/3.2.1/wp-admin/css/wp-admin.dev.css#L4287 Targeting this in `options-general.php`: {{{ %1$s'), date_i18n($timezone_format)); ?> }}} https://core.trac.wordpress.org/browser/tags/3.2.1/wp-admin/options-general.php#L167 I'm not quite sure why core is using an ID instead of a class. I'm also not quite sure why the plugins table isn't using a prefix of say `plugin-` since the slug can literally be pretty much anything. Probably better to change the former than the latter for backwards compatibility reasons though." Viper007Bond 14188 Quick Edit Parentage filosofo Administration 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-03T19:55:37Z 2012-10-19T22:06:25Z "If you change a page's page via quick edit, the page item stays below its current parent. It seems to me that it ought to move underneath the new parent or disappear if that parent is not on the current page." filosofo 15981 Quick edit (and other actions) need to cancel AJAX actions garyc40 Administration 3.1 low normal Future Release defect (bug) assigned has-patch 2010-12-26T05:17:36Z 2010-12-26T21:03:24Z "Right after you click to paginate, sort or try to search something, you may be inclined to click another link on the page. This happens often when I'm browsing, and on a server with a relatively slow AJAX round trip, it can happen quite commonly. Problem: If you open Quick Edit, then the ajax results should noop. There might be other actions, but this one in particular does not lead to another page (which obviously would kill the ajax). The reverse is also an issue. You can search, paginate, or sort when Quick Edit is open, and you lose your edit. This might be bad when quick editing a comment, as you could be losing actual content. Searching and paginating might be explicit actions, but it's not difficult to accidentally click a th and trigger a sort, especially if the first row's quick edit (or bulk edit) is open. I'm not sure what to do here, other than a JS popup for any time a Quick/Bulk Edit is open, asking you if you want to lose your changes. So again, two things: - Kill the AJAX action if Quick Edit is opened. I would consider this lower priority. - 'Lose your changes' confirmation for quick edit and bulk edit before an AJAX action. (We can probably fire the AJAX action and trigger the alert simultaneously, but delay processing the results until the confirm() is true.)" nacin 6342 "Rapidly spamming/deleting comments can break ""infinite river"" feature on comment moderation pages" mdawaffe Administration 2.5 normal normal Future Release defect (bug) new 2008-03-21T22:05:16Z 2011-12-14T13:18:06Z "Comment moderation pages have an ""infinite river"" feature whereby when you remove one comment (spam/delete), it'll load a new one at the bottom. Unfortunately, it doesn't seem to catch up if you click more rapidly than about once every 2 or 3 seconds, and you'll ""lose"" comments. At the end, you may just have one comment that, when dealt with, will be replaced by only one comment. This may have to do with doubleclicking the ""spam"" link, or maybe clicking the ""spam"" link of the next comment before the river action has finished." markjaquith 15414 Rework admin searches and make them compatible with no-js again ocean90* Administration 3.1 normal normal Future Release defect (bug) accepted 2010-11-13T13:53:19Z 2010-12-10T19:36:56Z "I'm working on #15355 and found some problems with the searches. I will use this ticket to add the patches, one patch for each problem which I have found. A list with what it not working: - ~~Comments search doesn't work without JS~~ fixed - ~~Users search doesn't work with and without JS~~ fixed - http://grab.by/7nC2 I like the idea with the new tab ""Search Results (1)"", but you will see it only in no-js version and only for themes and plugins search. We should add it for all searches, AJAX search and with no grey bgcolor to be consistent. '''Or''' we must respect the active tab like we did it on comments search, so if 'Sticky' tab is active search only through sticky posts and not all as it is yet. Consistent is the word here. - Behaviour after a search without any results: With JS it's an empty table and with no-js we have the message ""No xxx found.""" ocean90 24149 Set RTL body class for iframes Administration normal minor Future Release defect (bug) new commit 2013-04-21T03:57:06Z 2013-04-22T06:36:02Z "iframe_header() sets the current locale string in the body class, but not the RTL flag. Please add this. This came up in MP6 development, where MP6 does not (at this moment) rely on a separate rtl stylesheet like in the current admin CSS, but instead relies more on the body having .rtl set." mitchoyoshitaka 9296 Settings API & Permalink Settings Page Bug jfarthing84 Administration 2.7.1 normal major Future Release defect (bug) reopened has-patch 2009-03-07T05:33:55Z 2013-04-22T20:58:19Z Although there is a hook in the options-permalink.php to insert custom settings, it does not actually save any custom setting which is added to that page. Instead of posting to options.php like all the other options pages, it posts to itself and only handles the form data which is built into the wordpress core. It should be implemented on that page to also store custom settings that may be hooked onto that page. jfarthing84 16345 Some submit buttons shouldn't have names Administration 3.1 normal normal Future Release defect (bug) reopened has-patch 2011-01-22T18:24:30Z 2011-02-13T14:38:59Z "Technically a regression due to the submit_button implementation. What happens instead is the URL gets polluted. Noticed especially after we moved back to GET on a bunch of screens. In these cases, we just need the form to be sent. Don't need the context info." nacin 15993 Sort arrows improperly wrap on narrow columns Administration 3.1 normal normal Future Release defect (bug) reopened 2010-12-27T06:14:21Z 2012-11-01T06:22:32Z Specifically, I noticed the 'Posts' column on a taxonomy screen (or 'Links' for link categories, etc). nacin 15861 Sorting users by post count Administration normal normal Future Release defect (bug) new dev-feedback 2010-12-17T10:21:24Z 2012-01-18T22:48:06Z "Currently, to enable sorting by post count, there's a JOIN made between the users table and the posts table. This is bad, because users is a global table, which might be stored in a separate database. Short-term solution for 3.1 is to disable sorting. Long-term solution is to avoid the JOIN somehow. " scribu 17036 Theme editor shouldn't override root directory files with same names in child directories Administration 3.1 normal normal Future Release defect (bug) new 2011-04-03T19:11:33Z 2012-06-27T10:23:07Z "'''Steps to reproduce:''' 1. Create subdirectory: blogs 1. Create file in subdirectory: index.php 1. Try selecting Main Index Template in Theme Editor Example is taken from BuddyPress' theme structure. `get_file_description()` doesn't account in any way for the presence of subdirectories since it uses `basename()`." kawauso 21249 WP_List_Table::single_row_columns() needs to do an exact comparison Administration lowest trivial Future Release defect (bug) new has-patch 2012-07-13T01:20:28Z 2012-11-07T22:05:29Z "If for whatever reason you pass a column ID of `0` when dealing with a list table, !WordPress thinks it's a checkbox column because of the loose comparison, i.e. `==` instead of `===`. Since I don't see why passing a number instead of a string shouldn'r be allowed, attached is a patch." Viper007Bond 11207 WordPress may display incorrect message when post is saved/published/etc bsamrajni* Administration 2.9 normal normal Future Release defect (bug) accepted has-patch 2009-11-20T20:23:23Z 2011-06-25T20:35:42Z When post is saved, WP calls `wp_insert_post_data` filter. Plugin can use it to change post status. But even post status has been changed via plugin, WP still displays message basing on action originally executed by user. Need to change this and take into account final post status too. sirzooro 11311 kses converts ampersands to & in post titles, post content, and more Administration 2.9 normal normal Future Release defect (bug) new 2009-12-03T01:49:32Z 2013-05-17T10:03:16Z "Make a test user that has the ""author"" role (i.e. no `unfiltered_html`) and write a post with a title that has `&` in it. After saving, it will becomes `&` due to `wp_filter_kses()`. It gets saved in the database this way too. It's confusing to the user." Viper007Bond 16865 'post' definition should use menu_position Administration normal normal Future Release enhancement new has-patch 2011-03-16T15:03:00Z 2011-03-17T10:32:11Z Since WP 3.1, we don't need to hardcode the Posts $menu array, since register_post_type() is flexible enough to handle it. scribu 7756 AJAX saving method instead of reloading the page Administration normal normal Future Release enhancement new 2008-09-16T17:36:44Z 2013-01-03T16:12:25Z "Instead of using a traditional page refresh after saving a post, utilize AJAX, similar to how auto-saving already functions, to save the post. this would help decrease the load on the server and enhance the user experience." jdingman 11164 Add Theme Sort Filter Administration normal normal Future Release enhancement new has-patch 2009-11-17T16:03:18Z 2009-12-01T18:16:20Z "I've run across the need for this in a few plugins. You can't adjust the order of themes in the theme browser as all filters are applied before the sort. Aaron (for Incsub)" uglyrobot 15355 Add ability to clear search results garyc40 Administration normal normal Future Release enhancement assigned has-patch 2010-11-09T08:11:56Z 2012-04-13T11:32:28Z "Let's put a (X) next to ""Search results for `string`"" that immediately clears the search results. Otherwise there is no way to do it, without clearing the box manually and hitting enter. We would use the same X we use for bulk edit." nacin 11200 Add count for approved comments filter Administration normal normal Future Release enhancement new has-patch 2009-11-20T15:17:04Z 2011-06-29T17:28:19Z On wp-admin/edit-comments.php, Approved is the only filter that doesn't have a count after it. scribu 15261 Add do_action to form tag in edit-tag-form.php Administration 3.1 normal normal Future Release enhancement reopened has-patch 2010-10-30T16:07:46Z 2011-01-19T23:50:20Z "How about adding additional actions to the form tags in admin taxonomy pages like ''edit-tag-form.php''? An example can be found in ''user-edit.php'' line 183: {{{ > }}} " linguasite 13605 Add filter for admin-ajax get-tagcloud's arguments for wp_generate_tag_cloud Administration 3.0 low minor Future Release enhancement new has-patch 2010-05-28T20:30:43Z 2010-10-27T10:13:29Z Patch attached. mitchoyoshitaka 14126 Add hook for message on admin-header in h1-privacy Administration normal normal Future Release enhancement new needs-refresh 2010-06-28T08:35:10Z 2010-10-28T08:46:46Z "Add a hook for add a message inside from h1 in admin-header.php, same as privacy message in WP 3.0, see example images: [http://drp.ly/1glQ2G] I think, its great for the UI and create messages about all sites in backend. I change also the ID in class, no redunace on use this style. Please see the files and sorry for my bad english." bueltge 16105 Add info re mobile apps to admin isaackeyet* Administration normal minor Future Release enhancement accepted dev-feedback 2011-01-05T11:54:59Z 2013-04-17T01:14:56Z Not sure if it belongs in Tools, or in Writing Settings (or whatever that shakes out to be when we redesign settings), or what, but there should be a screen somewhere in the admin that lists/links all the mobile apps, probably in same area as Press This is promoted. jane 13005 Add plugin hook for ajax-tag-search westi* Administration normal normal Future Release enhancement accepted has-patch 2010-04-14T20:21:50Z 2013-05-10T12:44:02Z I would like to have a new plugin action hook added in the ajax-tag-search section of wp-admin/admin-ajax.php jimmcq 15796 Add spacing in the menu between 59 and 60 to allow menu items to appear above appearance Administration 3.1 normal normal Future Release enhancement new 2010-12-13T14:12:51Z 2011-01-06T12:44:41Z "I would like to place a menu item above appearance however the spacer is directly above the Appearance menu item at 60, the spacer is at 59, just a simple request to appropriate more space that is empty, 55 for the spacer and keep the appearance 60 giving 56,57,58,59 for add_menu items above 60 " Frumph 11469 Additional Admin UI hooks / filters Administration 2.9 normal normal Future Release enhancement new has-patch 2009-12-17T05:54:04Z 2010-12-13T12:43:33Z "Some might classify this as overkill, others as making Wordpress as completely extendable as people want it. I'd like to propose the addition of numerou hooks to the Wordpress core Admin UI which would allow the addition of UI elements outside of the current constraints, such as meta boxes. If that doesn't make sense, I have an example to illustrate: Given the ""Subtitle"" example from http://digwp.com/2009/10/ideas-for-plugins/, there would be a new hook named ""edit_post_form_after_title"" (or something along those lines) which would be placed directly after the post title is displayed on the screen and allow a plugin developer to insert a text field for a subtitle directly below the title field. See the attached patch." johnl1479 10652 Additional arguments required for page_template_dropdown Administration 2.8.4 normal trivial Future Release enhancement new has-patch 2009-08-19T17:29:05Z 2010-08-13T12:23:56Z "As a plugin/theme developer, it would be really useful to be able to call the page_template_dropdown function with a parameter string similar to [http://codex.wordpress.org/Template_Tags/wp_dropdown_pages wp_dropdown_pages]. For example, the current '$default' argument should accept a string of arguments where: - 'selected' is the selected template (replaces the current $default)[[BR]] - 'echo' can be set to 1 to return instead of output[[BR]] - 'name' will set a name/id for the menu[[BR]] This would make it easier to create plugin/theme options where you could select which templates you want to use for different content. At the moment it is possible to do this by replicating and adapting this function but I think it would make more sense to use the same multi-parameter argument as [http://codex.wordpress.org/Template_Tags/wp_dropdown_pages wp_dropdown_pages] and [http://codex.wordpress.org/Template_Tags/wp_dropdown_categories wp_dropdown_categories] and include it in core?" husobj 6822 Admin colors should be per-blog ryan Administration 2.5 normal normal Future Release enhancement new 2008-04-23T02:07:08Z 2010-03-25T05:58:52Z When shared user tables are used, changing the colors for one blog should not change it for all. matt 11515 Admin needs standardized way of handling messages (notices) displayed to the user Administration 3.0 normal normal Future Release enhancement new 2009-12-19T19:53:03Z 2013-03-15T23:45:50Z "If you try to upload a media item under Media > Add new without an uploads directory, you get the following vague error message: {{{ Error saving media attachment. }}} If you try instead to upload from the post edit page, you get a much more helpful message: {{{ Unable to create directory /path/wp-content/uploads. Is its parent directory writable by the server? }}} In each case, the root error is the same, but the second error message points the way to a solution. Even if the user doesn't know herself what that message means, it's a message that provides the necessary information to someone else who does and is trying to help the user. The first message is completely useless, as it states only what we already know: something went wrong. The reason Media > Add new doesn't offer a helpful message is that the error is generated on one page request, and ''then'' the user is redirected to another page. We need a standard, cross-page-load way of conveying messages in admin. I've thought of a few possible ways of doing this: * Define and use a standardized set of error codes and associated error messages. This is similar to what happens currently on many pages: the unhelpful ""Error saving media attachment."" appears when the message argument is set to ""3."" What I'm suggesting would use a common set of message codes across the admin and be much more detailed. So the above situation would instead produce a message like ""Unable to create the uploads directory."" * Save error messages to a cookie. Unlike the previous method, this would allow messages to be made particular to their event. * Have some kind of user messaging stack. New messages would be pushed into a user's stack (stored in usermeta) and popped off after a certain time, or when read, etc. This has the advantage of lasting across sessions and browsers and being usable for other applications, such as PMs between users. What do you think?" filosofo 10726 Admin notifications for more than 1 email Administration 2.8.4 normal normal Future Release enhancement reopened 2009-09-05T02:18:51Z 2013-01-03T05:59:29Z "Please allow admin notifications to go to more than 1 email address. It could be as simple as allowing a comma-separated list. Better yet, allow sending '''admin''' notifications to all people in the '''administrators''' role." novasource 7723 Allow filtering by author on Manage > Posts Administration normal normal Future Release enhancement reopened 2008-09-10T19:59:37Z 2011-12-19T18:04:36Z "In versions of wp before 2.5 you could select an author from a dropdown on MANAGE > POSTS to see only posts owned by that author. This was very useful for quickly sorting posts and is absolutely necessary when you have editor users without the 'edit_users' capability, as unlike admin users (most of us) they don't have access to the 'users' tab and thus have no way to see the manage screen sorted by user. The manage screen sorts by user simply by adding ?&author=$id in the url, but for users without access to the 'users' tab, even author id's are innaccessible. In the #wordpress-dev irc channel ryan boren expressed that the filter was removed because in some cases there were too many users in the system and the resulting dropdown was slowing down pageload time and ruining user experience. This is a paradox, because the more users your system has the more likely you are to need this filter. Wordpress needs to support filtering by author somehow if it wants to be a serious multi-user platform. Our editors are pulling out their hair. My personal opinion is that the dropdown select should be reinstated. Filters should be added to the list such that only users who can post are listed (other users have no use in the Manage > Posts screen), as well as to show only users with at least 1 post. This should avoid slowing down pages for installations where most users are 'subscribers', which would otherwise mean all open-registration blogs would have hugely long lists. Given those two filters, I think that anyone who still has load-time problems should deal with their problem themselves using a plugin. It should be easy to remove the filter dropdown if you don't want it using a plugin, as well as to further filter the authors shown to reduce their number. Any installation with that many users deserves the option of deciding if they want the pulldown or not, and I think many would choose to keep it even if there are problems because it is so incredibly useful in filtering through hundreds of users worth of posts. (Consider: the full categories list is shown, even if there are hundreds, despite the fact that this has the same effect on performance as many authors does). Also in IRC Matt M proposed that some kind of text box + ajax to predict which author you mean could be used for this purpose. I think that is a great idea but would take a lot more work than what I propose (the work for hte pulldown is already done and the old functions are still there, all that's needed is to add filtering and re-work it into edit.php). It could also be used in the 'Users' context for search though, so it could be worth the effort. " jeremyclarke 4221 Allow pure wp_nonce_url urls Administration 2.3 normal normal Future Release enhancement reopened close 2007-05-04T04:29:33Z 2012-08-15T03:44:11Z "wp_nonce_url sends the url through wp_specialchars, which converts {{{&}}} into {{{&}}} That's great for standards-compliant links, but if you're trying, for example, to use a nonce in a url passed to JavaScript, it can cause problems, as at least Firefox chokes when JavaScript requests a url with {{{&}}} instead of {{{&}}}. My patch allows you to toggle off the wp_specialchars; the default behavior remains the same." filosofo 23738 Audit our secondary button uses Administration trunk normal normal Future Release enhancement new 2013-03-11T17:31:26Z 2013-05-16T12:12:03Z "helen pondered in #wordpress-ui that maybe the ""apply"" button in the Screen Options dropdown should be a primary button. There's a good argument to be made that when this panel is down, that ""apply"" button is your new primary. We should do an audit of our buttons to see if there are any other cases where we could make an action or a temporarily primary action more obvious by using the primary button style." markjaquith 17704 Automatically enqueue necessary scripts when custom meta boxes are used Administration normal normal Future Release enhancement new has-patch 2011-06-06T05:53:43Z 2011-11-08T21:30:11Z Right now if you add_meta_box() to a custom page, like using add_submenu_page() and then calling do_meta_boxes(), the screen options and post box JS don't work automagically. They should. mitchoyoshitaka 17766 Browser update dismiss button lacks non-JavaScript fallback Administration 3.2 normal minor Future Release enhancement new 2011-06-11T11:20:58Z 2011-08-27T15:42:14Z The 'Dismiss' button in the browser update dashboard box doesn't do its thing without JavaScript enabled. johnbillion 17360 Change text from Options to Settings Administration 3.2 normal minor Future Release enhancement new has-patch 2011-05-09T23:31:56Z 2011-12-06T04:47:31Z "In various admin screens, change test from options to settings. " michaelh 17852 Collapsed menu fly-out headers should be clickable Administration normal normal Future Release enhancement new has-patch 2011-06-20T03:13:00Z 2012-03-07T20:59:48Z "When you hover over a collapsed admin menu icon, the extension of the icon is not clickable, only the submenu screens are. This is the same behavior in 2.7 to 3.1, but I think it should be considered." nacin 15782 Consolidate header Javascript Administration 3.1 normal normal Future Release enhancement new has-patch 2010-12-12T05:45:53Z 2011-03-24T08:48:43Z "As a followon to #15781 Currently there is a block of Javascript required on all admin pages, this is stored directly within admin-header.php, and iframe_header(). Unfortunately, when someone changes/adds code to one, the other is not always updated. This inline Javascript should be moved to a function and printed on a header action in order to reduce code duplication and prevent future issues." dd32 7797 Consolidate iframe headers Administration 2.7 normal normal Future Release enhancement new 2008-09-26T23:35:46Z 2012-10-30T16:40:45Z "Currently iframes are being used in multiple locations (ie. thickbox, plugin re-activation, etc) and in each case, theres generally a function for the header and footer, or its inline. What i suggest, Is to create a standard set of admin templates which print the headers out for the pages. And a side suggestion:[[BR]] As an added bonus, It should probably be possible to automatically detect if it was loaded via thickbox ($_GET[TB_iframe] shouldnt be set) and serve the correct header (ie. Full admin side menu if no thickbox)" DD32 19898 Create a is_login() function similar to is_admin() Administration 3.3.1 normal normal Future Release enhancement new dev-feedback 2012-01-25T23:13:43Z 2013-02-12T15:34:47Z "It would be useful for developers to have better detection of being on the wp-login.php and wp-register.php pages. Sure, this can currently be done by using the $pagenow global variable but having a similar function like is_admin() would make things easier/cleaner. One use case: -Using a hosted javascript file but then requiring SSL (FORCE_SSL_LOGIN). {{{ #!php function javascript_init() { if ( $pagenow == 'wp-login.php' || is_admin() ) return; wp_deregister_script( 'jquery' ); wp_register_script( 'jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.6/jquery.min.js'); wp_enqueue_script( 'jquery' ); } add_action( 'wp_print_scripts', 'javascript_init' ); }}} Proposed solution: Create a new function that does all the checking. {{{ #!php function is_login() { return in_array( $GLOBALS['pagenow'], array( 'wp-login.php', 'wp-register.php' ) ); } }}}" dcowgill 15790 Date column for Scheduled posts should also state the time Administration 3.0.4 normal normal Future Release enhancement new 2010-12-13T04:37:07Z 2013-01-22T17:33:17Z "For obvious reasons, for scheduled posts, it's very useful to see not just the date but the time, but the wp-admin posts interface does not show it - only the date. It'd be very useful to see the time as well. Thanks." archon810 18199 Deprecate IE7 in the Admin Administration normal normal Future Release enhancement new 2011-07-21T21:05:15Z 2013-04-26T01:27:26Z "markjaquith: > Everyone hates IE7. It’s insecure. Let’s make it go away. Also, dropping IE6 didn’t give us much beyond goodwill, because most of the hacks we needed for IE6, we also need for IE7. So we could actually clean up our CSS a bit if we dropped IE7." nacin 23108 Deprecate add_object_page() and add_utility_page() Administration normal normal Future Release enhancement new has-patch 2013-01-03T02:47:52Z 2013-05-16T11:55:27Z "`add_object_page()` and `add_utility_page()` are not used in core and are just wrappers which pass `$_wp_last_object_menu++` and `$_wp_last_utility_menu++`, respectively, to `add_menu_page()`. This can lead to a conflict with other menu items added by plugins, see #23095." SergeyBiryukov 8420 Disable error redirects when in DOING_AJAX kapeels* Administration 2.7 low minor Future Release enhancement accepted has-patch 2008-11-29T00:28:10Z 2010-11-28T11:30:25Z If a DB/install error occurs in admin during ajax requests (like autosave), the response shouldn't return the whole redirected page, see $ATT (admin-ajax-install-trigger.png). If something goes awry and we're DOING_AJAX, an error message that could fit inline would be better. janbrasna 17470 Display warning when editing the page_for_posts page Administration 3.2 normal normal Future Release enhancement new has-patch 2011-05-17T06:27:13Z 2012-11-19T16:33:34Z "I recently ran into a situation where someone was very confused by the page_for_posts setting and why their page edits were not being respected. It occurred to me that this feature is not terribly well described in the UI for users that don't already understand what it does. The attached patch will simply add a warning as an admin_notice when you are editing the page that is specified as the page_for_posts page. I used a class of error for the admin_notice, but updated might be more appropriate." alexkingorg 20345 Don't show Author column on posts screen for single author sites Administration 3.4 low normal Future Release enhancement new has-patch 2012-04-02T20:42:56Z 2012-04-18T20:39:05Z "The 'Author' column on post listing screens is a bit pointless for single-author sites. To simplify this screen, I think it would make sense to remove this column for sites which only have one user, and possibly also remove it for sites with more than one user but still only one author (ie. `!is_multi_author()`). I'm not sure how best to handle the column's visibility and a user's column visibility preferences at the point when a site goes from being a single-author site to a multi-author site." johnbillion 12890 Draft and scheduled pages not listed in the Parent dropdown Administration 3.0 normal normal Future Release enhancement assigned 2010-04-07T11:59:55Z 2012-07-03T14:15:23Z "Draft and scheduled pages are not available as choices in the Parent dropdown of the Attributes module. This is very similar to ticket #8592, regarding private pages. I'm hoping the fix might be simpler for drafts and future posts." rooodini 9604 Edit screens expire Administration 2.8 normal normal Future Release enhancement new 2009-04-21T06:35:08Z 2009-06-13T02:02:48Z "Steps to reproduce: 1) Open an edit post (or page) screen 2) Take your browser offline for 24 hours 3) Put the browser back online 4) Edit the post, type a lengthy, thoughtful, dramatic entry 5) Click save draft / publish as you prefer Expected result: Your poetic prose is committed to infallible digital memory. Actual result: You're told ""Your attempt to edit blah has failed."" Press the back button and likely see the previous version of your post. Your latest prose exists now only in your memory. Technical details: I think the nonce expires, so the post screen becomes invalid after a while. Proposed solution: Add a javascript timeout to warn the user that the edit screen has expired. Provide a mechanism for the nonce to be updated." chmac 6479 Encourage people to change default tagline markjaquith Administration 2.5 normal normal Future Release enhancement assigned 2008-03-30T19:09:41Z 2013-01-22T00:42:25Z "A lot of people don't change the default tagline, especially if using a theme that doesn't display it. But it still displays in their feed. We should check to see if they still have the default tagline and if so, put a little contextual help in Settings - General that (nicely) encourages them to change it. Props to Chris Silver Smith for bringing this issue up at WordCamp Dallas." markjaquith 16853 Error 500 when a user has too many sites PeteMall* Administration 3.0.1 normal minor Future Release enhancement accepted 2011-03-14T11:15:57Z 2012-02-13T09:36:58Z "'''My installation''' [[BR]] 3.0.1 multi-site installation with more than 7500 blogs, with one user each. I also have one moderation user that can administer each of the blogs. [[BR]] [[BR]] '''The issue''' [[BR]] In the admin interface, when I go to Super-Admin -> Users, and when I display the page that contains my moderation user, I get ""''An error (500 Internal Server Error) has occured in response to this request''"". The page tries to display all the sites administered by him (around 7500 of them), hence the error. [[BR]] [[BR]] Updating to 3.1 didn't resolve the problem. [[BR]] [[BR]] '''Recommended enhancement''' [[BR]] For each user in the list, display only a certain number of sites, with a possibility to see all of that user's sites, if needed." luuzan@… 9931 Extra class for the wrap div's in custom-header.php Administration normal normal Future Release enhancement new has-patch 2009-05-24T17:25:40Z 2010-08-13T11:41:15Z "I'm using custom-header.php to complete the options section for my own themes but for some themes I only need the image section to be visible> Would it be possible to add an extra class reference to the sections? This would make it possible for me (and others) to ''not'' display the irrelevant sections (and thus avoid questions from users about why changes aren't reflected). My suggestions is to go for something like this: {{{ }}} And perhaps that: {{{ }}} needs to be changed into something like: {{{ }}} to keep the icon available when you choose to hide the text section. Cheers :)" stgoos 14097 Idea for placeholder text Administration lowest trivial Future Release enhancement new 2010-06-26T06:28:25Z 2013-01-22T17:40:03Z "Placeholder text has a fatal flaw, in my mind: once the field is focused, that placeholder text is gone. This can be confusing, especially if you tabbed into that field or it was selected by default. You can actually use placeholder text instead of labels, for a minimalistic form layout, but only if you correct this flaw. So here's a potential solution: http://txfx.net/files/wordpress/labels/ It uses HTML 5's {{{placeholder}}} attribute (newest Safari and Chrome support it), with a jQuery plugin to handle that support for other browsers. Thoughts?" markjaquith 17783 Inconsistent theme management screens Administration 3.0 normal normal Future Release enhancement new 2011-06-13T12:32:26Z 2011-06-13T13:12:51Z "On single-site you have tabs, while on multi-site you have an ""Add New"" button: /wp-admin/themes.php (single-site): [[Image(http://core.trac.wordpress.org/raw-attachment/ticket/17783/themes.png)]] /wp-admin/themes.php (multi-site): [[Image(http://core.trac.wordpress.org/raw-attachment/ticket/17783/ms-themes.png)]] /wp-admin/network/themes.php (multi-site): [[Image(http://core.trac.wordpress.org/raw-attachment/ticket/17783/ms-themes-network.png)]]" scribu 22183 "Input type=""email""" Administration normal normal Future Release enhancement new has-patch 2012-10-13T19:01:18Z 2012-11-07T07:53:37Z "Text inputs for email addresses were replaced with email inputs in [20168] but reverted in [20196] due to poor client-side validation by Chrome 17 and Firefox 10, however we've had input type=""email"" on the registration form since [18763]. We should: 1. Test the current state of client-side validation. 2. Either introduce email inputs in the admin area or revert [18763] depending on the results of point 1. See http://core.trac.wordpress.org/ticket/17863#comment:25 for the email input validation issue." johnbillion 14515 Make admin table content filterable by column sirzooro Administration 3.0.1 normal normal Future Release enhancement assigned 2010-08-03T06:16:40Z 2011-10-21T09:15:42Z "I would like to modify Author column on post list - add link to user's profile. Now the only way is to add it to 1st column or custom column, and optionally move it later using JavaScript. Therefore I ask to add new actions for default columns, which will allow to do this. It may be also beneficial to implement this as a general hook which will be called on all columns, including custom ones." sirzooro 8243 "Make draft pages to appear in ""recent drafts"" dashboard gadget" Administration 2.7 normal normal Future Release enhancement new has-patch 2008-11-16T11:08:50Z 2010-06-25T20:21:01Z "In 2.7 beta 2, draft Pages do not appear in ""recent drafts"" dashboard gadget. It would be very nice to see draft pages there as well. Another option is to make it optional and allow one to select whether he/she wants to see draft pages in the gadget. " asandler 15865 Make it easy to disable options / user settings westi Administration normal normal Future Release enhancement new has-patch 2010-12-17T17:52:29Z 2013-01-21T04:12:48Z "We have a wonderful option white listing system. The one thing it doesn't support is hiding the ui of core options if you don't want them changed. We should have a generic way of doing this." westi 16165 Media Library Bulk Delete: Error in deleting... nacin Administration 3.1 low normal Future Release enhancement assigned dev-feedback 2011-01-09T14:20:39Z 2012-11-07T20:17:43Z "While Bulk Deletion, when a user gets the ""Error in deleting..."" message, there is no information given of how many elements have been deleted so far. Let's say there was a bulk of N deletions, getting this error can mean up to N-1 items have been deleted already. Same is the case if for some item, no permissions are granted to delete it. The number of successfully deleted items is missing as well." hakre 17028 "Move the ""last edited at"" text and saved/updated/published notices in post/page editor" Administration 3.1 low normal Future Release enhancement new has-patch 2011-04-02T21:56:59Z 2013-05-24T20:20:52Z "1. The timestamp of the last save is currently displayed at the bottom right of the editor box. It would make more sense for this information to be tied to the Publish box instead. 2. The yellow alert boxes that appear at the top of the page are weird. a) They should appear closer to the button that caused the action (general usability/accessibility best practice), so probably by the Publish box. b) Once you edit anything on the screen, the ""post updated"" (or saved, etc) text should go away, because it is no longer current. Am thinking we could combine these two things into one flexible status message that's located in or adjacent to the Publish box. " jane 16031 New bulk actions hook missing catcher behavior Administration 3.1 normal normal Future Release enhancement assigned 2010-12-29T20:31:04Z 2013-03-12T16:47:57Z "The new bulk actions filter allows you to modify the bulk-actions arrays, but neglects to add the ability to handle the new custom actions. The fix is to simply add one new do_action() hook to the default case of each affected page (similar to the way 'wp_ajax_' handles custom ajax requests). For example, the following might be added to users.php at line 285, immediately after default: do_action( 'bulk_action-'. $wp_list_table->current_action() );" Veraxus 12670 Non-standard htaccess filename breaks mod-rewrite setup ryan Administration 2.9.2 normal normal Future Release enhancement assigned has-patch 2010-03-22T17:44:41Z 2010-04-17T23:38:54Z "I use a non-standard .htaccess filename and thus the mod-rewrite for permalinks didn't work for me as the admin script wrote to a file called .htaccess - this also made my wordpress site throw an HTTP 500 error due to the ""missing"" .htaccess file I think it would be worth adding a check to see what the .htaccess filename is before writing it (the Apache config var is called ""AccessFileName"") I have worked around the problem by creating a symlink from the filename I use to .htaccess." thedotproduct 12694 Orphan themes are listed as broken, but can't be deleted from wp-admin Administration 2.9.2 low minor Future Release enhancement new has-patch 2010-03-24T21:40:44Z 2013-05-16T01:38:05Z "I had been giving a set of ""mobile"" themes a tryout on my WordPress blog. There's a parent theme and three child themes. Didn't really like them. Not realizing they were parent/children(I thought they were 4 independent themes that were identical except for color schemes), I deleted the parent theme first through the WP-Admin's theme screen (/wp-admin/themes). Now, the parent theme is gone. But WordPress still lists the child themes as broken themes with the disclaimer: ""The following themes are installed but incomplete. Themes must have a stylesheet and a template."" However, there's no option to delete them from the WP-Admin. Being a longtime WordPress user, I know I can FTP into my server and manually remove those directories. But I'll admit, I love how the newer versions of WordPress have made it possible to install/upgrade/delete themes and plugins right from the Admin system, without the need to open up the ol' FTP client and do it all manually. I'm sure there are also newer users of WordPress who may or may not be aware they'd need to go through FTP to delete a broken theme. Just saying it would be nice if we could delete broken themes right from the Admin system... but it's not a major/urgent request. " pnaw10 16122 Paging in link-manager Administration 3.1 normal normal Future Release enhancement new has-patch 2011-01-06T10:11:07Z 2011-08-06T14:42:39Z "I think it would be a good idea to have paging (""Show on screen"" option) in the link-manager like in pages, sites, media a.s.o." jezze 9883 Password shows under Settings / Writing ryan Administration 2.7.1 low trivial Future Release enhancement reopened has-patch 2009-05-19T23:07:29Z 2013-01-22T16:54:52Z "The password box in the section ""Post via e-mail"" on Settings -> Writing should hide the password, not show it." mastrup 7395 Plugins within a folder (in SVN) should be moved up a level in our plugin upgrader DD32 Administration 2.6 high normal Future Release enhancement new 2008-07-24T04:15:58Z 2010-02-13T02:02:12Z The Paged Comments plugin exists in SVN under a 'paged-comments' directory. Since the auto-upgrader puts plugins into a directory based on their slug, this results in the plugin being under two 'paged-comments' directories. We should be able to identify when a plugin's trunk (or current branch) directory contains only another directory, and move the whole plugin up a level. markjaquith 6106 Post slug improvements markjaquith* Administration 2.5 normal normal Future Release enhancement accepted 2008-03-05T21:08:21Z 2011-09-09T00:02:15Z " 1. ~~Right now, a post ID is shown as the post slug unless a slug is manually entered. Instead, it should show the dynamic slug generated from the title.~~ Ideally, as the title is updated. (maybe using onblur to see if the typed-in title has changed, and doing a quick AJAX request to see what the dynamic slug would be). 1. There is no way to tell the difference between a tentative slug, and a locked-in slug (either by choice, or by hitting ""publish""). Perhaps the highlighting could go away and the slug could be bolded to indicate that it is set. " markjaquith 8592 Private Pages not listed in the Parent dropdown nacin Administration 2.7 normal major Future Release enhancement reopened commit 2008-12-12T16:22:24Z 2013-02-28T12:51:59Z "Private pages are not available as a choice in the Parent dropdown of the Attributes module. You should be able to create a hierarchy of private pages if you want to. Tested with r10194." mtdewvirus 6286 "Proposed changes to ""E-mail me whenever"" Discussion Options" Administration 2.5 normal normal Future Release enhancement new has-patch 2008-03-18T19:14:55Z 2013-05-24T17:23:40Z "WRT the ""E-mail me whenever"" options on the Discussion options page: [[Image(http://img132.imageshack.us/img132/4215/picture1vf1.png)]] 1. For ""a comment is helf for moderation,"" the ""me"" is ambiguous. It should specify that it means the blog admin e-mail address. 1. For ""anyone posts a comment,"" again, ""me"" is ambiguous. In this case ""me"" means the author of the post. The comment notification setting is personal, and therefore should be set in the profile options (where it can retain the ""me""). Some authors may want e-mail notification, others might not." markjaquith 13924 Provide 'reasons to update' text with core update notice in GUU Administration 3.0 normal normal Future Release enhancement new 2010-06-16T19:39:25Z 2010-10-28T09:38:35Z Just like plugins can enter some text to ID why they should be upgraded, we should have this for core. jane 17906 Refactor submit box code Administration normal normal Future Release enhancement new has-patch 2011-06-27T13:27:34Z 2011-06-28T16:01:10Z "The code for the post submit metabox is a mess. It should be cleaned up, so that changes such as #17028 can be done more easily. Will post a patch shortly." scribu 17133 Register ctrl + s event for plugin/theme editor Administration 3.1 normal minor Future Release enhancement new has-patch 2011-04-14T12:20:34Z 2011-12-06T04:07:54Z Often when modifying code or writing a post using the wordpress editor I instinctively hit ctrl + s to save it. Up pops the save website dialog which I then have to close. In Gmail when I hit ctrl+ s it saves the email to drafts. I think a similar thing would be useful for wordpress. jcnetsys 10970 Remove 'siteurl' setting from options-general.php Administration normal normal Future Release enhancement new has-patch 2009-10-17T18:52:10Z 2012-11-16T16:26:34Z "From #10957: azaozz: > Better to fix the cause for this: ""WordPress address"" (siteurl) shouldn't be changeable from Settings->General at all as it cannot be set safely there. Most users would just break their blogs if they change it. > It is set at install and only needs changing when WordPress is moved to another domain or (sub)directory. This happens very rarely and there are other (better?) ways to set siteurl. Denis-de-Bernardy: > in this case, we need to make sure the www. pref is passed on to the site_url. else we're bound to get massive bugs (e.g. #9873) " scribu 14333 Remove page order UI Administration 3.0 normal normal Future Release enhancement reopened dev-feedback 2010-07-17T03:10:23Z 2012-09-02T23:01:02Z "Unkile posts, in pages we can order and re-order the pages (using ""menu_order"" field in ""wp_posts"" table). But since the new ""Custom Menu"" feature was introduced, do we realy need the page ordering? We can create new menus, add as many pages as we like and re-order them as we like (this is the purpose of menues). If we can do this using menus, then we can delete the ordering feature from the page editing screen." ramiy 18788 Remove redundant type attributes from script and style tags Administration 3.3 normal normal Future Release enhancement new has-patch 2011-09-27T06:54:02Z 2013-04-15T10:28:35Z "Now that the admin is using the HTML5 doctype everywhere, the `type=""text/javascript""` and `type=""text/css""` attributes on script and style tags are unnecessary (if they weren't anyway), and I think they can be safely removed to trim a few hundred bytes from core. Should be a simple search and replace exercise." solarissmoke 12432 River of comments in the Recent Comments dashboard module garyc40 Administration normal normal Future Release enhancement assigned has-patch 2010-03-01T00:23:32Z 2011-03-23T17:24:45Z "See #11891, the 3.0 effort. Upgrade the Recent Comments dashboard widget to pull in the 'river of comments' instead of only displaying the configured value (which winds up empty if you delete or spam those 5)." nacin 16413 Settings page needs HTML refactoring and UI improvements nacin* Administration 3.1 normal normal Future Release enhancement accepted 2011-01-30T20:22:09Z 2013-05-21T17:50:22Z "The settings pages haven't had much attention or improvement in a while. We need to refactor the HTML on the settings pages, as they are still using tables instead of divs. We also want to make some minor UI improvements including: - clearer differentiation between option groupings - using consistent text styles for descriptions and links (including the time zone/date format comment) - restructure for better readability Comment if you have any other" chexee 14858 Shortlink On Posts Edit Summary Screen Administration 3.0.1 normal normal Future Release enhancement reopened 2010-09-12T23:08:43Z 2013-01-22T17:32:34Z "We've got a very handy button on {{{/wp-admin/post.php}}} to get the posts shortlink, but that involves going into the post as if you want to edit something! So on {{{/wp-admin/edit.php}}} would it not be appropriate to add some kind of link/button where we can get without needing to go in and edit the post? - Meaning it doesn't need to load any content, possibly add yet another auto-revision, and such...!" markmcwilliams 7615 Show theme name when selecting page templates Administration 2.7 normal normal Future Release enhancement new has-patch 2008-08-27T20:12:39Z 2009-11-20T20:33:10Z "Currently, if a child theme inherits some templates from its parent theme and adds some itself, it's not clear when selecting a page template which templates are from which theme. The attached patch adds the theme name in parentheses after the template name. This is just something that struck me might be an issue, so feedback on whether there is actually a real benefit to the added complexity would be welcome." ionfish 16346 Slug field too narrow in Post Edit Administration 3.1 normal minor Future Release enhancement new has-patch 2011-01-22T18:56:24Z 2011-01-22T19:39:41Z When you edit a post, there is a Slug panel at the bottom where you can edit the slug. The field displaying the text of the slug is set inline to 13, which is not nearly wide enough to show more than 15 letters. ABTOP 9117 Spam queue doesn't distinguish between filter sources Administration 2.7 normal normal Future Release enhancement new 2009-02-12T22:50:51Z 2012-06-19T19:23:07Z "1. On the Settings / Discussion tab, go to the Comment Blacklist box, and add the string ""the"". 2. Post a comment containing the word ""the"". It will be caught as spam. 3. Visit the Comments / Spam tab. Your comment is there, but there is nothing to indicate whether it was caught by the Comment Blacklist, or by Akismet, or by another spam filter. Result: neither the user nor WordPress knows how to prevent that comment from being caught in future. Many users will forget about the Blacklist feature and assume their spam filter plugin is faulty. Suggested fix: comments caught as spam should record the reason. This should be displayed to the user, and used internally by spam filter plugins to decide how to handle false positives. " tellyworth 20052 Support sprites for admin menu icons in register_post_type and add_menu_page Administration normal normal Future Release enhancement new has-patch 2012-02-15T23:14:45Z 2012-12-14T23:49:22Z "We should encourage developers to maintain a consistent and beautiful admin UI by making it easier to register sprites with black and white and color versions of icons for the admin menu, namely in `register_post_type()` and `add_menu_page()` (and its wrappers). Related: We should also do an education push and create an external web tool to make it easy to generate a properly sized, colored, and positioned sprite. Related tickets: #20036, #19886" helen 7485 Terrible UX design on XFN section of Write->Link pages Administration 2.6 normal normal Future Release enhancement assigned dev-feedback 2008-08-08T17:02:49Z 2012-01-06T01:43:58Z "Regarding the XFN section on the Write-Link pages: The UX on this section is fairly terrible. We give the user an editable ""rel"" field and then don't let them edit it via javascript. Note that if you disable javascript and then edit that field, then your changes are indeed saved and then even show up on the resulting pages correctly. That javascript just won't let you manually edit the field. I propose that the javascript on this section be changed to allow manual editing of that field, and to make the checkbox/radio sections just add/remove the relevant bits from the field when they are selected/deselected. Result should allow user to manually insert stuff into the rel field and leave those manual insertions unaltered when changing the radio/checkboxes, unless they conflict with the selections being made directly. Also, side note, would be nice to add a nofollow checkbox to this section as well, to allow easy addition of nofollow to the rel field, which would be handy for the somewhat over-controlling SEO oriented people. ;) " Otto42 19123 Top and bottom pagination should be consistent Administration 3.3 normal normal Future Release enhancement new 2011-11-03T02:39:23Z 2012-12-24T11:45:33Z The top pagination on Install Themes and Install Plugins is the new style (box to type in page number), but for some reason the bottom pagination is old style. These should be consistent. IIRC, the bottom ones were reverted because there was a bug we couldn't solve in time for that version's launch, but we never came back to fix it. Both top and bottom should allow text entry of page number. jane 12914 Update the Right Now box when publishing via QuickPress Administration 3.0 lowest trivial Future Release enhancement new has-patch 2010-04-08T08:03:32Z 2013-01-22T15:57:58Z "When you publish a new post via QuickPress, it'd be cool for the Right Now box to then ++ the number of published posts. Quick proof of concept patch attached." nacin 9777 "Usability : add delete button to ""edit category"" menu" Administration 2.7.1 normal minor Future Release enhancement new has-patch 2009-05-09T22:56:39Z 2012-05-22T16:56:47Z "Add ""delete"" button to ""edit category"" menu so i can delete the category and not only edit it. this is a very useful feature that is missing in this menu. '''LOCATION:''' Admin -> Posts -> Categories -> Edit Category '''URL:''' http://www.site.org/wp-admin/categories.php?action=edit&cat_ID=302 " ramiy 16856 When registering custom post type, menu_position isn't honored if it's a number passed as a string Administration 3.1 normal normal Future Release enhancement new has-patch 2011-03-14T16:52:18Z 2013-03-31T02:52:15Z "When registering a custom post type, if you use '50' instead of just 50, is_int() will fail and the position will be set to ++$_wp_last_object_menu. Seems safer to use isset() instead, since position doesn't technically need to be an integer. ($menu gets sorted before being output, and '50' is the same as 50 in that case) This has the added benefit of allowing MANY more spaces in the $menu variable. For instance, if you passed '50.555' as menu_position, there's very little chance that this will conflict with another theme/plugin register a custom menu or custom post type, and will successfully go between 50 and 51 in the $menu array. There are currently no checks on $position when using add_menu_page() ... but the checks on register_post_type() currently make this an invalid universal solution. Personally, I don't see a downside to letting menu_position be a string. Anything other than a number (whole or decimal) will just go to the bottom of the $menu array, anyway, after the sort. I'm submitting two patches ... one is type independent, and the other casts menu_position as (int) after the isset() check." nathanrice 17851 Wrapping Sections with add_settings_section Administration 3.1.3 normal normal Future Release enhancement reopened has-patch 2011-06-20T03:09:34Z 2011-09-28T18:09:53Z "This is my first time reporting, so excuse my ignorance. I just wanted to see about enhancing the add_settings_section function. As of now, individual sections are not wrapper in any sort of container, which makes no sense to semantic sense to me. Sections should/need to be styled differently, but as of now, you really don't have much control of that. I propose something similar to the register_sidebar function, looking like this: add_settings_section( $id, $title, $callback, $page, $args ) $args would accept 3 parameters: before_section, after_section, and section_class. This way you can style each individual section with relative ease. Just a thought and enhancement to the Settings API. Thomas" griffinjt 12506 admin-color-scheme.css already loaded on wp-login.php. why? Administration 2.9.2 low minor Future Release enhancement reviewing has-patch 2010-03-03T21:55:21Z 2012-07-03T20:55:11Z "On wp-login.php we are already on admin, because wp is loading the whole color-scheme for a user... which is wrong. It is senseless, because the color-scheme the user selected for admin cannot be loaded without his user-data. And that is not possible as long as he/she didn't enter any login-data. REQUEST: get the ~30kB color scheme out of the wp-login.php and add the following to wp-admin/css/login.css: {{{ body.login { border-top-color:#464646; } body, #wpbody, .form-table .pre { color:#333333; } a, /* All obsolete on wp-login.php - could here simply be h1 a */ #adminmenu a, #poststuff #edButtonPreview, #poststuff #edButtonHTML, #the-comment-list p.comment-author strong a, #media-upload a.del-link, #media-items a.delete, .plugins a.delete, .ui-tabs-nav a { color:#21759B; } .submit { border-color:#DFDFDF; } textarea, /* All obsolete - could be #login #wp-submit */ input[type=""text""], input[type=""password""], input[type=""file""], input[type=""button""], input[type=""submit""], input[type=""reset""], select { background-color:#FFFFFF; border-color:#DFDFDF; /* Obsolete due to .submit-class above */ } input.button-primary, button.button-primary, a.button-primary { -moz-background-clip:border; -moz-background-inline-policy:continuous; -moz-background-origin:padding; background:#21759B url(../images/button-grad.png) repeat-x scroll left top; border-color:#298CBA; color:#FFFFFF; font-weight:bold; text-shadow:0 -1px 0 rgba(0, 0, 0, 0.3); } .submit { border-color:#DFDFDF; } .login #nav a { color:#21759B !important; } .login #backtoblog a { color:#CCCCCC; } }}} " F J Kaiser 17520 cite element used incorrectly Administration low trivial Future Release enhancement new has-patch 2011-05-20T17:47:14Z 2011-10-18T21:16:34Z "Here's what the HTML5 specification says about the cite element: The cite element represents the title of a work (e.g. a book, a paper, an essay, a poem, a score, a song, a script, a film, a TV show, a game, a sculpture, a painting, a theatre production, a play, an opera, a musical, an exhibition, a legal case report, etc). […] A person's name is not the title of a work — even if people call that person a piece of work — and the element must therefore not be used to mark up people's names. (In some cases, the b element might be appropriate for names; e.g. in a gossip article where the names of famous people are keywords rendered with a different style to draw attention to them. In other cases, if an element is really needed, the span element can be used.) http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#the-cite-element The element is used plugins/hello.php correctly to mark up the title ""Hello, Dolly"". But many more places it is used incorrectly to mark up an author's name. The obvious fix would be to replace all but the one correct instance of the cite element with spans with an appropriate class." holizz 11705 get_media_item()'s $form_fields do not allow for -style fields. This makes extending the ""Edit Media"" screen via the ""attachment_field_to_edit"" filter difficult for plugin authors to extend." johnl1479 18786 meta_form() should place some restrictions on meta keys Administration normal normal Future Release enhancement new dev-feedback 2011-09-26T22:37:58Z 2013-04-22T21:12:23Z "meta_form() echoes out all meta keys into a dropdown for the custom fields box, unless they start with an underscore (as bound by the query). We should consider is_protected_meta( $key, 'post' ) and/or current_user_can( 'add_post_meta', $post->ID, $key ). This isn't a security thing, just an opportunity to hide some things from the user they don't need to see. On the other hand, it's definitely a number of extra calculations. is_protected_meta() is light as long as there's no filter on things (and if there is, we probably want to know). current_user_can() might be a bit more weight than necessary here." nacin 7422 pass $post_id to filters in sanitize_post_field() on post updates - same for users, etc. Administration normal normal Future Release enhancement new has-patch 2008-07-28T21:18:05Z 2010-07-15T12:17:01Z "the function sanitize_post_field in wp-includes/post.php calls most of the ""database writes"" post filters (e.g. content_save_pre). if a post is updated or created, the function is called in a database context ('db' == $context) and the $post_id argument is not passed to the ""database writes"" filters. while i understand this behavior on post creation ($post_id not yet available) it seems to me that on a post update the $post_id is readily available and could/should be passed to the filters as well. an example where this would be useful is a case where i want to access a custom field value of a post that is currently being updated from the function hooked into content_save_pre. in its current form without the $post_id argument this doesn't seem to be possible." whoismanu 18710 post_deleted_messages filter nacin* Administration normal normal Future Release enhancement accepted has-patch 2011-09-19T21:19:21Z 2012-06-11T13:05:21Z It would be nice to be able to updated post deleted messages like you can through the post_updated_messages filter. jgadbois 14561 wp-admin/edit.php tags of post are hard to compare Administration normal normal Future Release enhancement new 2010-08-08T08:25:02Z 2010-11-18T10:13:25Z "To get an overview about tags used between articles on the post listing in the admin is hard to achieve by the user because they appear not to be ordered. A solution could be to sort them alphabetically. That done, it's easier for the user to compare the usage of tag distribution accross the listing." hakre 18287 wp-login.php - Logo URL should be relative (affects MultiSite) Administration 3.2.1 normal normal Future Release enhancement new has-patch 2011-07-29T00:31:49Z 2013-05-05T04:50:28Z "If you go to your domain.com/wp-login.php page it has a WP logo that links back to domain.com If you're using multisite and go to subsite.domain.com/wp-login.php, it links back to domain.com If you're using multisite and you MAP a domain and go to mappeddomain.com/wp-login.php, it links back to domain.com I can see why this would have been done. It points to network_home_url() which is perfectly sensible for MOST situations. But maybe we should just honor the site on which people are trying to login, so that it's all relative. Given the link on the bottom (back to...) goes to the relative site, this is a logical change. I would say to keep the EMAILS for password resets as is, since the network is in charge of it all, but the front end interface should be consistant. I did a quick test and this works fine on Single and Multi (as expected). So ... here's my first diff!" Ipstenu 15384 wp-login.php refactor Administration normal normal Future Release enhancement new early 2010-11-11T12:40:35Z 2012-05-31T21:40:02Z "wp-login.php needs some serious work. When looking to do some improvements in #5919, I realized I literally needed a goto in order to achieve the goals outlined in this comment: http://core.trac.wordpress.org/ticket/5919#comment:39 I am thinking a WP_Login class with some methods that can handle various different forms, POST handling, and rerouting." nacin 12801 Add Info link to plugins management screen Administration 3.0 normal normal Future Release feature request new 2010-04-01T19:08:40Z 2013-01-22T01:40:01Z "Related to #11050 but instead of the search results, on the regular plugins.php screen. Add ""Info"" link to left of Activate/Deactivate action links, which brings in the tabbed info from the repo. If not from the repo, link does not appear." jane 12273 Better support for sites with LOTS of pages Administration 2.7 normal normal Future Release feature request new 2010-02-18T15:10:02Z 2011-04-18T14:41:23Z "The default page listing is inadequate for sites utilise Pages as their main content type. An option to collapse the page listing and hide ""all"" sub-pages (only showing top-level) would dramatically improve the UI making it easier to find pages within the WordPress structure. '''Example:''' ''Current Page View'' {{{ Page 1 -SubPage 1.1 --SubSubPage 1.1.1 --SubSubPage 1.1.2 -SubPage 1.2 -SubPage 1.3 Page 2 -SubPage 2.1 -SubPage 2.2 --SubSubPage 2.2.1 --SubSubPage 2.2.2 }}} ''Proposed Page View'' ''Default View'' {{{ Page 1 [+] (< click to expand) Page 2 [+] }}} ''Expanded View'' {{{ Page 1 [-] -SubPage 1.1 [+] (< click to expand) -SubPage 1.2 -SubPage 1.3 Page 2 [+] }}} ''...'' {{{ Page 1 [-] -SubPage 1.1 [-] --SubSubPage 1.1.1 --SubSubPage 1.1.2 (> no further levels) -SubPage 1.2 -SubPage 1.3 Page 2 [+] }}} " mkjones 20013 Clean Up Touch UI for Left NavMenu / Flyouts Administration 3.3.1 normal normal Future Release feature request new reporter-feedback 2012-02-10T16:30:50Z 2013-01-22T15:24:19Z While the flyout is mostly usable in it’s current state, it is not as intuitive as it needs to be for the best user experience. They are ineffective at best on the Kindle Fire’s Silk Browser, but work pretty well on the iPad. We need to examine all target devices to ensure interactivity is supported cross-device. georgestephanis 19239 Combine WordPress News and Other WordPress News dashboard widgets Administration 3.3 normal normal Future Release feature request new has-patch 2011-11-12T19:01:42Z 2013-05-14T19:49:51Z We could lighten the dashboard by making this one widget with configuration instead of two separate ones. Anything from WordPress.org official blog would get a highlight to designate it as such. Configure would allow to choose display of both feeds or jus one, and how many items to show. jane 16434 Give site admin ability to upload favicon in Settings, General Administration 3.1 normal normal Future Release feature request new has-patch 2011-02-01T16:57:34Z 2013-02-14T18:13:55Z "WordPress has come a long way in terms of making it possible for someone completely non-technical to create a professional web site for a person or business. One of the little things that is still annoyingly technical is adding a favicon. WordPress.com does this via the Blavatar feature, a name I wouldn't really want us to adopt b/c this is more CMS-oriented, but the ease of uploading an image, scaling and cropping it, then having it become the favicon is something I do want to adopt. Keeping it a theme-based thing means the non-technical can't control it for their sites, which is lame. " jane 13516 Hide JS-only widgets on dashboard is no JS Administration 3.0 normal normal Future Release feature request new 2010-05-24T13:16:42Z 2011-12-24T16:16:41Z "We hide screen options and help; we should also hide these widgets instead of displaying by default with the 'you need JS' message. Affected modules: QuickPress, Incoming Links, Plugins, WordPress Development Blog, Other WordPress News. We should display an additional module for no-JS people that lets them know that their WordPress install would be even more awesome with JavaScript, and list out some of the features they would gain access to with JS enabled. " jane 15289 Make it easier for a non-standard URL to be used to access wp-admin Administration 3.1 normal normal Future Release feature request new dev-feedback 2010-11-02T13:27:05Z 2013-02-07T21:51:15Z "For some sites it is vital that the admin be accessible via a path other than {{{/wp-admin/}}}. Clients sometimes require this because it is easier for their users. Also, it is useful if replacing another CMS with WordPress for the root of the admin to have the same URL, although this can be partially fixed with a redirect. Even when not ''required'' per se, some of us prefer to use a different URL to access the admin because it is more intuitive for our users to use something like {{{/admin/}}} instead of {{{/wp-admin/}}}. To be clear: I am not suggesting renaming the wp-admin directory, nor am I suggesting adding an option in the UI to change the path. Rather, I am suggesting that small tweaks be ade to make it easier for power-users to enable the use of a different URL to access the admin area. I suggest making the following changes : '''1.''' Use relative urls within the admin where possible without affecting standard installations. '''2.''' Allow power-users to add a constant to wp-config.php to change the path of the admin for those links which have to be absolute. I don't think there is much work involved and I am happy to do it. Core devs have in the past stated that the user of alternative urls to access the admin is 'not supported', but it is unclear whether this simply means that it doesn't work at the present time or that the core team is opposed to allowing it to happen.[[BR]] If the latter is the case, I would appreciate an explanation - I'm sure there is a good reason if that is the case, but I can't for the life of me think what it could be. ;)" caesarsgrunt 14676 Moderation email option is confusing, limited Administration normal normal Future Release feature request reopened 2010-08-23T17:06:23Z 2012-05-22T00:53:20Z "The setting is ""E-mail me whenever a comment is held for moderation"" but in that sentence ""me"" is inaccurate; moderation emails are sent to admin_email. ""Email the admin ($admin_email) whenever"" would be accurate. Here's a related question: Why not send moderation emails to post authors?" andy 9057 "Need ""restore defaults"" buttons on all admin screens" Administration 2.7 normal normal Future Release feature request new 2009-02-06T08:50:30Z 2011-07-08T15:06:31Z "Need ""restore defaults"" buttons on all admin screen items, else once you change something, there's no way to get it back to whatever the default was, or find out even, short of a total reinstall. Includes ""screen options"" items too. " jidanni 12004 Select Sidebar when adding Posts/Pages Administration 3.0 normal normal Future Release feature request new 2010-01-25T13:26:16Z 2010-01-25T23:28:01Z "Hey all, I think it would be a cool feature to be able to create sidebars in WP, and then when creating a page you can choose that specific sidebar. I think that this can be accomplished by using the ''Parent'' page technique of selecting if the Page has a Parent and if so which one. Can we develop an option to choose a Sidebar created in the Widgets panel? Cheers, Aron ps: if my help is needed ( im good at design, not coding ) please contact me: info@zipyourmix.com ;)!" lsddesign 11972 Sort View Post/Pages by Column Administration 3.0 normal normal Future Release feature request new 2010-01-21T21:46:27Z 2010-03-21T01:51:40Z Recently I discovered in WPMU in Site Admin options, you can sort for instance Site Admin->Blogs by last activity date. That is a very handy feature, and certainly would useful for a site with hundreds of nested pages. To be able to sort that list by date, rather than just title would be useful, as it sorts by title of the parent page, and finding a 3rd level child can be difficult to say the least. The search feature is lacking but that is for another ticket. Likewise, sorting posts by category, author, etc could be useful. Since the functionality seems to already be there for sorting these type columns, and the code's been moved in already, I'd think it'd be a nominal change. I simply don't know what direction these menus are going yet to offer a working suggestion. Just wanted to get my 2¢ in before it's too late. miklb 18179 WP_Meta_Box Administration normal normal Future Release feature request new has-patch 2011-07-20T01:05:50Z 2013-03-08T16:31:47Z "Ryan, Nacin, and I would like to see a Meta Box class in 3.3. Let's make it happen. Attached is a first pass (in plugin form, for ease). It provides a basic API and supports multiple instances. Instances are stored in a static meta box registry, which should require minimal interaction. Keep in mind that meta boxes are not just registered on CPT pages — they are also used on the dashboard, in menus, and in custom UIs. The parent class should be suitable for each of these cases. I think we should move caps to the main Meta Box class (and allow subclasses/instances to specify/override the cap through $args), and also provide $args to enable/disable any checks we perform before saving (e.g. autosave, etc). It would also be interesting to integrate this with the proposed metadata API improvements. See #15066 for prior discussion." koopersmith 16379 "Better UI for doing ""Page on Front""" Administration 3.1 normal normal Future Release task (blessed) new 2011-01-26T19:47:25Z 2013-03-14T15:20:33Z "[[Image(http://grab.by/grabs/132427e6c1166ed3e4d8214959b9568a.png)]] This is the existing ""Page on Front"" UI. The process is as follows: 1. Create a ""Front"" Page 2. Create a ""Blog"" Page 3. Select the ""Front"" Page in the ""Front Page"" dropdown 4. Select the ""Blog"" Page in the ""Blog Page"" dropdown. 1 and 3 make sense. If you want a page on front, then you obviously need to create a page to live there, along with its content, and then designate it. But the ""Blog"" page is just a dummy. It's sole purpose is to create and maintain a URL for your blog. So why not just have something like this? Blog URL: http://example.com/ {input box} If a page exists in the URL they type, it gets used. If not, we create one on the fly as a dummy. This seems a more natural way of doing it. You don't care about the dummy page — you just want to choose an appropriate URL for your blog." markjaquith 18655 Responsive Admin for Small Screen Devices Administration normal normal Future Release task (blessed) new 2011-09-13T18:44:16Z 2013-01-03T06:24:12Z Working off of #18198 - Making the admin respond to small devices, phones, etc. saracannon 16339 pushState Test Case Administration normal normal Future Release task (blessed) new 2011-01-22T06:30:41Z 2011-01-27T09:42:50Z "This isn't a useful bit of code, just a test case to ground future pushState work for 3.2. Or be ignored by future pushState work for 3.2 :) Attached is a test case for determining browser behavior when using pushState. The numbered links use AJAX and pushState. The ""Other"" link is a real (non-AJAX) link to an external site. If the state of the page is refreshed via AJAX, you'll see a var_dump( $_POST ). If the state of the page is refreshed by a page refresh, you won't. An example of something this test says is broken in Safari 5.0.3 (6533.19.4): 1. Load the page (state = 0: pageload) 2. click ""One"" (state = 1: ajax) 3. click ""Two"" (state = 2: ajax) 4. click ""Three"" (state = 3: ajax) 5. click ""Other"" (state = external site: pageload) 6. go Back in browser history (state = 3: ajax or just history?) 7. go Back (state = 2: ajax or just history?) 8. go Back (state = 1: ajax or just history?) 9. go Back (state = 0: ajax). Everything is fine up to this point, though it's odd we do an AJAX request to get here. 10. refresh the page once, either by CTRL-R or by hitting enter in the URL bar (state = 3: ajax). That's wrong. What happened? Why are we here? 11. refresh the page a second time (state = 0: pageload). As expected. An example of something the test says is broken in Chrome10.0.642.2 dev: 1. Do pretty much anything. Chrome Dev fires a popState event on the first page load. It could be a badly written test, or a badly written implementation of push/popState handling, or both. These are the kinds of scenarios we'll need to test, though." mdawaffe 21890 Customizer spinner breaks button alignment with longer strings Appearance 3.4 normal normal Future Release defect (bug) new 2012-09-14T10:57:02Z 2012-11-08T22:01:23Z See the screenshot. SergeyBiryukov 20729 Improve Admin Colors CSS enqueuing Appearance 3.1 normal normal Future Release defect (bug) new early 2012-05-22T17:19:58Z 2012-05-22T17:20:17Z "The hacky way in which we enqueue the admin colors css means that you get different ordering of the CSS between the development version of the scripts and the script-loader sourced version of the scripts. This can cause CSS bugs which don't show when developing but do when running with the script loader - e.g. #16827 It also makes it harder to implement a custom css concatenator. We should do something like - http://core.trac.wordpress.org/attachment/ticket/16827/colors-hacked-fixed.diff To make this properly enqueue the styles. We should also make this kind of call fire a {{{_doing_it_wrong()}}} as {{{true}}} is not a url :) {{{ $styles->add( 'colors', true, array('wp-admin') ); }}} This code harks back from [7976]" westi 20859 Theme Installer: Preview should be scrollable on iPad and Kindle Fire Appearance 3.4 normal normal Future Release defect (bug) new 2012-06-06T21:51:09Z 2012-06-08T21:10:27Z "Related to #20805. We've added techniques for smoothly scrolling iframes when they're the only frame on the page, but the theme installer still uses the overlay technique. We may be able to iron this out in a similar fashion. Given that the old installer also used an overlay technique, this is not a regression." koopersmith 20733 Theme customizer doesn't order sections based on order added Appearance 3.4 normal normal Future Release defect (bug) new early 2012-05-22T23:36:48Z 2013-01-21T15:16:04Z "When adding sections to the theme customizer, sections with the same priority are given seemingly random order. From the [http://core.trac.wordpress.org/ticket/19910 original customizer ticket]: > Settings and sections both contain priority parameters (you can specify these in the constructor or alter them afterwards) which serve as the primary means of sorting sections before they're rendered. The order settings/sections are added serves as a secondary sorting mechanism (tiebreaker) when multiple items share the same priority. I was under the impression that if the priority was the same, the sections would appear in the order they were added. However, if you add sections A, B, and C (in that order) it seems to display them in order B, C, A. To replicate, add this code to your theme: {{{ add_action( 'customize_register', 'theme_customize_register' ); function theme_customize_register( $wp_customize ) { // Register Section A $wp_customize->add_section( 'theme_section_a', array( 'title' => 'Section A', 'priority' => 35, ) ); $wp_customize->add_setting( 'theme_option_a', array( 'type' => 'option', ) ); $wp_customize->add_control( 'theme_option_a', array( 'section' => 'theme_section_a', 'type' => 'text', ) ); // Register Section B $wp_customize->add_section( 'theme_section_b', array( 'title' => 'Section B', 'priority' => 35, ) ); $wp_customize->add_setting( 'theme_option_b', array( 'type' => 'option', ) ); $wp_customize->add_control( 'theme_option_b', array( 'section' => 'theme_section_b', 'type' => 'text', ) ); // Register Section C $wp_customize->add_section( 'theme_section_c', array( 'title' => 'Section C', 'priority' => 35, ) ); $wp_customize->add_setting( 'theme_option_c', array( 'type' => 'option', ) ); $wp_customize->add_control( 'theme_option_c', array( 'section' => 'theme_section_c', 'type' => 'text', ) ); } }}} '''Expected result:''' Sections show up in order A, B, C '''Actual result:''' Sections show up in order B, C, A Sorry if I'm doing something stupid, or if this isn't the intended functionality. I'm running trunk without any plugins." andyadams 21455 HiDPI (retina) theme custom backgrounds Otto42 Appearance normal normal Future Release feature request assigned 2012-08-02T17:07:06Z 2012-09-15T05:22:40Z "We should support HiDPI custom backgrounds. This will be a bit easier than custom headers, #21389, as we can do a media query in _custom_background_cb(). Worth noting that we will still need to solve some aspect of retina uploads, #21038." nacin 21389 Retina theme custom headers Otto42 Appearance normal normal Future Release feature request assigned 2012-07-25T19:40:56Z 2013-04-06T23:33:11Z We should support retina custom headers. Not sure how — ideas welcome. nacin 21785 Add header image uploads with cropping to the customizer Appearance 3.4 normal normal Future Release task (blessed) new early 2012-09-04T04:56:41Z 2013-05-22T10:06:20Z See #21355 for an explanation for why header image uploads (sans cropping) was removed from the 3.4 branch. This ticket is about adding it back, with a crop step, to ensure proper support. nacin 7361 Fixes for wp-app with PHP-CGI markjaquith AtomPub 2.9 normal normal Future Release defect (bug) assigned dev-feedback 2008-07-20T18:10:03Z 2012-10-17T18:10:44Z "I was trying to use Atom Publishing Protocol with my blog I a have found some quirks and bugs. My blog is hosted at Dreamhost, and, as far as I know, is using Apache 2.0.61 and PHP 5.2.6 as CGI. My first problem was, obviously, the authentication, but neither the solutions from [http://codex.wordpress.org/AtomPub the Codex] or [http://joseph.randomnetworks.com/archives/2007/09/19/http-basic-authentication-a-tale-of-atompub-wordpress-php-apache-cgi-and-ssltls/ this other blog post] worked. Reserching seems like PHP5 as CGI doesn't forward HTTP_AUTHORIZATION header, and nothing seems to change its mind. But it seems to forward REMOTE_USER as REDIRECT_REMOTE_USER. With my patch and this code in the .htaccess the authorization seems to work: {{{ RewriteCond %{HTTP:Authorization} !^$ RewriteRule wp-app.php wp-app.php [E=REMOTE_USER:%{HTTP:Authorization},QSA,L] }}} The other patch is to fix a bug in the wp-app.php code. It seems that when working with PHP as CGI, the ""Status:"" header needs to follow a specific format, with the number, and then the reason. The actual code (from Subversion, but it's there at least from version 2.5.1) do not send the number, making CGI/PHP/Apache to return with a ""500 Internal Server Error"" instead the ""401 Credentials Requiered"", confusing Atom clients. My other patch fixes this." yonosoytu 9513 Wordpress should allow input of XHTML/HTML via Atompub josephscott AtomPub normal normal Future Release enhancement new 2009-04-11T23:38:51Z 2011-03-14T09:50:06Z "One of the intended purposes of Atom standard was to allow better way of including XHTML in the feed than with “escaping it” (see this [http://www.xml.com/pub/a/2003/08/20/embedded.html article by Norman Walsh in xml.com] with followup at [http://norman.walsh.name/2003/06/30/hardline 1], [http://norman.walsh.name/2003/09/18/unescmarkup 2], and [http://norman.walsh.name/2003/09/16/escmarkup 3], there is also [http://www.intertwingly.net/blog/1571.html an interesting discussion under this blogpost] and [http://www.tbray.org/ongoing/When/200x/2003/06/28/Learning Tim Bray’s essay on the same theme]) Even though even [http://norman.walsh.name/2003/09/16/escmarkup#comment0006 Norm agrees that he lost this fight], at least Atom provides ''opportunity'' for conscious authors to use namespaced XML properly. Now, of course, the problem is that all this beauty is not supported by any known-to-me Atompub-accepting blog server. Particularly when this perfectly valid Atom 1.0 feed (take a look at [http://validator.w3.org/feed/#validate_by_input validator] if you don’t believe me): {{{ Late Night Thoughts on Listening to Mahler’s Ninth Symphony 2009-04-08T00:13:32+02:00 Matěj Cepl ceplm@seznam.cz http://matejcepltest.wordpress.com/ Copyright 2007 Matej Cepl John 3:17 or The Golden Middle Ground Between Grace and Sanctification? urn:mc:ceplovi.cz:atom1:blog:jan-3_17-2008-07-10 2008-07-13T00:00:00+02:00 John 3:17 or The Golden Middle Ground Between Grace and Sanctification? There is a couple of things, which make for me sense together (and I am not sure, of course, whether they will make sense to you as well), and which I would like to record here. “For God sent not his Son into the world to condemn the world; but that the world through him might be saved.” (J. 3:17) In some aspects and for some people (like me) and in certain moments, this is even more important than the previous verse, and yet it is quite rarely mentioned in the Church. Maybe because it so clear, that nobody gets much fame to explain (and there is not much to explain here?). For all of us, who live with the idea of God-policeman, following our doings to punish severely any small misstep, this is the good news. There is quite certainly something significantly wrong about preaching, that we always quote only (John 3:16) and we don’t continue one verse further. As if we are still more interested in what’s there in gospel for me, and we don’t understand, that we are not the central figures in whole Bible. Not that there wouldn’t be anything there for us, but … that’s another long discussion I would like to have with Dave. }}} is sent to Wordpress.com I get [http://matejcepltest.wordpress.com/2009/04/08/john-317-or-the-golden-middle-ground-between-grace-and-sanctification/ rather disasterous result]. According to [http://article.gmane.org/gmane.comp.web.wordpress.devel/27067 Peter Westwood] wordpress treats all content delivered by different modes of remote publishing as the same dummy plain text. OK, so the request of this ticket (and hopefully place of further discsussion if necessary) is to fix this and make considererd and delivered so that wordpress would just accept the nodetree inside of such element as a body of the blogpost without much further changes. Also #6128 might be caused by this." mcepl 15069 Autosave function assumes that there is only on tinyMCE on the page Autosave 3.0.1 normal normal Future Release defect (bug) new early 2010-10-08T10:28:12Z 2011-01-14T09:35:22Z "Autosave javascript assumes there is only one tinyMCE instance on the post editor page, thus breaking autosave feature under the next circumstances: 1. Content editor is in HTML mode 2. Some custom tinyMCE instances are added to the page by some plugin or theme. A patch that fixes that problem is attached." karevn 11049 Page Preview does not autosave page template nacin* Autosave 2.8.4 normal normal Future Release defect (bug) accepted dev-feedback 2009-10-30T21:19:34Z 2012-10-12T17:57:32Z When editing a published page, if you change the page template and then click Preview, the preview does not show the new template choice. janeforshort 4337 Blog by Email: No content is assumed westi* Blog by Email 2.2 high major Future Release defect (bug) accepted 2007-05-25T18:59:09Z 2013-02-05T03:14:40Z "It seems, the Blog by Email functions is broken in WP 2.2. Mails are recognized, but only the title/subject is assumed - no content. Content is empty :( No matter if text email or html email. {{{ Author = bla@example.org Content-type: text/plain, Content-Transfer-Encoding: 8bit, boundary: Raw content: Author: 1 Posted title: Test Posted content: Mission complete, message 1 deleted. }}} " jottlieb 4965 Blog by Email: any images and attachments in your email are not being posted inline westi Blog by Email 2.3 normal normal Future Release defect (bug) new 2007-09-12T18:15:29Z 2009-10-11T21:07:33Z "Blog by Email: any images and attachments in your email are not being posted inline Remaining issue from #4829." foolswisdom 5915 Same problem as in #252: apop broken if zero occurs in banner in 2.3.3 class-pop3.php westi* Blog by Email 2.3.3 normal normal Future Release defect (bug) accepted has-patch 2008-02-19T05:21:02Z 2009-10-11T21:08:22Z "While extracting the banner (function parse_banner) in preparation for apop, the empty method is called on $digit which when zero returns false and hence doesn't get put into the resultant $banner. Example parse_banner reply with <14649.123343777@code-werk.net> but the string was ""+OK ready <14649.1203343777@code-werk.net>"" or another example ""+OK ready <14649.1203343777@code-werk.net>"" and $pop3->parse_banner give back <14419.12334323@code-werk.net> then a md5($AuthString) must fail, because the 0 is significant by apop. I put a workaround at http://www.babsi.de/silentapop/, that does it for me, but this touch also wp-main.php " ASonno 5252 base64-encoded post-by-email post garbled. westi* Blog by Email 2.3 normal normal Future Release defect (bug) accepted 2007-10-24T08:58:20Z 2009-10-11T21:07:58Z "When posting-by-email, my cellphone submits code using ""content-transfer-encoding: base64"". The message appears (output from wp-mail.php) like so: Author = [my email] Content-type: text/plain, Content-Transfer-Encoding: base64, boundary: Raw content: SnVzdCB0ZXN0aW5nIHBvc3RpbmcgZnJvbSBteSBjZWxsLiBTdHJ1Y2sgbWUgd2hpbGUgcmVh ZGluZyAgUmFwaCBLb3N0ZXIncyBwb3N0cyBhYm91dCB0aGUgZmlyZXMgaW4gQ2FsIHRoYXQg YmVpbmcgYWJsZSB0byBwb3N0IHRvIHlvdXIgYmxvZyBmcm9tIGEgY2VsbHBob25lIGlzIGEg dXNlZnVsIGZlYXR1cmUuIA== Author: 1 Posted title: =?utf-8?B?Q2VsbHBob25lIHBvc3RpbmcgaW4gV1A=?= Posted content: SnVzdCB0ZXN0aW5nIHBvc3RpbmcgZnJvbSBteSBjZWxsLiBTdHJ1Y2sgbWUgd2hpbGUgcmVh ZGluZyAgUmFwaCBLb3N0ZXIncyBwb3N0cyBhYm91dCB0aGUgZmlyZXMgaW4gQ2FsIHRoYXQg YmVpbmcgYWJsZSB0byBwb3N0IHRvIHlvdXIgYmxvZyBmcm9tIGEgY2VsbHBob25lIGlzIGEg dXNlZnVsIGZlYXR1cmUuIA== Mission complete, message 1 deleted. The provided patch detects base64-encoded content transfers and base64_decodes them. For some reason (I'm no utf8-expert) the TITLE of the post has ""=?utf-8?B?"" prepended to the actual base64 content (see above), which means a check for this string + a cropping is needed or base64_decode will not decode the post title properly." kallewoof 16993 wp-mail.php doesn't account for half-hour and quarter-hour timezones. Blog by Email 3.1 normal trivial Future Release defect (bug) new has-patch 2011-03-29T06:55:06Z 2012-11-07T22:14:58Z "To reproduce the problem, install Wordpress and set it to post by email. Send a post from an email address which is configured to use a half-hour or quarter-hour timezone (like Afghanistan, +0430). wp-mail.php calculates the timezone by multiplying the timezone offset by 36. This works fine for whole-hour timezones (Pacific Time -0800, -800 * 36 = -28800 seconds). For half-hour and quarter-hour time zones this does not work (Afghanistan +0430, 430 * 36 = 15480, should be 16200). The reason this happens is because an hour has 60 minutes as opposed to 100 minutes. 430 / 100 = 4.3 hours, not 4.5 hours. 450 * 36 result in 16200 minutes, but timezones are represented as hours and minutes, not fractional hours. This results in posts that are posted via email from a half-hour or quarter-hour timezone to be posted in the future or in the past from when it was actually posted." neoscrib 24128 Twenty Eleven: add postMessage support for header_textcolor Bundled Theme normal normal Future Release enhancement new has-patch 2013-04-18T17:43:32Z 2013-04-23T16:53:14Z Similar to Twenty Twelve and Twenty Thirteen, this would add immediate visual feedback in the Theme Customizer UI when header text is hidden, or its color value changes. lancewillett 23834 Twenty Thirteen: add visual Indicator for menu items with children Bundled Theme trunk normal normal Future Release enhancement new 2013-03-21T04:07:43Z 2013-03-21T23:38:44Z "It's helpful to have a visual indicator when a top level menu item contains a hidden drop down menu. This patch adds a filter to wp_nav_menu_objects in order to add the class ""has-children"" to top level menu items that contain children. This allows us to style it with psuedo element, similar to how the menu-toggle is styled for smaller screens. The filter I used was posted by @chipbennet on the WordPress Theme Reviewers List. The same functionality could also be achieved by a Custom Nav Walker (see http://wptheming.com/2013/03/drop-down-menu-indicator/), but Chip's solution seemed more straightforward. Neither method works unless a menu has actually been set. " downstairsdev 23662 Twenty Twelve: style.css with Table of Contents Bundled Theme 3.5 normal normal Future Release enhancement reopened has-patch 2013-03-02T00:44:33Z 2013-03-15T18:08:49Z "Hello, I really like the 2013 initiative with Table of Contents, because it helps new users understand where goes what, especially developing child themes. I added Table of Contents to Twenty Twelve theme and renamed CSS comments titles accordingly." TomasM 23330 Allow autoloading all options, not just autoload = yes options Cache 3.5.1 normal normal Future Release defect (bug) new 2013-01-30T21:12:57Z 2013-02-21T04:26:41Z "For 5 years on wordpress.com we have ignored the autoload field for options. In wp_load_alloptions(), autoload = yes is not part of the query. Why? Because wordpress.com has a persistent cache. Thus, the transients that constitute the bulk of autoload = no options are stored in cache, never in the options table. Querying autoload=yes makes the query slower for no reason. Having autoload = no options also complicates notoptions caching. Core has a notoptions cache that would be unnecessary if you can assume that wp_load_alloptions() loads every option. If an option is not in alloptions, then it does not exist. Other large sites that use a persistent cache might also like to ignore the autoload flag. Core could automatically switch to ignoring autoload when an external object cache is being used, but administrators might want to control this so they can clean out old transients from options tables and do whatever other housekeeping is desired. So, let's add a filter that allows toggling this. When autoload is being ignored the wp_load_alloptions() query does not include autoload=yes and notoptions is not used." ryan 21267 Kill the serialization of $wp_filter in get_terms() Cache normal normal Future Release defect (bug) new has-patch 2012-07-13T21:35:11Z 2013-01-22T19:35:23Z "We use this as part of a persistent cache key: {{{ serialize($GLOBALS['wp_filter']['list_terms_exclusions']) }}} See [8225]. This is not good for two reasons. First, well, it's a not fun to reach into our internal API like that. But worse, it's broken whenever an object method is used, because spl_object_hash() will be unique to that object, thus rendering the cache invalidated on the next pageload. As an aside, we should probably have _wp_filter_build_unique_id() create a delimiter when dealing with a static class method — `$function[0].$function[1]` can conflict with a legitimate function name. I'm not sure how this should be fixed." nacin 22478 Remove $force argument from WP_Object_Cache::delete() Cache 3.4.2 normal normal Future Release defect (bug) new 2012-11-16T19:02:07Z 2012-11-16T19:02:07Z This was introduced way back in [3086] and hasn't been needed for years. ryan 11531 Some taxonomy names should be disallowed ryan Cache 2.9 normal normal Future Release defect (bug) new needs-unit-tests 2009-12-20T14:30:46Z 2013-05-16T15:05:44Z "I haven't tested, but can't we can get all sorts of weird bugs (some of which could have potential side effects in the security department) if a term taxonomy is called users, userlogins, posts, etc.? the reason are lines such as: {{{ wp_cache_add($term->term_id, $term, $term->taxonomy); }}} " Denis-de-Bernardy 14485 Taxonomy hierarchy cache isn't properly refreshed Cache 3.0 high normal Future Release defect (bug) new needs-unit-tests 2010-07-31T03:11:13Z 2013-04-30T20:46:25Z "I've developed a plugin that can create parent and children categories at the same time. It works well at 2.8.6 but it doesn't work as what I expect at 3.0. When I create new parent and children categories at the same time, it only shows parent category in the Categories dashboard, but the children category is actually created. If I create another category or delete one category, the children category shows up. I think it should be a problem of wordpress cache, but I have no idea where to start tracing. I use wp_create_category at wp-admin/includes/taxonomy.php to create categories. Besides, I have tried clean_term_cache but it didn't help. And I didn't activate other plugins when I tested this plugin. It happened exactly when creating NEW parent and children categories." thealien 22174 _get_non_cached_ids() should use wp_cache_get_multi(), if available. Cache 3.4.2 normal normal Future Release defect (bug) new 2012-10-12T14:12:40Z 2013-01-10T00:10:20Z Add wp_cache_get_multi() to all cache backends and conditionally use it in _get_non_cached_ids() so that post objects can be fetched from cache in parallel. ryan 22176 Cache the results of the posts_request_ids query Cache 3.4.2 normal normal Future Release enhancement new 2012-10-12T14:59:37Z 2013-01-10T00:11:47Z We are to the point where we could replace the advanced post cache plugin with something in core that is far simpler. We're most of the way there since introducing the split query. And with #22024 we have a good way of doing per-blog cache invalidation for classes of objects, which would be needed by this. Leveraging wp_cache_get_multi() as suggested in #22174 would provide a complete replacement for the adv post cache plugin. http://plugins.svn.wordpress.org/advanced-caching/trunk/advanced-caching.php ryan 20875 Introduce wp_cache_get_multi() Cache normal normal Future Release enhancement new has-patch 2012-06-07T13:56:28Z 2013-04-16T17:12:29Z "Both options (see #10274) and themes (see #20103) could benefit from a cache backend that implements get_multi(). For options, this means we can use individual keys. For both themes and options, we'd be able to make fast multiple gets. Both APC and Memcached (but not Memcache) implement multiple-get. A fallback would be looping over get(). Separately, as this would be a new function we use in core, we probably need to start doing some kind of versioning for drop-ins like db.php and object-cache.php." nacin 21401 Load packaged object cache when advanced-cache.php and object-cache.php don't implement wp_cache_init( ) Cache 3.0 normal normal Future Release enhancement new has-patch 2012-07-28T06:00:11Z 2013-05-14T13:22:25Z "'''This ticket has 3 purposes:''' 1) introduces {{{wp_using_ext_object_cache()}}} - mimic {{{wp_suspend_cache_invalidation()}}} and disallow direct access to {{{$_wp_using_ext_object_cache}}}, cleans up importing of globals in functions and provides function to modify that global[[BR]][[BR]] 2) load the wp-packaged object cache when {{{object-cache.php}}} doesn't implement {{{wp_cache_init()}}}[[BR]][[BR]] 3) adds file_exists for advanced-cache.php {{{wp_start_object_cache()}}}, at its core, is on the hunt for {{{wp_cache_init()}}} and then sets the toggle for the external object cache. We only care about the external object cache if it has that function. Rather than throwing a fatal error if their is a missing method, load the default object cache. If someone installs Memcached properly, then nothing changes - file loads, all is good. If they install a blanks file, the default Object Cache will load. If they install an external object cache without {{{wp_cache_init()}}}, the default cache loads. IMO - there is no reason to turn off non-persistent caching or throw a fatal error if the author of a cache plugin sucks or the user made a mistake in moving the files." wonderboymusic 15565 More context for clean_post_cache() Cache 3.1 normal normal Future Release enhancement new has-patch 2010-11-24T17:41:07Z 2012-10-17T14:21:18Z "I'd like more context to be available when the clean_post_cache hook is run. Scenario: I have a plugin caches the post_IDs of most post queries that go through WP_Query. Invalidating that cache is done via the clean_post_cache hook, but requires a bunch of fragile hacks to prevent cache invalidation for things like comment inserts, which update the post's comment_count (which could, in theory, affect a WP_Query, but that's another story). Option 1: Add extra actions to provide context. This is the simpler option. Patch 1 does this for the above scenario. Option 2: Add an optional context parameter to clean_post_cache(). This is more general, but I can't think of anyplace else WordPress uses as similar approach. Patch two." mdawaffe 21402 Remove PHP4 methods, format consistently Cache normal normal Future Release enhancement new has-patch 2012-07-28T06:24:33Z 2013-05-14T13:16:42Z "While I was looking around in cache.php, I noticed the TODO to remove the destructor that does nothing and the constructor that registers it to do nothing Also, the whitespace was different for almost every function - yet the functions all have similar code, this cleans it up" wonderboymusic 23327 Cache incrementors for get_bookmarks() Cache 3.5.1 normal normal Future Release task (blessed) new early 2013-01-30T18:24:08Z 2013-04-16T17:11:33Z "Make use of a caching incrementor and store queries in individual cache buckets to avoid memory exhaustion. Pattern this after #23167, which does the same thing for get_pages(). See #23173 for an explanation of the motivation behind this." ryan 23173 Don't cache arrays of query results in a single cache bucket Cache 3.5 normal normal Future Release task (blessed) new 2013-01-10T19:05:17Z 2013-04-16T17:10:11Z We have started using one cache bucket per query with passive invalidation controlled through a last_changed incrementor. See #22024 for an example. We also need to do this with get_pages(), wp_get_archives(), and elsewhere. On wordpress.com we have hacked some of these into separate buckets because saving multiple queries per cache bucket results in huge buckets. We have seen 72MB get_pages caches. Let's finally clean this up for good. Some of the last_changed work done for #22176 can be used here. ryan 15256 ?cat=## permalinks do not redirect when category is a parent Canonical 3.0.1 high normal Future Release defect (bug) reopened needs-unit-tests 2010-10-30T05:44:18Z 2013-02-25T13:08:53Z "One of my plugin users reported this while using dropdowns to display his categories: http://wordpress.org/support/topic/plugin-my-category-order-multiple-widget-support-broken I was able to duplicate it on my own site in 3.0.1. Any category that has children displayed in the dropdown will redirect to /?cat=## instead of the the friendly /category-name permalink when selected. Select any other category or one of the children and they redirect correctly. Any thoughts?" froman118 20388 ?cpage=N URLs do not have canonical redirection Canonical normal normal Future Release defect (bug) new 2012-04-07T05:43:02Z 2012-05-22T01:07:50Z ?cpage=N URLs aren't redirected to their pretty URL counterparts. They should be. markjaquith 17661 Appending date & author based query vars to a permalink overrides the permalink Canonical 3.1 normal normal Future Release defect (bug) new has-patch 2011-06-02T11:05:05Z 2012-09-09T20:14:26Z "Some canonical code branches are not properly accounting for extra query variables being specified via the url. For example, these url's are not handled properly: {{{ /2008/?author=1 redirects to /author/admin/ /author/admin/?year=2008 redirects to /year/2008/ /category/uncategorized/?year=2008 redirects to /2008/ }}} This happens with most date based branches, as once a higher priority canonical rule is hit, the permalink component is ignored. The canonical code includes a branch to add any ""forgotten"" `$_GET` variables back onto the url, however this doesn't help when it's the rewritten variables are being lost." dd32 14201 Canonical redirect kicks in in case of category/tag base containing other chars then a-z, 0-9, _ and - Canonical high major Future Release defect (bug) new 2010-07-05T09:03:39Z 2011-09-22T09:49:50Z "'''Expected behaviour''' Whatever the category base is, if we go to a properly formed category pretty permalink, canonical redirects shouldn't kick in. '''Actual behaviour''' If the category base is non-ASCII (for example: баба), the canonical redirect tries to redirect to the same URL. The redirect sanitizer removes the category base from the URL, because it is non-ASCII and redirects to {{{//category-name/}}}. This prevents endless redirects and usually results in 404. '''Why does it happen?''' Category base is always used verbatim. It can't be URL-encoded, because the percent signs will be interpreted as permalink variables. Because of that the generated urls will be always in the form: {{{/баба//}}}. The contents of {{{$_SERVER['REQUEST_URI']}}} are always URL-encoded, so the requested URI is: {{{/%D0%B1%D0%B0%D0%B1%D0%B0//}}}. Canonical redirect functionality assumes the requested URL would be the same as the generated term URL and since they are different tries to redirect. '''Solutions''' The easiest one is to assume that if we had come to the right category page without any get variables, we don't need the logic for redirecting to the canonical category page. This is valid statement, because that logic relies only on removing get arguments. The only disadvantage with that solution is that doesn't solve the more general problem of discrepancies between generated and requested URLs. But for now it will do a good job." nbachiyski 13041 Canonical redirection will redirect a non-exitant page to a post. markjaquith Canonical 3.0 normal normal Future Release defect (bug) new has-patch 2010-04-18T06:14:20Z 2010-11-13T07:53:23Z "Following on from #12601 Canonical redirection will kick in for http://localhost/wordpress-commit/apage/something and redirect it to http://localhost/wordpress-commit/2010/02/13/something-else/ #12601 limited redirect_guess_404_permalink() to only searching in the same post_type if one was provided, for posts and pages however, which are builtin, these vars are not set. I'm attaching a patch which will prevent a Page -> Post redirection, but not the other way around. - this patch was originally added to the other ticket." dd32 8593 HTTP_HOST being manipulated improperly for redirects markjaquith Canonical normal normal Future Release defect (bug) new has-patch 2008-12-12T16:37:23Z 2011-03-22T14:49:41Z "When redirecting a hit to the proper URL, WordPress makes some bad assumptions. Specifically, during redirects, any port information provided by the client is dropped. If I go to http://example.com:80/, I get redirected to http://example.com/. If I go to https://example.com:443/, I get redirected to https://example.com/. Thus far, no problem has occurred because we are on on server that uses default ports. However, lets say my web server is running http on 8080 and https on 8443. Now when I go to http://example.com:8080/ and get redirected to http://example.com/, it fails. As a workaround, you can change the following settings: WordPress address: http://example.com:8080/ Blog address: http://example.com:8080/ While this clears up the problem for http requests, you will not be able to use https becuse and attempt to go to https://example.com:8443/ now redirects to https://example.com:8080/ and it fails because the server does not speak ssl on 8080. Additionally, when you have an https proxy in front of your web server such as pound (with http on port 80 and https on port 8443), you run into another problem caused by this same bug. In this situation if you attempt to go to https://example.com/, the proxy server accepts the request and then on the back end makes a none ssl connection to apache. Good so far, but in order to not make any assumptions, the proxy server tells apache that the request was for 'https://example.com:443/' and apache sets HTTP_HOST (very appropriately) to example.com:443. WordPress sees this request and redirects it to 'https://example.com/' by responding to the web browser with a 'Location:' header. Thus the browser sends another request for 'https://example.com/' and starts the whole process over again resulting in an infinite redirect. As specifying a port is completely valid, this is a clear case of WordPress not handling things appropriately." revmj 16133 "Pagination issue with tag ""rss""" Canonical 3.0.4 normal normal Future Release defect (bug) new has-patch 2011-01-07T09:39:10Z 2012-09-04T21:50:34Z "When posts use ""RSS"" as a tag, and the /tag/rss/ page has more posts than it is set to display on one single page, the link to page 2: /tag/rss/page/2/ is redirected to: /category/page/2/ Tested on Paolo Belcastro test WordPress.org : http://test.belcastro.com/tag/rss/ Running 3.1-RC2-17229 with only Debug Bar plugin activated This is not theme related, same behaviour with TwentyTen or Thematic on this install." paolal 21700 Problem obtaining the Feed of an archive of tag “RSS” Canonical 3.4.1 normal normal Future Release defect (bug) new needs-unit-tests 2012-08-27T10:40:33Z 2013-05-24T16:15:58Z "I'm using RSS as a tag for some of my blog posts, and I was using them without any problem. '''myblog.com/tag/rss/''' But I've just realised that Google Webmaster Tools gives me some related errors. The issue is this: when trying to retrieve the feed of this tag, from '''myblog.com/tag/rss/feed/''' it gets redirected to '''myblog.com/tag/feed/''' And this gives an error." xavivars 20383 Strip trailing punctuation with canonical URLs Canonical normal normal Future Release defect (bug) new 2012-04-07T03:59:49Z 2012-07-13T00:47:29Z "A follow-up to #7537 where we removed %20 and "" "" from the end of URLs, we should try to remove all sorts of punctuation from the end of a URL, both URL-encoded and decoded. Example bad URLs we should surely be able to resolve: http://ma.tt/2012/03/productivity-per-square-inch/%7B http://ma.tt/2012/03/productivity-per-square-inch/) http://ma.tt/2012/03/productivity-per-square-inch/, http://ma.tt/2012/03/productivity-per-square-inch/! More difficult when there is no trailing slash in the permalink structure (or the link requested, regardless of permalink structure), but if is_404() is taken into account, it should be doable to trail various pieces of punctuation and see if we can get things to resolve." nacin 18734 Subcategory archive does work with any name as parent category in URL Canonical 3.0.1 normal normal Future Release defect (bug) new needs-unit-tests 2011-09-21T15:10:46Z 2012-10-22T23:10:00Z "Parent category is ''parentcategory'' and his sub category is ''subcategory''. The URL will be ''domain.com/category/parentcategory/subcategory''. The problem is, that you will get the same page if you use any words as ''parentcategory''. Examples: - ''domain.com/category/xxx/subcategory'' - ''domain.com/category/subcategory'' - ''domain.com/category/foo/bar/subcategory'' IMO {{{redirect_canonical}}} should do his work here (and sometimes it does). In 3.1 it does redirect. In 3.1.4 it doesn't redirect; after r17549. In 3.2.1 it doesn't redirect. Duck_ found that it does redirect before r18079. In current trunk it doesn't redirect. " ocean90 11856 URL for 1st comments page is not canonical markjaquith Canonical 3.0 normal major Future Release defect (bug) new reporter-feedback 2010-01-10T19:17:42Z 2011-12-22T01:55:08Z "When WP generates URL for comments, it always includes comments page number. It should not do this when URL is for 1st comments page - in this case post URL is sufficient. WP should also redirect to canonical URL version when someone will try to load URL like site.com/some-post/comment-page-1." sirzooro 10935 WP_Query and is_day() bug ryan Canonical 2.8.4 normal normal Future Release defect (bug) new commit 2009-10-09T05:05:24Z 2013-05-07T20:31:05Z "When you configure Wordpress with permalinks such as /%year%/%month% and even /%year%/%month%/%day/ there is a failure when you request URLs like /2009/10/58, because it's still generating the query to the database (AND YEAR(wp_posts.post_date)='2009' AND MONTH(wp_posts.post_date)='10' AND DAYOFMONTH(wp_posts.post_date)='58'). Also, is_day() returns true, when it should be returning false. As adding a post with that date is nearly impossible trough the wordpress admin or the database, no posts will be found, so Wordpress will show ""No page found"", but with HTTP status 200 OK, not 404 Not Found. I think it's important to validate the day on the applicacion side, so for some ideas to work correctly under WP (like take advantage of sticky posts and show all post for the month in day requests), and most importantly to save those wasted mysql queries. Of course I could validate the day using a filter, but that is not the general idea!" raliste 20386 "Year permalinks ""win"" against category permalinks" Canonical normal normal Future Release defect (bug) new 2012-04-07T05:20:55Z 2012-07-16T04:14:43Z "We need to decide whether category permalinks should take priority over year permalinks. e.g. /2008/?category_name=cat-a Should that stay the same, or redirect to: /category/cat-a/?year=2008 We have a unit test which is failing." markjaquith 19693 redirect_guess_404_permalink() can catch the wrong post types nacin Canonical normal normal Future Release defect (bug) reopened 2011-12-30T04:53:09Z 2012-05-24T16:19:12Z "When I access /blah, and that 404s, redirect_guess_404_permalink() will try to find a matching post name. If blah is the start of a post name for a random post type (perhaps one used as internal storage), it'll match it and redirect (and then end up 404ing, potentially). There's no constraint on the post type if the post_type query var isn't set, which is going to be common. We need to come up with a stricter query. (And while we're at it, we should hook redirect_guess_404_permalink() into redirect_canonical() so it may be unhooked without removing all canonical support.)" nacin 16557 Ability to disable redirect_guess_404_permalink() Canonical 3.1 normal minor Future Release enhancement new dev-feedback 2011-02-14T12:37:02Z 2011-04-08T11:29:36Z "Can you make redirect_guess_404_permalink() pluggable or have its return value pass-through a filter so that developers can override it? I know I can remove_filter('template_redirect', 'redirect_canonical') but redirect_canonical is too useful to be disabled. Only disabling URL guessing would be great. Thanks a lot, MK" msafi 12456 Canonical URL redirect issue with post_id/postname permalink structure dd32* Canonical 2.9.2 normal normal Future Release enhancement accepted has-patch 2010-03-02T14:06:38Z 2013-05-16T12:31:07Z "The issue: Using /%post_id%/%postname%/ as permalink structure, Most canonical redirects work fine, except: domain.com/post_id/ brings you to the post but does not redirect to the canonical domain.com/post_id/postname/ Additional info: The above permalink structure conforms to best practice as described in the codex: http://codex.wordpress.org/Using_Permalinks#Structure_Tags Therefore I figured this was a bug, given the attention given to redirecting to the canonical url ""So to avoid confusing search engines and to consolidate your rankings for your content, there should only be one URL for a resource."" http://markjaquith.wordpress.com/2007/09/25/wordpress-23-canonical-urls/ " Frank.Prendergast 14458 Create rel_canonical filter Canonical 3.0 normal normal Future Release enhancement new has-patch 2010-07-29T21:48:34Z 2011-05-06T14:18:54Z "Wouldn't it be nice to be able to set the canonical rel value. This comes in handy when you create a duplicate page and be able to manipulate the cannonical value. Usage: {{{ add_filter( 'rel_canonical', 'childtheme_rel_canonical', 10, 2 ); function childtheme_rel_canonical( $link, $id ) { return get_permalink( 55 ); } }}} " wjm 20496 Previews should redirect to the permalink if the post has been published Canonical normal normal Future Release enhancement new has-patch 2012-04-20T21:55:08Z 2013-05-21T20:00:47Z If a post is saved as a draft and you visit the preview URL, even after the post is published, you will stay on the preview view (with preview=true in the URL). This is confusing since you're not actually previewing anything, you're viewing a public post. evansolomon 4328 Redirect Old Slugs feature needs to redirect slugs for pages, not just posts, and redirect old permalink structure markjaquith Canonical 2.2 normal normal Future Release enhancement new has-patch 2007-05-24T01:52:44Z 2012-05-13T19:42:18Z "Create a page, browse to it, edit it, change its slug, WP redirects to the old page's slug and serves a 404. Wasn't WP 2.1 or WP 2.2 supposed to make the redirect old slug feature built-in? Along the same lines, it would be sweet if instead of simply redirect old slugs, WP would redirect old urls. When the date changes, when the page parent changes, or when the permalink structure changes, the url changes but neither of WP, the redirect old slug plugin, the permalink redirect plugin, or anything else catches this." Denis-de-Bernardy 15950 Tweak canonical redirect name requests Canonical 3.1 normal normal Future Release enhancement new has-patch 2010-12-22T18:09:54Z 2010-12-22T22:28:38Z "Scenario: A website has the following two pages: * `example.com/foo/amazing-thing/` * `example.com/amazing/` Upon requesting `example.com/amazin` the canonical redirect should favour the top-most level page. This doesn't happen as the relevant SQL query doesn't have an `ORDER BY` clause, making the behaviour unpredictable." johnbillion 15397 redirect_guess_404_permalink() purposedly doesn't guess posts with updated dates Canonical lowest normal Future Release enhancement new dev-feedback 2010-11-12T00:17:38Z 2012-07-03T15:37:18Z "'''Problem''' Here's my post path scheme: http://site.com/YEAR/MONTH/DAY/SLUG. Whenever I have writers working on a post for a while and saving drafts (we're all using Windows Live Writer), they oftentimes publish to the date when the last draft was saved, i.e. several days in the past. Then, they quickly correct the date but the previously tweeted/shared link is now 404 due to the changed date. I've looked into the source of redirect_guess_404_permalink(), and it purposedly narrows down the query when it sees a post date to that date only. If I understand correctly, this is done to minimize accidental redirects to the wrong post, but has the side effect of not guessing the new link if only the date was changed. A workaround of removing these lines: {{{ if ( get_query_var('year') ) $where .= $wpdb->prepare("" AND YEAR(post_date) = %d"", get_query_var('year')); if ( get_query_var('monthnum') ) $where .= $wpdb->prepare("" AND MONTH(post_date) = %d"", get_query_var('monthnum')); if ( get_query_var('day') ) $where .= $wpdb->prepare("" AND DAYOFMONTH(post_date) = %d"", get_query_var('day')); }}} fixes the problem for me. Can this case be solved in the trunk and the code above removed, or logic improved? My .htaccess file is filled with 301 redirects to correct wrong dates. Thank you." archon810 10543 Incorrect (non-UTF-8) character handling in tag's name and slug westi* Charset 2.8.2 normal normal Future Release defect (bug) accepted needs-unit-tests 2009-08-04T05:26:11Z 2010-11-13T01:15:40Z "Incorrect (non-UTF-8) character tag's name and slug are handled in different way: name is truncated on 1st such character, and in slug they are just removed (no truncation). WP should handle both in the same way - drop invalid characters, instead of truncation. I found this issue recently. One of the Polish programs for adding posts to the Wordpresses does not encode tags in UTF-8 - it left them in ISO-8859-2. I notified author of this bug. Unfortunately there are many copies around, so it may take a long time before everyone upgrade." sirzooro 5998 Invalid Unicode characters hakre Charset 2.3.3 normal major Future Release defect (bug) assigned 2008-02-25T18:17:22Z 2011-02-10T23:09:25Z "Wordpress does not check for invalid Unicode characters, such as the following: U+FFFE U+FFFF When the pages are served up as XHTML, allowing these characters through generates an XML error. WordPress should filter out illegal Unicode code points. Please see http://www.w3.org/TR/REC-xml/#NT-Char Also, the regex [http://www.w3.org/International/questions/qa-forms-utf-8 here] is incorrect, see [http://intertwingly.net/blog/2008/01/02/Keeping-On-Your-Toes this page]. " shelleyp 18007 is_serialized trouble for multibytes encoding Charset 3.2 normal normal Future Release defect (bug) new has-patch 2011-07-06T16:51:52Z 2013-04-10T12:47:42Z "Possible bug in the ''is_serialized'' function, in a multibytes environment : == Context == * ''utf-8'' encoded database fields * auto overlaoding singlebyte functions from conf (see http://www.php.net/manual/en/mbstring.overload.php) Retrieving an option from the database, the ''get_option'' function try to deserialize it. == Bug scenario == * the ''strlen'' call is actually a ''mb_strlen'' one * the ''$length'' var is the number of characters (not bytes) * using {{{ $data[$length-1] }}} don't retrieve the last char but one before, it's actual position is undefined, depending on the other content of the string * this ''$lastc'' is not '';'' or ''}'' * the string is understood has not serialized == Patch proposal == here is a fix i made to make it work with multibytes string : Not tested it for single bytes, but there is no reason for it to not work. {{{ --- a/wp-includes/functions.php +++ b/wp-includes/functions.php @@ -256,7 +256,7 @@ function is_serialized( $data ) { return false; if ( ':' !== $data[1] ) return false; - $lastc = $data[$length-1]; + $lastc = substr($data, -1); if ( ';' !== $lastc && '}' !== $lastc ) return false; $token = $data[0]; }}} " challet 11738 sanitize_text_field() issue with UTF-8 characters hakre Charset 2.9.1 normal normal Future Release defect (bug) new 2010-01-06T07:39:11Z 2010-11-13T07:36:00Z "See Description #11528 Suggested patch does not take UTF-8 properly into account. Function has been degraded in the commit(s) [12499], [12501] to not support shift-spaces any longer. Details about preg_replace and UTF-8 as well as a proper suggestion to fix w/o degration [https://core.trac.wordpress.org/ticket/11528#comment:10 here]." hakre 11175 wp_check_invalid_utf8() should drop invalid utf-8 chars only instead of truncating string hakre Charset 2.9 normal normal Future Release defect (bug) new needs-unit-tests 2009-11-18T19:18:43Z 2011-07-13T09:46:51Z "When you call wp_check_invalid_utf8() with 2nd param set to true, it tries to strip invalid utf-8. Now it removes 1st invalid utf-8 char and all chars after it, no matter if they are correct or not. Additionally it can print following notice: Notice: iconv() [function.iconv]: Detected an illegal character in input string in .../wp-includes/formatting.php on line 437 Attached patch changes this, so function removes invalid chars only. Additionally it is less configuration-dependent, because it can use either mb_convert_encoding() or iconv()." sirzooro 16134 Check capabilities/role before adding comment links to email Comments 3.0.4 normal normal Future Release defect (bug) new has-patch 2011-01-07T10:23:06Z 2011-02-19T20:35:22Z "Currently the Trash it, Delete it, Spam it are added to comment notifcation emails, which are sent to the author. However, the author may have had their role changed down to a lower-role (or had capability removed) since they wrote the post, and no longer would have permissions to use the links added to the email. It may also be the case that a subscriber user was assigned as the Post Author (perhaps as a sort of Guest Author) for a post, and never had the permissions to use those links. Can some sort of check be added, before these links be added to the email?" GaryJ 10377 Comment fields should have max lengths Comments 2.8 normal normal Future Release defect (bug) new 2009-07-10T14:34:27Z 2012-07-13T01:05:25Z "Hello, I don't know if exactly it's a bug or use javascript validation, but i think so there's no treatment for this, or was fix in the new version. In the section of comments(Wordpress 2.8), we can insert how many characheters we wants, generating an SQL Exception and breaking the all system. The solution is simple, use the property maxlenght in the tag e limit the characters if will be send to database. " muriloazevedo 12363 Comment permalink wrong when only listing one comment type Comments 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-02-24T14:31:51Z 2010-11-13T07:46:50Z "If you pass the `type` parameter to `wp_list_comments()` (for example, to show comments only and no pings), then comment permalinks can easily use the wrong page number as they expect there to be pings included. This is apparent after leaving a comment and WordPress attempts to redirect back to your new comment. At first I was thinking you could tell WordPress that you're filtering to a type and it could compensate when determining the page number, but then I realized perhaps it'd just be better for `wp_list_comments()` to check if there were 0 comments returned for the query and if so, see if there are any of that type of comment available. If so, then we know we're on too high of a page number and can instead display the highest existing page. Then again this introduces SEO issues. Ideas on what to do are welcome." Viper007Bond 8973 Function get_page_of_comment() returns incorrect page numbers Comments 2.7 normal normal Future Release defect (bug) reopened dev-feedback 2009-01-27T16:54:40Z 2012-06-17T22:37:09Z "The function get_page_of_comment(), defined in /wp-includes/comment.php for WordPress 2.7, returns wildly incorrect results in cases where the database includes spam trackbacks or pingbacks. The reason is that the DB query on line 595 does not include ""comment_approved = 1"" and therefore incorrectly counts unapproved trackback and pingback spam (not to mention non-spam comments in moderation). As far as I can tell from browsing my DB, although spam comments have their comment_type changed to 'spam' in the database, trackbacks and pingbacks still retain their original comment_type. As a newbie to the WordPress Trac, I'm afraid I don't know how to provide a diff, but the full correct query is as follows: $oldercoms = $wpdb->get_var( $wpdb->prepare( ""SELECT COUNT(comment_ID) FROM $wpdb->comments WHERE comment_approved = 1 AND comment_post_ID = %d AND comment_parent = 0 AND comment_date_gmt < '%s'"" . $comtypewhere, $comment->comment_post_ID, $comment->comment_date_gmt ) ); The upshot is that without the above fix, comment URLs in several places (e.g., RSS feeds) may point to non-existent pages. All the best, Greg " GregMulhauser 14711 Indexes for comment_author_email and user_id Comments 3.0 normal normal Future Release defect (bug) new early 2010-08-27T07:18:30Z 2011-01-08T19:36:17Z "There are currently no indexes on any of the author columns in wp_comments. That means there's no efficient way to count the comments written by a given commenter, for example. The enclosed patch adds two separate non-unique indexes, one each for comment_author_email and user_id. " tellyworth 13792 Invalid reply link from comment admin when comment nested level > max Comments 2.9.2 normal normal Future Release defect (bug) reopened 2010-06-09T07:05:56Z 2010-11-13T17:53:57Z "I have a blog with nested comments enabled, max depth of 4. When the last level comment is posted, it no longer contains a Reply link. However, in the Comment admin, the Reply link is still present. If used, this new reply will show up at the very bottom of the comment list once posted (even if other newer regular comments are entered, this new reply will still show up at the very bottom). The bug is, basically, that Comment admin doesn't respect the max nested value." archon810 12480 Moderated comments don't show blank links Comments 3.0 normal normal Future Release defect (bug) new has-patch 2010-03-02T18:29:09Z 2010-11-13T07:48:54Z "Comments caught in moderation won't show the blank links inserted into them unless you edit them. A comment with html code like will not show that link on the moderation page." donncha 10790 "No feedback given to commenter when ""Name"" field empty" Comments 2.8.4 normal normal Future Release defect (bug) new dev-feedback 2009-09-15T17:43:44Z 2011-01-21T05:44:40Z "On my installation, name and email are not required to post a comment. I must approve every comment before it appears. If a user chooses to give their name anyway, then after they post their comment, they get a screen that says ""Blah says:"" and below that ""Your comment is awaiting moderation."" This is expected behavior. However, if the user does not give their name, then they do not get any sort of confirmation that their comment was sent. It is sent successfully, but the user should have confirmation, otherwise they will likely try more than once before giving up in frustration. I have tested this bug using Firefox 3.0, with and without JS enabled, and Internet Explorer 6." WK1 11286 Normal User Input Causes Status 500 Comments 2.8.4 normal normal Future Release defect (bug) new commit 2009-11-30T21:45:04Z 2012-11-26T22:20:40Z "To reproduce: Click the Submit Comment button on any post with no other input. Expected Result: Status 200 or 403 with feedback to user. Actual Result: Status 500 with feedback to user. Status 500 means the server is at fault for an unexpected error condition, which is not the case here. It is the incorrect response to send, and it is alarming to see it show up in a server log without an error message. Patch should be ready shortly..." miqrogroove 11248 Paged wp_list_comments() should always output something Comments 2.9 normal normal Future Release defect (bug) new has-patch 2009-11-24T06:00:23Z 2010-03-13T22:04:21Z "Enable comment paging on your blog and visit `http://yourblog.com/a/single/post/comment-page-999999/`. Note no comments will be displayed. There's situations where the comment form will redirect you back to the wrong page (for example if you mess with the type parameter and exclude pings). The Walker should detect if there's no comments to be displayed on the requested page and if that's the case, then display the latest page that actually has comments." Viper007Bond 13648 Post link? ryan Comments 3.0 normal normal Future Release defect (bug) new 2010-05-30T22:51:23Z 2010-05-31T20:50:17Z Adding '''?comments_popup=1''' to the url go to that post id number but in comment view with the trackback to the post with the regular permalink. Found this via search engine that indexed it instead of post url. giuseppex 22261 Recent comments widget makes additional queries when pagination is enabled Comments normal normal Future Release defect (bug) new 2012-10-23T14:19:59Z 2012-10-23T14:19:59Z A continuation of #15400. nacin 16881 Remove all unwanted 'nofollow' attributes from 'reply to comment' links Comments 3.1 normal minor Future Release defect (bug) new commit 2011-03-17T20:27:43Z 2011-03-19T06:47:58Z "This should be a trivial fix. r16230 removed the rel=""nofollow"" attribute from ""reply to comment"" links in the comments list, for reasons discussed in #10550. In brief, the reasons are that these are not external links that we want to tell search engines not to follow in the first place, and there is actually an SEO penalty from adding the ""nofollow"" to internal links. Unfortunately, the ""nofollow"" was not removed from all of the ""reply to comment"" and ""reply to post"" links (for instance, in code branches when the site requires login/registration to comment). This patch corrects the rest of them. It doesn't delete the ""nofollow"" attributes we want. For instance, in `get_comment_author_link()` which escapes links to the comment author's URL. Additionally, the patch (see line 1110) fixes a minor inconsistency between the return values of `get_comment_reply_link()` and `get_post_reply_link()` when `get_option('comment_registration')` is TRUE. The version in `get_post_reply_link()` is missing the `class=""comment-reply-login""` and `esc_url()` wrap. I've added them." joelhardi 8755 Should be able to specify page order with wp_list_comments() Comments 2.7 normal major Future Release defect (bug) new 2008-12-30T02:50:53Z 2009-11-17T15:48:45Z "Passing the parameters ''reverse_top_level'' and ''reverse_children'' into the ''wp_list_comments()'' function only reverses the order of the comments '''on each page''', and not the entire comment list overall. It is therefore impossible to display the newest comments first using this function, when comments are great enough to be paged. At least, not without globally changing the comment order for the entire site using the Discussion settings screen so that the ""last"" page is displayed first. It should be possible to specify the page order in wp_list_comments() by, for example, passing a page_order parameter with 'asc' or 'desc' available." marky 15905 Using wp_list_comments using both the type and callback arguments causes the first comment to be repeated Comments normal normal Future Release defect (bug) new close 2010-12-20T03:12:18Z 2011-01-27T07:01:44Z "I'm using wp_list_comments like so: {{{ }}} When including the comments on a page listing many posts (like the home index page), the callback function is always passed the first comment that is encountered. Trying get_comments before wp_list_comments shows the proper comments that should be displayed, but the callback always receives the same comment as it's argument. Removing '&type=comment' yields the expected output. My current workaround is to remove '&type=comment' and only respond to comments with an empty string for the comment_type in my comment callback function. " benschell 15644 When deleting a user, corresponding comment user IDs aren't reset Comments lowest minor Future Release defect (bug) new dev-feedback 2010-12-02T11:19:18Z 2012-08-04T09:55:22Z "Delete a user with a comment. The user ID stays. Potential for clashes later. We should run this: `$wpdb->update( $wpdb->comments, array( 'user_id' => 0 ), array( 'user_id' => $user_id ) );` in wp_delete_user. Alternative is to do a full query then manually run wp_insert_comment() on each, so all hooks get fired, which is fine too and is more in line with what we do elsewhere." nacin 11566 clean_comment_cache() does not clean $GLOBALS['comment'] Comments 2.9 normal normal Future Release defect (bug) new has-patch 2009-12-22T21:18:23Z 2011-04-28T22:55:15Z "I am trying to add links to comment list, which will allow to delete comments directly without need to move them to trash first (and with trash enabled). For posts/pages I found working workaround: hook `trashed_post` and `call wp_delete_post()` again from. Unfortunately similar approach for comments does work. As I checked, `wp_trash_comment()` calls `get_comment()`. The latter function implements simple comments cache using `$GLOBALS['comment']`. When you change comment status to `trash`, `wp_set_comment_status()` clears cache by calling `clean_comment_cache()`, but it leaves that global set. As a result my workaround does not work. I think that `clean_comment_cache()` should clear that global too." sirzooro 13473 comment_status should be set to default_comment_status when commentstatusdiv is removed westi Comments normal normal Future Release defect (bug) reopened 2010-05-20T23:36:24Z 2011-11-24T16:13:29Z "When the Comment Status box is removed from the Add/Edit Post screens, posts should be created with the comment_status set to the value of the default_comment_status option. ----- I had hidden the Comment Status box via: remove_meta_box('commentstatusdiv','post','normal'); and made sure that default_comment_status was set to open: update_option('default_comment_status', 'open'); After adding a new post it displayed ""Comments Off"" when I was assuming that it should have honored the value of default_comment_status." jimmcq 4916 comment_type function doesn't return the comment type string Comments 2.3 normal normal Future Release defect (bug) assigned 2007-09-06T07:41:30Z 2012-03-12T11:37:16Z The comment_type function in comment-template.php only echoes string that explain the comment type. Sometimes we need the string to be returned instead of echoed, e.g. for i18n purposes. hudatoriq 14809 comments_by_type doesn't always get reset Comments 3.0.1 normal minor Future Release defect (bug) new reporter-feedback 2010-09-08T01:18:20Z 2011-07-09T17:40:40Z "in wp-includes/comment-template.php , in function comments_template(), it is possible for $wp_query->comments to be set but for $wp_query->comments_by_type NOT to get reset when it should be reset to array(). We ran into a bug because:[[BR]] - on a single page (actually inside of a widget), we were pulling comments from multiple posts[[BR]] - for each post, we were requesting get_comments(array('type' => 'comment'))[[BR]] - in wp-includes/comment-template.php , in function wp_list_comments(), code says: {{{ if ( 'all' != $r['type'] ) { if ( empty($wp_query->comments_by_type) ) $wp_query->comments_by_type = &separate_comments($wp_query->comments); if ( empty($wp_query->comments_by_type[$r['type']]) ) return; $_comments = $wp_query->comments_by_type[$r['type']]; }}} unfortunately, since we were running that again and again, it would not recalculate $wp_query->comments_by_type each time. I think that the function comments_template() in wp-includes/comment-template.php should have the following line added: {{{ $wp_query->comments_by_type = array(); }}} right after the line where $wp_query->comments is set." nmassey 13091 edit_post action on wp_update_comment_count_now should not be fired if the comment count hasn't changed Comments 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-04-23T06:43:15Z 2010-10-02T00:13:54Z "wp_update_comment_count_now() is called whenever a comment status is transitioned (or a comment is deleted). However, if the comment transition is not from/to the 'approved' status (e.g., if the comment is transitioned from 'spam' to 'trash' or from 'unapproved' to 'trash'), then the associated post is not actually affected. Therefore in such cases the edit_post action shouldn't be fired, because the post has not been edited/modified in any way. I would argue that the 'wp_update_comment_count' action also should not be fired. One solution is to check whether the comment count has changed before firing the action. Another possible option is to call wp_update_comment_count only when a comment has transitioned in/out of the ""approved"" status. I'm inclined to prefer the former because it involves less change. Proposed patch to follow." solarissmoke 16010 get_comments() returns as result (by default) comments that were not approved. Comments 3.0.3 normal normal Future Release defect (bug) new 2010-12-28T16:41:11Z 2011-01-13T04:00:49Z "I see two problems in behavior of ""get_comments()"" function (wp-includes/comments.php: 180). 1. The function returns as result (by default) comments that were approved and also comments that were not approved. I think that this does not fit the standard of all functions in WP that by default return only posts/comments that have been published/approved. 2. I think that there is no support of cookies of current responder. In other words, a parameter that allows the following functionality does not exist. comment_approved = '1 'OR (comment_author =% s AND comment_author_email =% s AND comment_approved = '0') ( wp-includes/comments-template.php: 852)" mati1000 13939 get_page_of_comment returns wrong page number when changing threading level Comments 3.0 normal normal Future Release defect (bug) new has-patch 2010-06-17T07:58:01Z 2010-11-13T10:04:51Z "Initial discussion settings: * Enable threaded comments 2 levels deep * 5 top-level comments per page, first page by default * Older comments at top of each page If I have comments on a post like: '''cpage 1''' * comment-1 * comment-2 * comment-3 * comment-4 * comment-5 * comment-6 {{{ $page = get_page_of_comment(6); // returns 1 which is the correct page }}} If I modify the initial discussion settings by disabling threading (e.g. changing the threading level to 1), the comments change to: '''cpage 1''' * comment-1 * comment-2 * comment-3 * comment-4 * comment-5 '''cpage 2''' * comment-6 {{{ $page = get_page_of_comment(6); // returns 1 which is incorrect }}} This function doesn't follow the same algorithm as what is used to display the comments This can potentially happen whenever you decrease the threading level from x to x-n" laceous 14279 wp_new_comment ignores comment_date_gmt and comment_date Comments 3.0 normal normal Future Release defect (bug) new has-patch 2010-07-12T14:07:06Z 2011-01-27T08:08:52Z "wp_new_comment takes in a $comment array, but then ignores the comment_date and comment_date_gmt passed into it, instead replacing them with the current time. It should only set them if the data passed in is empty or not a date/time. " johneckman 9959 wp_rel_nofollow_callback adds too many rel/nofollow attributes junsuijin* Comments 2.8 low minor Future Release defect (bug) accepted has-patch 2009-05-28T13:54:35Z 2011-04-13T20:57:31Z "if you insert a link in a comment, like: {{{ }}} wp_rel_nofollow_callback() turns that into: {{{ }}} Here's a correct implementation of a strip_nofollow() function: http://plugins.trac.wordpress.org/browser/sem-dofollow/trunk/sem-dofollow.php We'd probably want to do the same in WP, and then reverse it: add rel=nofollow if no rel is present, and add a nofollow to the rel if it's not in there already." Denis-de-Bernardy 11334 Add caching to get_page_of_comment() Comments 2.9 high major Future Release enhancement new has-patch 2009-12-05T07:33:50Z 2013-02-05T05:10:21Z "Ack. `get_page_of_comment()` lacks caching which means if you call `get_comment_link()` for the same comment ID on the same page multiple times (and outside of the loop), it will query multiple times. You also can't cache the result between page loads (the big ""uh oh""). Attached patch introduces a cache that stores comment ID => older comment count (in short, the result of the function's query) on a per-post basis. When any comment's status is changed, the entire cache for that comment's parent post is deleted as it will likely affect other comments (for example, deleting a comment can change the page of newer comments). I opted to make a new cache flag (group), but I'm not sure if using an existing one would be better or not. Oh, and this patch needs through testing and/or a good review." Viper007Bond 761 Add hook to conditionally disable comment notifications [w/ patch] matt Comments 1.2.2 normal normal Future Release enhancement reopened has-patch 2005-01-27T07:42:58Z 2012-11-07T07:56:15Z E-mail notifications for posted comments are controlled by the 'comments_notify' setting. E-mail notifications for comments needing modification are controlled by the 'moderation_notify' setting. Each is an all or nothing setting, i.e. if 'on', ALL post authors will receive notifications when appropriate. AFAIK, there isn't a clean way for a plugin to insert itself into the notification process. coffee2code 10569 Allow filtering of reply text with comment context Comments normal normal Future Release enhancement new has-patch 2009-08-08T13:55:54Z 2011-02-01T16:30:36Z "I know you can specify the reply text for comments, but you can't make them specific to each comment such as ""`Reply to comment #1234 by Joe`"". This will let you do that by adding a filter called `comment_reply_link_text` to `get_comment_reply_link()` that passes along $args, $comment, and $post (just like the existing `comment_reply_link` filter). I know you COULD do this with some processing on the link, but it would require pulling comment and post IDs from the URL and/or onclick, then replacing the text in the link itself. This way would be a lot simpler and only adds a single filter." aaroncampbell 12991 Allow setting default_comment_status specifically for Pages (or for any post type) messenlehner Comments 3.0 normal normal Future Release enhancement assigned has-patch 2010-04-13T22:52:28Z 2012-11-25T01:22:22Z "Now that the default theme has {{{comments_template}}} in Pages too, I have been thinking that maybe we should offer a way of setting {{{default_comment_status}}} specifically for Pages (as distinguished from Posts). Why? Say that I select Twenty Ten as my theme. I leave the global option for comments ON, because, like most people, I want comments on my Posts. However, like most people, I do not want comments on Pages, or I want comments only on a few selected Pages. So, every time I make a new Page, I have to untick the checkbox on the Edit screen, in order to override the global setting. That’s not convenient! I think we need to do something about that: Either we leave Twenty Ten as is and change something at the level of post type registration, or we change something in Twenty Ten. (I have no idea what would be a satisfactory way to deal with this at the theme level. Sandbox, for instance, displayed the form on Pages only if there was a certain custom field with a certain value, which may seem very unfriendly at first sight, but I find it is much friendlier than what we have now in Twenty Ten.)" demetris 15520 Break date/time into a separate column in Comments views Comments normal normal Future Release enhancement new needs-refresh 2010-11-20T15:30:35Z 2012-03-08T10:18:38Z "Now that column sorting is in, it makes sense to break the date and time a comment was made into a separate column in the Comments view so they can be sorted chronologically. Currently, the time is part of the content column, which can be confusing as if someone sorts by that column it becomes an alphabetical sort." markel 20487 Comment search isn't customizable Comments 3.2.1 normal normal Future Release enhancement new has-patch 2012-04-18T23:32:07Z 2012-07-12T16:05:07Z "*cross-posted to the wp-hackers mailing list last night* I work on a large news oriented WP site and first off, it actually scales remarkably well. We keep users, comments, and actual posts all in WordPress. However, due to our size, administering comments is causing us issues at the moment. Our last outage was caused by one of our comment moderators doing a simple comment search in the admin. The query took 16 seconds to execute, the next query locked, and, with our traffic, the DB couldn't handle the resulting queued traffic. Staying away from discussions of ""you should use Disqus"" or, ""you need more X for your mysql server,"" I think there is significant opportunity to improve the way WP handles comment searching. Every comment search takes the following form: SELECT * FROM wp_comments WHERE ( comment_approved = '0' OR comment_approved = '1' ) AND (comment_author LIKE '%TERM%' OR comment_author_email LIKE '%TERM%' OR comment_author_url LIKE '%TERM%' OR comment_author_IP LIKE '%TERM%' OR comment_content LIKE '%TERM%') ORDER BY comment_date_gmt DESC LIMIT #; As we can all see, this is a beast of a query. Even when the term is clearly an specific term (say an email or IP), or when the intent of the admin is known (e.g. clicking the IP link on a specific comment). Furthermore, there are no hooks activated in this process for plugins to use to say create an advanced comment search plugin. One might expect hooks like those activated in post search to be activated here, like ""parse_request"" and ""get_search_query."" Waxing philosophical, as posts, comments, and users are the three basic types of data to be stored and displayed in WP, one would expect them to have similar interfaces and functionality. They each have basic functionality of being able to retrieve a single item, a list (in full or in part), search for an element, or edit a single entry. For this reason I don't understand why each of their functionality isn't derived from something like an abstract class or an interface. The architecture here is also difficult in that you are not able to replace or extend a single class to change the functionality. Back on target. I propose that we add functionality by which we'll be able to search by exact match in addition to the existing full wildcard (left, right, or full wildcard is probably excessive) as well as specifying the field to search. This would allow my earlier use case of searching by IP to look for an exact match in the ""comment_author_IP"" field only, not searching the fulltext of every comment. This functionality can be created simply by: 1. Adding ""search_type"" and ""search_field"" to the WP_Comment_Query::query_vars data structure in wp_includes/comment.php 2. Replacing WP_Comment_Query::get_search_sql with something more robust, able to understand these new properties and construct the query on their basis 3. Upgrading WP_Comments_List_Table::prepare_items to accept the new queries and add them to the data structure it creates 4. Either modifying WP_List_Table::search_box to have some options of advanced search, or dropping a hook so that a plugin can easily modify it 5. Modifying the WP_Comments_List_Table::column_author to supply the correct query string to indicate an IP search If I can figure out a way to make this more similar to the signature of posts and users, or at least add some hooks at the right places, I can do that as well. This will add efficiency for everyone--particularly those who have lots of comments. I modified our core for this functionality today and we will fully QA it tomorrow. I made it on 3.2.1 as that is what we're running right now, and there are minimal changes in the affected files and functions between 3.2.1 and 3.3.1 and even the nightly. I can submit a patch as long as it passes our QA--how should I do that, off the nightly? Thanks, -Kenton Jacobsen" brokentone 16365 Comment transition for new comments Comments 3.1 normal minor Future Release enhancement new dev-feedback 2011-01-24T21:07:46Z 2012-05-28T12:39:19Z "As far as I can tell wp_transitions_comment_status() does not get called for new 'comments' based on my testing and review of comment.php in wp-includes. There is a similar transition for posts that gets called for new 'posts' including hooks like 'new_to_publish' and 'new_to_private'. I feel that there should be a similar hook to this form comments so that plugins can hook into new comments differently from comments moved from one existing status to another (like comment_unapproved_to_approved'." MattyRob 15015 Customisable submit button for comment form Comments 3.0.1 normal normal Future Release enhancement new dev-feedback 2010-10-02T16:38:10Z 2012-12-16T00:07:37Z "Note: I'm setting this as a blocker because it is a blocker '''to me'''. Set it whatever you feel appropriate. I badly needed to customise the submit button because I wanted to add a tabindex. I could reimplement the whole form with my markup, but as I already worked my way through all the other fields, I did want to continue this way. Sadly I discovered it's not possible. So, after discussing this in IRC, I decided to hack the core and propose the attached patch. Basically now you can create a filter and output your markup, like this: {{{ function awesome_comment_form_submit_button($button) { $button = '' . get_comment_id_fields(); return $button; } add_filter('comment_form_submit_button', 'awesome_comment_form_submit_button'); }}} and filter magic happens. Please notice that 1. you have to include [args:id_submit] and [args:label_submit] if you want the comment_form() parameters to work. 2. you have to use the get_comment_id_fields() function. It may be better but it works for me. If anybody feels like making it better, be my guest." morpheu5 7051 Delete blacklisted comments rather than mark them as spam Comments 2.5.1 normal normal Future Release enhancement new has-patch 2008-05-28T11:37:11Z 2011-02-08T04:10:40Z Comments that are blacklisted because of the Blacklist keys on options-discussion.php should be deleted immediately instead of being marked as spam. Patch attached. donncha 12521 Disable Site Wide Discussions - Admin Settings Comments 3.0 normal normal Future Release enhancement new 2010-03-05T01:44:26Z 2011-08-27T08:42:14Z In the admin discussions options there should be an option to completely disable discussions site wide. ceenz 11359 Don't nofollow links in admin comments Comments 2.9 normal normal Future Release enhancement new 2009-12-08T12:23:15Z 2011-04-15T08:25:24Z "Links in admin comments shouldn't have rel=nofollow. Admin comments are not user-generated content, and the site owner (admin) is vouching for the links just like when they link from the post itself. Therefore, this usage of nofollow is incorrect. Also, if I go and edit a comment and remove nofollow from a link, WP adds it back. It shouldn't do that either. Note that in the unlikely event of wanting a link in a comment to be nofollowed, this could still be done manually." caesarsgrunt 11360 Don't nofollow links within the site Comments 2.9 normal normal Future Release enhancement new has-patch 2009-12-08T12:24:42Z 2010-04-04T06:48:37Z "Relative links or links with the site's own domain shouldn't be nofollowed. This use of nofollow is damaging to the site's search engine rankings." caesarsgrunt 13363 Edit Comments: Pending > Approving shouldn't make them disappear from screen garyc40 Comments 3.0 normal normal Future Release enhancement assigned has-patch 2010-05-11T23:35:45Z 2012-03-08T01:56:30Z "Edit Comments: Pending > when clicking Approve the comments shouldn't just disappear from the screen. They should collapse and have an undo status like when you trash or spam a comment. ENV: WordPress trunk r14573 (3.0-beta2-14565) " lloydbudd 10869 Eliminate moderation on admin comments Comments normal normal Future Release enhancement new 2009-09-28T10:18:53Z 2009-11-28T12:34:10Z "Currently, if comment moderation is enabled, comments left by the admin are also moderated, requiring approval before they're posted. Proposed change: If comment moderation is activated, all replies and comments left by the admin are auto-approved." heather_r 13857 Email notifications lack a link to the comment, from address could be improved Comments normal normal Future Release enhancement new 2010-06-11T21:27:24Z 2010-10-28T01:47:17Z "'''Email Notification''' For the 6+ years I believe I have been using WordPress, the emails that notify me someone has made a comment have several links in them. '''Fields within an email notification''' Email, Url, Whois, Comment, All Comments, Delete, Spam The comment, at least in plain text emails, contains html markup, which often is encoded making it hard to read, depending on the comment complexity. I suggest a simple strip_html style function be ran on the comment copy. The link to the comments only takes you to the comments, but does not add in the identifier in the url to take you to that specific comment. The blog I am managing has 30+ comments on each page, making it harder than it should be to get to the comment and reply. An example of a better method might be: http://example.com/foo-bar-baz/#comment-7348 Compared to: http://example.com/foo-bar-baz/#comments ---- '''Email Headers''' The From header in the email is is correctly set to the ""Name"" value the user filled into the comment form, the email address is set to wordpress@example.com where example.com is the domain of the site. However, the reply-to header is correctly set to the actual sender. Bounces (NDR's) and the cosmetic view of an email could all be improved with a simple condition: {{{ if is_valid(emaIl) then from = name & ' <' & email & '>' reply-to = from else // looks like they did not set the data // fall back to some sane defaults end if }}} " hexley 16979 Extra hooks needed in comment process Comments normal normal Future Release enhancement new dev-feedback 2011-03-27T06:06:54Z 2012-05-22T16:29:11Z "I'm running into a few commenting issues whilst building a plugin with a custom post type.. * Duplicate comment check's cannot be bypassed * Empty comments are not allowed (In this case, the comment body is empty whilst a set of custom fields acting as metadata are set, meaning, the plugin wants to accept that comment) * being able to override the wp_die() in the commenting process would be useful (Currently: Duplicate comments, User not logged in, and not all fields filled in will cause this) One potential solution would be to move [http://core.trac.wordpress.org/browser/trunk/wp-comments-post.php#L55 lines 55-84] from `wp-comments-post.php` to functions hooked to `preprocess_comment`" dd32 13450 Filter Comments Link Comments normal normal Future Release enhancement new has-patch 2010-05-19T01:19:50Z 2010-10-28T12:12:51Z "This filter allows a developer to modify a post's comments link. Useful for situations where one needs to add or modify components of the URL such as on-click javascript, or changes to the anchor text, etc..." ikailo 7054 Generated avatars should not be shown on moderation pages. ryan Comments normal normal Future Release enhancement reopened has-patch 2008-05-28T15:53:22Z 2011-02-01T04:44:25Z "When moderating a lot of comments or checking the akismet queue the presence of an avatar can assist when checking for spammers. If generated avatars are shown on those pages it will increase the time to check comments and could lead to spam being inadvertently approved. These 2 pages should not show generated avatars. /edit-comments.php?comment_status=moderated /edit-comments.php?page=akismet-admin This does mean that avatar-free users who have had a previous comment approved would not have their generated avatar shown. In this case their avatar would need to be shown." podz 10863 Gravatars without email all end up looking generic Comments low minor Future Release enhancement new has-patch 2009-09-26T19:26:36Z 2011-01-06T14:50:54Z "When your blog has this option turned on ""Comment author must fill out name and e-mail"" and multiple users leave comments, if these users do not provide email addresses it will appear that they are all the same user as the identicon/monsterid/etc icons will be the same. With two additional lines of code, you can substitute the IP address in place of the email to get a unique hash in order to distinguish one anonymous/non-emailed user from another. Patch is attached" thecodepro 16219 If you can edit comments on the post, 'Slow down Cowboy' shouldn't kick in garyc40 Comments normal normal Future Release enhancement assigned has-patch 2011-01-13T19:05:44Z 2011-01-14T02:51:10Z Currently it's for administrators only. That doesn't make much sense for those who can already moderate comments. nacin 6536 "Introduce the concept of ""read"" and ""unread"" comments for better workflow in the admin" markjaquith* Comments 2.5 normal normal Future Release enhancement accepted 2008-04-02T00:48:54Z 2012-03-08T01:31:11Z "The Moderation Queue is a great way to manage your comment workflow. All comments go in there, and you approve, spam, or delete them. At the end you get a nice little ""0"" and you know you've dealt with all new comments. This doesn't work for people who don't moderate every comment. They have no idea when they are done, and which comments they have or have not looked at. I'd like to add a {{{comment_read}}} column to the comments table. It would be either ""1"" or ""0"". There would be a new sub-tab for Comments: ""Unread comments (%d)"" This page would be just like the Moderation page, except that it would only show comments with {{{comment_read = 0}}}. This could act as ""comment workflow central"" for both people who pre-moderate and people who post-moderate. Unapproved comments would have the actions: Approve, Spam and Delete. Approved comments would have the actions: Archive, Spam and Delete. Clicking any of these actions would both carry out that action AND mark that comment as read, making it disappear from the ""Unread comments"" page. (""Archive"" only marks it as read). Enterprising theme developers could even have this status shown on the public blog, so that people know whether their comments have been seen. For background on this idea, please see [http://markjaquith.wordpress.com/2008/03/20/the-comment-inbox/ The Comment Inbox] Note that this has benefits for people who moderate every comment, because they can now store comments in the moderation queue (comments they want to remove from the blog, but not delete) without that getting in the way of their comment workflow." markjaquith 22164 "Move comment ""keyboard shortcuts"" setting to comments -> screen options" Comments normal normal Future Release enhancement new has-patch 2012-10-11T14:14:23Z 2012-11-22T03:31:45Z "Seems like it would make more sense to move the comment ""keyboard shortcuts"" setting from ""Your Profile"" to the screen options pane of edit-comments.php. Something like: [[Image(http://f.cl.ly/items/1k210Z2V1o0b350I1n0V/keyboard-shortcuts.jpg)]]" lessbloat 12392 Move comment fields to meta data instead Comments normal normal Future Release enhancement new 2010-02-26T20:09:24Z 2012-07-16T04:19:52Z "Look at the comment table: {{{ CREATE TABLE $wpdb->comments ( comment_ID bigint(20) unsigned NOT NULL auto_increment, comment_post_ID bigint(20) unsigned NOT NULL default '0', comment_author tinytext NOT NULL, comment_author_email varchar(100) NOT NULL default '', comment_author_url varchar(200) NOT NULL default '', comment_author_IP varchar(100) NOT NULL default '', comment_date datetime NOT NULL default '0000-00-00 00:00:00', comment_date_gmt datetime NOT NULL default '0000-00-00 00:00:00', comment_content text NOT NULL, comment_karma int(11) NOT NULL default '0', comment_approved varchar(20) NOT NULL default '1', comment_agent varchar(255) NOT NULL default '', comment_type varchar(20) NOT NULL default '', comment_parent bigint(20) unsigned NOT NULL default '0', user_id bigint(20) unsigned NOT NULL default '0', ... }}} A lot of that is not actually being used on many sites and could be moved to standard meta data, available on demand, but not pulled out by default. Specifically: comment_author_IP - Used by Akismet and blacklist functions, included in emails sent to post authors/moderators, but once stored in the DB it's never really used again. comment_karma - Used by some of the importers as a space to store temporary data. Not actually used by core for anything serious anywhere. comment_agent - Used by Akismet and blacklist functions, but once stored in the DB it's never really used again. These could be pushed to meta and thus still made available, but without them being in the main table. This is a long term change, because some plugins would likely break. So the columns should be deprecated for a while first. " Otto42 10856 Move unesential comment fields to the comment meta table Comments 2.9 normal normal Future Release enhancement new dev-feedback 2009-09-26T03:07:47Z 2011-07-28T21:03:24Z "The wp_comments table has 3 less-used fields that would be better placed in the new commentmeta table. These are: - comment_author_IP - comment_agent - comment_karma" scribu 7532 Need comment_modified_date_gmt for approvals and edits Comments 2.6 low minor Future Release enhancement new 2008-08-17T04:45:49Z 2009-06-11T12:39:18Z "Summary:[[BR]] Currently there is only one date field for comments, comment_date_gmt. This is insufficient, because it represents only the creation date, not the approval date. The function get_lastcommentmodified can only check comment_date_gmt, which means that it can return an earlier date than the approval date. This can lead to RSS feeds wrongly returned HTTP 304 Not Modified responses. There needs to be comment_modified_date_gmt in addition to comment_date_gmt. Steps to Reproduce:[[BR]] (1) First comment is submitted.[[BR]] (2) First comment is mistakenly marked as spam by Akismet.[[BR]] (3) Second comment is submitted and posted.[[BR]] (4) Check comments feed in RSS reader. Second comment appears in feed, first comment does not.[[BR]] (5) Mark first comment as not spam.[[BR]] (6) Check comments feed in RSS reader again. Expected results:[[BR]] Comments feed returns HTTP 200, because there is a new comment in the feed. Actual results:[[BR]] Comments feed returns HTTP 304. Notes:[[BR]] The same bug could occur in other circumstances. For example, if a comment was held for moderation. " lapcat 12431 Record comment meta in wp_new_comment Comments 3.0 normal normal Future Release enhancement new has-patch 2010-02-28T21:29:43Z 2010-10-28T09:01:14Z "Spam filter plugins usually trigger on the preprocess_comment filter, which obviously happens prior to storing the comment (and thus prior to knowing comment_ID). Comment meta would be ideal for storing spam status information, but since the comment_ID isn't known at that point, doing so involves jumping through some hoops. This patch provides a simple way for spam filters to include comment metadata from preprocess_comment. They simply include values in a 'comment_meta' array like this: {{{ add_action('preprocess_comment', 'my_spam_handler'); function my_spam_handler($comment) { $comment['comment_meta']['my_spam_status'] = 'not-spam'; return $comment; } }}} Each key/value pair in the comment_meta array is stored as comment metadata. " tellyworth 8071 Refrain from querying all the comments on a post when paged Comments 2.7 normal normal Future Release enhancement reopened 2008-11-05T22:17:15Z 2012-07-16T04:35:24Z "If a post has more than (comment_per_page) comments, we should query them specifically, not query all the comments and sort in PHP (doesn't scale well). Logic: if threading is off, use a simple limit query elseif the page has equal or fewer comments than (comments_per_page), query them all else query (comments_per_page) parent comments, and keep doing queries for their children, up to the threading limit (10)." markjaquith 3842 Should make nofollow implementation cleaner and easier to remove Comments 2.1.1 normal normal Future Release enhancement new 2007-02-22T10:08:56Z 2011-07-23T06:44:21Z "{{{rel=""nofollow""}}} didn't appreciably stop comment spam, and there are many arguments for why it is a '''bad''' idea (and not just a failed idea). We should consider axing it." markjaquith 17020 Some comment queries are not filterable Comments 3.1 normal normal Future Release enhancement new has-patch 2011-04-02T16:56:32Z 2011-05-09T23:21:46Z "Although WP_Comment_Query::query() is fully filterable, some supplemental comment queries are still unfilterable. The submitted patch adds the following hooks: * function get_approved_comments() - query filter 'get_approved_comments_query' * function wp_dashboard_recent_comments() - query filter 'dashboard_recent_comments_query'" kevinB 17862 The second argument for wp_notify_postauthor() is unnecessary Comments normal normal Future Release enhancement new has-patch 2011-06-21T17:04:39Z 2011-06-21T17:04:39Z Only the comment id is needed. See patch. scribu 17275 UI: Missing comments count in admin screen Comments 3.2 normal normal Future Release enhancement assigned has-patch 2011-04-29T13:00:48Z 2013-02-23T11:29:14Z See Attached image. ramiy 4332 Unusable comment error pages markjaquith* Comments 1.5 normal normal Future Release enhancement accepted 2007-05-24T20:53:17Z 2012-03-08T01:35:22Z "No comment error page requires browser navigation to leave ENV: WP trunk r5486 While viewing a post, I click Submit Comment without entering any information and the result is (wp-comments-post.php): WordPress [[br]] Error: please type a comment. Dead end: no link back to the page where I meant to comment or maybe accidentally clicked the button, and ""Error:"" makes me feel stupid ;-) POSSIBLE SOLUTION I don't see any reason to navigate away from the post post. ADDITIONAL DETAILS Assuming the error page is desirable (sure hope not), being able to style it might be useful." foolswisdom 10653 Update comment_author when display_name changes Comments normal normal Future Release enhancement reopened has-patch 2009-08-19T19:43:29Z 2010-12-18T11:08:18Z One thing that has bothered me recently is the fact that your previous comments doesn't get updated when your display_name is being updated. Which could cause some confusion. I wrote a function (see attached file for further reference) that takes care of this but I would love to see a similiar feature in the WordPress core. mptre 10931 Verify Comment Email Addresses of Registered Users Comments 2.8.4 normal normal Future Release enhancement assigned has-patch 2009-10-08T14:34:44Z 2013-01-13T21:45:07Z "When leaving a comment with an email address of a registered user, WordPress should force the visitor to login or change the email address in the comment form. Anyone can impersonate a blog's user if they know the user's email address." mtdewvirus 17928 When a comment is spammed/trashed, change the parent of it's children Comments 3.2 normal normal Future Release enhancement assigned has-patch 2011-06-29T06:42:11Z 2012-03-08T02:17:19Z "When removing (spam/trash) a comment that has children, everything goes to hell in terms of hierarchy and you're left with a bunch of orphaned comments. See two attached images for what currently happens after removing a comment that has children. When a comment is removed, all immediate children of the comment to be removed should have their parent changed that of the the parent of the comment being removed (or top level if the comment to be removed is top level). Each comment that has it's parent changed then gets that action logged to it's post meta so that it can be moved back in the case of it's previous comment being restored (on post un-delete/spam, find all matching comment metas)." Viper007Bond 14510 comment_notes_before does not work. Comments 3.0.1 normal normal Future Release enhancement reopened 2010-08-02T18:39:34Z 2011-02-18T04:51:54Z "I am unable to get the comment_notes_before to work. Using the code: {{{ comment_form(array( 'comment_notes_before' => 'some text' )); }}} ... does not work. it just leaves the default text there. {{{ comment_form(array( 'comment_notes_after' => 'some text' )); }}} ... does work. It allows you to put whatever text you want." hotforwords 12104 edit-comments.php not available to roles with proper capabilities Comments 3.0 normal normal Future Release enhancement new has-patch 2010-01-31T22:25:24Z 2012-10-12T15:49:22Z "I tried to create a Comment Moderator role today and realized it wouldn't work. My intention was to create a role for people who can't write or edit posts, but can keep an eye on the comment threads. I created the role like so: {{{ #!php add_role('moderator', 'Moderator', array( 'read' => 1, 'moderate_comments' => 1, )); }}} ... then created a new user with that role. When I logged in as my test user, I realized that it was for all intents and purposes a Subscriber. I couldn't see any admin panels but the Dashboard, my profile, and the Tools. I went poking around in edit-comments.php and discovered that it's checking for another capability altogether: {{{ #!php if ( !current_user_can('edit_posts') ) wp_die(__('Cheatin’ uh?')); }}} I double-checked wp-admin/includes/menu.php and it agreed that 'edit_posts' was the minimum capability to see this page, so I tried adding 'edit_posts' to my new role, and I still couldn't get there. Later on in edit-comments.php, when actually trashing a comment, there is a check for 'moderate_comments', but it's a moot point: this screen doesn't even show up in the admin menu, and if you navigate directly to it, you'll get the ""You do not have sufficient permissions to access this page"" message. I thought it was entirely possible I'd missed some finer point of creating roles, so I redid it with Justin Tadlock's excellent Members plugin, and that didn't work either. This behavior might be intentional, but if so, I'm not following the logic. I know roles are due for an overhaul in the next version or two." sillybean 19903 wp_count_comments() and get_comments_count() both do SQL queries Comments 3.3.1 normal normal Future Release enhancement new 2012-01-26T22:16:42Z 2012-04-18T20:35:04Z "{{{wp_count_comments()}}} and {{{get_comments_count()}}} are similar functions, with a few differences: * Their results are returned in different formats: * {{{wp_count_comments()}}} returns an object of: * spam * approved * moderated * total_comments * trash * post-trashed * {{{get_comment_count()}}} returns an array of: * spam * approved * awaiting_moderation * total_comments * {{{wp_count_comments()}}} caches, but {{{get_comment_count()}}} always hits the database. * {{{get_comment_count()}}} is used nowhere in WordPress core. I propose that we add 'trash' and 'post-trashed' reporting to {{{get_comment_count()}}}, and then have {{{wp_count_comments()}}} use {{{get_comment_count()}}} instead of doing its own SQL queries. See #6884 and #19901" markjaquith 14697 wp_list_comments not fully HTML5-friendly Comments 3.0.1 normal minor Future Release enhancement new has-patch 2010-08-25T16:33:37Z 2012-07-04T09:47:48Z "Currently, wp_list_comments supports ol, ul, and div as ""styles"" of nesting for threaded comments. While HTML5 is new enough that good markup practices are not entirely settled, the closest thing I've seen to a consensus is nested article elements. This is currently not possible (except perhaps through a callback). Making it work right would also require inserting the comment classes as part of wp_list_comments' operation, which might require another parameter to turn it on. I'm sure there are other WP functions that could use expanding to accommodate good HTML5 markup, but this is what jumped out at me." adamrice 12223 Adding a titles to comment levels with the walker class Comments normal normal Future Release feature request new 2010-02-14T11:20:07Z 2010-02-14T17:52:36Z "Hi Everyone! This is only my second post here, and my first feature request, so please excuse me if I have duplicated something or my solution is completely unsuitable. I am experimenting with the CMS capabilities of Wordpress, especially the enhanced post_type GUI in the new 3.0 alpha release. While building a sort of Yahoo Answers type platform, I wanted to have 1st level comments as answers to a question (a post), and 2nd level comments as comments on the answer (1st level comments). I wanted to label comments on an answer as ""comments"", but this is not really possible to do, to my knowledge, using ""wp_list_comments"". I created my own function for wp_list_comments so I didn't have to modify Wordpress core, in order to get at the walker class at the bottom of wp_list_comments. I wanted to use start_lvl to add a title for comment level 2. However, start_lvl in ""class Walker_Comment extends Walker"" will only let you change the list type to ""ul"", ""ol"" or ""div"". My idea is to add an argument which would allow you to add a title, along with specifying it's heading (or surrounding tag). As I said, I am not an expert on Wordpress coding standards, so the following code may be completely off. {{{ /** * @see Walker::start_lvl() * @since unknown * * @param string $output Passed by reference. Used to append additional content. * @param int $depth Depth of comment. * @param array $args Uses 'style' argument for type of HTML list. * @param array $args Uses 'title' argument for title text. * @param array $args Uses 'title_heading' argument for title text heading level. */ function start_lvl(&$output, $depth, $args) { $GLOBALS['comment_depth'] = $depth + 1; switch ( $args['style'] ) { case 'div': break; case 'ol': echo ""\n""; break; default: case 'ul': echo ""\n""; break; } if (!empty ($args['title'])) { if(!empty ($args['title_heading'])) { echo '<'.$args['title_heading'].'>'; } echo $args['title']; if(!empty ($args['title_heading'])) { echo ''; } } } }}}" danielpataki 12986 Enhancement to comments_popup_link() Comments normal normal Future Release feature request new has-patch 2010-04-13T06:25:13Z 2010-04-18T05:53:20Z "Currently ""Comments Off"" is wrap with tag, but not ""Enter your password to view comments."" if post requires password. The idea is to wrap ""Enter your password to view comments."" with span tag, have its own css class e.g enter-password. Also adds $css_class if set. This way, theme author can easily style it based on post / comment status condition. And add another paramater $password so that theme author can customize the text to display if post is password protected. Need 2nd opinion with the attached patch. " zeo 13820 AJAX update the comment bubbles on edit-comments.php Comments 3.0 normal normal Future Release task (blessed) assigned has-patch 2010-06-10T13:45:27Z 2012-03-08T01:58:35Z "We update the bubble in the Comments admin menu item. We should also update the counts in the ""In Response To"" bubbles, as well as the bubble color." matt 13158 Cron : some events may not be scheduled westi Cron 3.1 high major Future Release defect (bug) new 2010-04-27T23:29:46Z 2012-08-03T22:39:04Z "the problem appears when two different events are scheduled at the same time what happens in code is : 1st event : _get_cron_array(); 2nd event : _get_cron_array(); 1st event : _set_cron_array( $crons ); 2nd event : _set_cron_array( $crons ); 1st event is lost." arena 20537 Don't spawn cron requests for suspended blogs Cron 3.3.1 normal normal Future Release defect (bug) new dev-feedback 2012-04-24T20:40:19Z 2012-09-17T06:54:10Z " {{{ }}} For multisite, spawning cron requests is wasteful and unnecessary. wp_cron()/spawn_cron()/wp-cron.php should check the blog's status and bail if the blog is suspended." ryan 12609 Enabling FORCE_SSL_ADMIN breaks wp-cron.php westi Cron normal normal Future Release defect (bug) new dev-feedback 2010-03-15T16:02:29Z 2010-11-13T07:50:43Z I just completed a server migration and discovered that scheduled posting broke during the process. I tried a few things, including the suggestions from ticket #8923 with no luck. I realized that one change I made, on the new server, was a requirement that the admin uses SSL. After disabling FORCE_SSL_ADMIN I discovered that scheduled posts work again. It seems that I can leave FORCE_SSL_LOGIN turned on and it doesn't cause any problems. This is good enough for our security needs, but I'm sure others might want to have both enabled. dphiffer 11826 Endless Cron Spawn westi Cron 2.9 normal normal Future Release defect (bug) new 2010-01-08T19:09:02Z 2010-12-14T10:00:23Z "I somehow get it managed to keep such request in memory while they consume CPU all the time. I noticed that first a week ago or so and now I was able to find out some specifics: {{{ REQUEST_URI /wordpress-trunk/wp-cron.php?doing_wp_cron REQUEST_METHOD post }}} Maybe there is a condition for an endless loop in there?" hakre 8923 cron timeout is too short Cron normal normal Future Release defect (bug) reopened reporter-feedback 2009-01-22T23:50:57Z 2011-09-21T17:13:46Z "Many users have reported that 2.7 cron sometimes fails to publish future post. And it is further reported that it depends on the number of jobs on the cron queue - when the queue is too long, it will miss some. I believe this is because we set the timeout value too short: wp_remote_post($cron_url, array('timeout' => 0.01, 'blocking' => false)); When making a request to wp-cron.php, it won't return until all cron jobs are executed. And 0.01 is just too short time span. It doesn't hurt to give it sufficent time, such as 10 minutes. It will return as long as the mature crons are fired up and executed (in most cases, it's going to be at most a few seconds ). " hailin 11800 doubled execution of cron jobs westi Cron 2.9.1 normal normal Future Release defect (bug) new 2010-01-07T11:17:53Z 2011-06-02T07:18:50Z "Hi, as I've already mentioned in ticket #11505 , cron-jobs occasionally get executed twice (e.g. daily backup arrives two times). I've changed the code according to the patch attachment:ticket:11505:ticket-11505-stop-gap.patch (which derives from [http://wpengineer.com/ping-problem/]) after my comment:ticket:11505:49 and had no doubles within this time period. This week I've upgraded to WP 2.9.1 and since then backups arrive two, sometimes three times, again. Looking at the changes from 2.9 to 2.9.1, I have no other explanation for this behavior. - Maybe we should consider having a closer look again on this patch attachment:ticket:11505:ticket-11505-stop-gap.patch . Greetz, Berny" neoxx 15148 Cron Storage Abstraction Cron normal normal Future Release enhancement new has-patch 2010-10-19T04:04:00Z 2011-06-02T07:03:36Z Abstract cron storage to allow pluggable storage schemes. ryan 18997 Adding wp_unschedule_hook function arena Cron 3.3 normal normal Future Release feature request reopened needs-unit-tests 2011-10-19T07:45:11Z 2012-04-20T00:02:54Z " Unschedule all previously scheduled cron job for a hook. Can be usefull for plugins when deactivating to clean up the cron queue The $hook parameter is required, so that the events can be identified. @param string $hook Action hook, the execution of which will be unscheduled. " arena 13103 """Unknown character set"" during install into database reports successful install." barrykooij Database 3.0 normal normal Future Release defect (bug) assigned has-patch 2010-04-24T15:10:23Z 2012-11-07T23:30:23Z "During editing of the wp-config.php, I changed {{{ define('DB_CHARSET', 'utf8'); }}} to {{{ define('DB_CHARSET', 'utf8_general_ci'); }}} Which I thought was valid. After clicking ""Install Wordpress"" I got a page full of: {{{ WordPress database error: [Unknown character set: 'utf8_general_ci'] }}} And at the bottom, ""Success"" with a login prompt, but nothing was actually created in the database. I think WP shouldn't report a successful install if the user happened to accidentally change this value (or another) during install as it would cause confusion. I used a svn checked out version of WP on 2010-04-24 on my local computer using PHP5 and apache2, but I think this is really a problem since 2.6 (or when the current install system was implemented)." MECU 21870 @ error control operator hides fatal error on mysql_fetch_object Database 1.5 normal normal Future Release defect (bug) new has-patch 2012-09-11T14:59:36Z 2012-11-07T19:49:19Z "I ran a get_posts() query that took me a while to track down to the @ error control operator on the mysql_fetch_object call (see wp-db.php:1219 in trunk), therefore PHP was silently die'ing on me because of a memory limit error. I'm curious as to what use cases there are for the error control operator to be used here. In my case, I want to see these errors and fix my code accordingly, or tailor my query to the memory constraints, or rethink my data relations in the database. " ericlewis 11151 Common White Screen of Death in wpdb Database 2.8.5 normal major Future Release defect (bug) assigned 2009-11-16T15:07:53Z 2010-12-08T21:32:54Z "I imported some 10.000 users into WP through a custom script, using wp_insert_users(). Import successful, I could log in with new users. Yet wp-admin/users.php page fails to load the users table; I got the admin header and menu but the page stopped loading when querying the DB for the users data. I set WP-DEBUG to true, but still no error. NO errors in the server log also. I eventually had to add define('WP_MEMORY_LIMIT', '64M'); to wp-config.php to get the users.php page working. The problem here is that the page doesn't issue the usual PHP memory limit fatal error, I had to guess to sort it out. " nutsmuggler 13310 Extend option_name to varchar(255) ryan Database 3.4.2 normal normal Future Release defect (bug) new dev-feedback 2010-05-09T13:34:25Z 2013-05-24T17:33:23Z "option_name is currently set to varchar(64). This raises problems when one tries to use transients with slightly longer names and a timeout: {{{_transient_timeout_feed_mod_23a137101df6920fbf6047...}}} has 60 chars already." scribu 15004 Missing index on signups table pento Database normal normal Future Release defect (bug) assigned commit 2010-10-01T03:48:25Z 2013-05-07T17:36:17Z "{{{ wp-includes/ms-functions.php:590: $signup = $wpdb->get_row( $wpdb->prepare(""SELECT * FROM $wpdb->signups WHERE user_email = %s"", $user_email) ); wp-includes/ms-functions.php:595: $wpdb->query( $wpdb->prepare(""DELETE FROM $wpdb->signups WHERE user_email = %s"", $user_email) ); }}} But there is no index on user_email in the signups table. Makes these queries perform a full table scan which is slow when you have lots of signups. Attached patch adds the index but I can't figure out how schema upgrades on MS-specific tables ever get run after the initial activation of MS mode and table creation. " barry 21504 Not checking if apply_filters exists before calling it in WP_DB Database 3.4.1 normal normal Future Release defect (bug) new has-patch 2012-08-06T22:49:52Z 2012-10-25T21:17:48Z "Prior to version 3.4, there was a check to verify that apply_filters existed before calling it in wp-includes/wp-db.php. {{{ // some queries are made before the plugins have been loaded, and thus cannot be filtered with this method if ( function_exists( 'apply_filters' ) ) $query = apply_filters( 'query', $query ); }}} In version 3.4 and above, that check doesn't exist anymore, and can throw an error. There is still a comment indicating that a check should be made, but the actual code to perform the check is now gone. This is around line 1081 {{{ // some queries are made before the plugins have been loaded, and thus cannot be filtered with this method $query = apply_filters( 'query', $query ); }}} Here is the github blame view to show when the code was remove (I'm not sure how to find this same view in your svn): https://github.com/WordPress/WordPress/commit/81ed9a7563e5ad4c0edccd059bc4ea7d9c1a4a10 There's no explanation about why the code was removed, so would it be possible to add it back in? Thanks! Julia " jdkoelsch 16107 WordPress Database Error Logging Extravaganza Database 3.0.4 normal normal Future Release defect (bug) new has-patch 2011-01-05T12:41:00Z 2011-01-05T14:33:05Z "If PHP error logging is enabled, the wordpress database class will log errors to file by using the error_log() function. This is a PHP function. While doing so, it does not reflect the PHP configuration setting for {{{log_errors_max_len}}} which defaults to 1024 (bytes). While not doing so, the database class can log extremely long queries into the file creating multiple gigabytes quite quickly." hakre 12302 add_metadata() Fails to Store Serialized Values as BINARY ryan Database high critical Future Release defect (bug) new 2010-02-20T10:52:15Z 2010-04-18T04:36:44Z "Symptoms: WordPress stores corrupt values in post_metadata if there are any non-UTF-8 bytes in the meta_value. Steps to reproduce: Call add_metadata() with non-UTF-8 values such as a latin-1 copyright char. Even though the serialized string goes through prepare() before the query, MySQL is required to truncate the invalid value being assigned to the meta_value field. The result is that the stored value can never be un-serialized. This behavior can also be replicated by trying to inject CHAR(169) into any UTF-8 table query." miqrogroove 14445 dbdelta do not handel FULLTEXT KEY correctly and generate MySQL errors Database 3.0 normal minor Future Release defect (bug) new has-patch 2010-07-28T17:36:36Z 2011-01-16T02:11:59Z "When using dbdelta during the update of a plugin that a Fulltext index use, dbdelta generate a MYSQL error due to duplicate index. This is due to the array_search return always false. I attached a posible solution to address this issue. I added a key named 'index_type' to the $index_ary. This way, when 'index_type' == fulltext, I add to $index_string ""FULLTEXT""." edirect24 12257 wpdb Scales Badly Due to Unnecessary Copies of All Query Results ryan Database normal critical Future Release defect (bug) reopened needs-refresh 2010-02-17T03:08:06Z 2013-03-19T05:19:44Z "While working on #11726, I encountered a reproducible crash in wpdb::query() The following code causes memory exhaustion on large result sets: {{{ while ( $row = @mysql_fetch_object($this->result) ) { $this->last_result[$num_rows] = $row; $num_rows++; } }}} The memory exhaustion message is error-controlled, causing a white screen of death even in debug mode. I searched wp-db.php for references to $this->last_result, and I found no justification for these object reference copies. $this->last_result '''should''' be maintained as a MySQL resource and properly optimized using the MySQL client layer instead of this PHP nonsense. Tagging for dev-feedback to discuss which Milestone is appropriate." miqrogroove 11717 Access to automatic database repair/optimize with admin rights ryan Database 2.9.1 normal normal Future Release enhancement new dev-feedback 2010-01-05T07:35:10Z 2012-08-08T08:52:02Z "Hi, I read somewhere that the reason for using a constant as enabler for the automatic repairing/optimizing database functionality was, that some people are not able to access their back-end in case certain tables are broken. Anyway, as db optimization (and not only repairing) is also included in ''/wp-admin/maint/repair.php'', it would be helpful, if we could avoid setting the constant and in addition grant users with the admin role the right to access the functionality. I've added the necessary two lines and attached a patch to this ticket. - Hopefully this will make it into core, because it would really ease access and increase usability. My Best, Berny" neoxx 15499 Add an index for get_lastpostmodified query Database 3.0.1 normal normal Future Release enhancement new dev-feedback 2010-11-19T18:20:31Z 2012-12-04T21:50:27Z "I had a friend (Jools Wills) look over a WordPress site recently, to get a fresh view on what might be optimised, and he noticed a query which might benefit from an additional index on ```WP_Posts```. The query ```SELECT post_modified_gmt FROM $wpdb->posts WHERE post_status = 'publish' AND post_type = 'post' ORDER BY post_modified_gmt DESC LIMIT 1``` in ```get_lastpostmodified``` is run for last modified date in GMT, and currently doesn't use an index. This SQL is run whenever certain types of feed are requested as far as I can see. We added ```CREATE INDEX type_status_modified ON wp_posts (post_type, post_status, post_modified_gmt);``` and ```CREATE INDEX type_status_modified_no_id ON wp_posts (post_type, post_status, post_date_gmt);``` and the query runs a lot faster now. The following timings were taken running the first query (```post_modified_gmt```) on a 36,362 row posts table. Note that it doesn't use filesort after the index has been added. ''Before:'' {{{ mysql> EXPLAIN SELECT post_modified_gmt FROM slgr_posts WHERE post_status = 'publish' AND post_type = 'post' ORDER BY post_modified_gmt DESC LIMIT 1; +----+-------------+------------+------+------------------+------------------+---------+-------------+-------+-----------------------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +----+-------------+------------+------+------------------+------------------+---------+-------------+-------+-----------------------------+ | 1 | SIMPLE | slgr_posts | ref | type_status_date | type_status_date | 124 | const,const | 24718 | Using where; Using filesort | +----+-------------+------------+------+------------------+------------------+---------+-------------+-------+-----------------------------+ 1 row in set (0.03 sec) }}} * 0.21290683746338ms * 0.25690102577209ms * 0.230553150177ms * 0.2274341583252ms * 0.23083996772766ms ''After:'' {{{ mysql> EXPLAIN SELECT post_modified_gmt FROM slgr_posts WHERE post_status = 'publish' AND post_type = 'post' ORDER BY post_modified_gmt DESC LIMIT 1; +----+-------------+------------+------+---------------------------------------+----------------------+---------+-------------+-------+-------------+ | id | select_type | table | type | possible_keys | key | key_len | ref | rows | Extra | +----+-------------+------------+------+---------------------------------------+----------------------+---------+-------------+-------+-------------+ | 1 | SIMPLE | slgr_posts | ref | type_status_date,type_status_modified | type_status_modified | 124 | const,const | 24718 | Using where | +----+-------------+------------+------+---------------------------------------+----------------------+---------+-------------+-------+-------------+ 1 row in set (0.00 sec) }}} * 0.00082707405090332ms * 0.00072288513183594ms * 0.00074386596679688ms * 0.00066494941711426ms * 0.00066208839416504ms In ```get_lastpostmodified``` both these queries are run, so the total savings in my case on a quiet server are nearly 0.5 seconds... worth having, I reckon. I've not created a patch for schema changes before, but I think the only place the change would need to go would be ```scheme.php```? Suggested patch attached." simonwheatley 9642 Database Schema Optimizations Database 2.8 normal normal Future Release enhancement assigned 2009-04-24T19:42:40Z 2013-02-16T16:15:57Z Diffs coming... Denis-de-Bernardy 22115 Further Simplifying errors Database 3.4.2 normal normal Future Release enhancement new dev-feedback 2012-10-06T11:32:15Z 2013-05-16T11:55:15Z "tracking errors while making API's and cron jobs, is a tad difficult. from the latest wordpress pack, '''''/includes/wp-db.php''''' {{{ function query( $query ) { ... ... if ( defined( 'SAVEQUERIES' ) && SAVEQUERIES ) $this->queries[] = array( $query, $this->timer_stop(), $this->get_caller() ); // If there is an error then take note of it.. if ( $this->last_error = mysql_error( $this->dbh ) ) { $this->print_error(); return false; } ... ... }}} if we change the above to simply {{{ // If there is an error then take note of it.. $this->last_error = ''; if ( $this->last_error = mysql_error( $this->dbh ) ) $this->print_error(); if ( defined( 'SAVEQUERIES' ) && SAVEQUERIES ) $this->queries[] = array( $query, $this->timer_stop(), $this->get_caller(), $this->last_error ); // If there is an error then take note of it.. if ( ! empty( $this->last_error ) ) return false; }}} then we have all required info in the array queries, for use later. may it be wp_footer, or for a plugin as debug info." msolution 20316 Garbage collect transients Database normal normal Future Release enhancement new dev-feedback 2012-03-28T22:04:35Z 2013-05-14T15:57:57Z "Per an IRC discussion and long-considered changes: * In wp_scheduled_delete(), look for expired transients and purge them. * On DB upgrade, purge all transients, regardless of expiration. (This should probably happen on auto-update as well, but let's let that part slide for now, as DB upgrade will run on all major releases these days.) We should only do this if ! $_wp_using_ext_object_cache." nacin 19019 Reduce duplication in $wpdb Database normal minor Future Release enhancement new commit 2011-10-20T21:16:00Z 2013-04-22T19:53:27Z "Currently, update(), insert() and soon delete() [see #18948] use the same code to generate the WHERE clause. It should be moved into a helper method." scribu 10819 Suggestion: Addition to dbDelta - returns FALSE on mySQL error ryan Database 2.8.4 normal normal Future Release enhancement new dev-feedback 2009-09-20T22:07:46Z 2009-09-20T22:21:53Z "I don't have any idea how to submit or recommend a change to the WordPress core, but I'm going to give this a shot anyway... having just spent a lot of time struggling with the dbDelta function while programming a plugin, I had a possible suggestion to make. It strikes me that said function would be a lot easier to use if something similar to the following code was added, starting on line 1363 of wp-admin/includes/upgrade.php: if($execute) { $query_error_num = 0; foreach($allqueries as $query) { //echo """".print_r($query, true).""\n""; $qresult = $wpdb->query($query); if ($qresult === false) { $query_error_num++; $qerror = 'error' . $query_error_num; $for_update[$qerror] = ""Query error - The following query failed: "" . $query; } } } return $for_update; There's probably a more optimized way to go about it - programming isn't my strong suit by any stretch of the means - but at least this way errors caused when *creating* tables with the function will return some kind of error message, even if it's PHP only. Opinions?" tinwatchman 13657 When WP_DEBUG is true show better errors for establishing database connection ryan Database low trivial Future Release enhancement new has-patch 2010-05-31T16:26:04Z 2012-12-30T09:35:09Z "Right now no matter if WP_DEBUG is enabled or not we always show some generic errors for Error establishing a database connection We should display the specific error when WP_DEBUG is enabled." sivel 10883 db-error.php not used for all DB failures ryan Database 2.8.4 normal normal Future Release enhancement new dev-feedback 2009-10-01T02:45:28Z 2013-01-25T04:39:55Z "db-error.php (the optional custom DB error message file to be placed in wp-content) does not get included all the time. Sometimes wp-db.php will use its {{{bail()}}} method to spit out its own message. This code needs to be there too: {{{ if ( file_exists( WP_CONTENT_DIR . '/db-error.php' ) ) { require_once( WP_CONTENT_DIR . '/db-error.php' ); die(); } }}}" markjaquith 10404 dbDelta creates duplicate indexes when index definition contains spaces Database 2.8.1 normal normal Future Release enhancement new has-patch 2009-07-14T10:59:54Z 2013-03-25T12:24:45Z "I was adding a much needed index in wp_object_term_relationships, and testing revealed it was getting added multiple times. This works as intended: {{{ CREATE TABLE $wpdb->term_relationships ( object_id bigint(20) unsigned NOT NULL default 0, term_taxonomy_id bigint(20) unsigned NOT NULL default 0, term_order int(11) NOT NULL default 0, PRIMARY KEY (object_id,term_taxonomy_id), UNIQUE KEY reverse_pkey (term_taxonomy_id,object_id), KEY term_taxonomy_id (term_taxonomy_id) ) $charset_collate;""); }}} This doesn't: {{{ CREATE TABLE $wpdb->term_relationships ( object_id bigint(20) unsigned NOT NULL default 0, term_taxonomy_id bigint(20) unsigned NOT NULL default 0, term_order int(11) NOT NULL default 0, PRIMARY KEY (object_id,term_taxonomy_id), UNIQUE KEY reverse_pkey (term_taxonomy_id, object_id), KEY term_taxonomy_id (term_taxonomy_id) ) $charset_collate;""); }}} the only difference between the two is a space in the reverse_pkey column list. we should remove spaces in there to avoid potential bugs." Denis-de-Bernardy 14273 maybe_create_table cleanup pento Database 3.0 normal normal Future Release enhancement assigned has-patch 2010-07-11T13:08:09Z 2012-08-08T07:47:23Z "Cleaned up maybe_create_table() - no more iterations. Cheers. Dragoonis aka Dr4g(irc)." dragoonis 15158 wpdb insert & update with null values sorich87* Database 3.0.1 normal normal Future Release enhancement accepted has-patch 2010-10-19T20:47:51Z 2013-01-08T13:39:21Z "From: http://wordpress.org/support/topic/bug-fix-wpdb-insert-amp-update-with-null-values ""Some of you might have noticed but the wpdb's insert & update methods don't work well with null value (if you try to set null on a numeric field you'll end up with 0)"" " westi 5932 "wpdb should reconnect and retry query when ""MySQL server has gone away""" pento Database 3.0 normal normal Future Release enhancement assigned has-patch 2008-02-20T08:17:01Z 2012-11-07T06:15:56Z "Using 2.3.3, here are the type of errors that crop up in error_log everyday. {{{ [25-Jan-2008 08:37:35] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = '0' WHERE option_name = 'doing_cron' [25-Jan-2008 09:23:19] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = '0' WHERE option_name = 'doing_cron' [26-Jan-2008 00:03:54] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = '0' WHERE option_name = 'doing_cron' [26-Jan-2008 00:04:29] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_pingme' LIMIT 1 [26-Jan-2008 00:04:29] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_encloseme' LIMIT 1 [26-Jan-2008 00:04:29] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = 'publish' [26-Jan-2008 00:05:09] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_pingme' LIMIT 1 [26-Jan-2008 00:05:09] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_encloseme' LIMIT 1 [26-Jan-2008 00:05:09] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = 'publish' [26-Jan-2008 00:05:47] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_pingme' LIMIT 1 [26-Jan-2008 00:05:47] WordPress database error MySQL server has gone away for query SELECT * FROM wp_posts, wp_postmeta WHERE wp_posts.ID = wp_postmeta.post_id AND wp_postmeta.meta_key = '_encloseme' LIMIT 1 [26-Jan-2008 00:05:47] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE CHAR_LENGTH(TRIM(to_ping)) > 7 AND post_status = 'publish' ................. }}} " dtc 12819 wpdb::prepare support for null ryan Database normal normal Future Release enhancement reopened 2010-04-02T18:15:19Z 2013-05-13T16:39:35Z "now we can not submit null values using wpdb::prepare. if we lets say have datetime field that can be null, and execute query prepared with $wpdb->prepare(""update table set date_time_field = %s"", null) - it sets value of the field to 0, which results in 0000-00-00 00:00:00 date. what is happening here - null is quoted and passed as a string, that should not be the case." roxaz 21663 Use PDO for MySQL queries when PDO is available Database 3.5 normal normal Future Release task (blessed) new dev-feedback 2012-08-22T21:02:28Z 2013-05-20T22:21:49Z "the mysql_* functions are officially deprecated for PHP 5.4 and will begin throwing E_DEPRECATED errors in the next version of PHP. http://marc.info/?l=php-internals&m=131031747409271&w=2 Wordpress should use PDO by default, but fall back to mysql_* when PDO is not present. See also: #11622 for last year's discussion." scottconnerly 20328 get_date_from_gmt assumes current gmt_offset is appropriate nacin Date/Time normal normal Future Release defect (bug) reopened has-patch 2012-03-29T22:02:24Z 2013-05-14T13:22:54Z "For locations that have daylight savings time, the gmt_offset changes over time. Yet get_date_from_gmt assumes the offset that is in effect now is always the right offset. But I might be trying to display date/times that are in a different timezone transition than the current one. Proposed fix is to use timezone_transitions_get() as wp-admin/options-general.php does in order to translate those date/times accurately." scottconnerly 15921 date column filter in media list table Date/Time 3.1 normal normal Future Release enhancement new 2010-12-20T18:25:49Z 2011-03-23T17:08:18Z "please add a filter for date column in media list table, like posts list table. in wp-admin\includes\class-wp-media-list-table.php @ line:288 replace: {{{

}}} with: {{{}}}" gonahkar 10660 Time zone suggester based on nascent WordPress.org API call rmccue Date/Time 2.8.4 normal normal Future Release feature request assigned has-patch 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 17391 Alternative color schemes and theme settings in editor styles azaozz Editor 3.2 normal trivial Future Release defect (bug) assigned early 2011-05-12T13:14:56Z 2012-01-14T19:10:10Z "Hello there. There is no support for links color change in editor-style.css. If you change it in Theme Options, you will see the same: {{{ a { color: #1b8be0; text-decoration: none; } }}} As we want the editor to be WYSIWYRG, maybe we should include this change in editor-style.css too. I have tried to do that with `add_editor_style()`, but it is only intended for .css archives. I have tried to add it as a filter extending `twentyeleven_print_link_color_style` in `mce_css` and `tiny_mce_before_init`, unsuccessfully. All ideas for what can I use to make tinyMCE read the options are welcome. " bi0xid 19649 DFW Auto textarea lengthening is twitchy koopersmith Editor normal normal Future Release defect (bug) assigned 2011-12-22T21:52:36Z 2012-04-27T21:08:56Z "The auto textarea lengthening is twitchy. It shoves the content up a line, then pulls it back down. Best seen in a screencast: http://screencast.com/t/e5zIpkk9nY" markjaquith 11986 HTML comments in post/page content get wrapped in P tags Editor 2.9.1 normal normal Future Release defect (bug) new 2010-01-23T19:32:13Z 2010-06-14T01:39:31Z "I don't know if someone already caught this i had mentioned it to someone in the #chat but When you write a post or a page and include comment html tags the comments end up being wrapped in tags An older plugin i use makes use of comment tags to know where to insert content but comments may be used for other reasons inside posts. the more comments you add the more line breaks errr paragraph breaks additionally the plugin I was using could not pickup the comment tag and insert the content. " NPSites 16116 Hide 'Move to Trash' for auto drafts Editor 3.0 normal normal Future Release defect (bug) new dev-feedback 2011-01-06T05:54:59Z 2013-01-22T16:52:51Z "The 'Move to Trash' link should not appear for auto-drafts. This was the original intent of what [13905] removed, which I want to say was designed to reflect additional scenarios." nacin 13942 Logged-out notice in post edit page is easily missed Editor 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-06-17T11:25:40Z 2012-09-27T15:42:48Z "When a user gets logged out during post editing, a small warning appears bellow the post editor, next to the word count. This warning states that changes will not be saved until user logs in again - but it's a small notice and is very easily missed. Since this can be potentially catastrophic for users writing long posts while relying on auto-save, a bigger and more prominent notice probably makes more sense. === Repro === ENV: WP 3.0 This bug can be reproduced in WordPress 3.0 by opening two tabs – one tab with a blog’s Dashboard, and another tab with the same blog’s New Post page. In the Dashboard, click Logout, then switch to the New Post tab. Here, enter any text in the post’s title, then hit Tab to switch to the editor. This will trigger the permalink preview, which will in turn trigger the notice about being logged out: “ALERT: You are logged out! Could not save draft. Please log in again.” === Additional Details === The notice comes from wp-admin/admin-ajax.php, in line 36. Currently behavior was introduced by #7630, where it was already noted ""maybe something more obvious needed""" RanYanivHartstein 16077 Placement of link popup in full-size visual editor when browser window is resized garyc40 Editor 3.1 normal normal Future Release defect (bug) assigned has-patch 2011-01-02T19:47:30Z 2013-01-22T16:54:13Z "To recreate: Writing a post in the full-window view of the visual editor, click the link popup. While popup open, resize browser window to be smaller. Link popup stays in original location, even if the window gets small enough to cut it off. You can move the link popup by dragging the top bar. If you do this, then the link popup will stay in the new place b/c our save state stuff, even when you're writing in the regular size visual editor. Preferred UX: if browser window resizes, have link popup recenter itself in the overlay. " jane 13327 Post editor puts content through wpautop() before displaying it to users without JS enabled Editor 3.0 low normal Future Release defect (bug) new 2010-05-10T21:42:50Z 2010-11-12T11:24:54Z "'''Steps to reproduce:''' 1. With JS on, change to the Visual Editor 2. Disable JS 3. Add a new post 4. Save as draft 5. Note that the content is wrapped in {{{}}} tags in the textarea. [[Image(http://img19.imageshack.us/img19/6363/screenshot20100510at524.png)]] '''Expected:''' No paragraph tags are added." markjaquith 11082 Saving an empty draft dumps user out to edit.php akhilasuram Editor 2.7 low minor Future Release defect (bug) assigned needs-refresh 2009-11-05T15:16:46Z 2012-12-13T20:09:23Z "ENV: wp trunk r12138 (2.9-rare) When a user starts up the editor for a new post and attempts to save a post with no title and no content, WordPress dumps the user back out to the list of posts in edit.php with no message or indication as to why this happened. You can edit the publish information (date, status, etc.), tags, and categories, but as long as there is nothing for either the post title or the post content, the behavior is the same. It's expected that a post with no content whatsoever wouldn't be saved (there's nothing there!), but would be nice if the behavior were easier to understand or explained why nothing was happening." markel 9716 WordPress Theme/Plugin editor adds blank lines Editor 2.7.1 normal normal Future Release defect (bug) reopened has-patch 2009-05-03T20:32:01Z 2012-04-20T16:29:42Z "When I edit theme css in theme editor in WP admin !WordPress reformats my CSS and adds a blank life between entrys in css. it adds a cr and line break .... In other words if you have a 100 line css download with FTP look at in text editor it is now 200 lines as WP added blank lines to css it should not be adding things to the CSS? It may only do this when it wraps window but I think not it appears to add blank lines. Imagine the damage to a 1000 line CSS it spaces every entry by 1 line!!!!!!!!!!!!!! It stiil works but it messes it up. THAT IS COFIRMED ONE EDIT DOUBLE SPACE ENTIRE CSS... VERY BAD Here is part of the problem but not the double space in total. When you down load the file in FTP and it is in windows encoding the line endings. So you ftp back and all is fine. Now you are at the coffee shop and what a quick change, so you login to WP admin and theme editor edit CSS. Now you get home and download in ftp to continue your work on CSS. The file is now mac formatted (or thinks it is) so when you edit the line endings do not contain the right line breaks for windows OR WP theme editor as it ignores them. This explains the wierd spacing though not the double spacing .... why is it converting to mac and yet ignores mac?! weird.. it adds a CR tag must be bug again though its still double spacing on edit IN windows line ending though if you down load cSS its tagged mac format... Use notepad 2 or Note pad plus to see the error. When ever you edit with !WordPress editor it adds cr and says css is now mac formatted. FTP download the file and now see all the extra CR's it adds. So it likes CR only so I convert to CR only and it beaks CSS it wants CR LF to work but if that is the case why does the online editor add CR only????????????????????????? " Vistronic 14808 Add Editor Documentation Functions URL for theme-defined functions Editor normal normal Future Release enhancement new has-patch 2010-09-08T00:57:20Z 2011-08-25T00:15:44Z "Currently, functions that are called within template files shown on the editor are included in the list of functions that you can try and lookup documentation for. (The $ignore_functions array only seems to be for functions defined, not called, in a file.) As the http://api.wordpress.org/core/handbook/1.0/?function=... seems to be hard-coded in, it's not possible for themes to overwrite it for functions they've defined. Is it possible to allow themes to define where the documentation lookup should be for their own functions?" GamajoTech 7665 Add jQuery UI's datepicker() where applicable chsxf Editor 2.7 lowest minor Future Release enhancement assigned has-patch 2008-09-01T09:32:03Z 2013-05-14T07:48:59Z "Obviously it'll need some skinning, but it's handy dandy: http://jqueryui.com/demos/datepicker/ It'd be slick to have that for choosing dates (for example publish dates). We should still allow manual entry though." Viper007Bond 11268 Allow Image Map in KSES Editor 2.9 low minor Future Release enhancement new has-patch 2009-11-26T00:12:31Z 2010-03-31T08:50:20Z Add image maps in allowed post tags. mtdewvirus 15631 Custom fields auto-focus Editor 3.1 normal normal Future Release enhancement new has-patch 2010-12-01T19:02:16Z 2013-01-22T15:23:25Z When you are on the post editor (page editor, whatever), if you want to create a new custom field and click on Create New, it should auto-focus on the text input field that appears. jane 20186 Default font in the Visual Editor doesn't work well in all languages Editor normal normal Future Release enhancement new 2012-03-06T20:41:53Z 2012-05-02T20:25:57Z As the title. This is somewhat unnoticed as most themes seem set the fonts there with editor-style.css. However we would need a default that works well for themes that don't set that. azaozz 2702 Easier way to change page order (AJAX/jQuery?) mdawaffe Editor 2.3 normal normal Future Release enhancement new 2006-05-03T21:36:37Z 2011-10-08T03:23:13Z "When having a lot of pages, they get harder to manage (see also Ticket #2004 [Pages page should page]). When needing to change the page order, it's very inefficient to manually change the page order value, or whole series of page order values, just to move one page up or down the list. Suggestions for alternative ways to change the page order are: In ""Manage - Pages"" 1) With up/down arrows (page goes one up or down when the button/link is clicked). 2) or: Drag+Drop (The post/page settings can be dragged and dropped, so why can't this, too?) " FireMotion 14640 "Feature Requst: Add Action Hook ""post_submitbox_end""" Editor 3.0.1 normal normal Future Release enhancement new has-patch 2010-08-18T21:09:53Z 2013-01-10T02:55:26Z I'd like to add a button UNDER the Publish button on an edit post page. There is an action for adding a button (or other elements) BEFORE the Publish button (post_submitbox_start), but I'd like one at the end. I know that I can address this w/ CSS if necessary, but it would be nice to be able to position my button in the HTML as well. ancawonka 18820 Formatting bar loading experience is subpar azaozz Editor 3.2.1 normal normal Future Release enhancement reopened 2011-09-29T21:51:41Z 2011-11-18T07:23:24Z "When you save a post, the way the formatting bar loads in (Visual and HTML both) is subpar. It pops in really late, and shoves your post content down. Screencast: http://s3.amazonaws.com/txfx/screencasts/Formatting-Toolbar.mov Let's make this better." markjaquith 18423 Make internal linking's River + Query constructors public koopersmith Editor 3.2 normal normal Future Release enhancement reviewing has-patch 2011-08-16T02:00:07Z 2011-12-19T00:24:45Z ...and restructure them so that they're slightly more configurable, i.e. making the AJAX endpoint URL and result rendering overrideable. mitchoyoshitaka 18306 Make sample permalink clickable Editor 3.2 normal normal Future Release enhancement new has-patch 2011-07-31T14:41:39Z 2012-11-01T20:02:13Z "Following the lead from #17282, the ""View Post"" button next to the sample permalink is also just a link to another screen. I propose we get rid of it and make the sample permalink itself clickable" scribu 18245 Make the visual editor KSES filter/user capabilities aware Editor normal normal Future Release enhancement new 2011-07-25T18:11:21Z 2011-08-23T20:16:45Z "Currently the visual editor assumes ""unlimited html"" for all users. This can result in some surprises when a user doesn't have that capability. We can make a function that translates the KSES allowed tags and attributes into TinyMCE format and sets the editor accordingly." azaozz 16284 Remove the wpdialog plugin from TinyMCE azaozz Editor 3.1 high normal Future Release enhancement new 2011-01-18T14:26:28Z 2011-01-18T14:26:28Z "Combining TinyMCE with jQueryUI is not a very good idea IMHO: * TinyMCE has all the functionality to create dialogs which is native, more extended and seems more robust than jQuery UI. * The reason why most dialog type scripts use an iframe is to remove any possibility of conflicts with the parent page. In out case such conflict might be introduced by a plugin that alters the edit screen. * There were suggestions some time ago to stop using jQuery UI in WordPress admin and replace it with one of the other jQuery plugins with similar functionality that are a lot more concise and robust." azaozz 8368 Scheduling post time behavior and language refinements garyc40 Editor 2.7 low minor Future Release enhancement assigned early 2008-11-26T17:56:19Z 2013-01-22T17:38:00Z "On post editor, in publish module, at Publish Immediately-Edit. If click Edit, layer opens revealing the entry boxes for date and time of publication but still says Publish Immediately. Text should change to say ""Publish at:"" b/c it's weird if you change time and screen still says immediately until you click OK. Move OK button to the right side of module (submission buttons to the right as standard placement) with cancel to left (as with other places). If you start to type in an alternate time then hit cancel, it reverts to publish immediately, which makes sense. If you have already scheduled the publish time but you decide to change it and start typing a different alternate time, if you hit cancel it does not revert to your originally scheduled time, but to publish immediately. It should revert to your previously saved schedule time. Should have a separate link to revert to publish immediately. " jane 23630 Simplify the DFW implementation Editor normal normal Future Release enhancement new early 2013-02-26T16:44:57Z 2013-03-06T20:04:42Z "I was sad to see that distraction free writing [http://make.wordpress.org/core/2013/01/08/wordpress-3-6-distraction-free-writing-improvements/#comment-7469 didn't get picked up] for 3.6. I decided to play around with a rough proof of concept to see how difficult it would be to use the existing TinyMCE instance for DFW. Benefits of handling it this way include: - It eliminates the need (and complexity) of juggling multiple instances of TinyMCE - We'll be able to remove a bunch of the old DFW code - It makes the transition between regular mode and DFW mode much more smooth - It can be as fully featured as we want it to be" lessbloat 15139 Texteditor: link button always enabled Editor normal normal Future Release enhancement assigned 2010-10-17T08:27:06Z 2012-01-06T01:32:10Z "When you make a link you are forced to write the text in the editor and select the text before the link button is usable. I have seen users fail to understad this and getting stuck at creating links. It might be better if the link button was enabled as default and if no text was selected a textfield with the link text appeared in the insert/edit link. Another alternative is that the link text textfield (just mentioned) is visible all times but if text is selected it's written there by default. Otherwise it's left blank." olalindberg 11319 oEmbed should be integrated into Add ... from URL experiences Editor 2.9 normal normal Future Release enhancement new 2009-12-03T22:55:05Z 2010-10-28T08:50:33Z "oEmbed should be integrated into Add ... from URL experiences enhancement, ENV: WP 2.9-beta-2 ++ (trunk r12320) For WP 2.9 we removed oEmbed from the UI, #11288. The ""Embed"" field did not validate the oEmbed, that is part of the reason I recommended not incorporating UI for WP 2.9 -- I think JS based validation is essential to a good experience. If you use the ""Insert an image from another web site"", once you input a URL, WordPress should automatically check if it is an oEmbed link and adjust and populate the fields as appropriate. ADDITIONAL DETAILS If JS is disabled, I see little benefit to including a oEmbed form. The ability just to include oEmbeds on their own line in the content seems like a good balance." lloydbudd 6619 permalink field misleading in page editor: it displays the erroneous values Editor 2.5 normal normal Future Release enhancement new 2008-04-06T14:48:15Z 2009-11-20T20:32:33Z "if you create a sub-page, the permalink field should display the proper permalink. currently, if you have: site.com/page/ and when you create: site.com/page/subpage/ the permalink shows: site.com/subpage/ until it gets saved the expected behavior would be for it to show the correct permalink. the same remark applies when you then change the permalink. if the parent is no longer page, but rather page-2, then the permalink should update accordingly." Denis-de-Bernardy 11489 iTouch useability in the editor out of the box Editor 2.9 low minor Future Release feature request new dev-feedback 2009-12-19T03:47:58Z 2013-02-01T11:37:40Z "I have tried to write a post in 2.9 in iPod Touch and the text zone has some problems: * When you write the title, if you want to write the post the keyboard doesn't appear. You must move to another text-editable zone and go back to the main text zone to have the keyboard. * Once you have the keyboard, you have capslock activated and cannot deactivate it (you can deactivate letter-per-letter). I have tried in 2 different iTouchs with the same result. I put it as low because WordPress has an iPhone/iTouch app and don't know if happens the same in other mobile platforms. " bi0xid 17210 Massive duplication of oEmbed postmeta Viper007Bond Embeds 3.1 normal normal Future Release defect (bug) reopened dev-feedback 2011-04-21T23:38:35Z 2013-02-15T19:56:22Z "Hey guys, Ever since my blog grew to a considerable size (a few million PVs a month) and started slowing down and exploding my server, I've been looking and implementing various optimizations. During one such passes through the data, I noticed this really weird oEmbed related behavior, which I've been observing for a number of WP version upgrades. I use [embed] shortcodes a lot, and every new post after a few minutes ends up with a ton of oembed caches that don't belong to it at all - they're all from other posts. Posts that don't even have [embed]s at all still have over 100 oembed entries in wp_postmeta. Here's an example of just a small subset of data residing in the table: [[Image(http://farm6.static.flickr.com/5230/5641419581_0610c9e267_b.jpg)]] There are now about 150,000 entries in the wp_postmeta table due to this, half of which are duplicated _oembed entries, which I think has heavy impact on server load. Not only that but I'm sure WP is filling the table up with values by redoing oEmbed queries, which may explain that load shoots up very high at times when publishing. {{{ mysql> select count(*) from wp_postmeta where meta_key like '_oembed%'; +----------+ | count(*) | +----------+ | 81499 | +----------+ 1 row in set mysql> select count(*) from wp_postmeta; +----------+ | count(*) | +----------+ | 148451 | +----------+ 1 row in set }}} Just look at how many times this random video embed value shows up in the table. I'm sure it was used in only one actual post: {{{ mysql> select count(*) from wp_postmeta where meta_value like '%p2oWELcd-lI%'; +----------+ | count(*) | +----------+ | 815 | +----------+ 1 row in set }}} Just to clarify - I don't have 815 updates to a single post that may have explained this - these are completely unrelated, separate, published posts. To put things in perspective, here are the top 20 offenders: {{{ mysql> select distinct meta_key, count(*) as cnt from wp_postmeta where meta_key like '_oembed%' group by meta_key order by cnt desc limit 20; +------------------------------------------+-----+ | meta_key | cnt | +------------------------------------------+-----+ | _oembed_5607e41abb700707540a854ae76182cf | 864 | | _oembed_984bc07d3bc0f61b6b35230cd2fa7ced | 859 | | _oembed_da8ae36275b4576cfcd92c0ed455be96 | 859 | | _oembed_71dd4068a9a6911f50dbe57b3ff477c5 | 858 | | _oembed_9f817e820c23ccbfac9b22b3474e5dd3 | 858 | | _oembed_f3c1c03a81bc301b5f1a063f65119328 | 857 | | _oembed_31bf10d95cb7c8e9f646d9d6e5728da0 | 857 | | _oembed_25d0ebf59c994050cb604900cf04f53f | 856 | | _oembed_6265dae657e38579c0a8ddb66132d526 | 852 | | _oembed_562dd8c13888905cbd15dbd74e8699cc | 849 | | _oembed_30ea17d1cc73acd925a74373d2be32ec | 848 | | _oembed_87f16916b4da6571f454266bfbfaebe0 | 847 | | _oembed_9f1f038d43e973bd60929201eee24f57 | 843 | | _oembed_d46317d44fe11c0d90ef2cc3b45bce57 | 843 | | _oembed_b1f8685ba405feee46baf9408eb632f7 | 841 | | _oembed_1b56f492eba4c4ea698d816d0ecf2d51 | 840 | | _oembed_fe597714de4081e6e7e78a88256c7db4 | 840 | | _oembed_fb843e7b604cbc4e1ffa144d4eb300c8 | 839 | | _oembed_97b12f2f1e59ee6eff95c61095aa5bef | 838 | | _oembed_2b94d9f7c28ee37bfbead0a622c8be85 | 838 | +------------------------------------------+-----+ 20 rows in set }}} I'm quite at a loss here and would appreciate the next debugging steps. I haven't been able to determine where things are going wrong on my own. Thank you. P.S. The site in question is AndroidPolice.com" archon810 21632 Adding Imgur as an oEmbed provider markjaquith Embeds normal normal Future Release enhancement reopened dev-feedback 2012-08-19T15:51:15Z 2012-09-23T18:26:36Z Adding imgur to the list of oEmbed providers! (wcgr rocks) bradparbs 14759 Improve the way oEmbed deals with caching Embeds 3.0.1 normal normal Future Release enhancement new 2010-09-01T23:47:30Z 2013-03-15T07:57:59Z "As Matt pointed to me today, caching oEmbed results to post meta is kinda lame. I originally did this because I didn't want the HTML in old posts changing on it's own, say for example if the oEmbed provider got compromised. However I think that's extremely unlikely since we only whitelist major websites that can be trusted. Perhaps instead we should use transients to cache this data. That way when embed HTML is updated, posts will eventually be updated too due to expiring caches. I'm thinking a cache time of a week would be good, but with some random +/- to make sure multiple caches don't all expire at once. A good example of this is Vimeo. Anyone who embedded a Vimeo embed in their post before a few weeks ago got `