The following paths are examples and need to be adapted to your drive and user names.
- Internet Explorer: C:\Users\IEUser\AppData\LocalLow\Adblock Plus for IE\patterns.ini
- Google Chrome: C:\Users\IEUser\AppData\Local\Google\Chrome\User Data\Default\File System\004\p\00\00000000
For Chrome, please note that the path's part "004" is the number of how many extensions are installed at the time Adblock Plus is was added to Chrome.
- Opera: C:\Users\IEUser\AppData\Roaming\Opera Software\Opera Stable\File System\000\p\00\00000000
For Opera, please note that the path's part "004" is the number of how many extensions are installed at the time Adblock Plus is was added to Opera.
- Firefox: C:\Users\IEUser\AppData\Roaming\Mozilla\Firefox\Profiles\79cqr13z.default\adblockplus\patterns.ini
For Firefox please note that the path part "79cqr13z.default" is the unique name of your Firefox profile.
In the files above, above, besides some very short preferences version header, the basic structure is always one section [Subscription] including the meta data of each filter list in use followed by one section [Subscription filters] containing all its filters. While most of the possible values are only relevant, if you want to provide an own filter list subsription, merely described at en/filters#comments, manually adding whitelisted domains, for example for your intranet pages, can be done by adding sections as follows, eg at the end of the document:
Code: Select all
[Subscription] url=~user~1337 title=Custom group [Subscription filters] @@||foofoo.com^$document @@||moepbar.nl^$document @@||blubbfoo.de^$document
"Custom group" can be anything
The added domain exceptions will also show up in ABP's filter settings page. They can also be deleted by the user there. Please note that if the ABP user adds further domain exceptions either via the filter settings page or by clicking "Disable on this page" in the icon menu, it is possible that those entries will land within the same section than the one you just added. If you want to avoid this, for example to be able to clearly distinguish between the ones that you added and the ones that the user added, you can simply make sure that another [Subscription] / [Subscription filters] section pair exists with the additional key/value pair "defaults=whitelist" under the [Subscription] section. This tells ABP to put all domain exceptions created via the application itself into this section pair's [Subscription filters] section.