Using WordPress in addition to an FTP program

They would be “sub-domains” and not the “motdaugrnds.com” domain

That is very easy to do at BlueHost, and the Support Techs there will help you, if you wish. I have that setup with a total of three sites there. First have their special .htaccess file ready (domain name in three places, as I recall) for upload via FTP (and you should have them set you up for SFTP to protect your login credential there), then move (or have a Support Tech move) your primary domain into a sub-folder you can name anything you wish…then put the .htaccess where it needs to be and log in. It really is that simple there, and you will not have to do anything more to make things continue working just as they do right now. Then after that, you can add as many domains as you wish with each being in a sub-folder of its own and completely separate from any other domain.
note: You could leave your primary domain right where it is, but it is more convenient for you while using FileZilla and more secure overall to have it in a sub-folder.

Leejosepho I want so badly to understand what you have just said; but I don’t understand.

I do want to do it all myself and not ask BlueHost to do it for me.

The only .htaccess file I’ve seen was in the server side of my FileZilla program. I have no idea how to get it ready (domain name in 3 places) for upload via FTP. (As far as I can tell, it is already uploaded as it is in the server side of the FTP program.) Nor do I know how to have BlueHost set me up for SFTP, though I’ve been wanting to do this. And when you said to “…move your primary domain into a sub-folder you can name anything…” I get confused.

I was told to place all my uploads into the “public_html” directory; so that is what I’ve done. Wouldn’t moving all these created directories, folders, html pages and images into a “sub-folder” (I guess you mean “different folder”.) and naming it anything at all mess up my html coding? (Wouldn’t I have to include this new folder to all my html codes just to access what I placed in there?)

Then you say to “…put the .htaccess where it needs to be and log in…” Where does it need to be? How do I move it? Login to what? Then you say, “…after I do all that, I can add as many sub-domains as I want with each being in a sub-folder of its own completely separate from my main domain…” This sounds good though I’m not sure what to do to accomplish it. And no, I don’t want to leave my primary domain where it is because, as you mentioned, I do want it all to be convenient for me when using FileZilla and more secure overall.

I’m so sorry I’m having difficulty understanding you. I’m not an auditory learner; so I have to be able to put all the words I hear into pictorial form to make sense out of them. I do so hope you will have patience with me and help me understand what you have suggested. It all sounds like what I want to do. I just have no clue as to the step-by-step process to get it done.

I understand, and I will try to simplify!

First, you will find the folks at BlueHost quite knowledgeable, friendly and helpful. To see that in action, open your BlueHost CP while also having FileZilla open, then give BlueHost Support a call to ask for SFTP setup. A Developer had taken care of that for me, then BlueHost later helped me do that at another account I help manage, so I do not know how to do that all by oneself.

Concerning a folder to contain your primary domain inside public_html: The deal there is to move your primary domain into its own unique folder inside public_html so your overall FTP navigation will be much simpler (and less confusing, at least in my own case) later on. You will go into public_html just like always and as you had been told, then move on into the unique folder for any site where *all* files for *that* site will be found rather than having the folders for your primary site scattered around inside public_html along with the folders for your sub-domains.

[I’ve already created directories, folders, html files and images for my motdaugrnds.com…working fine…]

I was told to place all my uploads into the “public_html” directory; so that is what I’ve done.

Understood, and you have actually uploaded your stuff into public_html/wp-content, correct?

Either way, go to public_html and make a new folder with any name you might wish, such as motdaugrnds (since BlueHost has something else as your root folder and that will make your new folder unique), then copy everything inside public_html (other than your new motdaugrnds folder, of course) over into that new folder…then take a look here (and ignore the part about “When using WordPress” since nothing there will be necessary):
https://my.bluehost.com/cgi/help/347

After getting that new .htaccess ready locally (see “Modifying the .htaccess”) for upload and either making a backup of the one that is already there or renaming it to .htaccess_old, you should next be able to upload that new file into public_html and begin accessing and running your site from its new location without anything being negatively affected. But if something is not right, just put the previous .htaccess back to work.

note: After you are sure all is well, you can later delete from public_html anything that is now in the new folder for your primary domain.

I am wondering if it would be best if I created “sub-domains” for my store and blogs, using WordPress strictly for those sub-domains.

I think I have covered that, but please let me know otherwise, if necessary. Overall, all of this can seem complex at first, but its actual simplicity is as true as I have stated:

1. Give BlueHost Support a call to ask for SFTP setup.
2. Copy your primary domain into its own unique folder inside public_html.
3. Make the new .htaccess file to tell BlueHost where to find your primary domain in its new folder.
4. Opload that new file into public_html and begin accessing and running your site from its new location.
5. If something is not right, just put the previous .htaccess back to work.
6. Add as many new folders inside public_html for as many sub-domains as you might wish to have.
7. Install a unique WordPress installation in each…and you will then find you have a unique database for each that you can access at your BlueHost CP.

Thank you so much for your patience. I actually “replied” to the notification of your post so I guess you won’t get that. So I’ll respond here.

I do understand that I need to create a new folder (I will name it motdaugrnds.) and place it into the public_html directory on the user side of my FileZilla program. I will then move all the files that I, myself, created into that folder. However, there are files in that public_html folder that I did not create myself, such as the “cgi-bin”, “wp-admin”, “wp-content” & “wp-includes”. Should I move those into the new motdaugrnds folder too? (I did not use WordPress for what I created that is being moved into the new motdaugrnds folder; however I will be using WordPress for the sub-domains which have not been created as yet.)

No, I have not uploaded anything into public_html/wp-content. I have not used WordPress as yet to create anything; so all I knew to do was move what I had created myself into the public_html directory….not /wp-content.

I did go over to that URL and, though the first part of “locating the .htaccess file in the File Manager” was clear enough for me to do, the “Modifying the .htaccess” is terribly confusing. And how to upload it even after I figure out how to modify is confusing as well, though I certainly understand renaming the old .htaccess just in case the new one doesn’t work and I need to use it. And where to upload the new file to or how to do this when it is not on my personal computer files is beyond me. And when you say, “…note. After you are sure all is well, you can later delete from public_html anything that is now in the new folder for your primary domain.” are you saying to delete all my directories, folders, html files and images that I have created for my primary domain and had moved into the new motdaugrnds folder? I doubt this is what you’re saying, so I don’t understand your note.

Your last 7 sets of instructions are so very clear. Thank you so much for those. I think it is what to do with the .htaccess file that is giving me the most problems now. I simply don’t understand that process. I do know you have tried so hard to help me understand and I am so grateful for your patience. It is still very confusing. ??

Thank you so much for your patience.

No problem at all.

I actually “replied” to the notification of your post…

Yes, that is in my box, but I had not yet been there and typically just look back here anyway.

…there are files in that public_html folder that I did not create myself, such as the “cgi-bin”, “wp-admin”, “wp-content” & “wp-includes”. Should I move those into the new motdaugrnds folder too?

*Copy* for now (for overall safely), not move, and those are your WordPress folders that constitute your WordPress installation for that domain no matter what else you might have in there. So again, just copy everything there into public_html…and as a preview for later, my own public_html now looks like this:

..
cgi-bin (folder)
WPsitea (folder)
WPsiteb (folder)
WPsitec (folder)
.htaccess
favicon.ico
php.ini

note: That php.ini is generated at your BlueHost CP to cover PHP for youe entire BlueHost account, and you should not mess with that until being sure you understand how BlueHost handles PHP.

I did not use WordPress for what I created that is being moved into the new motdaugrnds folder; however I will be using WordPress for the sub-domains which have not been created as yet.

I do not know *exactly* what all you are doing there, so just copy everything in and then later delete whatever is actually not necessary, if you wish. BlueHost only complains when someone uses their account for storing stuff that is not site-related.

No, I have not uploaded anything into public_html/wp-content. I have not used WordPress as yet to create anything; so all I knew to do was move what I had created myself into the public_html directory….not /wp-content.

Question: Are you actually accessing any of those things as a site or whatever at the moment or simply storing those things for now to be used by WordPress later?

I did go over to that URL and, though the first part of “locating the .htaccess file in the File Manager” was clear enough for me to do, the “Modifying the .htaccess” is terribly confusing.

That simply amounts to adding your specifics into these lines as noted:

# Change example.com to be your main domain.
RewriteCond %{HTTP_HOST} ^(www.)?motdaugrnds.com$
# Change 'subdirectory' to be the directory you will use for your main domain.
RewriteCond %{REQUEST_URI} !^/motdaugrnds/
# Don't change these line.
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
# Change 'subdirectory' to be the directory you will use for your main domain.
RewriteRule ^(.*)$ /motdaugrnds/$1
# Change example.com to be your main domain again.
# Change 'subdirectory' to be the directory you will use for your main domain
# followed by / then the main file for your site, index.php, index.html, etc.
RewriteCond %{HTTP_HOST} ^(www.)?motdaugrnds.com$
RewriteRule ^(/)?$ motdaugrnds/index.php [L]

Caution: Make your own file to be sure of accuracy; do not just copy-and-paste from there, please!

And how to upload it even after I figure out how to modify is confusing as well

Via FTP into public_html to tell BlueHost to point motdaugrnds.com to its new location.
note: You will later do that pointing for your *sub-domains* at your BlueHost CP, but your primary domain gets re-pointed here.

And where to upload the new file to or how to do this when it is not on my personal computer files is beyond me.

Copy that file content from the page at the link I had provided, then add your info (as above) and then save all of that locally in plain text as your new .htaccess file to later be uploaded via FTP.

And when you say, “…note. After you are sure all is well, you can later delete from public_html anything that is now in the new folder for your primary domain.” are you saying to delete all my directories, folders, html files and images that I have created for my primary domain and had moved into the new motdaugrnds folder? I doubt this is what you’re saying, so I don’t understand your note.

I was saying you can eventually delete one set or the other after everything is working as it should with whichever set is being used. Or, of course, you could just leave both intact with one being a backup.

I think it is what to do with the .htaccess file that is giving me the most problems…

Just let us know if the above is not yet quite clear.

You are a wonderful person. Thank you so much for your kindness in helping me and your patience in dealing with my questions. I do realize I must sound terribly dumb. (I’m really not. I actually have an I.Q. of 152; however, I am such a visual learner that it has always presented a problem in communicating with others.) I do so much appreciate your patience. Creating this website is important to me at this time in my life; and I’ve little doubt if it were not for people like you, I would not get it done.

In answer to your question, “…Are you actually accessing any of those things as a site or whatever at the moment or simply storing those things for now to be used by WordPress later?” I am accessing all I’ve put up and am not saving anything to use with WordPress.

The “motdaugrnds” changes I see you’ve made are very clear where they are. It is the first few # I don’t follow.
#.htaccess main domain to subdirectory redirect
#copy and paste the following code into the .htaccess file
#in the public_html folder of your hosting account
#make the changes to the file according to the instructions.
#Do not change this line.

Are these simply telling me that in order to redirect the .htaccess attached to my main domain, I am suppose to copy/paste the code with the changes you specify (as to where motdaugrnds should go) and without changing certain lines into the public_html and, thereby, replace the .htaccess file that is there now?

Like this:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(www.)?motdaugrnds.com$
RewriteCond %{REQUEST_URI} !^/motdaugrnds/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /motdaugrnds/$1

Then wherever I see the word “example” or “subdirectory” replace those with “motdaugrnds (without quotes)
followed by / then the main file for your site, index.php, index.html, etc.

And this would look like “motdaugrnds/index.html ” simply because all my folders have “index.html” in them?

Then the next two lines of the code would look like this:
RewriteCond %{HTTP_HOST} ^(www.)?motdaugrnds.com$
RewriteRule ^(/)?$ motdaugrnds/index.html [L]

Is this the “code” I’m suppose to copy/past?

What do you mean, “…Make your own file to be sure of accuracy; do not just copy/paste from there…” Are you sayin the above code is a “file” and that I should type it onto a separate page instead of copying and pasting it where I found it? If so, I don’t know how to make that upside down lower case “v” in front of the (/)?$ seen above.

If I’m understanding you correctly, I am literally creating a page on my computer with that code on it and uploading it as a “.txt” via FileZilla into public_html (not into my new motdaugrnds folder). Is this correct? Just type the code on a page with no html coding of any kind and put a .txt extension on it as I name it .htaccess for uploading?

I do understand all I would be doing with this page.txt (code) is telling BlueHost to point motdaugrnds.com to its new location which is inside the newly created motdaugrnds folder and that this will not have anything to do with sub-domains I will be setting up. Is this correct?

Ummm, your answer of “…Copy that file content from the page ‘at the link I had provided’ then add your info … (the “motdaugrnds” changes), then save all in plain text… (This must be the .txt extension.)….” It is the latter part I’m not real sure about, i.e. “…as your new .htaccess file to later be uploaded via https://FTP.” Are you saying to replace the .htaccess file in that public_html folder with this .txt page? If so, should this page be named .htaccess.txt ? ROFL I think I just answered my own question; so maybe I’m making some progress here. ??

Ummm When you talk about deleting all my directories, folders, html pages and images, you are meaning that instead of “moving” all of them into the newly created motdaugrnds folder, I have simply “copied” them into it to be on the safe side in case the re-routing did not take place appropriately. Is this correct? And if it is correct, how will I know the re-routing did not work? (Since all I’ve created would still be in the public_html even though all of it is also in the newly created motdaugrnds folder, wouldn’t it continue to show up on the internet anyway even if the re-routing did not work?

Again, I simply cannot thank you enough for hanging in with me on this. My gratitude is surely yours.

I actually have an I.Q. of 152; however, I am such a visual learner…

You and I could be twins in that department, and we are actually not alone here.

I am [presently] accessing all [of my own stuff] I’ve put up and am not saving anything to use with WordPress.

I have just visited your site, and I have also just spoken on the phone with a BlueHost Support Tech about your particular kind of situation. At the moment, and while I have no idea what you presently have in any .htaccess file anywhere, you apparently have one that points incoming motdaugrnds.com traffic to your HTML work…and the .htaccess file we have been talking about here will re-point *all* of that traffic to your WordPress installation after it has been moved/copied into its new folder. If that is not what you want to do, then do not make the .htaccess file we have been talking about. Rather, you would have to find someone who can help you with how to direct traffic away from your HTML work and on into your WordPress installation…and then on the other hand, of course, you could proceed with this .htaccess file and then do whatever is needed to link back out to your HTML work.

The “motdaugrnds” changes I see you’ve made are very clear where they are. It is the first few # I don’t follow.

The hash mark “#” indicates a comment line with a note saying what you need to do in a line or lines below it in order to make the proper .htaccess file.

I am suppose to copy/paste the code with the changes you specify (as to where motdaugrnds should go) and without changing certain lines into the public_html and, thereby, replace the .htaccess file that is there now?

If you wish to re-point all traffic to your WordPress installation in its new folder, yes, later on. Otherwise, do nothing at all with that file for now.

Then wherever I see the word “example” or “subdirectory” replace those with “motdaugrnds (without quotes)
followed by / then the main file for your site, index.php, index.html, etc.

Yes, and you have likely already noticed those characters to be changed are highlight at the BlueHost page where you see that file.

And this would look like “motdaugrnds/index.html” simply because all my folders have “index.html” in them?

I do not have an answer there since I do not know whether you wish to proceed with preparing to re-point all inbound motdaugrnds.com traffic to your WordPress installation after it has been moved/copied into its new folder.

Then the next two lines of the code would look like this:
RewriteCond %{HTTP_HOST} ^(www.)?motdaugrnds.com$
RewriteRule ^(/)?$ motdaugrnds/index.html [L]

Please see my previous answer…yet here I would add that the BlueHost Support Tech had his eye on that last line while considering his own answer in a situation where someone’s HTML work and a WordPress installation might co-exist and/or interact.

What do you mean, “…Make your own file to be sure of accuracy; do not just copy/paste from there…” Are you sayin the above code is a “file” and that I should type it onto a separate page instead of copying and pasting it where I found it?

No, I meant to suggest you not simply copy what I had posted here. If you wish to proceed with a new .htaccess file, copy the sample from the BlueHost page then make your changes and save your work as a new file.

If I’m understanding you correctly, I am literally creating a page on my computer with that code on it and uploading it as a “.txt” via FileZilla into public_html (not into my new motdaugrnds folder). Is this correct?

Other than the “.txt” part, yes. However, .htaccess is actually a nameless file with .htaccess as its *extension*, not a name, so you will need to be using an editor that will allow you to save it that way.

I do understand all I would be doing with this [new] (code) is telling BlueHost to point motdaugrnds.com to its new location which is inside the newly created motdaugrnds folder and that this will not have anything to do with sub-domains I will be setting up. Is this correct?

Correct, but doing that will also completely bypass your HTML work presently being displayed at motdaugrnds.com.

“…as your new .htaccess file to later be uploaded via https://FTP.”
Are you saying to replace the .htaccess file in that public_html folder with this [new one]? If so, should this page be named…

See above.

When you talk about deleting all my directories, folders, html pages and images…

Please ignore all of that now since it seems you will only be copying or moving your WordPress installation.

Edit PS: One thing you *could* do here as a test is to proceed with the WordPress copying/moving and the new .htaccess file, then simply switch from one htaccess to the other to display whichever you wish at motdaugrnds.com. And to make that easy to do, make a WPmotdaugrnds folder and an HTMLmotdaugrnds folder there on your computer so you can save the respective .htaccess files there in a way that easily distinguishes one from the other while making each easy to grab.

=============
Copyright notice: Copy at will, just be sure to “copy it right”!

OMG I’m so glad I’m going slowly.

You state, “…At the moment…you apparently have one (.htaccess file) that points incoming motdaugrnds.com traffic to your HTML work…and the .htaccess file we have been talking about here will re-point “all” of that traffic to your WordPress installation after it has been moved/copied into its new folder…”

I’m sorry I confused you. At this time I have nothing created by WordPress to move/copy into a new folder. I thought you understood I had not used WordPress to do anything and have everything working well using html coding I created myself using Note Tab light and uploading via FileZilla. I do have WordPress “installed” into that domain but I have not used it at all.

So are you now saying the sub-domains I have set up at BlueHost and installed WordPress to cannot be connected to my main domain because my main domain was created with html coding and was not created by WordPress? Thus, any hyperlinks I add to my existing pages that would direct to my sub-domains will not work?

No, all is well so far, and I also like going slowly to be certain at each step!

At this time I have nothing created by WordPress to move/copy into a new folder.

Understood, but you do have the WordPress folders in public_html, and moving that WordPress installation into its own folder is a good idea for a bit of added security and to facilitate good organization and clear FTP navigation. After moving your WordPress installation, your public_html would only contain your HTML work and possibly look something like this:

..
cgi-bin (folder)
HTMLfolder01
HTMLfolder02
WPsitea (folder)
WPsiteb (folder)
WPsitec (folder)
.htaccess
favicon.ico
htmlfile01
htmlfile02
htmlfile03
htmlfile04
php.ini

At the moment, you have your HTML work and all the folders and files for your WordPress all intermingled there inside public_html. That is fine as far as function is concerned, but the above is much easier on the eye and brain when I go looking for something specific at my own FTP account.

I thought you understood I had not used WordPress to do anything and have everything working well using html coding I created myself using Note Tab light and uploading via FileZilla.

I had understood and still do. What I do not know is how you intend to have your HTML work and WordPress interconnected.

So are you now saying the sub-domains I have set up at BlueHost and installed WordPress to cannot be connected to my main domain because my main domain was created with html coding and was not created by WordPress? Thus, any hyperlinks I add to my existing pages that would direct to my sub-domains will not work?

No, I am not saying that at all.

Question: Do you intend for motdaugrnds.com to always land at your HTML work where hyperlinks would go to WordPress things? If so, do not make any .htaccess changes just yet since the file we have been talking about would need some additional modification.

I just sent you two (2) emails responding to this; but will re-iterate here for your possible convenience.

FIRST EMAIL I SENT TO YOU:
What I’ve done so far and what I want to do is now not only much more clear but can be organized in such a way that keeps my main domain (including the WP files connected to it) separate from the sub-domains, which I want to use WP to create. I am feeling so more relaxed now and quite good. Thank you so much for hanging in with me thru all this turmoil.

What you’ve said is still a bit confusing, i.e. “…After moving your
WordPress installation, your public_html would only contain your HTML work and possibly look something like this…” and you go on to list what looks like what is in my public_html now. This is confusing. Isn’t it true that, when I create that new “motdaugrnds” folder, move all my html directories, folders, files & images (plus the WP folders/files) then the public_html directory would have nothing in it except that one new motdaugrdns folder plus the 4 new sub-domain folders? Then when I open the new motdaugrnds folder, it would show all those files you listed in this latest email to me? And when I open each of the sub-domain folders, they would only show what WP
has placed in them thus far?

If I’m understanding you correctly now, I should go ahead and create the new “motdaugrnds” folder, placing it into the public_html directory on the FileZilla server. (BlueHost told me to do this from my account and not thru the FileZilla program.) Only instead of moving all the html directories, folders, html files and images into it, I would only move the WP folders/files into it? No, wait, I should place EVERYTHING (all my html work plus all the WP folders/files) into that new motdaugrnds folder? When that motdaugrnds folder is now opened it would contain both what I’ve created PLUS the WP items connected to it and look similar to what you have listed. Is this correct?

I am a bit unclear about what gets moved.

The only thing we have been discussing that I would NOT DO is change the
.htaccess file?

SECOND EMAIL TO YOU ANSWERING QUESTIONS:
Question: What I do not know is how you intend to have your HTML work and WordPress interconnected.

Answer: I have no real understanding of how to do this. The only thing I can think of is to put some html coding into my html pages that send traffic over to the sub-domains. It would be a simple html hyperlink. I have no idea whether or not that would be recognized by the WP coding in those sub-domain folders.

Question: Do you intend for motdaugrnds.com to always land at your HTML work where WordPress things will then be available? If so, do not make any changes related to .htaccess just yet since the file we have been talking about would need yet some additional modification.

Answer: Yes. I want motdaugrnds.com to always land at my HTML work. Then send traffic from my html work over to the WP things in my sub-domains.

I just sent you two (2) emails responding to this

Please note that these forums do not provide support by email. Please keep all discussion on the forum so that all community members will benefit.

Thank you.

Please keep all discussion on the forum so that all community members will benefit.

Most certainly.

#motdaugrnds: Back to you here in a few minutes…

…can be organized in such a way that keeps my main domain (including the WP files connected to it) separate from the sub-domains, which I want to use WP to create.

We will have to talk more later about your mention of “sub-domains, which I want to use WP to create”, but for now, yes, overall organization is key. When I first started doing any of this stuff just under a year ago, I clicked a SimpleScripts button at BlueHost and my primary (WordPress) domain was installed for me inside public_html. That was fine at that time, of course, but then I later began having difficulty knowing exactly where to go for doing whatever via FTP after I had added two sub-domains as separate WordPress installations in their own folders. So to get rid of that “problem” (at least for me), I next moved my primary WordPress installation into a folder just like SimpleScripts had made for my sub-domains. So overall, my own experience now causes me to suggest you do the same even before ever using your WordPress for the very first time.

What you’ve said is still a bit confusing, i.e. “…After moving your WordPress installation, your public_html would only contain your HTML work and possibly look something like this…” and you go on to list what looks like what is in my public_html now. This is confusing.

Question: Where do you have any folders beginning with wp- (admin, content, includes)?
Either inside public_html or elsewhere, a typical (default) WordPress installation has folders with those names plus an .htaccess file as well as several files ending in .php.
Where are those folders and files right now?

Isn’t it true that, when I create that new “motdaugrnds” folder, move all my html directories, folders, files & images (plus the WP folders/files)…

You might have just answered my question there, and do not “move all my html directories, folders, files & images” anywhere. No matter what else you do, leave those right where they are so they can continue working just as I assume they already do (or in whatever state they might happen to be at this moment). If you already have “the WP folders/files” you have mentioned in some location other than public_html, that is possibly already what I am (or have been) suggesting as far as a motdaugrnds folder is concerned.

…then the public_html directory would have…plus the 4 new sub-domain folders?

Question: Do those “4 new sub-domain folders” already exist? If so, that is fine, but I have been uncertain about that as we have been going along here.

Then when I open the new motdaugrnds folder, it would show all those files you listed…

Just put all of that on hold for the moment…

And when I open each of the sub-domain folders, they would only show what WP has placed in them thus far?

In principle, yes. WP places images and such inside one or more folders inside wp-content while storing and retrieving everything else in/from your database…and in your case (as in my own), that will happen in each separate instance of a WP installation, respectively and exclusively.

If I’m understanding you correctly now, I should go ahead and create the new “motdaugrnds” folder…

No, not until we clarify your mention of “4 new sub-domain folders”.

Only instead of moving all the html directories, folders, html files and images into it, I would only move the WP folders/files…

In principle, yes, but maybe wait on that until we have the above completely clarified.

No, wait, I should place EVERYTHING (all my html work plus all the WP folders/files) into that new motdaugrnds folder…

One of my original suggestions was to have you do that for the sake of having a backup of all your HTML stuff, but that is optional.

Question: What I do not know is how you intend to have your HTML work and WordPress interconnected.
Answer: I have no real understanding of how to do this. The only thing I can think of is to put some html coding into my html pages that send traffic over to the sub-domains. It would be a simple html hyperlink. I have no idea whether or not that would be recognized by the WP coding in those sub-domain folders.

Those are the kinds of things esmi or someone else can help you do where I cannot, so just keep all of that on hold for now.

I want motdaugrnds.com to always land at my HTML work. Then send traffic from my html work over to the WP things in my sub-domains.

That makes your overall plan quite clear, and now we just need to do these things:

1. First be sure all folders and files are in their logically-proper (final) locations for ease (convenience) during FTP navigation.
2. Do whatever is necessary for WP to begin working properly (for the first time) and completely right wherever it might (then) be.
3. Add any new sub-domains not already in place and be sure each is doing the same.
4. Enjoy!

ESMI, I will do so. Thanks for letting me know.

Lee, To clarify what has been done.

I created my entire main domain using html coding without using anything from WP. All those directories, folders, html files & images are in the public_html directory.

I’ve already created four (4) sub-domains, installed WP on all four and will be using WP to create all of them.

Here is what is now showing up on the server side of my FileZilla program under the public_html directory: (Individual files were also found and are listed innext post.)

(folder with ?) cgi-bin … This is empty at this time
(folder with ?) developing-small-farm … This is one of four sub-domains I want to use WP with.
(folder with ?) education-relationships … This is one of four sub-domains I want to use WP with.
(folder with ?) educational … This is one of my html folders
(folder with ?) farm-sales … This is one of four sub-domains I want to use WP with.
(folder with ?) howitwasalldone … This is one of my html folders
(folder with ?) inspirational … This is one of my html folders
(folder with ?) inspirations … This is one of four sub-domains I want to use WP with.
(folder with ?) wp-admin … I didn’t even open this.
(folder with ?) wp-content … I didn’t even open this.
(folder with ?) wp-includes … I didn’t even open this.

When opening each of the 4 sub-domain folders, this is what is in each one: (If I remember correctly, they are all folders with ?)
cgi-bin
wp-admin
wp-content
wp-includes

Yes, my entire site works fine at this time. I have not put any links to any of the sub-domains and will not do so until they are ready to be linked to. Thus, those will just sit until I learn how to use WP to create them (one store and 3 different types of blogs). Then I’ll add some html coding that will link them to my main domain. (Just heard from BlueHost about this and was told in so many words that a link is a link is a link, i.e. if I create a hyperlink in my html coding to take me to the WP created sub-domain, it will connect to that sub-domain without problems. At least this is my understanding of what BlueHost said in an email today.)

Hopefully, we are on the same page now??

I will be working within the WP program for awhile now to create the contents of each of those four sub-domains. I’m not looking forward to this because of the problems I initially had trying to work within the WP program to develop my main domain. It just got so confusng, I quit and started using my Note Tab Light to create all the content in that main domain, then uploaded it using the FTP FileZilla program. I am hoping I won’t find WP this confusing again.

It was my understanding WP was a user-friendly program and anyone with half a brain could create a workable store and a workable blog with it. I will be finding out as soon as I catch my breath from what you and I have just been thru…whew! (Wishing I had a strong drink!)

Here are the individual files I found in that public_html directory on the server side of FileZilla. I have no idea how they got there are what they are for. I’m hoping I can delete them in order to clean up a bit. (This list does not include the WP “folders” mentioned above.)

.htaccess
400.shtml
401.shtml
403.shtml
404.shtml
500.php
500.shtml
default.html
favicon.ico
index.php
license.txt
readme.html
wp-activate.php
wp-blog-header.php
wp-comments-post.php
wp-config-sample.php
wp.config.php
wp-cron.php
wp-links-opml.php
wp-load.php
wp-login.php
wp-mail.php
wp-settings.php
wp-signup.php
wp0trackback.php
xmlrpc.php

Can I get rid of all this or should I leave some?