PhpDig.net - View Single Post - Can't get PHPDig to index an htaccess protected site

Charter · 02-20-2004, 08:54 AM

>> I set the ../admin/temp directory, the ../includes directory and the ../text_content directory to chmod 777 (don't know if this is how it is supposed to be.

Hi. Yes, those are the correct directories to set to 777 permissions.

>> So I go ahead and enter a URL to be spidered into the text box. For example: http://username:password@www.mydomain.com
Nothing happens. It just hangs.. doesn't even go to the next page.

Are you able to access http://username:password@www.mydomain.com from the browser window without using PhpDig? What OS/setup are you using?

>> However, if I write: http://www.mydomain.com
It goes to the next page, but doesn't find any links on that page. Totally weird.

As the directory is username/password protected, PhpDig doesn't have access so it doesn't find any links.

>> When I go ahead and remove the htaccess username/password protection from that website and try it again with: http://www.mydomain.com
It does find the links and seems to spider it correctly.

Without the username/password protection, PhpDig has access and can find links.

>> I would like to split that admin directory out of the phpdig directory...

Try installing everything in the secure search_tools directory and then move the search.php file where wanted and make the following edits:

In search.php edit $relative_script_path = '.'; to reflect the directory of the PhpDig install, something like $relative_script_path = '../search_tools'; or $relative_script_path = './secure/admin/search_tools'; depending on your setup.
In config.php edit the first line of code (the code checking the $relative_script_path variable) so that it contains && ($relative_script_path != "fill_in") where fill_in matches what $relative_script_path = '.'; gets set to in the search.php file.

02-20-2004, 08:54 AM	#2
Charter Head Mole Join Date: May 2003 Posts: 2,539	>> I set the ../admin/temp directory, the ../includes directory and the ../text_content directory to chmod 777 (don't know if this is how it is supposed to be. Hi. Yes, those are the correct directories to set to 777 permissions. >> So I go ahead and enter a URL to be spidered into the text box. For example: http://username:password@www.mydomain.com Nothing happens. It just hangs.. doesn't even go to the next page. Are you able to access http://username:password@www.mydomain.com from the browser window without using PhpDig? What OS/setup are you using? >> However, if I write: http://www.mydomain.com It goes to the next page, but doesn't find any links on that page. Totally weird. As the directory is username/password protected, PhpDig doesn't have access so it doesn't find any links. >> When I go ahead and remove the htaccess username/password protection from that website and try it again with: http://www.mydomain.com It does find the links and seems to spider it correctly. Without the username/password protection, PhpDig has access and can find links. >> I would like to split that admin directory out of the phpdig directory... Try installing everything in the secure search_tools directory and then move the search.php file where wanted and make the following edits: In search.php edit $relative_script_path = '.'; to reflect the directory of the PhpDig install, something like $relative_script_path = '../search_tools'; or $relative_script_path = './secure/admin/search_tools'; depending on your setup. In config.php edit the first line of code (the code checking the $relative_script_path variable) so that it contains && ($relative_script_path != "fill_in") where fill_in matches what $relative_script_path = '.'; gets set to in the search.php file. __________________ Responses are offered on a voluntary if/as time is available basis, no guarantees. Double posting or bumping threads will not get your question answered any faster. No support via PM or email, responses not guaranteed. Thank you for your comprehension.