Copy link to clipboard
Copied
I have a local IIS server used for local testing. I also have a cloned site used with a remote IIS testing server at my hosting company. I clone the remote testing site for production once approved by clients. Under Dreamweaver CS6, with the local test site or cloned site, when a file was changed or is rendered using F12 for Firefox (or alt-F12 for Chrome) the page was updated automatically on the testing servers.
Now, under Dreamweaver CC 2017 the pages are not being updated on either testing server. The update does not happen when I use the Real-Time Preview (RTP) capability and also when I right-click on the file to render it in the chosen browser on my local IIS server or remote IIS server on the cloned site. The automatic update function is not working for RTP or when directed to a specific testing server. I must "push" the file to testing servers or RTP for the file to be updated and rendered in the browser of choice.
Should I rollback development to CS6 until this is fixed?
CC 2017.1 on Win10 using the site set-up described above. When I save files locally, they are automatically updated on my local testing server. However, I must refresh browser (F5) to see changes.
Chrome can be especially sticky about caching. Try using a different browser. Or get the Clear Cache extension for Chrome.
Nancy
Copy link to clipboard
Copied
Please have a look at How to set up connection between Dreamweaver and the publishing server especially the part about Advanced server options.
Copy link to clipboard
Copied
Ben,
Thanks for the advice but the server settings, to include the advanced settings, on my CS6 server setup are the same for my CC 2017 setup. The files on my CC 2017 setup are not being updated on the testing server when I render the pages under RTP or with my localhost testing server.
Copy link to clipboard
Copied
Pushing files to local testing server is not necessary if your local site folder resides in your testing server's web directory. See screenshot below.

That said, when I want to view files on my localhost, I prefer to use the old Preview in Browser feature. To access it, right-click on open document tag (or a file in your Files Panel). Select Open in Browser.
Nancy
Copy link to clipboard
Copied
Nancy,
I also use the old "Preview in Browser" using the right-click. This renders the page using my localhost as opposed to the RTP. However, the pages are not being automatically updated on the my localhost testing server using CC 2017 like that are using CS6. I have to "push" the pages with CC 2017.
Copy link to clipboard
Copied
CC 2017.1 on Win10 using the site set-up described above. When I save files locally, they are automatically updated on my local testing server. However, I must refresh browser (F5) to see changes.
Chrome can be especially sticky about caching. Try using a different browser. Or get the Clear Cache extension for Chrome.
Nancy
Copy link to clipboard
Copied
Nancy,
Thanks for the update. I could be a caching problem with browsers. It's hit or miss depending on the browser. I'll try the extension and other solutions to see what works for the different browsers.
If I find solutions, I'll post them to the discussion.
Carl
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more