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 22272 shortcode_unautop() Doesn't Account for Opening/Closing Shortcode tags each Being on Their Own Line Shortcodes 3.4.2 normal normal Awaiting Review defect (bug) new 2012-10-24T17:54:22Z 2012-10-24T17:54:22Z "The shortcode_unautop function does not appear to account for when the opening and closing shortcode tags are put on separate lines from the paragraph they are surrounding.
For example: the following is after wpautop() adds the paragraph tags.
{{{
[cool_shortcode]
A paragraph about something you should know.
[/cool_shortcode]
}}} I would expect that shortcode_unautop would remove the paragraph tags from around both the opening and the closing shortcode tags. Instead it treats it all as if the entire thing were in one paragraph. Resulting in the following code being output. {{{ [cool_shortcode]A paragraph about something you should know.
[/cool_shortcode] }}} " bonnerl Future Releases 20077 shortcode_parse_atts should not force arguments to be lowercase General normal normal Awaiting Review defect (bug) new close 2012-02-19T19:21:33Z 2012-02-20T17:42:42Z "Inside wp-includes/shortcodes.php, the shortcode_parse_atts() function forces shortcode arguments to be lowercase. So if your shotcode had something like [my_shortcode MyVar=123], then your code that uses something like ""print $MyVar;"" fails... you have to use ""$myvar"" instead. This is counter-intuitive. I understand that there needs to be some restrictions on what is a valid parameter name (see http://core.trac.wordpress.org/ticket/9405), but I think it makes the most sense that the parameter names can correspond to any valid PHP variable name; PHP variables ARE case-sensitive, so this arbitrary restriction of forcing lower-case parameters seems like the incorrect approach." fireproofsocks Future Releases 23694 Shortcode attributes mess up html strings Shortcodes 3.5.1 normal normal Awaiting Review defect (bug) new dev-feedback 2013-03-05T15:15:48Z 2013-03-07T03:42:37Z "{{{ [shortcode attribute=""some HTML""/] }}} produces: {{{ some HTML
}}}" prometh Future Releases 22781 setUserSetting cannot handle hyphens General 2.7 normal normal Future Release defect (bug) new early 2012-12-06T06:18:39Z 2012-12-06T18:25:43Z "sanitize_key() can, setUserSetting should be able to as well. It's not that sanitize_key() plays a role, but it sets expectations for what is allowed in keys across core. Both keys and values should be able to accept a hyphen. The post-thumbnail image size cannot be remembered, for example, if it is added to image_size_names_choose." nacin Future Releases 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 Future Releases 16413 Settings page needs HTML refactoring and UI improvements nacin* Administration 3.1 normal normal Future Release enhancement accepted 2011-01-30T20:22:09Z 2013-01-03T19:25:28Z "The settings pages haven't had much attention or improvement in a while. We need to refactor the HTML on the settings pages, as they are still using tables instead of divs. We also want to make some minor UI improvements including: - clearer differentiation between option groupings - using consistent text styles for descriptions and links (including the time zone/date format comment) - restructure for better readability Comment if you have any other" chexee Future Releases 18307 Settings mixed with WP installations sharing same database Administration 3.2.1 normal major Awaiting Review defect (bug) new 2011-07-31T21:22:09Z 2012-02-20T20:27:18Z "I have WP website installed on main domain, and another WP installation on subdomain. These two share users tables. When I rearrange admin dashboard widgets, or post editor widgets in one installation, other one uses same settings making the mess due to differences in available elements (different plugins installed). All WP settings cookies are saved without proper setting of the cookie path/domain, and all sub-domains use same cookies as the main domain does. Cookies have to have full domain set to avoid mix-up like it happens now. Same issue happens with Opera, Chrome and Firefox. Milan " GDragoN Future Releases 13548 Settings API to include user options westi Plugins 2.7 normal normal Future Release enhancement new 2010-05-26T07:42:52Z 2013-01-03T19:25:19Z "Hi, I've reworked all of my plugins to build upon the [http://codex.wordpress.org/Settings_API new Settings API]. The handling and security are great. As far as I understand, the Settings API can't be used for user options. - What do you think about an extension of {{{ register_setting }}} & Co. to reflect user options? Greetz, Berny" neoxx Future Releases 15237 Settings -> Permalinks blank on PHP 5.3.2 Permalinks 3.0 normal major Awaiting Review defect (bug) new 2010-10-28T12:30:07Z 2011-04-26T13:34:11Z "I've setup a brand new wordpress with a fresh db for testing this. To replicate this, install WordPress in an environment with PHP 5.3.2: # run through the standard installation # login # click Settings -> Permalinks # Observe the bleak, white, cold content area looking back at you Works fine in this scenario when I revert to PHP Version 4.4.9. I tried enabling debug mode, then in php.ini setting display_errors = On and ERROR_REPORTING = E_ALL but still couldn't view any output on the page in question. I'm attaching the phpinfo for the broken setup to this bug." EdwardIII Future Releases 18488 set_transient crashes when value parameter is a SimpleXMLElement object Cache 3.2.1 normal normal Awaiting Review enhancement reopened 2011-08-19T18:58:02Z 2012-09-01T18:03:16Z "I have been developing a plugin that obtains information about high and low tides in the UK. The data is obtained from another site as a SimpleXMLElement. I found that when I passed a value to set_transient that had been assigned directly from the SimpleXMLObject then it was being received as an object and somewhere in the innards of the function the routine crashed. My workaround was to cast the assignment. e.g. this failed {{{ $title = $channel->item->title; $store = '1'; $secs = bw_time_of_day_secs(); $secs = 86400 - $secs; $set_transient( ""bw_tides_title_"" . $store, $title, $secs); }}} but change line 1 as below and it works $title = '''(string)''' $channel->item->title; Two questions therefore. 1. Am I misinterpreting the documentation that says I don't need to serialise the value? What does mixed actually mean. 2. Does set_transient have to crash when the parameters are wrong? The problem is completely reproducable. I now have a working solution so I don't need a fix right now. I just want to understand. Herb " bobbingwide Future Releases 14087 Set up team to evaluate web-hosting providers for WP.org recommendations WordPress.org site normal normal WordPress.org enhancement new 2010-06-25T13:47:32Z 2010-07-17T14:39:18Z "The problem is simple to describe: When setting up a CMS-based website, two of the most critical—if not the two most critical—decisions are: * publishing platform * web host For the first you can pick at random among the best-known offerings and you won’t go much wrong. (Or you can pick the most popular one, and, in most cases, you will have made the best choice! :-D) But the second is different — or so my little experience tells me: Fame and familiarity do not seem to be directly correlated with quality in the case of shared web-hosting, which is the best type of hosting for the majority of WP users. And that’s unfortunate, because bad web hosting can ruin the experience of web publishing. In addition, evaluting web hosts is not easy for a single individual, even for individuals who have the technical understanding, because it takes time and also money. We, the people involved with WordPress development, are in a better position to offer some insight into the problem: We are many, we have collective knowledge, and also collective experience. So, here is my idea: * Set up a team * Set up a set of criteria * Start evaluating services for a period of two or three months * Publish the final recommendations on the WP.org page (along with the criteria used) What do you think?" demetris Future Releases 16301 set limits to nesting of menus Menus normal normal Future Release enhancement new dev-feedback 2011-01-19T16:21:10Z 2011-01-20T20:12:38Z It would be great to be able to limit/control the nesting depth of menus. I'm using menus to let my editors control where posts show up in various spots in our theme, and don't want them to accidentally nest a link deeper than it should be. alxndr Future Releases 23531 Separate tests into unit / integration / ... directories Unit Tests trunk normal normal Awaiting Review enhancement new 2013-02-19T15:51:16Z 2013-02-19T15:51:16Z "To improve the speed how tests can be run - especially the unit-tests - I suggest to divide tests into sub-directories, for example: ''unit'' - for unit tests[[BR]] ''integration'' - for integration tests[[BR]] ''functional'' - for functional tests Right now all tests are roughly labeled as ""Unit-Tests"" even they are not unit-tests per-se, e.g. some of them interacting with the database or the file-system. Background: [http://stackoverflow.com/q/4904096/367456 What's the difference between unit, functional, acceptance, and integration tests?]" hakre Future Releases 13372 Separate Image sizes for different post types Media normal normal Future Release enhancement new close 2010-05-13T07:59:07Z 2013-01-03T16:14:23Z Would be nice, especially moving forward with custom post types to have the ability to set different image sizes using an additional parameter of `add_image_size()` for different post types: Page, Post, and Custom. brandondove Future Releases 15977 Send the Locale in Plugin/Theme Update Check Requests nacin* Upgrade/Install 3.1 normal normal Future Release feature request accepted early 2010-12-25T20:59:43Z 2013-01-22T00:00:56Z "Currently, we send locale (and other information about installation) only in wp_version_check and not in wp_update_plugins and wp_update_themes. Since we still don't know how system for plugins/themes localization will work, I propose that we send this from 3.1. Why? As said above, there is no definitive agreement on how will localization system work, but it is possible that system wont require changes in core, ie. be same or similar to one I [http://wppolyglots.wordpress.com/2010/12/10/proposal-for-plugins-localization-system/ suggested] over at Polyglots. In that case localization system will be made independently what means that it'll can start working before 3.2 version. If we don't send locale for plugins/themes, we will need to wait for 3.2 even though that wont be significant change. In theory, plugin/theme developers could also benefit if alongside locales, we would send all information we send in wp_version_check and later show them as are plugin versions shown now. I know that is very late for this change but issue with plugin localization tool has been ignored for a very long time as I described in my post mentioned above in more detail." dimadin Future Releases 20225 Self-contain wp-includes/load.php, wp-includes/plugin.php Performance 3.3.1 normal normal Awaiting Review feature request new 2012-03-13T10:50:01Z 2012-04-01T09:44:46Z "I'm trying to write a high-performance plugin. I still want the whole of WP to be used by the admins, and the main part of WP to still be used by most user workflows, but I want certain end users to instead be using an alternate controller, instead of /index.php, when they're doing certain things. This new controller I'll write will use a couple of the core files, but skips most for the goal of increased performance. The proposed core files to re-use are: * wp-includes/version.php * wp-includes/load.php * wp-includes/plugin.php * wp-includes/wp-db.php * wp-includes/class-wp-error.php However, wp-includes/functions.php is a can of worms, that if I included, would require me to include many other files, and it spiders out from there. What would be better is if the following functions that wp-includes/load.php and wp-includes/plugin.php require be moved into those files from the functions file. Specifically: * wp_die() * validate_file() * stripslashes_deep() * add_magic_quotes() * _doing_it_wrong() * trailingslashit() If they aren't, I'll have to copy-paste them into my custom controller, maintaining separate versions of them (less than optimal). Of course, this process still requires me to write my own simpler versions of many more complex functions: * wp_cache_init() * wp_cache_close() * wp_get_active_network_plugins() * is_blog_installed() * get_option() * update_option() but that's completely acceptable. Moving those first 6 functions from the functions file to the load and plugin files would not negatively affect core, but would positively affect plugin authors' abilities to write high-performance plugins." scottconnerly Future Releases 12004 Select Sidebar when adding Posts/Pages Administration 3.0 normal normal Future Release feature request new 2010-01-25T13:26:16Z 2010-01-25T23:28:01Z "Hey all, I think it would be a cool feature to be able to create sidebars in WP, and then when creating a page you can choose that specific sidebar. I think that this can be accomplished by using the ''Parent'' page technique of selecting if the Page has a Parent and if so which one. Can we develop an option to choose a Sidebar created in the Widgets panel? Cheers, Aron ps: if my help is needed ( im good at design, not coding ) please contact me: info@zipyourmix.com ;)!" lsddesign Future Releases 13509 Searching doesn't return Private results to logged in users with read_private_ permissions ryan Post Types 2.9.1 normal normal Future Release defect (bug) new 2010-05-24T00:31:11Z 2010-11-13T08:01:18Z "When you do a search with these requirements...[[BR]] - You are a registered user.[[BR]] - You are logged in.[[BR]] - You have '''''read_private_posts''''' permissions. ... you expect seeing in the results those Private posts that contains your query's terms. But you end up with showing only the ones that belongs to you. I think the bug is in these lines: {{{ if ( is_user_logged_in() ) { $where .= current_user_can( ""read_private_{$post_type_cap}s"" ) ? "" OR $wpdb->posts.post_status = 'private'"" : "" OR $wpdb->posts.post_author = $user_ID AND $wpdb->posts.post_status = 'private'""; } }}} As '''''$post_type_cap''''' is set to ""any"" when you do a search, the conditional expression always fails as it's asking for this: {{{ current_user_can( ""read_private_anys"" ) }}} ... and ends up always in the second part of the conditional expression. That is: {{{ "" OR $wpdb->posts.post_author = $user_ID AND $wpdb->posts.post_status = 'private'"" }}} Thanks." inbytesinc Future Releases 12477 Search with special characters and similar terms nbachiyski I18N normal normal Future Release feature request new 2010-03-02T17:42:46Z 2010-03-24T10:25:15Z "I did:Tried searching for terms Metis and Métis I saw:Those two searches turned up different sets of results. I expected:The same set of search results, or at least everything when I searched for Metis. Can search be smarter when special characters are involved?" mrroundhill Future Releases 22424 Search support threads for a particular theme/plugin WordPress.org site normal major WordPress.org enhancement new 2012-11-12T19:09:45Z 2012-11-12T19:12:55Z "A lot of duplicate support threads for themes/plugins could be avoided if users had a way to search through existing threads only for that particular theme/plugin. For example, when I'm on http://wordpress.org/support/theme/p2 there could be a search box at the top that would only look through those topics." scribu Future Releases 20008 Search Results Paging Doesn't Work on Lighttp 404 Handler General 3.3.1 normal major Awaiting Review defect (bug) new 2012-02-10T07:01:47Z 2012-02-10T23:02:55Z "Quote from http://core.trac.wordpress.org/ticket/11723 I'm running Wordpress on lighttpd, using server.error-handler-404 = ""index.php"", all the pretty permalinks work perfectly. However, when doing a search, i only get the first results page, that is mysite.com/?s=query works but '''mysite.com/page/2/?s=query''' doesn't (i get shown the home page saying it's on page two of it). Paging on categories, archives and tags works as expected too. I believe this is a Wordpress error, as the variables are being correctly passed to the script. Strangely '''mysite.com/index.php/page/2/?s=query''' or '''mysite.com/?s=query&page=2 works''' as expected, i have tried exploring the code but i don't really know about the internals of the wordpress core. I tried the solution but not working for me. {{{ function wp_fix_lighttpd() { //checks if URI has parameter and sets globals if (isset($_GET) && isset($_SERVER['QUERY_STRING'])) return; $donga = explode('?', $_SERVER['REQUEST_URI'], 2); if (count($donga) > 1) { $_SERVER['QUERY_STRING'] = $donga[1]; parse_str($donga[1], $_GET); $_REQUEST = array_merge( (array)$_GET, (array)$_REQUEST); } } }}} I hope anyone can help me fix this. Thanks. " anniyan07 Future Releases 18851 search form in edit.php should keep parameters it does not understand Administration normal normal Awaiting Review enhancement new 2011-10-03T21:48:17Z 2011-11-15T11:29:40Z "the component is class-wp-list-table.php. if you carry along some kind of status in the url in the post list (e.g. url=https://example.com/wp-admin/edit.php?post_type=post&my_status=""abcdefg"") the search field should not remove the parameter." ibotty Future Releases 9785 Search Enhancements -- consolidated ticket General 2.8 normal normal Future Release enhancement new 2009-05-10T23:54:34Z 2012-06-25T01:47:24Z "Closing the following as dups, pending ""the big search overhaul"" that may never come: - #5149 -- search everywhere (with committed patch) - #9230 -- search in post and pages and both - #5525 -- also search for posts with search query as terms (tags, cats, ...) - #5054 -- allow to negate keyword on search - #7394 -- assign greater weight to posts with search query in title - #7647 -- search in attachment descriptions" Denis-de-Bernardy Future Releases 15417 Search by Author on Install Plugins - requires inside knowledge WordPress.org site 3.0.1 normal normal WordPress.org enhancement new 2010-11-13T17:07:49Z 2011-02-19T01:19:08Z "If you search for plugins to install by author - say for example - Justin Tadlock - or - Tadlock - you get no results. If you are aware that ""GreenShady"" is Justin Tadlock - you get a long list of plugins (as you should) all listed as by ""Justin Tadlock"" This seems broken. " transom Future Releases 14749 Scrollbar position jumping in the Appearance->Editor newcontent textarea Editor 3.0.1 normal normal Awaiting Review defect (bug) new 2010-09-01T01:32:10Z 2012-11-01T05:14:52Z "As I am editing code in the Appearance Editor main textarea called newcontent, the scrollbar slider will jump upward to a new position moving the current line being edited down. On a vista machine using ie8 with wp3.0.1 and the 2010 theme, a single character stroke will move the scrollbar up 3 lines. On an xp machine using ie8 with wp3.0.1 and a custom theme, a single character stroke will move the scrollbar up 8 lines. Ocasionally the scrollbar will only move 1 line and every keystroke will bring the down. Pasting text can and often does bring the line being edited below the visible area of the textarea. It is very frustrating when it jumps around like this." Giant Slayer Future Releases 18943 Scroll back to previous editor position after post save/update Editor 3.2.1 normal normal Awaiting Review enhancement new 2011-10-14T10:23:05Z 2012-09-21T14:38:47Z "I work exclusively in html mode in the WordPress editor, but this probably applies to the visual mode too. When editing long(ish) posts it is really frustrating that the cursor position defaults to the beginning of the post after saving/updating. Constantly having to manually scroll back down to the previous cursor position after updating, soon gets really tedious. Focus always seems to be returned to the post title text box after saving/updating a post. It would be more intuitive to return focus to the main editor instead and automatically jump to the previous cursor position." dgwyer Future Releases 15833 Script concatenation fails to take external dependencies into account. General 3.0 normal normal Future Release defect (bug) new 2010-12-15T17:35:17Z 2011-01-16T02:19:59Z "Script concatenation places the concatenated script include first, before any scripts loaded separately. If one of the scripts in the concatenation relies on a script outside the concatenation the dependency order is ignored. When the dependencies are all internal to the concatenation things work fine (for example script4 relies on script3): * concat=script1,script2,script3,script4,script5 But when script3 is loaded externally, script4 will break: * concat=script1,script2,script4,script5 * external-script3 This becomes apparent if jQuery is loaded from a non-standard location (via a plugin or the [http://codex.wordpress.org/Function_Reference/wp_enqueue_script#Load_a_default_WordPress_script_from_a_non-default_location code from the Codex]) in that the visual editor fails to function correctly because source:/trunk/wp-admin/js/editor.js uses jQuery (which it fails to register as a dependency, see ticket:15830, but when I fixed that locally the results were the same). I'm working around this in [http://wordpress.org/extend/plugins/use-google-libraries/ Use Google Libraries] by globally disabling concatenation, but it would be nice if this was fixed. If possible, it would be nice if the loader was smart enough to do something like: * concat=script1,script2 * external-script3 * concat=script4,script5 Or at least flagged the script with the dependency as unsafe for concatenation: * concat=script1,script2,script5 * external-script3 * script4 " jczorkmid Future Releases 11009 screenshots of plugins from wordpress.org load over http instead of https when FORCE_SSL_ADMIN is enabled Upgrade/Install 2.9 normal normal Future Release defect (bug) new dev-feedback 2009-10-23T02:30:21Z 2010-02-05T13:52:39Z "1. Enabled FORCE_SSL_ADMIN in Wordpress on an appropriate host. 2. Use default settings in Internet Explorer 8. 3. Go to the plugin installation page. 4. Choose a plugin from wordpress.org to install. Actual Result: You get a mixed mode warning because the screenshots and possibly other content loaded from wordpress.org are loaded over http instead of https. Expected Result: Screenshots are loaded over https so that content is not mixed." brantgurga Future Releases 23410 Screenshots behaviour not same between /assets and /tags/xxx WordPress.org site normal normal WordPress.org defect (bug) new 2013-02-07T06:04:23Z 2013-02-17T04:32:27Z "Plugins screenshots have differing behaviour whether stored in /assets or /tags/xxxx folders in plugin SVN repository. * /tags/xxxx => scaled images with links to source images * /assets => scaled images without links Also, when loading a plugin for the first time recently, the screenshots didn't appear until after I added them to the /assets folder. I suspect something has changed there, as I had read that screenshots should fallback to stable tag/trunk folder. Examples: * [http://wordpress.org/extend/plugins/gravity-forms-dps-pxpay/screenshots/ Gravity Forms DPS PxPay] has /assets folder, screenshots don't link * [http://wordpress.org/extend/plugins/gravityforms-eway/screenshots/ Gravity Forms eWAY] has no /assets folder, screenshots link to source images" webaware Future Releases 17370 Screen options and meta box settings can lose per-blog meta box positions Users 3.1.2 normal normal Awaiting Review defect (bug) new 2011-05-10T21:13:37Z 2011-08-04T21:13:59Z "User preferences for admin interface appearance of the Dashboard and the Edit/Add New pages are stored in per-user options in wp_usermeta: closedpostboxes_$page, metaboxhidden_$page, meta-box-order_$page, and screen_layout_$page, where $page is one of 'post', 'page', or 'dashboard'. Users can customize the order of the Dashboard and editing meta boxes to better suit their workflow using the drag-and-drop AJAX interface to move the meta boxes into ordered columns and the Screen Options tab to show and hide the boxes. Many plugins add custom meta boxes to the Edit/Add New Post page. In a multisite installation, with different plugins active on different blogs, users who rearrange an Add New Post page on a blog with a custom meta box and then rearrange it on a different blog without that meta box will lose the position of the custom meta box. Blogs can have different features and workflows implemented, and having per user options for the appearance instead of per user, per blog options limits the ability of a user to customize the interface. The expected behavior for moving things around is that it changes on one blog, not on all blogs." jmdodd Next Release 23930 Screen option for post formats UI Administration trunk normal normal 3.6 feature request new needs-unit-tests 2013-04-03T18:28:10Z 2013-05-14T18:16:58Z "As discussed in IRC, there should be a screen option for the post format UI on the post editing screen. Nacin would like the UI to be hidden by default when the current theme does not support post formats and there are no non-standard format posts in the database. In this case, the UI would have to be enabled by the user. The UI would need to be automatically enabled when a theme that supports post formats is activated. Willing patchers, make yourself known. See also #23929 IRC logs: https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-02-18&sort=asc#m558297 https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2013-04-03&sort=asc#m588002" johnbillion Future Releases 23203 Scheduling Posts assumes GMT but UI uses local timezone (creating undesired scheduled posts) Date/Time 3.5 normal normal Awaiting Review defect (bug) new dev-feedback 2013-01-15T15:32:09Z 2013-01-16T13:16:59Z "I experienced an odd behavior when going to edit a page on a newly created site in a multisite environment. The site uses the New York timezone (GMT-5). When quick-editing the page, I changed the title and slug, but pressing ""Update"" set the page as ""Scheduled"" rather than leaving it ""Published"". This was very confusing, and took a while to figure out and then explain to the end user. It seems that although the date/time is shown in the UI in the current time zone, once submitted the form interprets the time as if it were in GMT. To the end user, it looks like the page should be published since the time shows what we thought was a 5 minutes ago. In reality, the time in the date field is not recognized as 5 minute ago but 4 hours and 55 minutes in the future. This is a problem in the full edit form for pages in this newly created site as well. When I go to edit the published time/date, the posted time in my timezone is shown. However, ''even if I hit 'Cancel' the ""Update"" button changes to ""Schedule""''." bananastalktome Future Releases 8368 Scheduling post time behavior and language refinements garyc40 Editor 2.7 low minor Future Release enhancement assigned early 2008-11-26T17:56:19Z 2013-01-22T17:38:00Z "On post editor, in publish module, at Publish Immediately-Edit. If click Edit, layer opens revealing the entry boxes for date and time of publication but still says Publish Immediately. Text should change to say ""Publish at:"" b/c it's weird if you change time and screen still says immediately until you click OK. Move OK button to the right side of module (submission buttons to the right as standard placement) with cancel to left (as with other places). If you start to type in an alternate time then hit cancel, it reverts to publish immediately, which makes sense. If you have already scheduled the publish time but you decide to change it and start typing a different alternate time, if you hit cancel it does not revert to your originally scheduled time, but to publish immediately. It should revert to your previously saved schedule time. Should have a separate link to revert to publish immediately. " jane Future Releases 10296 scheduled unpublishing / post expiration General low minor Future Release enhancement new 2009-06-29T06:02:33Z 2010-12-21T11:40:21Z Is there any particular blog-philosophical reason why this isn't yet possible in the core version while scheduled publishing has been a longstanding feature? As usual with such issues, client requested WP, but wants features that aren't easily supported in WP. There's a plugin called post-expirator (http://homeworker-directory.com/blog/how-to-make-your-wordpress-posts-and-wordpress-pages-auto-expire-on-a-chosen-time-or-date-with-post-expirator/) that does this in a way, but given WP's apparent increased use as a CMS I think this should be a core feature. youngmicroserf Future Releases 21773 Scheduled pages/posts should not appear in custom menus Menus 3.0 normal normal Awaiting Review defect (bug) new 2012-09-02T14:30:48Z 2012-10-23T22:03:31Z "When I add a '''scheduled page/post''' in a custom menu the page/post immediately appears in the front-end menu. I think these scheduled pages/posts should only be visible in the front-end navigation when their scheduled time is reached (as it is the case with automatic menus). Otherwise the ""Schedule"" functionality makes no sense with custom menus, especially for pages. Here is another forum post regarding this issue: http://wordpress.org/support/topic/custom-menu-support-for-scheduled-pagesposts" Lorangeo Future Releases 10834 schedule a revision to publish without unpublishing existing content Revisions normal normal Future Release feature request new 2009-09-23T20:49:27Z 2010-03-25T04:28:23Z "Boy, it sure would be swell if I could take an existing post/page, edit the content or add tags/custom terms, and then schedule that revision to be published later, without unpublishing the previous revision. Other people think it would be cool too... [[BR]] http://wordpress.org/support/topic/216545 [[BR]] http://wordpress.org/support/topic/226600 [[BR]] http://wordpress.org/support/topic/273701 [[BR]] http://wordpress.org/support/topic/273730 [[BR]] http://wordpress.org/support/topic/275932 [[BR]] " alxndr Future Releases 22003 Saving custom fields goes to post-new.php rather than post.php Administration 2.5 normal normal Awaiting Review defect (bug) reopened 2012-09-26T15:57:01Z 2012-09-26T19:19:54Z "Create a new post or page. Add a title and message. Add a custom field (click ""Add Custom Field"") The post is saved, but as you are taken to post-new.php rather than post.php, it looks as if your post has disappeared! All is well - it is actually saved - but it's confusing. Tested on 3.5-alpha-21989" curiousdannii Future Releases 11082 Saving an empty draft dumps user out to edit.php akhilasuram Editor 2.7 low minor Future Release defect (bug) assigned 2009-11-05T15:16:46Z 2012-12-13T20:09:23Z "ENV: wp trunk r12138 (2.9-rare) When a user starts up the editor for a new post and attempts to save a post with no title and no content, WordPress dumps the user back out to the list of posts in edit.php with no message or indication as to why this happened. You can edit the publish information (date, status, etc.), tags, and categories, but as long as there is nothing for either the post title or the post content, the behavior is the same. It's expected that a post with no content whatsoever wouldn't be saved (there's nothing there!), but would be nice if the behavior were easier to understand or explained why nothing was happening." markel Future Releases 22412 Save posts via Ajax Editor 3.4.2 normal normal Awaiting Review enhancement new 2012-11-11T12:18:09Z 2012-11-12T09:39:16Z "When editing a post/page (as with any other type of document) one of the primary benefits is the undo/redo feature. However, as soon as you update your changes you lose access to undo your previous keystrokes before the update. If you could save posts via Ajax then you would still be able to undo/redo post edits seamlessly. Perhaps there could be a toggle in general settings for this option, and have it enabled by default?" dgwyer Future Releases 19140 Save Menu Forces Sub-Menus (Child Menus) Back To Parent Menus in IE 9.0 Menus 3.2.1 normal normal Awaiting Review defect (bug) new reporter-feedback 2011-11-03T22:50:29Z 2012-02-29T20:32:43Z "The following issue appears in Internet Explorer 9.0.8112.16421 (current version). In Appearance->Menus for both primary and secondary menus, when you try to define a sub-menu by drag-n-dropping to the right in the menu definition box, it shows indented properly. However, when you click Save Menu, all sub-menus return to being parent menus. The only way to get the sub-menus to work was to edit them in another browser. In this case, I used Internet Explorer 7.0.5730.11 and it worked properly." webby 2 Future Releases 23423 sanitize_title() in dynamic_sidebar() restricts the use of specific characters for sidebar IDs Widgets 2.2 normal normal Awaiting Review defect (bug) new 2013-02-08T13:25:00Z 2013-02-19T05:20:42Z "In the dynamic_sidebar() function in wp-includes/widgets.php uses sanitize_title() on the given index when it looks for a sidebar with a name that matches the index. After that it leaves the index value sanitized making it impossible to use characters not allowed by sanitize_title() in a sidebar ID. By not overwriting the given index value with the sanitized version it would still be possible to use any character for the ID. To achieve this, lines 847-853 {{{ $index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $index ) { $index = $key; break; } } }}} should be replaced with {{{ $sanitized_index = sanitize_title($index); foreach ( (array) $wp_registered_sidebars as $key => $value ) { if ( sanitize_title($value['name']) == $sanitized_index ) { $index = $key; break; } } }}}" paulvandermeijs Future Releases 11738 sanitize_text_field() issue with UTF-8 characters hakre Charset 2.9.1 normal normal Future Release defect (bug) new 2010-01-06T07:39:11Z 2010-11-13T07:36:00Z "See Description #11528 Suggested patch does not take UTF-8 properly into account. Function has been degraded in the commit(s) [12499], [12501] to not support shift-spaces any longer. Details about preg_replace and UTF-8 as well as a proper suggestion to fix w/o degration [https://core.trac.wordpress.org/ticket/11528#comment:10 here]." hakre Future Releases 21421 Sanitize/remove admin page slug from admin menu CSS classes Administration normal normal Awaiting Review defect (bug) new 2012-07-30T11:26:15Z 2013-03-02T21:00:41Z "As I discovered when testing #21307, browsers won't parse a CSS class name with both underscores and hyphens. Instead, they handle it ''really'' badly. For example: `.toplevel_page_link-manager` will affect `body` in both Firefox and Chrome. Plugin page menu items have both an ID and class generated as such, which seems rather redundant. I propose either dropping the redundant and only partly functional CSS class or standardising the menu slug to produce a valid class name." kawauso 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 21281 "RTL wysiwyg ""padding""/""indention"" action is not works as expected." azaozz TinyMCE 3.4.1 normal major Awaiting Review defect (bug) assigned 2012-07-15T08:33:06Z 2013-02-01T16:11:41Z "By clicking the padding button(for indention) the action not works - it warpped the text by ""p"" element with '''padding-left''' insted or '''padding-right''' in RTL." AlmogBaku Future Releases 17709 RTL for the Support Forum theme on the international sites WordPress.org site normal normal WordPress.org defect (bug) new 2011-06-06T15:57:51Z 2011-09-07T00:06:17Z "The RTL styles for the support forums are incomplete. I don't have access to the original files to make a patch, but these fixes should be all that's needed: {{{ #pages a:after, #pages span:after { content: "\200F"; } #pagebody table.widefat th { text-align: right; } #pagebody ol#thread { list-style: none; } #footer iframe, #footer p { float: left; } #footer h6 { float: right; } }}} " RanYanivHartstein Future Releases 16544 RSS2 feeds are published as text/xml rather than application/rss+xml Feeds 3.0.5 normal trivial Awaiting Review defect (bug) new close 2011-02-12T21:25:45Z 2011-02-13T06:00:04Z "It seems to me that there is a bug in feed-rss.php, feed-rss2.php and feed-rss2-comments.php All files have the following header header('Content-Type: ' . feed_content_type('rss-http') . '; charset=' . get_option('blog_charset'), true); Which seems to publish the feed as text/xml rather than application/rss+xml which I believe it should be." Orakel78 Future Releases 21872 RSS Widget, and all of fetch_feed() I believe, forces its own feed order of Post Date DESC General normal normal Awaiting Review defect (bug) new 2012-09-11T15:25:32Z 2012-09-11T15:58:00Z "My events management plugin wanted to provide Upcoming Events via RSS. I wrote a pre_get_posts filter to modify the order and orderby of the event's feed to be Ascending based on a the event's start date, and it was good. Good, however, for only as long as you don't subscribe to the feed using WordPress (whether it be the event site or one on a totally different network). WordPress, upon fetching the feed, always re-sorts the posts according to the post date. Subscribing with something like iGoogle, will show me my upcoming events in the order that I've coded. Is this an intentional design decision? It feels to me that the generating site should be responsible for the order of the feed, and WordPress should respect the generating site's wishes and present the feeds in the order it is given." madtownlems Future Releases 22010 RSS Widget with hardcoded icon and style Widgets normal normal Awaiting Review defect (bug) new 2012-09-26T22:13:58Z 2012-09-26T22:13:58Z "Standard RSS Widget outputs hardcoded icon and oldschool inline style=""border:0"" e.g. {{{}}} elements after {{{wpautop()}}} filtering for display. They turn up in the editor too, which reinforces the problem. I've adapted one of the filter functions to strip superfluous newlines, and changed my RSS importer to use it. The results have been warmly welcomed by users, who no longer have to clean up their imported blog content. ;-) {{{strip_newlines()}}} should probably go into {{{wp-includes/formatting.php}}}, if there isn't already a function that already serves this purpose. I couldn't find one, so I adapted this. Given that similar HTML block/inline-savvy string-replacement code exists in other formatting functions, perhaps there's an opportunity for some refactoring here? I feel kind of silly proposing a function that is almost entirely duplicated from other code in the core. I've used it immediately before the ""Clean up content"" section in {{{wp-admin/import/rss.php}}}'s {{{get_posts()}}}, and in an Advogato importer that I've written (which also uses HTML as the content format). {{{ function strip_newlines($text) { // Respectfully strip unnecessary newlines $textarr = preg_split(""/(<[^>]+>)/Us"", $text, -1, PREG_SPLIT_DELIM_CAPTURE); $stop = count($textarr); $skip = false; $output = ''; // loop stuff for ($ci = 0; $ci < $stop; $ci++) { $curl = $textarr[$ci]; if (! $skip && isset($curl{0}) && '<' != $curl{0}) { // If it's not a tag $curl = preg_replace('/[\n\r]+/', ' ', $curl); } elseif (strpos($curl, '
' . __('Your password has been reset.') . '
'); }}} This change forces the user to return to the homepage before logging in again and then they dont get the ""invalid key"" error. It would be nice if there were a more permenant fix for this issue that wouldn't get lost when we update the next time." binaryweb Future Releases 12929 Reserved names for taxonomies Taxonomy normal normal Future Release enhancement assigned 2010-04-08T20:30:17Z 2013-01-16T17:42:20Z To prevent issues like #12917, register_taxonomy() should check a list of reserved names, before registering the taxonomy. scribu Future Releases 12461 "Resend Pass to users from ""admin > users""-list" Users 2.9.2 normal normal Future Release feature request new 2010-03-02T15:23:32Z 2010-03-02T17:34:01Z "In some of my projects i got the case, that i have to resend the password to some of my users (in this cases WP is used as a CMS). So i needed a possibility to resend (better would be: reset) the pass. Currently i'm stuck with a custom admin-UI on a template-page that contains a list of users (each in a row). Currently i got the follwing (in a custom list/table of users) for each user at the end of the