moving existing site to add-on domain

[superbison]

I am confused about something and I'll present it here before asking support.

When using the add-on domain feature in the cpanel, it says DO NOT create a folder before creating the add-on domain.

I am confused about the timing of a transfer.

Example:
I have a site running WordPress that I will place here as an add-on dom.
My thinking would be to create a subdomain where I could place MANY domains, such as sites.mydomain.com, then place my domains there in separate "directories/folders"
eg; sites.mydomain.com/site1
sites.mydomain.com/site2 , etc...

THEN, regardless of whether it can be set up this way, I'd think I would
1.) copy over the site information or install a new WordPress, I haven't read how-to yet.
2.) back up existing mySQL and transfer data to a new mySQL here.
3.) have everything ready and THEN make the DNS changes.

I don't understand how to do this if I can't create the directory until I make the DNS changes and I can't obviously fill the directory with data if I'm not allowed to create it first.

What's the order for this transfer to an "add-on" which is really just a folder off my main directory.

Another Q along the same lines is, If I have unlimited add-on domains then it seems a folder for each on the root level "public_html" would make a massive mess of my root. I'd like them all to be in the sites.mydomain.com folder.

Thanks in advance for your reply.

_superbison.

[riostyles]

Are you a little confusing subdomain and add-on domains. Look close in the man, and addon is a full domain in a folder having his own domain name registrered (separately).
A sub.domain.tld is a sub domain an the master domain name remains visible.The procedures are the same for both. They are each one logged in a directory.

If this you want to do and if the the future addon already registered as domain, just go to your cpanel and create an addon domain.
I think it is better to recreate the whole WP with the DB then move the datas from the DB. If WP needs to create the directort himself (Non existing) create first WP.
Don't forget to give the user(s) acces to the DB.
Good luck

[Edit] The dns move comes really at the end after testind. Do not close your old service before all is wright.

[superbison]

Thanks for struggling through English to reply.

I understand that a subdomain and an add-on are functionally different but as you say "They are each one logged in a directory".

What I'd like is to create a SUBDOMAIN only in order to keep my root level from being cluttered with folders for each "add-on" domain.

Basically at my host now I created a folder called "sites" and in it go all the sites I own. I set the ftp privilege to that specific folder. It keeps my public_html folder cleaner.

1ftp://domain.com/sites/add-on1
1ftp://domain.com/sites/add-on2
1ftp://domain.com/sites/add-on3

Second part question, to clarify, is.. How am I supposed to have everything in the folder, up and running, before making the DNS switch if I am not allowed to create the folder until after the DNS change has been made?

That requirement is baffling.

baffle |?baf?l| verb [ trans. ] 1 totally bewilder or perplex

Maybe I should read how to transfer WP 1st. but will this answer the can't make folder before making add-on Q?

[riostyles]

Originally Posted by superbison

Thanks for struggling through English to reply.

I understand that a subdomain and an add-on are functionally different but as you say "They are each one logged in a directory".

What I'd like is to create a SUBDOMAIN only in order to keep my root level from being cluttered with folders for each "add-on" domain.

Basically at my host now I created a folder called "sites" and in it go all the sites I own. I set the ftp privilege to that specific folder. It keeps my public_html folder cleaner.

1ftp://domain.com/sites/add-on1
1ftp://domain.com/sites/add-on2
1ftp://domain.com/sites/add-on3

Thank you for undersatanding my non native English.
The FTP's have nothing to do with the differenciation sub / ad. In both cases they are the same.

Second part question, to clarify, is.. How am I supposed to have everything in the folder, up and running, before making the DNS switch if I am not allowed to create the folder until after the DNS change has been made?

That requirement is baffling.

baffle |?baf?l| verb [ trans. ] 1 totally bewilder or perplex

By creating or per FTP up to you.
If you use a new WP he will probably create the folder, check-out the install for the answer.
If you create a sub or addon domaiin, cpanel will create it for you. I do not see any chicken/egg problem there, just choose what you want to do. When ready after or upload or creating from scratch and moving the DB you test over the IP then you swap the DNS.

Maybe I should read how to transfer WP 1st. but will this answer the can't make folder before making add-on Q?

Is not such a bad idea.

But,... right now it is unclear to me if you want to create:
a sub domain eg sub.maindomain,tld or
an addon domain like mypressplace.tld or
Internal links to what you are calling subdomains but aren't.

[ldearing]

Originally Posted by riostyles

... right now it is unclear to me if you want to create:
a sub domain eg sub.maindomain,tld or
an addon domain like mypressplace.tld or
Internal links to what you are calling subdomains but aren't.

either way, subdomains or add-on domains, they will create a folder off the public_html folder... and i dont think you can change that.

[Serra]

Originally Posted by ldearing

either way, subdomains or add-on domains, they will create a folder off the public_html folder... and i dont think you can change that.

It can be changed with symbolic links, but that is a VERY bad idea.

[superbison]

ok.
listen, i'll give up to the understanding that the provided methods result in "unlimited" folders created off public_html.

I have purchased this hosting for 1 single domain. it will be using many files and occupy the root with many directories.

I didn't want "unlimited" unrelated folders being created. It makes for difficult separation and mgmt. of the One important domain. I will get confused as to which are which.

I will just create a single folder called sites and use URL forwarding from the registrar to the folder each site is in. It's only two deep I don't know why I can't specify the add-on to be created within sites.domain.com but whatever.

It seems pointless to use the add-on domain if I have to change the DNS, and wait until it propogates) in order to create it. My site will be down until I can upload the files and restore the DB. (what if there is an error?) How does that make sense?

[gtgeorge]

I too had to get used to how cpanel servers set addon domains up by adding them to your main accounts public_html instead of creating it's own public_html folder when I changed from a host that used H-sphere.

If you choose to use add-on domains you can set them up in your cpanel...which will create the folder in your public_html whereas you may upload your files. Disregard that the dns has to be set first as I have done it, uploaded the files and then changed dns on customer accounts on a reseller server.

In fact you may want to consider a reseller package as it will allow you to set up completely seperate accounts for all your domains, so they have their own seperate public_html or could use the extra tools in whm to modify your dns zones to possibly point to subfolders within an account?

[Serra]

Originally Posted by superbison

It seems pointless to use the add-on domain if I have to change the DNS, and wait until it propogates) in order to create it. My site will be down until I can upload the files and restore the DB. (what if there is an error?) How does that make sense?

You don't need to wait for it to propagate. You can normally change the dns and then create the addon a few minutes later. It does appear you need a reseller account or a dedicated server to do what you are trying to do.

[charlesgan]

Originally Posted by superbison

It seems pointless to use the add-on domain if I have to change the DNS, and wait until it propogates) in order to create it. My site will be down until I can upload the files and restore the DB. (what if there is an error?) How does that make sense?

there is hosting cpanel that allow you to addon domain as you like, even the DNS is not yet pointing to it. eg is here.

for some hosting like hostmonster, they require you to make the DNS changes first, once propagated, then only you can addon the domain at cpanel without error. then then upload your file. Which is subject to downtime at this migration.