I had Engine Hosting make me a duplicate of my original database, we’ll call “B”, hosting on the same server, same username, same password. They coached me through what I would need to have in my htaccess file to make the subdomain work. My htaccess then reads:
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^testsite.mainsitedomain.com [NC]
RewriteCond %{REQUEST_FILENAME} !testsite/
RewriteRule ^(.*)$ testsite/$1 [L]And so I copied the entirety of the site’s public_html folder and put the copy into the testsite folder I created. Then I went into the testsite/system/config file and changed the path to the CP to be testsite.mainsitedomain.com/system/ and I changed the database name to the “C” version of the database - the duplicate that Engine Hosting created for me. I then accessed the control panel by visiting that new subdomained address to the CP and used deeploy helper to update the remaining paths in the control panel so that everything in the subdomained CP referred to the subdomained copy of the site. But I see strange things happening - deeploy helper still indicates that, despite my being seemingly logged into the subdomain control panel, the database listed is the B database and not the C database - which i thought was determined solely by the database name in the config file. And changes i make in deeploy helper are showing up in both - so i think I’m getting logged into the same control panel, same database despite the separate CP homepage URLs and seemingly separate database name entries in their respective config files. I’m at a loss to explain why.
My intention was to use the duplicate version to run a duplicate of the live site to do some testing on it, but i can’t seem to make this connection quite right. Any pointers you folks can share?
Thanks!