|
I got Sitescooper working (great tool, BTW) with the latest
version of Plucker and wanted to share the (trivial) solution. I am running Sitescooper with the version from CVS, so the changed
variables that people have mentioned being a problem with older versions of Sitescooper
(doc_name and doc_file
-> db_name, db_file in Main.pm) was already fixed. But it needs to be fixed if you
are using version 3.1.2 of Sitescooper. I installed Plucker 1.6 to the default location. It seems
that they changed the name of the main entry point for building a pdb file. What used to be plucker-build (which was I guess
a batch file or exe) is now a python file. The only change I needed to make was
to the sitescooper.cf file where I added the line Plucker: "C:\Program Files\Plucker\parser\python\vm\python" "C:\Program
Files\Plucker\parser\python\pyplucker\spider.py" In addition, I needed to create the .plucker directory in my
profile directory (on windows XP, it's located at "C:\Documents and
Settings\username"). You will need to do this from the command line (e.g.
run "md .plucker" when at "C:\Documents
and Settings\username") because Windows Explorer has a problem with making
directories that start with a period. Once I did those 2 things, the -mplucker
option worked great. The latest version of the Plucker viewer is great – I highly
recommend trying it! David |
