Things work . . .
. . . but the directory structure is whacked. There must be something that is not being built correctly on this end. Here's what I see . . .
If the sub-directories of the webhost exist below the root then that structure has to be described/mirrored on the "local" design station. This is true for all sites, correct?
So, if the website's hosted structure consists of:
html (where all "pages"must be in html)
The "local" structure is:
S:\Websites\yourwebsite\ (as the root in Dreamweaver's Manage Sites panel), so you can then upload a directory named "html" and the pages within it. When the "local" design station takes a page, and an eCart Object is described, the "WA_eCart" directory is placed on the same level as "html". But that configuration yields the "../WA_eCart/eCart1_PHP.php" etc. path reference plus the .js "not located on this server" message ("../WA_eCart/Scripts/copyShipping.js). Links are relative to document, correct?
If the "local" root is described as:
S:\Websites\yourwebsite\html (as the root in Dreamweaver's Manage Sites panel)
Then the described "eCart Object" must be placed as a sub-directory of html because the "html" directory designation is not viewable, so no "upload" of a WA_eCart directory will be visible as it's one level "up" from this "root". With the "eCart Object" (WA_eCart/eCart1_PHP.php) within the "html" directory, all scripts & pages "work" online & in DW but the "pages" on the design station (DW) cannot find the eCart Object (if you double-click on a server behavior, for instance, or click on the eCart Object icon in the eCart menu bar). And, all uploads place the "corrected" pages on the same level as the html directory, not "in" html, so they do not display (fixed is not "fixed") . . .
At least, that's what's happening here . . .
What am I missing?