Skip to:

Opened 7 years ago

Last modified 7 years ago

#7503 new defect (bug)

Add identifying tag parameter to bp_has_*() loop arguments.

Reported by: dcavins's profile dcavins Owned by:
Milestone: Awaiting Contributions Priority: normal
Severity: normal Version:
Component: Templates Keywords:


When filtering arguments via hooks like bp_after_has_groups_parse_args, knowing more about the loop's context would help determine whether filters should be applied and how. At the moment, you can look at the incoming arguments and make a guess, but it would be easier to target the loop in the group widget, for instance, and not the main groups directory loop on the same page, if the widget's parameters included 'context' => 'widget' or similar.

These loops are good candidates for this additional parameter:

  • bp_has_activities()
  • bp_has_blogs()
  • bp_has_groups()
  • bp_has_members()
  • bp_has_message_threads()
  • bp_has_notifications()
  • bp_has_profile()

The function bp_has_activities() is used in a number of ways within BP:

  • bp_activity_embed_has_activity() to embed activity items
  • bp_activity_heartbeat_last_recorded() to return new activity items
  • RSS feed output
  • Recent posts widget
  • activity-loop.php (template used in a number of contexts)
  • Activity single item display

@jjj notes that bbPress does something similar in bbp_set_query_name():

This is not a technically difficult change to make, but we should decide what we want to call the parameter and what pattern should be used for the names. We could use names patterned like OOCSS, for example:
'loop_name' => 'directory--main'

Thanks for your thoughts about how to make this small change as useful as possible.

Change History (3)

This ticket was mentioned in Slack in #buddypress by hnla. View the logs.

7 years ago

#2 @hnla
7 years ago

Personally not a fan of BEM, OOCSS is something that really is common sense that many devs have practised for years without having to give it a name ( a series of elements requiring same styles would have the common styles described in a grouped selector sense or set as a class that could be applied to elements as needed)

As we haven't adopted a BEM methodology to our markup in the past or in current endeavours not sure we should have an odd example spring up, I would plump for a traditional 'directory-main'.

#3 @DJPaul
7 years ago

  • Component changed from Core to Templates
  • Milestone changed from Awaiting Review to Future Release

This is very low priority and I doubt anyone will get it done soon (this ticket is already 3 months old), but sure.

Note: See TracTickets for help on using tickets.