Ability to set the default filter for components

[nickrita]

On the activity-stream there is always "no filter" the first option that is shown.
There should be a possibility for the admin to set another one, i.e. blog posts, as the filter that is shown first.

[DJPaul]

Plugin or theme territory?

[boonebgorges]

I don't know that there's an easy way for a plugin to do it at the moment, except by using some JS. Let's leave it in Future Release, as I think it'd be pretty easy to do a bit of shuffling and at least provide a default with apply_filters() wrapped on it.

[slaFFik]

As we are aiming for site builders and developers, would be nice to have this eventually be done.

We should decide:
1) whether to give ability to filter out and/or modify the order and default value using PHP
2) create an admin area options for that.

I would go with route 2) by creating a separate page under "BuddyPress Settings" - "Personalization" (or "Tweaks" etc).

Relates to select#activity-order-by (same for members, groups, blogs, activity) (for easier code search).

Modifying component to Core, as it should be done for all components, so there should be a centralized solution.

[boonebgorges]

Building (1) will be a prerequisite for (2). I'd suggesting using this ticket to track (1), because I have a feeling it'll be much easier (and thus faster) than trying to decide where to stuff new options in our Dashboard UI.

[slaFFik]

Ok, I agree, lets do it for 2.8.

[slaFFik]

Related duplicate tickets to investigate: #5526, #5582 (has patch with UI, check it).

[tw2113]

Just throwing this out there, as it's something I've recently utilized in a plugin I'm involved in.

Provide a filter for the spot in general, allowing for someone to change it that way, if they so desire. Also add a UI element to set a value. Then, in a callback attached to the filter, check for a set UI setting, and return that value if available, else return the default incoming filtered value.

[boonebgorges]

I've had to wrestle with this for three different clients in the past month. Let's fix it for 3.0.

The technical trick is to remain compatible with the current cookie-based JS.

[DJPaul]

Fixing it for Nouveau-only is acceptable (it's a feature, not a bug fix).

[hnla]

As Paul says lets focus energies for features & enhancements on Nouveau. It makes sense that Nouveau is the project that presents many new features and framework to handle enhancements perhaps better than core or legacy can.

Two other good reasons might be that Nouveau already has the Customizer sections in place so adding a select option for admins is relatively trivial, and Activity stream is heavily JS/Ajaxed and so should be able to link through there to set defaults.