Welcome to the forum:
Welcome to the iThemes, PluginBuddy and WebDesign.com forum. We've created several tutorial video's to help you get you started with using the forum, please check them out!
Also take note of the forum guidelines.
Our moderators actively respond to forum support requests during normal business hours which are Monday-Friday, 8am - 5pm Central Standard Time, typically within one business day. Although some moderators choose to work during the weekends, we can not guarantee immediate attention to your requests. Thanks for understanding.
What is included with support:
Premium support includes theme/plugin issues such as: bugs encountered under normal operation, how to use basic features, basic WordPress help, and basic help with customization (meaning we point you to resources and will help in more depth as time allows). More information.
The iThemes offices will be closed Thursday Nov. 27 and Friday Nov. 28 for Thanksgiving.
Support will be limited, as we allow our support staff to spend some well deserved time off with their families. The iThemes Support team wishes you a great Thanksgiving weekend.
Posted 20 February 2012 - 06:12 AM
I intend to use BackupBuddy to set up a development environment on a subdomain. I have not done this before and that's why I would like to clarify a few questions:
I have moved my wp-config.php from the htdocs directory to the root of my installation. Do I need to move it back before to migrate my site to the subdomain? Or does BackupBuddy automatically create a separate wp-config.php within the directory of the subdomain?
Once migrated, how can I access the subdomain with my WP backend? Is it a matter of logging in to my TLD with https://mydomain.com/wp-login.php? and to my subdomain with https://sub.mydomain.com/wp-login.php?
Posted 22 February 2012 - 12:01 AM
BackupBuddy requires the wp-config.php file to be in the web root of the site for it to be backed up. Site will still work with it up a level just being above the web root it doesn't get included in the backups (which are used for migrations). Can move temporarily so it gets included in a backup or just upload it along with backup .zip file and importbuddy.php on a migration.
When BackupBuddy creates a backup of a site it is essentially creating a copy of the site. When a BackupBuddy backup is migrated it is essentially putting that copy at the destination site (does a lot of background stuff still but to put it basically) so if there is a wp-config.php file in the backup then it will be creating a wp-config there.
Logins would be the same as they were on the source site as well for the newly migrated site.
PRAISE LORD HELIX
Posted 22 February 2012 - 01:35 AM
Thanks a lot for your explanation! This is what still puzzles me:
I would like to use BackupBuddy to migrate my site to a development environment (on a subdomain), but keep the current site live. So I would eventually have two sites online: One for the public and one for development. But both would reside on the same server.
So I would want to login to my live site and make changes there, or login to my development environment to test e.g. new themes. That's why I think I need two separate logins.
Is what I am planning to do possible with BackupBuddy?
Posted 22 February 2012 - 11:36 AM
Yes that can work. At the time of the migration they would be the same (but not connected) because the new site would be a copy of what the old site was at the time the backup was made. But they are separate sites, so you can change logins however you want once migrated and alterations made on one site won't affect the other site.
PRAISE LORD HELIX
Posted 22 February 2012 - 03:05 PM
Thank you very much for your help! I am glad that what I was planning to do can indeed be done - and BackupBuddy will by my tool of choice.
I understand that changes I do to one site will not affect the other. Once I am done with the development I will migrate everything back to the live site.