Moving site to sub-domain for development
Permalink
I have an existing/live site that I want to reproduce in a development environment for development/testing, and the development site lives under a sub-domain, with its own document root and an additional subdirectory under that.
I've been able to install Concrete 5 5.6.1 at the desired location, and had it working fine. I then erased that "dry run" install, and followed instructions to make a copy of the existing/live site in the development location, and am trying to first get it running just as-is in its new location.
I can't get to the dashboard via direct link - it prompts me for login, but the login seems to fail. I get some of the content for the main page at the base URL. No matter where I try to visit in the site, I get tons of errors of this nature:
Strict Standards: Non-static method PermissionsCache::add() should not be called statically, assuming $this from incompatible context in /home/thecompany/wwwdev/sitename/concrete/models/permissions.php on line 221
... its not always the same function name mentioned - lots of different functions. The pages delivered (aside from all the errors) are also not fully-delivered or fully-functional, nor are they completely broken ... it just seems like bits and pieces of the content are being successfully delivered.
This doesn't happen at all if I just install Concrete 5 from scratch into the same location, so it seems very unlikely that it could be server/apache config causing it.
Here's the general process I used to migrate the site:
- Took a snapshot of the exiting MySQL database using mysqldump
- Used rsync to duplicate the existing site's files into the new location
- Removed everything under <siteroot>/files/cache and <siteroot>/files/tmp in the new (dev) location
- Loaded the database snapshot into a new development database
- Edited the <siteroot>/config/site.php in the new (dev) location to reflect new database connection info and new URL/location, keeping the password salt unchanged
Any suggestions would be greatly appreciated ...
Thanks
I've been able to install Concrete 5 5.6.1 at the desired location, and had it working fine. I then erased that "dry run" install, and followed instructions to make a copy of the existing/live site in the development location, and am trying to first get it running just as-is in its new location.
I can't get to the dashboard via direct link - it prompts me for login, but the login seems to fail. I get some of the content for the main page at the base URL. No matter where I try to visit in the site, I get tons of errors of this nature:
Strict Standards: Non-static method PermissionsCache::add() should not be called statically, assuming $this from incompatible context in /home/thecompany/wwwdev/sitename/concrete/models/permissions.php on line 221
... its not always the same function name mentioned - lots of different functions. The pages delivered (aside from all the errors) are also not fully-delivered or fully-functional, nor are they completely broken ... it just seems like bits and pieces of the content are being successfully delivered.
This doesn't happen at all if I just install Concrete 5 from scratch into the same location, so it seems very unlikely that it could be server/apache config causing it.
Here's the general process I used to migrate the site:
- Took a snapshot of the exiting MySQL database using mysqldump
- Used rsync to duplicate the existing site's files into the new location
- Removed everything under <siteroot>/files/cache and <siteroot>/files/tmp in the new (dev) location
- Loaded the database snapshot into a new development database
- Edited the <siteroot>/config/site.php in the new (dev) location to reflect new database connection info and new URL/location, keeping the password salt unchanged
Any suggestions would be greatly appreciated ...
Thanks
- Sites never move well if cached. So its always best to disable the cache and clear it before making the clone.
- Sites also never move well with pretty URLs enabled, so disable pretty uRLs before making the clone.
- For subdomains, .htaccess can be a bit funny. It depends a lot on host setup. For example, on some hosts I find subdomains work without any messing, on others I have to tweak the rewrite base or rewrite rule.
- There may be a different version of php running on the subdomain. You may be able to adjust that through .htaccess or php.ini.
- Maybe you have a php.ini with other settings that did not get copied across.