__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter
Commit Candidates 16942 Dead code in add_query_arg() General 3.1 normal trivial Awaiting Review defect new commit 2011-03-23T02:15:56Z 2011-03-29T09:31:33Z "As it just has been checked that $uri contains at least one ?, then exploding $uri on ? with a limit of 2 must return two elements, right?
{{{
if ( strpos( $uri, '?' ) !== false ) {
$parts = explode( '?', $uri, 2 );
if ( 1 == count( $parts ) ) {
}}}
So the if clause can never be true, the code is dead." hakre
Needs Dev / Bug Wrangler Feedback 16884 URL generation in setup-config's get_bloginfo() Upgrade/Install 3.1 normal normal Future Release defect new dev-feedback 2011-03-18T11:49:08Z 2012-06-02T19:12:24Z "See [http://php.net/manual/en/function.str-replace.php str_replace()]
Replacing some string with something in an **empty string** is obviously bogus." hakre
Has Patch / Needs Testing 16906 Bogus call to wp_kses_no_null() General 3.1 normal normal Awaiting Review defect new has-patch 2011-03-20T21:44:21Z 2011-03-20T21:45:23Z Nullchars and \ have been already replaced in string in question one line above. See [http://core.trac.wordpress.org/browser/tags/3.1/wp-includes/kses.php#L943 wp_kses_no_null()]. hakre
Has Patch / Needs Testing 16907 Redirecting w/o using wp_redirect(); General 3.1 normal normal Awaiting Review defect new has-patch 2011-03-20T22:00:28Z 2011-03-23T20:38:20Z Some places in worpdress core do not make use of the wp_redirect() function. hakre
Has Patch / Needs Testing 16890 Mutliple Location response headers can trigger notices HTTP normal normal Awaiting Review defect new has-patch 2011-03-18T17:08:33Z 2011-03-18T22:42:40Z "The current implementation for manual cUrl redirects (safemode / openbasedir restrictions, see #11305) will do notices and fail if a response contains more than one location response header.
Technically this is possible.
In the RFC I have not found any definition so far wether or not this is violating any standard or not not. Next to that I could gather no information how a HTTP client should interprete such a response.
For my fix I will prefer the first location header over any additional one." hakre
Needs Patch 16909 some Location headers are using relative url's (2) General 3.1 normal normal Awaiting Review defect new 2011-03-21T00:25:26Z 2011-04-02T13:24:37Z "I started this in #14062 and already did some fixes for 3.1.
Just collecting some more and providing patches." hakre
Commit Candidates 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
Commit Candidates 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
Commit Candidates 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
Commit Candidates 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
Needs Early Attention 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
Commit Candidates 14169 Slashes not removed when $_SERVER in process_conditionals() General 3.0 normal normal Future Release defect (bug) new commit 2010-07-01T20:40:28Z 2011-01-06T23:42:37Z Since [1964] (now after [12732] in {{{wp-includes/load.php}}}) slashes are added to all values of {{{$_SERVER}}}. If then {{{$_SERVER}}} is accessed, slashes must be removed again otherwise things might not work as intended, e.g. comparing and parsing strings. hakre
Commit Candidates 22663 Performing a non-square rotate() with Imagick, then cropping, can result in incorrect Image Media 3.5 normal minor Future Release defect (bug) new commit 2012-11-30T22:49:42Z 2013-05-07T20:38:29Z "Note: This is only for *some* recent versions of ImageMagick. Older ones seem to be a bit more sane, and work fine without any patch whatsoever.
When ImageMagick performs certain operations, it sets its virtual page's x/y origin values to non-zero numbers and leaves them there, which can break some further operations that depend on the virtual page.
In this case, when rotating in non 90 degree increments, Imagick doesn't set the x/y, which means that core doesn't run into this bug, since the built-in image editor only allows for 90 degree rotates in either direction.
However, if you're a user of the API, and perform a ""non-square"" rotate, then a crop, you could end up with an image result that differs from what you'll get from GD.
There are two ways of fixing this:
- Update the virtual page with each update_size()
- Update the virtual page immediately after a rotate() only
The first is what I think we should land on eventually, because it will prevent plugins' methods from breaking core's accidentally (if they do not reset the page's values). However, that would require an additional error message to be added, which means a new string.
The second would fix the bug for anything core's APIs would do, but would depend on plugins handling resetting the page values appropriately in their own methods. It is, however, a bit safer (and wouldn't require a string change), if this is something that might land for 3.5.
I've attached patches for each method." DH-Shredder
Commit Candidates 21534 Walker: has_children is only set if $args[0] is an array betzster Menus 3.0 normal normal Future Release defect (bug) new commit 2012-08-10T02:12:33Z 2013-04-23T02:09:53Z "You can't depend on `has_children` because it doesn't get set if `$args[0]` is an object. This is obviously an easy fix, just check if it's an object and set it in that case.
Related: #15214" betzster
Commit Candidates 17981 XML-RPC wp.getComments should work for non-admins XML-RPC 3.2 normal normal Awaiting Review defect (bug) new commit 2011-07-04T22:23:03Z 2012-03-08T13:35:11Z "Right now, if the caller doesn't have the moderate_comments permission, the XML-RPC call returns a 401 error.
A more graceful alternative would be to return the approved comments. The user may not be able to moderate, but still should be able to read/reply" koke
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 20938 Adding existing category duplicates default one Administration 3.3.2 normal minor Awaiting Review defect (bug) new dev-feedback 2012-06-13T13:52:18Z 2013-01-22T03:35:53Z In the post editing page, if you add a category which already exists, Wordpress duplicates the default category (Uncategorized), instead of showing a warning or doing nothing. hvsupr
Needs Dev / Bug Wrangler Feedback 21211 Alter how settings_errors are output in options.php Administration 3.4.1 normal normal Awaiting Review defect (bug) new dev-feedback 2012-07-10T23:44:37Z 2012-12-10T18:43:09Z "The `*_settings_error(s)` and `settings_error` functions are used mainly as part of the Settings API, but with the way that options.php currently handles the settings errors, it assumes that people will use this functionality exclusively with the Settings API. Notice options.php, starting at line 153:
{{{
/**
* Handle settings errors and return to options page
*/
// If no settings errors were registered add a general 'updated' message.
if ( !count( get_settings_errors() ) )
add_settings_error('general', 'settings_updated', __('Settings saved.'), 'updated');
set_transient('settings_errors', get_settings_errors(), 30);
}}}
This simply assumes that no other outside source has registered any sort of setting error other than the current options page. TwentyEleven does this, and so if any other source has registered any notices via these functions, the ""Settings saved."" message will not be output because the first bit of logic will fail. I don't think this assumption can (nor should) be warranted, so there needs to be another way to handle this so that themes like TwentyEleven who only call `settings_errors` at the top of their options page don't get unknowingly hijacked by other sources.
I always suggest registering your own errors at the end of the sanitization callback for your setting, and then output those specific errors within settings_errors to avoid any internal conflicts like this.
Just looking for some ways to approach this. :-)
" griffinjt
Needs Dev / Bug Wrangler Feedback 18530 Browser update dismiss setting ignored with JavaScript disabled Administration 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-08-27T15:41:24Z 2013-01-22T01:14:57Z "When working on a corporate desktop you can not update your browser. When freely deciding about when to upgrade you might not even want to upgrade.
Therefore a user setting has been introduced to remove the nag warning. E.g. my linux distro is perfectly ok with it's firefox and it's taken care of by the pacakager. For my OS, I have the latest version.
I needed to press dismiss (with JS enabled, the related report is #17766).
What has been missed is to not display that nag if javascript is disabled. The setting gets ignored.
How to Reproducde
* Setup a WP 3.2.1 Blog.
* Log into admin with a Firefox 3 browser.
* Enable Javascript.
* Dismiss the Nag.
* Logout and close the Browser.
* Restart the Browser.
* Disable Javascript (if you need to).
* Log into Dashboard.
Result: Browser Update Nag is displayed.
Expected Result: Browser Update Nag is not displayed as specified by the user." hakre
Needs Dev / Bug Wrangler Feedback 17413 Code added by WP_List_Table::_js_vars is duplicated sorich87 Administration 3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2011-05-13T09:45:49Z 2011-10-27T17:58:16Z When a list table is 'ajax enabled' (e.g. comments list table on edit-comments.php), javascript code is added by WP_List_Table::_js_vars to the footer. If you look at the source code in your browser, you will see that code is duplicated. sorich87
Needs Dev / Bug Wrangler Feedback 20595 Collapsible Admin menu fails if items are added by code Administration 3.3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2012-05-01T23:27:42Z 2012-05-02T07:48:13Z "If I add a Button to the admin meny by '''action adminmenu''' the menu wont rebuid from collapsed state due z-index issues. In my opinion creating the menue might be changed to the following:
{{{
diff --git a/wp-admin/menu-header.php b/wp-admin/menu-header.php
index cdd81b2..8454a3d 100644
--- a/wp-admin/menu-header.php
+++ b/wp-admin/menu-header.php
@@ -164,10 +164,6 @@ function _wp_menu_output( $menu, $submenu, $submenu_as_parent = true ) {
}
echo """";
}
-
- echo '
';
?>
}}}
see also: http://wordpress.org/support/topic/admin-menu-wont-dis-collapse-anymore" digitaldonkey
Needs Dev / Bug Wrangler Feedback 22214 Inconsistency in the show_ui parameter for register_post_type Administration 3.4.2 normal normal Awaiting Review defect (bug) new dev-feedback 2012-10-17T20:58:42Z 2012-10-18T00:58:36Z There is an inconsistency with the `show_ui` argument to `register_post_type`. When set to false, the post type listing page is open, while the 'Add new' page is not accessible. nofearinc
Needs Dev / Bug Wrangler Feedback 20453 Media screen links to non-public post types Administration normal normal Awaiting Review defect (bug) new dev-feedback 2012-04-16T02:31:56Z 2012-04-16T03:23:46Z "I have a non-public custom post type registered, so it doesn't get an admin UI.
A file in the media library is attached to one of my custom posts (done at the point the file is uploaded using `media_handle_upload()`). The media item shows up in the Media Library as expected, but the 'Attached To' column links to the editing screen for the parent post, even though the post is non-public.
This allows a user to see the post editing screen for a non-public post type." johnbillion
Needs Dev / Bug Wrangler Feedback 21770 Multiple New Feature Pop-ups mess UI Administration 3.4.1 normal normal Awaiting Review defect (bug) new dev-feedback 2012-09-02T11:09:51Z 2013-01-22T03:06:39Z "WordPress admin and plugins [[Image(http://dl.dropbox.com/u/184353/wordpress-admin-pop-ups.png)]] New Feature Pop-up messages appear on the admin simultaneously, blocking each other messages and functionality. The UI gets seriously messed up.
User attention focuses on how to get rid the overlaping pop-ups rather than reading the messages and understand and start using the new features." titanas
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 22700 Walker_Category_Checklist should sometimes set the value as the term name Administration 3.0 normal normal Awaiting Review defect (bug) new dev-feedback 2012-12-03T19:45:57Z 2013-02-19T05:12:08Z "The `Walker_Category_Checklist` class has been partially adapted to work with taxonomies other than `category`, but it does not seem to cope with non-hierachical taxonomies.
For non-hierachical taxonomies, the HTML form elements (checkboxes, radios, dropdowns, whatever) need to set the term **name** as the value, not the ID… otherwise WordPress will cast the ID to a string and create a new term with that string as a name.
To see the problem:
* Use `Walker_Category_Checklist` to create a checkbox in a metabox on the post edit screen for a non-hierarchical taxonomy
* Add some terms to the taxonomy
* Check the box for the taxonomy and update the post
* Watch a new term appear with its name set to the ID of the term you checked
" simonwheatley
Needs Dev / Bug Wrangler Feedback 19531 Wrong error message after correcting an error in username Administration normal normal Awaiting Review defect (bug) reopened dev-feedback 2011-12-13T10:07:56Z 2012-12-17T16:11:17Z "After entering an illegal username (fe. ""Wim (wim@go2people.nl)""), WordPress gives an error message saying:
""ERROR: This username is invalid because it uses illegal characters. Please enter a valid username.""
So far so good.
Now, when I correct the issue and click ""Add new user"" again, the above error message remains in the screen, while the illegal characters are no longer there and the actual error I am facing is that I forgot my password. Which is confusing for me.
The same occurs, when I enter an e-mail which has already been registered. I get the error message:
""ERROR: This email is already registered, please choose another one.""
When I correct, the error message remains, while this particular problem has been solved.
WP v: 3.3
Browser: Google Chrome 14.0 on Ubuntu 11.10
" wimfeijen
Needs Dev / Bug Wrangler Feedback 21989 update_option() calls sanitize_option() twice when option does not exist Administration normal normal Awaiting Review defect (bug) new dev-feedback 2012-09-25T05:04:34Z 2012-09-25T05:54:32Z "
I just spent several hours tracking down an issue when using the Settings API where `sanitize_option()` is called twice which is unnecessary execution especially if sanitization includes calling an external API for username/password authorization ''(this was how another developer set it up for a plugin I was debugging.)''
What happens is that a call to `update_option()` will call `sanitize_option()` and then if the option wasn't previously in the options table `update_option()` will delegate to `add_option()` which calls `santize_option()` a second time. This would normally be easy to workaround by first calling `get_option()` and testing for `false` and calling `add_option()` instead of `update_option()` if `false`, but not when the Settings API chooses how to call it.
I've looked at the problem and can envision several different ways to solve it such but don't know which the core developers would choose ''(or if they'd choose yet another option I haven't envisioned)'' so I didn't submit a patch:
- Adding a 3rd parameter `$mode` to `sanitize_option()` that identifies the mode ''('add', 'edit', default = 'unknown')'' and thus allow the hook to ignore one of the options ''(this would be more backward compatible but would put the onus on the developer to know to do this)'',
- Adding a 5th parameter `$bypass_sanitize` to `add_option()` defaulted to `false` that is only passed as `true` in `update_option()` allowing `update_option()` to disable the call to `sanitize_option()` found in `add_option()` ''(this would be less backward compatible and hacky, but seemless to the developer)''
- Adding a 3rd parameter `$bypass_sanitize` to `update_option()` defaulted to `false` that is only passed as `true` from `/wp-admin/options.php` allowing `update_option()` to bypass the call to `sanitize_option()` if an `add_option()` will happen ''(this would be less backward compatible and hacky, but seemless to the developer)''
- Have `/wp-admin/options.php` test for no pre-existing option and then call `add_option()` or `update_option()`, respectively ''(this would be seemless to the developer but less backward compatible and not hacky, and it wouldn't handle the general case.)''
So is this worth fixing to save other users and developers debugging time, and to reduce the chance of subtle errors in new code? If yes, how best to approach?" MikeSchinkel
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 21554 Problem with determining e-mail charset in wp-mail.php lizhenry Blog by Email 3.4.1 normal normal Awaiting Review defect (bug) assigned dev-feedback 2012-08-12T11:06:52Z 2012-08-29T13:58:26Z "In wp-mail.php the charset of the incoming e-mail message is determined on line 77 by taking the string between the second ""="" in the line and the end of line/second "";"" respectively.
'''The problem'''
If the header line in question looks like any of the following that method is perfectly fine:
{{{
Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
Content-Type: multipart/alternative;
}}}
However in messages sent from e.g. Gmail or Goolge Reader this header line usually looks like this:
{{{
Content-Type: multipart/alternative; boundary=f46d044516dd9cd71f04c70e55e8
}}}
I this case ""f46d044516dd9cd71f04c70e55e8"" is determined as the charset and the iconv function further down on line 187 returns false which causes the post content to be emptied.
'''Suggested solution'''
I personally think that it is better to have the post published with an ""incorrect"" charset than with no content at all.
Therefore I suggest that on line 76 in wp-mail.php...
{{{
if ( ! empty( $content_type[1] ) ) {
}}}
...is replaced by...
{{{
if ( ! empty( $content_type[1] ) && stripos( $content_type[1], 'charset' ) !== FALSE ) {
}}}
...in order to check if there is actually a charset definded.
Alternatively/additionally the return value of the iconv function on line 187 should be checked and the $content variable only modified if the return value doesn't equal FALSE." mighty_mt
Needs Dev / Bug Wrangler Feedback 14254 update_meta_cache fails; query too large? Cache 2.9.2 normal normal Awaiting Review defect (bug) reopened dev-feedback 2010-07-09T19:49:22Z 2013-03-13T10:10:05Z "In the file meta.php, around line 183 in the 'update_meta_cache()' function, it tries to do a query but I noticed this can fail (ie. crash wordpress) if there are too many post id's in the query.
The function is being called from query_posts(), with 'posts_per_page' set to -1.
An example query that crashed it:
{{{
SELECT post_id, meta_key, meta_value FROM wp_postmeta WHERE post_id IN (1009,1006,989,933,902,860,859,858,857,793,838,837,836,827,825,310,780,777,776,775,774,773,770,763,760,759,758,757,728,756,755,754,753,752,751,750,748,746,
732,736,729,726,725,724,723,722,720,719,717,716,715,710,709,503,692,289,625,268,593,583,582,332,32,30,28,26,24,22)
}}}
Maybe there is some limit associated with queries of this type internal to wordpress, as this query works fine in phpMySql.
Apologies if this is already reported or irrelevant in 3.0!
" newpixel
Needs Dev / Bug Wrangler Feedback 20902 redirect_canonical() on using permalink: Not all $_GET being redirected Canonical 3.4 normal normal Awaiting Review defect (bug) new dev-feedback 2012-06-11T09:30:08Z 2012-11-01T04:54:03Z "Using permalink, I suppose that all query_var entered manually on URL or using $_GET will be redirected to proper permalink. Apparently not all being redirected at all. AFAIC:
1. /?post_format=image : should be redirected to /type/image/
2. /?pagename=blog : should be redirected to /blog/
3. /?author_name=admin : should be redirected to /author/admin/
Unfortunately, they are not.
It can be done by filtering redirect_canonical() but it will be better if it's being done by default as we can see that /?category_name=cat will be redirected to /category/cat/" arieputranto
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 17714 Comment/pingback handlers don't check whether the post type supports comments Comments 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-06-07T06:09:02Z 2011-06-07T06:17:45Z "wp-comments-post and XML-RPC don't check post type support for comments before accepting them - I think they should. We can't rely solely on `$post->comment_status` because that may not always be set to ""closed"" even if the post type doesn't support comments (see also #13473)
Maybe we could add a check to `comments_open()`?" solarissmoke
Needs Dev / Bug Wrangler Feedback 18603 Comments on pages which exceed paginate settings create erroneous permalinks Mike Sagman http://www.dogfoodadvisor.com Comments 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-09-06T17:32:14Z 2013-02-07T17:09:36Z On my website, clicking on any of the Recent Comments that possess large numbers of comments exceeding paginate settings (50 comments) present erroneous permalinks. Only the posts containing enough comments on page 3 or higher present these improperly constructed links that take users to the wrong page (a page that does not contain the comment in question). The problem does not occur on pages containing a limited number of comments. So far, we have removed our Thesis theme and changed to the standard WP default theme. And we've deactivated all plugins. Yet neither solution appears to resolve the issue. Thanks for your consideration. You may view this issue live at http://www.dogfoodadvisor.com msagman
Needs Dev / Bug Wrangler Feedback 16976 Don't use photo as avatar class in comments Comments 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-03-27T00:54:44Z 2011-03-27T01:07:30Z "If you use an image in your post with class 'photo' to show it in Google's search results as a rich snippet is not possible if you make use of avatars in your comments. Google will pick the last class 'photo' image on the page to show as the search result.
Suggestion is to change the avatar class in comments to from 'photo' to 'comment-photo'. A post image is more important than a comment avatar to use for rich snippets." Okoth1
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 20262 "When ""Automatically close comments on articles older than X days"" is enabled, comments appear closed on draft posts" Comments 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2012-03-20T15:14:21Z 2012-09-05T17:12:08Z "If the setting to ""Automatically close comments on articles older than X days"" is enabled via Settings -> Discussion, comments automatically appear as closed on draft posts until the post is published. This is regardless of the Discussion settings configured on the Post Edit page for the draft post.
To replicate:
1. Via Settings -> Discussion, click on ""Automatically close comments on articles older than X days.""
2. Create a new post and save it as a draft. Make sure comments are enabled in your Discussion module.
3. When previewing the draft post, it will say ""Comments closed"" regardless of the Discussion settings.
The post will show comments as being allowed once it's published, they only show up as closed when in the draft format. " evarlese
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 23085 Calling $wpdb->query() when no connection exists causes mysql_error() to throw an error Database 3.5 normal minor Awaiting Review defect (bug) new dev-feedback 2012-12-30T10:30:49Z 2013-01-21T00:42:22Z "In the query() method of wp-db.php, the mysql_error() expects that if a parameter is passed to it then it should be a valid link identifier.
*May need feedback or added testing* ...this error may be specific to transactions, which is why it hasn't been noticed before. Unit tests do use transations and I only get these errors when ROLLBACK is called during specific unit tests that don't modify the DB state. A simple transaction opened & rolled back in the Debug Bar Console is not triggering this for me.
Unit test failure examples:
'''Test: test_is_image_positive'''
{{{
mysql_error() expects parameter 1 to be resource, integer given
Execution time: 0.02507209777832s
Stack Trace:
Array
(
[0] => Array
(
[file] => C:\xampp\htdocs\wpnew\wp-includes\wp-db.php
[line] => 1202
[function] => mysql_error
[args] => Array
(
[0] => 0
)
)
[1] => Array
(
[file] => C:\xampp\htdocs\wp_test_svn\includes\testcase.php
[line] => 25
[function] => query
[class] => wpdb
[type] => ->
[args] => Array
(
[0] => ROLLBACK
)
)
)
}}}
'''Test: test_is_image_negative'''
{{{
mysql_error() expects parameter 1 to be resource, integer given
Execution time: 0.02237606048584s
Stack Trace:
Array
(
[0] => Array
(
[file] => C:\xampp\htdocs\wpnew\wp-includes\wp-db.php
[line] => 1202
[function] => mysql_error
[args] => Array
(
[0] => 0
)
)
[1] => Array
(
[file] => C:\xampp\htdocs\wp_test_svn\includes\testcase.php
[line] => 25
[function] => query
[class] => wpdb
[type] => ->
[args] => Array
(
[0] => ROLLBACK
)
)
)
}}}
I don't think we should attempt {{{if ( $this->last_error = mysql_error() )}}}. That is because when mysql_error() is called without a link identifier then the most recent connection to MySQL is referenced. On a busy server this may not be the same connection as our page or transaction originally used. See #3544 for history/details." mbijon
Needs Dev / Bug Wrangler Feedback 22408 wp_insert_attachment and _real_escape input validation and better error handling Database 3.4.2 normal trivial Awaiting Review defect (bug) new dev-feedback 2012-11-10T21:47:03Z 2012-11-10T21:49:25Z "Recently when using the `wp_insert_attachment()` function I passed the whole result of the `wp_check_filetype()` function for the `""post_mime_type""` attribute, instead of the `""type""` property from the filetype check result. What I got was an error in the `_real_escape()` function which expected a string, but received an array, which didn't quite help me find my error.
I believe some kind of type checking would be nice for both the `_real_escape()` function as well as the `wp_insert_attachment()`.
It seems suitable if the `wp_insert_attachment()` function returned a `WP_Error` object in case there are issues with the passed arguments.
I'm not sure, however, what the best solution would be for the `_real_escape()` function -- return false, fail quietly, raise an exception or also return a `WP_Error`.
I would have proposed a patch, but I'm not sure what solution to implement. Let me know if I should do it in a certain way and I'll submit a patch for review, saving you a little time for other ticket review." magadanski_uchen
Needs Dev / Bug Wrangler Feedback 23227 Properly reflect date and time formats throughout admin area Date/Time 3.5 normal trivial Awaiting Review defect (bug) new dev-feedback 2013-01-17T19:37:21Z 2013-01-18T14:13:53Z "I have noticed several places in the admin area where the time & date formats set on the General Settings screen are not reflected. For example, on Page Edit, revisions have a hardcoded date format of `'j F, Y @ G:i'` and ajax autosaves use `'g:i:s a'` to show the ""Draft Saved at"" time (of note is the 24 hour vs 12 hour time). The ""Last Edited By _ on _"" time ''does'' properly use the time & date format options.
I have included a patch for the two examples above (comments/critiques welcomed), but there were a few others I noticed that may be somewhat more involved to fix. These include:
- Dates shown in the ""Date"" column of list tables (both the displayed and title text)
- ""Published on:"" date/time for pages (this may be tricky since editing the published time uses a 24-hour time format)
- ""Uploaded on:"" date/time shown in 'Save' metabox on Media edit screen
And there are probably other places I have missed as well.
Obviously somewhat low priority compared to other issues (and may be enhancement rather than defect), but I figured I'd bring it here and see what others thought." bananastalktome
Needs Dev / Bug Wrangler Feedback 23203 Scheduling Posts assumes GMT but UI uses local timezone (creating undesired scheduled posts) Date/Time 3.5 normal normal Awaiting Review defect (bug) new dev-feedback 2013-01-15T15:32:09Z 2013-01-16T13:16:59Z "I experienced an odd behavior when going to edit a page on a newly created site in a multisite environment. The site uses the New York timezone (GMT-5).
When quick-editing the page, I changed the title and slug, but pressing ""Update"" set the page as ""Scheduled"" rather than leaving it ""Published"". This was very confusing, and took a while to figure out and then explain to the end user. It seems that although the date/time is shown in the UI in the current time zone, once submitted the form interprets the time as if it were in GMT. To the end user, it looks like the page should be published since the time shows what we thought was a 5 minutes ago. In reality, the time in the date field is not recognized as 5 minute ago but 4 hours and 55 minutes in the future.
This is a problem in the full edit form for pages in this newly created site as well. When I go to edit the published time/date, the posted time in my timezone is shown. However, ''even if I hit 'Cancel' the ""Update"" button changes to ""Schedule""''." bananastalktome
Needs Dev / Bug Wrangler Feedback 16477 """View post"" link should not change when sample permalink changes" Editor 3.0 normal normal Awaiting Review defect (bug) new dev-feedback 2011-02-07T08:15:26Z 2011-12-18T23:54:38Z "To reproduce:
- Go to edit a post
- Change the permalink
- Click on ""View post"" and you get a 404 because the href has been changed to the new sample permalink but the post hasn't been updated yet
The ""View post"" link should always point to the permalink of the currently saved post." solarissmoke
Needs Dev / Bug Wrangler Feedback 19947 Copy paste behavior in Visual mode differs from HTML mode Editor normal normal Awaiting Review defect (bug) new dev-feedback 2012-02-02T13:13:11Z 2012-02-02T13:13:11Z "Copy a random html page from a random site including links and images and paste it into the WYSIWYG Editor Visual mode and it will include the images and links. Basically it (mostly) looks like the copied page. If you paste the same into the WYSIWYG Editor HTML tab and it will strip out _all_ HTML markup and just leaves the plain text, without the images or links.
Expected:
I would expect the Visual and HTML mode of the WYSIWYG editor to behave the same, either both use the code (displaying the results of the markup code in the Visual tab and the markup code itself in the HTML tab) or both strip out all html.
" BjornW
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 22996 IE8 - Hierarchical Taxonomies with bulk terms cause massive slow-down / freeze Editor normal minor Awaiting Review defect (bug) new dev-feedback 2012-12-18T19:18:02Z 2013-01-06T08:07:28Z "For a project, we have about 550+ terms in a single taxonomy, the other taxonomies have around 10-40 each themselves too. There appears to be an issue when IE8 comes across too many checkboxes on a page, and this recently was exacerbated by an upgrade to WP 3.5. The upgrade itself didn't cause it, but it coincided with the addition of a few new terms (don't know how many were added before the upgrade just yet, will post if I find out more info).
To reproduce, you've gotta have a large amount of terms for your taxonomies, then go into the post editor (for whatever post type you're testing on), and ensure your taxonomies have 'hierarchical' set to true in their definitions. I've seen the issue crop up on save (on subsequent load of the page w/ success message on it), and on open of the edit page itself.
The issue seems to be more severe for IE8 on Windows XP Service Pack <= 1, but I've seen it cause a massive slow-down for newer XP versions, just not freeze up entirely like it did on the XP SP 1 machine I was primarily testing on.
''I'm not really sure'' what the solution is going to have to be here, or if this will serve merely as a paper-trail for the folks searching for information about this.
I did a blanket forceful change for checkbox input to autocomplete on the meta boxes associated to hierarchical taxonomies using the following Gist to resolve the freezing for now:
https://gist.github.com/4330772
Here's the info you'll probably ask for, I went down to the basics to see exactly what the cause was:
1. No plugins activated (except a small plugin that had the Gist in it to resolve the issue for me)
2. Standard Twenty Twelve theme activated
3. Tested and found the issue happening on both WP 3.4.x and WP 3.5
4. Tested on XP SP 1 with IE8, saw the greatest degradation of performance here
5. Tested on XP SP 3 with IE8, saw a noticeable freeze and then slow-down of performance as the page loads here" sc0ttkclark
Needs Dev / Bug Wrangler Feedback 19645 Image caption gets removed when editing image dimensions. Editor 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2011-12-22T16:24:34Z 2011-12-23T18:25:53Z "When editing an image placed into a post in a certain way, the caption of the image is removed.
Steps to reproduce:
1. Edit a post that contains an included image.
2. Click the edit options icon when selecting the image.
3. Go to the advanced image settings(make sure the image does have a caption).
4. Empty the width field.
5. Press the submit button.
-> The caption of the image is set empty.
Remarks,
In my case only leaving the width input field blank caused this issue." JanJaapKempenaar
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 21934 Title field on Insert/edit link form shouldn't allow autosuggest Editor 3.4.2 normal normal Awaiting Review defect (bug) new dev-feedback 2012-09-19T21:10:18Z 2012-09-20T22:37:44Z "When entering a link through the ""Insert/edit link"" thickbox form, Firefox displays autosuggest dropdowns for both the URL field and the title field.
This would be helpful, except that the javascript keyboard handlers bound on keydown/keyup prevent the browser UI from being accessible.
What happens is:
1. User tries to add link to text through the editor (Visual or HTML).
1. User enters the correct URL into the URL field, and exits that field by hitting ""tab"".
1. User begins typing the link title. Firefox browser UI helpfully suggests some similar titles.
1. User sees a title they'd like to use, and hit the keyboard down arrow, thinking that this will select the correct title for them.
1. What actually happens is that the first link listed below in the link to existing content gets selected. This overwrites what's been entered in the URL and title field.
1. User says, WTF just happened.
Solutions:
- Adding `autocomplete=""off""` to these two form fields would prevent Firefox from displaying its autosuggestions. This might fix the problem, but feels kind of like a bandaid.
- A keydown/keyup handler could be attached to each of the text input fields with event.stopPropagation could stop the ui keyboard behavior when typing into those fields." goldenapples
Needs Dev / Bug Wrangler Feedback 20073 When I publish a draft the posting date is not updated Editor 3.3.1 normal major Awaiting Review defect (bug) new dev-feedback 2012-02-18T20:39:13Z 2012-02-19T15:23:57Z "I believe this was a bug previously that has come back with the latest version. If you create a draft post and edit it over time, then publish it the date is NOT automatically adjusted to the date you publish. It keeps the original date the post was created as a draft, thus putting it behind in the RSS feed and on your posting list. This used to be an issue before, and seemed to be corrected and has come back up again
Steps to re-produce:
1) Create a draft today
2) Wait a couple days then publish
3) You will see the ""published Date"" is the date it was created NOT the date it was published
This also happens with scheduled publishes " ccolotti
Needs Dev / Bug Wrangler Feedback 22392 save_state() in postbox.js should look at the hidden checkboxes instead of :hidden Editor normal normal Awaiting Review defect (bug) new dev-feedback 2012-11-08T16:05:28Z 2012-11-08T18:11:13Z "At this moment save_state() looks at all the metaboxes that are really hidden with filter(':hidden'). With can lead to weird behavior when a plugin starts to hide a metabox in some cases since it can be showed/hidden by default.
I was wondering if it is possible to look at the checkboxes and mapped them as a string and pass it to the AJAX action closed-postboxes." markoheijnen
Needs Dev / Bug Wrangler Feedback 19354 wp_allowed_protocols() does not allow data URI scheme Editor 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-11-25T03:34:46Z 2012-03-26T03:27:19Z "When inserting images into a post via copy-paste, Firefox will paste a base64 text string (using the Data URI scheme) into the post editor. The result will look something like:
When the post is saved, the ""data:"" portion of the src attribute is stripped away by wp_kses_hair() via the line:
if ( in_array(strtolower($attrname), $uris) )
$thisval = wp_kses_bad_protocol($thisval, $allowed_protocols);
""data:"" is treated as a protocol prefix, and is not seen as part of the src attribute.
To reproduce this error, try the following in Firefox:
1) Do a Google image search for a rendom image.
2) Right-click -> ""Copy Image""
3) Paste into rich text editor
4) Save post
5) View HTML tab of the editor and notice that the ""data:"" scheme has been removed.
A side effect of this issue is that the image src is treated as a relative image path on the server (in subdirectory ""image/png"" with long string of characters as the ""file name."" The server will typically report an error in its log file about the request length of the URI being too long." hardy101
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 23364 Unstable sorting with jQuery UI 1.9.1 and above External Libraries 3.5 normal normal Awaiting Review defect (bug) new dev-feedback 2013-02-02T03:07:18Z 2013-02-02T03:09:35Z "There seems to be an issue with jQuery UI (sortable) 1.9.1 and above that affects (rather severely) sorting of elements inside sortable source and target containers. I haven't seen this affect core, but since WP has been shipping with one of the affected versions (1.9.2) since 3.5, I'm worried about potential repercussions on WP theemes, plugins or projects relying on this script. For instance, Ultimate Tinymce, by Josh Lobe and myself (recently), has been affected by this.[[BR]]
[http://elblawg.com/jqueryui-test/ Here] is a testing platform I created on my server about the problem. Choosing any version of UI newer than 1.9.0 will result in said behavior.[[BR]]
[http://bugs.jqueryui.com/ticket/9041 Here] is the ticket I submitted to jquery UI Trac and [https://github.com/MarventusWP/jquery-ui/commits/master here] the Commits to their github project.[[BR]]
Finally, as recommended by Andrew Nacin on the wp-forums list, [http://jsfiddle.net/Marventus/THwqS/1/ here] is a JSFiddle that reproduces the problem.[[BR]]
I am not really sure what to do about this, but I thought I should leave it on record just in case.
Thanks!" Marventus
Needs Dev / Bug Wrangler Feedback 21225 Dashboard Incoming Links - Google blogsearch fails when get_option( 'home') is not a TLD Feeds 2.5 normal minor Awaiting Review defect (bug) new dev-feedback 2012-07-12T02:47:09Z 2012-07-12T04:23:56Z "When WordPress gets installed and the first time a user visits the dashboard the dashboard_widget_options get set for dashboard_incoming_links. The Google blogsearch link gets set based on your settings for wp_home. If your developing on a local machine most likely wp_home is not a true TLD.
Google blogsearch incorrectly returns incoming links when the site: url is not a true TLD. For example I'll use an install where wp_home is set to http://wp.patch. The link that gets formed is:
http://blogsearch.google.com/blogsearch_feeds?scoring=d&ie=utf-8&num=10&output=rss&partner=wordpress&q=link:http://wp.patch/
If you visit that link you will notice that results are getting returned just using the ""patch"" keyword.
If the sited gets moved to live production you will continue to get the incorrect incoming links unless the dashboard_widget_options get manually changed or deleted.
Also to note is that the Google blogsearch API has been deprecated: https://developers.google.com/blog-search/
My suggestion is to remove the widget or hide it by default in screen options like we did for some of the stuff in post.php.
Another option is to do a check and return WP_Error if wp_home is not a TLD before setting the dashboard widget options." c3mdigital
Needs Dev / Bug Wrangler Feedback 10984 If content uses the nextpage tag then only the first page is shown in feeds Feeds 2.8.4 normal normal Future Release defect (bug) new dev-feedback 2009-10-20T11:03:11Z 2012-08-27T17:40:40Z "If content uses the nextpage tag then only the first page is shown in feeds if the ""full text"" option is selected in ""Settings > Reading > Show Full Text (in feed)"".
No links are displayed to read the full content and no indication is given in the feed that it isn't the full content.
I think the behaviour should be to ignore pagination in feeds which are set to ""full text"".
I have attached a patch which alters the behaviour of the_content() so that if it is used in the context of a feed it concatenates the pages to form the full content and returns that." simonwheatley
Needs Dev / Bug Wrangler Feedback 13066 Last-Modified headers for individual comment feeds are incorrect jgci* Feeds 3.0 low normal Future Release defect (bug) accepted dev-feedback 2010-04-21T07:32:34Z 2010-11-28T16:18:31Z "The WP::send_headers function currently uses get_lastcommentmodified() to set the Last-Modified header for all comment feeds. This is a problem when used for individual post comment feeds. The function gets the last modified comment across all blog posts. That means that every time a comment is posted anywhere, the Last-Modified header for ALL comment feeds is refreshed. Issues:
1. This is technically incorrect, since only the global comment feed and one specific post's comment feed have changed with the last comment (not all possible comment feeds); and
2. It means that If-Modified-Since requests for other post comment feeds will not receive a 304 response when they should do (since their content hasn't changed). On blogs with many posts and many comment feeds, this will have a large impact on bandwidth because lots of requests will receive 200 responses where 304's would have done, just because a comment was posted on some other post.
If I've understood the flow correctly, $wp_query hasn't been fully set up at the time this function is called, so changing this behaviour would require some change in the flow of things (e.g., the handling of last modified headers for feeds moves into the do_feed() function). But doing so would mean that Last-Modified headers are correct/meaningful and that many more 304 responses can be served.
Any thoughts?" solarissmoke
Needs Dev / Bug Wrangler Feedback 10713 Output encoding not set in fetch_feed Feeds 2.8.4 low normal Future Release defect (bug) new dev-feedback 2009-09-01T15:56:15Z 2012-12-13T20:30:56Z "If using WP Super Cache (or a similar plugin) on a blog with a non-UTF-8 charset that has an RSS widget then the charset is incorrectly changed to UTF-8 by SimplePie.
The fix is to explictly set the encoding in fetch_feed before SimplePie sends any headers (which it only does if WP Super Cache is being used, since it checks if any headers have already been sent).
{{{
*** live/wp-includes/feed.php 2009-05-25 11:13:48.000000000 +0200
--- dev/wp-includes/feed.php 2009-09-01 17:40:19.000000000 +0200
***************
*** 552,557 ****
--- 552,558 ----
$feed->set_file_class('WP_SimplePie_File');
$feed->set_cache_duration(apply_filters('wp_feed_cache_transient_lifetime', 43200));
$feed->init();
+ $feed->set_output_encoding(get_option('blog_charset'));
$feed->handle_content_type();
if ( $feed->error() )
}}}
I've put this as low priority since I guess most blogs use UTF-8 and don't use WP Super Cache." iansealy
Needs Dev / Bug Wrangler Feedback 15110 Useless MIME type served for rss feeds Feeds 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-10-13T14:16:54Z 2012-06-05T08:37:39Z "Both /feed/, /feed/rss2/, and /feed/rss/ are served using the very undescriptive and generally useless ""text/xml"" MIME type. ATOM and RDF feeds are served with their proper MIME types. It looks like the MIME types for RSS are in feed.php, but for some reason there is a special ""rss-http"" type that returns the useless type? Changing the first line in feed-rss.php and feed-rss2.php to use the rss and rss2 type instead of rss-http fixed it on my site." singpolyma
Needs Dev / Bug Wrangler Feedback 13049 Wordpress should not generate feeds for 404 pages Feeds 3.0 low normal Future Release defect (bug) reopened dev-feedback 2010-04-19T11:32:20Z 2010-12-05T22:04:49Z "Say I try to visit: `http://my.blog.tld/non-existent-slug/`, (where non-existent-slug is not a valid slug) I get a the normal 404 template.
However, if I try to visit `http://my.blog.tld/non-existent-slug/feed/`, then the response is a bit weird. A 404 response header is sent but the content is nonetheless sent through the feed template. And so you get something like this:
{{{
A Sandbox » Page not found
http://my.blog.tld
Just another WordPress weblogMon, 19 Apr 2010 11:17:05 +0000http://backend.userland.com/rss092en
}}}
Assuming this isn't intentional (I can't think why it would be), this should be changed so that the content is the normal 404 template." solarissmoke
Needs Dev / Bug Wrangler Feedback 19643 Allow array for $extra_fields in request_filesystem_credentials Filesystem 3.0 normal minor Awaiting Review defect (bug) new dev-feedback 2011-12-22T07:47:38Z 2012-09-10T22:54:04Z The current implementation for passing extra fields through request_filesystem_credentials() does not allow for an array of data to be passed. I came across this issue when trying to process a bulk installation of plugins with my plugin installation class. My patch fixes this from what I can tell and doesn't break anything that I can see from my testing. griffinjt
Needs Dev / Bug Wrangler Feedback 19543 Broken formatting when using HTML5 element Formatting 3.3 normal normal Awaiting Review defect (bug) new needs-unit-tests 2011-12-14T10:32:07Z 2012-10-12T18:25:51Z "When using HTML5 element, the resulting markup is invalid because some paragraphs isn't closed properly.
Reproduced with WP 3.3, TwentyEleven theme and no plugins.
Example markup attached to this ticket. Paste into html view of the WYSIWYG editor and publish. Resulting markup also attached. " exz
Needs Dev / Bug Wrangler Feedback 12690 Square brackets breaking links that contain square brackets Formatting normal normal Future Release defect (bug) reviewing dev-feedback 2010-03-24T19:16:50Z 2012-09-19T22:40:34Z "In the editor, wrapping square brackets around an anchor with a URL that contains square brackets, like so
{{{
[photos by KeepCalmPosters ]
}}}
converts the last double prime in the href attribute to the character code for the right double quotation mark, like so
{{{
[photos by KeepCalmPosters ]
}}}" iandstewart
Needs Dev / Bug Wrangler Feedback 17571 bad double quote replacement in wp_texturize Formatting normal minor Future Release defect (bug) new dev-feedback 2011-05-26T09:18:08Z 2012-04-30T12:49:51Z "Bug seen in Wordpress 3.1.2. with buddypress 1.2.8
Some database fields that contain a string like this 'a string with \""escaped double quotes\""' are displayed this way : 'a string with >>escaped double quotes>> ' instead of 'a string with <>'
The bug come from wp_texturize function in wp-includes/formatting.php .
I join a patch to resolve this issue.
" csanquer
Needs Dev / Bug Wrangler Feedback 16859 esc_url eats square brackets. westi* Formatting 3.1 normal minor Awaiting Review defect (bug) accepted dev-feedback 2011-03-15T17:28:32Z 2013-02-19T12:30:30Z "When adding a link to the blogroll (using wp-admin/link-add.php), square brackets in the link are removed, breaking the link.
Example:
{{{
http://lokale-wochenzeitungen.de/index.php?id=485&tx_ttnews[pointer]=6&tx_ttnews[tt_news]=132583&tx_ttnews[backPid]=741&cHash=ee9c87874b
}}}
becomes
{{{
http://lokale-wochenzeitungen.de/index.php?id=485&tx_ttnewspointer=6&tx_ttnewstt_news=132583&tx_ttnewsbackPid=741&cHash=ee9c87874b
}}}
Workaround: Use URL-encoded links (%5B and %5D instead of [ and ]).
This also affects urls which are made clickable by {{{make_clickable}}" f00f
Needs Dev / Bug Wrangler Feedback 19028 make_clickable fails when contains \r characters Formatting 3.2.1 normal minor Awaiting Review defect (bug) reopened needs-unit-tests 2011-10-22T07:00:35Z 2011-11-02T00:34:43Z "Hi.
I'm using the make_clickable php function in my project SaltOS to add the links feature to the email client and feeds reader.
I detect that when try to make clickable the urls that has the link tag and this tag contains \r characters it fails.
I fixed the problem removing all \r of the tag but understand that can be a possible bug.
Thanks in advance." josepsanzcamp
Needs Dev / Bug Wrangler Feedback 14050 shortcode_unautop() should also remove the added after shortcodes Formatting 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-06-22T18:15:27Z 2013-01-19T08:38:00Z "Currently `wpautop()` wraps a shortcode in `
Once
I saw it here, I instantly knew what I wanted. I love my new woven wood
shades.
- Ginny Good
}}}
" Denis-de-Bernardy
Needs Dev / Bug Wrangler Feedback 13429 Updating Link URL on image within Admin with Gallery Gallery 2.9.2 normal normal Future Release defect (bug) new dev-feedback 2010-05-18T01:43:42Z 2013-01-02T13:11:27Z "Image insertion no longer allows url to off site resource within Gallery.
When inserting a gallery you are unable to specify the Link URL. It keep reverting back to the default." vshoward
Needs Dev / Bug Wrangler Feedback 16164 """You are not allowed to delete this post."" - While Deleting a Media Library Item" General 3.1 normal normal Future Release defect (bug) new dev-feedback 2011-01-09T13:39:10Z 2012-06-30T20:14:21Z "While deleteing 999 media library items, the request timed out. Resending the same request triggered an error message:
> You are not allowed to delete this post.
For me as a programmer, I know that those library items are technically a post, but for communicating with the user, the error message is misleading." hakre
Needs Dev / Bug Wrangler Feedback 21581 Add orderby meta_value to WP_User_Query General normal normal Awaiting Review defect (bug) new dev-feedback 2012-08-14T21:24:05Z 2012-08-14T21:40:10Z "For some reason, we cannot easily order the WP_User_Query() by last_name without directly editing the SQL statements. However, there is an easy way to add this that would work parallel to WP_Query().
{{{
// prepare arguments
$args = array(
'orderby' => 'meta_value',
'meta_key' => 'last_name',
);
$user_query = new WP_User_Query( $args );
}}}" wpsmith
Needs Dev / Bug Wrangler Feedback 16672 Admin Bar and param href = FALSE General 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-02-26T00:21:52Z 2011-02-27T11:21:37Z "Current i dont find an solution to add an element in the admin bar with a a-tag inside the li-tag. But the function add_menu has an param href and is also possible to add the value false, but the a-tag ist always visible
maybe a fix on wp-includes/class-wp-admin-bar.php
{{{
/* Helpers */
function recursive_render( $id, &$menu_item ) { ?>
query_vars['suppress_filters'])
{
if (!is_home())
$post_type = array('video', 'post');
$query->set('post_type', $post_type);
}
return $query;
}
add_filter('pre_get_posts', 'add_posttypes_to_query');
}}}
The error I get is: “Warning: Illegal offset type in isset or empty in /home/lxg/www/shops.supreme.de/supremeshops/branches/private_wp3/wp-includes/post.php on line 811”.
It appears that the function {{{get_post_type_object}}} gets the array passed if no posts were found.
Also, I realized that custom post single pages don't issue a HTTP 404 status on errors. But this may be due to local modifications. I am currently not able to set up an environment where I isolate this problem." mastermind
Needs Dev / Bug Wrangler Feedback 18503 Delete-Plugin Error Validation Clears Form Values General 3.2.1 normal minor Awaiting Review defect (bug) new dev-feedback 2011-08-23T22:43:22Z 2011-09-01T17:17:22Z "When bulk-deleting a set of plugins, if an error is encountered - all selected values are lost.
Process:
1. Go to plugins overview screen, select several (active) plugins to delete.
2. From the bulk-action dropdown menu, select ""delete"", then ""apply""
Expected behaviour:
Error message: ""You cannot delete a plugin while it is active on the main site."" - Check marks are preserved, so you simply select ""deactivate"" and click on ""apply"" again.
Actual behaviour:
Error message: ""You cannot delete a plugin while it is active on the main site."" - All check marks lost, and you have to start all over again - which is a pain for sites with lots of plugins." JohnONolan
Needs Dev / Bug Wrangler Feedback 21432 Deprecate *_blog_option() ryan General 3.4.1 normal normal Future Release defect (bug) reopened dev-feedback 2012-07-31T21:53:06Z 2012-10-24T17:44:45Z "Deprecate get_blog_option(), add_blog_option(), update_blog_option(), and delete_blog_option(). The regular *_option() functions wrapped with switch_to_blog() and restore_current_blog() should be used instead.
Previous discussion:
http://core.trac.wordpress.org/ticket/21270#comment:11" ryan
Needs Dev / Bug Wrangler Feedback 15963 Don't try to add orphaned pages' parents' slugs to the page URL General 3.1 normal normal Future Release defect (bug) new dev-feedback 2010-12-23T11:08:55Z 2012-09-19T22:31:20Z "If a page becomes orphaned---in other words, if a page points to a parent object that doesn't exist any more---`get_page_uri()` doesn't sanity check that the parent object actually exists.
Patch does the check without any extra work, by moving stuff around." filosofo
Needs Dev / Bug Wrangler Feedback 21537 Email address sanitisation mangles valid email addresses General 3.4.1 normal normal Awaiting Review defect (bug) new dev-feedback 2012-08-10T11:24:50Z 2013-01-22T09:00:07Z "If you change your email address to one including an ampersand then we mangle the address with html entities.
For example:
* This - peter&paul@sitting.in.a.tree.com
* Becomes - peter&paul@sitting.in.a.tree.com
This is due to the call to {{{wp_filter_kses}}} on {{{pre_user_email'}}} in {{{default-filters.php}}}.
The was added in [5906] for #4546.
I'm not sure if we need kses filtering for emails - if we do which should probably revert this conversion of the & => & afterwards." westi
Needs Dev / Bug Wrangler Feedback 18002 Entering page number for spam comments takes you to page 1 General 3.2 normal normal Future Release defect (bug) new dev-feedback 2011-07-06T11:27:25Z 2011-11-22T17:17:15Z When browsing through spam comments, I attempt to view pages in the middle of the set (e.g. page 9 of 13) using the number-entry feature (at the top right) introduced in WP 3.1. Unfortunately, in WP 3.2 this feature has been broken, and when I press Enter, it substitutes '1' for the page number I enter, and then takes me to page 1. I have tried this when browsing posts or normal comments, and it doesn't happen; it only happens when viewing spam comments. I have tried it on Chrome in Linux and Safari on Mac OS X and the same thing happens. IndigoJo
Needs Dev / Bug Wrangler Feedback 12760 Escaping shortcode conditionally markjaquith General 3.0 low normal Future Release defect (bug) assigned dev-feedback 2010-03-29T12:21:55Z 2011-04-07T00:11:32Z "Using additional brackets is the official way to ""escape"" a shortcode. e.g. {{{[[escaped]]}}}
Using additional brackets {{{[[shortcode]]}}} in a post works only when the plugin (function) for this shortcode is active. When deactivated, additional brackets are shown in the post. It is annoying for many users, because editors sometimes test a plugin, write about it in a post with shortcode example and after some months this plugin is deactivated. Now there will be additional brackets, breaking their example code.
Input:
{{{[[shortcode_that_does_not_exist]]}}}
Expected output, regardless of whether that plugin is active:
{{{[shortcode_that_does_not_exist]}}}
Actual output, if plugin is not active:
{{{[[shortcode_that_does_not_exist]}}}
[edited by Mark Jaquith]" pavelevap
Needs Dev / Bug Wrangler Feedback 18685 GET Requests with hostname in them causes wrong redirect General 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-09-16T14:34:54Z 2011-10-07T08:49:01Z "Hi!
I have noticed that my Android phone when using Cyanogenmod with default browser does some ""special"" things when on 3G. (It does not happend via WiFi)
It appears that the hostname is sent with every GET-request. Its common to only send the path in a GET-request but the HTTP secification also allows for the use of hostname within a GET-request.
My test page ( http://h3x.no/dump/test.php ) shows the hostname in the REQUEST_URI via 3G, and skips the hostname when on WiFi.
This causes Wordpress(i suspect) to redirect me to the wrong page.
Example:
I want the page:
http://h3x.no/2011/09/12/getting-windows-2008-server-uptime-via-the-command-line
My phone sends me to:
http://h3x.no/2011/09/12/getting-windows-2008-server-uptime-via-the-command-line/http/h3x.no/2011/09/12/getting-windows-2008-server-uptime-via-the-command-line" Ueland
Needs Dev / Bug Wrangler Feedback 15619 General Settings Tab Not Allowing trailing URL slash to be stored in Site & WordPress address (URL) General 3.0.1 normal normal Future Release defect (bug) reopened dev-feedback 2010-12-01T02:35:11Z 2011-01-21T10:15:11Z "**Thank you for all of the efforts you've made regarding plugins easier to maintain - I deeply appreciate it.**
When WordPress is installed in a subfolder, attempts to add the trailing slash currently will not save properly. From this URL:
http://www.domain.com/wordpressinstalledinfolder/wp-admin/options-general.php
The General Settings Tab - WordPress address (URL)
The General Settings Tab - Site address (URL)
Want to enter ""http://www.domain.com/wordpressinstalledinfolder/""
***it won't let me enter a trailing slash on the end like it will in other URL fields on the site.***
Request: Please tweak this field to allow storage of folder trailing slash.
" dsquared
Needs Dev / Bug Wrangler Feedback 17296 Link Descriptions Are Truncated Without Notification General 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-05-01T03:04:09Z 2011-07-03T07:48:46Z "When creating new links, or editing existing links, using the WordPress admin interface, link descriptions are truncated to 255 characters. This is because there is a 255 character limit defined in the link_description column in the wp_links database table.
Steps to reproduce:
1) Go to WP dashboard
2) Select Links > Add New from the menu.
3) Create a link with a description longer than 255 characters.
4) Go back to the link in the links interface; the description has been truncated.
Expected behavior:
1) The field should have a larger limit (perhaps 1024 characters?).
2) Even if we keep the limit at 255, the UI should prevent users from entering more than the limit, or notify them that the description they have entered will be truncated to the limit.
Thanks for your time!" achmafooma
Needs Dev / Bug Wrangler Feedback 17491 Make is_email() compliant with RFC2822 General 3.1.2 normal minor Future Release defect (bug) reopened dev-feedback 2011-05-18T14:48:52Z 2013-01-10T11:02:05Z is_email('toto.@toto.com') returns true arena
Needs Dev / Bug Wrangler Feedback 16482 Visibility: password-protected breaks with redirected domains General 3.0.4 normal minor Awaiting Review defect (bug) new dev-feedback 2011-02-07T18:58:45Z 2012-09-05T18:47:28Z "Pre-requisite to reproduce: domain.com must redirect to www.domain.com (haven't tested with other subdomains than www, but I'm sure it would be the same).
1. password protect a page
2. visit domain.com/protected (which redirects to www.domain.com/protected)
3. enter password
4. something about the redirect OR the way the password is stored/checked is broken; you are redirected to the wp-admin (WordPress login) page.
Sanity check:
1. password protect a page
2. visit www.domain.com/protected (requiring no subdomain redirect)
3. enter password
4. successful log-in
" monkeyhouse
Needs Dev / Bug Wrangler Feedback 12016 get_calendar can output a calendar when there are no posts General 3.0 normal normal Future Release defect (bug) reviewing dev-feedback 2010-01-25T17:54:31Z 2010-11-13T09:06:16Z "If a site doesn't have any posts, get_calendar isn't supposed to display a calendar. You can visit a page or have a static home page, and a calendar is displayed. The get_calendar function is looking at global $posts to determine if the site has posts but this variable can contain data from other post_types.
r12821" mtdewvirus
Needs Dev / Bug Wrangler Feedback 20853 get_post_custom show directly serialized data from the post_meta arrays. General 1.5 normal minor Awaiting Review defect (bug) assigned dev-feedback 2012-06-06T05:39:23Z 2013-03-11T16:46:21Z "get_post_custom show directly serialized data from the post_meta arrays.
For example:
If I save a data with:
{{{
update_post_meta( $post_id, 'camp',
array(
'some' => $var,
'thing' => $var_2
)
);
}}}
When I use get_post_meta(); :
{{{
$var_get = get_post_meta($post_id, 'camp', true);
echo $var_get['some']; // Fine.. Print: $var content.
}}}
but, when I use get_post_custom() :
{{{
$var = get_post_custom($post_id);
echo $var['some']; Metod, (Not work because ""Returns a multidimensional array"" with all values, and 0 is the first or the unique value).
echo $var['some'][0]; /* Metod, >:( , Not work. Print:
a:2:{i:some;s:4:""this"";i:thing;s:7:""content"";} */
}}}
Instead of display ""array"", and can not handle sub arrays." shadowhck
Needs Dev / Bug Wrangler Feedback 12264 links truncated: link_url column in wp_links table -- datatype too small General 2.9.2 normal normal Future Release defect (bug) new dev-feedback 2010-02-17T20:27:25Z 2011-08-03T19:55:37Z "Here is my original post about the issue: [http://wordpress.org/support/topic/365540?replies=3]
In short, the link_url column in the wp_links table has a datatype of VARCHAR(255). As far as I know, there is no pre-defined limit to the length of a URL. However, browsers typically enforce their own practical limits, the shortest of which is much larger than the 255 character limit that WP is enforcing. Entering urls longer than 255 characters causes them to be truncated.
I tried altering the table so that link_url has a datatype of VARCHAR(1024). This allowed me to use much larger links without them being cut off. Therefore, I believe that the limiting factor is the DB and not some other code within WP.
" goto10
Needs Dev / Bug Wrangler Feedback 16059 wp_kses_split2() is private, no need to create a function with the sole purpose to call a function. General 3.1 lowest normal Future Release defect (bug) new dev-feedback 2011-01-01T17:06:19Z 2011-01-01T21:41:01Z "In the effort to remove create_function() constructs from the file (#10623, #7363) the last one was removed in 16313 / #14424.
While the analysis in the last ticket was right that create_function() is not needed, the resolution to introduce a named function was not.
Infact the anonymous callback function has been replaced with a named callback function without taking into account, that a named callback function already exists. So a function whith its sole purpose to call another function has been introduced by the google summer of code student.
The existing functions name is wp_kses_split2(), having the needed properties. The function is marked as private and not used anywhere else in the file kses.php nor the whole core php code.
It can be safely adopted to fulfill the requirements of the callback function signature.
This saves the overhead of a function call per callback call.
Additionally passing the data needs only one entry in the symbol table by using an array." hakre
Needs Dev / Bug Wrangler Feedback 18525 "zlib.output_compression ""on"" in server conflicts with autoupdate" General 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-08-26T20:11:45Z 2012-11-13T05:12:06Z "If zlib.output_compression is ""on"" in server (my vps server), then auto-update works, but without verbose output or any indication that install has succeeded.
This error is consistent for all auto-updates WordPress Application and all plugins.
It is NOT a plugin conflict. Occurs on different servers.
Testing has confirmed that when zlib.output_compression is returned to ""off"", then updates work as expected.
In my opinion this is a minor bug and probably a note in the readme file will suffice.
Thank You,
Neil Miller
zx@avidre.net" avidre
Needs Dev / Bug Wrangler Feedback 16158 3.0.4 Upgrade failed on localhost testbed, successful on public site HTTP 3.0.1 normal normal Future Release defect (bug) new dev-feedback 2011-01-08T21:03:55Z 2011-01-09T14:15:17Z "Running: 3.0.1, Ubuntu, Apache
I'm still looking at this but wanted to report it while I have a break.
I got the holiday notice to upgrade to 3.0.4. When I did an auto-upgrade on my local testbed (http://localhost:9090/wp/wp-admin/update-core.php), WP reported that I have latest version. Plugin upgrades work fine. The auto upgrade was successful on my public sites. I have WP_DEBUG, etc. on for my local testbed and no errors were reported. I have upgraded my local testbed this way in the past, definitely for 3.0.1.
Below is a debug dump I hack in the WP_HTTP->request call coming from wp_version_check. I pasted the URL use into the browser bar it returned the correct information. Called from wordpress localhost, api.wordpress.com returns a HTML document with the Page not found and a bunch of info about wordpress.
{{{
[08-Jan-2011 20:42:48] URL='http://api.wordpress.org/core/version-check/1.5/?version=3.0.1&php=5.3.2-1ubuntu4.5&locale=en_US&mysql=5.0.83&local_package=&blogs=1&users=2&multisite_enabled=0'
[08-Jan-2011 20:42:48] r=array (
'method' => 'GET',
'timeout' => 3,
'redirection' => 5,
'httpversion' => '1.0',
'user-agent' => 'WordPress/3.0.1; http://localhost:9090/wp/',
'blocking' => true,
'headers' =>
array (
'wp_install' => 'http://localhost:9090/wp/',
'wp_blog' => 'http://localhost:9090/wp/',
'Accept-Encoding' => 'deflate;q=1.0, compress;q=0.5',
),
'cookies' =>
array (
),
'body' => NULL,
'compress' => false,
'decompress' => true,
'sslverify' => true,
'ssl' => false,
'local' => false,
)
}}}
So two problems:
1) If the local site core check fails, it assumes what it is running is the most current. There is no indication that the core check failed. It seems like the ""Page Not Found"" page returned from api.wordpress.org should be displayed. See #16156, #16094 for similar issues.
2) What in the request is causing the HTTP get to fail? I think it must something in the header information. BUT, it USED to work. Is the server behaving differently?" dturvene
Needs Dev / Bug Wrangler Feedback 17010 Inconsistent handling of HTTP response codes HTTP 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-04-01T00:00:13Z 2011-04-06T00:20:04Z "I noticed during some testing to see what would happen if a server returned a 404 when streaming to a file,and found some inconsistent handling of response codes between transports.
The below test checks to see if the transport returns a WP_Error or if it returns an actual response. If the second column is an integer matching the first column then the transport returned a response, if the second column is 'wp_error' then the transport returned WP_Error for that response code.
STREAMS:
{{{
100 => 100
101 => 101
102 => 102
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => 400
401 => 401
402 => 402
403 => 403
404 => 404
405 => 405
406 => 406
407 => 407
408 => 408
409 => 409
410 => 410
411 => 411
412 => 412
413 => 413
414 => 414
415 => 415
416 => 416
417 => 417
422 => 422
423 => 423
424 => 424
426 => 426
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}
FSOCKOPEN:
{{{
100 => 100
101 => 101
102 => 102
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => wp_error
401 => wp_error
402 => wp_error
403 => wp_error
404 => wp_error
405 => wp_error
406 => wp_error
407 => wp_error
408 => wp_error
409 => wp_error
410 => wp_error
411 => wp_error
412 => wp_error
413 => wp_error
414 => wp_error
415 => wp_error
416 => wp_error
417 => wp_error
422 => wp_error
423 => wp_error
424 => wp_error
426 => wp_error
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}
EXTHTTP:
{{{
100 => wp_error
101 => wp_error
102 => wp_error
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => 400
401 => 401
402 => 402
403 => 403
404 => 404
405 => 405
406 => 406
407 => 407
408 => 408
409 => 409
410 => 410
411 => 411
412 => 412
413 => 413
414 => 414
415 => 415
416 => 416
417 => 417
422 => 422
423 => 423
424 => 424
426 => 426
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}
CURL:
{{{
100 => wp_error
101 => wp_error
102 => wp_error
200 => 200
201 => 201
202 => 202
203 => 203
204 => 204
205 => 205
206 => 206
207 => 207
226 => 226
300 => 300
301 => 301
302 => 302
303 => 303
304 => 304
305 => 305
306 => 306
307 => 307
400 => 400
401 => 401
402 => 402
403 => 403
404 => 404
405 => 405
406 => 406
407 => 407
408 => 408
409 => 409
410 => 410
411 => 411
412 => 412
413 => 413
414 => 414
415 => 415
416 => 416
417 => 417
422 => 422
423 => 423
424 => 424
426 => 426
500 => 500
501 => 501
502 => 502
503 => 503
504 => 504
505 => 505
506 => 506
507 => 507
510 => 510
}}}
We need to define when we want to return a WP_Error, if ever. I am thinking that returning a WP_Error is not very useful if we get a response from the server. The response codes tested were obtained from get_status_header_desc()." sivel
Needs Dev / Bug Wrangler Feedback 11740 Sorting tags and towns does not work well for utf-8 nbachiyski I18N 2.9 normal normal Future Release defect (bug) new dev-feedback 2010-01-06T12:42:24Z 2012-09-02T14:25:29Z "There are problems with sorting special Czech characters:
1) Options - General - Timezone selection.
Evropa (Europe)
First item should be Amsterdam, but instead of it there is ""Řím"" (Rome in Czech). And this is not right, character Ř should be between R and S.
2) Editing posts - Select from most used tags.
You can create tags ""Rome"", ""Amsterdam"" and ""Řím"".
Tags are also sorted in a bad way, first is ""Řím"".
It is very problematic for Czech users when there are many tags, because it does not help them..." pavelevap
Needs Dev / Bug Wrangler Feedback 20813 _get_plugin_data_markup_translate fails to load plugin translations I18N 2.9 normal normal Future Release defect (bug) new dev-feedback 2012-06-01T21:22:17Z 2013-05-08T00:49:29Z "Example Plugin:
{{{
Plugin Name: XYZ
Text Domain: zzz
Domain Path: /lang
}}}
For showing the translated description, _get_plugin_data_markup_translate() will be called.
{{{
function _get_plugin_data_markup_translate( $plugin_file, $plugin_data, $markup = true, $translate = true ) {
// Translate fields
if ( $translate ) {
if ( $textdomain = $plugin_data['TextDomain'] ) {
if ( $plugin_data['DomainPath'] )
load_plugin_textdomain( $textdomain, false, dirname( $plugin_file ) . $plugin_data['DomainPath'] );
}}}
This will call (replaced vars with values):
{{{
load_plugin_textdomain( 'zzz', false, ""/full/path/to/plugin/dir/"" . ""lang"" );
}}}
But load_plugin_textdomain only accepts the subdirectory ""lang"" as the third argument, leading to an incorrect path since WP_PLUGIN_DIR will be put in front.
The fix is to use basename(dirname()) to only get the plugin directory instead of the full path." arnee
Needs Dev / Bug Wrangler Feedback 21319 is_textdomain_loaded() returns true even if there are no translations for the domain nbachiyski* I18N 3.0 normal normal Future Release defect (bug) accepted dev-feedback 2012-07-20T03:48:56Z 2012-11-06T23:15:36Z "#10527 introduced is_textdomain_loaded(). It returns true if load_textdomain() has been called, even if no translations were loaded for that domain. I think it should return false if no translations were loaded. As the documentation says, ""@return bool Whether there are translations"". In this case, no, there are not translations.
Attached patch also does the following:
* Does not store instances of NOOP_Translations inside the $l10n global. Previously, we instantiated NOOP_Translations once for each domain that was missing translations; since we are no longer storing NOOP_Translations instances inside $l10n, we need to avoid instantiating it for every call to get_translations_for_domain(). Thus, NOOP_Translations is now instantiated only once, using a static variable.
* Removes by-references for get_translations_for_domain(), which are no longer needed in PHP5." nacin
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 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
Needs Dev / Bug Wrangler Feedback 22558 Attachment term counts feels/are inaccurate Media normal normal Awaiting Review defect (bug) new dev-feedback 2012-11-23T16:21:26Z 2013-02-21T14:31:24Z "For posts:
* Assign a term to a post, save as draft. Term count returns 0.
* Publish the post. Term count returns 1.
* Change post status back to draft. Term count returns 0.
For attachments:
* Upload an image, assign a term. Term count returns 0.
* Create a new post and insert the image in a published post. Term count returns 0.
* Create a new post, use the insert media modal and upload an image. Then go the the media edit screen and assign a term to the image. Term count returns 1.
* Change the post status back to draft. Term count returns 1.
* Upload an image, assign a term, attach the attachment to a published post. Term count returns 0.
The default term update callback is `_update_post_term_count`. The function includes a special case for attachments, that's the reason why we have the 1 in step 3.
IMO the term count for attachments shouldn't rely on the parent post status. We should just force `_update_generic_term_count`.
Also noted here: comment:ticket:21391:41" ocean90
Needs Dev / Bug Wrangler Feedback 23954 Checkbox value is not updated correctly inside media-views.js Media 3.5.1 normal major Awaiting Review defect (bug) new dev-feedback 2013-04-05T22:11:18Z 2013-04-06T14:43:52Z "I added two custom fields to the ""Edit Gallery"" interface using a hook and discovered that my ""select"" and ""text"" inputs were working fine, but my ""checkbox"" input did not work at all.
I enabled `SCRIPT_DEBUG` so that I could explore further and discovered that the bug on line 3939 of media-views.js.
A double-bang has been incorrectly used to cast from a string encoded boolean value to an actual boolean value (since !!""false"" is actually true).
This is the current implementation:
{{{
} else if ( $setting.is('input[type=""checkbox""]') ) {
$setting.attr( 'checked', !! value );
}
}}}
This is my recommendation which resolves the issue:
{{{
} else if ( $setting.is('input[type=""checkbox""]') ) {
value = value !== false && value !== 'false';
$setting.attr( 'checked', value );
}
}}}
I would submit a patch, but I do not know how to do that." NumberKruncher
Needs Dev / Bug Wrangler Feedback 18297 Cropping in step 2 in Custom_Image_Header Media 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-07-29T17:35:27Z 2012-05-24T22:50:56Z "The cropping should not be based on the ratio but should follow some basic logic.
if ( ( yimg < HEADER_IMAGE_HEIGHT ) && ( ximg < HEADER_IMAGE_WIDTH ) ) // no crop
else //do follow current functionality" wpsmith
Needs Dev / Bug Wrangler Feedback 16891 Deleting all attachments from post under 'Gallery' tab shows 'From Computer' tab sans uploader Media 3.1 normal normal Future Release defect (bug) new dev-feedback 2011-03-18T17:33:26Z 2012-07-04T14:12:42Z "'''Steps to Reproduce:'''
1. Attach images to post using 'Add an Image' dialog
1. '''Save post'''
1. Go to Gallery tab under dialog
1. Delete images
1. View changes to 'From Computer' tab with only empty table from Gallery tab" kawauso
Needs Dev / Bug Wrangler Feedback 17255 Draft status for media files Media 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-04-27T11:48:11Z 2012-06-23T00:56:18Z "It's weird that media files don't carry any concept of pub status. If someone wants to upload files (either attached to a post or directly into the library), they should be able to keep them hidden via 'draft' status just like any other content. The fact that people can link to things that haven't been explicitly published is bizarre.
Media files should have a pub status. If uploaded as post attachment, should inherit publish on post publish. Would then need a workflow for if a post becomes unpublished containing media, as it then lives in library for use by other content, so would need to ask if user wants to unpub media files as well. This would be a big shift, so would make most sense as part of a media redux with a long notice period for plugin and theme authors. " jane
Needs Dev / Bug Wrangler Feedback 11824 Erroneous MIME type for .ico files cnorris23* Media 2.9.1 low minor Future Release defect (bug) accepted dev-feedback 2010-01-08T14:23:48Z 2012-02-17T22:28:59Z "wp-includes/functions.php
line 2286
{{{
$mimes = apply_filters( ...
...
'ico' => 'image/x-icon',
...)
}}}
this is an erroneous label for ico file.
the right one is:
{{{
$mimes = apply_filters( ...
...
'ico' => 'image/vnd.microsoft.icon',
...)
}}}
read : http://www.iana.org/assignments/media-types/image/vnd.microsoft.icon
or: http://en.wikipedia.org/wiki/ICO_(file_format)" davide.vicario
Needs Dev / Bug Wrangler Feedback 15807 Featured image doesn't attach to post Media 2.9 normal normal Future Release defect (bug) new dev-feedback 2010-12-14T11:57:23Z 2010-12-26T23:09:57Z "When you use an image as featured, it doesn't attach to the post.
Possibly related with #14390 (post image (thumbnail) in [gallery])
Tests:
• If the image is already attached, it doesn't reattach ✔
• If the image is uploaded while writing the post, it attaches like another image, even if you are not using it in the post. ✔
• If an image is in the media library, not attached, and you use it in your post, it automatically attaches to the post. ✔
• If the image is in the media library, not attached, and you use it as featured image in a post, it doesn't attach ✘
" bi0xid
Needs Dev / Bug Wrangler Feedback 11325 Image cropping doesn't work for small areas Media 2.9 normal normal Future Release defect (bug) new dev-feedback 2009-12-04T19:46:08Z 2011-02-03T14:22:23Z "Image cropping works for JPEG images, but not for PNGs. The crop button is disabled.
Rev.179738" caesarsgrunt
Needs Dev / Bug Wrangler Feedback 13461 Preserve GIF transparency/alpha during thumbnail creation Media 2.9.2 normal normal Future Release defect (bug) new dev-feedback 2010-05-20T13:23:30Z 2012-12-19T23:22:40Z "GIF images with transparent backgrounds get thumbnails with black backgrounds.
It was a similar ticket for PNG images in: http://core.trac.wordpress.org/ticket/2805" javitxu123
Needs Dev / Bug Wrangler Feedback 22135 Special characters in caption lead to failure of inserting images Media 3.4.2 normal normal Awaiting Review defect (bug) new dev-feedback 2012-10-08T21:25:46Z 2012-10-11T16:26:47Z "Found this when double-checking #22132:
1. Go to add a new post.
2. Click ""Upload/Insert"" (the ""old"" media upload).
3. Upload an image, or go to choose one from the media library.
4. Insert {{{Title""}}} in the ""Caption"" field.
5. Click ""Insert into Post"".
Instead of the image (or Shortcode) being added to the editor (with a somehow escaped caption field), the media upload iframe just gets a new content:
{{{
[/caption]'); /* ]]> */
}}}
Reproduced in 3.4.2 and trunk." TobiasBg
Needs Dev / Bug Wrangler Feedback 17764 TinyMCE breaks the autoembed feature azaozz Media 2.0 normal normal Future Release defect (bug) assigned dev-feedback 2011-06-11T10:20:43Z 2012-09-18T10:39:26Z "The auto embedding works with URLs on a separate line:
{{{http://www.youtube.com/watch?v=e0Qt5CKdoOY}}}
Right now the Visual Editor makes all URLs clickable:
{{{http://www.youtube.com/watch?v=e0Qt5CKdoOY}}}
and auto embedding no longer works.
Reported here:
http://en.forums.wordpress.com/topic/embedding-video-does-not-work?replies=1" dzver
Needs Dev / Bug Wrangler Feedback 20948 Unnecessary post type check in wp_get_attachment_url Media 3.4 normal normal Awaiting Review defect (bug) new dev-feedback 2012-06-14T02:38:16Z 2012-12-16T23:21:48Z Not sure why this needs to be done. You wouldn't be calling this function on a post if it wasn't an attachment. If you are, then you must have a good reason to be doing so, like I do. jfarthing84
Needs Dev / Bug Wrangler Feedback 21679 media_handle_upload does not provide a way to change the file's name Media 2.5 normal normal Awaiting Review defect (bug) new dev-feedback 2012-08-24T04:00:30Z 2012-08-24T10:33:06Z "`wp-admin/includes/media.php` has two operations that I believe should be reversed. Basically, `$name` is set based on the name of the raw uploaded file ( `$_FILES[$file_id]['name']`), however in the `wp_handle_upload` function you are able to use `wp_handle_upload_prefilter` to adjust the file's name - but when after the `wp_handle_upload` returns the changes will not show up in the title of the media dialog field even though the file has been renamed properly:
{{{
$name = $_FILES[$file_id]['name'];
$file = wp_handle_upload($_FILES[$file_id], $overrides, $time);
if ( isset($file['error']) )
return new WP_Error( 'upload_error', $file['error'] );
$name_parts = pathinfo($name);
$name = trim( substr( $name, 0, -(1 + strlen($name_parts['extension'])) ) );
}}}
In short, uploading a file named Picture.png and changing the name to test3.png using the `wp_handle_upload_prefilter` filter does in fact allow the file's name to be changed before it is saved, but the ""title"" is then incorrectly displayed in the media uploader dialog box.
[[Image(http://img24.imageshack.us/img24/3679/pictureyp.png)]]
This would be relatively easy to fix using this patch:
{{{
--- media.php 2012-08-23 23:57:02.000000000 -0400
+++ media-patch.php 2012-06-06 12:00:08.000000000 -0400
@@ -209,8 +209,8 @@
$time = $post->post_date;
}
+ $name = $_FILES[$file_id]['name'];
$file = wp_handle_upload($_FILES[$file_id], $overrides, $time);
- $name = $file['name'];
if ( isset($file['error']) )
return new WP_Error( 'upload_error', $file['error'] );
}}}" Willshouse
Needs Dev / Bug Wrangler Feedback 22070 Deleting menus with no title / slow menu saving Menus 3.4.2 normal normal Awaiting Review defect (bug) new dev-feedback 2012-10-01T12:28:55Z 2012-10-01T12:35:48Z "Hello there
I saw that when saving nav menus in wp-admin/nav-menus.php WordPress executes the following lines, if a menu item is saved (no matter if newly added or existing) that doesn't have a title:
{{{
if ( empty( $_POST['menu-item-title'][$_key] ) )
continue;
}}}
I changed this to the following to make it work. Problem is, it needs to be removed from $menu_items, because it's handled like a deleted menu else.
{{{
if ( empty( $_POST['menu-item-title'][$_key] ) ) {
if (isset($menu_items[$_POST['menu-item-db-id'][$_key]]))
unset($menu_items[$_POST['menu-item-db-id'][$_key]]);
continue;
}
}
}}}
'''Sidenote''':
With that fixed, I was able to solve a major saving bug. Many of our customers have a lot of menu items in out nav_menu (like 100 - 600), which without a timeout would take 10 minutes and more to save.
So I created some hotfix jQuery script that does ""dirty-handling"". Basically it marks everything that's touched (like changed data, adding a menu item or moving things around) as ""dirty"". On submit it doesn't nothing more than change every ""undirty"" menu items title to an empty string so it doesn't get saved.
I think WordPress core developers could integrate something like this with far less code since I wasn't able to use events - I didn't really had a lot of time to fix this. So if it helps anyone, this is the jQuery code I used to create the fix:
{{{
jQuery(function($) {
// the currently displayed menu form
var $form = $('#update-nav-menu');
// Listen to new menus, since we have no possibility to hook
// we have to interval it, because we can't capture an event here
$('.submit-add-to-menu').click(function() {
var $item_count = $form.find('.menu-item-handle').length;
var $interval_id = setInterval(function() {
var $current_item_count = $form.find('.menu-item-handle').length;
if ($item_count < $current_item_count) {
clearInterval($interval_id);
// Add the dirty flag and set it to dirty immediately
add_dirty_flags(1);
// Reassign the mousedown/up events
assign_mouse_events();
}
},200);
});
// add a hidden field, telling if the menu is dirty (by default, it's not)
function add_dirty_flags($flag) {
$form.find('.menu-item-handle').each(function() {
if ($(this).find('.dirty-handle').length == 0) {
var $html = '';
$(this).append($html);
console.log('flag added');
}
});
}
// (re)assigns mouse events to menu items
function assign_mouse_events() {
var $menu_items = $('.menu-item-bar');
// Unbind previously assigned events
$menu_items.unbind('mouseup').unbind('mousedown');
// Dirty Flag handler if a click happens
$menu_items.mousedown(function() {
$(this).find('.dirty-handle').val('1');
});
// if the parent changes on release the mouse handle, change all items with the new parent to dirty
$menu_items.mouseup(function() {
menu_save_mouseup($(this));
});
}
// The call back for mouseup on menu bars
function menu_save_mouseup($this) {
var $temp_object = $this.parent();
// Mark everything with the same parent dirty
setTimeout(function() {
var $parent_id = $temp_object.find('.menu-item-data-parent-id').val();
// Go through all fields, dirtying everything that has the same parent
$('.menu-item-data-parent-id').each(function() {
if ($(this).val() == $parent_id)
$(this).parent().prev().find('.dirty-handle').val('1');
});
},200);
}
// On submit make every undirty menu an empty title, so it won't get saved
// We're using a hoax in nav-menus.php, line 335 here..
$form.submit(function() {
// Now traverse all handles and make only dirties saveable
$form.find('.menu-item-handle').each(function() {
// Find the dirty flag
var $is_dirty = $(this).find('.dirty-handle').val();
$(this).find('.dirty-handle').remove();
if ($is_dirty == 0) {
// The div containing the menu informations
var $forms = $(this).parent().next();
// Remove the title value so it doesn't get saved
$forms.find('.edit-menu-item-title').val('');
}
});
return true;
});
// Assign mouse events on first load
assign_mouse_events();
// Add all dirty flags (not dirty by default of course)
add_dirty_flags(0);
});
}}}
Since WordPress now only saves the menu's that changed it doesn't matter how many menu items a customer has, but only how many he want's to save at one time." msebel
Needs Dev / Bug Wrangler Feedback 19038 Menu Items aren't deleting on page being trashed, only when deleted Menus 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-10-24T17:38:44Z 2011-12-20T20:32:57Z The linked menu item for a page isn't removed when the page is trashed. jeremyatignition
Needs Dev / Bug Wrangler Feedback 16382 "Menus adds ""current_page_parent"" class to the blog page when viewing a custom post type entry" Menus 3.0.5 normal normal Future Release defect (bug) new close 2011-01-26T22:37:36Z 2013-02-15T17:10:13Z "Here is an example: http://www.flowermag.com/article/love-rocks/
This entry is in the custom post type ""article"", but the navigation item ""blog"" is getting the class ""current_page_parent"" even though an article is not a blog post.
This is a problem since if you're using ""current_page_parent"" for navigation highlighting, this would render an incorrect display." tammyhart
Needs Dev / Bug Wrangler Feedback 20289 wp_nav_menu container is not set when menu isn't defined Menus 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2012-03-23T10:27:03Z 2012-03-23T13:19:41Z "When you use wp_nav_menu in your theme, but the actual menu isn't set via the backend menu interface, the container provided in the args is ignored and falls back to 'div'.
Attached diff always uses container provided in args, if 'div' or 'nav' is provided. If no container arg is provided, falls back to using 'div'.
{{{
wp_nav_menu(
array(
'theme_location' => 'main_menu',
'container' => 'nav',
'menu_class' => 'main-menu-navigation',
)
);
}}}
To test this: Use this function in your theme, without assigning a menu to this theme_location." dannydehaan
Needs Dev / Bug Wrangler Feedback 23908 wp_nav_menu generates wrong classes for li elements Menus 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-03-30T13:42:46Z 2013-03-30T13:42:46Z "Function '''wp_nav_menu''' generates 2 different classes for '''
''' with exactly the same meaning: e.g. '''current-page-parent''' and '''current_page_parent'''. It sometimes generates one of them, but sometimes both.
Also this coresponds to '''current-page-ancestor''' and '''current_page_ancestor''' classes.
I think there should be one of them, but to preserve compatibility with older websites, it is better to leave both but generate both at the same time, so that user could use either ""'''-'''"" or ""'''_'''"" as separators." anyname2
Needs Dev / Bug Wrangler Feedback 19686 404 - File or directory not found Multisite 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2011-12-29T19:47:45Z 2012-01-03T21:38:51Z "We are running Wordpress using multiuser with Buddypress. Users are getting the 404 error after they click the save button in their settings.
I'm opening this ticket to report the source of the problem.
Wordpress 3.x
Buddypress 1.5
Windows 2008 R2 (IIS 7.5)
Themes installed are all Buddypress compatible and all themes seem to be affected.
All option pages are affected.
Settings are updated when the user returns to the page - despite the error. A screen shot of the error can be seen at http://blogs.cnc.bc.ca/gagel/?attachment_id=38
The source of the problem appears to be in the wp_get_referer() function on line 164 in options.php. With the variables passed to the function it should redirect the user to the page they just submitted when they updated options. Instead they get the 404 error.
The page they're redirected to appears to be the absolute path of the submitted page appended to the absolute path again (minus the domain). So it looks like this:
userblog/wp-admin/userblog/wp-admin/options-general.php?settings-updated=true
When I switch out the wp_get_referrer() function with the variable $parent_page then the redirect worked as expected.
I'm uncertain about leaving it like this as my change may have introduced issues elsewhere...
This issue is discussed at http://wordpress.org/support/topic/recuring-404-file-or-directory-not-found-error?replies=8#post-2527566" kwgagel
Needs Dev / Bug Wrangler Feedback 14539 Cache-Control / Expires headers not applied to files in Multisite files location Multisite 3.0.1 normal normal Awaiting Review defect (bug) new dev-feedback 2010-08-05T04:21:33Z 2012-09-19T16:02:17Z "First reported in Multisite forum and detailed there:
[http://wordpress.org/support/topic/cache-control-headers-and-uploaded-files-not?replies=5]
These file type accesses should return 304s according to the rules in .htaccess but consistently return 200, showing an incorrect Cache-Control header specification, instead of no specification at all--which is still undesired.
This occurs in two 3.0.1 Multisite installs on all blogs, domain mapped or not, but does not occur on any other domains on the server or in any other file locations in the WP tree (themes, etc.).
Initially, it was image files that I had identified this on but a subsequent check of a CSS file in the files/ location returned the same header that is set for (.php|.pl|.cgi) files; same as the image files do.
Apache 2.2.15, PHP 5.2.13, FreeBSD 7.2-STABLE, MySQL 5.0.90
" spherical
Needs Dev / Bug Wrangler Feedback 18242 Changing domain for a network blog make faulty changes in database Multisite 3.0 normal major Future Release defect (bug) new dev-feedback 2011-07-25T11:33:51Z 2012-11-20T11:49:53Z "When changing the domain for a network blog, if the network is set up on a subdomain and using sub-folder options for blogs, the save to the database is faulty, saving wrong urls.
The network main site uses eg http://my.blog.com and the blogs has http://my.blog.com/blog1
When changing the domain for blog1 in ""Network admin -> All Sites -> Edit blog1"" and choose to also update ""home and siteurl"" the new url for home and site become http://blog.com/blog1/my
Happens in both Firefox 5 and Safari 5.1" darkwhispering
Needs Dev / Bug Wrangler Feedback 15943 Custom Post Type not set after customizing permalinks. sterlo* Multisite 3.0.3 normal critical Future Release defect (bug) accepted dev-feedback 2010-12-21T23:42:55Z 2011-01-06T23:11:07Z "Developing a plugin,
It sets a custom post type on init:
{{{
register_post_type(
'staff_listing',
array(
'labels' => array(
'name' => 'Staff Listings',
'add_new_item' => 'Add a Staff Member',
'new_item' => 'Staff Member',
'add_new' => 'Add a Staff Member',
'singular_name' => 'Staff Member'
),
'public' => true,
'publicly_queryable' => true,
'show_in_nav_menus' => false,
'exclude_from_search' => false,
'show_ui' => true,
'hierarchical' => false,
'rewrite' => array(
'slug' => 'staff',
'with_front' => false
),
'query_var' => 'staff',
'supports' => array(
'title',
'editor',
'thumbnail',
'comments',
'revisions'
)
)
);
}}}
If I add a staff member called ""john doe"" and then go to that on the front end - I expect to see this in $wp_query->query_vars:
{{{
[staff] => john-doe
[post_type] => staff_listing
[category_name] =>
[name] => john-doe
[is_404] =>
[queried_object_id] => ###
}}}
(I replaced the ID with ### since it changes from one install to the other)
That '''works''' on a standard WordPress 3.0.3 install.
But does '''not work''' on a WordPress 3.0.3 MU install.
The MU install gives me this:
{{{
[name] => john-doe
[post_type] =>
[category_name] => staff
[is_404] => 1
[is_singular] =>
[queried_object_id] => 0
}}}
Both the permalinks on the MU and standard setup are set as follows:
{{{
/%category%/%postname%/
}}}
If I change the permalink structure on the MU site to the default structure - the problem goes away.
The new URL is: ?staff=john-doe and it sets the following:
{{{
[staff] => john-doe
[post_type] => staff_listing
[name] => john-doe
[category_name] =>
[is_404] =>
[queried_object_id] => ###
}}}" sterlo
Needs Dev / Bug Wrangler Feedback 14873 HTTPS related issue with ms-settings.php Multisite 2.9 normal normal Future Release defect (bug) new dev-feedback 2010-09-14T18:23:26Z 2012-09-13T23:13:22Z "ms-settings.php hard-codes ""http://"" in a few places. This didn't impact me, but I can see that it might impact someone.
Hopefully, a developer can take a look at the code and verify that, in fact, it has to change. Seems like it does since hard-coding ""http:"" isn't a good practice, but I don't want to claim it since I haven't seen the need for it personally.
Here's the updated code that needs to replace the code in ms-settings.php starting at line 83 and ending at line 105:
{{{
$protocol = is_ssl() ? 'https://' : 'http://';
if ( ! defined( 'WP_INSTALLING' ) && is_subdomain_install() && ! is_object( $current_blog ) ) {
if ( defined( 'NOBLOGREDIRECT' ) ) {
$destination = NOBLOGREDIRECT;
if ( '%siteurl%' == $destination )
$destination = $protocol . $current_site->domain . $current_site->path;
} else {
$destination = $protocol . $current_site->domain . $current_site->path . 'wp-signup.php?new=' . str_replace( '.' . $current_site->domain, '', $domain );
}
header( 'Location: ' . $destination );
die();
}
if ( ! defined( 'WP_INSTALLING' ) ) {
if ( $current_site && ! $current_blog ) {
if ( $current_site->domain != $_SERVER[ 'HTTP_HOST' ] ) {
header( 'Location: ' . $protocol . $current_site->domain . $current_site->path );
exit;
}
$current_blog = get_blog_details( array( 'domain' => $current_site->domain, 'path' => $current_site->path ), false );
}
if ( ! $current_blog || ! $current_site )
ms_not_installed();
}
}}} " mareck
Needs Dev / Bug Wrangler Feedback 15936 IPv6 literal support in multisite broken Multisite 3.0.3 normal major Future Release defect (bug) new dev-feedback 2010-12-21T16:00:25Z 2013-02-02T06:32:22Z "The logic for handling explicit port numbers in wp-includes/ms-settings.php is confused by IPv6 literal addresses in URLs as defined by RFC 2732.
It tries to handle the URL as it as if there were a port appended, but then fails to strip it off. Incidentally the error message here: 'Multisite only works without the port number in the URL.' is untrue, since ports are handled (but for only two particular cases, port 80 and 443).
The attached patch, against Wordpress 3.0.3, fixes both these issues, and allows ports other than 80 and 443 to be used with Wordpress, by just stripping off the trailing port rather than special-casing the two well-known ports, and not incorrectly detecting IPv6 literals as URLs with ports in. It also has the advantage of being much more compact.
It may be worth someone thinking through whether the substitution is strictly correct with reference to the URL standards, but I'm pretty sure that this is an improvement on the current code.
Thanks,
Dominic." jmdh
Needs Dev / Bug Wrangler Feedback 16293 In multisite installs, users with id 1 or 2 can't be deleted Multisite 3.1 normal normal Future Release defect (bug) reopened dev-feedback 2011-01-19T00:21:34Z 2013-04-25T15:15:19Z "You can't delete a user with user id of 1 or 2.
See: source:trunk/wp-admin/network/edit.php@17326#L359" PeteMall
Needs Dev / Bug Wrangler Feedback 16609 "Misleading ""Error establishing a database connection""" Multisite 3.0.5 normal minor Awaiting Review defect (bug) new dev-feedback 2011-02-21T17:31:10Z 2011-02-21T17:31:10Z "Multisite install shows:
""Error establishing a database connection""
Even if credentials are OK when it doesn't find the domain entry in wp_blogs table, this is very misleading, would be helpful to have the same meaningful error message that /wp-admin shows.
I posted this problem originally at http://wordpress.org/support/topic/misleading-error-establishing-a-database-connection" roberto.carvajal
Needs Dev / Bug Wrangler Feedback 20104 Show network-activated plugins on site plugins screen Multisite normal normal Future Release defect (bug) new dev-feedback 2012-02-22T22:05:35Z 2012-08-18T22:07:03Z "Per http://wpdevel.wordpress.com/2011/12/23/core-team-meetup-recap-multisite/, one action item is:
> Include network activated plugins in the plugins menu and give message that it is automatically on for the whole network (if admin/have rights to see plugins screen).
To enable the plugins screen for a network, a super admin can go to network/settings.php and enable the menu.
Network-activated plugins should still show on this screen to site administrators. (They just can't activate them.) This should require a few tweaks to the plugins list table." nacin
Needs Dev / Bug Wrangler Feedback 23865 Trailing slash is not enforced when editing the path for a subdirectory site in multisite Multisite 3.0 normal normal Awaiting Review defect (bug) new needs-unit-tests 2013-03-26T19:53:23Z 2013-04-01T09:38:28Z "It is possible to edit an existing subdirectory site so that the path does not end in a trailing slash, this causes the subdirectory site in question to have an inaccessible home URL.
To reproduce:
* Create a multisite network in subdirectory mode
* Create a new subdirectory site
* Visit the subdirectory site successfully
* Edit the site to change the path so there is no trailing slash
* You should be unable to visit the subdirectory site now" simonwheatley
Needs Dev / Bug Wrangler Feedback 18117 get_blog_details is sensitive to path's trailing slash Multisite 3.0 normal normal Awaiting Review defect (bug) new dev-feedback 2011-07-14T20:20:39Z 2011-11-16T01:32:02Z "STR:
1. Create a site, then edit it so that the domain is the main domain and the path is /sub. Note that the admin doesn't turn this into /sub/, nor give an error.
2. Go to /sub/wp-admin. You'll notice it doesn't redirect, but it just gives you the main site's wp-admin. Going to /sub also just gets interpreted as a URL for the main site.
Potential solutions:
1. Make the admin automatically turn the path of /sub into /sub/.
2. Make get_blog_details match modulo trailing slash.
3. (Document carefully in Codex and hope people read it.)" mitchoyoshitaka
Needs Dev / Bug Wrangler Feedback 21352 wp_lostpassword_url() on multisite Multisite 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2012-07-23T15:58:23Z 2013-04-24T18:59:15Z "The wp_lostpassword_url() function on Multisite outputs the link to the primary domain not the current domain.
Although it works its not what should be expected if a user is registered to use blog ID 2 but not Blog ID 1.
The lost password email generated also links back to the primary domain not the current domain.
" philly max
Needs Dev / Bug Wrangler Feedback 16894 Bulk load Comment Meta upon access Performance 3.1 normal normal Future Release defect (bug) new dev-feedback 2011-03-19T11:19:27Z 2011-03-19T12:12:05Z "When we query posts, we bulk load all of the posts meta and taxonomies at the time of request. Since adding comment meta, we load the comment meta on-the-fly since nothing really currently uses it in core.
I've added a filter to ''get_comment_text'' which modifies the comment content based on the value of a meta key.
The problem arises when multiple comments are displayed on a page, The metadata for every comment is loaded individually:
{{{
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (4)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (5)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (6)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (7)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (34)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (35)
SELECT comment_id, meta_key, meta_value FROM wp_commentmeta WHERE comment_id IN (37)
}}}
in all cases, the function stack is:
{{{
comments_template, wp_list_comments, Walker->paged_walk, Walker_Comment->display_element, Walker->display_element, call_user_func_array, Walker_Comment->start_el, call_user_func, twentyten_comment, comment_text, get_comment_text, apply_filters, call_user_func_array, MY_FUNCTION_HOOKED_TO_GET_COMMENT_TEXT, get_comment_meta, get_metadata, update_meta_cache #12 (0.7ms)
}}}
It isn't ideal that every comment causes an extra query, instead, we should bulk load comment meta for the comments being displayed.
However, Since comment meta is not always used, in order to keep the load down, I'd suggest that we only bulk load the comment meta '''on the first request for comment meta''', this should allow current users to have no detrimental affect on query count/performance, whilst allowing those who use comment meta to manage each comment better performance." dd32
Needs Dev / Bug Wrangler Feedback 22301 Performance problem with Recent Comments widget Performance 2.8 normal normal Awaiting Review defect (bug) new dev-feedback 2012-10-29T06:07:14Z 2013-01-15T23:18:08Z "When a comment is posted (or the status of a comment changes), the `widget_recent_comments`cache item is invalidated, which the Recent Comments widget uses to populate the widget content. On the next widget display, it will call `get_comments()` to repopulate the cache.
The problem occurs when you have a very large number of comments, the MySQL query will use the `(comment_approved, comment_date_gmt)` index, but if MySQL has to scan too many rows in an index, it'll switch to table scan instead. As the `comment_approved` column is mostly the same value, this will almost always happen. This is compounded by the query occurring on every page load until the cache is re-populated - if the query takes 60 seconds to run, there could potentially be hundreds of instances of the same query running.
So, we need a solution that either hides or eliminates how slow this query can be, and only runs it (at most) once per new comment.
After discussing this with @matt, we have a couple of ideas:
1. Move this query to a `wp_schedule_single_event()` call, which has the bonus of ensuring only one is scheduled at any given time. The downside is that it may cause the cache to be outdated on a low traffic site.
2. Keep a queue of recent comments in cache, and push a new one onto the queue when posted. This avoids the query entirely, but there would be a race condition if two comments were posted at nearly the same time - one of them could be left out of the queue entirely." pento
Needs Dev / Bug Wrangler Feedback 14397 slow sql query from probably is_blog_installed Performance 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-23T06:38:11Z 2010-11-23T00:10:38Z "When everything else fails, is_blog_installed uses
$tables = $wpdb->get_col('SHOW TABLES');
which can be costly in a big multisite or even when you have many single installations on the same DB
Related question - why does is_blog_installed is even being called on wp_widgets_init()? I would assume that if the DB is not set properly not only the widgets will suffer but also the themes and the plugins which are not protected at the same way." mark-k
Needs Dev / Bug Wrangler Feedback 22338 Add filter for the output from `get_sample_permalink` Permalinks 3.4.2 normal normal Awaiting Review defect (bug) new dev-feedback 2012-10-31T22:32:41Z 2013-04-11T12:59:34Z "When getting the sample permalink the `post_name` is not always set in the Post object at this point. The `get_sample_permalink` gets around this by hacking the `post_name` into the Post object for the duration of the function, however it is not possible to get this ""hacked in"" information from the `post_type_link` filter. I suggest that a filter should be added to the `$permalink` array (which contains the link and the post name string) and various additional parameters, including the hacked Post object.
The alternative would be to try to detect situations where the data needs to be hacked in, e.g. watching for particular `action` GET params in an AJAX context, but this seems like a hack too far." simonwheatley
Needs Dev / Bug Wrangler Feedback 19918 Attachments are viewable from any permalink that matches their slug Adrian (designmodo.com) Permalinks 3.2 normal major Awaiting Review defect (bug) new dev-feedback 2012-01-29T11:02:27Z 2012-02-20T07:49:55Z "I see one problem in WordPress, for example if you upload an images with name comments.png, all your url contain hide url like: /comments
example:
original post: yourdomain.com/myarticle
if you have in media gallery file with name comments.png url will be: yourdomain.com/myarticle/comments
or
yourdomain.com/myarticle2/comments
or
yourdomain.com/myarticle3/comments
and all this url's contain the same comment box.
my users report this problem, because if i share in twitter or g+ one link, many users redirect not to the post but to url with /comments in the end.
Adrian,
designmodo.com
" prorock
Needs Dev / Bug Wrangler Feedback 10786 Implementation of %my_taxonomy% in permastructs is incomplete ryan Permalinks 2.9 normal minor Future Release defect (bug) new dev-feedback 2009-09-15T03:30:56Z 2012-05-05T22:21:42Z "The `register_taxonomy()` function includes a call to `add_rewrite_tag()` which should allow for a site's permastruct to include a %my_taxonomy% tag just like you can include a %category% tag or a %tag% tag, however this implementation is incomplete and doesn't work.
Example:
`register_taxonomy('genre','post');`
should allow you to create a permastruct (from the Settings->Permalinks screen) which includes %genre% in it.
The problem is that `get_permalink()` doesn't check for custom taxonomies and the replacement of %genre% with your post's genre in the permalink doesn't happen.
Patch upcoming." johnbillion
Needs Dev / Bug Wrangler Feedback 10249 Page slug in cyrillic = Error 404 - Not Found! westi* Permalinks 2.7 normal major Future Release defect (bug) accepted needs-unit-tests 2009-06-23T19:44:34Z 2012-04-27T19:04:18Z "When I create a page with page slug for example ""киро""
then when I try to open domain/киро - Error 404 - Not Found
The permalinks are %postname%
Post slug with this slug is working just fine, the same BUG exists in 2.7, 2.7.1 and 2.8" kalifi
Needs Dev / Bug Wrangler Feedback 14036 "Post 404 errors due to a base post's name matching the Permalink option ""category base""" Permalinks 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-06-22T02:12:58Z 2011-01-21T09:09:24Z "When the ""category base"" option under Settings>Permalinks is set as a value, one can still create a post with the same value used as the new post's name and thus its permalink path. Thus, when a user tries to navigate to the post via its permalink, Wordpress thinks the user wants to access a category and gives a 404 error.
Here's an example.
Say I set my category base in Settings>Permalinks to ""general."" All my categories are at mysite.com/general/... Now say I make a regular post and name it ""General."" Wordpress automatically assigns it the permalink ""mysite.com/general"". So, on my menus that list this post, this will be the link. However, when a user visits this link, Wordpress is set to recognize /general/ as the category base and it gives the user a 404 error. All subposts under ""General"" also have a permalink that begins with mysite.com/general/ and thus are seen as categories by apache mod_rewrite and become 404 as well.
Solution: users should not be able to have base pages whose names (and thus permalinks) are exact matches to the Settings>Permalinks>Category base value." sniper231
Needs Dev / Bug Wrangler Feedback 10414 Some trackbacks timeout due to short timeout period Pings/Trackbacks 2.8.1 normal normal Future Release defect (bug) new dev-feedback 2009-07-15T07:47:35Z 2009-11-23T21:43:36Z "A trackback by WordPress to an external blog can timeout without any network congestion. WordPress 2.8.1 timeouts if it has not received any response from the receiving system for 4 seconds although some blog system can take more than 10 seconds to accept a trackback. If the trackback fails, WordPress keeps trying to resend the trackback every time the user posts a new entry, but it never succeeds and WordPress keeps resending for ever. It annoys the blog owner whose blog the WordPress is trying to send the trackback to.
I propose that function trackback in wp-includes/comment.php should be modified for the timeout period to be extended from 4 seconds (e.g. to 30 seconds).
This modification is different from one appeared in ticket #8665." gnaka08
Needs Dev / Bug Wrangler Feedback 21699 Losing post status Post Types 3.4.1 normal normal Awaiting Review defect (bug) new dev-feedback 2012-08-27T05:19:40Z 2012-08-27T07:00:09Z I created custom post type and custom post status for it. Then I programmatically set custom status for new post and then edit it using admin panel. When I save post status is set to 'published' and I can't select my status from statuses list. barmin.alexander@…
Needs Dev / Bug Wrangler Feedback 20900 Throw an error in `get_default_post_to_edit` if the specified post type is not defined. Post Types normal minor Awaiting Review defect (bug) new dev-feedback 2012-06-10T23:07:23Z 2012-06-10T23:07:23Z "Currently get_default_post_to_edit will generate a post with the specified post type, even if it doesn't exist. Let's give it a chance to do something else.
If this is conceptually a good idea, also do it during wp_insert_post() and other similar functions." georgestephanis
Needs Dev / Bug Wrangler Feedback 18950 get_post_types() does not return post-types registered with verbose alternatives of the $public argument Post Types 3.2.1 normal major Awaiting Review defect (bug) new close 2011-10-14T16:50:26Z 2012-07-18T10:03:52Z "The $public argument for the '''register_post_type()''' function is supposedly an alternative for setting the arguments for publicly_queriable, show_ui, show_in_nav_menus, and exclude_from_search; It's true that setting the public argument does cause these other values to be set, but if you then use '''get_post_types()''' to query for public post-types, WP does not recognize the equivalence between setting the public option or verbosely setting the others.
== To Reproduce: ==
Enter the following code into a plugin:
{{{
function testing() {
$args => array(
'publicly_queriable' => true,
'show_ui' => true,
'show_in_nav_menus' => true,
'exclude_from_search => false
);
register_post_type('my_custom_post_type', $args);
}
add_action('init', 'testing');
}}}
In a theme file (or somewhere after the init event):
{{{
$pts = get_post_types( array('public'=>true, '_builtin'=>false) );
print_r($pts); // <-- empty!
}}}
== Expected Result ==
I would expect the get_post_types() function to return the '''my_custom_post_type''' post-type because it is using the equivalent of the $public argument.
== Actual Result ==
No post-types are returned.
This represents a problem: other plugins that interact with post-types often rely on the $public argument when using the '''get_post_types()''' function, so any plugin that attempts to verbosely set component attributes will not be recognized. This effectively breaks the API and trainwrecks the interconnectedness of the post-types.
== See Also ==
See forum post: http://wordpress.org/support/topic/public-attribute-for-register_post_type?replies=5#post-2391689
WordPress 3.2.1
PHP 5.3.2" fireproofsocks
Needs Dev / Bug Wrangler Feedback 15995 query is separating post_type 'post' from custom post_types when retrieving custom field Post Types 3.0.3 normal normal Awaiting Review defect (bug) new dev-feedback 2010-12-27T12:37:39Z 2011-02-02T19:46:24Z "{{{
query_posts(
array( 'post_type' => array(
'post',
'custom_1',
'custom_2'
),
'orderby' => 'title',
'order'=>'ASC' )
);
}}}
It doesn't matter which parameter you take for 'orderby' it will separate the post_type 'post' from the custom post_types as shown in the example below:
custom_1, title = AAA[[BR]]
custom_2, title = DDD[[BR]]
custom_1, title = GGG[[BR]]
post, title = BBB[[BR]]
post, title = EEE[[BR]]
I cannot believe that this is intended. The proper output should to be:
custom_1, title = AAA[[BR]]
post, title = BBB[[BR]]
custom_2, title = DDD[[BR]]
post, title = EEE[[BR]]
custom_1, title = GGG[[BR]]" bowstreet
Needs Dev / Bug Wrangler Feedback 14825 'Sticky' Posts from excluded category still included in WP_Query results ryan Query 3.0.1 normal major Awaiting Review defect (bug) reviewing dev-feedback 2010-09-10T00:05:55Z 2011-04-20T22:54:20Z "Hi,
I want to have a list of articles that exclude posts in a category I have called ""Stories."" Some articles in the Stories category are marked as ""sticky"".
{{{
$cat_id = get_cat_id(""Stories"");
$query = new WP_Query(""cat=-{$cat_id}&posts_per_page=10&caller_get_posts=0"");
}}}
However, this still returns articles from the Stories category, but only those that are marked as ""sticky"".
I've taken a look at the source code of wp-includes/query.php, and it seems that what's happening is that it prepends all ""sticky"" posts that were not in the initial query results, regardless of category. (There is only logic implemented that honours the {{{post_type}}}.)
I would appreciate it this bug be addressed and released in an upcoming WordPress release.
Thanks." newmediarts
Needs Dev / Bug Wrangler Feedback 18386 "Bug in custom query when ""Front page displays"": ""A static page""" Query 3.2.1 normal normal Future Release defect (bug) new needs-unit-tests 2011-08-12T10:34:16Z 2012-05-09T10:13:53Z "Here is the bug I have found:
When Front page displays is set to: A static page
and Blog posts are displayed on other page a bug accours...
Lets prepare test enviroment, with clear wp installation and two posts, where one of them is set to default category, and other is set to newly created category (which defautly has ID = 3).
Now, prepare two pages, and in Setting -> Reading set Front page to one of those pages, and Posts page to second one.
If You would like to exclude posts from category no 3 from main blog index, normaly You would use:
in index.php (or specified loop file linked there).
This would work if blog index is set as home page, but fails to work when above test enviroment is used." CyberSpy
Needs Dev / Bug Wrangler Feedback 23849 Unexpected results when running WP_User_Query with role and meta_query Query normal normal Awaiting Review defect (bug) new dev-feedback 2013-03-22T19:48:50Z 2013-04-24T00:42:11Z "There appears to be a couple of bugs in WP_User_Query when doing a role query and adding additional meta_query options (especially when relation is set to ""OR"").
This code:
{{{
$args = array(
'role' => 'Author',
'number' => 100,
'offset' => 0,
'meta_query' => array(
'relation' => 'OR',
array(
'key' => '_my_key',
'compare' => 'NOT EXISTS',
),
array(
'key' => '_my_key',
'value' => 'off',
'compare' => 'NOT LIKE',
),
),
);
$users = new WP_User_Query( $args );
}}}
Expected results:
Any author where _my_key either does not exist or if it does exists is set to ""off""
Returned results:
All authors and/or all users with _my_key set.
The above generates this SQL:
{{{
SELECT DISTINCT SQL_CALC_FOUND_ROWS wp_users.*
FROM wp_users
INNER JOIN wp_usermeta ON wp_users.ID = wp_usermeta.user_id
INNER JOIN wp_usermeta AS mt1 ON (wp_users.ID = mt1.user_id)
INNER JOIN wp_usermeta AS mt2 ON (wp_users.ID = mt2.user_id)
WHERE 1=1
AND (wp_usermeta.meta_key = '_pigeonpack_subscription'
OR (mt1.meta_key = '_pigeonpack_subscription' AND CAST(mt1.meta_value AS CHAR) NOT LIKE '%off%')
OR (mt2.meta_key = 'wp_capabilities' AND CAST(mt2.meta_value AS CHAR) LIKE '%\""Author\""%') )
ORDER BY user_login ASC LIMIT 100
}}}
This seems like a bug to me, the ""Author"" meta should not be modified by the relation => 'OR' argument and thus should not be included in the other meta query statement. Further, the NOT EXISTS isn't a true NOT EXISTS statement. In fact, I'm not even sure why the NOT EXISTS statement looks the way it does. I haven't had too much time to look into this any more in depth.
I tested this in WP3.5 and Trunk
" layotte
Needs Dev / Bug Wrangler Feedback 9300 WP_Query with posts_per_page and sticky posts Query 2.7 low minor Future Release defect (bug) reopened dev-feedback 2009-03-08T06:22:26Z 2013-04-29T08:28:36Z "When using WP_Query with showposts=some_number and you have one post set as a sticky that is out of the range of some_number, the query returned will have some_number plus one posts returned. If the sticky post is within the range of some_number then only some_number of posts is returned by WP_Query.
'''Example Normal''': have 3 posts in order:
Post 1,
Post 2,
Post 3
my_WPQuery = new WP_Query(""showposts=2"");
This will return Post 1 and Post 2
'''Example Error''': have 3 posts in order:
Post 1,
Post 2,
Post 3 (<-- make sticky)
my_WPQuery = new WP_Query(""showposts=2"");
This will return 3 posts (Post 3, Post 1, Post 2).
''Expected to return 2 posts (Post 3, Post 1).''
'''Example OK''': have 3 posts in order:
Post 1,
Post 2 (<-- make sticky),
Post 3
my_WPQuery = new WP_Query(""showposts=2"");
This will return 2 posts (Post 2, Post 1)." yukataninja
Needs Dev / Bug Wrangler Feedback 13365 WP_Query, author_name, and sticky posts ryan Query 2.9.2 normal normal Awaiting Review defect (bug) new dev-feedback 2010-05-12T06:09:42Z 2012-08-30T00:17:35Z "I have a template which is being used as my front page on WP 2.9.2. In this template I setup my loop with the following code:
{{{
$postresults = new WP_Query();
$postresults->query(""author_name=frontpage&post_types=post&post_status=publish"");
while($postresults->have_posts()) { $postresults->the_post(); ?>
// etc...
}}}
I am not using the ""caller_get_posts=1"" option, but my sticky posts are still showing up in order with other posts rather than at the beginning. If I remove the ""author_name=frontpage"" the sticky posts will move back to the first items, however I am stuck with posts by authors I do not want. Using ""author=2"" results in the same behavior as using ""author_name""." eryanv
Needs Dev / Bug Wrangler Feedback 21790 When set a static front page WP main query isn't set correctly Query 3.4.1 normal normal Awaiting Review defect (bug) new dev-feedback 2012-09-04T13:50:26Z 2012-09-05T16:00:06Z "In my project I use on several places pre_get_posts filter. When setting a static frontpage and blog page I get several notices on my screen. When I var_dump the main query the only value that is set it the page_id.
Even the post_type isn't set." markoheijnen
Needs Dev / Bug Wrangler Feedback 17235 meta_query fails if you don't pass in an array of arrays Query 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-04-25T20:20:39Z 2011-07-10T20:44:55Z "This tripped me up the first time I used meta_query (see #16563) and I've seen others fall into the same trap. If you don't pass in an array of arrays into meta_query, it generates some funky (but valid) SQL and fails to return anything.
The main instance where people will fall into this is if they only have a single key/value pair to look for. In this case, passing in an array of arrays does not seem intuitive, and meta_query should be smart enough to work with either. Examples below.
This doesn't work:
{{{
$my_query = WP_Query( array
array (
'post_type' => 'post',
'meta_query' => array (
'key' => 'my_key',
'value' => 'my_value',
),
),
);
}}}
But this does:
{{{
$my_query = WP_Query( array
array (
'post_type' => 'post',
'meta_query' => array (
array(
'key' => 'my_key',
'value' => 'my_value',
}
),
),
);
}}}" batmoo
Needs Dev / Bug Wrangler Feedback 17427 query_posts and tag Query 3.1.2 normal normal Future Release defect (bug) new dev-feedback 2011-05-13T22:58:52Z 2011-11-17T20:57:12Z "When i try to make a query like this:
query_posts('tag=sometag');
and ""sometag"" isn't previously used in some post, the query show me all the posts.
i've to add the tag in a post and after delete it ( wp just need the tag exist in ""wp_terms"" table) and after the query works.
" venerabile
Needs Dev / Bug Wrangler Feedback 20067 /search/.+ takes priority over pages since 3.3 - Breaks some sites Rewrite Rules 3.3 normal major Awaiting Review defect (bug) new dev-feedback 2012-02-18T07:36:46Z 2012-02-24T13:19:21Z Was on WP 3.2.1 and upgraded to 3.3.1. Immediately started experiencing problems with WP intercepting page urls such as: www.mydomain.com/search/advanced-search.html, or any other url whose first level folder was /search/. This is a valid folder and url set on my real estate site, and it all worked fine in 3.2.1. But WP 3.3.1 redirected to some kind of search process, and returned summaries of various pages on the site. As a test, I located and renamed the search.php in my theme folder. After that, the content and formatting of the results changed, but it still incorrectly redirected to some kind of search process, probably the WP core search since the one in the theme folder had been renamed. During this entire process, no other changes were made. The exact same plugins were installed and active, and no changes were made to .htaccess. .htaccess was reviewed, and there were no redirects that could have caused this. No redirect or site search plugins were ever installed or active. I re-installed WP 3.2.1 core files and all of the improper redirecting to search issues went away. Did 3.3.1 have some kind of new internal rewrite rules regarding when/how to do a site search? Affected site is www.denverhomevalue.com. ronnieg
Needs Dev / Bug Wrangler Feedback 16303 Improve documentation and usability of WP_Rewrite Endpoint support westi Rewrite Rules 3.1 lowest normal Future Release defect (bug) new needs-docs 2011-01-19T16:25:01Z 2013-04-05T00:28:06Z "When you know how it works the WP_Rewrite Endpoint support is really simple and cool.
When you don't it looks really difficult to use.
We should document it better and add an endpoint mask for Custom Post Types." westi
Needs Dev / Bug Wrangler Feedback 21526 get_post_type_capabilities() assumes $args->capabilities is an array Role/Capability normal normal Awaiting Review defect (bug) new dev-feedback 2012-08-09T12:29:01Z 2012-08-09T12:46:39Z "get_post_type_capabilities() assumes $args->capabilities is an array and should check and confirm it. Otherwise a warning appears: Warning: array_merge() [function.array-merge]: Argument # 2 is not an array in /home/username/public_html/wp-includes/post.php on line 1183. I discovered this when I accidentally set this to null instead of array().
Type setting it seems to clear the warning, if we want to clear the warning.
{{{
$capabilities = array_merge( $default_capabilities, (array)$args->capabilities );
}}}
" wpsmith
Needs Dev / Bug Wrangler Feedback 23377 map_meta_cap() throws error from has_cap() from current_user_can() Role/Capability normal normal Awaiting Review defect (bug) new dev-feedback 2013-02-04T02:49:22Z 2013-03-07T05:57:10Z "Based on the [http://codex.wordpress.org/Function_Reference/current_user_can current documentation], current_user_can() only requires one argument, a capability. However, if I call it from the `save_post` hook with WP_DEBUG turned on, I will receive the following errors:
{{{
Notice: Undefined offset: 0 in /var/www/XXXX/htdocs/wp-includes/capabilities.php on line 1067
Notice: Undefined offset: 0 in /var/www/XXXX/htdocs/wp-includes/capabilities.php on line 1067
Notice: Undefined offset: 0 in /var/www/XXXX/htdocs/wp-includes/capabilities.php on line 1067
Warning: Cannot modify header information - headers already sent by (output started at /var/www/XXXX/htdocs/wp-includes/capabilities.php:1067) in /var/www/XXXX/htdocs/wp-includes/pluggable.php on line 876
}}}
As a result, the admin save post will die.
Basic Sample Code:
{{{
if ( ( 'page' == $post->post_type && ! current_user_can( 'edit_page' ) ) || ! current_user_can( 'edit_post' ) )
return;
}}}
As a result, in my opinion `map_meta_cap()` should ensure that `$args[0]` exists." wpsmith
Needs Dev / Bug Wrangler Feedback 21425 the 'edit_users' capability also allows 'promote_users' Role/Capability 3.4.1 normal major Awaiting Review defect (bug) new dev-feedback 2012-07-30T17:07:52Z 2012-09-22T10:11:33Z "Hello all,
I have found an issue where I have created a Support role in order to have a user make changes to basic user information. What I noticed was that the capability 'edit_users' allows said User (role) to promote users to any role - including admin! I tried removing the cap 'promote_users' and it does nothing.
add_role(
'support',
'Support',
array(
'read' => true,
'edit_feedback' => true,
'edit_others_feedback' => true,
'list_users' => true,
'edit_users' => true
)
);" ew_holmes
Needs Dev / Bug Wrangler Feedback 16483 Visibility: password-protected exposes multiple pages Security 3.0.4 normal minor Future Release defect (bug) new dev-feedback 2011-02-07T19:02:15Z 2013-03-18T19:47:52Z "1. password protect a page ('protected') with a password
2. password protect another page ('thistoo') with the SAME password
3. visit 'protected' and enter the password. Page is visible
4. visit 'thistoo'; expected: prompt for password. What happens: Page is visible
Regardless of whether someone with a password has the right to try it in as many pages as they want (and would therefore successfully see the page if the passwords were the same), the user should still be prompted on a page-by-page basis. Global authentication to multiple pages is possible with user accounts and roles. It should not be possible with visibility: password-protected pages." monkeyhouse
Needs Dev / Bug Wrangler Feedback 13051 admin_url() and site_url() shouldn't need esc_url() ryan Security 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-04-19T16:57:13Z 2010-11-13T03:09:47Z "I noticed that the 3.0 codeline includes the addition of esc_url() around admin_url() like:
esc_url(admin_url());
I believe that admin_url() and site_url() should be ""safe"" functions to use and should not need escaping. Perhaps they should call esc_url() internally?
I cannot think of a viable reason to allow unsafe results from admin_url() and site_url(), though perhaps there are some internationalization edge cases that I'm not aware of.
If you really need raw access to an unsafe value in wp_options, you can use get_option() to get to it.
Another issue to consider here is input validation and stripping before saving to these fields.
If this is approved in principle, I'd be happy to produce a diff against the current code base.
I think this is very important to address before 3.0 is released as it has a significant impact on theme and plugin developers." alexkingorg
Needs Dev / Bug Wrangler Feedback 10551 wp_die() triggers block when using ModSecurity Core Rules westi* Security 2.8.3 low normal Future Release defect (bug) accepted dev-feedback 2009-08-05T19:47:28Z 2011-03-22T09:51:47Z "wp_die() causes ModSecurity (using Core Rules), a commonly used Apache plugin, to throw a 406 error, blocking the message from displaying.
This seems to be triggered by the fact that a 500 error is thrown. I went and changed the default status code to 401 (Unauthorized) and it worked like a charm. I just wonder if there is a better fix for this issue... or simply a better status code to use.
Perhaps making a group of functions to make the error codes more focused.
Example:
{{{
wp_die_auth( __('You do not have sufficient permissions to access this page.') );
/**
* Exits WordPress with Unauthorized status code.
*
* @see wp_die()
*/
function wp_die_auth($message, $title = '') {
wp_die( $message, $title, 401 );
}
}}}" cstrosser
Needs Dev / Bug Wrangler Feedback 14380 Caption shortcode inserts inline style forcing width of containing div nacin* Shortcodes normal minor Future Release defect (bug) accepted dev-feedback 2010-07-21T19:45:21Z 2013-01-31T22:03:52Z "This is related to #9066.
The problem is that the image caption shortcode inserts an inline style on the containing div which sets the width to an arbitrary value which cannot be overriden by the theme's stylesheet.
The proposed solution is to replace the shortcode function with a custom one which creates the markup without the inline style, but this is undesirable. It adds unnecessary complexity for beginners and is just generally annoying and shouldn't be necessary.
Creating an inline style violates web standards and contradicts the philosophy behind a theme-based architecture.
The inline style on the div should be removed so that theme developers can style the caption like they would any other element, without having to resort to inconvenient workarounds." iandunn
Needs Dev / Bug Wrangler Feedback 23694 Shortcode attributes mess up html strings Shortcodes 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-03-05T15:15:48Z 2013-03-07T03:42:37Z "{{{
[shortcode attribute=""some HTML""/]
}}}
produces:
{{{
some HTML
}}}" prometh
Needs Dev / Bug Wrangler Feedback 14370 Custom Taxonomies tagging Attachments Taxonomy 3.0 normal normal Awaiting Review defect (bug) reopened dev-feedback 2010-07-21T02:28:52Z 2012-08-30T08:56:17Z "There appears to be an issue where if the custom taxonomy has only attachment:image, attachment:audio, and attachment:video The attachments return nothing found. Only 'post' post types are returned.
adding to a query 'post_status' => publish, allows it to display the images but does not allow pagination.
WordPress should return all post_types that the Taxonomy is defined for. Somehow ma.tt found a way around this issue. refer to:
http://osdir.com/ml/wp-testers/2010-06/msg00317.html
http://wordpress.org/support/topic/383096?replies=29
Does not affect pre 3.0
" thee17
Needs Dev / Bug Wrangler Feedback 20850 Duplicate term insertion allowed after insertion with case differences Taxonomy 3.3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2012-06-06T00:00:33Z 2012-06-08T20:20:38Z "I've discovered a case where duplicate terms can be inserted with wp_insert_term(). Steps to reproduce:
1. Insert a term, i.e.
{{{
wp_insert_term('USA', 'country');
}}}
2. Insert the same term, but with a different case, i.e.
{{{
wp_insert_term('usa', 'country'); // it's ok that this succeeds, because technically it *is* different (case-wise)
}}}
3. Insert the same term as in step 2. It should fail, but doesn't:
{{{
wp_insert_term('usa', 'country'); // succeeds
}}}
This is because wp_insert_term() does the following:
1. Finds the first term in the db that matches the initial (non-unique) slug for the new term name
2. If the name of the found term doesn't match the new term name, then insert continues. In the example above, it's comparing all subsequent 'usa' term names to the first 'USA' term name and determining that it's ok to continue, when it's not because there are other 'usa' terms that it didn't look at." jazbek
Needs Dev / Bug Wrangler Feedback 12729 Fix [6326] - wp_unique_term_slug() when changing the parent ryan Taxonomy normal normal Future Release defect (bug) new dev-feedback 2010-03-27T08:04:40Z 2012-11-25T01:35:53Z "[6326] uses $args (as an array) when it appears it should use $term (an object).
It's never worked, so I'm hesitant to patch it as I imagine it might break something elsewhere in the taxonomy API.
Assigning to ryan for now, who authored the commit." nacin
Needs Dev / Bug Wrangler Feedback 16101 Numeric term fields are strings Taxonomy normal normal Future Release defect (bug) new dev-feedback 2011-01-04T23:25:00Z 2013-02-13T01:37:57Z "The numeric fields (term_id, parent, etc.) on term objects are strings. I only noticed this because term_exists() uses is_int() to determine if the $term value is an ID or slug.
Only ticket I could find about this is #5381.
sanitize_term() should fix this, but it bails early in the ""raw"" context. sanitize_term_field() sanitizes the numeric fields in every context. I don't see a reason for sanitize_term() to bail early so I made a patch that takes that out. The patch also adds some missing fields to the list of those to be sanitized and changes term_exists() to use is_numeric() (which will correctly identify strings containing only numbers) instead of is_int().
" foofy
Needs Dev / Bug Wrangler Feedback 22511 Taxonomy manage screen checks for manage_terms and edit_terms, instead of just manage_terms. Taxonomy 3.0 normal normal Awaiting Review defect (bug) new dev-feedback 2012-11-19T23:13:56Z 2012-11-20T03:14:40Z "I'm trying to set up permissions so the Contributor role can add terms but not edit or delete terms. I setup my taxonomy so it looks like this:
{{{
register_taxonomy( 'custom_taxonomy', array( 'post' ), array(
...
'capabilities' => array (
'manage_terms' => 'edit_posts',
'edit_terms' => 'manage_options',
'delete_terms' => 'manage_options',
'assign_terms' => 'edit_posts'
)
) );
}}}
However, when logged in as a contributor I get the error ""You are not allowed to edit this item."" In edit-tags.php there are two checks for caps, one is for manage_terms and one is for edit_terms. I don't believe the second one should be there, because looking at the other code it should be like this:
* User with manage_terms can access the main taxonomy page
* They can also add terms
* There are checks in WP_Terms_List_Table to restrict showing the Edit/Quick Edit/Delete links for users without those capabilities (edit_terms/delete_terms).
* There is even plenty of other checks on edit_terms in edit-tags.php to include/change the content shown to the user.. if the entire page is restricted for users without edit_terms, why are any of those necessary?
Even if I'm wrong on the fact that roles with edit_terms can't add new terms (it's not completely clear anywhere, it seems like manage_terms should be enough), I still think that this page should be viewable at the very least considering the other code in that page and the list table.
Recommended solution: move the edit_terms check back into case 'edit' (line 121 of edit-tags.php in trunk, currently) as it was before [15491].
This was introduced in: [15441] and [15491]. Related: #14343." andrewryno
Needs Dev / Bug Wrangler Feedback 15741 Taxonomy: Duplicate term slug error message refers to the name Taxonomy 3.0.2 normal normal Awaiting Review defect (bug) new dev-feedback 2010-12-09T01:03:10Z 2011-02-25T15:52:39Z "You can't create a term if there is another existing term with the same slug. The error message indicates this warning incorrectly, referring to the term ""name"" instead of ""slug"":
A term with the name provided already exists with this parent.
Problem in action:
1. Create a category name ""Example"" with slug ""example"" without any parent category.
2. Once that is saved, try creating the exact same category again.
3. ""A term with the name provided already exists with this parent."" error shows up.
4. Create a category name ""Example"" with slug ""example-2"".
5. No error. Category with the same '''name''' can be created, contrary to the error message in step 3.
The error message should refer to the slug not name if this is an intended behavior. If the same term name should not exist under one level, step 4 should not be allowed either (especially with Tags)." Nao
Needs Dev / Bug Wrangler Feedback 24354 get_cat_id() fails with category names containing ampersand Taxonomy 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-05-17T08:25:08Z 2013-05-17T10:07:10Z "{{{
echo get_cat_id('News');
results in 3 (as expected);
echo get_cat_id('Test OtherName');
results in 8 (as expected);
echo get_cat_id('Test&OtherName');
Results in 0
echo get_cat_id('News & Media');
Results in 0
}}}
All the category names were created in the Category Edit page, category names were copied from the text box directly into the code to allow no formatting issues.
I tracked the code to get_term_by and I think the ampersand in category name screws up possibly after being added into the prepared SQL statement.
" Kenshino
Needs Dev / Bug Wrangler Feedback 12981 odd behavior of exclude_tree parameter in wp_list_categories() tott Taxonomy 3.0 normal normal Future Release defect (bug) assigned dev-feedback 2010-04-12T20:10:50Z 2010-11-13T01:26:38Z "When running a query such as
{{{
}}}
the exclude_tree parameter is not obeyed as [10276] introduced a change that would overwrite it with the exclude parameter.
" tott
Needs Dev / Bug Wrangler Feedback 14343 user_can_access_admin_page not recognising taxonomies Taxonomy 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-18T08:37:30Z 2010-12-07T23:29:51Z "Hello,
I have a custom taxonomy with custom capabilities.
The ""edit_customtaxonomy"" cap is removed from all roles.
The problem is that the user is still able to click on each term (in the taxonomy page).
When each term is clicked, the user goes to the ""Update term"" page and he is able to click the ""Update"" submit button.
After all, he can't update and get a ""cheatin huh?"" message.
The problem is they should't have access to the update page from the first place.
" ClementN
Needs Dev / Bug Wrangler Feedback 11003 wp_get_object_terms Returns Duplicate Terms ryan Taxonomy 2.9 normal normal Future Release defect (bug) new dev-feedback 2009-10-22T11:14:20Z 2010-12-04T04:21:10Z "wp_get_object_terms() accepts multiple objects in its first parameter. If the multiple objects have terms in common, then wp_get_object_terms() returns those terms more than once in the returned array of term data.
Patch makes the array of terms unique." filosofo
Needs Dev / Bug Wrangler Feedback 10663 Category name handling wrong function is_category Template 2.8.4 normal normal Future Release defect (bug) new dev-feedback 2009-08-20T15:40:46Z 2010-07-15T13:19:54Z "When putting numbers in front of the category names, Wordpress uses them as basis for the function is_category which leads to problems with e.g. plugins using this function.
Example:
- 3 Categories: ""News"" (id 1), ""1st Release"" (id 2), ""2nd Release"" (id 3)
- Trying to check the category with is_category(1) works for news, but also returns true for the category ""1st Release""
- Trying to check the category with is_category(2) returns true for both, ""1st Release"" and ""2nd Release""
This behaviour is not expected. It might be interesting when you explicitely give the category numbers as names (e.g. ""1"", ""2"", ""3""). Changing the in_array function to a simple equal comparison makes everything work as expected." Azaroth
Needs Dev / Bug Wrangler Feedback 23202 Enable is_page_template() within the Loop Template normal normal Awaiting Review defect (bug) new dev-feedback 2013-01-15T14:21:48Z 2013-01-15T17:28:07Z "There have been a few times where, in the loop, I need to know if I were on a page using a specific page template.
The function `in_the_loop()` provides this functionality for us to expand is_page_template()." wpsmith
Needs Dev / Bug Wrangler Feedback 14224 Use NCR instead of HTML entity in feed autodiscovery links Template 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-07T04:23:35Z 2011-05-10T18:54:35Z "Currently, » is used as the separator. This will break sites served with the internet media type ""application/xhtml+xml"". The equivalent numeric character reference » should be used instead." peaceablewhale
Needs Dev / Bug Wrangler Feedback 11699 adjacent_post_link fails to strip anchor tags from post titles Template 2.9 normal normal Future Release defect (bug) new dev-feedback 2010-01-03T01:01:00Z 2010-11-13T07:34:49Z "If you create a post with a title of ""Started using WordPress"", adjacent_post_link() emits a link that has that entire string (including the anchor tags) inside its own link.
The expected behaviour would be to strip the anchor tag to leave the link generated to the WordPress post.
This would then match being able to put links in post titles and using template code such as
which results in a heading with the appropriate title including the link that is part of the title. (If you see what I mean.)
A (but possibly the wrong) fix is to strip the anchor tags using:
{{{
1265a1266,1268
$allowed_html_in_titles = $allowedtags;
unset($allowed_html_in_titles['a']);
$title = wp_kses($title, $allowed_html_in_titles);
}}}
applied to wp-includes/link-template.php
" jaylett
Needs Dev / Bug Wrangler Feedback 14361 the_title does not escape HTML special characters properly Template 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-20T13:45:52Z 2012-09-11T12:46:20Z "The 'the_title' function does not escape HTML special characters properly, causing invalid HTML.
Test case: ""This is a test""" peaceablewhale
Needs Dev / Bug Wrangler Feedback 11678 wpautop() fails on uppercase closing tags Template 2.9 normal minor Future Release defect (bug) new dev-feedback 2009-12-31T11:26:11Z 2011-10-07T00:45:23Z "To reproduce, in a post enter:
{{{
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
}}}
View the post (source) and you get:
{{{
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
}}}
Because I (incorrectly) entered an uppercase closing tag, wpautop() thinks there is no closing tag so adds a , which then often renders as a double
tag. Close if this is not a bug, though I thought it may be good to do some sanitizing or something on uppercase tags.
" joehoyle
Needs Dev / Bug Wrangler Feedback 19674 Do not prefix wp_title() with spaces if $sep is empty Themes 2.0 normal trivial Future Release defect (bug) new dev-feedback 2011-12-27T05:14:23Z 2012-12-02T23:56:48Z "1. Add `wp_title('')` to `header.php`.
2. Notice two spaces before the title:
{{{
Hello World
}}}
This was previously brought up in #7114, but the fix suggested there wasn't backward compatible." SergeyBiryukov
Needs Dev / Bug Wrangler Feedback 20009 Escape later when getting post and body classes Themes normal normal Awaiting Review defect (bug) new dev-feedback 2012-02-10T08:11:37Z 2012-02-15T21:24:17Z "Both get_body_class() and get_post_class() provide filters that allow plugins and themes to add custom values to the list. These filters are applied after the values in the $classes array have been filtered through esc_attr(). I think that it would be best to move the escaping after the filter has fired.
esc_attr() was first added to get_body_class() and get_post_class() in [11838]" mfields
Needs Dev / Bug Wrangler Feedback 16707 No theme is one theme Themes 3.1 normal minor Awaiting Review defect (bug) reopened dev-feedback 2011-02-28T23:39:32Z 2012-11-01T05:43:07Z "If you have no themes at all it still says:
""You only have one theme installed right now. Live a little!""" cogmios
Needs Dev / Bug Wrangler Feedback 15251 Adding Image breaks Blockquote TinyMCE 3.0.1 normal normal Future Release defect (bug) new dev-feedback 2010-10-29T10:47:15Z 2012-09-09T09:56:47Z "When creating entries, adding an image regularly breaks my code.
I am working on a wordpress-based project where I am defining a 'lexicon' of words. I have discovered this bug during the following standard behavior I follow in creating an entry:
All my entries open with a number of words in bold text followed by a definition. These are encapsulated in a blockquote (see example1.jpg or real world examples at kitoconnell.com/lexicon). At first, the visual editor works fine, creating healthy code as I request (I am creating these in the visual editor, but see code example code1.jpg).
Then, I add a photo and the code breaks and has to be fixed manually in the HTML editor. See attached files example2.jpg and code2.jpg; I have not made any changes except to embed a photo with a caption. Adding a picture has moved the blockquote and bold tags to incorrect positions.
Although this is not a system breaking bug, it is an annoyance I am encountering on a daily basis. Thanks for your attention and let me know if anything is unclear or I can provide more data." kitoconnell
Needs Dev / Bug Wrangler Feedback 23371 Subdir front-end Toolbar bug on first login Toolbar 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2013-02-02T22:36:59Z 2013-02-04T20:17:25Z "In an obscure set of circumstances, I encountered a small bug where the Toolbar doesn't display on the front-end of a subdirectory install on the first login where the site URL points to the root domain.
`show_admin_bar_front` is rightly set to true both on first and second+ logins, but the Toolbar doesn't display on the front-end. The js isn't even being loaded.
I can reproduce this all the way back to 3.3.
To reproduce:
1. Install a fresh copy of !WordPress in a subdirectory.
2. Login.
3. Change site url to point to the main domain.
4. Visit the front-end, observe the Toolbar isn't displayed.
5. Logout.
6. Login again.
7. Re-visit the front-end, observe the Toolbar now displays as expected.
I'm unable to trace back what's causing the Toolbar not to be displayed after the initial login. Maybe we should just force the user to login again after changing the site url." DrewAPicture
Needs Dev / Bug Wrangler Feedback 19826 Error behavior for deleting trashed posts is different for Bulk Delete versus Empty Trash Trash 3.1.2 normal minor Awaiting Review defect (bug) new dev-feedback 2012-01-13T18:38:00Z 2012-06-19T19:34:42Z "Bug testing a custom blog build, but I may have located a bug with core (wp-die) Trash error messages.
Background:
*The blog has different users, with different roles.
*Issue occurs on trash page of a custom post type (post status = trash .../edit.php?post_status=trash&post_type=subject)
*Trash contains posts by both an admin role (who can add/edit/delete all custom posts) and an author role (who can add/edit/delete his/her own posts).
*Logged in as an author.
*Using Capability Manager Plug-in. (Tested bug without plugin too)
*Issue is specific to behavior after normal WP-error is thrown.
Issue:
Same WP error. Two different behaviors.
Different functionality occurs between using the Bulk Actions (Delete Permanently) > ""Apply"" button and the ""Empty Trash"" button, after a normal WP error is thrown. In the first case (Bulk Actions > Apply [1a below]), after I return from the error page and refresh the Trash page, all of the selected author pages have been deleted. No admin pages have been deleted.
In the second case (""Empty Trash"" [1b below]), after I return from the error page and refresh the Trash page, all of the selected author pages have NOT been deleted. No admin pages have been deleted.
Behavior:
1a. When I am logged in as an author and I highlight posts by both author and admin, and I attempt to delete using Bulk Actions (Delete Per.) > ""Apply"", I receive the WordPress error ""You are not allowed to delete this item."" ///After I return from the error page and refresh the Trash page, all of the selected author pages have been deleted. No admin pages have been deleted.
1b. When I am logged in as an author and I highlight posts by both author and admin, and I attempt to delete using ""Empty Trash"" button, I receive the WordPress error ""You are not allowed to delete this item."" ///I return from the error page and refresh the Trash page, all of the selected author pages have NOT been deleted. No admin pages have been deleted.
returning to the Trash page. Tested both scenarios.
1. I hit back on the browser, and return to the Trash page. I refresh the page.
2. Move to a different WP admin page, not the Trash page, then return to the Trash page.
Question, because the same text/error is thrown for both buttons, why is the functionality different? Both single functions seem appropriate, however, having both functions exist together instead of picking one behavior seems problematic." jpbellona
Needs Dev / Bug Wrangler Feedback 10884 Available plugin update count disappears after updating plugin dd32* Upgrade/Install 2.8.4 normal normal Future Release defect (bug) accepted dev-feedback 2009-10-01T18:25:59Z 2011-04-03T10:52:00Z "When there are any available plugin updates, WP displays number of them next to ""Plugins"" item in menu. However when you have more than one update available and update one plugin, it disappears.
Steps to reproduce:[[BR]]
- make sure you have more than one plugin with update available (WP should count of them in menu);[[BR]]
- go to the Plugin page and click on Autoupdate link for plugin;[[BR]]
- when update page will load completely, click on provided link to return to plugin list.
Expected result: WP displays new number of available updates next to Plugins menu.[[BR]]
Actual result: nothing is displayed.
Note: I tested this for inactive plugins only." sirzooro
Needs Dev / Bug Wrangler Feedback 11009 screenshots of plugins from wordpress.org load over http instead of https when FORCE_SSL_ADMIN is enabled Upgrade/Install 2.9 normal normal Future Release defect (bug) new dev-feedback 2009-10-23T02:30:21Z 2010-02-05T13:52:39Z "1. Enabled FORCE_SSL_ADMIN in Wordpress on an appropriate host.
2. Use default settings in Internet Explorer 8.
3. Go to the plugin installation page.
4. Choose a plugin from wordpress.org to install.
Actual Result:
You get a mixed mode warning because the screenshots and possibly other content loaded from wordpress.org are loaded over http instead of https.
Expected Result:
Screenshots are loaded over https so that content is not mixed." brantgurga
Needs Dev / Bug Wrangler Feedback 16156 update-core is oblivious to api.wp.org being unreachable Upgrade/Install normal normal Future Release defect (bug) new dev-feedback 2011-01-08T09:51:38Z 2011-04-04T07:46:30Z "A server running 3.0.4 had trouble reaching *.wordpress.org for some unknown reason. (This wasn't during the brief api.wp.org outage, and it worked otherwise.)
Problem is, update-core was completely oblivious to this. It's even worse when running 3.1, because the 'Check Again' button will refresh the page and tell you we last checked for updates *just now*.
Try Again or Check Again should reflect that the API is unreachable when this can be determined. Claiming that we checked for updates is also really lame, so we should see if the transient tells us how long it's been since the last one.
Side note, the plugin install et al. HTTP error messages are rather cryptic, and we should also make those more user friendly." nacin
Needs Dev / Bug Wrangler Feedback 16820 Browser uploader in media library shows no error information Upload 3.1 normal minor Awaiting Review defect (bug) new dev-feedback 2011-03-10T11:45:54Z 2011-03-11T04:53:19Z "In `wp-admin/media-new.php`, if you use the browser uploader, you get no information about errors.
For example if the file you upload is too large, you just get redirected to the media library with the message ""Error saving media attachment."" Not very helpful - and also inconsistent - because if you do exactly the same thing using the pop-up image editor (i.e., select ""Add an Image"" from the Upload/Insert menu while editing a post), then you do get useful error information.
I propose that if there are errors, the user should not be redirected to the Media Library. Instead Wordpress should wp_die telling them what went wrong." solarissmoke
Needs Dev / Bug Wrangler Feedback 17547 Image upload issues - Size reported as 0x0 Upload 3.1.2 normal critical Awaiting Review defect (bug) new dev-feedback 2011-05-24T08:27:21Z 2012-05-16T17:35:28Z "When I upload any image of any size to my wordpress installation the image uploads fine, but the size is reported as 0x0 and has only one option of inserting it as a full-sized image!
Further inspection of this issue has led me to believe that it lays with wordpress not inserting the correct (if any) meta data for the attachment into the database.
As you can see in the image below, the meta data is present and this image shows all options of inserting the image in the post at all sizes specified in the WordPress media settings panel.
http://www.millerswebsite.co.uk/images/meta%20data.jpg
But as you can clearly see from the image below, when the meta data is missing it shows you can't post the image at any size except full which is stated as 0x0px - Clearly something is wrong!
http://www.millerswebsite.co.uk/images/no%20size.jpg
Many people have had and are still having this issue since 2.5. There are quite a few forum threads relating to it with not a single word from anyone from WordPress.
Several tickets have been submitted to the WordPress Trac system with the issues going unresolved. This is a major problem and many people have reported it, yet nothing seems to have been done.
Sources :
http://core.trac.wordpress.org/ticket/12532
http://wordpress.org/support/topic/cant-adjust-media-file-size-since-upgrading-to-27
http://wordpress.org/support/topic/images-upload-fine-but-wp-shows-0x0-size
http://wordpress.org/support/topic/add-image-size-only-allows-fullsize-with-0x0-dimensions
http://wordpress.org/support/topic/image-upload-in-wp-28-with-translation
If any solution exists to this problem, please let me know, I have been searching for weeks now to no avail. When I talk about solutions, I do not mean using plugins to ""regenerate thumbnails""! Yes I know this works, but it does not solve the problem as its only a temporary fix. Plus it needs to regenerate the images every time you upload a new image.
Side note :
I have tried a completely new installation of WordPress with and with out plugins on a completely different database. I have uploaded and re-uploaded the WordPress files also.
This is the type of image I am uploading. I took it on my Nikon D3100 and compressed to 80% @ 960x768 which makes it 83KB so it's not exceeding any upload limits and I am still having problems.
http://www.millerswebsite.co.uk/images/wordpress/DSC_2165.jpg
My host claims it is not their fault and they have recompiled apache and php for me, the php memory limit is also set to 128mb and file upload size is limited to 8mb.
A phpinfo() can be seen here : http://www.millerswebsite.co.uk/info.php
My original complaint can be seen on the forums here : http://wordpress.org/support/topic/image-upload-issues-size-reported-as-0x0?replies=10" David_Miller
Needs Dev / Bug Wrangler Feedback 18474 Misleading error message when theme ZIP exceeds post_max_size Upload 3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2011-08-18T16:16:03Z 2011-08-23T22:46:14Z "''post_max_size'' is 32MB, now try to uploading a 40MB big ZIP.
You will get the ''Are you sure you want to do this? Please try again.'' message. But ''try again'' will not help.
Notice:
''Warning: POST Content-Length of 47774864 bytes exceeds the limit of 33554432 bytes in Unknown on line 0''" ocean90
Needs Dev / Bug Wrangler Feedback 16191 Uploaded files with quote marks in the filename are undisplayable in MS Upload normal normal Future Release defect (bug) reopened dev-feedback 2011-01-11T19:28:49Z 2011-01-14T03:17:05Z "If you upload a file with quote marks in the filename, e.g. `""Test"".jpg`, WordPress records the filename as `%22test%22.jpg` but the file is called `""Test"".jpg` (on 'nix-like systems anyway) so is undisplayable.
I'm unsure about the implications (security and otherwise) of my suggested patch (attached), so please give feedback. (I guess the other approach would be to retain the url-encoded characters and ensure that the file is named with the URL encoded version of the filename.)" simonwheatley
Needs Dev / Bug Wrangler Feedback 18039 Allow apostrophes in email addresses when accounts are added via Dashboard Users 3.2 normal normal Awaiting Review defect (bug) new dev-feedback 2011-07-08T16:36:55Z 2013-04-02T09:54:29Z "See #4616.
Currently it's not possible to add a user with an apostrophe in his email address in any of the following ways:
- Dashboard > Add User (non-MS)
- Dashboard > Add User > Add Existing User (MS)
- Dashboard > Add User > Add New User (MS)
With existing users, you get a 'user not found' error. Otherwise you get an error about invalid email addresses.
This is inconsistent with WP's basic email address behavior, which allows apostrophes in email addresses.
For the most part, the problem is simply that the value of 'email' in the $_POST data must be stripslashed. In a few cases, adjustments had to be made to the way that email addresses are escaped, to allow for the ' character (see esc_email()).
See attached patch." boonebgorges
Needs Dev / Bug Wrangler Feedback 16788 Ampersands in e-mail address become invalid Users 3.0.5 normal major Awaiting Review defect (bug) new dev-feedback 2011-03-07T20:01:38Z 2012-09-19T17:46:32Z "When an e-mail address contains an ampersand, WordPress improperly escapes the ampersand invalidating the e-mail address.
Example: h&f@domain.com becomes h&@domain.com
First of all, the proper HTML entity for ""&"" is '''&'''. Where did the extra '''amp''' come from?
Also, an ampersand is a valid character in an e-mail address and should not be escaped. Escaping it could be a completely different e-mail address.
I have not dug into the code to find out where this is happening but I'd assume in '''sanitize_email()'''." jfarthing84
Needs Dev / Bug Wrangler Feedback 9640 wp_update_user() blindly calls add_magic_quotes(), even on objects Users 2.8 normal normal Future Release defect (bug) reopened dev-feedback 2009-04-24T18:14:53Z 2011-10-12T05:41:40Z "If there's an object stored in usermeta, then the call to add_magic_quotes() will lead to an error in wpdb::escape():
{{{
Catchable fatal error: Object of class stdClass could not be converted to string in /web/ven/wp-includes/wp-db.php on line 472
}}}
http://core.trac.wordpress.org/browser/trunk/wp-includes/registration.php
See also #9638. The two problems are related, but probably need to be solved independently. " misterbisson
Needs Dev / Bug Wrangler Feedback 21061 Can't drag an opened widget to other widget area Widgets 3.4 normal normal Awaiting Review defect (bug) new dev-feedback 2012-06-24T19:43:44Z 2012-06-24T19:43:44Z "the placeholder does not appear and the option to drag the opened widget is not possible, to fix this: to auto-close the widget before drag event (sortable) or add option to accept opened widgets
http://wpimpact.com/wp-content/uploads/2012/06/Untitled-5.png" alexvorn2
Needs Dev / Bug Wrangler Feedback 19695 Links widget does not generate width or height attributes when showing an image Widgets 3.3 normal normal Awaiting Review defect (bug) new dev-feedback 2011-12-30T07:10:48Z 2011-12-31T07:41:57Z "It's a best practice to include width and height attributes in image tags to prevent reflows when the browser renders the page. Both PageSpeed and YSlow include rules that measure this.
{{{_walk_bookmarks()}}} in {{{/wp-includes/bookmark-template.php}}} does support adding images to the output of the Links widget. However, it doesn't output the width or height attributes.
It is possible to size images with CSS instead of by tag attributes (and PageSpeed rules consider this acceptable). But it doesn't seem ideal to force users to set dimensions in CSS, when the Link edit page doesn't accept CSS directly. Plus, I think it's best to have all the meta info about something in one place, not to set an image in a WP link, and then the dimensions in a theme's CSS file." mbijon
Needs Dev / Bug Wrangler Feedback 12342 New widget option after calling register_widget creating empty widget azaozz Widgets 2.9.2 normal normal Future Release defect (bug) new dev-feedback 2010-02-23T00:36:39Z 2010-11-13T07:45:48Z "After I register a new widget class that has never been registered before, navigate to the widgets.php admin page and allow the option to be created automatically. The option value looks like this as serialized data:
{{{
a:2:{i:2;a:0:{}s:12:""_multiwidget"";i:1;}
}}}
As you can see there is an empty widget in there for some reason. Basically the unserialized option value looks like the following as an array:
{{{
array( '2' => array(), _multiwidget => 1 );
}}}
This is odd behavior since the first multi number has always started at 2, but with that previous array in there it starts at 3, and randomly which is what irks me. i can't seem to find when it happens or a pattern, so naturally this feels like a bug.
As this does not seem to break anything with the core functionality of WordPress, I would say this is normal priority. What this does do is pose many questions for those of us that dive deep into the Widget API, where our plugins and the functionality of them are dependent on how these things work. My widget plugin is quite large, and I need to know if I can depend on the first multi number of a widget when the class is first registered.
If this is not a bug, and normal functionality, I apologize, and would like to ask for a heads up on the subject.
Thank You,
Jim Isaacs" jimisaacs
Needs Dev / Bug Wrangler Feedback 18446 Widget removes fields w/ default HTML on initial save in IE8 and 9 Widgets 3.2.1 normal normal Awaiting Review defect (bug) new dev-feedback 2011-08-16T15:51:02Z 2011-08-17T02:43:18Z "Weird problem, testd in IE8/9, Chrome, and Firefox. If you have a widget, with HTML in the default value, IE8/9 will remove the field entirely. However, if you then paste the HTML back into the field and save, it works fine. This ONLY happens after the initial drag/drop then save of the widget. It even happens if you drag/drop the widget, change the field and click save.
Example Plugin: http://wordpress.org/extend/plugins/ft-calendar/
Widget: Upcoming Events Widget
The Event Template (event_template) is set by default to:
{{{
%TITLE%
}}}
The event_template source for the Available Widget is:
{{{
}}}
The event_template source for the widget after it is dragged to a widget area is:
{{{
}}}
The source for the widget after it is first saved is:
{{{
}}}
I setup a test to output $new_instance and $old_instance during the ""update"" process.
Step 1: Moving widget from Available Widgets to Widget Area (in IE):
{{{
NEW INSTANCE:
Array
(
[title] =>
[date] =>
[number_of] => 1
[date_types] => Month
[limit] => 0
[timeformat] => g:i a
[dateformat] => jS
[date_template] => %DATE%
[monthformat] => F Y
[month_template] => %MONTH%
)
OLD INSTANCE:
Array
(
)
}}}
Step 2: Saving widget in Widget Area:
{{{
NEW INSTANCE:
Array
(
[title] =>
[date] =>
[number_of] => 1
[date_types] => Month
[limit] => 0
[timeformat] => g:i a
[dateformat] => jS
[date_template] => %DATE%
[monthformat] => F Y
[month_template] => %MONTH%
)
OLD INSTANCE:
Array
(
[title] =>
[show_rss_feed] => off
[show_ical_feed] => off
[date] =>
[span] => +1 Month
[number_of] => 1
[date_types] => Month
[calendars] =>
[limit] => 0
[dateformat] => jS
[timeformat] => g:i a
[monthformat] => F Y
[event_template] =>
[date_template] => %DATE%
[month_template] => %MONTH%
[hide_duplicates] =>
)
}}}
Step 3: Pasting HTML code back into Event Template and saving Widget:
{{{
NEW INSTANCE:
Array
(
[title] =>
[date] =>
[number_of] => 1
[date_types] => Month
[limit] => 0
[timeformat] => g:i a
[dateformat] => jS
[date_template] => %DATE%
[monthformat] => F Y
[month_template] => %MONTH%
[event_template] => %TITLE% (%TIME%)
)
OLD INSTANCE:
Array
(
[title] =>
[show_rss_feed] => off
[show_ical_feed] => off
[date] =>
[span] => +1 Month
[number_of] => 1
[date_types] => Month
[calendars] =>
[limit] => 0
[dateformat] => jS
[timeformat] => g:i a
[monthformat] => F Y
[event_template] =>
[date_template] => %DATE%
[month_template] => %MONTH%
[hide_duplicates] =>
)
}}}
Here is a screenr showing the problem not working in IE9 and working in Chrome: http://www.screenr.com/mkhs
" layotte
Needs Dev / Bug Wrangler Feedback 21977 Allow 0, NULL and empty string values for 'parent'. XML-RPC normal normal Future Release defect (bug) new dev-feedback 2012-09-23T18:28:04Z 2012-11-07T21:51:29Z We must allow 0, NULL and empty string values for 'parent' in wp_newTerm and wp_editTerm sam2kb
Needs Dev / Bug Wrangler Feedback 12939 Counterpart to content_save_pre hook not called when getting post content via API josephscott XML-RPC 2.9.2 normal normal Future Release defect (bug) reviewing dev-feedback 2010-04-09T13:53:57Z 2011-04-05T08:50:45Z "When a post is submitted either through the web editor interface or from an API call to newPost or editPost, the content of the post is inevitably passed through the content_save_pre filter.
And when a post is opened for editing in the web editor, the content is passed through filters such as the_editor_content and content_edit_pre.
However, when a post is fetched for editing via XMLRPC API calls such as getPost or getRecentPosts, the content_edit_pre filter is never reached.
This leads to a situation where whatever massaging of the content that a plugin may peform on the way into the database is not reversed on the way back out, for clients of the API. A concrete example of this problem is with the popular Syntax Highlighter Evolved:
http://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/
This plugin performs encoding of the post content before it is stored in the database, and it counts on being able to decode that content by adding filters to hooks such as the_editor_content. However, none of these filters are reached via the API, leading to ""corrupted content"" when users try to edit posts from API clients such as the iPhone WordPress app, or my desktop editor, MarsEdit.
(My previous bug report #10802 exhibits the same symptoms of this bug, but this is a different cause).
In summary:
1. WordPress needs to establish a clear, baseline hooks for massaging content before it is saved to the database, and for un-massaging the content on the way out of the database. Currently there seems to be uncertainty about which hooks need to be overridden and under what circumstances. It seems to me that content_save_pre and content_edit_pre are probably good candidates for this.
2. Whatever hooks are established as the guarantees need to be applied once and only once in both the web-based editing scenario, and in the API editing scenario.
I think that having a well documented pair of hooks for this purpose that works identically in the web editing and API editing cases will do a lot to ensure correct behavior when plugins are installed that massage content, and will make it easy for plugin developers to ""do the right thing"" without relying on hooks that are specific only to the web editor, or to the API.
" redsweater
Needs Dev / Bug Wrangler Feedback 20070 Deprecate Blogger XML-RPC Methods XML-RPC 3.3.1 normal minor Awaiting Review defect (bug) new dev-feedback 2012-02-18T18:32:26Z 2012-02-18T18:32:58Z "The XML-RPC API supports the legacy Blogger API methods, but these methods have apparently not been very well tested or maintained.
Given that the `wp.*` XML-RPC namespace now covers everything that the Blogger API does, I suggest the blogger methods be officially deprecated with an eye towards removing them in a future version.
At the very least, the MetaWeblog API should be used by clients instead, as it was explicitly designed to enhance and supersede the Blogger API." maxcutler
Needs Dev / Bug Wrangler Feedback 14452 Duplicate check for comments: Inappropriate errorhandling for xmlrpc XML-RPC 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-07-29T08:44:34Z 2012-06-23T22:48:28Z The duplicate check for comments just dies in case a dulicate is detected(see wp-includes/comment.php around line 550). This ends up with a html page delivered in any cases. When accessing through xmlrpc this leads to the problem that this html page is send back to the xmlrpc client instead of a proper xmlrpc formated message. mrutz
Needs Dev / Bug Wrangler Feedback 16980 Empty Values are ignored by class-ixr.php XML-RPC 3.1 normal major Awaiting Review defect (bug) new dev-feedback 2011-03-27T12:34:47Z 2011-05-25T05:19:53Z "I tried to fix the following bug #10599
Found out when you send and empty value via xmlrpc it converts it to null value.
Say you send and array of arguments for mw_editpost, set
{{{
$content_struct[mt_keywords] = '';
}}}
IXR client passes a null value instead of an empty value.
In mw_post method consider this statement
{{{
$tags_input = isset( $content_struct[mt_keywords] ) ? $content_struct[mt_keywords] : null;
}}}
Even if you send an empty value this statement fails because
{{{
$content_struct[mt_keywords]
}}}
is set to null by IXR client." nprasath002
Needs Dev / Bug Wrangler Feedback 21098 Out of memory errors in XML-RPC XML-RPC 3.4 normal major Awaiting Review defect (bug) new dev-feedback 2012-06-28T13:48:53Z 2012-09-23T19:43:33Z "Since WPiOS 3.0 and WordPress 3.4 we're getting a lot of ""Out of Memory"" reports on XML-RPC.
See http://ios.forums.wordpress.org/topic/couldnt-sync-posts-after-update-to-300
XML-RPC clients have no idea of the memory available, and even if they did it'd be hard to translate that to ""how many items can I request""
Some ideas:
* Can we try raising the memory limit on xmlrpc.php, or at least for system.multicall?
* Setting limits on the number of items returned if we can predict that they're going to need too much memory. Currently asking for the latest 100 comments can trigger an out of memory error in some hosts.
* Fail more gracefully: return an XML-RPC error instead of a HTTP 500 Internal Server Error
* Any hints on debugging where memory is going and if there are any leaks?" koke
Needs Dev / Bug Wrangler Feedback 17920 Unnecessary code in wp.getPage XML-RPC 3.2 normal minor Awaiting Review defect (bug) new dev-feedback 2011-06-28T16:33:00Z 2012-06-24T20:22:32Z Pages Does not have categories nprasath002
Needs Dev / Bug Wrangler Feedback 10764 XML- RPC, blogger_editPost, Publish Status not working josephscott XML-RPC normal normal Future Release defect (bug) new dev-feedback 2009-09-10T00:58:09Z 2012-06-23T20:39:22Z "In the blogger_editPost function in xmlrpc.php is not working properly. Currently you cannot change publish status. It looks like we are missing a line of code.
{{{
$post_status = ($publish) ? 'publish' : 'draft';
}}}
When I inserted this line into the function before the
{{{
$postdata = compact('ID', 'post_content', 'post_title', 'post_category', 'post_status', 'post_excerpt');
}}}
I was able to gain control of the publish status.
" bobby_drk
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 12257 wpdb Scales Badly Due to Unnecessary Copies of All Query Results ryan Database normal critical Future Release defect (bug) reopened early 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
Needs Early Attention 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
Needs Early Attention 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
Needs Early Attention 20903 Exporter gets stuck in a loop a loop/break in the category hierarchy westi Export 3.1 normal normal Future Release defect (bug) new has-patch 2012-06-11T11:26:07Z 2012-06-12T08:13:02Z "Ideally it should be impossible for a loop/incorrect parentage in a category hierarchy to exist.
But sometimes they do.
If one does exist then {{{export_wp()}}} gets stuck :(
It gets stuck in this code:
{{{
// put categories in order with no child going before its parent
while ( $cat = array_shift( $categories ) ) {
if ( $cat->parent == 0 || isset( $cats[$cat->parent] ) )
$cats[$cat->term_id] = $cat;
else
$categories[] = $cat;
}
}}}
Similar to #20635 but different." westi
Needs Early Attention 4539 Abbreviated year followed by punctuation or markup doesn't texturize jmstacey Formatting 2.5 low normal Future Release defect (bug) reopened has-patch 2007-06-26T03:36:36Z 2012-12-17T14:49:10Z "An abbreviated year followed by punctuation or markup doesn't texturize properly.
e.g. (Bruce Sterling, '97) is texturized as (Bruce Sterling, ‘97) when the apostrophe should be texturized as ’
e.g.
Casino Royale '06
is texturized as
Casino Royale, ‘06
when the apostrophe should be texturized as ’" pah2
Needs Early Attention 10823 Bad handling of ampersand in post titles Formatting 2.8.4 normal minor Future Release defect (bug) new has-patch 2009-09-21T10:59:50Z 2013-01-23T22:12:06Z "Titles with ampersand (&) are not correctly handled:[[BR]]
1/ the_title_attribute() doesn't transform & to & causing XHTML validation errors[[BR]]
2/ titles with & followed by ; generate truncated post name (slug)
e.g. ""Test this & believe ; what ?"" => ""test-this-what""" Commeuneimage
Needs Early Attention 15367 WordPress strips multiple line breaks inside of
tags garyc40 Formatting 3.1 normal normal Future Release defect (bug) assigned has-patch 2010-11-10T01:39:33Z 2012-09-12T19:49:52Z "Write a post:
{{{
This
is
a
test.
}}}
You end up with this:
{{{
This
is
a
test.
}}}
Probably related to `wpautop()` I imagine." Viper007Bond
Needs Early Attention 10041 like_escape() should escape backslashes too Formatting 2.8 high normal Future Release defect (bug) reopened has-patch 2009-06-05T11:18:16Z 2013-04-16T17:04:06Z "The like_escape() function doesn't escape backslashes.
source:trunk/wp-includes/formatting.php@11518#L2260
{{{
return str_replace(array(""%"", ""_""), array(""\\%"", ""\\_""), $text);
}}}
should be ...
{{{
return str_replace(array(""\\"", ""%"", ""_""), array(""\\\\"", ""\\%"", ""\\_""), $text);
}}}
or simply ...
{{{
return addcslashes($text, '%_');
}}}
Considering multi-byte characters ...
{{{
if (function_exists('mb_ereg_replace')) {
$text = mb_ereg_replace('\\\\', '\\\\', $text);
$text = mb_ereg_replace('%', '\\%', $text);
$text = mb_ereg_replace('_', '\\_', $text);
return $text;
} else {
return addcslashes($text, '%_');
}
}}}" miau_jp
Needs Early Attention 15657 wp_strip_all_tags causes paragraphs to run together Formatting 2.9 normal normal Future Release defect (bug) new needs-unit-tests 2010-12-03T06:05:40Z 2011-12-27T20:49:30Z "If a post contains HTML like ""foo
bar"", the RSS feed ends up with the text ""foobar"" instead of the more appropriate ""foo bar"" or even ""foo\n\nbar"".
Here is a simple patch to wp-includes/formatting.php that fixes this: basically, convert
, and certain similar tags to newlines before calling the PHP-builtin strip_tags() function.
" jwz
Needs Early Attention 15918 wpautop() breaks inline tags on the same line as block tags dunno Formatting 3.0.3 normal major Future Release defect (bug) new early 2010-12-20T16:01:31Z 2012-04-11T15:22:31Z "Hi guys! I've got latest WP installation (3.0.3) and found strange bug in posts parser.
Create article with following HTML:
{{{
but who cares. All seems to be OK.
Create article with following HTML:
{{{
WP IZ ASSUM
}}}
Browser will get:
{{{
WP IZ ASSUM
}}}
Now isn't that cool? But check what is even cooler!
Create article with following HTML:
{{{
WP IZ ASSUMNO IT'S BUGGY AS HELL
}}}
Browser will get:
{{{
WP IZ ASSUM
NO IT’S BUGGY AS HELL
}}}
Wow! Say hello to invalid markup and rendering problems! Auto-closing of tags turned off. No matter of the settings I still get this nice messed up html. WYSIWYG turned off also." retrib
Needs Early Attention 13821 Changing visibility to password-protected without entering a password does not warn user kapeels* General normal normal Future Release defect (bug) accepted has-patch 2010-06-10T13:48:48Z 2012-10-01T17:42:25Z "Tested on r15182.
If the status of a post is set to Password Protected, and a password is not specified before the user clicks the OK button in visibility and then either publishes, saves, or updates the post, no warning is given to the user that not setting a password forces the post or page to remain Public.
In fact, if updating a post, and this is the only change made, the success message (1) for updating the post appears instead, even though no change was made to the post.
If the post was previously published as Private, and switched to Password Protected without entering a password, then saved, the post switches to Public on save instead of remaining Private.
Either a failure message upon updating or a warning to the user before saving should be displayed to the user to remind them that they didn't properly set a password.
To reproduce the last case above:
1. Create a post. Publish it as Private.
2. Edit the post. Change the visibility to Password Protected, but do not enter a password. Click OK.
3. Update the post.
4. The post visibility will be changed to Public." markel
Needs Early Attention 19120 Interim login needs some work azaozz General normal normal Future Release defect (bug) assigned early 2011-11-02T22:46:42Z 2012-05-02T19:43:33Z "A CSS style causes a white 20px stripe at the top of the otherwise gray interim login screen.
That should go, and azaozz thinks the popup should as well.
3.3 for now, but the rest may be punted by azaozz." nacin
Needs Early Attention 20569 We need addslashes_deep() General 3.4 normal major Future Release defect (bug) new has-patch 2012-04-29T08:08:28Z 2012-09-02T03:15:55Z "
I don't imagine anyone still feels that having `update_metadata()` call `stripslashes_deep()` is still the Right Thing to do, but I understand why removing it is basically impossible for backward compatibility reasons.
That said, !WordPress as a platform does not currently provide a way for this data to be stored accurately as a meta value:
{{{
$data = array(
'Check me out, I have backslashes \\'
);
update_post_meta($post->ID, 'my_key', $data);
}}}
I'm not saying that this is a great deal better from a code purity standpoint:
{{{
$data = array(
'Check me out, I have backslashes \\'
);
update_post_meta($post->ID, 'my_key', addslashes_deep($data));
}}}
but it's at least explainable.
Telling people they have to do something like this:
{{{
$data = array(
'Check me out, I have backslashes \\'
);
$slashed_data = array();
foreach ($data as $item) {
$slashed_data[] = addslashes($item);
}
update_post_meta($post->ID, 'my_key', $slashed_data);
}}}
or this:
{{{
if (!function_exists('addslashes_deep')) {
/**
* Navigates through an array and adds slashes to the values.
*
* If an array is passed, the array_map() function causes a callback to pass the
* value back to the function. Slashes will be added to this value.
*
* @since 3.4.0? (oh please, oh please, oh please)
*
* @param array|string $value The array or string to be slashed.
* @return array|string Slashed array (or string in the callback).
*/
function addslashes_deep($value) {
if ( is_array($value) ) {
$value = array_map('addslashes_deep', $value);
} elseif ( is_object($value) ) {
$vars = get_object_vars( $value );
foreach ($vars as $key=>$data) {
$value->{$key} = addslashes_deep( $data );
}
} else {
$value = addslashes($value);
}
return $value;
}
}
$data = array(
'Check me out, I have backslashes \\'
);
update_post_meta($post->ID, 'my_key', addslashes_deep($data));
}}}
is just indefensible.
FWIW, @rboren created this function as [http://core.trac.wordpress.org/attachment/ticket/12402/12402.2.diff part of a patch] a couple of years back (#12402), but it hasn't landed yet. Pretty please can we get just this bit in for 3.4?" alexkingorg
Needs Early Attention 17923 add_query_arg() should encode values General 3.2 normal normal Future Release defect (bug) new has-patch 2011-06-28T22:55:50Z 2013-02-26T14:08:52Z "One (or me at least) would expect that the result of
{{{
add_query_arg( 'foobar', 'this&that', 'index.php' )
}}}
would be
{{{
index.php?foobar=this%26that
}}}
since the whole purpose of the function is to build a URL. However the actual result is
{{{
index.php?foobar=this&that
}}}
You're asking to the function to create a URL in which `foobar` is `this&that` but instead it creates a URL in which `foobar` is set to only `this`. You shouldn't have to pre-encode values -- the function should take care of it for you.
The function to ""blame"" for this is our `build_query()` which for some reason does not encode by default.
Semi-related: #16943" Viper007Bond
Needs Early Attention 16221 admin bar hover class toggle adds whitespace koopersmith* General 3.1 low normal Future Release defect (bug) accepted close 2011-01-13T22:32:25Z 2012-12-13T19:52:17Z "Every time I mouseover and mouseout an admin bar item, its class attribute gets longer.
Seen in Chrome while inspecting elements in the admin bar." andy
Needs Early Attention 22781 setUserSetting cannot handle hyphens General 2.7 normal normal Future Release defect (bug) new early 2012-12-06T06:18:39Z 2012-12-06T18:25:43Z "sanitize_key() can, setUserSetting should be able to as well. It's not that sanitize_key() plays a role, but it sets expectations for what is allowed in keys across core. Both keys and values should be able to accept a hyphen.
The post-thumbnail image size cannot be remembered, for example, if it is added to image_size_names_choose." nacin
Needs Early Attention 13841 Some HTTP Transports do not respect transfer timeouts HTTP 3.0 normal normal Future Release defect (bug) new has-patch 2010-06-11T04:48:30Z 2012-08-03T01:30:39Z "While doing some testing I found that fopen, fsockopen and streams do not respect transfer timeouts.
Out fopen transport cannot support a transfer timeout properly because we do not pass the 3rd optional parameter to fopen for stream context. We don't do this on purpose because the 3rd parameter was not added until php 5, and that is partially what the streams transport is designed to cover. So in short, unless we want to conditionally use the streams context here for php versions > 5, we cannot reliably use transfer timeouts.
The streams timeout was missing the context for timeout, which does support ""microtime"". However, unsure at this point why, but the timeout needs to be divided by 2, so that the timeout happens requested timeout.
With fsockopen, we need to actually test for the timeout during the while loop, because the stream_set_timeout applies to each pass of fread and not the total process." sivel
Needs Early Attention 16606 WP_Http_Streams::test doesn't check enough to confirm if it can do HTTPS HTTP 3.0.5 high major Future Release defect (bug) new has-patch 2011-02-21T08:16:44Z 2013-01-20T20:44:55Z "The WP_Http_Streams doesn't check for all it's prerequisites before saying it can process HTTPS request.
It seems to be common for the openssl extension to no be loaded.
Example Warnings:
{{{
[21-Feb-2011 08:06:48] PHP Warning: fopen() [function.fopen]: Unable to find the wrapper "https" - did you forget to enable it when you configured PHP? in .../wp-includes/class-http.php on line 1063
[21-Feb-2011 08:06:48] PHP Warning: fopen(https://example.com/feed/) [function.fopen]: failed to open stream: No such file or directory in .../wp-includes/class-http.php on line 1063
}}}
We need to at least check: {{{extension_loaded( 'openssl' )}}}
" westi
Needs Early Attention 22302 Multisite administration - default date format I18N 3.1 normal normal Future Release defect (bug) new has-patch 2012-10-29T15:11:58Z 2012-11-07T18:17:39Z "1) There is default non-translatable format for dates in multisite administration:
Sites - All sites (columns Last Updated and Registered)
Users - All users (column Registered)
Please see attached patch, I used existing localization format.
2) Sites - All sites - Edit any site. There are also Registered and Last Updated values in default date format, but I am not sure how to solve this issue..." pavelevap
Needs Early Attention 13651 Problem with plural form in comments_number nbachiyski I18N 3.0 high major Future Release defect (bug) new has-patch 2010-05-31T07:55:14Z 2013-04-10T16:06:03Z "Hi, there is problem with comments_number in WordPress (and also Twentyten theme). There is possibility to use 0, 1 or more comments. But for Czech there are also two plural forms: 0 (žádný komentář), 1 (1 komentář), 2-4 (komentáře) and 5 and more (komentářů).
Function comments_number does not support it, also in Twentyten it is not possible..." pavelevap
Needs Early Attention 20974 Remove obsolete locale-specific files on upgrade dd32 I18N 3.4 low normal Future Release defect (bug) assigned has-patch 2012-06-15T14:06:43Z 2012-11-07T20:20:44Z "We used to have `wp-content/languages/ru_RU.css` file in ru_RU package.
Since #19603, it's no longer needed, but is still left over on upgrade. We should probably include it in `$_old_files`.
I suppose the same applies to zh_CN and he_IL packages ([19825])." SergeyBiryukov
Needs Early Attention 19730 "Death ""Add Media"" link after permanently deleting media items." Media 3.3 normal minor Future Release defect (bug) new has-patch 2012-01-04T10:30:13Z 2012-05-01T13:27:10Z "After deleting a media item permanently and try to directly add a new one via the 'title-menu-link' (the button-link near the ""Media"" title in the admin screen) will result in a death link (""Invalid post type"").
Follow these steps to reproduce the death link(s):
If you have no '''unattachted''' media in your library, first do this:
- Media > Add New
- From the 'title' menu ""Add New"" (Button near ""Media Library"" at the top)
- Add a random image/file and press ""Save changes""
- You'll get redirected back to the overview of all your media.
If you already have one or more '''unattached''' media items in the library:
- Click on the ""Delete Permanently"" link of the file you just uploaded (the unattached file) (and press oke in the alert dialog)
- This is where something goes wrong: You'r now redirected to the edit.php page where you can read: ""Item permanently deleted."". Now click again on the ""Add New"" link in the title-menu near the title ""Media""
- You're now redirected to an invalid page: ""Invalid post type"".
" Jordi-Fun
Needs Early Attention 16330 media_sideload_image() broken with filenames containing strange characters (e.g., +, %) Media 3.1 normal major Future Release defect (bug) reopened needs-unit-tests 2011-01-21T13:56:19Z 2013-03-17T10:31:55Z "I'm using the {{{media_sideload_image()}}} method in the upcoming version of my [http://wordpress.org/extend/plugins/e107-importer/ e107 Importer script] (see: http://github.com/kdeldycke/e107-importer/blob/b7925fdac6aa43db4be5b7925265a83d95fc62ad/e107-importer.php#L277 ) to upload remote images into WordPress.
This method work as expected with lots of images from a lot of different sources, but fail on URLs containing spaces.
Let me illustrate this bug with an example.
When trying to upload the image located at
{{{
http://home.nordnet.fr/francois.jankowski/pochette avant thumb.jpg
}}}
the result looks like this on the file system: http://twitpic.com/3s0dk7 . As you can see, image file names are clean. But in the Media Manager, here is what you have: http://twitpic.com/3s0e5d . No thumbnails seems to have been created.
Now, trying to fix this, I modified the original URL before calling {{{media_sideload_image()}}} with the following code:
{{{
$img_url = str_replace(' ', '%20', html_entity_decode($img_url));
$new_tag = media_sideload_image($img_url, $post_id);
}}}
With this patch, here is the result on the filesystem: http://twitpic.com/3s0ets . I was surprised by WordPress not sanitizing URLs. Is that normal ?
But the most surprising stuff is in the Media Manager: http://twitpic.com/3s0hup . It looks like thanks to this hack, WordPress somehow succeeded downloading the remote file but messed with filesystem naming. What let me think this ? The Media Manager, get the right image thumbnail dimensions but not the binary payload of the thumbnail (contrary to the case above were no binary nor dimensions are available about the thumbnail).
All of this was tested in WordPress 3.1-RC2.
As for the idea of the patch above, it come from a very old version of my plugin (v0.9) that was based on WordPress 2.3.2. There, I somehow found the root cause of the problem, [http://github.com/kdeldycke/e107-importer/blob/e107-importer-0.9/e107.php#L410 according the comment I wrote 3 years ago]:
{{{
// The fopen() function in wp_remote_fopen() don't like URLs with space chars not translated to html entities
}}}
I should have posted this bug report sooner, as now I've forgotten everything about this issue... :(" Coolkevman
Needs Early Attention 17450 Almost pretty permalinks with non-ASCII characters do not work in Apache westi Permalinks 3.1 normal major Future Release defect (bug) reopened needs-unit-tests 2011-05-16T05:53:14Z 2012-04-27T19:03:50Z Almost pretty permalinks (using PATH_INFO) with non-ASCII characters do not work in Apache; a not found error is returned. The same permalink works in IIS when UTF-8 is used for server variables. It also works when mod_rewrite is used. peaceablewhale
Needs Early Attention 9102 Inverse proxy breaks permalinks ryan Permalinks 2.7 normal normal Future Release defect (bug) new has-patch 2009-02-12T01:58:37Z 2010-04-02T00:34:00Z "I have a WP installation at my university's webspace (on an apache server), say http://myuni.ac.at/mydir/wordpress/ , and an inverse proxy domain http://mydomain.at/ for it.
This means that any request to the latter, eg for http://mydomain.at/2009/02/12/inverse-proxy-trouble/ , is forwarded to http://myuni.ac.at/mydir/wordpress/ , which in turn means that the REQUEST_URI there becomes /mydir/wordpress/2009/02/inverse-proxy-trouble/ . My ''home'' variable is of course set to http://mydomain.at/ (''siteurl'' is set to http://myuni.ac.at/mydir/wordpress/ -- otherwise I wouldn't be able to login to WP).
Unfortunately, when analyzing REQUEST_URI, wordpress chops off the ''home'' path, not the ''siteurl'' one. This may be okay for some purposes, but in the inverse proxy case, permalinks break. For a fix, I had to hack two wordpress core files, namely
wp-includes/classes.php
in function parse_request: change line 162 from
{{{
$home_path = parse_url(get_option('home'));
}}}
to
{{{
$home_path = parse_url(get_option('siteurl'));
}}}
and wp-includes/rewrite.php, in function get_pagenum_link, line 987, same modification.
This is a dirty hack, of course; so I wonder if in general, using the ''siteurl'' path is valid in any case where the ''home'' host differs from the ''siteurl'' host. If so, I suggest changing the affected files in such a manner." Bernhard Reiter
Needs Early Attention 20419 get_sample_permalink() passes the wrong post_status to wp_unique_post_slug() Permalinks 3.3 normal minor Future Release defect (bug) new has-patch 2012-04-11T23:15:38Z 2013-05-09T04:19:10Z "get_sample_permalink() fakes a 'publish' post_status so that it can create a pseudo-permalink for drafts and scheduled posts. Also wp_unique_post_slug() bails when the post_status is 'draft', 'pending', or 'auto-draft', so faking a 'publish' post_status helps there too.
However, that means the incorrect post_status is passed to the 'wp_unique_post_slug' filter at times, creating unexpected behaviour -- namely sometimes the $post_status parameter of the wp_unique_post_slug filter will report a non-published post is published.
The best approach here seems to be to let the wp_unique_post_slug() function know when a fake $post_status is being passed to it, what that status is so it can be passed to the wp_unique_post_slug filter. That way anybody using the filter will always get the actual post status all the time without having to do anything special.
Related: #14111" mintindeed
Needs Early Attention 16055 Only fire 'Side Wide Only' plugin header deprecated notice if the plugin is activated Plugins 3.0 normal normal Future Release defect (bug) new has-patch 2010-12-31T23:13:56Z 2010-12-31T23:25:07Z Apparently it can be fired on a deactivated plugin. That's annoying and confusing. nacin
Needs Early Attention 10535 _wp_filter_build_unique_id issues with the first time a filter is hooked by a class Plugins 2.9 normal normal Future Release defect (bug) reopened has-patch 2009-08-02T12:22:18Z 2013-01-10T20:02:38Z "Ref #8723
The first time _wp_filter_build_unique_id is used to generate an ID the ID returned is different to the second time it is called. This presents a problem if the first ID is used when adding a filter which then needs to be removed later in the app flow... as the IDs don't match the filter is unremovable.
One workaround proposed is to set a wp_filter_id property before add the filter, and this will cause _wp_filter_build_unique_id to bypass the problem code and effectively forces the ""unique"" ID which is generated... this workaround feels unpoetic. ;)" simonwheatley
Needs Early Attention 14881 do_action should not pass empty string by default Plugins normal normal Future Release defect (bug) new has-patch 2010-09-15T20:44:56Z 2012-05-17T21:09:41Z "{{{
function test( $a = true ) {
var_dump( $a );
}
add_action( 'test', 'test' );
add_action( 'test', 'test', 10, 0 );
do_action( 'test' );
}}}
Second example is bool(true) as expected, but the first is a zero-length string.
In this case, since do_action() is not passing any arguments, then no arguments should be passed to test() -- even if by default, one argument gets passed.
The issue here is how do_action() is defined: `function do_action( $tag, $arg = '' );`. There's our zero-length string. Of note, apply_filters() does not have this same issue.
The solution looks something like what I have attached. Has yet to be benchmarked.
Of note, this does not appear to have any direct implications for passing all args by default, as proposed in #14671, but I wanted to reference it anyway." nacin
Needs Early Attention 15335 register_setting() filter for sanitization callback needs to indicate 2 arguments accepted markjaquith Plugins 3.1 normal normal Future Release defect (bug) reopened has-patch 2010-11-08T01:10:46Z 2011-10-12T16:37:35Z "'''register_setting()''' adds the function for sanitization of the option with the following line (wp-admin/includes/plugin.php):
{{{
add_filter( ""sanitize_option_{$option_name}"", $sanitize_callback );
}}}
For users wanting to declare a function for option sanitization, use of the option name within the function is sometimes desired, and is provided for in the filter application inside the '''sanitize_option()''' declaration as such (wp-includes/formatting.php):
{{{
$value = apply_filters(""sanitize_option_{$option}"", $value, $option);
}}}
With the filter always being applied with the option name as the second argument, I see no reason not to propose that the '''add_filter()''' call in register_setting() include ""2"" as the number of accepted arguments, allowing the option name to be passed." lumination
Needs Early Attention 21169 remove_action on a tag within do_action for that tag can cause actions to be missed Plugins normal major Future Release defect (bug) new has-patch 2012-07-05T21:08:22Z 2012-11-07T15:35:21Z "'''Problem:'''
If an action (or filter) in a given priority for a given tag removes itself as part of its execution, and it was the only action/filter at that priority for that tag (or only one remaining), the next priority level is skipped.
'''Reproduction:'''
See the attached unit test.
'''Analysis:'''
This appears to possibly be a bug (or at least an undocumented feature) of PHP (tested up to 5.4.3), where next() falls over if the current array element is unset (but each() has no problem even if the /next/ array element is unset). Example non-WP code demonstrating this is included.
'''Proposed solution / workaround:'''
Switch all uses of next() in plugin.php to use each() instead; I've included a proposed patch.
Props to smathiascrowdfavorite for bringing this bug to my attention." devesine
Needs Early Attention 24248 'guid' not properly escaped Post Types 2.5 normal normal Future Release defect (bug) new needs-unit-tests 2013-05-02T14:03:35Z 2013-05-10T20:37:34Z "Probably related issues: #18274 #19248
'guid' being saved in database not properly escaped, example:
{{{http://www.wordpress.dev/?post_type=changeset&p=57}}} , see the ampersand encode {{{&}}}
It supposed to be {{{&}}} or at least {{{&}}}
Once 'auto-draft' saved, 'guid' is correct: {{{http://www.wordpress.dev/?post_type=changeset&p=57}}}
Once post is saved as 'draft' or published (triggered 'update post' on auto-draft), 'guid' gets malformed.
Source of issue: inappropriate usage of {{{get_post_field()}}} function in the {{{wp_insert_post()}}}
{{{get_post_field()}}} defaults to 'display' context, we not specify context while obtaining field, and in the {{{wp_insert_post()}}} we are not going to display it anywhere, just get, check, and save again, correct?
Attached patch adds the 'raw' context to usage of {{{get_post_field()}}} with 'guid'
" meloniq
Needs Early Attention 21963 Consolidate post insertion APIs Post Types normal normal Future Release defect (bug) new needs-unit-tests 2012-09-22T03:46:24Z 2012-12-27T15:14:44Z "In wp-includes, we have:
* wp_insert_post()
* wp_insert_attachment()
* wp_update_post()
* wp_publish_post()
For saving from the admin, we have:
* edit_post()
* wp_write_post()
* write_post()
'''wp_publish_post()''' is, as of [21942], now wraps wp_insert_post().
'''wp_update_post()''' is a fairly mundane wrapper of wp_insert_post(), but we really should eliminate the differences between the two functions and make it a straight-up wrapper.
'''wp_insert_attachment()''' was a fork of wp_insert_post(), and wp_insert_post() has gotten a lot of improvements that haven't reached wp_insert_attachment(). It doesn't take much to merge these two, though, and make wp_insert_attachment() a wrapper.
'''wp_write_post()''' calls edit_post() if it has a post ID. And since we have had a post ID since the days of auto-drafts, this function is dead code. It's wrapper, '''write_post()''', can also be deprecated.
I'm attaching a patch that takes care of wp_insert_post(), wp_write_post(), and write_post(). wp_update_post() will require a bit more concentration.
Needs testing and unit tests." nacin
Needs Early Attention 22556 A taxonomy archive query for attachments can't return results Query 3.5 normal normal Future Release defect (bug) new early 2012-11-23T15:11:50Z 2012-12-19T20:08:06Z "In #21391 we made it easier to use custom taxonomies for attachments.
Example:
{{{
function ds_register_attachment_taxonomies() {
$args = array(
'label' => 'Color',
);
register_taxonomy(
'image-color',
'attachment:image',
$args
);
}
add_action( 'init', 'ds_register_attachment_taxonomies' );
}}}
This makes it also possible to make a query for this specific taxonomy. Example: 5 images has the term ""red"". The query: !http://example.com/image-color/red/
But: The page returns no attachments.
The query:
{{{
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (404) ) AND wp_posts.post_type IN ('attachment') AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'private') GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 0, 1
}}}
The problem is the `AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'private')` part. Attachments post status is inherit, therefore no results.
The attached patch checks if the current post type is `attachment` and sets the post_status to `inherit`.
I would like to get this in 3.5, since it's one of the new features and could be really annoying,
" ocean90
Needs Early Attention 15949 WP 3.0.x comments popup on pages returning 404 [including posible solution] Query 3.0 normal normal Future Release defect (bug) new has-patch 2010-12-22T17:04:42Z 2010-12-26T23:38:37Z "comments-popup does not work on pages (but still working on blog entries) since the 3.0.x upgrade.
i confirm bug and sollution on both: my own theme and on default them after adding comments_popup_link and comments_popup_script functions.
after a long time looking for a solution i found that the new ""handle_404"" method in class WP (wp-includes/classes.php line 475) is the responsable, substituing this method with an older one from wp 2.x brunch solves the problem.
looks like the new method ""think"" that there is no content when the index file is called with comments_popup parameter on a page id, so it returns a 404 status, as said the old one solves the problem.
" odosuiadan
Needs Early Attention 20904 WP_Query instances getting entangled with $wp_query global Query normal normal Future Release defect (bug) new has-patch 2012-06-11T11:55:39Z 2013-05-14T13:25:32Z "`WP_Query::the_post()` fires `setup_postdata()`, which then uses `get_query_var()`. `get_query_var()`, in turn, calls the `get()` method on the `$wp_query` global object. In this way, WP_Query instances are not truly insulated from each other - they all are tied up with `$wp_query` in a way that seems unnecessary, and causes fatal errors in some cases.
In normal use, you would never really notice the issue, because after the `'init'` action, the following offending line in `setup_postdata()` will return the 'page' query var from `$wp_query`:
{{{
$page = get_query_var('page');
}}}
And, since secondary `WP_Query` instances don't paginate in the same way as the primary query, the 'page' property on those instances doesn't matter much. So, while the value of `$page` is not strictly speaking correct in these cases (it comes from the wrong object), it generally fails silently.
However, if you instantiate a WP_Query object before 'init', you get a fatal error, because `$wp_query->get()` is an undefined method. Here's a simple mu-plugin that will demonstrate the problem:
{{{
function bbg_create_early_wp_query_object() {
$q = new WP_Query( array(
'post_type' => 'post'
) );
if ( $q->have_posts() ) {
while ( $q->have_posts() ) {
$q->the_post();
}
}
}
add_action( 'plugins_loaded', 'bbg_create_early_wp_query_object' );
}}}
My suggested solution is to move the `setup_postdata()` logic into a method of the `WP_Query` class, and then use `$this->get( 'page' )` rather than `get_query_var( 'page' )`, to ensure that you're referring to the query vars of the correct query object. The old function `setup_postdata()` then becomes a wrapper for `$wp_query->setup_postdata()`.
In addition, I modified the way that the `$more` global is set, so that it references the current object as well. This prevents `_doing_it_wrong()` errors when firing up a `WP_Query` instance before `'init'`." boonebgorges
Needs Early Attention 16839 Category Base Should be Slugified Rewrite Rules 3.1 normal normal Future Release defect (bug) reviewing early 2011-03-12T21:42:52Z 2011-08-29T23:45:18Z "Vanilla install of 3.1. Change category base to Foo Bar. Link generated is example.com/Foo Bar/cat (note the %20/space). Clicking link tries to access /FooBar/cat and 404's.
I see there are a few other tickets regarding categories, including #16662 but no specific mention of custom category base.
" miklb
Needs Early Attention 23016 Allow plugins to manipulate WP_Roles ($wp_roles global) on construct Role/Capability 3.5 normal normal Future Release defect (bug) new early 2012-12-20T08:38:46Z 2013-05-14T13:32:58Z "The WP_Roles class is difficult to extend. There are no actions, filters, or intercept points to allow plugins to target it. Because the $wp_roles global can be created anytime (even doing_it_wrong on plugins_loaded) there's no reliable way to modify any part of $wp_roles.
(The only place WP_Roles actually has any action at all is in the set_role() method, which is the least useful function in the class since it noops all user roles if a user has more than one.)
The specific use case I have is bbPress's dynamic roles.
bbPress is unable to add its dynamic roles to the $wp_roles global on switch_to_blog(). Neither of WP_Roles's initialization methods have actions to allow bbPress to add its roles on.
* switch_to_blog() calls $wp_roles->reinit()
* then wp_get_current_user()
* finally $current_user->for_blog()
At no point can bbPress reliably append its roles to $wp_roles->roles, causing the current user to incorrectly be missing their bbPress role for that site.
More over, the WP_Roles::reinit() method seems like a one-use stop-gap to fix a specific problem, that ends up introducing other issues with trying to extend it. If the use_db flag is set to false, it bails early, and there's no way for plugins that don't use database roles to reinitialize their roles correctly again.
The attached patch does two things:
* Removes the reinit() method completely, and instead re-instantiates the $wp_roles global inside switch_to_blog(). WP_Roles::_init() is not a heavy function, and the guts are basically identical between the two methods.
* Adds a byref action to WP_Roles::init() that allow plugins like bbPress to add their dynamic roles anytime $wp_roles is created." johnjamesjacoby
Needs Early Attention 16719 Remove vestige add_users capability Role/Capability normal normal Future Release defect (bug) new has-patch 2011-03-01T20:17:38Z 2012-10-25T20:18:37Z Listed in populate_roles_300() and added in [14174], it was never used. The situation it was presumably introduced for now falls on promote_users. nacin
Needs Early Attention 11623 review options list and update sanitize_option() dd32* Security 2.9 normal normal Future Release defect (bug) accepted early 2009-12-26T01:22:13Z 2010-11-13T01:18:42Z "A lot of options have been added since 2.0.5, and as a result, not all of them have been added to {{{sanitize_option()}}}
Ideally, Options which are to be (int) or absint() should have a filter applied to them here.
Attached patch is for the first option thats brought this up, 'start_of_week' which is tested to be int in some function uses, ignored elsewhere.
I've set this to security as its preventive security.." dd32
Needs Early Attention 5809 Updating a term in one taxonomy affects the term in every taxonomy garyc40 Taxonomy 2.3 high major Future Release defect (bug) reopened has-patch 2008-02-10T02:21:01Z 2013-05-15T08:13:16Z "As reported by klawd on #wordpress and reproduced by me, editing a category will affect a tag with the same name.
{{{
Steps to reproduce:
1. Create a category called Testing
2. Create a tag called Testing
3. Rename the Testing category to Another Test
4. Check the name of the tag
}}}" rmccue
Needs Early Attention 20635 _pad_term_count get's stuck if there is a loop in the hierarchy westi* Taxonomy normal normal Future Release defect (bug) accepted has-patch 2012-05-08T10:31:37Z 2012-12-06T22:51:42Z "Ideally it should be impossible for a loop in a taxonomy hierarchy to exist.
But sometimes they do.
If one does exist then {{{_pad_term_counts()}}} gets stuck :(
When one of these does exist the category widget breaks the front page of your site.
We currently hook {{{wp_check_term_hierarchy_for_loops}}} on {{{wp_update_term_parent}}} and I wonder if there are other places we should be doing this check too." westi
Needs Early Attention 18828 function wp_get_object_terms() passes sql data into `wp_get_object_terms` filter for $taxonomies Taxonomy 3.2 normal normal Future Release defect (bug) new has-patch 2011-09-30T19:07:08Z 2011-11-15T23:55:10Z "In wp-includes/taxonomy.php, the return data is passed through the `wp_get_object_terms` filter using the sql-ready data for $taxonomies, meaning it is quoted and comma seperated, for example ""'category', 'post_tag', 'post_format'"". Even for one taxonomy, it has quotes added, it seems this would be easier to work with if it matched the data passed into the function more closely." postpostmodern
Needs Early Attention 17646 wp_get_object_terms should return arrays of integers for IDs and tt_IDs Taxonomy 3.2 normal normal Future Release defect (bug) new has-patch 2011-06-01T18:00:41Z 2013-05-14T11:39:18Z "Currently when you use ```wp_get_object_terms``` to request an array of IDs or tt_IDs, the array returned contains strings representing the IDs, not integers. This then creates issues if you send the values back into ```wp_set_object_terms``` as it creates terms named as per those strings, rather than associating the term_ids as expected.
Code to prove the issue:
{{{
$term_ids = wp_get_object_terms( get_the_ID(), 'category', array( 'fields' => 'tt_ids' ) );
var_dump( $term_ids );
}}}
Results in:
{{{
array
0 => string '1' (length=1)
1 => string '5' (length=1)
}}}
I believe that the array should have all values cast to integers before they are returned. The attached patch does this by mapping a created function to utilise ```(int)``` for the desired result." simonwheatley
Needs Early Attention 15513 Home Page fails to use page template sometimes filosofo Template 3.1 normal normal Future Release defect (bug) reopened has-patch 2010-11-20T01:33:44Z 2010-12-23T17:05:31Z "If a page is the home page but not also the front page and it has a page template, the page template is ignored. This behavior is counter-intuitive:
* When editing the home-page page, either normally or with quick edit, the page template is shown as being the template.
* When acting as a front page, a page uses its page template if available." filosofo
Needs Early Attention 15729 Better UX after supplying incorrect information to setup-config kapeels* Upgrade/Install low normal Future Release defect (bug) accepted has-patch 2010-12-08T07:19:24Z 2010-12-23T02:42:49Z "In #15682 I added a 'Try Again' button to step 2 of setup-config.php if the credentials were incorrect.
The button is a simple link with a `javascript:history.go(-1)` hack. This should instead be a form with hidden values that submits back to setup-config.php?step=1, and fills out the form so they can try again.
Additional enhancement: If the prefix is malformed (can only contain letters, numbers and underscores), we do a wp_die(). We should again have a form with a 'Try Again' button that returns them.
As an added bonus, incorrect credentials should be filled out (for reference) but marked as incorrect and potentially with the focus set on that field.
Only caveat I can think of: This will require the use of esc_attr(), which we don't have access to yet. Not sure how to solve that without reverting to htmlspecialchars() with some extra work." nacin
Needs Early Attention 16001 Invited Users Can Disappear in MS Users 3.0 normal major Future Release defect (bug) new has-patch 2010-12-27T22:37:15Z 2013-04-22T21:56:32Z "Steps to reproduce:
* In ''Site Admin'', go to Users > Add New
* Add a new user
* You get a message to the effect of, said user needs to respond to an invitation.
Now the user has disappeared. There's no way for a super admin or anybody to search for that user and add her directly, or delete her, or anything like that. If the user doesn't get the email, she's out of luck: that username and email are now reserved for ""a couple of days.""" filosofo
Needs Early Attention 22367 "Usernames with ""@"" char are assumed email addresses, causing incorrect look-up in several places" Users normal normal Awaiting Review defect (bug) new has-patch 2012-11-06T00:45:19Z 2013-01-10T10:57:23Z "'''Problem'''
Usernames containing the ""@"" character are mistakenly assumed to be email addresses when:
* wp-login.php - Resetting passwords
* /wp-admin/user-new.php - Adding an existing user to a site, in multisite
* /wp-includes/user.php - Searching for a user
----
'''Duplicate'''
* Create a user with the login ""@testing""
* Verify the account, etc...
'''Bug in Search'''
* Visit: wp-admin/network/users.php - attempt to search for: ""@testing""
* Result: no users found
* What should happen: find the user
'''Bug in Add New'''
* Visit: wp-admin/wp-admin/user-new.php - attempt to add: ""@testing""
* Result: no users found
* What should happen: add the user
'''Bug in Reset Password'''
* Visit: wp-login.php - attempt to reset password for: ""@testing""
* Result: retrieve_password() accidentally succeeds, because strpos() check returns 0, which is the correct position of the ""@"" character. If the username was ""testing@"" this test would fail
----
'''Solution'''
The attached patch fixes these bugs by using is_email() instead of an strpos() for an @ character." johnjamesjacoby
Needs Early Attention 15394 "Ancient ""Are you sure you want to do this"" now confusing" Warnings/Notices 3.1 normal trivial Future Release defect (bug) new early 2010-11-11T21:51:26Z 2012-09-15T00:14:05Z "The default failing nonce message did not pass the wife test. Asking ""Are you sure you want to do this?"" now that there is no longer ""OK"" and ""Cancel"" buttons is confusing and my wife just asked me ""How do I tell I'm sure?""
Not sure about the best wording, I took the same approach as Twitter's expired OAuth token links with a message that does not let user think there is something to confirm." ozh
Needs Early Attention 12722 Concurrent editing of widgets azaozz Widgets normal normal Future Release defect (bug) new has-patch 2010-03-26T18:07:46Z 2013-04-25T05:39:22Z When two admin users edit widgets at the same time which ever one saves last wins. I think we'd need something like the post edit lock to be able warn users when someone else is already editing widgets. josephscott
Needs Early Attention 17541 Blogger-XMLPRC API does not work with Multisite/SSL/DMZ combination westi* XML-RPC 3.2 normal major Future Release defect (bug) accepted has-patch 2011-05-23T07:26:29Z 2012-12-14T23:12:02Z "I have the following setup:
My WordPress Blogs (multisite) are set up behind a firewall that exposes the public address via SSL. Inside my DMZ I'm only using HTTP, so that's what WordPress sees. When I now try to access the blogger.getUsersBlogs XMLPRC-API, I get an empty result back.
I analyzed the WordPress source code and found out that the blogger.getUsersBlogs method in the file wp-includes\class-wp-xmlrpc-server.php uses another XMLRPC call to the wp.getUsersBlogs method in case of the multisite. I further checked and found out that this appears to be the only case in which WordPress executes a remote call itself to sevice the request. I then replaced the logic in _multisite_getUsersBlogs with the multisite part from wp_getUsersBlogs and it worked.
I aso found an issue that might be related: http://core.trac.wordpress.org/ticket/16402
But since the source code in the trunk still uses the regular IXR_Client, I'm not sure if this would fix the issue.
I attached my fix as a patch, but it's not refactored to remove code duplication since I don't have a dev-environment set up for WordPress.
Michael" michael_k
Needs Early Attention 21292 XML-RPC: wp_upload_bits should act like wp_handle_upload westi XML-RPC 3.0 normal normal Future Release defect (bug) assigned has-patch 2012-07-17T07:01:23Z 2013-05-07T11:37:28Z "At this moment there isn't a check for file size when uploading an image through the XML-RPC. The reason is that the method wp_upload_bits is used. This only checks it does is if the file size is to big for a network installation.
The function check_upload_size() is something what you want except that it will use wp_die() if there is an error like this. The function is used as a filter: wp_handle_upload_prefilter. Which only get applied in the function wp_handle_upload.
We should probably change check_upload_size() a bit so it doesn't use wp_die() but does it somewhere else.
related: #6559 and #21085" markoheijnen
Needs Early Attention 17604 wp.uploadFile overwrite doesn't work XML-RPC 3.2 normal normal Future Release defect (bug) new has-patch 2011-05-29T10:27:21Z 2012-11-08T01:52:09Z "Removing the following lines from the function ''mw_newMediaObject'' file ''class-wp-xmlrpc-server.php'' solves the problem:
{{{
$filename = preg_replace('/^wpid\d+-/', '', $name);
$name = ""wpid{$old_file->ID}-{$filename}"";
}}}
Why are these lines there anyway? overwrite is overwrite.
This, presumably, bug exists in WP 3.1 too." M66B
Needs Docs or Unit Tests 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
Needs Docs or Unit Tests 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
Needs Docs or Unit Tests 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
Needs Docs or Unit Tests 21602 redirect_canonical can lead to infinite loop on index navigation if site url is not all lower case Canonical normal normal Awaiting Review defect (bug) new needs-unit-tests 2012-08-15T21:31:17Z 2013-04-23T07:53:55Z "The function redirect_canonical in wp-includes/canonical.php (WordPress 3.4.1) on line 406 and 422 makes the following check:
{{{
if ( !$redirect_url || $redirect_url == $requested_url )
return false;
}}}
This ensures that it does not attempt to redirect you to the page you requested in the first place. However this function is not case sensitive so if the redirect URL is in a different case than the requested URL then the user can enter an infinite redirect loop. (For example if the Site Address (URL) of the site is set to be in all upper case.)
This function should do a case-insensitive string comparison since domain names are case-insensitive.
The issue only appears to happen with certain plugins installed (ShareThis and PilotPress both led to this issue,) I haven't figured out yet why it's only an issue with certain plugins but it should still be fixed in WordPress to make the proper string comparison. " sreedoap
Needs Docs or Unit Tests 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
Needs Docs or Unit Tests 9993 Rss and atom feeds are dropping some characters Feeds 2.7.1 normal normal Future Release defect (bug) new needs-unit-tests 2009-05-31T23:54:40Z 2012-10-17T19:40:12Z "Blog post with title:
{{{
& > test <
}}}
has the less than ( < ) is stripped from the atom and rss feed.
" pm24601
Needs Docs or Unit Tests 3833 Extra inside blockquote Archibald Leaurees Formatting 2.7 normal normal Future Release defect (bug) new needs-unit-tests 2007-02-21T19:01:26Z 2012-09-10T22:08:20Z "When using blockquote is inserted directly in front of , making the code invalid XHTML.
Example:
{{{
This is a blockquote
}}}
Gives the following result:
{{{
This is a blockquote
}}}
Seems like [http://wordpress.org/support/topic/106474 this forum thread] adresses the same issue in the support forum." audwan
Needs Docs or Unit Tests 4857 More issues with wpautop() mdawaffe* Formatting 2.3 low normal Future Release defect (bug) accepted needs-unit-tests 2007-08-29T06:47:01Z 2009-11-28T06:33:01Z "''Not sure if this should slide into 2.3 or if it can wait for 2.4. Change as need be.''
`wpautop()` has issues with closing ``'s when it comes to HTML.
For example:
{{{
Foo
Bar
}}}
Results in:
{{{
Foo
Bar
}}}" Viper007Bond
Needs Docs or Unit Tests 8775 Numbers in quotation marks get wrong smart quotes Formatting 2.8 normal normal Future Release defect (bug) reopened needs-unit-tests 2009-01-01T18:05:14Z 2013-05-01T15:41:31Z "Have a number in quotation marks, such as {{{""12345""}}} or {{{'12345'}}} and {{{wptexturize}}} converts the right quotation mark to double-prime and prime marks, respectively.
Patch fixes." filosofo
Needs Docs or Unit Tests 20943 Paragraphs get removed in table cells when Visual editor is refreshed Formatting 3.2 normal normal Awaiting Review defect (bug) new needs-unit-tests 2012-06-13T19:06:04Z 2013-04-18T16:14:03Z "As far as I know, this issue has been around since 3.1. It's not a bug in 3.0.4. I even stopped upgrading at 3.0.4 for any sites where I knew the client would need to edit tabular data. For security reasons, it's time to upgrade these and I'd REALLY like this issue to be fixed.
The problem happens when using paragraphs in a table cell. When I hit enter to create a new paragraph within a table cell, it looks fine. If I then hit Update/Publish, when the page refreshes, WordPress converts that paragraph break into a single line break. If I then click Update again, WordPress removes that linebreak entirely and the paragraphs are essentially merged.
I can also reproduce this behaviour without even clicking Update. If you just switch to HTML mode and then back to Visual mode, the same issue occurs." JboyJW
Needs Docs or Unit Tests 20304 Strikethrough does not work for multiple paragraphs in the post editor Formatting 3.4 normal normal Future Release defect (bug) new needs-unit-tests 2012-03-25T20:13:00Z 2012-05-24T07:32:15Z "'''Overview'''
If you have multiple paragraphs of text in the text editor and select all of them and push the strikethrough button, the text appears to be striked through; however, upon publishing/updating, only the first paragraph of text retains the strikethrough.
'''Steps to Reproduce'''
1) In a new post write screen add two paragraphs of text.
2) Select all of the text
3) Click the strikethrough button
4) Viewing the HTML of the rich text editor through web inspector (note that I am not toggling the visual/html tabs) shows:
{{{
text
text
}}}
5) Save post
6) The text in the textarea only has strikeout for the first paragraph.
7) When viewing the source of the content on the front end, you get the following HTML:
{{{
text
text
}}}
'''Other Information'''
I have tried these same steps on a clean install of 3.3.1. The strikethrough works as expected, and produces in all scenarios:
{{{
text
text
}}}
I first had this issue crop up for a .com client approximately 3-4 weeks ago, so this issue may have been introduced with a more recent patch." tollmanz
Needs Docs or Unit Tests 23922 make_clickable() breaks when colon in hash Formatting lowest minor Awaiting Review defect (bug) new needs-unit-tests 2013-04-03T00:41:39Z 2013-04-03T19:31:00Z "`make_clickable()` doesn't like this string:
{{{
http://en.wikipedia.org/wiki/URI_scheme#tel:
}}}
It results in this HTML:
{{{
http://en.wikipedia.org/wiki/URI_scheme#tel:
}}}
Specifically it's the colon that is causing the issue. It can be a part of the URL too, it doesn't have to be a part of an anchor." Viper007Bond
Needs Docs or Unit Tests 4116 wp_texturize to defect certain links in comments and on page Nazgul Formatting 2.2.1 normal normal Future Release defect (bug) reopened needs-unit-tests 2007-04-09T13:29:33Z 2010-11-23T04:53:07Z "the wp_texturize() function in formatting.php (includes) of wordpress breaks links of the domain format (number)x(number).
For example, a comment left by a domain such as www.h4x3d.com, which includes the (4)x(3) in the domain name, renders to www.xn--h43d-rma.com. This breaks the link.
It does occur on the page, but also with in the page comments.
It does also occur when the text with the special combination is not a link, but plain text." h4x3d
Needs Docs or Unit Tests 2833 wpautop breaks style and script tags Formatting 2.0.3 low normal Future Release defect (bug) reopened needs-unit-tests 2006-06-17T20:36:00Z 2012-09-09T21:01:21Z "When I create a post in which I want to include Javascript or some styles, WordPress 'breaks'when showing those posts, because all newlines in the SCRIPT and STYLE tag are converted into BR tags.
Example:
{{{
}}}
Becomes:
{{{
}}}
And:
{{{
}}}
Becomes
{{{
}}}
This happens because wpautop adds those BR tags to the post. (As it should, just not within STYLE or SCRIPT tags.)
I've made a (temporary?) workaround for this by creating a pre and post event for wpautop, which substitute the necessary newlines by a temporary value in the pre event and placing them back in the post event. Although I think this should be incorporated in wpautop itself.
See also: http://wordpress.org/support/topic/76433 and http://wordpress.org/support/topic/76297
While searching trac I also found ticket #2346, which is about the same problem, but which was for 2.0 and self-closed by the submitter?
P.S. I have TinyMCE turned of." Nazgul
Needs Docs or Unit Tests 8912 wptexturize malforms HTML comments that contain HTML tags Formatting 2.7 normal normal Future Release defect (bug) reopened needs-unit-tests 2009-01-21T20:16:08Z 2013-03-18T15:01:17Z "Because it's replacing -- with #8211, a comment like put into the HTML part of a post gets broken.
This makes it difficult for people writing special HTML in posts (like people putting in object tags, or javascript, or whatever) to do that sort of thing.
What is needed is to recognize --> as different from -- and not replace it with the en dash in that case.
" Otto42
Needs Docs or Unit Tests 14754 add_query_arg() refactoring General normal normal Future Release defect (bug) new needs-unit-tests 2010-09-01T16:32:20Z 2011-03-23T19:34:24Z "The function add_query_arg() looks like that it could benefit from a refactoring. Especially the handling of optional parameters (did introduce PHP 4 that language feature?) can benefit by a sligh touch-up.
Attached patch reflects only the first few lines of the function." hakre
Needs Docs or Unit Tests 23881 get_transient() could delete transient timeout options in an unexpected way General 2.8 normal minor Future Release defect (bug) new needs-unit-tests 2013-03-28T11:02:07Z 2013-04-22T21:17:24Z "get_transient() could delete transient timeout options if a given transient name has the ""timeout_"" prefix.
To reproduce:
{{{
set_transient( 'test', 'test', 60*60 );
get_transient( 'timeout_test' ); // will delete the _transient_timeout_test option
}}}
Solution:
Check if get_option( $transient_timeout ) is not returning false.
{{{
if ( false !== get_option( $transient_timeout ) && get_option( $transient_timeout ) < time() ) {
}}}
" tenpura
Needs Docs or Unit Tests 16282 PHP catchable error with get_term_link and WP3.1RC2 Multisite 3.1 normal major Future Release defect (bug) reopened needs-unit-tests 2011-01-18T12:23:37Z 2011-03-08T23:10:45Z "I recently updated my WP Network to 3.1RC2, and suddenly the get_term_link() I was using in the footer gave me this error:
PHP Catchable fatal error: Object of class WP_Error could not be converted to string
It was working fine in 3.0.4" illutic
Needs Docs or Unit Tests 22192 update_metadata() and update_option() strict checks can cause false negatives Performance normal normal Future Release defect (bug) new needs-unit-tests 2012-10-15T03:19:23Z 2012-10-15T10:22:31Z "Given this:
{{{
add_post_meta( $post_id, 'key', 1 );
update_post_meta( $post_id, 'key', 1 );
}}}
The update should not work, because they are the same. However, the meta cache will have ""1"" as a string, and then it will strict compare it to 1 as an integer. Thus, an unnecessary update will run.
Best I can tell, this could also affect update_option().
It is quite common to use integers and booleans directly into these functions. They should be smart enough to recognize that ""1"" == 1 == true and ""0"" == 0 == false, and that any numeric string is also equal to a properly cast integer.
Unit tests needed.
Ticket from which this was spun: #22189, saving navigation menus is slow." nacin
Needs Docs or Unit Tests 24142 Zero value for posts_per_page value in wp_query custom instance and for 'Blog pages show at most' option Query normal normal Awaiting Review defect (bug) new needs-docs 2013-04-20T09:04:16Z 2013-04-20T12:55:34Z "To show no posts if the posts_per_page value is 0.
Currently for custom instances of wp_query, if the value is 0 then this is changed with the value from posts_per_page option from the database. ""get_options( 'posts_per_page' )""
For home page if we set value 0 on the settings page, in wp-admin/options-reading.php, after the saves are changed, this value is changed to 1.
I think for both cases if the posts per page value is 0 then no posts should not display.
" alexvorn2
Needs Docs or Unit Tests 19907 Updating an unpublished draft post in quick-edit mode sets the post's publish date Quick/Bulk Edit 2.7 normal major Future Release defect (bug) new needs-unit-tests 2012-01-27T14:51:32Z 2013-01-14T11:35:22Z "'''Problem:'''
• If you update an unpublished draft post in quick-edit mode, the post's ''publish date'' is saved. [[BR]]
• Then, later on, when you actually publish the post, its publish date is incorrect.
'''Suggested fix:'''
• If the post is a draft, do not automatically set the post's publish date in quick-edit mode.
'''Steps to reproduce:'''
(1) Go to WP-Admin -> Posts.
(2) Create and save a new post. Make sure you click ""Save Draft"" — not ""Publish"".
(3) Note that the post is marked as ""Publish immediately""; that is, it has no publish date.
(4) Go back to WP-Admin -> Posts.
(5) Hover your pointer over the post you just created. Click ""Quick Edit"".
— Note that in the panel that appears, the ""Date"" field is automatically set to [the current date and time].
(6) Click ""Update"" in quick-edit mode.
(7) Hover your pointer over the post you just updated. Click ""Edit"".
— Note that in the Edit Post page that appears, the post is now marked as ""Publish on: [the date and time from step (5)]""
" uxtremist
Needs Docs or Unit Tests 11160 Inconsistancies in Naming and Using Sidebar Names and IDs. azaozz Widgets 2.9 normal normal Future Release defect (bug) new needs-unit-tests 2009-11-17T12:58:55Z 2012-11-22T03:18:21Z "register_sidebar() allows more sidebar names and IDs to be registered than dynamic_sidebar() recognizes as valid names and IDs.
For example, register_sidebar() allows me to name a side bar ""1"" with a id of ""first"". I don't know why anyone would choose those values, but register_sidebar() allows it [1].
{{{ register_sidebar( array('name' => 1, id => 'first') ); }}}
dynamic_sidebar() will not be able to find the sidebar given its name (1).
{{{
if ( is_int($index) ) {
$index = ""sidebar-$index""; /// 1 becomes 'sidebar-1'
...
}}}
The main problem is that dynamic_sidebar() is trying to process both IDs and names through the same variable ($index) while register_sidebar() separates the two with an array ( array('name' => 'Top', 'id' => 'sidebar-1' ).
According to the in-line docs for dynamic_sidebar():
It is confusing for the $index parameter, but just know that it should just work. When you register the sidebar in the theme, you will use the same name for this function or ""Pay no heed to the man behind the curtain."" Just accept it as an oddity of WordPress sidebar register and display.
It does ""just work"" if you never use your own sidebar IDs.
I started looking at this because I wanted to use is_active_sidebar() which tests to see if a dynamic_sidebar() has anything in it. There is no get_dynamic_sidebar(). dynamic_sidebar() sends everything to the browser or returns false.
{{{
register_sidebar( array('name' => 'Top') ); // id defaults to ""sidebar-1""
...
if ( is_active_sidebar('Top') )
dynamic_sidebar('Top');
}}}
Which fails because is_active_sidebar() just completely skips over searching for an id to go with a name. To get it to work you need to know when it was registered. Not something theme authors and designers are going to follow easily. There's a ticket to fix this: [http://core.trac.wordpress.org/ticket/10440 #10440]
{{{
if ( is_active_sidebar(1) )
dynamic_sidebar('Top');
}}}
Like dynamic_sidebar(), is_active_sidebar() converts 1 to ""sidebar-1"". Unlike dynamic_sidebar() it assumes everything is entered as an id.
unregister_sidebar() assumes its parameter (incorrectly named $name, not $id) is an id. But it wants a literal id, like ""sidebar-1"". unregister_sidebar(1) unregisters a sidebar with an id of 1, while dynamic_sidebar(1) tries to display a sidebar with an id of ""sidebar-1"".
=== Widgets (Admin Page) ===
The dynamic_sidebar() function is used by the Widgets management page. So, it is possible to create a sidebar with register_sidebar() that dynamic_sidebar() cannot find. You can populate it with drag and drop [2] and not have it appear on the web site.
== After Patch ==
If committed, this patch would remove the need for tickets [http://core.trac.wordpress.org/ticket/10440 #10440] and [http://core.trac.wordpress.org/ticket/10956 #10956]. It changes the current argument behavior of unregister_sidebar(), but doesn't break backward compatibility. It allows is_active_sidebar(), unregister_sidebar() and dynamic_sidebar() all point to the same sidebar.
=== Before ===
These all refer to the same sidebar:
{{{
is_active_sidebar(1);
unregister_sidebar('sidebar-1');
dynamic_sidebar('Sidebar Top');
}}}
In an admittedly contrived case, dynamic_sidebar() would silently fail to allow this sidebar to show:
{{{ register_sidebar( array('name'=>'Sidebar Top', 'id' => 1) ); }}}
=== After ===
These all refer to the same sidebar (the first two would have broken before the patch):
{{{
is_active_sidebar('Sidebar Top');
unregister_sidebar('Sidebar Top');
dynamic_sidebar('Sidebar Top');
}}}
After the patch this shows fine:
{{{ register_sidebar( array('name'=>'Sidebar Top', 'id' => 1) ); }}}
After the patch it is possible to force an argument to be only a name or only an id:
{{{
is_active_sidebar(array( 'name' => 'Sidebar Top' ));
unregister_sidebar(array( 'name' => 'Sidebar Top' ));
dynamic_sidebar(array( 'id' => 1 ));
}}}
=== Notes ===
[1] register_sidebar() allows the user to override the default setting of: 'id' => ""sidebar-$i"",
[2] When you refresh the Widgets management page the widgets will disappear from the sidebar. They are still attached to a sidebar, but dynamic_sidebar() cannot see the sidebar." CharlesClarkson
Needs Docs or Unit Tests 20630 XML-RPC Extending documentation for methods called with a single param XML-RPC normal normal Awaiting Review defect (bug) new needs-docs 2012-05-07T18:47:46Z 2012-05-07T19:06:01Z "When an XML-RPC method is called with a single parameter, the method will receive the value directly instead of receiving an array with a single value. This seems to be intended, though unexpected, behavior. The documentation should be updated to mention this.
The related code is inside IXR_Server->call()." scott.gonzalez
Needs Docs or Unit Tests 16985 XML-RPC endpoint set the datetime when saving a Draft XML-RPC 3.1 normal normal Future Release defect (bug) new needs-unit-tests 2011-03-28T13:33:46Z 2012-06-24T00:15:12Z "When uploading a draft post from one of the WordPress mobile apps the post date is set to the current time/date, even if the datetime field is not specified on the client request.
This could cause issues, because when you change the post status to ""publish"" it will be published using the date set during the first upload.
On the web dashboard if you do not set the post datetime explicitly, it is not set and hitting publish will then populate the datetime field with the current time.
The same happens if you start a draft on the web and then you publish it using any mobile apps.
details here: http://ios.trac.wordpress.org/ticket/826" daniloercoli
Has Patch / Needs Testing 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
Has Patch / Needs Testing 15926 Give header and background images alt tags Accessibility 3.0 normal minor Awaiting Review defect (bug) assigned has-patch 2010-12-20T22:16:12Z 2013-01-11T11:42:52Z "''Section 1194.22 Web-based Internet information and applications: (a) A text equivalent for every non-text element shall be provided (e.g., via ""alt"", ""longdesc"", or in element content).''
To meet accessibility guidelines, the header images and backgrounds (when supported by a theme) need to be given user-editable alt tags." jane
Has Patch / Needs Testing 22254 """Do you really want to log out"" message after already logged out" Administration 3.4.2 normal normal Awaiting Review defect (bug) new has-patch 2012-10-22T16:21:06Z 2013-02-28T16:03:33Z "1. Log into admin area
2. Open some page within admin area in a new tab (middle click or ""Open link in new tab"" or similar)
3. Select ""Log Out"" in menu in one tab
4. Normal ""You are now logged out."" screen appears
5. Select ""Log Out"" in menu in other tab
6. The following message appears:
{{{
You are attempting to log out of Blogname
Do you really want to log out?
}}}
The content of this message is wrong as the user is already logged out at this point." Ov3rfly
Has Patch / Needs Testing 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
Has Patch / Needs Testing 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
Has Patch / Needs Testing 19069 Admin menu generation doesn't check whether default post types have 'show_ui' as true Administration normal normal Awaiting Review defect (bug) new has-patch 2011-10-27T19:47:06Z 2011-11-16T05:00:27Z While patching #19055, I found wp-admin/menu.php doesn't check whether default post types have 'show_ui' set to true. The Comments menu is also displayed regardless of whether available post types support comments or not. kawauso
Has Patch / Needs Testing 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
Has Patch / Needs Testing 18048 Ctrl+S draft save causes prompt on exit Administration normal normal Awaiting Review defect (bug) new close 2011-07-09T12:25:25Z 2011-11-15T03:45:49Z "When you use the ""save draft"" button and leave the edit page, the ""unsaved changes"" prompt doesn't show up. However, when you save using Ctrl+S and leave - the prompt appears." jakub.tyrcha
Has Patch / Needs Testing 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
Has Patch / Needs Testing 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
Has Patch / Needs Testing 21947 Fix 3-column dashboard display Administration 3.4 low normal Awaiting Review defect (bug) new has-patch 2012-09-20T20:06:46Z 2013-04-14T06:02:52Z "Issue #20015 'enhanced' the dashboard with a pure-CSS based multi-column dashboard. Excellent.
The CSS used makes gross assumptions about how many columns are appropriate for different-sized displays. Double plus ungood.
Users should be left to decide how many columns they wish to use.
There was [http://wordpress.org/support/topic/three-column-dashboard/ considerable discussion] of this when 3.4 was released, but no remedy yet, other than to hack away at the CSS of one's install, precluding upgrades; I've changed {{{@media only screen and (min-width:800px) and (max-width:1200px){}}} to {{{@media only screen and (min-width:800px) and (max-width900px){}}} in wp-admin.css to get a usable interface." belg4mit
Has Patch / Needs Testing 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
Has Patch / Needs Testing 20848 Header images are cropped and resized with improper permissions. Administration 3.3.2 normal normal Awaiting Review defect (bug) new has-patch 2012-06-05T17:41:45Z 2012-06-05T17:41:45Z "On some systems the cropped and resized header images become unreadable by the web server.
The attached patch makes the files inherit the permissions from the parent folder.
" gtenney99
Has Patch / Needs Testing 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
Has Patch / Needs Testing 21015 Months dropdown should not show if only posts are 'auto-draft' status Administration 3.1 normal normal Awaiting Review defect (bug) new has-patch 2012-06-18T19:16:54Z 2012-09-28T14:42:09Z "The months dropdown at the top of edit.php should only show if there are actually posts in the list.
Right now, if you click 'Add new' an auto draft post will be saved. Leave the post edit screen without saving the post (so no draft will be created) and go back to the edit.php screen. There is no post in the list, but the month drop down will be shown because the auto draft is counted." CoenJacobs
Has Patch / Needs Testing 16696 "No synchronisation between ""most used"" and ""all categories"" in link edit" Administration 3.1 normal normal Awaiting Review defect (bug) new has-patch 2011-02-28T07:14:37Z 2011-03-04T14:02:26Z "There are issues with the ""all categories"" and ""most used"" tabs when editing links:
- Go to edit a link
- Click on ""Most used"" in the category section. All the listed categories are unchecked - including the ones that are checked in the ""All Categories"" tab. There is no sync between the two.
- Now check a category in the ""most used"" tab. Go to the ""all categories"" tab and you will find that the same category is now checked (as expected). Now uncheck it from the ""all categories"" tab. Go to ""most used"" and it is still checked there. The sync only works one way ( ""most used"" -> ""all categories"" ).
The first issue is because `wp_popular_terms_checklist()` assumes that you're using it in the context of a particular post, and sets checkedness based on whether the `$post` global has that term. If the `$post` global is empty (as when editing links), nothing is checked. I don't think we should be using `wp_popular_terms_checklist()` as it's context is for individual posts.
The second issue is because the IDs on the most used elements are wrong compared to what the Javascript is looking for.
Patch to follow.
" solarissmoke
Has Patch / Needs Testing 22509 No-JS fallback for default color in color picker Administration normal normal Awaiting Review defect (bug) new has-patch 2012-11-19T19:42:19Z 2012-12-19T20:48:22Z "The no-JS fallback for the color picker is just a plain input. Since the color picker implementation now includes the ability to reset to a specified default, it seems to make sense to include a no-JS fallback for the default, even just as a little bit of hidden descriptive text.
See #22461 for discussion stemming from the custom header screen." helen
Has Patch / Needs Testing 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
Has Patch / Needs Testing 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
Has Patch / Needs Testing 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
Has Patch / Needs Testing 24104 Remove duplicated separators in admin menu Administration 2.7 normal normal Awaiting Review defect (bug) new has-patch 2013-04-16T17:26:37Z 2013-04-17T02:37:08Z "I'm working on WordPress admin menu, and I found that the code to remove duplicated separators in admin menu in `wp-admin/includes/menu.php` doesn't work correctly.
Assuming we have these items in the `$menu`:
{{{
$menu = array(
100 => array(
0 => 'Admin Style',
2 => 'wp-admin-style.php',
1 => 'read',
4 => 'menu-top menu-icon-generic toplevel_page_wp-admin-style menu-top-first menu-top-last',
6 => 'none',
),
110 => array(
0 => '',
1 => 'read',
2 => 'separator1',
3 => '',
4 => 'wp-menu-separator',
),
130 => array(
0 => '',
1 => 'read',
2 => 'separator2',
3 => '',
4 => 'wp-menu-separator',
),
140 => array(
0 => '',
1 => 'read',
2 => 'separator-last',
3 => '',
4 => 'wp-menu-separator',
),
150 => array(
0 => 'Hide Menu',
1 => 'manage_options',
2 => 'hide-admin-menu',
3 => 'Hide Admin Menu',
4 => 'menu-top toplevel_page_hide-admin-menu',
5 => 'toplevel_page_hide-admin-menu',
6 => 'http://localhost:8080/wp/wp-content/plugins/hide-admin-menu/img/icon.png',
),
);
}}}
WordPress will remove only the 1st duplicated separator (130) and still keeps the 2nd one (140).
Another problem with current code is if separator menu item has classes like `'wp-menu-separator woocommerce'` (WooCommerce does this), it won't be recognized as a separator, because the function to check separator uses `strcmp`.
" rilwis
Has Patch / Needs Testing 22200 Require users to set a site title Administration normal normal Awaiting Review defect (bug) new has-patch 2012-10-15T18:52:14Z 2013-01-26T20:43:26Z "Currently, users can get away with setting a blank site title under Settings -> General.
As a consequence, meta and title tags in both the front-end site and wp-admin may be empty, or contain extraneous spaces and separators.
A common reason why users leave site titles blank is due to the misperception that the site title is necessarily displayed in the header on the front-end site.
I suggest that we display an alert when users attempt to set a blank site title, and possibly suggest that if they don't want it to appear in their header, they can edit their CSS or hide header text under Appearance -> Header." chrisrudzki
Has Patch / Needs Testing 17636 Search subtitles are handled inconsistently across admin Administration 3.2 normal normal Awaiting Review defect (bug) new has-patch 2011-06-01T12:15:48Z 2011-07-09T11:44:29Z "Try the following strings in the Comments admin screen and any other:
`\'""\fs""\\\""`
`imareallylongstringlookatmegoandgoandgoandgoandgoandgoandgoandgoandgoandgoandgoandgoandgoandgo`
The Comments screen uses `strip_slashes()` and `wp_html_excerpt()` to limit search strings to 50 characters, while other screens do not." kawauso
Has Patch / Needs Testing 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
Has Patch / Needs Testing 23886 Use set_url_scheme for draft Preview links in post table Administration trunk normal normal Awaiting Review defect (bug) new has-patch 2013-03-29T01:20:52Z 2013-03-29T01:23:03Z "When using FORCE_SSL_ADMIN and this filter to prevent non-SSL preview of posts:
{{{
add_filter('secure_logged_in_cookie', '__return_true');
}}}
Preview links for unpublished drafts on `wp-admin/edit.php` do not use SSL and will 404.
This can be fixed by using `set_url_scheme` for the unpublished preview link. A similar unpublished preview link in `meta-boxes.php` was changed to use `set_url_scheme` in [21664]. For context, see #20759, #13328." reidburke
Has Patch / Needs Testing 17959 WP-Tab css WraithKenny Administration 3.2 normal minor Awaiting Review defect (bug) reopened has-patch 2011-07-01T17:03:44Z 2013-01-21T23:20:35Z "The classes wp-tab-panel, wp-tab-bar, and wp-tab-active should adjust to side tabs in the post column (to match the behavior of categories for example)
Also, there are several unneeded duplicate css classes that can be cleaned up." WraithKenny
Has Patch / Needs Testing 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
Has Patch / Needs Testing 16864 WP_Terms_List_Table doesn't call sanitize_term() on display Administration 2.9 normal minor Awaiting Review defect (bug) new has-patch 2011-03-16T12:54:07Z 2011-06-22T17:05:26Z "Steps to reproduce:
Add this filter:
{{{
add_filter( 'category_slug', function() {
return 'filtered';
} );
}}}
and go to {{{edit-tags.php?taxonomy=category}}}" scribu
Has Patch / Needs Testing 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
Has Patch / Needs Testing 24328 blogname and blogdescription strip content between angle brackets Administration normal normal Awaiting Review defect (bug) new has-patch 2013-05-13T09:12:06Z 2013-05-15T13:18:35Z "I was trying to set my Site Title to ''''''. On saving the settings, the field returned empty. The same problem occurred with the Tagline.
After looking into `wp-admin/options.php`, I noticed that there was no provision made for escaping the fields." aniketpant
Has Patch / Needs Testing 13416 media for install.css missing (patch) Administration 3.0 normal normal Awaiting Review defect (bug) new has-patch 2010-05-16T18:48:17Z 2013-01-22T07:40:13Z In /core-root/wp-includes/general_template.php the function wp_admin_css is missing the @media definition. See patch. F J Kaiser
Has Patch / Needs Testing 17557 AtomPub service sends duplicate status headers, breaking FastCGI AtomPub 3.2 normal normal Awaiting Review defect (bug) new has-patch 2011-05-25T20:33:33Z 2011-08-08T01:00:38Z "The AtomPub service (wp-app.php) sends duplicate Status headers when authorization is not provided, which breaks on FastCGI setups. This is seen when you attempt to connect to the service using e.g. [https://github.com/calavera/Ape Ape], resulting in the following error message in the Apache logs:
{{{
[Wed May 25 16:09:21 2011] [error] [client 10.5.62.176] FastCGI: comm with server ""/tmp/webadmin_test"" aborted: error parsing headers: duplicate header 'Status'
}}}
This results in a 500 Internal Server Error from Apache:
{{{
HTTP/1.1 500 Internal Server Error
Date: Wed, 25 May 2011 20:09:21 GMT
Server: Apache
X-Powered-By: PHP/5.2.6RC4-pl0-gentoo
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Wed, 25 May 2011 20:09:21 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
WWW-Authenticate: Basic realm=""WordPress Atom Protocol""
Content-Length: 735
Connection: close
Content-Type: text/html; charset=iso-8859-1
401 Credentials required.
Credentials required.
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator,
webmaster@ufl.edu and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.
More information about this error may be available
in the server error log.
Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.
Apache Server at test.news.ufl.edu Port 80
}}}
Patch attached to refactor Status headers in wp-app.php to use the {{{status_header}}} function like most of the code uses. There's also a function that handles which I have refactored to use {{{wp_redirect}}}. Affects all versions back to 2.9.2, including trunk.
Examples of this issue (and corresponding fixes) include:
* #2628
* http://trac.symfony-project.org/ticket/3191" dwc
Has Patch / Needs Testing 18060 image upload handling between atompub and xmlrpc different AtomPub 3.2 normal normal Awaiting Review defect (bug) new has-patch 2011-07-10T12:33:27Z 2012-06-17T12:58:30Z Uploading images via XMLRPC generates different image sizes in addition to the original image. Uploading the same image through AtomPub will only create a single original file in the uploads/year/month/ directory, the thumbnail and different formats normally generated on upload are missing. It is probably because wp_handle_upload is missing from the wp-app.php create_attachment definiition - it only uploads the bits and creates an attachment, but neither handles metadata updates nor image thumbnail generation. rfc1437
Has Patch / Needs Testing 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
Has Patch / Needs Testing 24244 Clean post cache when post was moved to trash Cache normal normal Awaiting Review defect (bug) new has-patch 2013-05-02T00:36:22Z 2013-05-02T00:36:22Z Clean post cache when post was moved to trash m_uysl
Has Patch / Needs Testing 22683 Don't load advanced-cache.php when running via CLI Cache normal normal Awaiting Review defect (bug) new has-patch 2012-12-02T18:46:48Z 2012-12-03T20:05:29Z "When you're loading WP via a command-line program, it doesn't make much sense for a plugin like WP Super Cache to take over. It's not like you have thousands of CLI users hammering the install.
Example issue in wp-cli: https://github.com/wp-cli/wp-cli/issues/164" scribu
Has Patch / Needs Testing 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
Has Patch / Needs Testing 21650 replace serialize() with print_r() in stats() function in wp-includes/cache.php Cache 3.4.1 normal minor Awaiting Review defect (bug) new has-patch 2012-08-21T13:42:29Z 2012-09-10T15:17:49Z "In PHP 5.3 it is no longer possible to serialize data that contains a SimpleXMLElement object. It produces a fatal error. See https://bugs.php.net/bug.php?id=49800
The stats() function attempts to determine the allocated space for objects in the cache by using strlen() of the serialized object.
This can fail for the reason above.
Given that the figure returned is simply an estimation of the space
I propose that the code is changed to use
print_r( $cache, true ) instead of serialize( $cache )
ie. to become
`echo ""
';`
This TRAC was raised after a longish chain of events starting with #18488 and the final response (today) which led to another chance discovery of a similar problem in the debug-bar plugin.
http://wordpress.org/support/topic/plugin-debug-bar-fatal-error-uncaught-exception-serialization-of-simplexmlelement-is-not-allowed
" bobbingwide
Has Patch / Needs Testing 21879 wp_count_posts() cache is not destroyed after post inserts and deletions Cache 3.4.2 normal normal Awaiting Review defect (bug) new has-patch 2012-09-13T01:23:38Z 2012-09-13T02:11:19Z "`wp_count_posts()` caches its results, but that cache is not destroyed when posts are inserted, deleted, or transitioned. This can lead to incorrect counts.
The attached patch fixes that (although it doesn't destroy the cache set when `$perm='readable'` in `wp_count_posts()`, which would be more complex as we wouldn't know the name of the key(s), though it could be done with `preg_match`).
" mark8barnes
Has Patch / Needs Testing 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
Has Patch / Needs Testing 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
Has Patch / Needs Testing 17718 Don't redirect if user is already on port 80 Canonical 3.1.3 normal normal Awaiting Review defect (bug) new has-patch 2011-06-07T11:31:40Z 2012-10-16T16:36:46Z "If user is already using port 80 but {{{$original['port']}}} is set to 80 anyway, do not send a needless redirect.
wp-includes/canonical.php line 324
change from
{{{ if ( !empty( $original['port'] ) )}}}
change to
{{{ if ( !empty( $original['port'] ) && $original['port'] != 80 )}}}
Fixes, for example, Nagios's check_http getting sent a redirect rather than the page content.
-davidc" davidcx
Has Patch / Needs Testing 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
Has Patch / Needs Testing 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
Has Patch / Needs Testing 20319 $page value not being defaulted to 1 in the absence of cpage query var in get_next_comments_link()/get_previous_comments_link() Comments 3.0 normal normal Awaiting Review defect (bug) new has-patch 2012-03-29T09:23:19Z 2012-05-24T07:27:29Z "get_next_comments_link() generates incorrect comment pagination links on the first page when used alongside a user-made call to wp_list_comments().
Currently, get_next_comments_link() doesn't take into account instances where there is no 'cpage' query var (which is the case when a user-made call to wp_list_comments() is performed). The intval() of the empty $page variable returns 0, and at this point should then be defaulted to 1 in order for the correct link to page 2 to be generated. Instead, it's left as 0, and the resulting link is self-referencing to page 1.
In wp-includes/link-template.php:
{{{
function get_next_comments_link( $label = '', $max_page = 0 ) {
global $wp_query;
if ( !is_singular() || !get_option('page_comments') )
return;
$page = get_query_var('cpage'); //RETURNS EMPTY IN ABSENCE OF A cpage VALUE ON PAGE 1 OF A USER-MADE CALL TO wp_list_comments()
$nextpage = intval($page) + 1; //intval() RETURNS 0, 0+1=1, RESULTING IN THE ""Newer Comments"" LINK SELF-REFERENCING PAGE 1, INSTEAD OF POINTING TO PAGE 2
...
}}}
Coincidentally, in paginate_comments_links() (wp-includes/link-template.php) this situation is handled correctly, and $page does get correctly defaulted to 1. The same conditional used in paginate_comments_links() can be applied to both get_next_comments_link() and get_previous_comments_link(). The code to properly account for it is:
{{{
function get_next_comments_link( $label = '', $max_page = 0 ) {
global $wp_query;
if ( !is_singular() || !get_option('page_comments') )
return;
$page = get_query_var('cpage');
if ( !$page ) //******** ADDED
$page = 1; //******** ADDED
$nextpage = intval($page) + 1; //intval() RETURNS 0, 0+1=1, RESULTING IN THE ""Newer Comments"" LINK NOT POINTING TO PAGE 2
...
}}}
The same addition should be made to get_previous_comments_link() as well, although it's obviously unnoticeable on the first page." MomDad
Has Patch / Needs Testing 16430 Comment 'Reply' button still present when comment max depth has been reached, just without text. Comments 3.0.4 normal normal Awaiting Review defect (bug) new has-patch 2011-01-31T22:12:56Z 2013-01-15T23:41:09Z "With comment max depth set, in my case, to 5 on the admin panel, the div for the reply link would still appear even though the text that says 'Reply' would not. Basically, it was an empty div with class=""reply"". The fix is quite easy, which I implemented in test on one of my WP sites.
Around line 1372 of wp-includes/comment-template.php, there is the following is code:
{{{