#5949 closed enhancement (fixed)
BP XProfile Hooks Documentation
Reported by: | tw2113 | Owned by: | tw2113 |
---|---|---|---|
Milestone: | 2.2 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | |
Cc: |
Description
This ticket will be where all BP XProfile patches go for the Hooks Documentation.
Relevant files:
bp-xprofile-actions.php
bp-xprofile-activity.php
bp-xprofile-admin.php
bp-xprofile-cache.php
bp-xprofile-caps.php
bp-xprofile-classes.php
bp-xprofile-cssjs.php
bp-xprofile-filters.php
bp-xprofile-functions.php
bp-xprofile-loader.php
bp-xprofile-screens.php
bp-xprofile-settings.php
bp-xprofile-template.php
Change History (18)
#1
@
10 years ago
- Milestone changed from Awaiting Review to Future Release
- Type changed from enhancement to task
#8
@
10 years ago
How would we like to handle these action hooks?
do_action( bp_get_the_profile_field_errors_action() );
From the looks of it, it's technically a dynamic hook based on field IDs. From the example in the phpdoc block for bp_get_the_profile_field_errors_action
, they look similar to bp_field_12_errors
. with the number corresponding to the field.
#9
@
10 years ago
My preference would be to leave the code as-is, and put the documentation as per usual right above the do_action()
calls. In the documentation, explain that it's a dynamic hook, and explain how it's concatenated (like you've done here).
If, for some technical reason, this won't work with the parser, then we could start concatenating inline, and stop using bp_get_the_profile_field_errors_action()
function in core.
Moving into Future Release; we can keep these here and move them into particular releases' milestones as we commit things (or work on them).