The error is happening with Dreamweaver 21.2, using Cloudberry Drive 220.127.116.11 on Windows 10 and Windows 11.
We do not get the same error using Cloudmounter. We would switch but have already invested in CloudBerry Licensing.
Copy link to clipboard
For best results in DW, your local site folder should reside on your primary hard drive so the drive's files can readily communicate back & forth through your operating system without unwanted delays.
When working with dynamic PHP files, it helps to have a local Apache testing server installed so you can check files and process scripts on the localhost. I use Wamp server for Windows but Xampp is another good option.
To further on what Nancy said, I'm not sure a S3 server is the best use in your setup to store files. S3 servers cannot serve up anything dynamic and have a lot of limitations which is why you can't host more than a static site from it. Doing what you are doing could suggest that potentially multiple users are mounting these drives to do work which could lead to version-control issues which would create an inadequate testing environment. Have you considered moving your files to an EC2 server which can support web technologies and even run multiple servers for testing/prod and try to eliminate the need for that Cloudberry app?
We had started down the EC2 path as we as FSX storage. VPN costs were killing us. We already have dedicated VPN into rackspace where our web servers live. I may explore a storage option there.
That would be a better plan to have your web servers all tied together. Do you have a repo in your environment to push things from your testing to your prod server? If not, I would look into a solution to be able to setup a repo that you can store your site in and then push updates to a testing and production server. This way you don't need to mess with mapping drives to DW because anything not on your computer is where DW struggles in that instance, but is also why they built in the git support.