Changeset 483653
- Timestamp:
- 01/02/2012 09:52:43 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
r483647 r483653 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 67 If you wanted to add a new type of exclusion, for example IP Address Range, you would have to do the following .67 If you wanted to add a new type of exclusion, for example IP Address Range, you would have to do the following: 68 68 * Create a new directory inside the code folder, naming doesn’t matter much here, it could be called “ip-range”. 69 69 * Create a file called exclusion.php, this will be a class which could be called “ipRangeExclusions”, this class must implement the “appExclusions” interface, and should (for posterity) extend the primary “advancedPostPrivacy” class. This will force the class to have 5 static methods, broken down as: … … 95 95 96 96 97 **Data available to your Exclusion Module** 97 **Data available to your Exclusion Module** 98 98 If you followed the conventions, all of your classes will ultimately extend the core advancedPostPrivacy class, 99 99 meaning you have access to all the methods within the class, however most of them may be made private in the
Note: See TracChangeset
for help on using the changeset viewer.