This is DW CS6 on Windows 7.
I have several browsers set up for preview. I use the option "Preview using temporary file".
For no reason that I can figure out the preview will stop working. i.e. I hit F12 and nothing at all happens. My impression is that it will be trigered by the content of certain pages - jQuery served by CDN? or something like that? Once it starts NO pages work. If i restart Dreamweaver some pages will be OK, but then the problem will re-appear.
DW > Edit > Preferences (Ctrl + U shortcut).
Preview in Browser from left sidebar > Select all displayed browsers, remove them using '-' button.
Click '+' button on top and navigate to the installed application path of your preferred browsers. Add the .exe files to the browser. Set your preferred browser as 'Primary'. Save changes. Check to see if Previewing works now.
It could be that a corrupt cache/ preferences are causing this error. Trying to 'reset' it may fix it.
The next step would be for you to try trashing your cache: http://forums.adobe.com/thread/494811
Thanks. I tried trashing the cache and even deleting the entire configuration folder. No joy.
But now I think I have the solution after a lot of time debugging (thanks Adobe).
1) The problem is caused by a specific HTML file. (Though I have had different ones cause this in the past months. Presumably they have something in common).
2) If I start DW, preview is fine. Once I try the problem file however, NO files can be previewed until I restart DW
3) With the problem file, no 'tmp' file gets created
4) I have CSE HTML validator. If I open the problem file in that, I can preview the page in my browser. So it's not as if the page kills the browser.
So what is it in the problem file that causes the problem?
Well the file is a Wordpress file with a "Thesis" theme, and one of the external CSS files has a long comment:
/*
File: custom.css
Description: Custom styles for Thesis
BASIC USAGE:
If you have enabled the custom stylesheet in the Thesis options panel, the <body> tag
will be appended with the "custom" class, like so: <body class="custom">. You can use
the "custom" class to override *any* CSS declarations contained in the style.css file.
For example, if you wish to change the default link color to green, you would add the
following declarations to this file:
.custom a, .custom a:visited { color: #090; } <--- This makes links green
.custom a:hover { color: #00f; } <--- This makes links blue when you mouse over them
WHY THIS WORKS:
By using the "custom" class, you are creating more specific CSS declarations for HTML
elements. CSS styling is applied through rules of specificity, and because declarations
prepended with .custom are more specific, they get applied when the page is rendered!
More information about styling your Thesis installation using this file can be found
in the User's Guide:
http://diythemes.com/thesis/rtfm/customizing-thesis-with-customcss/
*/
If I remove that comment, DW does not screw up.
Adobe - is anyone there? This is a bug. Can it be fixed?
If you think this bug is reproducible, file a report here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
I have expereinced the preview in browser not working. It's not a browser issue like Mr. Litiboloo stated. I've tried Firefox, Safari and Chrome when the problem started. It is clearly a Dreamweaver issue.
I get the following error message when I switch the design view to live view:
The system reported the error: An unknown error occurred while accessing OS:Users:xxxx.xxxx
I'm using cs6 with 10.8.2
HELP -- Please
It is clearly a Dreamweaver issue.
I get the following error message when I switch the design view to live view:
The system reported the error: An unknown error occurred while accessing OS:Users:xxxx.xxxx
I'm using cs6 with 10.8.2
I think it's more likely a System issue, as the error message suggests. It appears that there is an inability to access a particular directory or file. Do you see this problem on all files, in all sites?
Photoshop cs6, FW, and AI don't have this sissue. Imported then exported than impofrted the same file to different directories without a problem.
The issue I speak of with Dreamweaver was intermittant at first and now constant.
In addition, the css path vanishes when the preview in browser is called.
I bring in a file from a different folder than I have been speaking to, and the file displays properly in preview. I close the preview page and the css "tree," What I call is in place.
This is what I mean by a css tree: http://screencast.com/t/Buto6yeMWg
Then, I open another page from the same folder and it does show the css "tree." When I preview the file it displays properly. When I close the page and return to Dreamwaver, the css "tree" is gone.
The issue I was having with the preveiw page is not happening now.
??
What you are calling the CSS tree is called the "Tag Selector" by Adobe.
So, you open a page, can see the tags on the tag selector, and it previews properly. Then you close ... what? The browser with the preview, or the page in DW?
Also, in Preferences > Preview in Browser, are you set to use temporary files on preview?
Preview is set up like this:
http://screencast.com/t/0UmeKe7CIk
I close the browser with the preview. The tag editor is there. When I open another file in the same folder then edit then preview in browser -- I close the browser and the tag selector is gone.
To resotre it I have to close Dreamwever and evoke it. Then the tag selector reapperas when any file in the folder is openend. Then the behaviour resumes if I i open a diferent file in the same folder.
The tag editor vanishes now when I open another file in the same folder.
My workflow is beign interrupted becuase I have eo evoke Dreamweaver as time after time I edit a new page.
This situation is almost intolerable. Is there an update to ver 12.0?
If seeter and I are both experiencing the same bug, then that rules out a lot of system and hardware issues.
I NEED HELP HERE please.
I NEED HELP HERE please.
I'm not sure you will get it here. Clearly all of the 'answerers' are puzzled by your symptoms. If any of us had also experienced such, you would surely have heard from us. It seems to me as if there are system issues contributing to the problem, but I can't describe any specific ways to test for that since I don't know what those system issues might be.
Failing physically coming to your computer and sitting at the keyboard, perhaps you can describe your site definition and architecture and system details in as much detail as you can? That may illuminate some common element between each of you.
Hi Murray -
Thanks for offereing to do a temviewer meeting to diagnose the missing tag selector problem.
I figured out the issue. You eluded to it but I didn't comprehend. What happend was I had two pages open in Deamweaver with two differnt style sheets. I don't get why DW couldn't handle that but when I switched between the two documents the tag selector went away and I had to evoke DW to "fix" it. The problem persisted of course.
The work around for me was to open one of the pages in a browser and view source or use a plain text editor to view the .css.
Maybe I spoke too soon.
While editing a site yesterday, the tag editor displayed on the first page I opened. When I opened the second page that shares the same .css, the tag editor would not display. When I swtihced over to the first page, the tag editor was there.
The issue with the preview in browser has gone away after I deleted then replace the primary and secondary browsers.
North America
Europe, Middle East and Africa
Asia Pacific