Changeset 483640
- Timestamp:
- 01/02/2012 09:22:01 PM (14 years ago)
- Location:
- advanced-post-privacy/trunk
- Files:
-
- 2 edited
-
advanced-post-privacy.php (modified) (1 diff)
-
readme.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
advanced-post-privacy/trunk/advanced-post-privacy.php
r483450 r483640 5 5 * Author: Dan LaManna 6 6 * Author URI: http://danlamanna.com 7 * Version: 0.0.17 * Version: 1.0.0 8 8 */ 9 9 -
advanced-post-privacy/trunk/readme.txt
r483450 r483640 52 52 directory. 53 53 54 **Available Actions**: 55 * adv_pp_add_ip_address_exclusion (1 arg, the IP address being added) 56 * adv_pp_remove_ip_address_exclusion (2 args, the IP address, and the post type slug being removed) 57 * adv_pp_uninstall (No arguments, runs on uninstall) 58 59 **Available Filters**: 60 * adv_pp_applicable_post_types (Array of slug => label post types that APP can access.) 61 * adv_pp_post_type_labels (Array of labels for Post Types) 62 * adv_pp_bypassed_post_ids (Array of Post Ids the current user can bypass) 63 64 **Adding a type of Exclusion** 54 **Available Actions**: 55 * adv_pp_add_ip_address_exclusion (1 arg, the IP address being added) 56 * adv_pp_remove_ip_address_exclusion (2 args, the IP address, and the post type slug being removed) 57 * adv_pp_uninstall (No arguments, runs on uninstall) 58 59 **Available Filters**: 60 * adv_pp_applicable_post_types (Array of slug => label post types that APP can access.) 61 * adv_pp_post_type_labels (Array of labels for Post Types) 62 * adv_pp_bypassed_post_ids (Array of Post Ids the current user can bypass) 63 64 **Adding a type of Exclusion** 65 65 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. 66 66 If you wanted to add a new type of exclusion, for example IP Address Range, you would have to do the following. … … 94 94 95 95 **Data available to your Exclusion Module** 96 If you followed the conventions, all of your classes will ultimately extend the core “advancedPostPrivacy”class,96 If you followed the conventions, all of your classes will ultimately extend the core advancedPostPrivacy class, 97 97 meaning you have access to all the methods within the class, however most of them may be made private in the 98 98 future as they are really for the core. The protected static property of $_json_config is stored here, … … 100 100 101 101 **Assets Available** 102 jQuery chosen js, and css, is enqueued via APP, and can be called on any pages as it is normally called. 103 APP uses many constants, of which are: 104 APP_PREFIX (“adv_pp_”)105 APP_PATH 106 CODE_PATH 107 DESIGN_PATH 108 PLUGIN_URL 109 DESIGN_URL 110 APP_CONFIG_FILE (path to the config.json file) 111 VIEWER_IP_ADDRESS (users REMOTE_ADDR from $_SERVER) 102 jQuery chosen js, and css, is enqueued via APP, and can be called on any pages as it is normally called. 103 APP uses many constants, of which are: 104 APP_PREFIX 105 APP_PATH 106 APP_CODE_PATH 107 APP_DESIGN_PATH 108 APP_PLUGIN_URL 109 APP_DESIGN_URL 110 APP_CONFIG_FILE (path to the config.json file) 111 VIEWER_IP_ADDRESS (users REMOTE_ADDR from $_SERVER) 112 112 113 113 == Changelog == 114 114 115 = 1.0 = 115 = 1.0.0 = 116 * Switching Versioning Syntax 117 118 = 0.0.1 = 116 119 * First stable release.
Note: See TracChangeset
for help on using the changeset viewer.