lp:buddypress
- Get this branch:
- bzr branch lp:buddypress
Branch information
Import details
This branch is an import of the Subversion branch from http://svn.buddypress.org/trunk.
Last successful import was 2 hours ago.
Recent revisions
- 9796. By imath 14 hours ago
-
Nouveau: improve the way customizable slugs are handled
BuddyPress uses constants such as `BP_FRIENDS_SLUG` to let advanced users customize component URL slugs. The Nouveau template pack was wrongly checking hardcoded component names at various places into its code, in particular into the following functions and template tags:
- `bp_nouveau_
current_ object( )`
- `bp_nouveau_filter_ options( )`
- `bp_nouveau_wrapper( )` This commit also introduces a new BP Core function to get the active BP Component objects: `bp_core_
get_active_ components( )`. The `$args` argument can be used to filter the active components according to their slugs, names, ids or root slugs. Nouveau uses it to determine the component ID out of its slug and use this component ID instead of slugs to create its needed dynamic selectors, classes and data attributes. Props mattneil
Fixes #8133
- 9795. By imath on 2021-04-17
-
Nouveau: clear errors when the Activity Post Form feedback is removed
To make sure a new error is generating a feedback view, the errors attribute of the Activity model needs to be unset.
Prop studiocrafted
Fixes #8112
- 9794. By imath on 2021-04-17
-
BP Nouveau: improve the way we get the `nonce` in JavaScript main file
Splitting the `data-bp-nonce` attribute to get Ajax buttons nonce is not the right way to do it. There can be situation where the `_wpnonce` URL param is not the last one (eg: the `data-bp-nonce` attribute of the Accept Group Invite button contains a `redirect_to` param). Using the `bp.Nouveau.
getLinkParams( )` function is fixing the issue. Prop meijioro
Fixes #8396
- 9792. By imath on 2021-04-16
-
xProfile: skip caching existing data about fields of the WP field type
This allows existing xProfile fields to be converted from the `textbox` to the `wp-textbox` type (for example) by ignoring any pre-existing values retrieved by the uncached data query.
This commit also prevents the WordPress xProfile field `$table_name` property from being cleared prior to priming the cache.
Props needle
Fixes #8455
- 9791. By imath on 2021-04-16
-
Update both Template Pack registration forms to use signup fields
- Nouveau and Legacy are now usinf the `bp_xprofile_
signup_ args()` to build the argument of their registration's form xProfile loop.
- Include a backward compatibility mechanism if the `register.php` page has been overriden from a theme or a plugin.
- This commit also includes PHP Unit tests about the xProfile loop and Signup Fields.Props johnjamesjacoby, boonebgorges, DJPaul, Offereins
Fixes #6347
- 9790. By imath on 2021-04-16
-
Use drag and drop into the xProfile Admin UI to to set signup fields
- Create a new "Signup Fields" tab to list signup fields. By default this tab will include the primary field (Name).
- The install process has been adapted to make sure this is the case.
- An upgrade task is migrating fields into the primary group as signup fields.
- Make it possible to drag fields from any group into the "Signup Fields" one.
- Make it possible to use drag and drop to reorder signup fields from the corresponding tab.
- Include a link on each field entry (except the primary one) to remove the field from this "Signup Fields" field group.Props johnjamesjacoby, boonebgorges, DJPaul, Offereins
See #6347
- 9789. By imath on 2021-04-16
-
Improve the Field/Group APIs to pick selected fields as signup ones
- Introduce the `bp_xprofile_
get_signup_ field_ids( )` function to get an ordered list of field IDs to use as signup fields.
- Introduce the `bp_xprofile_signup_ args()` function to get the signup arguments to use into the registration page xProfile loop. If no signup fields are available, it falls back to the primary fields group.
- Introduce the `$signup_fields_ only` xProfile loop argument to restrict fetched fields to signup ones if set to `true`.
- Adapt the `BP_XProfile_Data_Template` class to build a unique xProfile field group out of any possible field groups containing one or more signup fields when the `$signup_ fields_ only` argument is set to true and registration is allowed on the site.
- Adapt the `BP_XProfile_Field` class to get the possible field's signup position and add a new metabox to add a field to signup ones from the xProfile Field Administration screen.
- Adapt the `BP_XProfile_Group` class to ignore non signup fields if the `$signup_fields_ only` argument is set to true. Props johnjamesjacoby, boonebgorges, DJPaul, Offereins
See #6347
- 9788. By imath on 2021-04-13
-
xProfile: introduce the Checkbox Acceptance field type
This new field type helps community site administrators get members agreement about specific rules. It can be terms of service, code of conduct, game rules, etc.
When adding such a field, the xProfile field Admin screen will contain a specific metabox to select the WordPress page to use as the linked content needing members agreement.
This field can be required or not, but cannot be updated once members agreed to the WordPress page it relies to.
Props mahdiar, vapvarun
Fixes #4747
- 9787. By imath on 2021-04-13
-
xProfile: make sure a Field Type can enforce field visibility
When saving a field having a Field Type where the custom visibility feature is disabled and the visibility property is set, use this visibility to enforce the field visibility. This part was forgotten in #7162 and it is needed by the Checkbox Acceptance field to make sure only the logged in user can see they agreed to the page requiring their acceptance.
Props mahdiar, vapvarun
See #4747
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)