missing hook in bp_core_admin_page_options()

[gordie.lachance]

There should be a hook in bp_core_admin_page_options() to be able to add custom sections for plugins.

[boonebgorges]

We don't have a hook on that page because plugins automatically appear on this list when they are registered in the proper way. See #3474. Do one of the following to ensure that your plugin appears on that list:

• Modify your plugin so that it extends the BP_Component class, making sure to set has_directory as true
• Register your plugin as requiring a top-level directory with bp_core_add_root_component()
• If all else fails, you can manually add yourself to the $bp->loaded_components global, and also make sure that $bp->{component}->has_directory is set. (I don't recommend this third way - the other two methods will accomplish the same thing in a more future-proof way.)

We would like to enforce these methods for requiring top-level directory pages, because if you manually add a dropdown to the Pages panel, your component will not be properly integrated with the rest of the bp-pages infrastructure (for example, the admin notices that appear when pages are not properly associated).

[johnjamesjacoby]

Moving closed ticket out of Awaiting Review.