My client asked me to duplicate their current tiki setup so they could have one site for production usage and a second for testing. The current production site was laid out as a virtual directory like this (all for example's sake):
This worked for years.
So, I copied the C:\prod location to C:\staging and set that up in IIS as a virtual directory on the same default server. Now we have these locations:
I duplicated the production database of db_prod as db_staging and changed the local.php file in C:\staging\db to look at db_staging.
If I navigate to https://wiki.domain.com/staging/tiki-index.php it works, but any changes made affect the PRODUCTION site. I added some error_log entries to see what is going on, and it appears that it is using *SOME* of the files from production. Specifically, the tiki-index.php is correctly being pulled from staging, but anything in a subdirectory seems to be pulled from prod, Additionally, the production database is being used. I renamed local.php in staging and the site never noticed, which tells me that it's being redirected somehow to not even read that file.
I need these two tiki installs to function separately as far as files, and use separate databases. (I know there is a multi-tiki which uses the same set of files, but this is not an option due to security restrictions on the data housed on this system...some people can access staging but must not be able to access production.)
I've dug around everywhere I can think in IIS to find where this issue could be. ANY IDEAS will be welcomed!