something in the end]]>44772013-02-03 12:10:102013-02-03 12:10:10closedclosed
[...]
}}}
And now, when I try to import that (exactly in unmodified form) it strips
{{{
style=""padding: 3em 0 0 0; margin: 0 0 3em 0; background-color: rgba(195, 195, 195, 0.15);""
}}}
part in some places but not all (I guess this is important)!
And it doesn't strip it when I go to [Pages > Example] and switch to ""Visual"" editor or update the page. It is imported this way (already wrong).
I'm absolutely sure that this happens, tested several times and I can't find an error or explanation.
Export file: UNIX, UTF-8 w/o BOM.
Importer Version: 0.6
Plugin URL: http://wordpress.org/extend/plugins/wordpress-importer/
I've seen a couple of issues related to ""update_post_meta"" that is stripping quotation marks etc. Maybe this is related.
Installation: WPMU (unfiltered_html is probably disabled because it's non-super-admin blog)." Looimaster
Today 22096 IN meta_query with empty array as meta_value results in invalid database query wonderboymusic* Query 3.1.3 normal normal 3.6 defect (bug) accepted has-patch 2012-10-04T13:56:54Z 2013-04-29T09:06:36Z "If you do an {{{IN}}} meta_query and pass in an empty array to the {{{value}}}, the {{{INNER JOIN}}} clause for the postmeta table isn't added, which results in an invalid query:
{{{
new WP_Query( array(
'meta_query' => array( array( 'key' => 'abc', 'value' => array(), 'compare' => 'IN' ) )
) );
}}}
This results in an error like so:
{{{
WordPress database error: [Unknown column 'wp_postmeta.meta_key' in 'where clause']
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'private') AND (wp_postmeta.meta_key = 'abc' ) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 0, 5
}}}" batmoo
Today 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
Today 23219 Duplicate enclosure metadata created because of disagreement on meta field formatting XML-RPC 2.8 normal normal 3.6 defect (bug) new needs-unit-tests 2013-01-16T21:48:42Z 2013-04-29T03:10:09Z "Years ago I reported an issue in Ticket #7773 that the enclosures would be duplicated each time the post was edited and resubmitted through the XMLRPC API. That bug was fixed in [10383] but a nuance was overlooked that causes this kind of duplication to occur with every edit if the ORIGINAL custom field meta for the enclosure was generated by the automatic content-scraper in WordPress.
If a post with links to ""enclosure"" type files is submitted either through the web interface or through the XMLRPC API, it will automatically generate the insertion of enclosure metadata as a custom field with fragile-structured content of the format:
{{{add_post_meta( $post_ID, 'enclosure', ""$url\n$len\n$mime\n"" );}}}
But the XMLRPC implementation, where the attempt is made to avoid generating duplicates, uses a slightly different fragile template, with no trailing newline:
{{{$encstring = $enclosure['url'] . ""\n"" . $enclosure['length'] . ""\n"" . $enclosure['type'];}}}
To make a long story short: the attempt to detect an existing enclosure on the post always fails because the existing enclosure string has a newline, and the XMLRPC-based one does not.
I propose that this be fixed by at enacting 1 and probably also 2:
1. Make sure duplicate detection method insensitive to trailing whitespace. This will fix the bug in a way that doesn't require retroactively ""fixing"" the existing stored metadata with trailing newline.
2. Change the format of the ""scraped"" enclosure generation to match the format used by XMLRPC. Either with or without the newline would probably be fine, but it seems cleaner to stick with the one that doesn't require a trailing newline, just three blobs of text separated by newlines. It also seems lucky that the last blob is a MIME type and thus would never have a meaningful newline at the trailing end.
I'm attaching a patch that achieves both of these goals. I report this to the XML-RPC component because that's the impact is, even if some of the issue is in the default scraping code from functions.php.
I'm a little less certain about how to tackle a unit test for these cases, but if somebody wants to point me in the right direction I can take a hack at that too.
" redsweater
Today 24216 wp_unique_term_slug uses variable that doesn't exist Taxonomy 2.5 normal normal 3.6 defect (bug) new 2013-04-28T22:44:13Z 2013-04-28T23:30:19Z "http://core.trac.wordpress.org/browser/trunk/wp-includes/taxonomy.php#L2380
`$args['term_id']` doesn't exist. It should be `$term->term_id`.
This means that even though the DB schema allows for different taxonomies to have the same slug the code will never allow it." lonnylot
Today 23088 Multisite, Subdomains and www Multisite 3.0 normal normal Awaiting Review defect (bug) new 2012-12-30T20:05:33Z 2013-04-28T16:21:25Z "I installed a WordPress Multisite network (in subdomain mode) on Zend's PHPCloud.com.
Zend does not provide an IP address, recommending a CNAME instead. CNAME records are not allowed on the root of a domain, so they recommend using the www subdomain, with a redirect from the root domain to www.
This site can NEVER be accessed on the naked domain; it will always be accessed via the www subdomain.
So, I setup wildcard DNS for *.mydomain.com, then created a network on www.mydomain.com. Then, I went to a non-existant subdomain on my network, nonexistant.mydomain.com, and WordPress redirected to www.mydomain.com/wp-signup.php?new=nonexistantwwwmydomaincom.
The correct behavior is to redirect to www.mydomain.com/wp-signup.php?new=nonexistant
The fix for this is in wp-includes/ms-settings.php, replace line 89 with:
{{{
$site_domain = preg_replace( '|^www\.|', '', $current_site->domain );
$destination = 'http://' . $current_site->domain . $current_site->path . 'wp-signup.php?new=' . str_replace( '.' . $site_domain, '', $domain );
}}}
Also, on the registration page at the bottom it says:
""The site you were looking for, http://nonexistant.www.mydomain.com/ does not exist, but you can create it now!""
The fix is in ms-blogs.php, line 53:
{{{
$url = preg_replace( '|^([^\.]+://)(?:www\.)?|', '$1' . $blogname . '.', $url );
}}}" jkhoffman
Today 21837 Site search for a domain by text fails in subdomain installs of multisite with www in primary domain Multisite 3.4.2 normal normal Awaiting Review defect (bug) new 2012-09-08T00:30:50Z 2013-04-28T16:21:22Z "To reproduce:
1) Create a subdomain network install where the main site's domain contains www
2) On the Network Admin->Sites search for an existing site based on the domain name, such as some* to find somedomain.domain.com.
3) Search returns ""No sites found."" even when the site exists and was searched for using a valid technique.
I've tested the problem on Apache and Nginx servers, with Twenty Eleven as the theme on the main site, and network activated plugins. Existing sites can never be found by domain name.
Subdomain installs in a network are allowed where the main site is www.domain.com. DOMAIN_CURRENT_SITE in wp-config.php points to www.domain.com. But blogs.domain stores the domain of a multi-site site named somedomain as somedomain.domain.com (without the www).
As a result, any site search for a domain based on text (the name of the domain) fails because of how the query is built on lines 70-73 of wp-admin\inludes\class-wp-ms-sites-list-table.php. A search for some* produces a query that searches for some%.www.domain.com instead of some%.domain.com; the result is that nothing is ever found.
Searches based strictly on site ID work fine.
Possible fixes: 1) leave as is but warn that subdomain network installs where the primary domain includes www will have a broken site search (not ideal) and encourage no www on primary site of a subdomain network install or 2) check if the primary domain contains www and strip it out prior to building the query (ideal)." frisco
Today 24212 Add missing inline docs for esc_attr_x() and esc_html_x() Inline Docs 2.8 normal normal Awaiting Review defect (bug) new 2013-04-28T16:02:54Z 2013-04-28T16:02:54Z "See [source:trunk/wp-includes/l10n.php:22346#L208].
#9650" ocean90
Today 24211 WPMU works with example.com but not sub.example.com Multisite trunk normal normal Awaiting Review defect (bug) new 2013-04-28T12:00:24Z 2013-04-28T12:19:00Z "Installtion 1:
I created a WPMU installation on http://example.com/ domain with http://example.com/site/ link structure and it works just fine. Users can register new blogs and they can access them using respective links they chose.
Installtion 2:
I created another WPMU installation on http://test.example.com/ domain with http://test.example.com/site/ link structure and it works just fine. Users can register new blogs and they can access them using respective links they chose.
Installation 3:
I created yet another WPMU installation on http://test2.example.com/ and it works (I can access main theme, Dashboard etc.) but as soon as user registers new site under http://test2.example.com/site/ - it returns 404 not found in admin panel and when I try to view this website. I copied .htaccess etc. correctly, paths are correct. In case of this installation I also redirected this subdomain to another server.
DNS:
test2.example.com - record A - 000.000.000.000 (IP of the second server)
I bet that it generated invalid .htaccess content but I may be wrong." Looimaster
Today 24201 Error in RegEx for proxy excluded URL in function send_through_proxy HTTP 3.1 normal normal Awaiting Review defect (bug) new 2013-04-26T13:13:37Z 2013-04-26T13:51:27Z "Dear WordPress Team,
I've detected a bug in the function send_through_proxy in the class WP_HTTP_Proxy. The coded regex for wildcarded domains only works for subdomains containing characters (a-zA-Z0-9) and . (dot) but not for subdomains containing characters (a-zA-Z0-9) and - (dash).
File: wp-includes/class-http.php around line 1411
Example:
{{{
define(WP_PROXY_BYPASS_HOSTS, '*.example.com');
}}}
foo.bar.example.com will not use proxy.
foo-bar.example.com will use proxy.
POSSIBLE SOLUTION:
Change the line 1411 from
{{{
$wildcard_regex[] = str_replace('\*', '[\w.]+?', preg_quote($host, '/'));
}}}
to
{{{
$wildcard_regex[] = str_replace('\*', '[\w.-]+?', preg_quote($host, '/'));
}}}
Yours,
Erich Lerch" erich1978
Today 6297 Unbalanced tags across more and nextpage tags Formatting 2.5 normal normal Awaiting Review defect (bug) reopened has-patch 2008-03-19T09:55:50Z 2013-04-26T11:39:08Z "It's easy to produce broken front page markup by including a --nextpage-- tag that breaks an enclosing bold or italic tag. There's some code in get_the_content that fixes this for --more-- tags, but it doesn't handle --nextpage--, and it'd be more efficient to do it at post save time.
The enclosed patch fixes this by splitting the content into slices at those boundaries and separately balancing each slice. Balancing happens in the content_save_pre action. No filtering is needed on the output side for posts saved after this filter.
It was a bit of a struggle figuring out where to fit this but I think the solution is fairly clean. It includes a new split_nextpage() function that can be used instead of ad-hoc regexps for splitting a post into pages.
" tellyworth
Today 24189 {$taxonomy}_relationships cache can easily become stale when a term is updated. Taxonomy trunk high major 3.6 defect (bug) new 2013-04-25T11:18:16Z 2013-04-26T02:35:03Z "The {{{{$taxonomy}_relationships}}} cache stores the information about the terms associated with an object for a particular taxonomy.
If you update the term then we don't invalidate the cache and therefore a call to something like: {{{get_the_terms()}}} will return invalid data.
An example set of steps to reproduce (needs some form of persistent caching like memcache):
1) Create a new tag and assign it to a post
2) Use get_the_terms()
3) Edit the tag to change the description
4) Use get_the_terms() and find the old description is returned.
Very easy to reproduce in a unit-test.
Re-constituting the relationships cache for every object that is related to the term is probably going to be very expensive.
Maybe we should just switch to only caching IDs and then populating the term data from a different cache?
" westi
Today 23831 Insert Into Post for Audio / Video doesn't always work Post Formats trunk normal normal 3.6 defect (bug) new commit 2013-03-20T20:05:43Z 2013-04-25T23:38:37Z "As Otto pointed out, ""Link To"" can be set to ""None"" which was sending a broken shortcode to the editor. The HTML sent to the editor should be based on what is selected using ""Link To"" in the Media modal." wonderboymusic
Today 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
Today 24156 If you submit file through wp curl it doesnt send boundary params for file mutlipart HTTP 3.5.1 normal major Awaiting Review defect (bug) new has-patch 2013-04-22T15:38:12Z 2013-04-25T14:05:33Z "If you submit file through wp curl it doesnt send boundary params for file multipart, because in class-http.php at line 174 `$r['body']` array is converted to string:
{{{
$r['body'] = http_build_query( $r['body'], null, '&' );
}}}
And curl wants array to send file boundary to rest api , in that case it fails.
ex.
{{{
$headers['Content-type'] = 'multipart/form-data';
$args['file'] = '@/pathtofile';
$request = new WP_Http;
$result = $request->request($url,$args);
}}}
Let me know if you have questions " samnani
Today 23688 esc_textarea, wp_richedit_pre and wp_htmledit_pre eat post content under PHP 5.4 westi Formatting trunk high blocker 3.6 defect (bug) reopened 2013-03-04T17:27:22Z 2013-04-25T09:51:24Z "Because of a change in default behaviour in {{{htmlspecialchars}}} in PHP5.4 it is possible for these three functions to eat perfectly valid post content and make it impossible to edit existing posts.
Scenario:
* blog_charset is ISO-8859-1
* Post contains some 8bit characters
You try and edit the post and instead of the post content you are presented with a blank editor :(
On the front end the posts display fine.
The underlying cause it this change in {{{htmlspecialchars}}}
""5.4.0 The default value for the encoding parameter was changed to UTF-8.""
Because the string is not a valid UTF-8 sequence an empty string is returned :(
Related to #20368" westi
Today 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
Today 24183 MediaElement.js i18n issues I18N trunk high normal 3.6 defect (bug) new has-patch 2013-04-24T22:54:17Z 2013-04-25T03:18:34Z "As reported by dimadin in #23282:
> MedaElement.js has very poor i18n support that isn't compatible with one we use in !WordPress since it relies on browser's language to determine locale, and strings are hardcoded in it (see [https://github.com/johndyer/mediaelement/pull/627 pull] that introduced this).
>
> I looked how to improve this and have it backward compatible and attached patch contains my proposal. Note that this shouldn't go straight to !WordPress since it contains changes to MedaElement.js too. I wanted to hear thoughts from others before submitting pull to MedaElement.js. When they add compatible support, we can patch !WordPress." SergeyBiryukov
Today 24175 Image post format insertion results in a broken image for unlinked images Post Formats trunk high normal 3.6 defect (bug) new has-patch 2013-04-24T16:06:52Z 2013-04-25T02:18:49Z "Steps to reproduce:
1. Go to Appearance > Themes and activate the Twenty Twelve theme
2. Go to Posts > Add New
3. Click the ""Image"" post format at the top
4. Click ""Select / Upload Image""
5. Upload a new image and set Link To = None
6. Click ""Select Image""
7. Note that the ""_format_image"" textarea contains a link even though I selected Link To = None (looks like a separate bug), remove the anchor tag so just the img tag is left (that's the expected behavior for what I selected). See the highlighted part of the first screenshot below for an example.
8. Click ""Publish""
9. View the post
* Expected: to see an image post format appear normally with the image showing
* Actual: no image appears and I see the following mangled HTML:
{{{
}}}
In theme js, put in:
{{{
$('.test').tabs();
}}}
Then go to your homepage in the frontend to confirm the tabs are working and normal. Now go to the backend theme customize and you will see the issue I am trying to describe." splashingpixels.com
Today 21974 esc_url() doesn't allow protocol-relative URLs with colons Formatting normal normal 3.6 defect (bug) new has-patch 2012-09-23T00:58:25Z 2013-04-10T18:15:42Z "This doesn't work:
{{{
wp_enqueue_style( 'twentytwelve-fonts', ""//fonts.googleapis.com/css?family=Open+Sans:400italic,700italic,400,700"", array(), null );
}}}
The colon is the culprit. `wp_kses_bad_protocol()` reduces the URL to:
{{{
400italic,700italic,400,700
}}}
So `esc_url()` returns an empty string: [[BR]]
http://core.trac.wordpress.org/browser/tags/3.4.2/wp-includes/formatting.php#L2572" SergeyBiryukov
Today 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
Today 23779 Can't insert large image if it's smaller than media setting but larger than theme setting Media 3.0 normal normal 3.6 defect (bug) new has-patch 2013-03-15T00:47:08Z 2013-04-10T14:06:27Z "If you upload an image that is larger than $content_width but not larger than the ""large"" setting in settings->media, the option to insert a ""large"" image into the post isn't available even though the image is large enough.
It looks like it must use $content_width as the actual width of the large image that's inserted, and the large_size_w setting to decide whether to show that option or not." aaroncampbell
Today 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
Today 24030 Add an action for when nonce verification fails General 3.4.1 normal normal Awaiting Review defect (bug) new 2013-04-10T10:21:37Z 2013-04-10T10:21:37Z "Currently when a plugin (or core) calls `check_admin_referer()` there is no way for auditing (or debugging) plugins to hook in and record an event that the nonce check failed.
Previously it was possible to use the `explain_nonce_$nonce` filter to do this, but that was removed in [21133].
If a plugin wants to record an event for a failing nonce, it'll need to call wp_verify_nonce() manually itself, and die afterwards, or call `check_admin_referer()` after verifying the nonce itself for logging purposes.
I'd suggest either resurrecting the previous filter as an action (for back compat) or adding a new nonce failure hook." dd32
Today 10840 Plugin upgrade sometimes shows a scrollbar Plugins 2.8.4 low normal 3.6 defect (bug) new has-patch 2009-09-24T10:34:05Z 2013-04-10T07:58:54Z "Please see attached screenshot, made in Safari 4.0.3 on OS X.
The iframe only contains the ""Plugin reactivated successfully"" line.
Increasing the window's height or width does not make it disappear, or even evolve." xibe
Today 24017 Network admin sites list page displaying bad links for Dashboard and Visits Multisite normal normal Awaiting Review defect (bug) new reporter-feedback 2013-04-09T22:44:04Z 2013-04-10T06:14:46Z "After upgrading to 3.5.1 (from 3.5), we noticed that the links to Dashboard and Visits in the/wp-admin/network/sites.php weren't working properly.
For subsites, the Dashboard link pointed back to the root site, and the same for the Visits link.
I traced the code to the following file: /wp-admin/includes/class-wp-ms-sites-list-table.php.
Line 251 currently is:
{{{
$actions['backend'] = """" . __( 'Dashboard' ) . '';
}}}
Adding the $blogname variable to the get_admin_url function as the second parameter fixed the issue:
{{{
$actions['backend'] = """" . __( 'Dashboard' ) . '';
}}}
Similarly for the Visits link.
Line 272 currently is:
{{{
$actions['visit'] = """" . __( 'Visit' ) . '';
}}}
Changing it to the following fixes it:
{{{
$actions['visit'] = """" . __( 'Visit' ) . '';
}}}
" morriswanchuk
Today 23560 Keyboard Accessibility of Add Media Panel Accessibility 3.5.1 normal normal 3.6 defect (bug) new has-patch 2013-02-20T14:26:56Z 2013-04-09T23:28:25Z "Trying to keep this trac specific I'm talking here about keyboard-only interaction with the new Add Media panel once you have opened it by actioning the Add Media link whilst editing a page or a post.
Accessibility Issues:
* The most serious problem with accessibility in the Add Media functionality is that it is not possible to select any of the pre-uploaded media without using a mouse. This will effectively preclude any keyboard only or screen reader users from using this functionality.
* When the Add Media panel first opens it is unclear where keyboard focus sits. This could be disconcerting for some users.
* Reverse tabbing from the panel transfers focus back into the main page whilst leaving the panel open. Recommend that focus is kept cycling within the panel until the user either explicitly closes the Add Media panel or inserts some images.
* It is possible to tab through the text links on the panel(s), but the Upload Files link does not show focus as obviously as other links as there is no outline.
* When tabbing forwards from the Upload Files link there is a tab stop that is not at all visible. Believe this to be Media Library but it's not clear.
* The Insert into Page link can receive focus even when inactive.
Separate trac tickets will be raised to cover the full screen reader and speech recognition software experience." grahamarmfield
Today 23995 Weird Error After Post Published Successfully General trunk normal normal Awaiting Review defect (bug) new 2013-04-08T20:46:26Z 2013-04-09T23:20:59Z "I didn't get the exact message, but I was stuck on the New Post screen after clicking Publish with something to the effect of: The server connection has been lost. This message will go away once you get reconnected.
I ended up clicking on Visit Site and I could see that the post was already published.
My server has been acting up a bit today, so I figured this is a good time to test out the new post saving logic. I'm not sure if this was the intended experience though?
Tested on 3.6-beta1. Only happened once so far." miqrogroove
Today 20299 "Preview changes on a published post makes all post meta ""live""" Revisions 3.3.1 normal major 3.6 defect (bug) new has-patch 2012-03-25T02:02:16Z 2013-04-09T22:06:08Z "Here's the use case. Client wants to preview an update to a published post (as the Preview Changes button correctly implies they can). This post has some important post meta that impacts that preview.
Here's the problem - because post meta is not saved to a revision (it looks for the ""real"" post), when the preview button is pressed, save_post runs, and saves the meta data to the real, published post, even though the user only intends to preview the change.
Without realizing it, the user has updated the published version. That can be prevented by not saving post meta to revisions (when using custom save_post hooks), but then there's no non-hacky way to actually preview the full changes.
I believe this bug has been present for a while, we just rarely use the Preview function on published posts, and when we do, probably never tested it with critical post meta." jakemgold
Today 18249 Rosetta needs a facelift ryanimel* I18N normal normal WordPress.org defect (bug) accepted has-patch 2011-07-25T20:47:35Z 2013-04-09T19:21:07Z This is a Trac ticket for http://make.wordpress.org/ui/2011/07/25/small-design-project-rosetta/. nacin
Today 24005 WordPress.org search field looks broken in Opera WordPress.org site normal minor WordPress.org defect (bug) new 2013-04-09T13:07:58Z 2013-04-09T13:13:08Z This is how it looks in Opera 12.15, Win8, x64 (see attach) seezer
Today 23668 Check for empty slug input in register_taxonomy Taxonomy 3.5.1 normal normal 3.6 defect (bug) new dev-feedback 2013-03-02T18:20:56Z 2013-04-09T10:12:02Z "If you give an empty string for the `slug` part of the `rewrite` array in a `register_taxonomy` call, like:
{{{
'rewrite' => array(
'slug' => ''
)
}}}
...you get some wacky permalink issues, even when you flush properly. In my case, I was seeing top-level pages (only) 404 while everything else worked. Removing this admittedly poor part of the code fixed it, but this should be checked for. The `register_post_type` function ensures this isn't empty, and this function should as well." cliffseal
Today 23989 Wonky download button on plugin support forums WordPress.org site normal normal WordPress.org defect (bug) new 2013-04-08T15:27:57Z 2013-04-08T18:21:06Z "On the 'Support' tab for any plugin in the wordpress.org plugin repo, the Download button is a bit wonky.
[[Image(http://i.imgur.com/5gctAEO.png)]]" johnbillion
Today 6369 Blogger importer inefficient handling of data Import normal normal WordPress.org defect (bug) new 2008-03-24T03:58:47Z 2013-04-08T17:04:48Z If the import dataset is large, the Blogger importer can store huge amounts of data in the blogger_importer option. It then updates this data over and over throughout the import. If MySQL logging (binary or query) is enabled, this can result in a large amount of data being written to disk, potentially filling up the partition rather quickly. On WordPress.com, I have seen an import write 100MB of binary logs every 2 min. Andy's suggestion is that we split up the data from the import rather than store it in one option. This would allow us to manipulate it more granularly and prevent the huge updates from happening. barry
Today 14244 Upload file types should be checked BEFORE uploading. Media normal normal Future Release defect (bug) new 2010-07-09T01:06:36Z 2013-04-08T15:12:57Z "Wanna get frustrated? Try uploading a 50 meg video and realizing you forgot to set your Upload file types to allow m4v.
Is there any way this can be checked BEFORE the file gets uploaded? As it stands today, you upload THEN it checks and deletes. Arg :)" ipstenu
Today 23971 Post Set Featured Image No Light Box Media trunk normal normal Awaiting Review defect (bug) new reporter-feedback 2013-04-07T03:51:04Z 2013-04-08T13:21:09Z "For posts when clicking on set featured image the media browser is opened in the current window instead of a light box.
Setting featured image on pages works fine" azchipka
Today 23469 Comment meta query is parsed before the pre_get_comments filter Comments 3.5 normal normal 3.6 defect (bug) new has-patch 2013-02-13T12:21:26Z 2013-04-08T06:54:07Z "Currently it is impossible to use the `pre_get_comments` filter to adjust the meta_query, because `parse_query_vars( $this->query_vars )` is run before the filter is applied http://core.trac.wordpress.org/browser/tags/3.5.1/wp-includes/comment.php#L243:
{{{
// Parse meta query
$this->meta_query = new WP_Meta_Query();
$this->meta_query->parse_query_vars( $this->query_vars );
do_action_ref_array( 'pre_get_comments', array( &$this ) );
}}}
Comment meta query should be parsed '''after''' the `pre_get_comments` filter has been applied." kasparsd
Today 21795 Menu collapse option not saved correctly Administration 3.5 normal normal 3.6 defect (bug) reopened reporter-feedback 2012-09-04T23:39:17Z 2013-04-08T01:00:54Z "The menu collapse option is not saving correctly when at a resolution > 900px. When collapsing and them re-expanding the menu, the menu auto collapses on each new page load. It's caused by the script deleting the folded setting but not actually setting the unfolded setting as far as I can tell.
The attached patch works for me." griffinjt
Today 23923 wp_get_post_revisions returns incorrect order Revisions normal minor Awaiting Review defect (bug) new 2013-04-03T12:07:19Z 2013-04-08T00:27:47Z "When a post has multiple revisions and each revision has the exact same timestamp, `wp_get_post_revisions` returns revisions in reversed order, causing `wp_save_post_revision` to [http://core.trac.wordpress.org/browser/trunk/wp-includes/revision.php#L116 make a bad choice] for `$last_revision` (which is actually the first revision) and produce an extra revision, even if it has not been changed.
In a normal environment this doesn't happen, unless you run `wp_update_post` several times in a row in under one second, so this is an edge case. This edge case causes our [http://core.trac.wordpress.org/browser/tests/trunk/tests/post/revisions.php#L55 revisions.php tests] to fail randomly, depending on whether the updates happened with the same timestamp or not.
To reproduce, try running the revisions unit tests several times in a row." kovshenin
Today 23975 force_balance_tags in get_the_content breaks non-HTML formats Formatting 2.8 normal normal Awaiting Review defect (bug) new 2013-04-07T10:05:44Z 2013-04-07T10:58:50Z "The change in r11398 (to fix #9765) breaks Markdown formatted articles that use angle bracket links: `` turning it into ``.
If we call force_balance_tags after adding the more link, we need to establish filter hooks for formatters. This should have happened before r11398 already, but because balancing tags wasn't forced, this issue has not affected sites that disable balancing tags in their preferences.
Typically formatters attach to the `the_content` filter (among others). This should probably change into a `get_the_content` filter (similar to `get_the_excerpt`) that is called early on the full content of the post.
I haven't yet decided where the best place for the new filter would, or if it would be better to undo the force_balance_tags call.
Thoughts? I could work on the change, but would rather prefer some input first." ruckus
Today 9207 redirect_to wp-admin Should Force SSL If FORCE_SSL_ADMIN is enabled hakre* Security 2.9 normal normal Future Release defect (bug) accepted reporter-feedback 2009-02-21T22:36:07Z 2013-04-06T20:36:05Z "Around Lines 406 to 426 on wp-login.php:
{{{
$secure_cookie = '';
// If the user wants ssl but the session is not ssl, force a secure cookie.
if ( !empty($_POST['log']) && !force_ssl_admin() ) {
$user_name = sanitize_user($_POST['log']);
if ( $user = get_userdatabylogin($user_name) ) {
if ( get_user_option('use_ssl', $user->ID) ) {
$secure_cookie = true;
force_ssl_admin(true);
}
}
}
if ( isset( $_REQUEST['redirect_to'] ) ) {
$redirect_to = $_REQUEST['redirect_to'];
// Redirect to https if user wants ssl
if ( $secure_cookie && false !== strpos($redirect_to, 'wp-admin') )
$redirect_to = preg_replace('|^http://|', 'https://', $redirect_to);
} else {
$redirect_to = admin_url();
}
}}}
As we can see on the present code, if a redirection is set while login and this redirection goes to the plain version of the dashboard then client will go to the non-SSL version of the dashboard which therefore will move the client to the secure version (generating and extra request).[[BR]]
I know this is kinda a tongue twister sentence so i think is better to put a request example of the problem...
Client: POST http://foo.bar/wp-login.php?redirect_to=http%3A%2F%2Ffoo.bar%2Fwp-admin%2Findex.php [[BR]]
Server: HTTP 302 ... Location: http://foo.bar/wp-admin/index.php [[BR]]
Client: GET http://foo.bar/wp-admin/index.php [[BR]]
Server: HTTP 302 ... Location: https://foo.bar/wp-admin/index.php
I know that wordpress is actually working as suppose to work (cause we told to move to non-SSL version of the dashboard) but and a extra http request is issued.[[BR]]
IMHO if we (admins) have enabled FORCE_SSL_ADMIN, then all redirections to wp-admin should go SSL/HTTPs even if we fill redirect_to with the plain version of the dashboard.[[BR]]
There is part of the code that detect this and replace it but it has issues or well it isn't prepared to do this.[[BR]]
At the moment we can filter login_redirect to fix this but (again) IMHO this should move to the core..." g30rg3x
Today 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
Today 23958 http://wordpress.org/showcase/ is broken for retina WordPress.org site normal normal WordPress.org defect (bug) new 2013-04-06T12:19:26Z 2013-04-06T12:19:26Z "First time I do see an image but when whole page is loaded the image is ""File not found"". Only Quartz is showing up in the slider." markoheijnen
Today 23956 jQuery UI Datepicker adds empty but visible div at bottom of page Appearance 3.5.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2013-04-06T01:52:12Z 2013-04-06T08:19:52Z "This bug seems to be related to the [http://bugs.jqueryui.com/ticket/4111 this] jQuery UI bug, which has been fixed, but the following WordPress stylesheet seems to be making the bug re-appear:
wp-includes/css/jquery-ui-dialog.min.css
As far as I can tell, removing the following rule seems to fix it:
{{{
.ui-helper-clearfix:after {
content:""."";
}
}}}
" julianm
Today 23335 Bizarre sorting while browsing WordPress themes and plugins WordPress.org site normal normal WordPress.org defect (bug) new 2013-01-31T05:01:52Z 2013-04-05T15:21:54Z "Currently, there's some fuzzy logic while sorting plugins and themes. Sorting by popularity seems to be reset I'm guessing on every major WP version update, which I guess is fair, in which case the problem is just missing the proper description of the sort option.
However, while sorting by rating, nothing really makes sense of the bizarre sort order there. ( [http://wordpress.org/extend/themes/browse/top-rated Top Rated Themes] )
Even while searching for a keyword, and sorting by ""rating,"" the [http://wordpress.org/extend/plugins/search.php?q=slideshow&sort=top-rated bizarre sorting ensues].
WordPress.org should be a shining example of what WordPress can do, and nail it. " ericlewis
Today 23873 Gallery shortcode orderby does not support multiple column sorting Gallery 3.5.1 normal normal Awaiting Review defect (bug) new 2013-03-27T21:13:53Z 2013-04-05T12:42:03Z "In wp-includes/media.php, function gallery_shortcode, lines 689-694 are:
{{{
// We're trusting author input, so let's at least make sure it looks like a valid orderby statement
if ( isset( $attr['orderby'] ) ) {
$attr['orderby'] = sanitize_sql_orderby( $attr['orderby'] );
if ( !$attr['orderby'] )
unset( $attr['orderby'] );
}
}}}
The sanitize_sql_orderby function requires commas between multiple column names. If you enter, for example orderby=""menu_order ID"", the lack of a comma causes the parameter to be deleted from the query.
Just after this test, on line 698, a multi-column sort without the comma delimiter is used as the default value.
If you enter commas to get past the sanitize_sql_orderby test, logic in wp-includes/query.php, function get_posts will not accept the commas (lines 2358 - 2361) and all but the last of the columns are ignored.
This issue should be considered along with those raised in #17065 and #16584. Thank you." dglingren
Today 23939 Wrong capability check in wp_ajax_replyto_comment Comments 3.1 normal normal Awaiting Review defect (bug) new has-patch 2013-04-04T18:39:21Z 2013-04-05T01:06:32Z "The wp_ajax_replyto_comment function in the wp-admin/includes/ajax-actions.php checks the ""edit-post"" capability instead of the ""edit-comment"" capability.
Attached a tested patch. " fgauthier
Today 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
Today 20973 date_i18n() produces invalid output for shorthand formats Date/Time 3.4 normal normal Awaiting Review defect (bug) new 2012-06-15T13:39:50Z 2013-04-04T16:36:54Z "date_i18n() function relies on parsing passed format to make adjustments. However shorthand formats are not handled and produce invalid output.
Example:
{{{
var_dump( date_i18n( 'Y-m-d\TH:i:sP', time() ) ); // 2012-06-15T13:34:03+03:00 << ok
var_dump( date_i18n( DATE_W3C, time() ) ); // 2012-06-15T13:34:03+03:00 << ok
var_dump( date_i18n( 'c', time() ) ); // 2012-06-15T13:34:03+00:00 << broken time zone!
}}}
Hook-level fix:
{{{
add_filter( 'date_i18n', 'fix_c_time_format', 10, 3 );
function fix_c_time_format( $date, $format, $timestamp ) {
if ( 'c' == $format )
$date = date_i18n( DATE_W3C, $timestamp );
return $date;
}
}}}
See [http://wordpress.stackexchange.com/q/54700/847 Why time functions show invalid time zone when using 'c' time format?]
Possibly related (can't say for sure from description) #13538" Rarst
Today 23683 Fatal error in WP_User_Query SergeyBiryukov Users 3.4 normal normal 3.5.2 defect (bug) reopened commit 2013-03-04T05:54:40Z 2013-04-04T15:58:07Z "To reproduce in single site:
1. Go to Users screen.
2. Enter a URL into the search input and click ""Search Users"".
3. You'll see a fatal error:
{{{
Fatal error: Call to undefined function wp_is_large_network() in wp-includes/user.php on line 477
}}}
`wp_is_large_network()` is only defined in Multisite admin: [[BR]]
http://core.trac.wordpress.org/browser/tags/3.5.1/wp-admin/includes/ms.php#L696
This can be reproduced when using `WP_User_Query` on front-end as well (in single site and Multisite). Introduced in [19886]." SergeyBiryukov
Today 23826 Funky conditional tags for posts archive Query trunk normal normal Awaiting Review defect (bug) new 2013-03-20T13:51:22Z 2013-04-04T04:14:12Z "If a WordPress install is set to ""Front page displays ... Your latest post"", then some funky conditional tags are set. Of interest here are:
{{{ [""is_home""]=> bool(true) }}}
Sure, makes sense.
{{{ [""is_post_type_archive""]=> bool(false) }}}
Erm, what? Isn't this the post type archive for the posts post type?
{{{ [""is_archive""]=> bool(false) }}}
Isn't this also an archive?
This means is_post_type_archive( 'post' ); doesn't work anywhere.
I also attempted creating a ""posts page"" for blog posts, and got the same results." ericlewis
Today 23836 add_submenu_page() duplicate menus Administration normal major Awaiting Review defect (bug) new 2013-03-21T16:43:24Z 2013-04-04T03:22:08Z "Creating two sub-menus with the same ""menu slug"" using add_submenu_page() should create only the last sub-menu.
But it creates two sub-menus with the same ""menu slug"".
Based on documentation ""menu slug"" should be unique for each sub-menu." king_of_the_ring
Today 23847 "Media Manager default ""link to"" setting overriding custom setting" Media 2.7 normal minor Future Release defect (bug) new 2013-03-22T17:58:40Z 2013-04-04T03:18:58Z "http://core.trac.wordpress.org/browser/trunk/wp-includes/js/media-views.js#L444
The line I'm looking at is this:
{{{
link: defaultProps.link || getUserSetting( 'urlbutton', 'file' )
}}}
{{{getUserSetting( 'urlbutton', 'file' )}}} returns the correct value that I set in the theme on 'init' with {{{set_user_setting( 'urlbutton', 'none' )}}} but that value is not saved on this line because defaultProps.link has already been set to 'file'.
I can't figure out why it tests for a default setting before a user setting, and not the other way around" joshkadis
Today 23863 Post Formats: allow filtering content_width per format in wp-admin Post Formats normal normal 3.6 defect (bug) new dev-feedback 2013-03-25T20:55:33Z 2013-04-04T01:10:04Z "On front-end a theme can filter {{{$content_width}}} like so:
{{{
function twentythirteen_content_width() {
if ( has_post_format( 'image' ) || has_post_format( 'video' ) ) {
global $content_width;
$content_width = 724;
}
}
add_action( 'init', 'twentythirteen_content_width' );
}}}
But ... functions called in wp-admin that use the global {{{$content_width}}} variable won't be changed.
For example, using trunk and Twenty Thirteen theme:
1. Create a new post, set to Image post format
2. Click Add Media to insert an image
3. Upload an image at least 800 px wide
4. You'll see in ""Attachment Display Settings"" that width for the ""large"" size to insert to the post is 604 pixels and not 724.
Also, even if detecting a Post Format this way worked correctly on edit, it wouldn't work on first post creation because of how the UI uses JS to switch between the formats." lancewillett
Today 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
Today 23909 Widgets Settings Loaded When No-Needed Widgets 3.5.1 normal normal Awaiting Review defect (bug) new 2013-03-30T16:02:05Z 2013-04-03T19:21:32Z "Hi, This ticket about the performance in the back-end interface .
WordPress run query to get the active widgets settings in every page even in the dashboard ! , This makes the site admin slow especially when the site have many widgets !
You can use '''Debug Bar''' & '''Debug Bar Extender''' plugins to check the queries ." alex-ye
Today 23931 wp_insert_comment should require comment_post_ID Comments normal normal Awaiting Review defect (bug) new 2013-04-03T18:41:58Z 2013-04-03T19:06:08Z "At this moment there is no check for example comment_post_ID. Not sure if there are more checks needed. Reason I asked are a few notices on the unit tests caused by WP_UnitTest_Factory_For_Comment. Those comments don't add a post ID what should change.
Currently, if a null comment_post_ID is passed, the comment isn't connected to a post. This can create confusion. Also Unit tests should run with WP_Debug on." markoheijnen
Today 23825 Demand to disable plugins in order to create a network doesn't make sense Network Admin 3.0 normal normal Awaiting Review defect (bug) new 2013-03-20T11:02:37Z 2013-04-03T14:46:47Z "1. have some plugins active on a stand alone WP
2. add define('WP_ALLOW_MULTISITE', true); to wp-config.php
3. go to ""tools"" >> ""Network Setup"" and you get a ""Warning: Please deactivate your plugins before enabling the Network feature.""
4. you have to disable the plugins in order to continue the process
And I have to ask why? This doesn't make sense for the following reasons
1. Why plugins and not themes? any ""bad"" code that can be in a plugin can also be in a theme.
2. If the plugins provide essential functionality, then my site will stop behaving as expected. This basically will put the site in maintenance mode, so why not to do it automatically in the code to be able to get faster in and out of this mode?
3. Did it ever happened that a plugin ruined a network install?
At the least this should be treated as a warning and not as an error, i.e. the text get displayed but the user can continue with the process if he decides to ignore the warning." mark-k
Today 23041 Images Don't Become Attached When Inserting a Gallery Gallery 3.5 normal normal 3.6 defect (bug) new has-patch 2012-12-21T20:15:21Z 2013-04-02T13:32:45Z "Steps to Reproduce:
1. Go to the ""Upload New Media"" page (wp-admin/media-new.php)
1. Upload an image.
1. Create a new post.
1. Create an image gallery that includes the newly-uploaded image.
1. Insert the gallery into the post.
1. Publish the post.
Expected result: Any ""(Unattached)"" image(s) should get attached.
Actual result: Images remain ""(Unattached)""." miqrogroove
Today 23178 "Screen reader shortcut links generated by _render() from WP_Admin_Bar class should use rel=""nofolow""" Toolbar normal normal 3.5.2 defect (bug) new has-patch 2013-01-11T13:07:29Z 2013-04-02T12:45:12Z "Screen reader related links generated by _render() from WP_Admin_Bar class assume toolbar is being shown only to logged in users. When toolbar is being shown to visitors using
{{{
function my_set_current_user() {
if(!is_user_logged_in()){
add_filter('show_admin_bar', '__return_true');
}
}
add_action('set_current_user', 'my_set_current_user');
}}}
search engines report 403 error code on every page of the website when trying to follow wp_logout_url() from one of these links (Logout link). Including rel=""nofollow"" into _render() should avoid this.
" Marko-M
Today 14686 Widget Instance Form Update Bug Widgets 3.0.1 normal normal Future Release defect (bug) new has-patch 2010-08-24T21:13:23Z 2013-04-02T10:57:57Z "Hi.
When dragging and dropping a widget into a sidebar the widget form doesn't get properly updated, unless you manually press the ""Save"" button. However the widget instance data is saved (you can see the widget in the frontend even if you don't press 'save').
This problem is noticeable when you're developing a widget and want to display some widget options in the form based on the widget's location or position. You can't do this because '''$widget->id''' or '''$widget->number''' appear to be initialized within the form() function only after you press Save...
I can provide the code of a test widget if necessary
" digitalnature
Today 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
Today 23915 discover_pingback_server_uri cases an error when discovery URI sets multiple Content-type headers Pings/Trackbacks 3.5.1 normal normal Awaiting Review defect (bug) new 2013-04-01T14:25:25Z 2013-04-02T01:58:44Z "Line 1673 in wp-includes/comment.php uses preg_match() on the output of wp_remote_retrieve_header(). When multiple headers are set of the same name, wp_remote_retrieve_header() returns an array.
Thus occasionally the following error occurs:
PHP Warning: preg_match() expects parameter 2 to be string, array given in xxxxxxx/wp-includes/comment.php on line 1673
I have no idea how to make pingbacks happen so to reproduce, add this line to functions.php: discover_pingback_server_uri('http://localhost:8080/');
And in a terminal window run this (you may need to install the netcat-openbsd package in Debuntu): while true; do echo -en 'HTTP/1.1 200 OK\r\nContent-type: text/html\r\nContent-type: text/plain\r\n\r\n' | nc -lp 8080; done
Then visit your WP installation and you shall get the aforementioned error message." tomdxw
Today 23449 Refactor customizer accordion to work anywhere in admin markjaquith Appearance normal normal 3.6 defect (bug) reopened has-patch 2013-02-11T14:23:41Z 2013-04-02T01:39:54Z "We'll plan to use the default styles/structure from the customizer accordion for menu item selection options on nav-menus.php. Currently the code is very customizer specific.
- The class names should be made more generic.
- The CSS should be extracted and placed in wp-admin.css
- The JS, should be moved so that you don't have to include the customizer JS elsewhere in the admin to re-use the accordion code." lessbloat
Today 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
Today 23470 Convert slash to dash and make body class for page templates look better Template 3.4 normal normal Awaiting Review defect (bug) new has-patch 2013-02-13T12:24:09Z 2013-04-01T03:16:13Z "If you keep you page templates in a page-templates folder in your theme. Let's we have a template named front-page.php - the template slug written in the postmeta will be '''page-templates/front-page.php'''
When generating the classes for the body, get_body_class() will convert the dot to a dash but the slash will be stripped by sanitize_html_class().
So finally we will have a class:
'''page-template-page-templatesfront-page-php'''
Isn't it prettier to convert the slash to dash and to have it like:
'''page-template-page-templates-front-page-php'''" Caspie
Today 17626 image_get_intermediate_size() may return wrong thumbnail size nacin Media normal normal Future Release defect (bug) reopened has-patch 2011-05-31T14:33:27Z 2013-03-31T16:26:12Z "See [http://wordpress.stackexchange.com/questions/17511/featured-image-with-the-same-height-thumbs-returns-wrong-thumb this WPSE question] for a more detailed explanation of the problem.
Essentially, if `get_the_post_thumbnail()` is passed an array for the `$size` argument, and if two images have one dimension exactly the same, the image with the ''smaller'' opposing dimension will be returned, even if the dimensions for the other image are declared explicitly.
The issue appears to be due to the way that `image_get_intermediate_size()` determines if an image exists that is cropped to dimensions similar to the specified `$size` array. As soon as it finds one, it uses it.
I've attached a patch that first attempts to find an image cropped ''exactly'' on both dimensions, before looking for images cropped exactly only on one dimension. There will still be edge cases where the wrong image might be returned, but I'm not sure of the most efficient way to handle such cases.
(Note: props to Rarst for finding the underlying issue.)" chipbennett
Today 13078 Make wp_register_style and wp_enqueue_style consistent General 3.0 normal minor Future Release defect (bug) new has-patch 2010-04-22T01:08:39Z 2013-03-31T05:06:56Z "When fixing #13056, I noticed that wp_register_style and wp_enqueue_style had a few odd differences.
1. Enqueue truncates the $handle variable after the first '?' while register (and all other wp_style functions) accept any string.
2. Register set the default for $media to 'all', while enqueue set it to false. (fixed in the #13056 patch).
Moreover, since the two functions are practically the same, I've grouped them together in a private _wp_register_style function with an additional $enqueue boolean. Both enqueue and register call _wp_register_style.
I've omitted the truncate behavior mentioned above. If there's any reason for it in one, and not the other, or in both, feel free to correct me.
We could also just remove the truncate behavior from enqueue. It's a minor patch, and comes down to coding style." koopersmith
Today 18614 post_type_archive_title doesn't work when tax_query is added to wp_query Template 3.2 normal normal 3.6 defect (bug) reopened has-patch 2011-09-07T17:52:04Z 2013-03-30T21:55:25Z "post_type_archive_title( ) gets called by wp_title( ) on Custom Post Type archive pages
To get the data for the post type object, post_type_archive_title( ) calls get_queried_object( ). This is problematic. If the query has been altered in any way (such as adding a tax_query in pre_get_posts filter), get_queried_object( ) will probably return a term, not a post type object.
Hence, accessing $post_type_obj->labels will fail and their will be no title returned
{{{
//old potentially broken way
$post_type_obj = get_queried_object();
// new doesn't break way
$post_type_obj = get_post_type_object( get_post_type() );
}}}" wonderboymusic
Today 23907 Scandinavian ligatures transcribed wrong in remove_accents() I18N trunk normal minor 3.6 defect (bug) new has-patch 2013-03-30T08:52:56Z 2013-03-30T16:32:08Z "remove_accents() is transcribing old scandinavian ligatures wrong: ÆØÅøå should be transcribed as 'Ae', 'Oe', 'Aa', 'oe' and 'aa' respectively.
Transcribation rules are the same in swedish, danish and norwegian. In trunk they are transcribed as 'AE', 'O', 'A', 'o', 'a'.
See #4739, #9591 for history." dnusim
Today 23862 Clean up old WP->public_query_vars and WP->private_query_vars General normal trivial 3.6 defect (bug) new has-patch 2013-03-25T19:20:07Z 2013-03-30T15:54:18Z "There are some old non-working public_query_vars still in the WP class that should be cleaned up.
* posts - broken 10 years ago http://core.trac.wordpress.org/changeset/182/trunk/blog.header.php
* search - hasn’t done anything since wp_query was created
* calendar - don’t see support since ‘b2’
* pb - don’t see support since ‘b2’
* static - only used in determining if is_page, though it no longer works correctly, added http://core.trac.wordpress.org/changeset/1527/trunk, but functionality was partially changed the next commit
Also, since 'post_type' is now a public_query_var, it can be removed from the private_query_vars.
" prettyboymp
Today 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
Today 23905 Add_post_meta strips slashes General 2.5 normal normal Awaiting Review defect (bug) new 2013-03-30T00:20:29Z 2013-03-30T05:32:01Z "Let's assume that JS generated an object that I want to store in custom field. Everything goes smooth when I convert it back and forth from JS to PHP and from PHP to JS (using json_encode() and json_decode()) and it even works when I do update_post_meta() manually in my file but this stops working as soon as WordPress Importer tries to load it from XML file (in XML it's still valid object) using add_post_meta().
This is the code from importer from the bottom of process_posts() function:
{{{
if ( $key ) {
// export gets meta straight from the DB so could have a serialized string
if ( ! $value )
$value = maybe_unserialize( $meta['value'] );
$value = '{""0"":{""type"":""text"",""text"":""""},""1"":{""type"":""html"",""html"":""
here goes html
"",""css_class"":""""}}'; // I added this for test purposes
add_post_meta( $post_id, $key, $value );
do_action( 'import_post_meta', $post_id, $key, $value );
}}}
This is an object:
{{{
{""0"":{""type"":""text"",""text"":""""},""1"":{""type"":""html"",""html"":""
here goes html
"",""css_class"":""""}}
}}}
It strips slashes from HTML tags (before each double quote sign) from objects that are stored as strings. I bet it shouldn't happen. Why would add_post_meta strip slashes or anything if XML explicitly says:
{{{
If you’ve made it this far, check out my 2010 State of the Word speech at WordCamp San Francisco, it’s jam-packed with information on the growth of WordPress, 3.0, what we’re planning for the future, and the philosophy of WordPress.
\n\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:50:\""http://wordpress.org/news/2010/06/thelonious/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""5\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:7;a:6:{s:4:\""data\"";s:41:\""\n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:7:\""3.0 RC3\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:42:\""http://wordpress.org/news/2010/06/3-0-rc3/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:51:\""http://wordpress.org/news/2010/06/3-0-rc3/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Fri, 11 Jun 2010 20:49:38 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:1:{i:0;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1376\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:257:\""A weekend present, in haiku: Last call; final bugs Itch, scratch, contort; calmly wait For now: RC3 That’s right. What will hopefully be the final release candidate, RC3, is now available for download and testing. Plugin developers: test your plugins!\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:438:\""
A weekend present, in haiku:
\n
Last call; final bugs \nItch, scratch, contort; calmly wait \nFor now: RC3
\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:47:\""http://wordpress.org/news/2010/06/3-0-rc3/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:8;a:6:{s:4:\""data\"";s:47:\""\n \n \n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:37:\""Expanding the Theme Review Experiment\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:72:\""http://wordpress.org/news/2010/06/expanding-the-theme-review-experiment/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:81:\""http://wordpress.org/news/2010/06/expanding-the-theme-review-experiment/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Wed, 09 Jun 2010 16:06:11 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:3:{i:0;a:5:{s:4:\""data\"";s:9:\""Community\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:1;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}i:2;a:5:{s:4:\""data\"";s:6:\""Themes\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1347\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:272:\""When I was a kid my dad used to practice his typing skills (on a real typewriter no less) with the phrase: Now is the time for all good men to come to the aid of their country. For some reason that has stuck with me all these years. Today I’m going to rephrase and [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:12:\""Joseph Scott\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1962:\""
When I was a kid my dad used to practice his typing skills (on a real typewriter no less) with the phrase:
\n
Now is the time for all good men to come to the aid of their country.
\n
For some reason that has stuck with me all these years. Today I’m going to rephrase and re-purpose that line:
\n
Now is the time for great theme developers to come to the aid of their community.
\n
The theme directory has been chugging along for more than a year now. During that time we’ve tinkered with the review process and some of the management tools, but haven’t really opened it up as much as we’d like. It’s time to rip off the band-aid and take some action; to that end, we’re looking for community members to help with the process of reviewing themes for the directory.
\n
Right now this is a bit like a New Year’s resolution to exercise every day: it’s what we need to do, but we’re still figuring out exactly how it will all work. That’s part of the community involvement as well — we expect that those who pitch in will also help shape the process.
\n
What’s involved in reviewing themes for the directory? There are some obvious things, such as being familiar with PHP and WordPress theme code (and the theme development checklist), with an eye for security issues. You would also need to have the ability to set up a separate install of the latest version of WordPress for testing theme submissions.
\n
Hopefully a few talented theme developers are reading this right now and saying to themselves, “I’d love to help! How do I get started?” Just join the new theme reviewers mailing list and we’ll get you up to speed on this new opportunity to come to the aid of your community.
\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:77:\""http://wordpress.org/news/2010/06/expanding-the-theme-review-experiment/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}i:9;a:6:{s:4:\""data\"";s:41:\""\n \n \n \n \n \n \n\n \n \n \n \n \n \"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";s:5:\""child\"";a:5:{s:0:\""\"";a:7:{s:5:\""title\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""WordPress 3.0 Release Candidate\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:66:\""http://wordpress.org/news/2010/05/wordpress-3-0-release-candidate/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:75:\""http://wordpress.org/news/2010/05/wordpress-3-0-release-candidate/#comments\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:7:\""pubDate\"";a:1:{i:0;a:5:{s:4:\""data\"";s:31:\""Fri, 28 May 2010 02:35:04 +0000\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:8:\""category\"";a:1:{i:0;a:5:{s:4:\""data\"";s:11:\""Development\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:4:\""guid\"";a:1:{i:0;a:5:{s:4:\""data\"";s:40:\""http://wordpress.org/development/?p=1358\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:1:{s:11:\""isPermaLink\"";s:5:\""false\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:11:\""description\"";a:1:{i:0;a:5:{s:4:\""data\"";s:345:\""As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What’s an RC? An RC comes after beta and before the final launch. It means we think we’ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using [...]\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:32:\""http://purl.org/dc/elements/1.1/\"";a:1:{s:7:\""creator\"";a:1:{i:0;a:5:{s:4:\""data\"";s:10:\""Jane Wells\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:40:\""http://purl.org/rss/1.0/modules/content/\"";a:1:{s:7:\""encoded\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1993:\""
As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What’s an RC? An RC comes after beta and before the final launch. It means we think we’ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using WordPress with a wide variety of configurations and hosting setups, it’s entirely possible that we’ve missed something. So! For the brave of heart, please download the RC and test it out (but not on your live site unless you’re extra adventurous). Some things to know:
\n
\n
Custom menus are finished! Yay!
\n
Multi-site is all set.
\n
The look of the WordPress admin has been lightened up a little bit, so you can focus more on your content.
\n
There are a ton of changes, so plugin authors, please test your plugins now, so that if there is a compatibility issue, we can figure it out before the final release.
\n
Plugin and theme *users* are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.
\n\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:36:\""http://wellformedweb.org/CommentAPI/\"";a:1:{s:10:\""commentRss\"";a:1:{i:0;a:5:{s:4:\""data\"";s:71:\""http://wordpress.org/news/2010/05/wordpress-3-0-release-candidate/feed/\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:38:\""http://purl.org/rss/1.0/modules/slash/\"";a:1:{s:8:\""comments\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""0\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}}}s:27:\""http://www.w3.org/2005/Atom\"";a:1:{s:4:\""link\"";a:1:{i:0;a:5:{s:4:\""data\"";s:0:\""\"";s:7:\""attribs\"";a:1:{s:0:\""\"";a:3:{s:4:\""href\"";s:31:\""http://wordpress.org/news/feed/\"";s:3:\""rel\"";s:4:\""self\"";s:4:\""type\"";s:19:\""application/rss+xml\"";}}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}s:44:\""http://purl.org/rss/1.0/modules/syndication/\"";a:2:{s:12:\""updatePeriod\"";a:1:{i:0;a:5:{s:4:\""data\"";s:6:\""hourly\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}s:15:\""updateFrequency\"";a:1:{i:0;a:5:{s:4:\""data\"";s:1:\""1\"";s:7:\""attribs\"";a:0:{}s:8:\""xml_base\"";s:0:\""\"";s:17:\""xml_base_explicit\"";b:0;s:8:\""xml_lang\"";s:0:\""\"";}}}}}}}}}}}}s:4:\""type\"";i:128;s:7:\""headers\"";a:8:{s:6:\""server\"";s:5:\""nginx\"";s:4:\""date\"";s:29:\""Thu, 18 Nov 2010 07:10:47 GMT\"";s:12:\""content-type\"";s:23:\""text/xml; charset=UTF-8\"";s:10:\""connection\"";s:5:\""close\"";s:4:\""vary\"";s:15:\""Accept-Encoding\"";s:10:\""x-pingback\"";s:36:\""http://wordpress.org/news/xmlrpc.php\"";s:13:\""last-modified\"";s:29:\""Thu, 30 Sep 2010 03:23:31 GMT\"";s:4:\""x-nc\"";s:11:\""HIT luv 138\"";}s:5:\""build\"";s:14:\""20090627192103\"";}', 'no') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)
WordPress for iPhone/iPad v2.6 Released September 30th, 2010
Attention Apple-gadget-owning WordPress users! Have you been using the WordPress iOS app for iPhone and iPad? Or maybe you tried it a while back and thought it wasn’t for you? Either way, the new release — v2.6 — will knock your socks off. Why? A bunch of reasons: Video. Record, upload, attach, and play videos […]
WordPress Trademark Changes Hands September 9th, 2010
The WordPress community took a big step forward today when Matt announced that Automattic has donated the WordPress trademark to the non-profit WordPress Foundation. Moving forward, the Foundation will be responsible for safeguarding the trademarked name and logo from misuse toward the end of protecting WordPress and preventing confusion among people trying […]
}}}
" Viper007Bond
Today 21219 get_post_type_archive_link in multisite context: struct issue Post Types normal normal Awaiting Review defect (bug) new 2012-07-11T17:48:27Z 2012-09-03T12:11:03Z "Context : multisite and a site aaa ( http://localhost/wpmu_svn_34/aaa/ ) trying to display the '''post_type_archive_link''' of cpt 'book' of the blog bbb
{{{
switch_to_blog( $b );
$link = get_post_type_archive_link( 'book' ) ;
/*/ http://localhost/wpmu_svn_34/bbb/book/ and not http://localhost/wpmu_svn_34/bbb/livre/ */
restore_current_blog();
}}}
when name, slug and query_var of the post_type are the same: no problem because $struct to find the '/book/' is kept from the caller site BUT
if in the called site, the CPT have the same type name ('book') but with different slug and query_var, the home_url is correctly changed but the $struct is not good... 'book' instead 'livre' as declared in cpt in site bob.
The issue came from global $wp_rewrite; which is not this of the target after the switch_to_blog !
Instead of a non elegant filter ''post_type_archive_link'', is there a way to ""find"" the $wp_rewrite of $b ?
Best regards !
" michelwppi
Today 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
Today 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
Today 20263 Backticks in dbDelta cause warning and actually causes a query to alter all columns and indexes to run even if none have changed Upgrade/Install 1.5 normal minor Awaiting Review defect (bug) new has-patch 2012-03-20T16:11:18Z 2012-09-01T20:13:24Z "Backticks in a CREATE TABLE in a dbDelta call are causing the below warning, and running a query to alter all columns and indexes with backticks even if they haven't changed:
Notice: Undefined offset: 1 in /home/backuptechnology/public_html/wp-admin/includes/upgrade.php on line 1544
Seems this started a long long time ago after this was fixed:
http://core.trac.wordpress.org/ticket/8014
Seems there is a match on line 1587 of WordPress 3.3.1 wp-admin/includes/upgrade.php:
{{{
// For every field in the table
foreach ($tablefields as $tablefield) {
// If the table field exists in the field array...
if (array_key_exists(strtolower($tablefield->Field), $cfields)) {
// Get the field type from the query
preg_match(""|"".$tablefield->Field."" ([^ ]*( unsigned)?)|i"", $cfields[strtolower($tablefield->Field)], $matches);
}}}
The preg_match bit is what fails to match because it is looking for ""fieldname"" instead of ""`fieldname`"".
So this is where the warning occurs, and why it assumes the type of the field is wrong.
This means the previous patch 3 years ago probably meant when you have backticks in your CREATE TABLE, when you run dbDelta it actually runs an ALTER TABLE for every single column in the table, and then an ALTER TABLE ADD INDEX / PRIMARY for every single KEY and PRIMARY (there's more than just the above code that needs adjusting), causing duplicate key errors, but ignored. Guess it kinda works though...
Also seems during the DESCRIBE it doesn't use backticks so if someone has a table with a reserved name (stupid I know) it would break dbDelta completely, but that's me digressing I just think getting rid of the warnings for CREATE TABLES with backticks will be good.
But explains why my plugin takes a few seconds to activate hahaha. :-)
I'll provide a patch at some point this week or next unless someone has already done so." Driskell
Today 21762 Storing a multidimensional array using register_setting double-serializes subarrays identified with a string sekatsim Database 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-31T22:43:16Z 2012-09-01T16:36:41Z "Storing a multidimensional array, such as `$options['my-option'][$id] = ""value""`, into the database using register_setting results in the ""my-option"" string getting double serialized. The option_value is stored as:
`s:9:""'my-option'"";a:1:{s:9:""option-id"";s:5:""value"";}`
The my-option array is encased in both single and double quotes, so that `isset($options['option-id']` evaluates false, but `isset($options[""'option-id'""]` evaluates true." sekatsim
Today 21753 Feed excerpts are missing important filter formatting Feeds 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-31T14:20:56Z 2012-08-31T14:20:56Z "Excerpts included in feeds are missing important formatting because the relevant filters are not applied (e.g. wpautop).
In file wp-includes/feed.php, function the_excerpt_rss() does not apply the same filters as the_excerpt() whilst results in lost formatting instructions. By comparison, function the_content_feed() ensures that the same filters declared for the_content() are applied.
A suggested patch is attached. Note that for symmetry between the_excerpt_rss() and the_content_feed() this patch also removes the (unnecessary?) filter ent2ncr() from the_excerpt_rss() and retains the (controversial?) escaping for CDATA blocks (see #3670).
A few related issues are worth mentioning. Firstly, shortcodes are still not applied to excerpts (see #7093). Also, the (obsolete?) RDF feed does not make use of a CDATA block unlike those for RSS, RSS2 and Atom (see #20888). Finally, a similar problem occurs with comment text in feeds (see #16466)." mdgl
Today 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
Today 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
Today 16833 Signup mechanism shortens usernames without warning Users 3.0 normal normal Future Release defect (bug) new has-patch 2011-03-11T15:09:23Z 2012-08-29T23:40:31Z "When a user signs up for an account on a wordpress blog, if their chosen username is longer than the limit, wordpress chops of the end of the username, without warning the user, and without offering the user the opportunity to choose again.
Steps to reproduce: Go to a wordpress blog, sign up with a long username, and read the confirmation email. An example: forum.xbmc.org, which has a limit of 15 characters." hughcharlesparker
Today 16762 wpdb::$base_prefix is not documented Database normal normal Awaiting Review defect (bug) new has-patch 2011-03-05T16:17:01Z 2012-08-29T19:59:25Z "Probably wpdb::$base_prefix has been merged into from MU and not further specified then.
It ''genereally'' can be replaced with {{{wpdb::get_blog_prefix(0)}}} when the MULTISITE constant is defined. That is are after wp-settings.php has been included (wp-config.php, wp-load.php), even on SHORTINIT.
It ''might'' be that this function call does not cover all cases needed because if MULTISITE is not defined when called, it will not return the {{{wpdb::$base_prefix}}}.
More insight into MU is needed, feedback appreceated. Some places look like that they are not aware of the wpdb::get_blog_prefix() function. Probably legacy MU code.
Related: #16756" hakre
Today 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
Today 10752 Uploading new media to existing posts/pages backdates file location Media 2.8.4 normal minor Future Release defect (bug) new 2009-09-08T20:35:20Z 2012-08-28T20:57:35Z "Using WP 2.8.4, when uploading new media files to a page or post that has already been published, the new file is added in the /UPLOAD_DIR/year/month/ directory that corresponds to the original page/post publication date, rather than the file upload date.
Also, the correct file-upload-date-based directory is created (if it does not already exist), but the file is still placed in the older incorrect directory.
Example: Assume the following...
On /wp-admin/options-misc.php:
* ""Store uploads in this folder"" (referred to above as UPLOAD_DIR) is set to ""wp-content/uploads"" or any other location, such as ""files""
* ""Organize my uploads into month- and year-based folders"" is checked
On an existing Page:
* Page has a published date of 3/1/2008
* File a_test_file.jpg is uploaded on 9/1/2009
* UPLOAD_DIR is set to ""wp-content/uploads"", has 777 permissions, and contains no subdirectories or files
WordPress 2.6.x and below would have created the following:
* /wp-content/uploads/2009/09/a_test_file.jpg
However, WP 2.8.4 is creating:
* /wp-content/uploads/2008/03/a_test_file.jpg
* /wp-content/uploads/2009/09
This issue was previously mentioned on the wordpress.org forums as being a known issue with WP 2.7.1: http://wordpress.org/support/topic/254786" dpie
Today 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
Today 21669 "Make ""Home"" option persistent in Pages box on Menus screen" Menus 3.4.1 normal minor Awaiting Review defect (bug) new 2012-08-23T16:57:08Z 2012-08-27T15:09:43Z "If you have some pages, or even a page, then on nav-menus.php in the Pages box, View All, it will display Home as an option. However, if you do not have any pages at all (mostly Blog on front page scenarios), then it just says ""No items."" in the Pages box.
It should always be populated with at least the Home option. Oversight on our part that we didn't uncover this behavior before. " jane
Today 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@…
Today 15317 My Sites limited to 23 sites on Admin Bar Toolbar 3.1 low normal Future Release defect (bug) new has-patch 2010-11-04T13:35:21Z 2012-08-26T08:16:23Z "I have a test site with 25 sites. I can only access 23 from the My Sites tab on the admin bar.
(This is a minor bug, but I hadn't seen it mentioned.)
Ron
I'm using latest trunk." ronbme
Today 21652 wp_update_nav_menu_items returns false instead of WP_Error for non-existent menu items Menus 3.4.1 normal normal Awaiting Review defect (bug) new has-patch 2012-08-21T16:57:45Z 2012-08-25T14:49:33Z "'''Use case:'''
Calling wp_update_nav_menu_items with a non-existent menu_item_id as the first parameter
'''Expected return value:''' WP_Error object (as per the method's documentation)
'''Actual return value:''' Boolean false
'''Fix:''' wp-includes/nav-menu.php#L279 - This line should check for a false value first, and if `$menu == false`, set it equal to a `new WP_Error` object - then check `is_wp_error($menu)`" mltsy
Today 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
Today 18730 media_sideload_image() doesn't handle dynamic image url's well Warnings/Notices 2.9 normal normal Awaiting Review defect (bug) new has-patch 2011-09-21T10:49:11Z 2012-08-23T20:17:02Z "Example URL: http://www.tumblr.com/photo/1280/10464566223/1/tumblr_lrum2xzkpC1r3z8e3
As a result, the preg_match() for the file extension fails and issues a notice (no file extension in that url, although the redirection location does have).
The handling of a download failure also seems hairy, upon failure, it still attempts further importing before loading - I haven't looked into that too far." dd32
Today 21659 wp_mail() problem with Reply-To header General 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-22T14:43:43Z 2012-08-22T14:43:43Z "I am using in email headers also Reply-To:
{{{
$headers .= ""Reply-To: \""$name\"" <$email>\r\n"";
}}}
But there is a problem when name contains special non-English characters.
Example (from email headers):
Name: Žlutý kůň
{{{
Reply-To: =?UTF-8?Q? ""=C5=BDlut=C3=BD_k=C5=AF=C5=88"" _ ,
?=@example.com
}}}
I think that it is somehow related to wp_mail() function, because I also tried to use SMTP plugin and it worked well:
{{{
Reply-To: =?UTF-8?Q?""=C5=BDlut=C3=BD_k=C5=AF=C5=88""_?=
}}}
Also when I use simply mail() instead of wp_mail() then everything works well. Problem can be seen only for Reply-To header, all others work well (for example From).
I am using WP 3.4.1." pavelevap
Today 21658 Meaningless adjacent post links for pages General 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-22T12:34:26Z 2012-08-22T12:34:26Z "In WP 3.3 we removed a number of obsolete elements from the page header leaving just those with rel=""next"" and rel=""prev"" generated by function adjacent_post_rel_link_wp_head() in file wp-includes/link-template.php [see #18128].
This change brings the function of these links into sharper relief and raises several concerns. Presently, they are generated only for singular pages/posts that are not attachments.
Such links make some kind of sense for ordinary posts, because these can be considered to be part of an ordered collection where the next/previous relationship is meaningful. It may also make sense for custom post types, depending on the use to which they are being put.
For pages, however the links generated refer to the next/previous pages as they happen to be stored in the WP database and these are unlikely to have any meaningful relation to the originating page.
Others have reported performance and other problems with browsers such as Firefox that use these links to prefetch content [see #12603, #14382 and #19018].
You can see their point! If I'm viewing page ""about"" what are the chances that I will next want to view the page ""contact"" just because this happens to have the next sequential ID in the WordPress database?
At the very least, I believe that these links should not be generated for pages. Better still would be to follow Google's advice [see #18672] and use these just for paginated content (i.e. individual posts/pages [with ] or archives [including blog home]). Some potential patch code is available against #18660 which raised a similar issue. Links between adjacent posts can be left to the usual navigation elements within the page body." mdgl
Today 21645 Rewrite API logic and flush_rules Rewrite Rules 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-21T00:24:05Z 2012-08-21T08:24:19Z "
It is not clear if or how visiting the Settings -> Permalinks calls flush_rules. It is referenced occasionally as an apparent alternative to $wp_rewrite->flush_rules() in Documentation. This should be explicitly confirmed in the admin interface and/or a button based action.
Documentation for the Rewrite API functions do not point at $wp_rewrite->flush_rules() effectively. (Updated some codex links, but seems worth including a pointer inline in function definitions.)
I was confused while editing an existing theme why duplicating existing add_feed() structures in functions.php did not produce duplicated behaviour in the permalinks. ?feed=atom1 worked , but /feed/atom1/ didn't, until calling flush_rules()
Logic seems broken between these functions. Why call Rewrite API add_feed() every init, but still require a flush_rules reset to activate? They should be more explicitly linked / combined / triggered. See prior conversation in #21335
http://codex.wordpress.org/Rewrite_API" here
Today 20847 "Documentation references to ""digits"" should be ""characters""" Inline Docs normal trivial Awaiting Review defect (bug) new has-patch 2012-06-05T14:49:08Z 2012-08-20T21:14:53Z Some documentation references to digits should really be called characters, since they refer to parts of a hexadecimal number, and therefore not strictly 0-9 only. GaryJ
Today 21631 HTML encoded characters in the custom menu's URL html are decoded after first save and removed after second save Menus 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-19T15:27:20Z 2012-08-19T15:49:04Z "Special characters in the custom menu's URL get double html encoded after second save.
Having an array in the URL that is using square brackets (site.com/key[value]), the links break after the second save of that menu item because the & in the & gets double html encoded." rocketwood
Today 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
Today 18790 add_theme_support with post type doesn't add theme support but overwrites it Themes 3.2.1 normal normal Awaiting Review defect (bug) new has-patch 2011-09-27T12:17:13Z 2012-08-18T01:48:57Z "The function add_theme_support has an optional second parameter, which allows you to add support for post thumbnails for certain post types.
You would expect this function to add the theme support for that post type, but instead it overwrites the theme support for that feature, which results in the theme support being set for just the post type(s) that were passed.
Reproduce:
{{{
function add_thumbnails_support()
{
add_theme_support('post-thumbnails', array('my_post_type'));
print_r(get_theme_support('post-thumbnails'));
add_theme_support('post-thumbnails', array('another_post_type'));
print_r(get_theme_support('post-thumbnails'));
}
add_action('after_setup_theme', 'add_thumbnails_support');
}}}
" Jesper800
Today 21616 add-textdomain doesn't conform to WP coding standards I18N normal normal WordPress.org defect (bug) reopened 2012-08-17T03:07:19Z 2012-08-17T21:37:50Z I used add-textdomain.php from http://i18n.svn.wordpress.org/tools/trunk on my plugin code, but it does not include a space before the closing parenthesis of the gettext function call it alters, which violates http://codex.wordpress.org/WordPress_Coding_Standards#Space_Usage groovecoder
Today 21237 "Terminology for ""Front"" and ""Home""" General normal normal Awaiting Review defect (bug) new 2012-07-12T13:59:40Z 2012-08-17T19:25:29Z "The following related tickets all have discussions concerning the Terminology for ""Front Page"" and ""Home Page"" is some way.
#16379 - Better UI for doing ""Page on Front"" [[BR]]
(UI effected by the terminology)
#10158 - Deprecate is_home() and is_single(), in favor of is_blog() and is_post() [[BR]]
(Conditional Tags effected by the terminology)
#18705 - home_url() and is_home() with a static front page [[BR]]
(URL function effected by the terminology)
Additionally, Template files are effected by the terminology (home.php and front-page.php)
This ticket is intended to discuss the best options that address the above terminology concerns for the sake of consistency and usability. If a determination is made here, hopefully we can use the terminology to inform the above tickets." WraithKenny
Today 21613 format_to_edit runs esc_textarea if $richedit param is set to false, not true General normal minor Awaiting Review defect (bug) new has-patch 2012-08-16T19:59:20Z 2012-08-17T15:35:26Z "Currently, the docs on format_to_edit() indicate that it runs the content through esc_textarea (which in turn runs htmlspecialchars() ) if the $richedit param is set to true. The code, however, runs the filter if the param is not set (or passed as false, see line 1270).
{{{
#!php
1255 /**
1256 * Acts on text which is about to be edited.
1257 *
1258 * The $content is run through esc_textarea(), which uses htmlspecialchars(
1259 * to convert special characters to HTML entities. If $richedit is set to t
1260 * it is simply a holder for the 'format_to_edit' filter.
1261 *
1262 * @since 0.71
1263 *
1264 * @param string $content The text about to be edited.
1265 * @param bool $richedit Whether the $content should not pass through htmls
1266 * @return string The text after the filter (and possibly htmlspecialchars(
1267 */
1268 function format_to_edit( $content, $richedit = false ) {
1269 $content = apply_filters( 'format_to_edit', $content );
1270 if ( ! $richedit )
1271 $content = esc_textarea( $content );
1272 return $content;
1273 }
1274
}}}
My thought is the if statement should evaluate whether $richedit is true, rather than false, and therefore apply the esc_textarea function only when explicitly passed as a param. This would, however, result in unexpected behavior for anyone currently passing only the default $content param and getting sanitized output." vhauri
Today 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
Today 20006 get_comments (and WP_Comment_Query) does not accept multiple post_type Comments 3.3.1 normal normal Awaiting Review defect (bug) new has-patch 2012-02-10T05:46:52Z 2012-08-14T08:34:53Z "Although get_comments was recently improved to support post_types, it does not seem to properly handle MULTIPLE post_types.
Suppose you need to get the most recent comments for posts, pages, and attachments (attachments don't seem to be included by default). The following doesn't work, as it only returns comments on attachments (or whichever status is listed first):
{{{
get_comments(array('number'=>20, 'status'=>'approve', 'post_type'=>array('attachment','post','page')));
}}}
The following doesn't work either, only returning the default post/page comments (taken from the example for multiple category handling at http://codex.wordpress.org/Class_Reference/WP_Query):
{{{
get_comments(array('number'=>20, 'status'=>'approve', 'post_type__in'=>array('attachment','post','page')));
}}}
A quick look at wp-includes/comment.php, line 327 (WP v3.3.1) shows that the 2nd option will be array_filter'ed away. Immediately below, all of the WHERE clauses are hardcoded as ""="", which is why there's no way to specify more than one. As a result, it seems like the only way to get recent comments on posts,pages,and attachments (or any other subset of >1 post_type) is to do multiple calls to get_comments (i.e. one with default params and one for attachments) then merge the results together...effectively requiring twice the work." Justin_K
Today 13689 multisite noblogredirect set, 404 error result not sending proper info with IIS Multisite 3.0 normal normal Future Release defect (bug) new 2010-06-02T01:01:31Z 2012-08-14T08:32:10Z "Scenario. With NOBLOGREDIRECT specified as the main sites url, the 404 errors and the bad blog url are supposed to go what is specified as the location in the noblogredirect define.
The bug is the 404 errors are *not* pointing to what is specified in the noblogredirect, the 404 errors (that are not bad blog urls) are triggering an IIS error response and not redirecting.
When it's done triggering the IIS error it then uses the web.config to transfer to the main site.
Besides this bug.
This tells me 2 things, this tells me that the method/behavior of this is wrong and should be looked at. *if* wordpress knows the difference between a bad blogurl and a 404 error page, the 404 error *should* go to the 404 template, however in the past WPMU versions it did not do that it went straight to the mainsite as well. It *should* go to the 404 template and since it knows the difference it should be coded a such.
1) Bad subdomains should go to the specified noblogredirect define.
2) 404 error pages should go to the 404 page template for the theme.
Not to mention that the bug in question *is* that the 404 error itself is not redirecting to it's intended location to begin with.
" Frumph
Today 21550 Plugin changelog truncation can break WordPress.org site layout WordPress.org site normal normal WordPress.org defect (bug) new 2012-08-11T16:32:59Z 2012-08-11T16:35:41Z "WordPress.org appears to truncate plugin changelogs after a certain number of characters. However, if the truncation occurs in an inconvenient place -- such as the middle of an HTML tag -- it can cause browser rendering issues in other parts of the page.
For example, on the [http://wordpress.org/extend/plugins/seo-ultimate/changelog/ changelog page] for my plugin SEO Ultimate, the plugin page sidebar is currently showing up below the changelog ([http://img405.imageshack.us/img405/7557/brokenchangelogscreen.png screenshot]). This is because the changelog is being truncated in the middle of an
tag, apparently leading my browser (Chrome) to fail to recognize a closing tag:
{{{
}}}
I would suggest that the easiest and perhaps best solution would be simply to stop truncating plugin changelogs. Layout breakage possibilities aside, I would prefer it if my plugin's changelog were not cut off after a certain point." JohnLamansky
Today 13576 wordpress.org themes list, sidebar broken in IE7 ryan WordPress.org site normal normal WordPress.org defect (bug) new 2010-05-27T14:49:20Z 2012-08-10T18:25:26Z "wordpress.org themes list
the sidebar in IE7/IE8 is displayed AFTER the themes, Firefox ok." maurizio04
Today 21035 Encoding problem on my profile page? WordPress.org site normal normal WordPress.org defect (bug) new 2012-06-21T12:30:42Z 2012-08-10T18:18:31Z "Please see my profile page: http://profiles.wordpress.org/pavelevap.
I made several plugins with non-English names. And these names are broken on profile page..." pavelevap
Today 19635 Non-ASCII chars in user name changed to question marks after sending new plugin request WordPress.org site normal normal WordPress.org defect (bug) new 2011-12-21T13:52:47Z 2012-08-10T18:12:55Z "I have just sent request to add new plugin to repository, and found that some chars in my name were changed to question marks:
{{{
WordPress Plugins » Requests
user-ranks from Daniel Fru?y?ski (sirzooro) [plugin]
}}}
Should be:
{{{
WordPress Plugins » Requests
user-ranks from Daniel Frużyński (sirzooro) [plugin]
}}}" sirzooro
Today 21542 WP.org notifications don't support UTF-8 WordPress.org site normal normal WordPress.org defect (bug) new 2012-08-10T18:10:09Z 2012-08-10T18:12:51Z See the screenshot. SergeyBiryukov
Today 17168 redirect loop when accessing wp-admin/network/ Multisite 3.1.1 normal normal Awaiting Review defect (bug) reopened has-patch 2011-04-18T17:59:55Z 2012-08-10T06:31:44Z "As of 3.1.1 administrators are getting redirect loops when accessing wp-admin/network/. I run a multi-site multi-domain network and we've noticed that this bug is effecting new and old sites. One super admin reported clicking Update Network put's it in a redirect loop as well.
For new sites if this bug occurs the quick solution is to delete / recreate. I checked _options siteurl, _blogs blog_id domain, and _sitemeta siteurl. Nothing out of the ordinary in the db." chaos1
Today 14798 Twenty Ten Theme - adding an extra skip link Bundled Theme normal normal WordPress.org defect (bug) new 2010-09-07T12:07:33Z 2012-08-09T20:12:48Z "Being able to skip to content is good, but currently there is no easy way to jump to the sidebar menu.
In order to add this extra skip (jump to menu) link I've changed the div to ul. CSS changes are similar to #14795 but tweaked to allow for the new markup.
" elfin
Today 16858 Usage of HTTP_HOST in the administration Administration 3.1 normal normal Awaiting Review defect (bug) reopened reporter-feedback 2011-03-15T13:33:47Z 2012-08-09T18:46:29Z "In some files like wp-admin/includes/class-wp-list-table.php (there are more files I think), some links are created by using the HTTP_HOST variable.
It's better to use the defined wordpress URL to create those links.
In our case, we have a wordpress running behind a Squid cache. When you check for HTTP_HOST you get the *real* HOST and not the one with the Squid server.
To bypass the problem, I added in the main config.php a line like this :
{{{
$_SERVER['HTTP_HOST'] = 'www.my-visible-http-host.com';
}}}
Without this setting and in our case, some links in the admin (next, previous page, re-ordering...) where pointing to the wrong server.
" amirhabibi
Today 17047 Not following spec for REQUEST_URI sterlo Rewrite Rules 3.1 normal normal Future Release defect (bug) reviewing has-patch 2011-04-04T20:11:00Z 2012-08-09T18:44:05Z "Possibly related: #16932
Spec: http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html#sec5.1.2
Structure: http://en.wikipedia.org/wiki/URI_scheme#Examples
The spec for REQUEST_URI:
{{{
Request-URI = ""*"" | absoluteURI | abs_path | authority
}}}
The specs for REQUEST_URI in Apache are such that it allows for absolute paths to a given resource.
Given that throughout WordPress there are concatenations like:
{{{
$_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI']
}}}
These are intended to generate ""mysite.com/resources""
But in certain cases will generated ""mysite.com/mysite.com/resources""
Case Study:
{{{
GET http://subdomain.mydomain.com/ HTTP/1.1
}}}
This should be allowed.
Apache in this case sets the URI to ""http://subdomain.mydomain.com/myfile.php""
Solution: Do not assume that URI is not an absolute path.
A quick fix is something like the patch attached." sterlo
Today 18944 wrong url in sortable column headers when behind a reverse proxy General 3.2.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2011-10-14T11:50:57Z 2012-08-09T18:33:29Z "Hi, I have a wordpress site behind a reverse proxy. All works fine but for the urls used in the headers of sortable columns.
For instance, the links of ""Title"", ""Author"", etc. of the table of posts in wp-admin/edit.php --> Posts report something like ""http://backend/backend-dir/..."" while they should be ""http://frontend/frontend-dir/..."".
I don't think this is a proxy configuration problem because, AFAICS, the rest of the site is working: I can make posts, pages, media, install themes and plugins.
I tried to play with $current_url al line 649 of
wp-admin/includes/class-wp-list-table.php
but with no luck.
I suppose that pagination may have the same problem.
" gamboz
Today 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
Today 21510 Use get_background_color() in _custom_background_cb() Themes 3.4.1 normal normal Awaiting Review defect (bug) new has-patch 2012-08-07T17:57:52Z 2012-08-07T21:53:35Z "When themes add a default background color via the `custom-background` feature, it isn't shown until the user saves it in the admin. The issue is that the `_custom_background_cb()` uses `get_theme_mod( 'background_color' )` instead of `get_background_color()`, which will handle the default.
The attached patch should correct this." greenshady
Today 21428 Bad mail subject encoding on new blog notification Multisite 3.4.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-07-31T14:02:59Z 2012-08-07T11:43:45Z "Email subject is in Russian language. When trying to add new blog using page http://mysite.com/wp-admin/network/site-new.php, user gets email where subject is like - '''=??B??='''. So I was trying to find where this bug appears. And I think, I found it.
Script tries to send notification using function '''wpmu_welcome_notification''' on line http://core.trac.wordpress.org/browser/tags/3.4.1/wp-includes/ms-functions.php#L1250. But '''get_option('blog_charset')''' returns empty string, so header is bad-generated and encoded..." TheSteelRat
Today 21495 wp_insert_user allows a user to be created with empty passwords Users normal minor Awaiting Review defect (bug) new 2012-08-06T02:10:00Z 2012-08-06T02:10:00Z "While looking at the different files where user information is created, I noticed that there are some differences between wp_insert_user(programmatic creation of users) and edit_user (called from the admin).
wp_insert_user assumes that a user_pass parameter is included, which creates a user with no password.
" ancawonka
Today 21492 Theme customizer > Static front page: missing error message when front page and posts pages are similar Appearance normal normal Awaiting Review defect (bug) new 2012-08-06T00:15:25Z 2012-08-06T01:11:40Z "Steps to reproduce:
1. Activate Twenty Eleven
2. Open the Customizer
3. In ""Static Front page"", choose the same page as your front page and Posts page:
* You do not receive any warning
* http://i.wpne.ws/IYAO
* In Reading Settings, you do actually receive a warning: http://i.wpne.ws/IY2S (see http://core.trac.wordpress.org/browser/trunk/wp-admin/options-reading.php#L99 )
Would it be possible to display the same warning in the Customizer, to avoid any confusion for the users?
Related: #19627 and #16379" hd-J
Today 19198 Die fast in get_posts if in_search_post_types returns nothing ryan Query 3.2.1 normal minor Awaiting Review defect (bug) reviewing has-patch 2011-11-07T19:45:21Z 2012-08-05T22:28:35Z "From a comment of mine in #18364, which nacin suggested was worth a follow-up ticket:
Just noticed that this logic here might in fact have a flaw: if there are no post types which have exclude_from_search = false, then magically *all* post types will be checked? Am I reading this right? In that case, shouldn't we just immediately return no results?
Obviously, this wouldn't be an issue except in a very customized setup where all post types have exclude_from_search = true, but still... thoughts anyone?" mitchoyoshitaka
Today 18995 Superfluous check in WP_Users_List_Table::display_rows() Users 3.2.1 normal normal Awaiting Review defect (bug) new has-patch 2011-10-19T01:21:11Z 2012-08-05T22:25:26Z "Specifically, this one:
{{{
if ( is_multisite() && empty( $role ) )
continue;
}}}
It seems to have been a misguided attempt to fix something that should have been (and currently is) handled at the SQL level: #12711" scribu
Today 17812 "media_upload_form_handler runs twice when editing attachment from ""From Computer"" media upload tab (browser uploader)" Upload 3.1.3 normal normal Awaiting Review defect (bug) new has-patch 2011-06-15T18:48:58Z 2012-08-05T22:14:25Z "After uploading a new media item ""From Computer"" using the browser uploader, you are presented with a form to edit its fields.
Clicking ""Save all changes"" from this form causes {{{media_upload_form_handler}}} to run, then {{{media_upload_gallery}}} (presumably to redirect to the gallery tab), which then causes {{{media_upload_form_handler}}} to run again.
This can cause problems for {{{edit_attachment}}} actions that only run once and alter the posts table row for that attachment (since the subsequent {{{media_upload_form_handler}}} could overwrite whatever changes were made in the action if they don't match whats in {{{$_POST}}}).
If the only reason {{{media_upload_gallery}}} is being called from the other type upload handler is to redirect to the gallery tab.. perhaps this patch is a better approach." jeffstieler
Today 21470 Wrong menu when no menu is set Menus 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-05T13:27:13Z 2012-08-05T13:59:30Z In the case if the admin hasn't created any menu in the dashboard (and so the default menu is shown), some parameters of wp_nav_menu() don't work. I verified that 'container'=>false does not work. Other parameters may no work as well. porton
Today 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
Today 13158 Cron : some events may not be scheduled westi Cron 3.1 high major Future Release defect (bug) new 2010-04-27T23:29:46Z 2012-08-03T22:39:04Z "the problem appears when two different events are scheduled at the same time
what happens in code is :
1st event : _get_cron_array();
2nd event : _get_cron_array();
1st event : _set_cron_array( $crons );
2nd event : _set_cron_array( $crons );
1st event is lost." arena
Today 21460 The accesskeys in Quicktags don't work in all browsers Editor normal normal Awaiting Review defect (bug) new 2012-08-03T19:21:56Z 2012-08-03T22:01:43Z "IE (Alt+letter) works properly. Firefox (Alt+Shift+letter) only focuses the corresponding Quicktags button sometimes. Doesn't perform the action. If the button is hidden, performs the action (this shouldn't happen in Quicktags). Chrome doesn't seem to do anything. Opera works differently: Shift+Esc brings a list of all defined access keys on that page. The Quicktags access keys are not listed there.
" azaozz
Today 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
Today 21448 unfiltered HTML comments from a frame js fix breaks js in windowed comments Comments 3.4.1 normal normal Awaiting Review defect (bug) new has-patch 2012-08-01T21:58:53Z 2012-08-02T17:56:36Z "Noticed this today.
We have comments loading up in a jquery colorbox on a site being developed and it loads the comment form via ajax. When it's loaded, the fix in #20812 breaks javascript because the property ""name"" is null.
Attaching a patch after posting this for only executing when `document.getElementById(""_wp_unfiltered_html_comment_disabled"")` != null." nerrad
Today 21452 When uploading media wp_unique_filename() treats capitalisation as being different. Filesystem 3.4.1 normal normal Awaiting Review defect (bug) new 2012-08-02T13:24:11Z 2012-08-02T13:24:11Z "On most web servers ""Photo.jpg"" and ""photo.jpg"" can be treated as different files.
The problem is when backing up a local copy (to my Mac) it will not let both these files exist at the same time - it wants to replace one with the other as it treats lowercase and uppercase as the same.
I suggest that we should do the same with uploads so that if ""Photo.jpg"" exisits and you upload ""photo.jpg"" is is renamed to a unique name.
I guess this would require a fix in the wp_unique_filename() function." husobj
Today 21444 update msgid-bugs-address for plugins in makepot.php I18N normal normal WordPress.org defect (bug) new 2012-08-01T20:09:09Z 2012-08-01T20:16:12Z "The msgid-bugs-address for plugins in makepot.php is outdated. References ""/tag/"" instead of ""/support/plugin/""." convissor
Today 19858 Close comments on attached images Media 3.2 normal normal Future Release defect (bug) new has-patch 2012-01-19T16:03:03Z 2012-08-01T12:46:32Z "In posts, for gallery images and individual images which open in an attachment page when clicked, the image attachment page does not close comments after the designated xx days as the original post does.
This creates a pile of spam to manage for users that rely on closed comments after xx days and post lots of images.
You can replicate the problem with these steps:
1) In Discussion Settings: set comments to close after 1 day. 'Automatically close comments on articles older than 1 days'
2)Create a post with publish date 2 days ago. Insert an image or gallery which opens in in an attachment page, not just as the image file.
3) The post will have comments closed.
4) The image attachment page will still have comments open.
Here's a test post of mine. Notice the comments closed on the post but still open for the images.
http://hackhappy.wordpress.com/2012/01/17/image-attachment-comment-test/
Bottom Line: Comments should also close after xx days for image attachments, just as the post does. Users reasonably expect this.
Check the post type for image attachment page. It may be marked as a regular page as pages are not controlled by this setting.
" dohman
Today 20854 functions.php on line 155 ? Nikolaos Raftopoulos Multisite 3.3.2 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-06-06T12:45:29Z 2012-07-31T02:42:37Z "In my network dashboard I get the following error message :
Warning: number_format() expects parameter 1 to be double, string given in /home/tklighth/public_html/wp-includes/functions.php on line 155" leondari
Today 21411 Current Local Time for Port-au-Prince, Haiti is incorrect. patrick@… Date/Time 3.4.1 normal minor Awaiting Review defect (bug) new close 2012-07-29T00:44:29Z 2012-07-29T04:50:57Z "When the Port-au-Prince Timezone is selected via wp-admin/options-general.php the Local Time is one hour behind. Please see [http://wwp.greenwichmeantime.com/time-zone/caribbean/haiti/time-haiti/] for the correct local time.
Yes, the problem occurs even when all plugins are deactivated and the default theme is activated. " pnommensen
Today 21396 Categories widget reports categories without posts when they have custom posts Widgets 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-27T02:36:46Z 2012-07-27T04:27:26Z "This problem may be related to #14084, but this report is specific to the behaviour of the Categories Widget.
- Create a custom post type eg. ""Products""
- Create a category eg. ""Photographs""
- Add some posts of type Products, assign them to category Photographs
- go to the blog page and the Categories widget lists Photographs as a category
- click on Photographs
- the ""Nothing Found"" post is shown.
There are no normal posts of category Photographs, but the widget lists a category that returns nothing. I would have expected the widget not to list a category that has no normal posts.
" pkwooster
Today 11946 Ensure image MIME type matches extension Viper007Bond Upload 3.0 normal minor Future Release defect (bug) reopened 2010-01-19T08:02:17Z 2012-07-26T22:55:00Z "Take a bitmap (BMP) and rename it to `.png`. WordPress will say it's an `image/png` everywhere you look. This can cause issues if you're trying to manipulate it (thumbnail it, etc.).
We should either fix the extension or reject it." Viper007Bond
Today 20057 Media upload for multi-webserver setups introduces a nasty race condition that could corrupt uploaded files Media 3.3.1 normal major Awaiting Review defect (bug) new 2012-02-17T05:46:40Z 2012-07-26T03:53:59Z "I am in the process of scaling a Wordpress blog with several million monthly pageviews, and I have designed a plan to scale it in the highest availability manner possible.
'''The setup'''
Each web server that hosts HTML/PHP, static files, and uploads will be replicated via rsync from time to time and sitting behind a load balancer. Rsync will run every 5min to 1 hour, and to mitigate the 404s in the uploads, I put together an nginx setup that automatically tries a different upstream server in its configuration when it encounters 404s. This allows any web server to go down at any time, and the system to run as if nothing happened. This also gives me freedom for rsyncing periodically rather than immediately and avoids 404s completely.
'''The problem'''
Now, the bug (note, I'm using Windows Live Writer which automatically names uploads image.png, but I could see this potentially happen without WLW too since WP seems to automatically name files on disk in case of collisions).
Let's say we have server A and B. The site name is foo.com. Let's also say B is out of date by an hour and a bunch of files got uploaded to A that aren't on B. Say, A has image.png and image2.png and B has only image.png.
Now, the issue is that if the load balancer directs the new post uploader (the new post contains a single image) to server B, the file that it will create on disk will be named image2.png rather than image3.png. So now B will have a file that's different from A's but is named the same way.
The main problem is that the file name is given based on what's available on the disk rather than according to the database. It's easy for this race condition (between rsyncs) to destroy the integrity of the files. Furthermore, and I've experienced this first hand), if you delete the attachment from the Wordpress UI, it could actually delete the wrong file from the wrong server as a result.
Seeing this, I can't continue with my scaling plan until file names are assigned by the database rather than the file system or I figure out how to mitigate that. I don't want to force all writers to use only server A for uploads using its direct IP, as I want HA (high availability).
Thank you." archon810
Today 21380 Impossible to modify URL of attachment Media 3.4.1 normal major Awaiting Review defect (bug) new 2012-07-25T16:16:42Z 2012-07-25T17:45:33Z "When you upload an image to a post and want to change the URL field afterwards and click ""save changes"", wordpress reloads and the URL is still the same." mkampitsch
Today 18658 Allow apostrophe in email validation Users 3.2.1 normal normal Awaiting Review defect (bug) reopened has-patch 2011-09-14T09:23:38Z 2012-07-20T23:54:05Z "When the is_email function checks the format of a supplied email, it errors when it finds an apostrophe in the local part of the email address.
Many valid emails use apostrophe's, and as such this should be accomodated in the validation." swinhoe
Today 16946 Bug between CPT menu_position and add_object_page() Administration 3.1 normal normal Future Release defect (bug) reviewing 2011-03-23T10:11:12Z 2012-07-20T13:49:29Z I write a demo plugin for describe the bug. See attachment. momo360modena
Today 21323 wp_delete_attachment (leaves stale image class wp-image-### in content of post). Media 3.4.1 normal trivial Awaiting Review defect (bug) new 2012-07-20T13:33:56Z 2012-07-20T13:33:56Z "
Here is my Example I'm using:
Running a script below (placed in the wordpress docroot) to delete all thumbnails from the database:
{{{
require_once(""wp-load.php"");
echo 'Working... '; ob_flush();
global $wpdb;
$attachments = $wpdb->get_results(""SELECT * FROM $wpdb->postmeta WHERE meta_key = '_thumbnail_id'"");
foreach($attachments as $attachment){
$wpdb->query(""DELETE FROM $wpdb->postmeta WHERE meta_id = '$attachment->meta_id' LIMIT 1"");
wp_delete_attachment($attachment->meta_value, true);
}
echo 'done!';
}}}
Now after running something like above I'm left with (inside my content of each post) a stale image class tag that no longer points anywhere.
I think a simple regex replace of the post_content for wp-image-#### Inside an Image tag would remove the stale element.
I haven't checked this with other attachment types to see if it also exists, but my guess is it would." eliddon
Today 21311 "The ""Paste as plain text"" feature in TinyMCE produces double-line breaks between paragraphs." Editor 3.4.1 normal minor Awaiting Review defect (bug) new close 2012-07-19T10:41:13Z 2012-07-20T08:44:55Z "Mac OSX Lion, Chrome, WordPress 3.4.1
See attached SWF for a screen-video demonstration.
• In WP-Admin -> Posts -> Add new, with the editor in visual mode, click the ""Pase as plain text"" icon [[BR]][[BR]]
• Paste your content into the window that pops up and click ""Insert"" [[BR]][[BR]]
• Note that two paragraphs seem to be double-line breaked. [[BR]][[BR]]
• Switch to HTML mode and note that there are extra "" "" spaces inserted between paragraphs. [[BR]]
" uxtremist
Today 21306 "Archived blogs should return HTTP ""404 Not Found"", not ""410 Gone""" Multisite normal normal Awaiting Review defect (bug) new has-patch 2012-07-18T19:39:51Z 2012-07-18T19:39:51Z "In a multisite network, if a site is archived, ms_site_check() currently serves up a HTTP 410 status code. Here's what the [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html HTTP spec] has to say about 410:
The requested resource is no longer available at the server and no forwarding address is known. This condition is expected to be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.
It's acceptable to serve a 410 if the site is marked as deleted or spam, but I don't think that archiving the site is an indication that the site is permanently and irrevocably gone. Although a case can be made for changing it to 404, my contention is that a 403 is more appropriate for semantics and for bots. From the same HTTP spec:
403 Forbidden: The server understood the request, but is refusing to fulfill it.
vs
404 Not Found: The server has not found anything matching the Request-URI." amattie
Today 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
Today 18232 wp_nav_menu - Setting walker parameter affects fallback_cb Menus 3.2.1 normal normal Awaiting Review defect (bug) new has-patch 2011-07-24T08:14:35Z 2012-07-17T17:20:50Z "When using the walker parameter with wp_nav_menu and there is no menu present, wp_nav_menu falls back by default (set with fallback_cb) to wp_page_menu. It appears that the set walker also affects wp_page_menu, which in most cases breaks the output.
wp_nav_menu usage:
{{{
new Walker_Nav_Menu)); ?>
}}}
Output when no menu is present (falling back on wp_page_menu):
{{{
// Formatted for readability
}}}
Expected output:
{{{
// Formatted for readability
}}}
As you can see, the output from wp_page_menu is getting filtered through the walker, but since the walker was designed for menus specifically, it renders the default output from wp_page_menu useless (empty tags..etc)." bryanjwatson
Today 21293 Add bbPress as a flavor option to WordPress Showcase WordPress.org site normal normal WordPress.org defect (bug) new 2012-07-17T08:29:13Z 2012-07-17T12:02:44Z "First discussed here:
http://bbpress.org/forums/topic/bbpress-content-re-organization/#post-114999
The bbPress 2 plugin is now quite mature and gaining traction. There are some outstanding sites using bbPress 2 well worth showcasing already, such as [http://devpress.com/forums/ devpress.com/forums]. It's high time the WordPress showcase site received a ""bbPress"" flavor to accommodate great looking forum sites." Sadr
Today 21207 Link-template pagination link for page 1 missing query string args Template 3.4 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-07-09T20:28:25Z 2012-07-16T14:38:37Z "In paginated pages, when on a page that is greater than page 1, the link for page 1 and the 'previousposts' link do not include any query arguments. This is fine if not including the first page argument, but not for other arguments in the query string.
For example pages that show results for form searches. The search criteria are stored with the GET method as query strings in the URL and need to be maintained from page to page as the user pages through their results.
This is in /wp-includes/link-template.php on line 1421.
A probable fix is the 'if' clause from if( $pagenum > 1 ) changed to if( $pagenum > 0 ).
I was wondering if you can apply this fix to future updates?
Thanks" alexk45
Today 20386 "Year permalinks ""win"" against category permalinks" Canonical normal normal Future Release defect (bug) new 2012-04-07T05:20:55Z 2012-07-16T04:14:43Z "We need to decide whether category permalinks should take priority over year permalinks.
e.g. /2008/?category_name=cat-a
Should that stay the same, or redirect to:
/category/cat-a/?year=2008
We have a unit test which is failing." markjaquith
Today 21268 _wp_page_template is getting 'stuck' to a page General 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-13T22:21:42Z 2012-07-13T22:21:42Z "Unmodified WP 3.4.1 / Ummodified TwentyEleven theme
Create a page (id=2). Manually add a postmeta entry for
{{{
post_id=2,
meta_key = _wp_page_template,
meta_value = pagefull.php
}}}
The page now opens with margin: 0 7.6%; (correct!)
Now try to change it back to default, either by removing the _wp_page_template postmeta record or by editing the page -> Page Attribute / Template. The page will not revert back to Default. It continually displays as Full Width, and a postmeta item telling post_id 2 to use _wp_page_template = pagefull.php is added.
http://wp34.roveridx.com/?page_id=2
This behavior does not happen in 3.3.2." shawmutsteve
Today 21265 settings_fields() conflict with admin-ajax.php in ajax requests Plugins 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-13T19:30:32Z 2012-07-13T19:30:32Z "I created a plugin, which uses the function 'settings_fields()' to generate required fields. When I save the plugin options, I decided to use Ajax Requests to save time.
Until 3.3.2 this was working well, but with 3.4.1 admin-ajax.php code update generates a errors. Because ""settings_fields()"" generate hidden field called ""action"" and before 3.4.1 admin-ajax.php used $_GET['action'] to call ajax action dynamically.
'''How reproduce:'''
1. Use WP 3.4.1
2. Put this code snippet in a .php file in wp root folder:
{{{
}}}
In wordpress 3.4.1 field 'action' changes to 'update', because $_REQUEST['action']. In wordpress 3.3.2, field 'action' is 'mysettings_save'.
I have to redo all my work with my plugin with this change in Wordpress 3.4.1. " vdvtt
Today 10377 Comment fields should have max lengths Comments 2.8 normal normal Future Release defect (bug) new 2009-07-10T14:34:27Z 2012-07-13T01:05:25Z "Hello, I don't know if exactly it's a bug or use javascript validation, but i think so there's no
treatment for this, or was fix in the new version.
In the section of comments(Wordpress 2.8), we can insert how many characheters we wants, generating an SQL Exception and breaking the all system.
The solution is simple, use the property maxlenght in the tag
e limit the characters if will be send to database.
" muriloazevedo
Today 20383 Strip trailing punctuation with canonical URLs Canonical normal normal Future Release defect (bug) new 2012-04-07T03:59:49Z 2012-07-13T00:47:29Z "A follow-up to #7537 where we removed %20 and "" "" from the end of URLs, we should try to remove all sorts of punctuation from the end of a URL, both URL-encoded and decoded.
Example bad URLs we should surely be able to resolve:
http://ma.tt/2012/03/productivity-per-square-inch/%7B
http://ma.tt/2012/03/productivity-per-square-inch/)
http://ma.tt/2012/03/productivity-per-square-inch/,
http://ma.tt/2012/03/productivity-per-square-inch/!
More difficult when there is no trailing slash in the permalink structure (or the link requested, regardless of permalink structure), but if is_404() is taken into account, it should be doable to trail various pieces of punctuation and see if we can get things to resolve." nacin
Today 21234 Recursive directory creation & get_calendar() for custom post types General 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-12T12:31:28Z 2012-07-13T00:28:43Z "Hello!
I made two patches, and sent the pull request on githab.
https://github.com/WordPress/WordPress/pull/12
https://github.com/WordPress/WordPress/pull/14
And I want to join to contributers team. How can I do it?
Irc chanel is Terminated :(" avaddon
Today 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
Today 21204 Encoding problem with errors and warnings General 3.4.1 normal normal Awaiting Review defect (bug) new 2012-07-09T16:31:04Z 2012-07-09T22:01:05Z "There are several functions for debugging and their messages are also localized. For example _deprecated_argument(), _doing_it_wrong(), etc. But when these functions are fired, encoding of the whole administration (not only error messages) is damaged (see attached screenshot).
It is not very good because even if debugging is turned off, some errors can be still triggered - for example trigger_error() in ms_subdomain_constants() function, etc." pavelevap
Today 20944 Changing plugin filename causes Fatal error on automatic activation after update Plugins 3.3 normal normal Awaiting Review defect (bug) new has-patch 2012-06-13T19:43:38Z 2012-07-08T20:56:03Z "In a new version of a (my) plugin in the WordPress repository, I changed the filename of the main plugin file (to match the folder name). When an old version of the plugin is activated, doing an automatic update to the latest version of the plugin (with the new filename), the following error message is displayed: ""The plugin jonradio-display-kitchen-sink/jonradio-kitchen-sink.php has been deactivated due to an error: Plugin file does not exist.""
An immediate manual Activation completes successfully.
Observed on sites with WordPress Network turned off and on, including when the plugin was Network Activated.
Plugin is jonradio Display Kitchen Sink, and update was from Version 1.0 to 1.1." adiant
Today 21172 Adding the first filter/action in an earlier priority during a later priority causes the earlier priority to run (last) Plugins 3.4 normal normal Awaiting Review defect (bug) new has-patch 2012-07-05T23:30:54Z 2012-07-07T22:41:11Z "During testing of #21169, it occurred to me that [http://core.trac.wordpress.org/ticket/5338#comment:1] might present a problem with each rather than next/current, but that turns out not to be the case. Instead, this exposed a different bug:
If you add a new filter at priority 9, when priority 9 did not previously have any filters, during the priority 10 execution, the priority 9 filter will run (!) after all other priorities (since the filters are not resorted after each priority).
(Generally, if you add an earlier priority that did not previously have any filters during a later priority...)
The attached unit test demonstrates this behavior." devesine
Today 21185 Upload/insert popup not scrollable on iPad General normal normal Awaiting Review defect (bug) new 2012-07-07T20:58:36Z 2012-07-07T20:58:36Z "When using iPad (testing with a v1 iPad) the upload/insert popup is not scrollable so if you expand an image by clicking ""show"" you cannot scroll down to the"" insert into post"" link." husobj
Today 21182 WP_HTTP_Cookie doesn't handle the default conditions for the 'domain' and 'path' field correctly. HTTP low minor Awaiting Review defect (bug) new 2012-07-07T04:34:45Z 2012-07-07T04:34:45Z "WP_HTTP_Cookie currently handles ""simple"" cookies in exactly the same way they're received, that is, it only fills in the details that the set-cookie header contained.
However, some fields are optional, and as a result of this, the [http://www.ietf.org/rfc/rfc2109.txt rfc for state management] specifies a set of default values for certain fields:
{{{
4.3.1 Interpreting Set-Cookie
The user agent keeps separate track of state information that arrives
via Set-Cookie response headers from each origin server (as
distinguished by name or IP address and port). The user agent
applies these defaults for optional attributes that are missing:
VersionDefaults to ""old cookie"" behavior as originally specified by
Netscape. See the HISTORICAL section.
Domain Defaults to the request-host. (Note that there is no dot at
the beginning of request-host.)
Max-AgeThe default behavior is to discard the cookie when the user
agent exits.
Path Defaults to the path of the request URL that generated the
Set-Cookie response, up to, but not including, the
right-most /.
Secure If absent, the user agent may send the cookie over an
insecure channel.
}}}
We currently don't do anything special for Secure cookies (From what I can see), but we also need to handle the 'domain' and 'path' field defaults better, as currently they remain at the default null if nothing is passed. This can result in domains passing the WP_HTTP_Cookie::test() method to a different domain or path than they were issued on.
Example cookie values (and WP_HTTP_Cookie representations) which can trigger this:
{{{
PHPSESSID=ros1liponkqip23k9le0hhmp31; path=/' (length=44)
test=1341632838; expires=Sat, 07-Jul-2012 04:47:18 GMT
array (size=2)
0 =>
object(WP_Http_Cookie)[87]
public 'name' => string 'PHPSESSID' (length=9)
public 'value' => string 'ros1liponkqip23k9le0hhmp31' (length=26)
public 'expires' => null
public 'path' => string '/' (length=1)
public 'domain' => null
1 =>
object(WP_Http_Cookie)[86]
public 'name' => string 'test' (length=4)
public 'value' => string '1341632838' (length=10)
public 'expires' => int 1341636438
public 'path' => null
public 'domain' => null
}}}
This is not a issue for WordPress core, but could affect plugins who do anything special with Cookies." dd32
Today 20770 Introduce AJAX response message Widgets 3.4 normal minor Awaiting Review defect (bug) new has-patch 2012-05-29T02:34:09Z 2012-07-05T23:45:10Z "when clicking on Save button of a widget, a error should appear if the user is logged out.
So after clicking the button the wpspin animated images disappears and nothing happens. This can be a problem if the current user think he is logged in and he is not, the settings just will not be saved.
Sometimes the server is not working.
Need to adjust the javascript code and php:
in php we can use die function : die('1') or die('success');
in javascript something like this:
{{{
$.post(ajaxurl, data, function(response){
if (response === 'success') {} else { alert('Fail to save'); }
});
}}}
http://wpimpact.com/wp-content/uploads/2012/05/Untitled-4.png
" alexvorn2
Today 19945 Bug in ../wp-includes/widgets.php Barti112 Widgets 3.3.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2012-02-02T08:22:34Z 2012-07-05T14:21:33Z "in this file there are at some places the following code:
$widget = array_merge($widget, $options);
it is possible that $options is not an array and i become a php-warning.
i think better is to check the arrays before you use this function:
if(is_array($widget) && is_array($options)){
$widget = array_merge($widget, $options);
}
" Barti112
Today 21158 different result when shortcode atribute without value Shortcodes 3.4 normal normal Awaiting Review defect (bug) new 2012-07-04T19:11:44Z 2012-07-04T19:11:44Z "imagine those two shortcodes
{{{
[shortcode attribute]
[shortcode attribute=value]
}}}
IMO they should have the same result, just the second should have some value to the attribute and the first should have NULL or false
But if you do
{{{
add_shortcode( 'shortcode', 'my_shortcode' );
function my_shortcode( $atts ) { print_r ($atts); }
}}}
the first shortcode results in
{{{
array (
0 => 'attribute',
)
}}}
while the second in
{{{
array (
'attribute' => 'value',
)
}}}
I'm not sure, maybe it is intentional, i have not found any description, what should shortcode attribute without value do. But imo it should work as i have described as it is the only way how it could clear some predefined value (the only other way is to set it to empty string, which may not always be the same as NULL or FALSE)." thomask
Today 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
Today 12584 Emails from WordPress Admin are html encoded Mail 2.9.2 normal normal Future Release defect (bug) new has-patch 2010-03-11T16:41:17Z 2012-07-03T16:55:00Z "When a comment form is filled out that contains characters that are candidate for html encoding in the display of the comment on the web site, those comments are also html encoded in the display of the notification email send to the author.
Example comment left on my WordPress install:
Ampersand: &
Quote: ""
Registered: ®
Resulting email notification:
{{{
New comment on your post #168 ""Prevent iTunes from creating unnecessary clutter and cruft""
Author : --
E-mail : --
URL :
Whois : --
Comment:
Ampersand: &
Quote: ""
Registered: ®
}}}
You can see all comments on this post here:
http://example.com/prevent-itunes-from-unnecessary-clutter-and-cruft/#comments
Delete it: http://example.com/wp-admin/comment.php?action=cdc&c=xxxx
Spam it: http://example.com/wp-admin/comment.php?action=cdc&dt=spam&c=xxxx
It appears that only the ampersand has this issue. I am not sure if it also applies to the subject of the email, but can confirm it applies to the body of the email.
The email headers show it was sent as plain text:
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=""UTF-8""" hexley
Today 21134 Registering and enqueueing on the same action can cause enqueueing to happen before registering General 3.4 normal normal Awaiting Review defect (bug) new 2012-07-02T11:00:17Z 2012-07-03T01:42:10Z "We have two plugins, plugin1 and plugin2. Plugin1 registers a script, Plugin2 wants to enqueue this script. Both of these routines are executed on the [http://wpdevel.wordpress.com/2011/12/12/use-wp_enqueue_scripts-not-wp_print_styles-to-enqueue-scripts-and-styles-for-the-frontend/ _enqueue_scripts] action.
There is a chance that enqueueing in Plugin2 will happen before registering in Plugin1 and therefore fail.
Possible fixes:
* Every time we enqueue a script, registered in another plugin, we use a higher priority. I am not a fan of this approach, because it is opaque – we need to document each enqueue like this, because the next developer might not know why did we use higher priority.
* Every time we register a script, we use a lower priority. I am not a fan of this either, because we will have to do this for almost every register, because we can't know if another plugin won't try to enqueue our scripts.
* Violate core recommendation and register the script on an earlier hook. I am not a fan of approach for obvious reasons.
* Add {{{_register_scripts}}} hooks and recommend plugin authors to register their scripts at this time.
I would prefer if we added another set of hooks, because it both makes sense to register on a register hook (as opposed to enqueue hook) and it separates the two actions, so that we can execute them at different times.
When we agree on a solution, I would be happy to write the patch.
" nbachiyski
Today 20589 domain_exists should add trailing slash to path Multisite 3.0 normal minor Awaiting Review defect (bug) new has-patch 2012-05-01T16:49:18Z 2012-07-03T00:36:37Z {{{insert_blog}}} runs {{{trailingslashit}}} on the path, however, {{{domain_exists}}} uses whatever is passed in. If WP is enforcing the trailing slash on blog insertion, it really should when checking existence. It should probably also cast the site_id as an int per {{{insert_blog}}}. ejdanderson
Today 21140 """Display name publicly as"" setting not set until a change is made in the setting" nickharambee Users 3.4 normal normal Awaiting Review defect (bug) new has-patch 2012-07-02T21:29:48Z 2012-07-02T22:37:46Z "I have found this issue with several users that I have set up on my site. The default value for ""Display name publicly as"" is the first name of the user when creating a new user, or at least that is what shows in the ""Display name publicly as"" drop-down menu. However, when creating a new user, the full name, i.e. the first and last name is what displays publicly. In order to get only the first name to display publicly I need to set the ""Display name publicly as"" option to another option, save changes, and then reset it to just the first name, and save changes again.
Surely, if it is the first name that shows in the drop-down menu, it should be the first name that actually displays publicly, without having to go through this rather strange process?
I am using the latest version of Buddypress (1.5.6) as well as several other plugins. I have not tried disabling all of these." nickharambee
Today 21139 Month format in Publish box I18N 3.4 normal normal Awaiting Review defect (bug) new 2012-07-02T18:47:26Z 2012-07-02T20:03:24Z "New translatable month format was introduced in r19820.
Problems:
1) Month numbers are not localized. Czech does not use numbers with format 01, 02, etc. I can remove month numbers by ""not translating"" them, but it is not the best solution.
2) How should be strings ""May_May_abbreviation"" translated in the right way? I found that some languages uses for example ""Kvě_Květen_abbreviation"" translation and others only ""Kvě"". Translators are probably afraid of removing ""_May_abbreviation"" part because they do not want to broke anything even if there is preg_replace function following. I do not understand why there has to be the whole ""May_May_abbreviation"" original string? Also explanation for translators (three-letter abbreviation of the month) is not exact, because we can use 2 (better for Czech) or any other number of characters." pavelevap
Today 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
Today 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
Today 18172 Two lay-out buttons active at the same time azaozz TinyMCE 3.2.1 normal minor Awaiting Review defect (bug) reviewing 2011-07-19T11:26:49Z 2012-06-29T13:50:48Z "1) Click on the center button for writing in the middle. It doesn't matter if you write something or not.
2) Upload a image and line it out at the left or right side.
3) When you select the image two buttons are active. One for the text and one for the image...
(See screen)
" JonezJeA
Today 14465 Update Plugins Hangs while displaying 'updating' Upgrade/Install 3.0.1 normal normal Future Release defect (bug) new 2010-07-30T07:45:17Z 2012-06-28T14:49:09Z "Hi,
Whenever I try to update a plugin the update plugins screen hangs indefinetly.
Example message while this is happening would be-
""The update process is starting. This process may take awhile on some hosts, so please be patient.
Enabling Maintenance mode…
Updating Plugin Link Library (1/1)""
The plugin ulitmately gets updated if I wait a minute or two but this page never refreshes.
I am running WP 3.0.1 but this happend on 3.0.0 as well.
My host is running
MySQL 5.0.90-community
PHP 5.2.13
and my browser is IE8." jamesfed
Today 14060 "Misleading ""You do not have sufficient permissions to access this page.""" Plugins 3.0 normal normal Future Release defect (bug) new has-patch 2010-06-23T14:46:16Z 2012-06-27T21:50:39Z "When accessing a page of a plugin in the admin that does not exists any longer, you're told by an error message, that:
> You do not have sufficient permissions to access this page.
This message is a little misleading, because there is no such page.
A message that better reflects the decision to display it would be less misleading, e.g.:
> The requested page is not accessible.
" hakre
Today 17036 Theme editor shouldn't override root directory files with same names in child directories Administration 3.1 normal normal Future Release defect (bug) new 2011-04-03T19:11:33Z 2012-06-27T10:23:07Z "'''Steps to reproduce:'''
1. Create subdirectory: blogs
1. Create file in subdirectory: index.php
1. Try selecting Main Index Template in Theme Editor
Example is taken from BuddyPress' theme structure. `get_file_description()` doesn't account in any way for the presence of subdirectories since it uses `basename()`." kawauso
Today 21078 "Image Captions are inserted without caption=""..."" inside the caption tag" Template 3.4 normal normal Awaiting Review defect (bug) new close 2012-06-26T08:17:49Z 2012-06-27T01:38:46Z "Since WordPress 3.4 captions are inserted this way:
{{{
[caption id=""attachment_123"" align=""aligncenter"" width=""550""]
My Caption[/caption]
}}}
This means themes cannot display them properly. Previous versions inserted the caption like this:
{{{
[caption id=""attachment_123"" align=""aligncenter"" width=""550"" caption=""My Caption""]
[/caption]
}}}
Here's a forum thread discussing the issue: http://wordpress.org/support/topic/caption-broken-in-new-34-posts" versluis
Today 20882 Remove strings related to Akismet from WP localization files I18N 2.0 normal normal Awaiting Review defect (bug) new 2012-06-07T20:10:36Z 2012-06-26T03:14:15Z "There were several tickets (#19832, #19597) related to this issue, but we had to miss it somehow for 3.4.
Main purpose of this ticket is removing all strings related to Akismet from localization files. All strings (about 110) are loaded (mainly on frontend) even if Akismet is not active. Akismet can have its own localization file." pavelevap
Today 20870 error notice when $post = NULL with gallery_shortcode Media 3.3 normal trivial Awaiting Review defect (bug) new 2012-06-07T11:05:46Z 2012-06-26T03:12:02Z "i have noticed with many relevant plugins and functions it may happen, that gallery_shortcode is called when global $post returns NULL. problem is, that gallery_shortcode function media.php containts
{{{
'id' => $post->ID,
}}}
(row 798 on 3.4 or 783 on 3.3.2) so when $post is NULL it returns error notice
there is trivial solution - adding (!$post)