Changeset 482602
- Timestamp:
- 12/30/2011 11:54:03 PM (14 years ago)
- File:
-
- 1 edited
-
advanced-post-privacy/trunk/readme.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
advanced-post-privacy/trunk/readme.txt
r482600 r482602 13 13 allows you to make exceptions to any content types that have been marked as private. 14 14 15 [b]Possible Future Features[/b] 15 == Possible Future Features == 16 16 * Allowing exceptions on a per page/post basis. 17 17 * Allowing protected posts/pages to be bypassed. … … 48 48 directory. 49 49 50 [b]Available Hooks[/b] 51 Actions 52 adv_pp_add_ip_address_exclusion 53 adv_pp_remove_ip_address_exclusion 50 == Available Hooks == 51 adv_pp_add_ip_address_exclusion 52 adv_pp_remove_ip_address_exclusion 53 adv_pp_add_role_exclusion 54 adv_pp_remove_role_exclusion 55 adv_pp_uninstall 54 56 55 adv_pp_add_role_exclusion 56 adv_pp_remove_role_exclusion 57 adv_pp_applicable_post_types 58 adv_pp_post_type_labels 59 adv_pp_bypassed_post_ids 57 60 58 adv_pp_uninstall 59 60 Filters 61 adv_pp_applicable_post_types 62 adv_pp_post_type_labels 63 adv_pp_bypassed_post_ids 64 65 [b]Adding a type of Exclusion[/b] 61 == Adding a type of Exclusion == 66 62 By default, Advanced Post Privacy (APP) has two types of exclusions, IP Address, and Role. It’s built in a mostly modular fashion, and is a configuration based plugin, meaning after adding your functionality, you need to explicitly tell the system about your new functionality, via the config.json file. 67 63
Note: See TracChangeset
for help on using the changeset viewer.