Helen Foster added a comment - 28/Dec/07 01:35 AM

Helen Foster added a comment - 28/Dec/07 01:35 AM I'm in agreement with Ralf that we don't need a tags block AND a blog tags block. Let's simply have a tags block.

Martin Dougiamas added a comment - 21/Feb/08 05:35 PM

Martin Dougiamas added a comment - 21/Feb/08 05:35 PM As long as we "add an option in settings of the block to choose which tags are shown in the block" then I agree.

Mathieu Petit-Clair added a comment - 25/Mar/08 11:15 AM

Mathieu Petit-Clair added a comment - 25/Mar/08 11:15 AM This might not be a big job, but it's worth doing it right. Both blocks are now using the same css classes, but the links are different (blogs requires a bit more information in the url). A new block putting both together should also be extensible, so that other entities can use it (courses, eventually). It's worth thinking about which other useful settings could be offered to the users. Some ideas :

• a "max block width" could be useful for theming, as tags can be quite large (like 50 chars), which can disrupt fixed-width themes
• "only show my tags"
• order by date or popularity
• show as tagcloud (different font sizes) or as plain list (same font size for all tags)

Mathieu Petit-Clair added a comment - 08/Apr/08 11:16 AM

Mathieu Petit-Clair added a comment - 08/Apr/08 11:16 AM This would be a good opportunity to add a parameter $type to print_tag_cloud, or type either string or array, which would contain the type of the tags to show ('user', 'blog' .. 'bookmark', etc.). An array would make it possible to use many types together ("only show tags used by the current user on a blog", etc.). This would make it possible to display a tag cloud of a user tags on his profile, instead of the current list.