Skip to main content
July 16, 2021
Answered

DW doesn't recognize that there are files to synchronize (always an empty list)

  • July 16, 2021
  • 1 reply
  • 1646 views

In the past I did not have big problems with the synchronize feature of DW. But currently I have. I have a local folder and a remote folder (connected via SFTP). In the server settings in the site definition I activated "Maintain synchronization information" (of course).

 

When I upload files via right mouse click and the corresponding menu entry (I don't know the word in the English version), the upload is done correctly. But when I say "Synchronize", DW always tells me that there are no files to synchronize. Even if I create a completely new file, DW has nothing to upload!

 

I also tried this:

https://helpx.adobe.com/dreamweaver/kb/troubleshooting-synchronization-problems-dreamweaver-mac.html

 

But it did not help. What else can cause this problem?

 

I use the latest version of DW and Windows 10.

    This topic has been closed for replies.
    Correct answer

    You have my answer above.  Use the Adobe Cleaner Tool to remove it and start over with a fresh install.

     


    Now I have the solution! It was not DW directly, but the server I was uploading to.

     

    The root path in DW was "/var/www/". I was not allowed to write directly into that directory. But I could write into "htdocs" ("/var/www/htdocs/"). The local site root was "C:\wamp64\www\example.com\". On the local side all my files were also in "htdocs" ("C:\wamp64\www\example.com\htdocs\") and I only uploaded/synced those files.

     

    This worked sometimes (which is strange), BUT: DW obviously checks for permission in "/var/www/" (via the temp html file) and because I do not have permission, DW does not sync anything.

     

    So I had to adjust the folder rights on the server. So you could say, it was a server problem all the time. But why did it work sometimes and, even more important, why does DW check for permission in folders which I do not upload to?

     

    If you ask why I do not set the htdocs folder as root path for FTP: it's complicated. 😉 It has do do with Git in some way.

    1 reply

    Nancy OShea
    Community Expert
    Community Expert
    July 16, 2021

    Are you working within a defined local site folder? 

    Are all file residing on your primary hard drive and NOT a cloud drive like DropBox or Google Drive? 

     

    If yes, try creating a new site definition file. 

     

    For what it's worth, I NEVER use file sync.  Simply right click on your local site folder in Files Panel (F8).  Select >  Recently Modified files.  Hit the UP arrow to PUT files to server.

     

     

    Nancy O'Shea— Product User & Community Expert
    July 16, 2021

    What is a "defined local site folder"?

     

    The files are on my local and primary hard drive in the folder C:\wamp64\www\mysite\

     

    If I click on the mentioned menu entry, the same check is done like when I click synchronize. I do not see any difference. But I will test on Monday whether this will recognize my changed files. But I guess it will not find deleted files which should be deleted on the remote side, or will it?

    July 19, 2021
    Defined Local Site folder = Site > Manage Sites... Given that you're using a local testing server adds another layer to this. Is Wamp server on and are all PHP & Apache processes running?

     

    @Nancy OShea 

    (the quote is something you posted in my other thread, but it belongs here)

     

    Yes, I'm working within a defined local site folder. That's why I said "In the server settings in the site definition" in the first posting. 😉

     

    Wampserver and all processes (Apache, MariaDB and PHP) are up and running. But the local server is defined as "testing server", while the server with the SFTP connection is defined as "remote server".

     

    Today I tested the "Recently Modified files" feature. It does not recognize anything. So it's obviously the same as the synchronize feature. I have the problem at work and I just tested it at home, one local testing server and one remote SFTP server. Here it works. But as far as I remember it also worked for a short time at work.

     

    If just changed files would not be recognized, it wouldn't be such a strange problem as it is now, where even new files are not detected as missing on the remote site.