(From your lips to Adobe's ears. Crossing my fingers.)

In Site Manager -> Servers – double click on your [Remote Server definition]
Choose "Advanced" tab.
Testing Server -> Server Model:
choose PHP MySQL .
(or whatever is appropriate for your site – it would be whatever you chose for your REAL testing server. Or perhaps it doesn't matter, as long as it is not "none" – after all, it looks to your Testing Server definition for testing and running locally in DW).

Save.
That's it!

Under Site Manager -> Servers

for your Remote server definition name: checkmark "Remote", uncheck "Testing"
for your Testing server definition name : uncheck "Remote", check "Testing"

With these settings, everything works as expected !

————————————————————————————————-
IMHO: If the Remote site is Not being used as a testing server, I don't think it is appropriate, or correct to choose any Testing Server Model (other than "none") for the Remote (Non-Testing) Server definition. I see it as a bug introduced when CS5.5 overhauled it's Site Manager dialog box, but kept part of it's code using the legacy model. At best it is simply confusing.

To me, it makes sense to set a Server Model for the Remote Server Only if it IS Also the Testing Server.
Yet in such a case, having the drop down "Testing" server box in this location is redundant to having the Testing server Checkbox on in the "Server" main dialog. Worse, in fact, it allows contradictory settings (the hence the conflict I was experiencing) when: 1)Testing server Unckecked, and Testing Model: indicates a server model other than "none", such as "php MySQL", for example), OR 2)Testing server is Checked, but the Testing Server Model set to: "None".

Instead, I think in Site Manager -> Server dialog..
under the "Testing" column..
next to each Testing Checkbox..
-move the Testing Server Model drop-down box to this location.

This would keep everything clearly defined!
No Conflicts. No Confusion. Nothing hidden.

Thanks for the voice..
;)

I did not anticipate my response would have been read so soon, and was busy coming up with the (same) solution and writing it up. I guess also I didn't read Murray closely enough to see any difference from what I was doing.

Your response is quite Clear. :)

WOW! .

Thanks again for your response :D !

————————————————————-
For me, 95% of the time, I prefer Filezilla to upload, download, and view my remote server directory. But, there are a few circumstances when I prefer having DW upload my files, so this "fix" hardly impacts my workflow.
If I used DW for all, or most, of my remote operations, I would find it to be quite a pain!
In that case, I would find it easier to create two site definitions in Site Manager:
-One with a Testing Server.
-The other, (almost) identical, but with Only a Remote server.
Then just switch between the two "sites" from the File panel before/after uploading.
If you do this, you'll have to ignore following warning:
"The root folder you have chosen is the same as the folder for site '…'. This may cause some operations, such as synchronization, to work incorrectly. Proceed anyway?'
Just click OK. I think that if it is the only method you use for uploading files (to that site), synchronization could still work, but I haven't tested that.
I have never had problems by having site definitions with overlapping/nested folders. However, as I also use FTP software, I hardly pay attention to synchronization states. I'm interested in finding out if anyone knows how the above settup would impact synchronization tracking.

Murray's solution ("Create two sites") is a good one, although it seems slightly complex — however, it does seem to acknowledge that there's a problem with the testing server/remote server scenario.

I'd just set up the site twice in DW (that is, make two Site definitions) … once for the testing server, and the second one for the real (remote server).

Typically, when I'm designing sites for clients, I upload to a domain on our server where they can check out the progress, we can discuss, etc. However, once it's done, I just switch the DW Site definition (of the server location) to their server/web hosting account and upload the whole thing there.

This would be somewhat the same … just two Site setups for one website; use the one for the testing server while you're working on it, and switch to the other when it's upload time.

Does that make sense, and do you think it would work?

(And thanks for the compliment on my website.)

The first link, basically re-states my problem, but as you stated, there is no solution.

The second link, well the solution to the problem posed is exactly what I'm already doing..

I must say I am impressed you found articles related to my problem!
I have still had a difficult time finding a useful set of search terms for this particular issue. And still haven't been able to find a solution.

Thank You so much for taking the time to research and respond to my question.

Your Site is a Beautiful Site, By The Way..

:)
————————————————————-
I don't think I clearly indicated the configuration I chose; I hope you don't mind the recap..

-In site manager, I have the remote server setup.
This has been established for quite some time. Nothing there has changed.
TESTing my "Remote Server" via the link on its BASIC tab STILL Connects to my Web Server Successfully.
-I installed a testing server (on my computer). My local site files are still in "thehrprofessionalsgroup" directory, but it has been moved to reside under the XAMPP (htdocs) directory, as required by xampp. This is akin to the directory on your remote server which runs your live website(s).
-In site manager, I updated the "Local Site Folder," to the new location.
-In site manager, I added an "xampp Testing Server" definition. Doing so in DW (CS5 and above) allows visual editing of dynamic wordpress files – Handy! Love It. Point is, this Clearly indicates my testing server is setup correctly. Yea!

Problem:
Now, when I "Put" a file (from my local/testing location), instead of connecting, like it should, to the remote server, it establishes a "remote" connection back to my Local server. ..And I think it actually copies the file into itself. Very Weird.
It seems to ignore the Site Manager -> Servers – "REMOTE" checkboxes. It acts as if my "Xampp Testing Server" has Both "Testing" and "Remote" boxes checked, while my "Remote Server" has Neither..

But here's a solution from Murray, who's been a Team Macromedia Volunteer for Dreamweaver since before Adobe bought Macromedia: Managing sites: local, remote, testing.

I've had dreamweaver settup properly for my remote server.

I added a local testing server, which seems to be settup right – all works well UNTIL I try to
"Put" files to the remote server.

For some reason, it seems, instead to connect to the local XAMPP server. Of course, that means it just looks to see about overwriting the file with itself.

If there is a whole directory of files to upload, then I DW's file transfer dialog (not nearly as informative ad Filezilla's transfer logs) runs for a long time. In the end, I see no changes.

What could possibly be causing it to connect to the testing server to upload files?

BTW, in manager, "Test" seems to connect to the remote server fine. (Took me a few tries to get that right initially), and if I change anything, including password, It no longer connects – this is the only clue I have that it's Testing the Remote connection, rather than simply connecting locally to the testing server !

? Any Suggestions ?

Cheers,
Geoff