Show Bid Request
Need CGI Troubleshooter
Bid Request Id: 37301
|
|
|
|
Posted by: |
hrmcorp (9 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Above Average - 40.00%
|
|
Posted: |
Nov 27, 2002
12:33:38 PM EDT
|
|
Bidding Closes: |
Dec 2, 2002
1:26:03 PM EDT
|
|
Viewed (by coders): |
68 times
|
|
Deadline: |
12/3/2002
TIME EXPIRED
|
|
|
|
|
Description:
I need someone to troubleshoot and fix an existing cgi script for me.
Currently 1/2 of the people using this are getting an error message which reads as follows:
No - Trespassing
You do not have Permission to Access this Information
My assistant can replicate the error but I can't. When I try it, the script seems to work fine with one exception. The first time I tried it the error came up. Then it worked. A few times later I got a 500 internal server error although the main domain was still accessible.
I know it's something simple which can probably be fixed very quickly.
The off the shelf script was installed by the company that created it but their tech support is in Greece.
I need someone to help with this that lives in the US or Canada that I can conference with during regular business hours if necessary.
The person accepting this project must have experience with affiliate/associate program tracking as a similar system is integrated into this script.
The script in question was originally obtained from http://www.turboreferrer.com
When the project is accepted we'll provide you with access to the script on our server and anything else you need to get in and take a look at it. We also have the original source files if you need to look at them.
Please quote for troubleshooting and fixing this to ensure 100% trouble free usage before our website visitors access this page.
Thank you.
Deliverables:
1) Troubleshoot and fix the script so that it is a fully functioning working program accessible from our company website.
2) A trial run through from start to finish by creating an account, referring 3 people (we will furnish the 3 email addresses for you to use), checking your stats to ensure you were credited for the referrals.
We will place a test order through the referrals you make to us so the entire system can be checked in the same manner as it will be used by our website visitors.
Platform:
The program works in conjunction with the cgi-bin on our server hosted with olm.net.
Must be 100% finished and received by buyer on:
Dec 3, 2002 EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
Special Conditions / Other:
I would like to receive bids from coders in PST, CST or EST time zones in case we need to discuss this project during regular US business hours.
Remember that contacting the other party outside of the site (by email, phone, etc.) on all business projects < $500 (before the buyer's money is escrowed) is a violation of both the software buyer and seller agreements.
We monitor all site activity for such violations and can instantly expel transgressers on the spot, so we thank you in advance for your cooperation.
If you notice a violation please help out the site and report it. Thanks for your help.
|
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
| Name |
Bid Amount
|
Date |
Coder Rating |
|
|
This bid was accepted by the buyer!
|
$40 (USD)
|
Nov 27, 2002
3:03:25 PM EDT
|
10
(Excellent)
|
|
|
Dear hrmcorp,
I have ten years of programming experience with much experience in troubleshooting. I have an excellent understanding of both the fundamentals of web cgi scripting as well as specific knowledge of programming languages often used in cgi's ( Perl, PHP, Python, Ruby, etc.)
I would proceed to troubleshoot your cgi as follows.
1) collect information about the errors from your assistant as well as any server logging.
2) attempt to reproduce the error from my systems
3) narrow the error (or errors) down to a specific component - fix the component or script.
4) test the fix myself, then have you test the fix
Thanks for considering my services,
Alan
|
|
|
|
|
|
|
