Hi. I'm trying to iron out all the bugs and issues before a major release.
Things that may still be pending are the following in no particular order:
- PhpDig might not like some JavaScript links.
- Windows Server 2003 / IIS6 might not like PhpDig.
- Certain ISP configurations may cause problems.
- Maybe other things not listed here.
Quote:
Originally posted by rafarspd
...
My ISP uses two servers, one for normal html (called the homepages server) and one dedicated to CGI, PHP, MySql etc.
PhpDig resides on the CGI server.
It can crawl any site on the homepages server but fails on any site on the CGI server.
This has been proven by installing PhpDig under my own user name account in addition to the www.rafars.org account.
Here is the reply from my ISP:-
cut -----
This is normal, the CGI platform is a loadbalanced cluster of servers, it is therefore not possible to connect back to "itself" on the loadbalanced address.
We are investigating other possibilities to enable this for the use of htdig etc although there is no ETA for this.
---- cut
So at least an answer from the ISP.
I say again:-
NOT A PHPDIG PROBLEM but an ISP CONFIGURATION PROBLEM.
...
|
I've seen some sites using PHP-Nuke, but as I haven't used it, I'm not sure what 'like php Nuke' means.