Opened 2 years ago
Closed 2 years ago
#8918 closed enhancement (fixed)
Automate component's directory `buddypress` post type association
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 12.0.0 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Core | Keywords: | has-patch |
| Cc: |
Description
When a plugin's component uses the has_directory global, it's required a buddypress post type entry is associated with it. So far as we were using the page post type we were using a UI to achieve this as it's easy to create a page. The buddypress post type is not displayed into the WP Administration UI as we are not using its content so we need to automate this buddypress post type association for orphaned components.
Change History (5)
This ticket was mentioned in PR #116 on buddypress/buddypress by @imath.
2 years ago
#1
- Keywords has-patch added; needs-patch removed
#3
@
2 years ago
- Keywords needs-patch added; has-patch removed
- Resolution fixed deleted
- Status changed from closed to reopened
- Type changed from task to enhancement
Working on documenting the BP_Component class, I realize this part needs to be improved so that it takes in account the component's root_slug global as well as the directory_title one.
This ticket was mentioned in PR #127 on buddypress/buddypress by @imath.
2 years ago
#4
- Keywords has-patch added; needs-patch removed
- the
$bp->loaded_componentsarray uses the component slug as keys (not the component ID). Avoid potential problems when a component slug is very different than the component ID by looping into this array the right way. - Makes sure to use the component
$root_slugand$directory_titlewhen automatically creating abuddypresspost type for orphaned components.
Trac ticket: https://buddypress.trac.wordpress.org/ticket/8918
Create a
buddypresspost type entry for potentiel third party orphaned componentsTrac ticket: https://buddypress.trac.wordpress.org/ticket/8918