this is looking like an EXCELLENT script! thanks for sharing it!

Q: just to be sure, it is .htaccess in the ROOT of the site that gets 777, and not any of the .htaccess files that came with the package, correct?

also, i set .htaccess to 744 instead of 777. that OK? (trying to be more secure). if that is a good idea, may want to update the ReadMe.txt?

if i enable any of the following in my root .htaccess, i get a 500:

php_flag display_errors on
php_flag log_errors on
php_flag session.use_trans_sid off

possible suggestions

when in the admin interface and looking at the .htaccess file, it might be a good idea to check permission also? i didn't have .htaccess set to 777 and the admin interface didn't indicate any error.

» Q: just to be sure, it is .htaccess in the ROOT of the site that gets 777,
» and not any of the .htaccess files that came with the package, correct?

yes - only the root htaccess need write rights

»
» also, i set .htaccess to 744 instead of 777. that OK? (trying to be more
» secure). if that is a good idea, may want to update the ReadMe.txt?

In different server landscapes a 744 is throwing some errors. This is the reason for 777, but 744 is better for secure

»
» if i enable any of the following in my root .htaccess, i get a 500:
»
» php_flag display_errors on
» php_flag log_errors on
» php_flag session.use_trans_sid off
»
» possible suggestions

this three lines are not needed

»
» when in the admin interface and looking at the .htaccess file, it might be
» a good idea to check permission also? i didn't have .htaccess set to 777
» and the admin interface didn't indicate any error.

hm seems to be a good idea

Suche noch Programmierer für das Spider Trap Team, die mir helfen die Software weiterzuentwickeln.