warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Changed "permallow.p2b" location, add an IP to allow, PeerBlock creates new one. #402

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Set a new location for the "permallow.p2b"
2. Right click a IP and add it as allow.
3. PeerBlock then creates a new "permallow.p2b" inside the /lists/ folder of 
where PeerBlock is installed

Expected output:
PeerBlock should now use the new location as the "permallow.p2b".

What I see:
PeerBlock creates a new "permallow.p2b" inside the /lists/ folder of were 
PeerBlock is installed, causing the user to have two "permallow.p2b" files.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?

PeerBlock 1.1+ (r570) - DEV BUILD (I built it myself in VS2010) Windows XP SP3

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

http://forums.peerblock.com/read.php?3,10743 

Original issue reported on code.google.com by ineedali...@gmail.com on 7 Jun 2011 at 11:00