__group__ ticket summary owner component _version priority severity milestone type _status workflow _created modified _description _reporter
Future Releases 24149 Set RTL body class for iframes Administration normal minor Future Release defect (bug) new commit 2013-04-21T03:57:06Z 2013-04-22T06:36:02Z "iframe_header() sets the current locale string in the body class, but not the RTL flag. Please add this.
This came up in MP6 development, where MP6 does not (at this moment) rely on a separate rtl stylesheet like in the current admin CSS, but instead relies more on the body having .rtl set." mitchoyoshitaka
Future Releases 8592 Private Pages not listed in the Parent dropdown nacin Administration 2.7 normal major Future Release enhancement reopened commit 2008-12-12T16:22:24Z 2013-02-28T12:51:59Z "Private pages are not available as a choice in the Parent dropdown of the Attributes module.
You should be able to create a hierarchy of private pages if you want to.
Tested with r10194." mtdewvirus
Future Releases 10935 WP_Query and is_day() bug ryan Canonical 2.8.4 normal normal Future Release defect (bug) new commit 2009-10-09T05:05:24Z 2013-05-07T20:31:05Z "When you configure Wordpress with permalinks such as /%year%/%month% and even /%year%/%month%/%day/ there is
a failure when you request URLs like /2009/10/58, because it's still generating the query to the database
(AND YEAR(wp_posts.post_date)='2009' AND MONTH(wp_posts.post_date)='10' AND DAYOFMONTH(wp_posts.post_date)='58').
Also, is_day() returns true, when it should be returning false.
As adding a post with that date is nearly impossible trough the wordpress admin or the database, no posts will be found, so
Wordpress will show ""No page found"", but with HTTP status 200 OK, not 404 Not Found.
I think it's important to validate the day on the applicacion side, so for some ideas to work correctly under WP
(like take advantage of sticky posts and show all post for the month in day requests), and most importantly to save
those wasted mysql queries.
Of course I could validate the day using a filter, but that is not the general idea!" raliste
Future Releases 11286 Normal User Input Causes Status 500 Comments 2.8.4 normal normal Future Release defect (bug) new commit 2009-11-30T21:45:04Z 2012-11-26T22:20:40Z "To reproduce: Click the Submit Comment button on any post with no other input.
Expected Result: Status 200 or 403 with feedback to user.
Actual Result: Status 500 with feedback to user.
Status 500 means the server is at fault for an unexpected error condition, which is not the case here. It is the incorrect response to send, and it is alarming to see it show up in a server log without an error message.
Patch should be ready shortly..." miqrogroove
Future Releases 16881 Remove all unwanted 'nofollow' attributes from 'reply to comment' links Comments 3.1 normal minor Future Release defect (bug) new commit 2011-03-17T20:27:43Z 2011-03-19T06:47:58Z "This should be a trivial fix. r16230 removed the rel=""nofollow"" attribute from ""reply to comment"" links in the comments list, for reasons discussed in #10550. In brief, the reasons are that these are not external links that we want to tell search engines not to follow in the first place, and there is actually an SEO penalty from adding the ""nofollow"" to internal links.
Unfortunately, the ""nofollow"" was not removed from all of the ""reply to comment"" and ""reply to post"" links (for instance, in code branches when the site requires login/registration to comment). This patch corrects the rest of them.
It doesn't delete the ""nofollow"" attributes we want. For instance, in `get_comment_author_link()` which escapes links to the comment author's URL.
Additionally, the patch (see line 1110) fixes a minor inconsistency between the return values of `get_comment_reply_link()` and `get_post_reply_link()` when `get_option('comment_registration')` is TRUE.
The version in `get_post_reply_link()` is missing the `class=""comment-reply-login""` and `esc_url()` wrap. I've added them." joelhardi
Future Releases 15004 Missing index on signups table pento Database normal normal Future Release defect (bug) assigned commit 2010-10-01T03:48:25Z 2013-05-07T17:36:17Z "{{{
wp-includes/ms-functions.php:590:
$signup = $wpdb->get_row( $wpdb->prepare(""SELECT * FROM $wpdb->signups WHERE user_email = %s"", $user_email) );
wp-includes/ms-functions.php:595:
$wpdb->query( $wpdb->prepare(""DELETE FROM $wpdb->signups WHERE user_email = %s"", $user_email) );
}}}
But there is no index on user_email in the signups table. Makes these queries perform a full table scan which is slow when you have lots of signups.
Attached patch adds the index but I can't figure out how schema upgrades on MS-specific tables ever get run after the initial activation of MS mode and table creation.
" barry
Future Releases 19019 Reduce duplication in $wpdb Database normal minor Future Release enhancement new commit 2011-10-20T21:16:00Z 2013-04-22T19:53:27Z "Currently, update(), insert() and soon delete() [see #18948] use the same code to generate the WHERE clause.
It should be moved into a helper method." scribu
Future Releases 16983 Pass $sep to 'wp_title_rss' filter Feeds normal normal Future Release enhancement new commit 2011-03-27T21:11:14Z 2011-03-27T21:11:14Z Same for 'get_wp_title_rss'. scribu
Future Releases 14169 Slashes not removed when $_SERVER in process_conditionals() General 3.0 normal normal Future Release defect (bug) new commit 2010-07-01T20:40:28Z 2011-01-06T23:42:37Z Since [1964] (now after [12732] in {{{wp-includes/load.php}}}) slashes are added to all values of {{{$_SERVER}}}. If then {{{$_SERVER}}} is accessed, slashes must be removed again otherwise things might not work as intended, e.g. comparing and parsing strings. hakre
Future Releases 18035 ignore_sticky_posts fails to remove sticky class General 3.2 normal minor Future Release enhancement new commit 2011-07-08T10:03:44Z 2012-04-25T10:38:10Z "When setting the query_posts parameter:
ignore_sticky_posts = 1
all sticky posts are returned as normal posts and placed accordingly in the flow. However the sticky posts keep their sticky class, which means that an additional filtering of post_class is necessary to avoid any css rules defined for the .sticky selector taking effect.
is this intended, or could it be considered an enhancement if it was patched?
" mikkelbreum
Future Releases 22663 Performing a non-square rotate() with Imagick, then cropping, can result in incorrect Image Media 3.5 normal minor Future Release defect (bug) new commit 2012-11-30T22:49:42Z 2013-05-07T20:38:29Z "Note: This is only for *some* recent versions of ImageMagick. Older ones seem to be a bit more sane, and work fine without any patch whatsoever.
When ImageMagick performs certain operations, it sets its virtual page's x/y origin values to non-zero numbers and leaves them there, which can break some further operations that depend on the virtual page.
In this case, when rotating in non 90 degree increments, Imagick doesn't set the x/y, which means that core doesn't run into this bug, since the built-in image editor only allows for 90 degree rotates in either direction.
However, if you're a user of the API, and perform a ""non-square"" rotate, then a crop, you could end up with an image result that differs from what you'll get from GD.
There are two ways of fixing this:
- Update the virtual page with each update_size()
- Update the virtual page immediately after a rotate() only
The first is what I think we should land on eventually, because it will prevent plugins' methods from breaking core's accidentally (if they do not reset the page's values). However, that would require an additional error message to be added, which means a new string.
The second would fix the bug for anything core's APIs would do, but would depend on plugins handling resetting the page values appropriately in their own methods. It is, however, a bit safer (and wouldn't require a string change), if this is something that might land for 3.5.
I've attached patches for each method." DH-Shredder
Future Releases 13235 Simplify and add filtering to call to display author for media Media 3.0 normal normal Future Release enhancement new commit 2010-05-03T19:13:35Z 2011-04-25T16:03:53Z The author displayed on the media page (upload.php) is not filterable in any way currently. This patch adds a filter for the author ('media_author'). Perhaps more filters should be added for other fields, but at the least I would like to add this filter. sbressler
Future Releases 21534 Walker: has_children is only set if $args[0] is an array betzster Menus 3.0 normal normal Future Release defect (bug) new commit 2012-08-10T02:12:33Z 2013-04-23T02:09:53Z "You can't depend on `has_children` because it doesn't get set if `$args[0]` is an object. This is obviously an easy fix, just check if it's an object and set it in that case.
Related: #15214" betzster
Future Releases 20220 add test to see if sunrise === on in ms-settings Multisite 3.0 normal normal Future Release enhancement new commit 2012-03-12T19:06:56Z 2012-11-02T22:49:31Z "We needed to disable sunrise for certain requests.
We thought about declaring sunrise before including wp-load, but setting it to 'off'. Then having a conditial in the wp-config that only defines it to on if it is not defined and then in ms-settings to a additional check to see if sunrise is defined and equal to on. (the patch I am adding does not have the wp-config if !defined() as wp-config doesn't get updated, but if someone feels it is helpful I can add it)
Others could of changed the default defined value of sunrise and this could break bc. I am therefore not sure if the limited use case warrants it. But I thought I would suggest it." sboisvert
Future Releases 10384 Make IIS Permalink support enabled based on capability not on version number westi Permalinks 2.8 normal normal Future Release enhancement new commit 2009-07-11T08:37:44Z 2011-04-12T00:19:13Z "At the moment we enable the IIS permalink support based on checks for IIS7 and then some capabilities.
We should remove the version checking and work solely on capabilities so that we don't have to revisit when IIS8 is released." westi
Future Releases 16849 Add a filter for $overrides in wp_handle_upload() Plugins 3.1 normal minor Future Release enhancement new commit 2011-03-13T17:38:56Z 2013-03-19T06:21:47Z "I'm writing a plugin that needs to set a $unique_filename_callback in wp_handle_upload() during a normal post attachment upload (not a custom upload form), but there's no way to do it without a filter like this one:
{{{
$overrides = apply_filters( 'wp_handle_upload_overrides', $overrides );
}}}
For now I just modded my /wp-admin/includes/file.php to add it, but obviously that's not an ideal solution, especially since I plan on adding the plugin to the repository for others to use." iandunn
Future Releases 16415 Don't require CPTs to have archives in order to have feeds Post Types 3.1 normal normal Future Release enhancement new commit 2011-01-30T22:58:47Z 2013-05-16T15:33:43Z "When archives and feeds were added to custom post types (see #13818) it was set up so you had to have archives (has_archive) in order to have feeds (rewrite[feeds]).
There are some situations where it would be nice to have feeds but archives aren't needed." aaroncampbell
Future Releases 16603 Add hooks to wp_count_posts() Query normal normal Future Release enhancement new commit 2011-02-20T19:25:18Z 2013-05-04T22:40:31Z "[[Image(http://mikeschinkel.com/websnaps/Posts_%E2%80%B9_Watermark_Associates_Newsletter_%E2%80%94_WordPress-20110220-142441.png)]]
The use-case where this is needed is when the sites is using roles & capabilities to limit access to viewing posts to only those who have the proper capabilities to see them.
For example, assume we have a system with a ''""Manager""'' role and a taxonomy called ''""Post Visibility""'' where terms are ''""Visible to All""'' and ''""Visible to Managers Only.""'' We add a `'see_managers_posts'` capability to ''""Manager.""'' We then filter outs posts with the'' ""Visible to Managers Only""'' term using the `'posts_where'` and `'posts_join'` hooks when viewed by users whose role does not have the `'see_managers_posts'` capability.
With that configuration now assume for example we have 10 posts with 3 of them ''""Visible to Managers Only.""'' The post list in `/wp-admin/edit.php` will use `wp_count_posts()` to show that we have 10 posts when we can only see 7 of them. Currently to fix it so the post counts display `7` for non-managers we have to hook the `'query'` hook, which is a hook of last resort.
So, the attached patch adds two hooks to `wp_count_posts()`:
- `'wp_count_posts_sql'` - To allow modifications of the SQL used to count posts, and
- `'wp_count_posts'` - To allow modifications of the array returned by the function.
I decided to add two (2) hooks because not having the former would mean we'd need to make two SQL queries if we need to modify the counts, and not having the latter would mean that we'd have the complexity of modifying SQL in use-cases where the a SQL query modification is not what is needed to to determine the proper counts.
" mikeschinkel
Future Releases 21949 Allow private taxonomies (public = false) Taxonomy normal normal Future Release enhancement new commit 2012-09-20T22:22:14Z 2013-05-14T13:33:47Z "In a discussion with jaredatch & nacin, we discovered that the public arg is not working properly within WordPress query.
So I merged Limiting publicly queried post_types to those that are publicly_queryable with limiting publicly queried taxonomies to those that are public instead of just duplicating the code and making it for taxonomies." wpsmith
Future Releases 23247 Grammar Fix on setup when wp-config-sample.php does not exist Text Changes normal trivial Future Release enhancement new commit 2013-01-20T22:45:50Z 2013-05-14T13:26:47Z "Patch changes
Sorry, I need a wp-config-sample.php file to work from. Please re-upload this file from your WordPress installation.
to
Sorry, I need a wp-config-sample.php file to work from. Please re-upload this file to your WordPress installation.
Makes it a little more clear.
Perhaps in the future, we can remove the need for wp-config-sample.php all together." bradparbs
Future Releases 24078 Remove 'admin' as default username in install Upgrade/Install 3.5 normal normal Future Release enhancement new commit 2013-04-13T19:07:29Z 2013-05-05T21:06:45Z "The installation process populates the username field with 'admin' by default.
Many/most users probably leave it as-is, making them more vulnerable to brute force attacks that look out for ""admin"" usernames.
Seems a pretty easy improvement to specify no default username, and force the user to choose one themselves.
" chrisrudzki
Future Releases 16942 Dead code in add_query_arg() General 3.1 normal trivial Awaiting Review defect new commit 2011-03-23T02:15:56Z 2011-03-29T09:31:33Z "As it just has been checked that $uri contains at least one ?, then exploding $uri on ? with a limit of 2 must return two elements, right?
{{{
if ( strpos( $uri, '?' ) !== false ) {
$parts = explode( '?', $uri, 2 );
if ( 1 == count( $parts ) ) {
}}}
So the if clause can never be true, the code is dead." hakre
Future Releases 17981 XML-RPC wp.getComments should work for non-admins XML-RPC 3.2 normal normal Awaiting Review defect (bug) new commit 2011-07-04T22:23:03Z 2012-03-08T13:35:11Z "Right now, if the caller doesn't have the moderate_comments permission, the XML-RPC call returns a 401 error.
A more graceful alternative would be to return the approved comments. The user may not be able to moderate, but still should be able to read/reply" koke
Next Release 22030 "After ""clear background-color"" in design options, still css is added to html-output" Appearance 3.4.2 normal normal 3.6 defect (bug) reopened commit 2012-09-28T08:45:20Z 2013-04-22T19:12:19Z "After you select ""clear background-color"" in design options, the default color still is added as inline css to html-output of frontend.
Tested with 3.4.2 and Twenty Twelve 1.0 theme
Steps to reproduce:
1. Look at default html-output, no inline css for background-color
2. Design -> Background -> Color, select e.g. color #123456, save
3. Look at html-output, this is added:
{{{
}}}
4. Design -> Background -> Color -> Click ""clear"" option, save
5. Look at html-output, this is added with default value:
{{{
}}}
Expected behaviour: After ""clear"" option is used and default value #e6e6e6 (or only a #) is shown in backend, no inline css should be included in html output of frontend.
" Ov3rfly
Next Release 15576 Proper l10n of items per page in the screen options I18N 3.1 normal normal 3.6 defect (bug) new commit 2010-11-25T02:57:13Z 2013-05-11T16:29:49Z "Sites, Users, Comments, Media items and Plugins have their own translation context on the screen options tab, e.g. “sites per page (screen options)”.
To use the right grammatical case, Posts, Pages, Categories and Tags should have that context too. " SergeyBiryukov
Next Release 23713 WP 3.5.1 wp-image-editor: Scaling up images does not work Media normal normal 3.6 defect (bug) reopened commit 2013-03-07T16:59:57Z 2013-03-28T15:17:58Z "I can't scale up jpg within wordpress media library, while scaling down works as expected.
A new image file like somename-e1361912486333.jpg is created, but it has exact the same size as the original file.
phpinfo() says I have gd library installed. No imagick.
I already asked in WP Forums for help, with no reaction:
http://wordpress.org/support/topic/wp-351-wp-image-editor-scaling-up-images-does-not-work
" ullemehner
Next Release 23254 Empty Page Title Not Handled in Menu System Menus 3.0 normal normal 3.6 defect (bug) new commit 2013-01-21T20:57:57Z 2013-05-16T02:06:55Z "I noticed some peculiar menu layouts and sorted it out to having some pages with no titles (not sure the actual use case for a page without a title but it is in my test environments).
The Walker class is recognizing the page exists and creating an appropriate `` wrapper for it but with no Page Title it is not being displayed. If this is by design I think it should be revisited and if this is a defect then the included patch (not very pretty) may offer a possible solution or at least a consideration.
The patch checks if the Page Title is empty and if it is uses the Page ID as the title." cais
Next Release 14975 Nav-menu system does not always run titles through 'the_title' filter. Menus normal normal 3.6 enhancement new commit 2010-09-27T15:19:48Z 2013-05-04T23:41:26Z I am using the qTranslate plugin that uses the 'the_title' filter to parse its multilingual content (separated with comment tags). All titles are parsed well except for the titles appearing in the menu system's meta boxes; It seems this is because nav-menu functions don't run the titles through this filter. Goldfrapper
Next Release 22277 Admin (not just superadmin) should be able to add user without confirmation email in multisite Multisite 3.4.2 normal normal 3.6 defect (bug) new commit 2012-10-25T18:04:19Z 2013-05-02T00:48:36Z I don't know why admins would be restricted from adding existing users without sending them a confirmation, but they are in multisite. You have to be a superadmin to get that option. I think that is lame, and would like to see admins have that admin option. Is there is a reason why it is that way (security etc)? Since neither @markjaquith nor I could remember a reason, making this ticket and hoping we fix it. jane
Next Release 15765 wp-admin/ms-sites.php doesn't indicate required fields Network Admin 3.0.2 normal minor 3.6 defect (bug) new commit 2010-12-10T16:14:49Z 2013-05-05T00:12:24Z In '''wp-admin/ms-sites.php''', apparently all fields under '''Add Site''' are required, but there is no visual indication. novasource
Next Release 24219 All post formats not available in PressThis Post Formats high major 3.6 defect (bug) new commit 2013-04-29T04:50:17Z 2013-05-07T21:20:59Z "When creating a new PressThis post with Twenty Thirteen active, only Standard, Link, and Video are available as post formats:
https://www.evernote.com/shard/s2/sh/112e7c92-76b8-4b68-a17f-b59ac5deaaf2/32cb568f188b328ae97f285b46e7ac3b
Yes, I do use PressThis.
Similarly, mobile apps respecting `wp_getPostFormats` in XML-RPC will only show the post formats available with `get_theme_support( 'post-formats' )`
I haven't been following all of the recent post format discussion, but `get_theme_support( 'post-formats' )` should probably return all post formats unless the theme has explicitly identified which formats it supports. This is a different approach than what r24089 did, and I only see two other uses of `get_theme_support( 'post-formats' )` in core, but it doesn't accommodate for plugin/theme use of `get_theme_support( 'post-formats' )`." danielbachhuber
Next Release 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
Next Release 24059 All post formats filter to limit which formats a user can choose Post Formats trunk normal normal 3.6 enhancement new commit 2013-04-12T15:39:37Z 2013-05-13T23:56:16Z Pretty straight forward. This filter allows plugins to limit which formats a user can use based on their role/capabilities. tlovett1
Next Release 24096 Restore option to change post format in Bulk Edit box Post Formats trunk normal normal 3.6 enhancement new commit 2013-04-16T03:10:40Z 2013-04-24T21:46:08Z "For a faster change inline - to other format, add this option.
http://media.share.pho.to/1rFYs/7a29bd21_o.png" alexvorn2
Next Release 24011 "Consider hiding post title for ""Status"" and ""Aside"" formats and autogenerating" Post Formats trunk high normal 3.6 task (blessed) new commit 2013-04-09T18:51:36Z 2013-05-21T18:10:14Z The status and asides post formats shouldn't have a title. The only reason for having a title is to generate a slug. We should consider hiding the post title for these formats, and auto-generating a title based on the first X chars of the post, P2 style. markjaquith
Next Release 24013 "Hide ""Add Media"" for some post formats" markjaquith Post Formats trunk high normal 3.6 task (blessed) reopened commit 2013-04-09T18:59:25Z 2013-05-19T02:12:27Z """Add Media"" doesn't make sense for some post formats. Notably: aside, and status.
We should consider hiding it to simplify the UI for these formats." markjaquith
Next Release 24293 $allowedposttags to allow value for Security normal normal 3.6 defect (bug) new commit 2013-05-09T01:59:55Z 2013-05-09T02:11:01Z "HTML 5 allowed the `value` attribute in `` elements for use with `ol`s (e.g. setting `- ` would result in that item of the `ol` rendering as 31.
$allowedposttags strips that out currently, as that's not allowed.
Submitting a patch to allow the value attribute." kraftbj
Next Release 16705 "Unclear wording: ""An administrator must always approve the comment """ Text Changes 3.1 normal normal 3.6 defect (bug) new commit 2011-02-28T21:22:12Z 2013-05-05T01:04:18Z "I'm not certain if I should classify this as a bug or as a need to revise wording in the options menu, or if I should put in a feature request for a refined option...
...but...
If, under Settings->Discussion you have ""An administrator must always approve the comment"" checked, if the author of the post receiving the comment has the ""edit_comment"" capability, they will receive an email notification to moderate the comment in the queue.
After viewing the wp_notify_moderator function for 3.1 in pluggable.php (and comparing it to 3.0.5's version) I can see this functionality seems to be coded in by design.
What's confusing is that the option reads ""An administrator must always approve the comment"" and it's difficult to discern if that means the user role of ""Administrator"" or anyone who can be an ""administrator"" of the comments.
It's also hard to tell from the reading of the option text whether or not this means that the function is implemented incorrectly, or if the option is simply poorly worded.
In either case, it would be useful to be able to have more granular control over who is getting these email notifications for comment moderation.
Failing that, if the ""An administrator must always approve the comment"" is checked, that should mean that only users with the ""Administrator"" role should be able to approve the comment.
...depending on what the expected behavior of this functionality is meant to be." joe.woidpress
Next Release 20101 Can't use 'show_admin_bar' filter with conditional tags nacin Toolbar normal normal 3.6 defect (bug) reopened commit 2012-02-22T19:10:11Z 2013-04-22T22:10:49Z "I'm trying to show the admin bar only on the front page:
{{{
function scribu_show_admin_bar() {
return is_front_page();
}
add_filter( 'show_admin_bar', 'scribu_show_admin_bar' );
}}}
However, this doesn't work because '_wp_admin_bar_init' is called on 'init', before the main WP_Query is set up." scribu
Next Release 23850 Searchform Format SergeyBiryukov Widgets trunk normal normal 3.6 enhancement reopened commit 2013-03-22T19:51:03Z 2013-05-10T16:36:05Z We should use a filter instead of an argument. WraithKenny
Next Release 23715 Plugins/Themes that rely on get_option('embed_autourls') may fail in 3.5.x Embeds 3.5 normal normal 3.5.2 defect (bug) new commit 2013-03-07T17:43:17Z 2013-04-18T06:56:31Z "After upgrading to WordPress 3.5. or greater from 3.4.x and below, the option ""embed_autourls"" will still exist in the database. Plugins or Themes that make assumptions based on this may fail as regardless of the answer, the actual behavior is that embed_autourls is always on per http://codex.wordpress.org/Embeds
WordPress will automatically turn that into a YouTube embed when the post is viewed. As of 3.5, Auto-embeds are automatically enabled and there is no setting to turn them off in the WordPress admin pages. Prior to 3.5, there was an ""Auto-embeds"" checkbox in Administration > Settings > Media SubPanel.
Backwards compatibility could be preserved if this option would always return true from 3.5.x onward. Perhaps removing this option (from all sites if multisite) as an upgrade step could be another solution (though terrifying) to at least have a consistent (though not helpful) return value. These are just ideas that come to mind.
I did a quick scan through the options code I didn't see a history of forcing an option to a specific value for historical purposes. I assume this ticket will likely result in a ""won't fix"" but I wanted to make a record of it in the event others search the bug database.
Thank you for your time!" standardbanter
Next Release 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