I've been using DreamWeaver for a decade on a PC with no issues connecting to network servers via Local/Network. I was recently switched over to a Mac and now I have trouble getting sites to connect to the correct server. The problem seems to be that on Mac, DW renames every server to "Volumes." We have multiple servers with the same exact file paths, where only the server name is different. For example, for our Web site files:
Our local/testing server (Local Site Folder) might be \\ServerA\d$\WebFiles
Our remote server (Server Folder) would be \\ServerB\d$\WebFiles
So, once I connect to the testing server in DW, then try to connect to the remote server to "Put" files, it just keeps connecting to the local server because it thinks they are the same server!
When I go back into Manage Sites to check the file paths, sure enough, it replaces each server name with Volumes so now the site has:
Local Site Folder: /Volumes/d$/WebFiles
Server Folder: /Volumes/d$/WebFiles
Exact same path. I try changing both back to the server names but every time I save, it goes back to "Volumes."
Because of this issue, there is no way I can Get/Put in DreamWeaver for the Mac. Is there a special way to designate which server is which on the Mac?
The local path needs to be written as the "volumes". It's the Windows equivalent of using a Network Drive letter. If you have not set up the volume in the Mac Finder you will run into issues. DW was originally intended to have all files locally on your computer with a different testing server and different web server. The fact that you have the "d$" name suggests to me that these are Windows servers that are you connecting to. This article should help you map a drive that reconnects ( http://osxdaily.com/2012/05/04/automatically-connect-to-network-drive- mac-os-x/ ).
As far as the remote, for this DW should be allowing a network address because it is never assumed that the testing server is local on the computer. This may end up being a bug, but let's see if we can correct one problem at a time.
Thanks for the advice. Yes, the servers in question are Windows.
I tried mapping the reconnecting drives per the article you provided, but have not been able to get even that to work because apparently Finder is also confused by the matching file paths. When I log in, it does connect to the two drives, but they both show the contents of the same server every time. After connecting to one server, I have to eject the volume and THEN connect to the other server.
I don't think this will ever work as long as those two servers have the exact same file path. I am now doing all of my file transfers on a Windows virtual machine instead of within DreamWeaver (I don't have a license of DW for Windows available to me at work), because that is the only way I can connect to both servers at the same time. Oh well!
Did anyone ever find a solution to this? I'm dealing with this now. I've mounted two network drives and dreamweaver cannot recognize them when they are mounted together.
For instance, Here's an example of the servers:
I can mount those and access them through finder and they work properly, but in dreamweaver, I can only access one at a time... usually the first one I mount. This is a pretty big issue as we have a lot of servers at my company that I don't manage that all have very similar file structures and there's no way I can change the file structure.
Please help with this issue. It's very frustrating.
I never found a solution, and the problem still exists for me. Even if I mount both servers in the Finder before opening DreamWeaver, DW only recognizes the first one that I mounted.
Now I just mount the production server and when I am done editing the files, I go to my finder to transfer the files to the live server. It's a huge pain and VERY frustrating.
This is what I'm looking at right now, but not knowing much about macs, I'm not sure how to do it. It seems to have worked for a few people. Maybe you could get it to work and then post here how to do it for someone who doesn't know macs very well and/or command line commands.
The second to last post has a terminal command that you can use.