if you click icon on the right of destination folder and you then move with buttons on top to higher level (level up) then select the public folder and press ok. This way it goes all automaticly.

Then you can upload hopefully without error, you can also choose tp press no if screen comes up, upload will then also start. Do this only if you are sure all info is correct.

Hi Andre.  Attached is an image of the Export screen, where I left the destination folder empty and clicked on the folder to the right. Another screen pops up.  There appears to be a "public_ftp" and a "public_html" folder.  Do I click on one of those?  Also, I have several websites under one account on GoDaddy, so I want to make sure the path goes to "thevanstonegroup." Also, if I highlight one of those "public" folders, nothing goes into the path of WebsiteX5 destination folder.  And the path on the top of the "Select the folder that you want to publish to the website" remains with just a forward slash. Not sure what to do at this step. 

Hello Charlene, if you have several websites they should have a different login / ftp adress

but you can also have several website in 1 account by adding other folders. 

for instance if you make several language projects you could make default: mywebsite.com and for let's say german, make an extra folder and then make a new project in german and then upload to mywebsite.com/DE  you have to make an de folder in that case within the original one.

But anyway if you have several account i assume you have also different ftp server adres.

you need to pick for the standard website public_html, if you select that or double click or select and press ok, x5 should close the window and it should set this path in the destination folder (normaly it is with a / before) but this can be different for other hostingparty, it is not a standaard rule. I have checked at godaddy FAQ and found it should be public_html .

Maybe I am getting a little closer with your help.  My websites all have the same FTP address.  When I click on the Destination Folder, then click on the public_html, I get the image below - which shows both thevanstonegroup.com and hiddengardenart.com.  So I double-clicked on "thevanstonegroup.com" folder.  It inserted the same path tried earlier this morning.  "/public_html/thevanstonegroup.com"  When I clicked on start, I got the message, again, "The selected destination folder does not match the url. Do you want to set it now?" I think last night I tried clicking on "no" and then it proceeded, but the result was that the website didn't go live. Any idea what I may be doing wrong? 

Charlene, i think your main website is https://hiddengardenart.com/

to upload there use only public_html

This is your main adress!

is that correct? if so:

Then make a folder without com, you already have that. It will then be the same as with language example i gave;

make a folder:  thevanstonegroup

select that folder for upload, but change before that your website url,

this will be: https://hiddengardenart.com/thevanstonegroup

if you want your own name like https://thevanstonegroup.com you need to ask godaddy for another website space (this costs extra money and you will get another login)

Hope it's clear if not let me know.

My primary domain with GoDaddy is tecnofoto.net.  Below is a print screen of my cPanel at GoDaddy. Based on your explanation, maybe I should be putting "http://tecnofoto.net/thevanstonegroup" ??   I just want to make sure I don't replace anything on the HiddenGardenArt site yet. With the new site on vanstonegroup (which no one goes to) then we can test it for a few days, and then later make it live on HiddenGardenArt.  Meanwhile, I am in a chat quene waiting for GoDaddy to come on and maybe they will look at it from there end. Hoping that with  you looking at my cPanel listings you can either confirm what you said above, or provide additional instructions. So thankful for your review and help!

Andre -- I think this is good news.  GoDaddy said that the DNS was not uploaded.  He made a switch and it's starting to work (at least in my Edge browser, but not yet in Mozilla). He said it can take 2-24 hours to fully propogate. Not sure what all that means, but he sent me an article to read and hopefully when we go live I won't have the same issue. But at least the test site is up and we can start looking for errors! Thank you so much for your help!

Thanks again, Andre.  Of course, I just found another issue. I started a new post conversation. One step forward and two steps back!