A Sandbox » Page not found

`, `

` and other tags, all attributes should be made available too. `role` should be added to the required tags falling under `$allowedposttags`. Go through the link for more information on [http://www.w3.org/wiki/PF/XTech/HTML5/RoleAttribute roles]." aniketpant Next Release 24197 wp_localize_script() doesn't work for jquery handle General trunk normal major 3.6 defect (bug) new dev-feedback 2013-04-25T20:23:59Z 2013-05-22T17:27:12Z "Here's another odd bug introduced by WP 3.6 latest development version. I'm using the following code: [http://snippi.com/s/s058ms7] In WP 3.5.1 everything worked as it should, and wp_localize_script returned the ""icy_ajax"". Now, in 3.6-beta1-24067 , I get the following error in my console: ReferenceError: icy_ajax is not defined Just try and test it and let me know of any solution :-) " IcyPixels Next Release 24202 Self-explanatory argument values for new media functions Media trunk high major 3.6 enhancement new dev-feedback 2013-04-26T13:14:52Z 2013-05-17T19:43:58Z "We've introduced a bunch of functions, some with a relatively long list of arguments, which accept booleans: {{{ function get_content_media( $type, &$content, $html = true, $remove = false, $limit = 0 ) function get_embedded_media( $type, &$content, $remove = false, $limit = 0 ) function get_content_audio( &$content, $html = true, $remove = false ) function get_embedded_audio( &$content, $remove = false ) function get_content_video( &$content, $html = true, $remove = false ) function get_embedded_video( &$content, $remove = false ) function get_content_images( &$content, $html = true, $remove = false, $limit = 0 ) function get_content_image( &$content, $html = true, $remove = false ) function get_content_galleries( &$content, $html = true, $remove = false, $limit = 0 ) function get_post_galleries( $post_id = 0, $html = true ) function get_post_gallery( $post_id = 0, $html = true ) function get_content_chat( &$content, $remove = false ) function get_content_quote( &$content, $remove = false, $replace = '' ) function get_content_url( &$content, $remove = false ) }}} I wonder if we can convert them to use arrays instead for future-proof changes, or at least switch from booleans to self-explanatory values, per our [http://make.wordpress.org/core/handbook/coding-standards/php/#self-explanatory-flag-values-for-function-arguments coding standards]. Otherwise, we might fall into a trap of `submit_button()`: #20492. " SergeyBiryukov Future Releases 24251 Reconsider SVG inclusion to get_allowed_mime_types Upload normal minor Awaiting Review enhancement new dev-feedback 2013-05-02T19:36:57Z 2013-06-14T19:08:54Z "There are some who think SVG should be included in core as an allowed mime type. Makes fine enough sense to me, since there is a good argument for it, and we have support for WordPerfect documents...so there's that. Related: #20990" JustinSainton Next Release 24264 Post Formats - Gallery Format: the_remaining_content still contains the gallery Post Formats trunk normal normal 3.6 defect (bug) new dev-feedback 2013-05-04T20:15:31Z 2013-05-06T19:31:39Z "If you use the_post_format_gallery() along with the_remaining_content(), the gallery will be displayed twice. As far as I see, the only way to output a gallery separately from the rest of the post content is to use get_content_galleries(): {{{ $post_content = get_the_content(); $gallery = get_content_galleries( $post_content, true, true, 0 ); echo $gallery[0]; echo apply_filters( 'the_content', $post_content ); }}} This differs from the implementation for audio, video and images, as the_remaining_content() strips the media from the post content before display. the_remaining_content() should do the same with galleries." Frank Klein Future Releases 24334 """edit_form_after_title"" and ""edit_form_after_editor"" hooks wrapper optional?" Administration trunk normal normal Awaiting Review enhancement new dev-feedback 2013-05-14T10:51:21Z 2013-05-14T18:38:39Z "Would it be possible to make the `DIV.edit-form-section` wrapper applied around `edit_form_after_title` and `edit_form_after_editor` hooks in post/page edit screen optional in WP3.6? Or create additional non-wrapped hooks besides? [http://core.trac.wordpress.org/browser/trunk/wp-admin/edit-form-advanced.php#L462] [http://core.trac.wordpress.org/browser/trunk/wp-admin/edit-form-advanced.php#L502] These wrappers were actually introduced in WP3.6, the WP3.5 version was without them. '''Explanation of what I do:''' * `edit_form_after_title` hook - I output UL list of tabbed interface here and open the first tab content DIV * `edit_form_after_editor` hook - I close the first tab content DIV and output the other tab content DIVs The first content DIV is always a visual editor. But as you can see, when I open the DIV in one hook and closing it in another one, this was working fine in WP3.5 as no wrapper was added to those hooks. Once there is a wrapper, it obviously messes up the HTML and closes divs prematurely. This is causing issues obviously for tabbed interface. Screenshot: [http://awesomescreenshot.com/09915rzc37] Ticket started on Alpha/Beta support forum: [http://wordpress.org/support/topic/wrapper-of-edit_form_after_title-and-edit_form_after_editor-hooks-optional] Thank you!" lemmonaid Next Release 24348 Consider the post thumbnail in get_the_post_format_image() Post Formats trunk normal normal 3.6 enhancement new dev-feedback 2013-05-15T21:39:45Z 2013-05-25T00:06:30Z "`get_the_post_format_image()` makes valiant attempts to locate an image for use with a post of image post format. The function first attempts to find suitable data in the post format meta field. If no image is found there, it grabs the first attached image. Finally, if all else fails, it will look in the post content to use the first image inserted in the content. I think that the function should also consider grabbing the post's featured image as a fallback. I would prioritize this right after the post format meta data. I think this is important in that it seems that using the featured image was a common practice for adding an image to a post of image post format. I would think that this would help improve back compat for themes that have used this practice. Moreover, since grabbing an attached image or an image inserted in the post content is merely a guess at the right image to use for the post, I think that using the featured image is a better guess than either of these methods." tollmanz Future Releases 24354 get_cat_id() fails with category names containing ampersand Taxonomy 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-05-17T08:25:08Z 2013-05-17T10:07:10Z "{{{ echo get_cat_id('News'); results in 3 (as expected); echo get_cat_id('Test OtherName'); results in 8 (as expected); echo get_cat_id('Test&OtherName'); Results in 0 echo get_cat_id('News & Media'); Results in 0 }}} All the category names were created in the Category Edit page, category names were copied from the text box directly into the code to allow no formatting issues. I tracked the code to get_term_by and I think the ampersand in category name screws up possibly after being added into the prepared SQL statement. " Kenshino Future Releases 24368 Renaming feature for wp-includes Filesystem 3.5.1 normal normal Awaiting Review feature request new dev-feedback 2013-05-19T18:24:16Z 2013-05-20T06:37:10Z Currently it is possible to rename wp-content to anything you want. WordPress has a definition built in for wp-includes, that is WPINC, however, this definition isn't used in about 15 - 16 core files preventing it from being changed (For example, some CSS doesn't load for the admin bar). I have added the files that I have changed to allow this to work, to work add a definition for WPINC to wp-config with the name of your wp-includes folder without and slashes. Without the definition it just uses the standard wp-includes. JoeIzzard Next Release 24388 Optimize revisions diff loading - especially when many revisions Revisions trunk normal critical 3.6 defect (bug) new dev-feedback 2013-05-22T20:16:48Z 2013-05-24T23:16:21Z "Currently viewing the revisions page chokes the browser when there are many revisions (say over 50) - even with a lower number the browser seems overwhelmed by the numerous ajax requests fired to load the comparison diffs. * limit the number of simultaneous ajax requests * group diff requests to optimize loading and limit total number of calls when there are many revisions * caching for diff calculations " adamsilverstein Future Releases 24392 Customizer: Display section descriptions like sidebar descriptions Appearance normal normal Awaiting Review enhancement new dev-feedback 2013-05-22T22:05:58Z 2013-05-23T07:07:05Z "When adding a section to the Customizer, it offers the possibility to add a description of this section. Currently this description gets output as in a title attribute to the h3 headline of this section - and is completely hidden and gone. :( Or did you know we have a four line description of the navigation section? It would be awesome if we could move that more in the user's view, maybe like how we currently do it for widget sidebars?" obenland Next Release 24404 Allow get_the_post_format_image to return image without link Post Formats trunk normal normal 3.6 enhancement new dev-feedback 2013-05-23T20:34:41Z 2013-06-11T18:28:17Z "When a user adds a link to an image post in the new post format UI, `the_post_format_image()` and `get_the_post_format_image()` functions will always return the image HTML wrapped in the link. There are a number of cases in which a theme or plugin author may want to get the image without the link. For example, the author might want to wrap both the image and the title in a link. Having a link wrapped around the image complicates this. I think we should either add a new parameter that allows the image to be returned without the link, or create two functions: one that returns the image with the link and one without the link. I personally find it a little misleading to use a function called `the_post_format_image()` and get an image wrapped in a link. Separating functions that allow for returning just the image and the image with the link is important for flexibility. I think that wrapping the image in a link is making a decision that the developer should make and is limiting the developer without good reason. This will lead to some weird workarounds that will decrease the stability of community code. Having two functions instead of one does not increase complexity, yet it improves the flexibility of the API. I'm happy to work on this if people think it's worth adding." tollmanz Future Releases 24408 HTTPd Error Log: body.xml:1: parser error : Document labelled UTF-16 but has UTF-8 content XML-RPC 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-05-24T03:10:11Z 2013-06-09T16:51:09Z "I run a few pt_BR blogs and I regularly see ""body.xml:1: parser error : Document labelled UTF-16 but has UTF-8 content"" in the Apache error log I finally found a clue why this happens: (because) ""...é and á characters which are not valid UTF-8 according to Xerces. I can’t send the text as UTF-16 because XML-RPC doesn’t allow it – it only allows USASCII. So I think I have to find any non USASCII characters and convert them to their XML Hex equivalent."" (from http://tersesystems.com/2003/04/29/xml-rpc-encoding-of-utf-16) So the proper handling seems to be ""find any non USASCII characters and convert them to their XML Hex equivalent.""" crashnet Future Releases 24442 Visit theme/plugin/author homepage vs Visit theme/plugin/author site Text Changes normal normal Awaiting Review enhancement new dev-feedback 2013-05-28T16:08:11Z 2013-05-28T21:58:47Z "See: 1) http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-ms-themes-list-table.php#L334: '''Visit theme homepage''' and '''Visit Theme Site''' 2) http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-plugins-list-table.php#L418: '''Visit plugin site''' (2 same strings) 3) http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/plugin.php#L160: '''Visit plugin homepage''' 4) http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-plugins-list-table.php#L414, http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/plugin.php#L163, http://core.trac.wordpress.org/browser/trunk/wp-includes/class-wp-theme.php#L654: '''Visit author homepage''' These strings should be consistent but I'm not sure whether to go with '''site''' or '''homepage'''. I also suggest remove the redundant {{{title}}} attribute in 2). FYI, the strings only appear in the files that listed above." zeo Next Release 24449 Attachment display settings in the Media Library are ignored for audio and video inside 'Standard' post format and pages Post Formats trunk normal normal 3.6 defect (bug) new dev-feedback 2013-05-29T13:02:21Z 2013-06-18T15:11:01Z "Sometimes both clients and I will upload audio and video files through the media uploader and link them to Attachment Pages so that people can do the old right click -> Save link as... thang. Currently in trunk the Link to Attachment Page in the ""ATTACHMENT DISPLAY SETTINGS"" is ignored for audio and video and the new [audio] and [video] shortcodes are applied no matter what is selected. I can understand that this is desirable behaviour in both the Audio and Video post formats to reduce confusion for the user but I think it would be acceptable to remove those shortcodes in the Standard post format and for Pages (and CPTs) as well. '''i.e. Give the user some control when acceptable.''' To reproduce this upload either an .mp3 or .mp4 through the media uploader in a Standard Post format or in a Page and under ""ATTACHMENT DISPLAY SETTINGS"" choose ""Link To Attachment Page"" and the shortcodes for audio and video will be apply so that MediaElement.js will be triggered. I'm not sure if this is the desired behaviour so I'll tag this as a 2nd-opinion." sennza Next Release 24475 The empty pattern attribute causes Webkit (Chromium 25) to style the URL and Email HTML5 form fields always with :invalid styles. Comments trunk normal normal 3.6 defect (bug) new dev-feedback 2013-05-31T23:20:55Z 2013-06-01T09:09:42Z "Chromium Version 25.0.1364.160 Ubuntu 13.04 (25.0.1364.160-0ubuntu3) `input type=""email"" pattern=""""` `input type=""url"" pattern=""""` This code is generated for the HTML5 form in Wordpress. I am using bootstrap 3.0 CSS and it styles the `input:focus:invalid:focus` and `input:focus:invalid` with a red border and text. The issue is using the empty pattern variable the browsers marks everything as invalid. I simply removed the `pattern=""""` and the validation works, the browser then uses default pattern and the styles get removed as soon as the input in that fields are valid. I not tested it with manual pattern that will of course work as well. Not sure what the reason is you used empty pattern, I am new to this thing, but you might want to remove it or include some default pattern to be able to correctly validate the Email and URL." nico23 Future Releases 24478 The `theme_action_links` filter passes different arguments in different places. Themes 3.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-06-01T16:45:54Z 2013-06-09T05:26:45Z "Since r20029 at least, there has been an inconsistency in how core uses the `theme_action_links` filter. Ordinarily, it's used like this: http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-themes-list-table.php#L151 `$actions = apply_filters( 'theme_action_links', $actions, $theme );` with $theme being a WP_Theme object. However, in the Multi Site theme admin panel, it's used like this: http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/class-wp-ms-themes-list-table.php#L287 `$actions = apply_filters( 'theme_action_links', array_filter( $actions ), $stylesheet, $theme, $context );` which means that for any module to successfully function in both contexts, it needs to do the following: {{{ function theme_action_links_filter( $actions, $theme, $ms_theme = null ) { if ( is_a( $ms_theme, 'WP_Theme' ) ) { $theme = $ms_theme; } // stuff with $theme return $actions; } }}} as can be seen in this changeset for a practical implementation: http://plugins.trac.wordpress.org/changeset/721178 If we're using a filter in core, I feel that we should be consistent with what sequence parameters are being passed to it, or at least leave a comment to devs giving them a heads up that they need to account for the other sequence." georgestephanis Future Releases 24523 "The ""profile"" attribute on the head element is obsolete." Template 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-06-06T20:07:25Z 2013-06-09T16:53:22Z "if you try to validade an HTML5 doc, as HTML5, via validator.w3.org, you get the following error: {{{ Validation Output: 1 Error Line 3, Column 39: The profile attribute on the head element is obsolete. To declare which meta terms are used in the document, instead register the names as meta extensions. To trigger specific UA behaviors, use a link element instead. }}} comes from /wp-includes/theme-compat/header.php. '''Looks like the profile should be registered using META.'''" crashnet Future Releases 24541 wp_is_mobile() includes tablets Administration 3.4 normal normal Awaiting Review defect (bug) new dev-feedback 2013-06-08T12:41:08Z 2013-06-08T15:02:43Z "Android tablets have ""Android"" in user agent and Android mobile phones have ""Android"" and ""Mobile"". I use this to distinguish what is tablet and what is a mobile phone. http://core.trac.wordpress.org/browser/tags/3.5.1/wp-includes/vars.php" Looimaster Next Release 24542 Twenty Thirteen: Respect post password settings in image attachments? Bundled Theme trunk normal normal 3.6 defect (bug) new dev-feedback 2013-06-08T19:23:38Z 2013-06-12T21:14:59Z "In case the image attachment's parent post is password protected, we probably shouldn't display the image. Does someone have a better idea than to ask for the parent's post password? Downside: Since images can now be part of multiple galleries, it might happen that certain images in a gallery require a password because it has a different parent post (that is password protected), while others do not. Thoughts?" obenland Next Release 24547 """Go to All %s"" string not ready for i18n" I18N trunk high major 3.6 defect (bug) new dev-feedback 2013-06-09T18:07:29Z 2013-06-10T13:12:13Z "The ""Go to All %s"" string ([http://core.trac.wordpress.org/browser/trunk/wp-admin/includes/post.php#L1214 location] is marked with %s being any post type: ""Posts, Pages, etc."". As it is, translators cannot do a direct translation of it: as with any ""any post type""-related string, it should be known that depending on the language, some post types can have a ""gender"", and therefore cannot use the same sentence structure. For instance, in French, Post is Article, which is masculine, when Page is Page, which is feminine. Translation for this string would then either be ""Aller à tous les articles"" or ""Aller à toutes les pages"". Either the string is reworked, or translators should be advised to use a sentence structure that works for any content type." xibe Future Releases 24548 _wp_menu_item_classes_by_context assumes $queried_object->ancestors is an array Menus normal normal Awaiting Review defect (bug) new dev-feedback 2013-06-09T19:08:16Z 2013-06-09T19:08:16Z "Recently, on a site using [http://wordpress.org/plugins/cpt-onomies/ CPT-onomies], I ran into an interesting error with _wp_menu_item_classes_by_context(). In this function, when setting the parent class, there is a large if statement that assumes that `$queried_object->ancestors` and `$possible_taxonomy_ancestors[ $parent_item->object ]` are arrays." wpsmith Future Releases 24549 Follow the WP Handbook Standard, and change The Loop of Core Themes to Use Brackets Bundled Theme trunk normal normal Awaiting Review enhancement new dev-feedback 2013-06-10T04:32:26Z 2013-06-17T08:19:51Z "This started as a discussion over a pull request to change the if-endif statements to brackets in the template files for Easy Digital Downloads. After lengthy discussion on that [https://github.com/easydigitaldownloads/Easy-Digital-Downloads/pull/1194 Github issue], and even more discussion in our dev chat, @pippinsplugins published [http://pippinsplugins.com/please-do-not-use-curly-brackets-in-template-files/ a post] about his beliefs on the matter.http://techcrunch.com/ The reason for this Trac ticket is to request the core's themes, which (to date) are 2010, 2011, 2012, and in 3.6 trunk, 2013, to use braces instead of if-endifs in The Loop. At the very beginning, this may seem like a trivial matter. Instead it's far from it. This is actually a pretty deep rooted issue, caused by the ambiguity of the presence of endifs in Core, when combined with the discouragement from using them in the Codex. The problem lies in that, (as Pippin's belief is) that most new WordPress devs first learn coding by studying their theme's loops files. For most users of WordPress, either their theme is one of the aforementioned core themes, or contains a loop based on one of them. A plugin author, such as the EDD devs, then make template files for our plugins, which are intended to be edited by said users. A good place to start, would be advantages to using braces over if-endif. * Braces are fully supported by most IDEs. Most IDE's can find the corresponding open or close brace based on the highlighting of another one. Importantly, this includes IDE's that said new developers, might be more inclined to use, such as Dreamweaver, or similar. However, if-endifs are not supported in this manner, but in only a handful of IDE's. * New developers will understand braces better than if-endif. Whether from their background in CSS (where braces contain rules), mathematics, or otherwise, braces are a symbol of a containing element. From Pippin's post, it also seems the vast majority of developers also prefer braces. * It's shorter. Trivial maybe, but still slightly shorter. * It's standard. The [http://make.wordpress.org/core/handbook/coding-standards/php/#brace-style WordPress Code Handbook] states to use braces. If braces are the standard, they should be used throughout core, and particularly not in important, more prominent areas like The Loop of core themes. Several other prominent open source projects follow the same guidelines (ex [https://drupal.org/node/318 Drupal] etc etc). * Save users time learning both systems. Currently, if a user looks at The Loop, they learn endif. If they then proceed to other template files of core themes, or to plugin files, they then need to learn brackets. Making one way the Core's preferred method would cut the amount of time down for a new developer to learn the control logic (eliminate the need to learn endif). The attached patch/diff replaces all if-endif usages with braces in 2010, 2011, 2012, and 2013. " chriscct7 Next Release 24555 Twenty Thirteen: First image in featured gallery can be blurry if in landscape Bundled Theme trunk normal normal 3.6 defect (bug) new dev-feedback 2013-06-10T18:20:53Z 2013-06-12T22:54:03Z "[https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-06-10&sort=asc#m625858 Reported in IRC], if a landscape oriented image happens to be the first image in a featured gallery, it appears blurry. Since the medium image size does not crop, the image is most likely not 300px high. This causes the image to be magnified and to appear blurry. We previously discussed the issue of the best image size to use in IRC, I couldn't find the log in a reasonable amount of time though." obenland Future Releases 24567 Add help to media modals Help/About 3.5 normal normal Awaiting Review enhancement new dev-feedback 2013-06-12T08:06:29Z 2013-06-12T16:52:29Z They are far from simple screens but there is no help available for them. mark-k

"" . $args['title'] . ""

Static menu name