I am developing a new PHP website that must run on an existing ASP server hosted with Godaddy WITHOUT INTERRUPTING THE CURRENT SERVICES/WEBSITE. I have verified that the server supports PHP, and am ready to get started. The current site uses [url removed, login to view] to perform modRewrite for clean/pretty URLs. Unfortunately when I create a new directory (within the web root), I cannot access it. I get the following error:
Could not load type '[url removed, login to view]'
I have tried to figure out how to write a command in [url removed, login to view] file that will ignore my directory (and sub directories eventually)...but everything i put in ends up taking the main website offline.
I am looking for someone who has LOTS of experience working specifically with this rewriter application who can do all the work WITHOUT access to the live server. Attached is the current [url removed, login to view] file (with some identifiers removed). I need someone to do the following four tasks, and send me a corrected file for testing. If it works, we are finished with this project...if not, I will copy the error messages generated and send it to you for further tweaking. It is imperative that the new file NOT break any existing rewrites or modify any existing functionality. It is also not an potion to replace this rewriter with any other similar system, and moving to a different server is also not an option.
FOUR (4) TASKS IN THIS PROJECT:
(note, rewrite rules mentioned below are from Apache .htaccess files, and may not translate exactly to this application)
1. Set up such that directory "fun2010" (in web root) is accessible, and all sub-directories of this directory are accessible by their direct path and php filename (no rewrite). - See item #3 for some specific sub-directories...but there may be others which will be accessed directly without using the rewrite pattern.
2. Set up a rewrite where if the path uses a single "f", rewrites are accomplished using the following logic:
RewriteRule ^([^/\.]+)/?$ /[url removed, login to view]$1 [L]
RewriteRule ^([^/\.]+)/([^/\.]+)/?$ /[url removed, login to view]$1&n=$2 [L]
RewriteRule ^([^/\.]+)/([^/\.]+)/([^/\.]+)/?$ /[url removed, login to view]$1&n=$2&a=$3 [L]
# [url removed, login to view]
# [url removed, login to view]
3. Set up a rewrite rule to NOT rewrite items based upon the following pattern from within the /f/ path (described above):
RewriteRule ^css/$ - [NC,L]
RewriteRule ^images/$ - [NC,L]
RewriteRule ^js/$ - [NC,L]
RewriteRule \.(txt|gif|jpe?g|png|css|ico|js|pdf)$ - [NC,L]
# EXAMPLE: [url removed, login to view] is NOT rewritten into "[url removed, login to view]" but is left alone as [url removed, login to view]
4. Tell me exactly what line numbers were changed so that I can easily see what was done.
Please note that the provider who wins this project and completes it successfully and quickly will be given first priority on next project, which will involve using this same re-write system to replace the current website with the new one under development.
Just for additional info, currently when I go to http://www.mydomain.com/fun2010 the error message I get (mentioned above) is only part of the page...the full page of errors is attached in case it provides any additional useful info.
The web.config file is not able to be downloaded, so I have inserted it into a zip file (config.zip) which is now attached.