I don't know, but will look into it.  I agree it would be a cool feature.

Yes, I recently added that feature following another request. Try the latest development snapshot version. The only caveat I'm aware of is that although the tags are filtered for the user's actual post access, the cloud size is still based on total posts.

Hi Kevin!

I just downloaded and installed the latest version of Role Scoper, RC 0.9, to test the tag cloud feature.

But although I'm logged in, I do not see the tags I used a lot in my restricted posts.
- I suppose that the tag cloud just shows the tags which are used in public posts? I made all of them private because I do not want to have my private stuff on the internet when Role Scoper is deactivated for some reason.

Is it possible to make the tag cloud work nevertheless? Perhaps a new tag cloud function? I do not like the standard cloud that much anyway because it is not customizable at all.

I know this is probably quite some work, but I would still love to see it work.

I used wp_tag_cloud to generate the tag cloud. It is in my sidebar without the loop of course:

But I also tried the widget.

The results differ, but just slightly. I suppose it is due to the fact, that I changed the standard values of wp_tag_cloud as shown above. Still none of the tags in the private posts show up. (I can see that easily because the many private posts deal with the same topics and have the same tags.)

In the official documentation on the template tags list I do not find anything about a function get_tags.

I use WP 2.7 DE-Edition (German edition).

Yes, there is one hack in my theme's function.php:

It replaces the ',' in the css font-size values with '.'.

If the "no front-end admin" option doesn't explain your symptom, I am at a loss to reproduce it. Can you help by editing your role-scoper/hardway/hardway_rs.php as follows:

temporarily remove (or comment out) all the following code in flt_get_tags

if ( ! empty($args['exclude']) || ! empty($args['include']) || ! empty($args['offset'])
|| ! empty($args['parent']) || ! empty($args['child_of'])
|| ! empty($args['get']) || ! empty($args['name__like']) || ! empty($args['search']) )
{
  return $results;
}

global $scoper, $current_user;
$taxonomies = array( 'post_tag' );
$key = md5( serialize( $args ) . serialize( $taxonomies ) );
$ckey = md5( $key . serialize($scoper->get_terms_reqd_caps('post')) );
$cache_flag = SCOPER_ROLE_TYPE . '_get_terms';

if ( $cache = $current_user->cache_get( $cache_flag ) )
	if ( isset( $cache[ $ckey ] ) )
	     return apply_filters('get_tags_rs', $cache[ $ckey ], 'post_tag', $args);

and

$cache[ $ckey ] = $results;
$current_user->cache_set( $cache, $cache_flag );

$results = apply_filters('get_tags_rs', $results, 'post_tag', $args);

See if it works then. If not, put in an echo statement to make sure the function is actually running. Then find out what it is setting $qry to, and let me know.

Please try changing your function flt_get_tags in hardway_rs.php as follows:

change:

to:

$qry = "SELECT DISTINCT t.*, COUNT(p.ID) AS count FROM $wpdb->terms AS t"
 . " INNER JOIN $wpdb->term_taxonomy AS tt ON tt.term_id = t.term_id AND tt.taxonomy = 'post_tag'"
 . " INNER JOIN $wpdb->term_relationships AS tagr ON tagr.term_taxonomy_id = tt.term_taxonomy_id"
 . " INNER JOIN $wpdb->posts AS p ON p.ID = tagr.object_id WHERE p.ID IN ($posts_qry) GROUP BY t.term_id $limit";

That will draw the term count from readable posts instead of the stored count. It should fix your missing private tags AND make all the tag sizing reflect actual read access for the logged user!

No, that code is already in the current Role Scoper version.

You're welcome, and thanks for all your feedback.

I'll look into this again later tonight. Seems there's some difference between your configuration / content and mine (though I'm sure private tags are coming through and being sized for me).

Jessica said:

As for the tags: There is still something I really don't understand, but I suppose this is the problem of WP's built-in tag cloud feature and not Role Scoper: There are tags which are used quite often but they are not displayed while seldom tags do show up.

No, that was my fault. In the low-level tag query, I forgot to order the results by post count so that the results are your top N tags. This is fixed in rc9.9215, which also adds full support for all applicable get_tags / get_terms arguments.

I've been having some trouble with this today. I'm using the most recent dev. Any new tips?