Skip to:
Content

{5} Accepted, Active Tickets by Owner (Full Description) (10 matches)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

dcavins (3 matches)

Ticket Summary Component Milestone Type Created
Description
#6210 Create New Invitations API Core Future Release enhancement 02/11/15

Create a flexible API to create/retrieve invitations across components.

Examples:

  • invite to a group
  • invite to the site
  • invite to a blog
  • invite to edit a doc

Tasks:

  • Write tests for group invitations. (See #6209)
  • Write core invitations API code.
  • Switch group invitations over to using invitations API.
  • improve group invitations experience
  • Add new features.

Data structure

On one hand, it makes sense to use a dedicated table for this like we do with notifications, but it could easily be built using a new custom post type and post meta (since Boone’s been souping up WP_Query's meta queries...)

I would really appreciate some feedback on which way BuddyPress wants to go with future data and the positives of each approach.

If a table, here are the fields I’m imagining: id - primary key user_id - ID of invited user, maybe 0 if invitee is not a site member inviter_id - ID of user that created invite, maybe 0 if a request for membership invitee_email - used when invitee is not yet a member of the site component_name - e.g., groups, similar to activity/notification component_action - to cover components that need several invitations item_id - e.g., group id in the case of a group invitation secondary_item_id - flexibility for components content - store extra information provided by inviter/requester date_modified - date created or date invite sent invite_sent - 0 if draft, 1 if sent. opt_out - Has this user asked to receive no more invitations from a component?

Group Memberships

Currently, outstanding group memberships are stored in the group members table and identified via a combination of statuses. I’m thinking that users who have been invited or have requested membership would exist only in the new invitations table.

Areas for improvement/Adding new features

  • Allow multiple invitations to a group from different users, as imath proposed—this helps with transparency.
  • Allow site admins to decide if members can only invite friends to groups (current behavior), or if users can invite any site member.
  • Apply the new suggestions API to the group invitation pane. (Can it be extended to display status messages like “Violet Vance — already a member”?)
  • Allow invitation of non-site members to the site and groups, like Invite Anyone.
  • Maybe provide centralized invitations pane for user with status. Could be a new tab, or maybe should be under some other tab—there are a lot of navigation options on the user’s profile already—could notifications about invites contain actions for responding to invitations/requests?
  • Improvements to invitations UI so that it’s clear what status each invitation has—draft, sent (and when)—and the ability to resend.
  • Improved invitation management for group admins and site admins (via wp-admin groups management pane).

#6161 Group Bulk Edit Groups Future Release enhancement 01/24/15

So, I imported some Groups using a plugin.

When users started joining the groups, I realized that the first member automatically became the administrator of the group!

Hmm...looks like these groups were created without any members (or administrators) and since every group needs an administrator, therefore, the first member to join was being made administrator.

Ok, no problem, methinks...just like I can bulk edit posts/pages to change author, I should be able to bulk edit groups to change/add administrator, right? Wrong! There is no bulk edit function for groups.

Well, there should be.


#7343 Add the_group filter to allow group object modification Groups Future Release enhancement 11/12/16

Possible to add the_group filter, probably inside the_group() function, to allow to easily modify the group object in the loop? In a similar way to how the the_post filter works.

One scenario where the group objects needs to be modify is explained in ticket:7290. And the only solution at the moment is to modify the groups_template object using nested loops ticket:7290#comment:25 ( which I personally don't like ).

Same filter, I believe, should be applied to the the_member() function. Perhaps this should be created as a separate ticket.


johnjamesjacoby (4 matches)

Ticket Summary Component Milestone Type Created
Description
#6173 'Members' menu selected when current page user profile page Core Future Release defect (bug) 01/29/15

In attached screen shot you can see that the current page selected is "My Profile" URL "/members/chris/profile/"

But also menu "members" URL "/members" was selected.

I checked that the current menu selection was done by wordpress core in file /wp-includes/nav-menu-template.php. So I'm not 100% sure if this could be fixed within buddypress.

Seems like as "my Profile" also contains 'members' it selects the members link too.


#5121 Review and improve capabilities checks Core Future Release enhancement 07/26/13

As mentioned in comment:1:ticket:5115, there are places where is_super_admin has been used in lieu of a capabilities check. This is a follow-up to that, and can serve as a catch-all ticket for reviewing and replacing prior pseudo-capabilities checks with the capabilities API.


#6179 notification count doesn't match on admin bar Toolbar & Notifications Future Release enhancement 02/01/15

BP 2.2 RC2 theme 2013

All is in the title and the joined picture.

To reproduce: mention a user several times (more as once preferably :) )

To solve the issue, i modified the $count in bp_notifications_toolbar_menu function (bp-notifications-adminbar.php:20)

Change

$count = ! empty( $notifications ) ? count( $notifications ) : 0;

to

$count = bp_get_total_mention_count_for_user( bp_loggedin_user_id() );

#6347 XProfile fields used for signup should be configurable Extended Profile Future Release enhancement 04/03/15

BuddyPress has always used fields in the "Base" field-group as sign-up fields. In our templates, register.php just calls bp_has_profile() with custom arguments.

While it is possible to conditionally filter bp_before_has_profile_parse_args when bp_is_register_page() returns true, I believe BuddyPress should offer the ability to cherry-pick which fields across all field-groups should appear on the signup page.


netweb (1 match)

Ticket Summary Component Milestone Type Created
Description
#7535 Add npm `package-lock.json` for npm v5.x Build/Test Tools Future Release task 06/07/17

npm v5 now by default generates a package-lock.json file

Some paraphrased notes from the announcement post: http://blog.npmjs.org/post/161081169345/v500

  • package-lock.json and npm-shrinkwrap.json are aware of each other and happy to coexist
  • package locks no longer exclude optionalDependencies that failed to build. This means package-lock.json and npm-shrinkwrap.json should now be cross-platform.
    • This will hopefully mitigate the optionalDependencies issue with our build server in #38657 / r39368, when the build server is bumped to use the upcoming Node.js v8.x LTS release this can be tested and confirmed.
  • Running npm while offline will no longer insist on retrying network requests. npm will now immediately fall back to cache if possible, or fail, npm's caching is vastly improved in npm 5
  • On performance, NodeJS 6.9.1 and NPM 3.10.8 running npm install in tests took ~63.94 seconds on average, with NodeJS v7.10.0 and npm v5.0.0 this is halved to ~26.26 seconds on average, once npm modules are cached reinstalling node_modules averages 16.163 seconds, just shy of a 4x speed boost
    • Detailed bbPress, BuddyPress, and WordPress performance tests can be seen in this spreedsheet
    • The performance boost is comparable to that of Yarn, initial install 21.40 seconds, and subsequent installs 18.82 seconds, see #38603

Related: #7378 Investigate using yarn instead of npm Related: #WP40938 Add npm package-lock.json for npm v5.x


tw2113 (2 matches)

Ticket Summary Component Milestone Type Created
Description
#7377 Inline documentation improvements for 2.8 Core Future Release enhancement 12/05/16

There are bunch of places, where PHPDoc is not synced with the related doc. Example:

/**
 * Render the Group Type metabox.
 *
 * @since 2.6.0
 *
 * @param BP_Groups_Group|null $user The BP_Groups_Group object corresponding to the group being edited.
 */
function bp_groups_admin_edit_metabox_group_type( BP_Groups_Group $group = null ) {}

Note the usage of $user in @param and $group in code. This might be a problem later, when we will start using https://developer.buddypress.org by @tw2113, so it's better to fix earlier.

The goal of this task is to make constant improvements in such places in various parts of the BuddyPress code.


#7143 2016 list of filters/hooks missing documentation Core Future Release enhancement 06/26/16

Running list of hooks that are presently missing documentation, for my reference.

  • bp_register_email_tax_type -> bp-core-taxonomy.php

Note: See TracReports for help on using and creating reports.