<?php bloginfo_rss('name'); wp_title

bis

etc. }}} When you make manuell a new line in front of these elements, you won't find any problem, so WordPress must put an automatic line break in front of these elements and it doesen't do it. Please fix this nerved bug!! regards, Dunkelangst from http://www.dunkelangst.org/ " Dunkelangst Future Releases 23757 convert_smilies should not convert in pre,code tags Formatting 3.5.1 normal normal Awaiting Review defect (bug) new 2013-03-13T14:26:07Z 2013-03-14T11:22:31Z "This related to this ticket [[BR]] #23756 The purpose to this ticket is to make writing codes in posts more easier !! " alex-ye Future Releases 23605 esc_url() strips spaces instead of encoding them Formatting normal normal Awaiting Review defect (bug) new 2013-02-25T17:41:21Z 2013-02-27T23:56:38Z "If I pass a URL into `esc_url()` that contains a space, the space is stripped instead of encoded. To reproduce: {{{ $url = 'http://example.com/foo bar/'; echo '
';
var_dump( $url );
var_dump( esc_url( $url ) );
echo '
'; }}} The resulting URL ends up as `http://example.com/foobar/` instead of the expected `http://example.com/foo%20bar/`" johnbillion Future Releases 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 Future Releases 23050 make_clickable incorrectly formats anchors with URL's and spaces in them in comments Formatting 3.4.2 normal normal Awaiting Review defect (bug) new 2012-12-23T00:32:30Z 2012-12-23T16:27:36Z "When posting a comment, if an anchor tag contains both a URL and some words, make_clickable formats the output incorrectly. To duplicate, post the following content in a comment: {{{ Hey! http://wordpress.org is awesome in case you didn't know! }}} When viewing the comment, you'll get: {{{ Hey! http://wordpress.org is awesome in case you didn't know. }}}" johnjamesjacoby Future Releases 23308 "make_clickable problem with multiple ""Punctuation URL character""" Formatting 3.5.1 normal normal Awaiting Review defect (bug) new 2013-01-28T15:09:59Z 2013-01-28T15:09:59Z "make_clickable problem with multiple ""Punctuation URL character"" E.g. {{{ http://www.wordpress.org/some-(parentheses).html }}} Results in this html code: {{{ http://www.wordpress.org/some-(parentheses).html }}} But obvious should be: {{{ http://www.wordpress.org/some-(parentheses).html }}} I suggest to replace: wp-includes/formatting.php:1603 {{{ [\'.,;:!?)] # Punctuation URL character }}} with {{{ [\'.,;:!?)]{1,} # Punctuation URL character }}}" DrPepper75 Future Releases 23756 make_clickable should not convert the URLs in pre,code tags Formatting 3.5.1 normal normal Awaiting Review defect (bug) new 2013-03-13T14:17:36Z 2013-03-14T10:44:29Z "Hi , Maybe it's a duplicate ticket but I tried to search in history. Anyway , The purpose of this ticket is to have a clean snippet code posts .. for now it's hard to do it by plug-in .. and many people remove make_clickable filter at all ! So let's make it possible in 3.6 :)" alex-ye Future Releases 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 Future Releases 24157 safecss_filter_attr doesn't allow rgb() in inline styles Formatting 3.5.1 normal normal Awaiting Review defect (bug) new 2013-04-22T16:30:45Z 2013-04-22T16:30:45Z "I thought there should be a ticket somewhere, but I couldn't find it! So, `safecss_filter_attr` (which is used in `wp_kses` etc, does not allow inline styles that include rgba() etc, like his: {{{}}} I am not sure if this is intended, though not sure why it would be, there is a comment in `safecss_filter_attr` {{{if ( preg_match( '%[\\(&=}]|/\*%', $css ) ) // remove any inline css containing \ ( & } = or comments}}} " joehoyle Future Releases 14050 shortcode_unautop() should also remove the
added after shortcodes Formatting 3.0 normal normal Future Release defect (bug) new dev-feedback 2010-06-22T18:15:27Z 2013-01-19T08:38:00Z "Currently `wpautop()` wraps a shortcode in `
` tags as well as adding a `
` tag after the shortcode. We then use `shortcode_unautop()` to remove the `
` tags, but the `
` stays. To replicate, just drop a few caption shortcodes into a post and set them all to align left or right. You'll see that even though they all float (assuming that's how your theme handles them) they stair step down because of the extra `
` I'm not a regex expert so someone should probably double check my patch, but it seems to work for me." aaroncampbell Future Releases 18549 wp_texturize incorrectly curls closing quotes after inline HTML end tags Formatting 3.2.1 normal normal Awaiting Review defect (bug) new 2011-08-30T21:54:26Z 2013-03-22T13:39:47Z "The following source HTML: {{{ The word is ""quoted"". The word is 'quoted' The word is 'quoted.' The word is 'quoted'. The word is 'quot'd }}} Gets incorrectly transformed by wp_texturize() as: {{{ The word is “quoted“. The word is ‘quoted‘ The word is ‘quoted.‘ The word is ‘quoted‘. The word is ‘quot‘d }}} '''Note:''' all the double/single quotes in the above examples that should be closing are instead opening) This renders in the browser like this: {{{ The word is “quoted“. The word is ‘quoted‘ The word is ‘quoted.‘ The word is ‘quoted‘. The word is ‘quot‘d }}} The problem here is that wp_texturize splits the text on all start/end tags, which makes sense for block-level tags, but not inline-tags like {{{}}} and {{{}}}. formatting.php line 67: {{{ $textarr = preg_split('/(<.*>|\[.*\])/Us', $text, -1, PREG_SPLIT_DELIM_CAPTURE); }}} However if you change it to only split the content on block-level tags, you'll need something more sophisticated/complex than a regular expression to avoid curling quotes within html." justincwatt Future Releases 4116 wp_texturize to defect certain links in comments and on page Nazgul Formatting 2.2.1 normal normal Future Release defect (bug) reopened needs-unit-tests 2007-04-09T13:29:33Z 2010-11-23T04:53:07Z "the wp_texturize() function in formatting.php (includes) of wordpress breaks links of the domain format (number)x(number). For example, a comment left by a domain such as www.h4x3d.com, which includes the (4)x(3) in the domain name, renders to www.xn--h43d-rma.com. This breaks the link. It does occur on the page, but also with in the page comments. It does also occur when the text with the special combination is not a link, but plain text." h4x3d Future Releases 20444 wpautop acts on a single line of text Formatting normal normal Awaiting Review defect (bug) new 2012-04-15T03:02:06Z 2012-10-10T14:11:40Z "HTML markup on a single line wrapped in a block element is interpreted and changed by wpautop. The wpautop function is described as replacing ""double line-breaks with paragraph elements"" which led me to expect the single line would not become many lines. {{{ echo wpautop( '
Hello world
WordPress
' ); }}} {{{

Hello world

WordPress
}}} Extra
before the . I expected wpautop would find no newlines and return the original string. The same string placed inside a HTML5 or XHTML 1 Strict document is parsed as valid by W3C Validator. Plugins acting on the_content with a priority less than 10 may have their single-line markup reinterpreted by wpautop." niallkennedy Future Releases 2833 wpautop breaks style and script tags Formatting 2.0.3 low normal Future Release defect (bug) reopened needs-unit-tests 2006-06-17T20:36:00Z 2012-09-09T21:01:21Z "When I create a post in which I want to include Javascript or some styles, WordPress 'breaks'when showing those posts, because all newlines in the SCRIPT and STYLE tag are converted into BR tags. Example: {{{ }}} Becomes: {{{
}}} And: {{{ }}} Becomes {{{
}}} This happens because wpautop adds those BR tags to the post. (As it should, just not within STYLE or SCRIPT tags.) I've made a (temporary?) workaround for this by creating a pre and post event for wpautop, which substitute the necessary newlines by a temporary value in the pre event and placing them back in the post event. Although I think this should be incorporated in wpautop itself. See also: http://wordpress.org/support/topic/76433 and http://wordpress.org/support/topic/76297 While searching trac I also found ticket #2346, which is about the same problem, but which was for 2.0 and self-closed by the submitter? P.S. I have TinyMCE turned of." Nazgul Future Releases 4298 wpautop bugs markjaquith* Formatting 2.7 low minor Future Release defect (bug) accepted dev-feedback 2007-05-19T22:14:10Z 2010-04-04T06:42:21Z "wpautop should at least ignore multiline html tags, and possibly ignore any area enclosed within html. {{{

Once I saw it here, I instantly knew what I wanted. I love my new woven wood shades.
- Ginny Good

}}} gets formatted as: {{{ style=""width: 120px; height: 92px; text-align: left; margin-left: auto; margin-right: auto;""
border=""1"" cellpadding=""7"" cellspacing=""2"">
Once
I saw it here, I instantly knew what I wanted. I love my new woven wood
shades.

- Ginny Good }}} " Denis-de-Bernardy Future Releases 15918 wpautop() breaks inline tags on the same line as block tags dunno Formatting 3.0.3 normal major Future Release defect (bug) new early 2010-12-20T16:01:31Z 2012-04-11T15:22:31Z "Hi guys! I've got latest WP installation (3.0.3) and found strange bug in posts parser. Create article with following HTML: {{{
WP IZ ASSUM
}}} Browser will get: {{{
WP IZ ASSUM
}}} All seems to be fine! Now get rid of unnecessary div. Create article with following HTML: {{{ WP IZ ASSUM }}} Browser will get: {{{
WP IZ ASSUM
}}} Dunno why there is extra
but who cares. All seems to be OK. Create article with following HTML: {{{
WP IZ ASSUM
}}} Browser will get: {{{
WP IZ ASSUM

}}} Now isn't that cool? But check what is even cooler! Create article with following HTML: {{{
WP IZ ASSUM
NO IT'S BUGGY AS HELL

}}} Browser will get: {{{
WP IZ ASSUM

NO IT’S BUGGY AS HELL

}}} Wow! Say hello to invalid markup and rendering problems! Auto-closing of tags turned off. No matter of the settings I still get this nice messed up html. WYSIWYG turned off also." retrib Future Releases 6984 wpautop() formats the the contents of shortcodes Formatting 2.6 low trivial Future Release defect (bug) new 2008-05-17T10:34:02Z 2009-11-28T07:20:24Z "`wpautop()`, the bane of my existence as a plugin developer, is at it again. Here's an example of some PHP wrapped in a valid shortcode in a post of mine: {{{ [code lang=""php""]$text = str_replace( array('
', '
'), array('
', '
'), $text);[/code] }}} The content that gets passed to my shortcode function is this: {{{ $text = str_replace( array('
', '

'), array('
', '

'), $text); }}} Expected result: it shouldn't touch the insides of valid shortcodes (like adding line breaks or anything as it is doing now)." Viper007Bond Future Releases 5250 wpautop() issue with lists Formatting 2.3 normal normal Future Release defect (bug) new 2007-10-24T00:32:38Z 2011-07-30T15:34:50Z "First of all, my sincere apologies if this is a duplicate. The problem, in short: WordPress inserted a number of unclosed `
` tags into my post. It should either insert correctly closed tags, or none at all. I honestly would prefer the former. In detail: I had HTML code very similar to this:

text

subtext

more text

This was automatically converted to:

text

subtext

more text

Note the extra `
` tag in the above, which is unclosed (making the W3C validator choke on my website). Also note, I was not using the WYSIWYG editor (turning it off was the first thing I did), so it's unlikely to be due to that. As a workaround, manually inserting properly closed `
` tags works just fine:

text

subtext

more text

Since this workaround exists, the bug is not very prioritary, but it should also (hopefully) be easy to fix." Narc0tiq Future Releases 10033 wptexturize and wpautop problems with html comments and object tags Formatting 2.8 normal minor Future Release defect (bug) new 2009-06-04T12:06:35Z 2010-11-23T05:43:55Z "Bumped into this one when upgrading my mediacaster plugin to use swfobject 2.1 (which is not 1.5 compatible), as documented here: http://code.google.com/p/swfobject/wiki/documentation I take it I'm not the only one who is going to need to upgrade a plugin. It's minor, since I'll just move the filter further down in the queue, but it's still worth reporting: {{{ }}} Gets turned into the following mess: {{{
}}} So, two/three issues: - wpautop should also ignore double object tags, and html comments - wptexturize should ignore html comments" Denis-de-Bernardy Future Releases 16957 wpuntexturize - problem with numbers and non-breaking spaces Formatting 3.1 normal normal Awaiting Review defect (bug) new 2011-03-24T10:21:33Z 2013-01-14T01:37:56Z "1) Insert following code into HTML editor and publish. {{{ New Year ""2011"" will be fantastic. }}} Then look at website: {{{
New Year ”2011″ will be fantastic.
}}} You can see wrong html quotes. 2) I also worked with TinyMCE editor (only writing simple text, paragraphs, strong, moving some parts of text by CTRL+C and CTRL+V). But after publishing, there were hidden non-breaking spaces in text. There were on different places, for example before ""("" and after characters ""."", ""í"", ""é"", etc. But they were random. I am not sure how it can be caused? Non-breaking strings were not visible and also not transformed into HTML entity on website. I noticed them only in HEX editor, when examining HTML source code (C2 A0). Of course, when these non-breaking spaces were before (or after) quotes, then quotes were not recognized regurarly by wpuntexturize, example: {{{ Nemám žádné ""úžasné"" schopnosti. }}} Is transformed by wpuntexturize into: {{{
Nemám žádné ”úžasné” schopnosti
. }}} You can see wrong open quote: {{{ instead of “ there is ” }}} But only when hidden non-breaking space (C2 A0) is between žádné a ""úžasné""." pavelevap Future Releases 11023 Gallery Category Doesn't change with article Gallery normal normal Future Release defect (bug) new 2009-10-24T01:49:09Z 2009-12-08T00:56:23Z Lets say I have a default category setup called Drafts that all articles go into at first by default. Then on completing the article before posting it live, I movie it to another category called News (no longer having the draft category ticked also). If I've added an image with that article that I click to view a bigger picture of in the gallery page (image.php). It still shows it as being listed under the Drafts category, while the article itself is listed under just News category. mrgtb Future Releases 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 Future Releases 18701 """hierarchical"" argument for get_pages() does nothing" General 3.0 normal normal Awaiting Review defect (bug) new 2011-09-19T06:48:32Z 2011-11-16T00:17:33Z "The `hierarchical` argument for `get_pages()` is never actually used. It is in an `if` statement, but one that requires `child_of` to also be set: {{{ if ( $child_of || $hierarchical ) $pages = & get_page_children($child_of, $pages); }}} Props Vynce Montgomery for pointing this out to me." Viper007Bond Future Releases 18703 'pre_get_posts'-filter without effect when modifying 'tax_query'. Wrong parameters passed to 'parse_tax_query() ??; WP 3.2.1. info@… General 3.2.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2011-09-19T13:10:12Z 2012-05-31T16:27:52Z "When modifying the 'tax_query' array directly with 'pre_get_posts' filter (e.g. setting 'include_children' to false), then it will firstly be modified in 'wp-includes/query.php' -> get_posts() after running the filter in line 1911. But after line 2195 and running 'parse_tax_query' the 'tax_query' 'include_children'-parameter is unwanted reset/changed to the default value. I think the bug is the following: parse_tax_query() uses and needs values from the 'tax_query'-array but gets passed over only the 'query_vars'-array. so it resets the 'tax_query'-array-parameters in query.php line 1678 and hereby also the previously and individually set 'tax_query' values. as far as i understand the core, i assume that any changes to the 'tax_query'-array with 'pre_get_posts'-filter will get lost and only changes to the 'query_vars'-array will take effect." xitromedia Future Releases 24023 3.5/wp-includes/functions.php : missing break statement General 3.5.1 normal normal Awaiting Review defect (bug) reopened 2013-04-10T02:44:54Z 2013-04-10T18:59:20Z "Line 263: {{{ switch ( $token ) { case 's' : if ( '""' !== $data[$length-2] ) return false; case 'a' : }}} Need ""break"" after ""return false"", because return happens only if condition met. Otherwise - falls to case 'a' " tivnet Future Releases 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 Future Releases 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: {{{
here goes html

bis

', 'after_title' => '

$title

Heading

Edit Properties

Roles

Capabilities assigned to the role of ' . $name. '

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