Skip to:

Changes between Version 3 and Version 36 of Ticket #6026

07/25/2016 04:12:48 PM (8 years ago)


  • Ticket #6026

    • Property Status changed from new to assigned
    • Property Summary changed from And if the Blogs component had Single items? to Single items for the Blogs component.
    • Property Owner set to imath
    • Property Milestone changed from Awaiting Review to 2.7
    • Property Keywords has-patch added
  • Ticket #6026 – Description

    v3 v36  
    1 That's the question that came to my mind reading DJPaul's notes about your discussions at [ WCSF14]. Here’s the points about the Blogs component :
     1New areas to improve sites discoverability/Blogs component features.
    3 1. We like the existing integration into user profile (blogs you’re part of).
    4 2. We should add integration into groups (aka the groupblog plugin).
    5 3. Discoverability of blogs is hard to do because of limited info from WP, and of likelihood of integration of external tools for sites that try to do this (e.g. elasticsearch).
    6 4. Rename component away from “site tracking”.
    7 5. Directory:
    8  a. add blavatar. (avatars for blogs)
    9  b. there are some minor improvements/tweaks we can make to the template.
    10  c. add a “subscribe to blog” button and show it perhaps in a user’s activity stream, or on a new profile tab.
    12 So unlike a previous ticket about "Avatar attachments" where i misunderstood the notes, this time i haven't built a patch but an experimental plugin :)
    14 My goal was to explore if it could be interesting to add single items to the Blogs component. How would it look like? Behave? What could be the features ?
    16 The "fear" that led me into the plugin direction was the second point of the list where DJPaul is talking of the Groupblog plugin integration. Is it a way to have Groups to manage the different other blogs features listed ? If so, then simply set this ticket as invalid :)
    18 The [ BP Blogs Extended] plugin i wrote this last few days is suggesting an (or improving the) answer on points : 1., 3., 5.a., 5.c. and building it, it gave birth to questions or potential improvements about some BuddyPress areas such as the use of {{{bp_nav}}} and {{{bp_options_nav}}}
    20 ==== Home of the Blogs single item ====
    22 For this kind of single item, in order to improve the “Discoverability of blogs”, i think it’s really interesting to rely on the subsite widgets. So the plugin includes by default a front.php template, but it’s not loading like it’s the case for the Groups component. It’s loading only if at least one widget is added into a specific sidebar widgets (created by the plugin) from the subsite widgets Administration.
    24 [[Image(]]
    27 The widgets approach can be interesting to give the member visiting this “Site profile” page a “taste” of what he will find in the Site. Here’s a screen shot as an example, where i’ve added 1 text widget and 3 other widgets (''latest forum topics*'', latest posts, recent comments)
    29 [[Image(]]
    32 ''*for plugin’s generated widgets it requires the plugin to be network activated or activated on the subsite and on the root site''
    34 ==== Type of Sites ? ====
    36 BuddyPress is hiding from the sites directory the blogs having a “blog_public” option not set to 1 (discourage search engines). So i’ve defined a first type “Hidden”. Hidden are only accessible to their members and it’s not possible to subscribe to these types of sites.
    38 Then, i’ve defined a second type “Lock”, where subscriptions are not possible, but members of the community can discover the content of the blogs single item.
    40 Then the last type is “Open”, subscriptions are possible.
    42 ==== What to do in these single items ? ====
    44 Apart from discovering the home page, eventually have the curiosity to see who are members of the site using the Members tab, People can view the Site’s activity (Posts, Comments... tracked by the Blogs component) and if the Administrator of the blog defined from the Manage tab of his single item a specific setting, members can publish “Site Updates” and react to them using the activity features. Else, the administrator can be the only one to publish Site’s updates. @mention suggestions will only look into the Blogs single item members.
    46 [[Image(]]
    49 BTW, the plugin is modifying the way BuddyPress is tracking “hidden” site’s posts. If a site is “hidden” (discourage search engines) activities will be generated using the “hide_sitewide” mode. Members will be able to see them from the Site’s single item or from the Sites tab of the Activity Directory.
    51 ==== My favorite part : settings (Manage tab of the single item) ====
    52 A site administrator can define some WordPress properties (name/description) as they are in the single item’s header.
    53 He can :
    54 - set his preferences about subscriptions and Site Updates.
    55 - edit the (discourage search engines) setting.
    56 - And if you are using the WP Debug mode, you’ll see that i’ve explored a way to allow these administrators to define what post types to track for their blog. This list of post types could be stored as bp_blogmetas…(#5669 and #3460)
    58 [[Image(]]
    61 ==== Blavatar (#192) ====
    62 The second manage tab is to set the Site’s avatar, the same way it’s possible for a user or a group.
    64 [[Image(]]
    67 PS: I was a bit annoyed by #5999 so i’ve changed the posted var to ‘w_crop’... to avoid the notices.
    69 Again, maybe like in the “avatar attachments” ticket, i’m completely wrong about this and you will decide to not rely on a single item for the new Blogs features you’ve discussed of at WCSF14, but it was fun to build this plugin and i have some thoughts to share with you.
    71 1. {{{bp_nav}}} / {{{bp_options_nav}}} should be restricted to Members component navigation. In the plugin, to avoid slugs collisions (#5103), i’ve copy pasted these two navs and tried to init some “container” component nav (groups,blogs?).. See the navbar.php file of the plugin.
    72 2. Groups custom front feature should be improved (not by using widgets), but by avoiding disabling the activity tabs if a group has a custom front.
    73 3. Point 1 of WCSF14  notes : “Blogs you’re a part of”. Actually, so far it’s “Blogs you’re an ~~admin~~ {{{bp_blogs_get_allowed_roles()}}} of” The plugin is suggesting a way to really have “you’re a part of”. But i guess it's easier to filter {{{bp_blogs_get_allowed_roles()}}} to also include subscribers.
    74 4. The {{{bp_get_blog_avatar}}} filter is happening once the admin’s avatar was fetched, it could be interesting to have a {{{bp_pre_get_blog_avatar}}} before this avatar is fetched to allow plugins such as the one i’ve described in this ticket to fetch the blavatar and directly returns it.
    75 5. Custom updates, the filter could be improved : #6021
    76 6. BP_Blogs_Blog class could also be improved, for the plugin’s need i was forced to filter {{{bp_current_user_can}}} to achieve my goal. That’s the reason why i’m only doing my filters if WP_DEBUG is true. Without this filter a member of an hidden blog cannot access to his single item :(
    78 This is it, i’d be happy to work on a patch to bring this “Blogs single item” into core if you think it’s interesting, else i really like the plugin !
    80 If you want to test it : (define WP_DEBUG to true to see all features)
    82 PS: BP Theme compat only.
     3- Each sites of the network will get a new single area just like Members and Groups.
     4- Members of the community will be able to subscribe to sites and follow their activities from their profile page.
     5- Site Admins will be able to access to some BuddyPress specific settings for their sites (Visibility, subscriptions, custom post types tracked, avatars, cover images) and manage their subscribers.
     6- in a future release, we could provide an API to add modules to this area to publish content for the sites for instance etc..