Skip to main content
Known Participant
November 3, 2016
Answered

(DW CC 2017) Disable Real-Time preview... conflict with MAMP

  • November 3, 2016
  • 20 replies
  • 23817 views

Hello,

I'd like to disable the Real-Time preview in the new DW CC 2017 because not allow to open the webpages with custom urls of MAMP.

Now when use the keyboard alt/command-f12 shortcut, all the pages in the browser has the wrong url "http://127.0.0.1:62370/" instead of the "web url" indicate in the "Site Setup" for testing server (ex. http://weblocal.mydomain.com).

How to disable it?

Thanks.

This topic has been closed for replies.
Correct answer Prashanth Nethi

Sorry for the inconvinence. Though the address in the browser is pointing to 127.0.0.1,  the content is getting served from the actual server if any.  Actually we are loading all of the content from any testing server, if defined, in an iframe that is embedded inside the HTML that is being served from 127.0.0.1.

chrishuffman​ and everyone who i facing the issue with local preview. are you having any difficulty getting the preview right ?

you could get the legacy preview by selecting  file in the files panel -> right click on the Selected file -> choose Open in browser option. Also this is available in the context menu of the document tab.

20 replies

Participant
November 16, 2016

Please refer to the following post to bring back F12 functionality to be launching file preview.

Note: With this hack, real time preview would be completely disabled.

DW CC 2017 how to get back old F12 functionality

Participating Frequently
November 16, 2016

Thanks Prashanth,

Fingers crossed if we all report the bug they'll add a toggle into the Preference window or site preferences to restore the F12 function.

Participating Frequently
November 16, 2016

Same issue here.

It has to be a bug not a feature or the right click option wouldn't list "F12" as the shortcut.

Fingers crossed there is someone in Adobe who can get this big fixed ASAP.

I have reported it as a bug, please vote to help this issue get fixed.

Adobe Dreamweaver: Bugs: Hot (279 ideas) – Adobe Dreamweaver CC: Feature Ideas

ChrisBean
Participant
November 16, 2016

Hi What's the title for listed bug?  can't find it..

Participant
November 14, 2016

This is to annoying - Anybody know other good editors that are easy to jump to from DW?

I have looked at Sublime and Brackets...

Thanks in advance

BenPleysier
Community Expert
Community Expert
November 14, 2016

This is a Dreamweaver forum. If you want an honest answer, Google the subject.

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
johnyd10096109
Participant
November 13, 2016

Prashanth,

I have similar problem (Windows 8.1 machine and WAMP server up and httpd-vhosts.conf with redirection.

Problem No1 - If local server is up and running, DW will ignore it.

Problem No2 - If there is remote (my.remoteServer.com) and test (my.localServer.dev) servers defined in DW Site Setup, DW will give priority to the remote server with no warnings or options to define priorities. e.g when I click F12 it will open my.remoteServer.com instead my.localServer.dev, if I click on the Real-Time preview icon on bottom right hand side and then click on the primary browser, Real-Time preview will open localhost address, something like http://127.0.0.1:50536/preview/app/index.html.

Suggestion

These are serious problems and I would suggest to have additional option in Site Setup, where user can select if he want to use defined remote server, test server or built in DW server for the Real-Time preview.

Participant
November 10, 2016

Yeap same issue, this stop working for me, because in my config of my server i got to doesn't permit cross-origin framing, and i cant turn this option off in my server by security reasons, so hope you can fix it or give option to disable it and let use the traditional way by pressing F12, so annoying.

martinr59119573
Participant
November 12, 2016

Is this a DW bug or an oversight?

It wasn't broke - so why fix it?

Participating Frequently
November 10, 2016

Forgive me if we're talking about the same thing here, but I used to hit F12 and be able to deploy a new or existing file and see it displayed in my primary browser (Chrome). Now I'm merely shown the non-updated file loaded into an iframe hosted on some localhost server. Not sure what the point of that is. Better yet, I get a 404 'Not Found' error for a new file because it isn't being deployed to the server anymore using F12. And, yes, I've enabled "Automatically push files to testing server" in my testing server setup, but that checkbox appears to do nothing. What, exactly, is the "Background File Activity" pop-up window doing after an F12 if not sending my updated files to the server?

Now, in order to see the updated file on the server, I have to manually upload it (Ctrl-Shift-U - two hands) and then right-click the something-or-another and serpentine down and around to "Preview Open in browser" (where it sarcastically displays an "F12" next to Chrome in the list). What was a one finger keyboard operation has become a multi-step, two handed + mouse operation.

I should be used to things like this, but they never get easier. Each successive update has me scrambling to find workarounds for muscle memory that's used to functionality that has disappeared or changed so drastically as with the example I've described above. Anyone else customize their code coloring in the previous versions? My condolences.

Participant
November 10, 2016

Hi Southernroutes,

I feel you pain, I discovered that once I'd carried out the steps that I previously posted that hitting F12 was an intermittent affair, I would assume that the new updates are focusing on you having to use live preview more than the browser (unsubstantiated) but that's how I feel it is.

Although if memory serves, I don't recall being able to test links in live view either, which is the whole premise of building and creating websites or html emails in my case.

I'm sorry but the following won't be very helpful for some of you reading this, but I read a review of DW 2017 and the author felt that Adobe  appeared to be directing you to being more code orientated rather than design view so with that I fixed the issues I was experiencing with DW 2017 and simply uninstalled it, I returned to using DW 2015.

Although since reverting back to 2015 I've rekindled my love for Notepad ++ and have been using that extensively, at least I'm using code view now!

Participating Frequently
November 10, 2016

Ha, well, I've also got Notepad++ primed and ready to go, just in case. I can't tell you how many times I've switched over to it after a major DW update. :-P

I've never liked live view or split screen and this new 127.0.0.1 iframe thing this has me really scratching my head. Just working off the testing server and seeing my updates in the browser after an F12 was working so well. Oh well.

Participant
November 8, 2016

Hi,

If I'm understanding what you're saying, it sounds very similar to what I've experienced. I'm using DW to building product driven HTML Emails.

Prior to the 2017 upgraded of DW, when I previewed the email in a browser I could click on any of the hyper links and I would be taken to each of the products linked back to the email.

Since upgrading I can't do that because when I click on a link nothing happens other than serving me with a blank browser page, what's more the url, isn't as it used to be, it is something similar to the  one the original poster has presented.

In order to fix this issue, I clicked on the "Real Time Preview" in DW and selected the "Edit List" menu item, once you're in there looked to Real-time Preview in the left hand column, you'll then be presented by a list of browsers, look to the item below this window that says Options: check the box that says Preview using temporary file and that should fix you problem, can't remember if this is a one time thing or you have to select each of your browsers in turn and choose that option.

hope this helps someone.

Prashanth NethiCorrect answer
Participant
November 4, 2016

Sorry for the inconvinence. Though the address in the browser is pointing to 127.0.0.1,  the content is getting served from the actual server if any.  Actually we are loading all of the content from any testing server, if defined, in an iframe that is embedded inside the HTML that is being served from 127.0.0.1.

chrishuffman​ and everyone who i facing the issue with local preview. are you having any difficulty getting the preview right ?

you could get the legacy preview by selecting  file in the files panel -> right click on the Selected file -> choose Open in browser option. Also this is available in the context menu of the document tab.

Nancy OShea
Community Expert
Community Expert
November 4, 2016

Right-clicking on the open document tab > Select Open in Browser > works great!

Thank you so much for that .

Nancy O'Shea— Product User & Community Expert
Participant
November 5, 2016

It would be nice if you told us up front which features we will lose should we take the chance and roll the dice on an upgrade.

Nancy OShea
Community Expert
Community Expert
November 3, 2016

Yes,  it is a problem with localhost testing servers.  I'm having similar issues and I dropped back to my previous version for now.  

Nancy O'Shea— Product User & Community Expert
Participant
November 4, 2016

Any way to go back to the CC 2015 behavior which just opened the local HTML file directly in the browser when pressing F12 (i.e. no "real-time" nor any temporary file)?


That way, I can just press F5 to refresh the browser's display and can have multiple pages previewed simultaneously.

Best regards

Stefan

Jon Fritz
Community Expert
Community Expert
November 4, 2016

Stefan Malz wrote:

Any way to go back to the CC 2015 behavior which just opened the local HTML file directly in the browser...


Not yet. If it's important to you, you could start an Idea over here: Dreamweaver Ideas which would create a user-vote-able Feature Request. If enough people vote for it, it could make it into the next version.

Preran
Community Manager
Community Manager
November 3, 2016

I am checking with the team and will get back to you as soon as I have an answer.

Thanks,

Preran

rfranklin32
Participant
November 4, 2016

Please. How long does this answer take? I have work to do!

Nancy OShea
Community Expert
Community Expert
November 4, 2016

It may take a while.  Drop back to your earlier version for now.

Nancy O.

Nancy O'Shea— Product User & Community Expert