Support

 Hello, I am in California, GMT -8 Trying to comply with your request not to submit tickets before 8am in UK, close, but exhausted

we have a problem which we were able to prove that admin tools is causing, but I hope can be fixed easily

on two of the 5 sites where we have AT installed, there is a signup script which originates on a non AT site, it runs a credit card transacation thru the gateway. Once it is approved, the script then calls on a cgi-script at the site itself, where AT is installed, to create the user and password for the customer. The other 3 sites have no signups, no scripts, no problems

It aborts and says you do not have permission to run cgi-bin/pa4.cgi

We uninstalled Admin Tools totally on one of those two sites, and all worked fine, clear fault isolation seems to say something in your settings is prohbiting it. My guy who knows your package best, tried something to allow the cgi bin to run, but it still did not work

Its still installed on the other site, but signups fail, so we created a bulky inconvenient work around, inconvenient for both the customer and us, but AT remains in tact on that one site, for now.

Can you tell us how to allow the running of the cgi files. We have been using these scripts for ten years and that is why they are cgi, and perl I guess. But to replace them would be very complicated and expensive. Your tools are marvelous, but I do think we s/b allowed to say if we want a script to run or not, and suspect we can be, just don't know how.

Really like your tools, but we have to be able to run cgi on these two sites. Everything else is fantastic with AT, esp since we incorporated your idea of putting an htaccess into /administrator Our Sec Exc emails have gone from dozens a day to maybe 3 or 5 a day, total on the 5 sites we use AT on, since invoking your suggestion

But on these two sites, we simply MUST allow the two scirpts in the cgi-bin to run. Please tell us how to do this.

Please advise

Thanks and good morning to you in England? and good night from San Franscisco :)

Anna

I got out of bed to add something that may not have been understood, just want to clarify

This user/pw has nothing to do with joomla users. It creates a user/pw in .htaccess on a totally different member site. The signgup site is merely a teaser, an ad to join the real site. pa4.cgi creates the user and pw they want, in .htpasswd on a totally different non public path on the server.

we get 403, forbidden you are not allowed to run /cgi-bin/pa4.cgi

Just wanted to add that. Its too late to even digest your response, but appreciate such a quick answer

Afer uninstalling AT, we replace .htacess with the one that comes with joomla virgin install and all worked fine

I just know this has worked for a decade and stopped as soon as we installed admin tools.

and works just fine when we uninstall admin tools. Thanks. Just wanted to clarify that much

And I am pretty sure Andy did this, he mentioned it to me yesterday,,befrore we uninstalled AT

"However I'm pretty sure that you forgot to add an exception inside the Htaccess Maker page. Please add the cgi-bin/pa4.cgi path inside the field Allow direct access to these files, as described in this section of the manual."

But not positive. He lives in england too, but sleeps very odd hours and has a boat load of stuff to do tomorow. But i will pass this on to him in email Thanks!