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

[IronADDT]

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.

[BenPleysier]

I have received a compelling argument to unlock this discussion with the understanding that the offending post be deleted.

I will not delete said post with the hope that civility returns to the discussion.

[osgood_]

BenPleysier wrote:

I have received a compelling argument to unlock this discussion with the understanding that the offending post be deleted.

I will not delete said post with the hope that civility returns to the discussion.

Ben, there is no offending post if you're are refering to my post (49) If you care to remove said words in the post that you find offensive then please feel free to do so, perhaps using words like 'dick-head and moron' if that is what you found offence to describe Adobe staff is not called for but probably what a large majority are thinking. Other than that its a legitimate post about an important feature of a piece of software, which others may share and which Adobe technicians, should they care to listen, may learn from in terms of what web-developers require.

[patrickf83584863]

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.

[southernroutes]

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.

[patrickf83584863]

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!

[southernroutes]

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. 😛

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.

[Alienmau]

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]

Is this a DW bug or an oversight?

It wasn't broke - so why fix it?

[johnyd10096109]

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.

[krestenb69596302]

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]

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

[IronADDT]

For Mac users:

https://9to5mac.com/2016/11/14/visual-studio-for-mac/

Two weeks have passed and no update still available for Dreamweaver CC 2017.
My concern is that Adobe has closed the DW CC 2017 project (maybe Adobe fired the whole DW team) and it's planning the works for the 2018 version.

I think it's too difficult to correct all bugs and much better to start from scratch with a new and strong team.

Meanwhile, it's better to continue to use the old version 2015 or search another tools.

[Alienmau]

You can try Atom, or Sublime, both has a lot of potential with posibility of add mods, that made wonderfull this editors

[David.Turk]

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]

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

[Prashanth Nethi]

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

[David.Turk]

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.

[southernroutes]

Adobe (management) seems more concerned with trying to get us to buy their stock photography than fixing their broken software. I feel sorry for those devs. Releasing something this buggy, it has to be a toxic environment to work in day after day.

[dougm16560577]

I'm running XAMPP on windows and before I upgraded to DW 2017 my F12 key worked perfectly fine with my 127.0.0.1 loopback address. I often work with PHP files and the preview tool is not working. Instead of the proper address "http://127.0.0.1/xampp/" i get this garbage "http://127.0.0.1:51285/preview/app/index.html". I should have never upgraded.

[Jon Fritz]

When you right click the file name in either the Document Window (the file name tab) or within the Files window and choose "Open in Browser" does it function correctly?

Given all of the problems in CC2017: https://helpx.adobe.com/dreamweaver/kb/known-issues-dreamweaver-cc-2017.html it may be better in the short term to roll back to CC2015: http://blogs.adobe.com/adobecare/2015/06/16/how-to-find-and-install-previous-version-of-adobe-apps-i... until the first batch of patches come out for the new programs.

[software@openmoves.com]

I am really having an issue with updated grpahics not previewing. I work on html email and have depended on browser preview before testing, if updating graphics can't be preivewed correctly this is a major set back. The only thing that is working is opening each image in a new tab closing out my preview and previewing again. This is ridiculous. Are they working ona a fix?

[Nancy OShea]

To access the old Preview in Browser, right-click on open document tab or a file in your Files Panel.

Select Open in Browser > Do not hit F12.

Refresh your browser with Ctrl+R or F5.

Nancy

[Winginsue]

Sorry Nancy, that is not an acceptable work around.  Having to right click on the open document tab and selecting Preview in Browser is a hassle.  Additionally, when you do that it shows right there on the menu that the F12 is a shortcut.  This is a bug and needs to be fixed.  F12 has worked for YEARS and it needs to be resolved.

[Nancy OShea]

Winginsue wrote:

Sorry Nancy, that is not an acceptable work around. Having to right click on the open document tab and selecting Preview in Browser is a hassle.

I'm sorry it's a hassle for you.  But it's the only workaround Adobe has provided us with so far .

Nancy

[Winginsue]

Sorry, I was thinking you were an Adobe person.   I did submit a bug report.  Hopefully they will fix it.