Hi ~I have been building a site with DW 5.5 and yesterday after a save DW will not open the site again...it starts loading the HTML code...nothing apears in the design view (I work with split screen)...and then it says not responding at the top. (I have waited over an hour and it doesn't start working again.)I tried opening other sites and have no issue. So this is specific to this one site. I can open up my index.html file in browsers and every thing seems ok. I have tried the following:checked for updates - am up to dateno extensionsrestored the preferencesdeleted the .dws site cache filesdeleted the FileCache.dat file and the whole configuration folderI also tried opening a new file and coping my code into the new file. The HTML runs fine but different valid CSS3 seems to cause problems. For example it won't let me enter via hand or through the option menu the following....ul, ol, dl { list-style-image: none; list-style-type: none;}I've searched the forums and am at loss of what to try...any suggestions would be appreciated.~thanks,Beata

Participant

Answered

RE: Dreamweaver not responding

Forum|Forum|13 years ago
April 17, 2012
7 replies
28623 views

Hi ~

I have been building a site with DW 5.5 and yesterday after a save DW will not open the site again...it starts loading the HTML code...nothing apears in the design view (I work with split screen)...and then it says not responding at the top. (I have waited over an hour and it doesn't start working again.)

I tried opening other sites and have no issue. So this is specific to this one site. I can open up my index.html file in browsers and every thing seems ok. I have tried the following:

checked for updates - am up to date
no extensions
restored the preferences
deleted the .dws site cache files
deleted the FileCache.dat file and the whole configuration folder

I also tried opening a new file and coping my code into the new file. The HTML runs fine but different valid CSS3 seems to cause problems. For example it won't let me enter via hand or through the option menu the following....

ul, ol, dl {

list-style-image: none;

list-style-type: none;

}

I've searched the forums and am at loss of what to try...any suggestions would be appreciated.

~thanks,

Beata

This topic has been closed for replies.

Correct answer codeDawg

Very similar problem. I've been using DW for years and this problem just started happening today. Just today, opening up files that were created in DW made DW freeze with the dreaded "not responding" message in the title bar.

I'm using DW CS3 on a Vista 64 system.

I work in split screen - Code and Design.

Fairly "busy" pages with Google ads and other external banners in the sidebars, as well as other external javascript and CSS files.

(Note the problem is not there when using only code view - DW becomes unresponsive only when a design view is open.)

Tried the delete-cache-file fix and it didn't work. (I noticed that the deleted cache file was NOT recreated on subsequent DW startups.)

What worked for me was changing a setting found in the View menu.

"Display External Files" was checked on.

Turned if off and suddenly DW started working again

(I noticed that after I did this, that deleted cache file was recreated.)

The problem and solution are repeatable on my system.

Turn that option on and open the "problem" page - DW freezes

Restart DW, turn that option off and then open the "problem" page - DW runs.

Hope this helps

~codeDawg

StephenDP

Participant

That worked for me, thanks!

C

clearcomms-france

Known Participant

Re Carey Burgess's posting - "It should be under the Commands menu in Dreamweaver 8."

Where is it - I've just looked in my version of Dreamweaver 8 and while there are a good list of things in the dropdown menu from Commands, I can't see any reference to displaying external files.

Am I being dumb (not for the first time!) or is it hidden away somewhere?

John Waller

Community Expert

You're probably running Dreamweaver 8.0 (in DW, click Help > About Dreamweaver to see which version you have).

Display External Files is found in DW 8.0.2

Download and install the 8.0.2 updater

http://www.adobe.com/support/dreamweaver/downloads_updaters.html#dw8

C

clearcomms-france

Known Participant

Thanks John, that was the answer, and I now have the option.

This problem has been around for a while, and quite a few Dreamweaver 8 users have been asking about it; this is the first time I've seen any mention of that update3 in v 8.02, so I am VERY grateful to you.

A

Anonymous

Not sure if this will help anyone - but I have the same experience and my investigation shows ...

I see from a packet trace that when DW attempts to access an external facebook badge image, from http://badge.facebook.com/..., facebook returns an http redirection to http://www.facebook.com/unsupportedbrowser. When you browse to that page with a normal browser, you get a facebook 'improve your experience' page. When DW attempts to get that URL instead, it's request is for an image type file but receives a zero length text/html containing a header redirect - to itself, which DW responds to as a never ending loop. Problem in Facebook's handling of unsupported browsers.

Not sure if the recent facebook changes have impacted this, From memory, I never used to get the facebook badges appearing in DW, just a grey square, but they may have received a different (and more valid) response to a request for an image.

Anyway, switching off external images is a workaround for me.

GET /badge/<<snip>>.png HTTP/1.1

Host: badge.facebook.com

Pragma: no-cache

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*

HTTP/1.1 302

Location: http://www.facebook.com/unsupportedbrowser

Content-Type: text/html; charset=utf-8

X-FB-Debug: up7BW+X0Yk5PU4KrcrNyCjimd4cXMSDk0sijdqXwqj0=

Date: Tue, 01 May 2012 11:33:12 GMT

Content-Length: 0

Connection: keep-alive

GET /unsupportedbrowser HTTP/1.1

Host: www.facebook.com

Pragma: no-cache

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*

HTTP/1.1 302 Found

Location: http://www.facebook.com/unsupportedbrowser

Content-Type: text/html; charset=utf-8

X-FB-Debug: 5kSg1Y4twqfRoLhENQlhAQMUgbUBbiscYQfd2sJ4rKk=

X-Cnection: close

Date: Tue, 01 May 2012 10:58:09 GMT

Content-Length: 0

GET /unsupportedbrowser HTTP/1.1

Host: www.facebook.com

Pragma: no-cache

Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*

etc etc

AllDayDev2

Community Manager

Thanks for tracking this down, TimDownUnder!

So, it appears that a recent change to the way Facebook responds when you try to load the badge is causing this issue.

And, as mentioned before by codeDawg, the workaround in Dreamweaver is to uncheck "Display External Files" in the View menu.

S

scls_web

Participant

What is the workaround for Dreamweaver 8? I don't see any option to uncheck "Display External Files" in the view menu.

C

clearcomms-france

Known Participant

I've also been having this problem with Dreamweaver 8 on an XP Pro system.

I solved it by designing my own artwork, and using that to link to the relevant Facebook page instead of having an official Facebook Badge. Can't see any reason why that shouldn't work as well for me.

I had no problem with the original badge for some months, so it's a change to their script that has caused the problem. Seems fairly typical of their attitude to their users - look at what is happening over Timeline.

LRHH

Participating Frequently

Thank you CodeDawg. Any ideas on why this is suddenly an issue?

AllDayDev2

Community Manager

I'd like to find out why this is occurring as well, so that we can ensure others don't run into this problem in the future.

Display External Files is an option that enables files (usually images) that exist on the web to be displayed in Design View. Design View usually only displays files that are located locally on your machine. This means you would have an absolute URL (e.g. "http://mywebsite.com/image.jpg") to the file in your page's code, instead of a relative URL (e.g. "/image.jpg") which would only look on the local machine.

Do any of the pages where you are seeing this issue have absolute URLs to a file?

If so, and you remove (or comment out) that code and turn Display External Files back on, does that fix the issue?

Since I have not been able to reproduce the issue, I am relying on you all to help me investigate this. Once I know more, we can go from there to determine the cause of the issue and get it fixed.

Thanks!

Nancy OShea

Community Expert

@Carey,

In my experience, references to 3rd party scripts such as Google fonts/ads/widgets, Facebook badges, etc... can create problems with Design View when "Display External Files" is enabled.

Below is the an example caused by the OP's Facebook badge.

http://forums.adobe.com/message/4357898#4357898

Nancy O.

Nancy O'Shea— Product User & Community Expert

codeDawgCorrect answer

Inspiring

Very similar problem. I've been using DW for years and this problem just started happening today. Just today, opening up files that were created in DW made DW freeze with the dreaded "not responding" message in the title bar.

I'm using DW CS3 on a Vista 64 system.

I work in split screen - Code and Design.

Fairly "busy" pages with Google ads and other external banners in the sidebars, as well as other external javascript and CSS files.

(Note the problem is not there when using only code view - DW becomes unresponsive only when a design view is open.)

Tried the delete-cache-file fix and it didn't work. (I noticed that the deleted cache file was NOT recreated on subsequent DW startups.)

What worked for me was changing a setting found in the View menu.

"Display External Files" was checked on.

Turned if off and suddenly DW started working again

(I noticed that after I did this, that deleted cache file was recreated.)

The problem and solution are repeatable on my system.

Turn that option on and open the "problem" page - DW freezes

Restart DW, turn that option off and then open the "problem" page - DW runs.

Hope this helps

~codeDawg

B

BWoyenAuthor

Participant

Thanks codeDawg!!!

It worked!!! Even reinstalling didn't help - but your steps worked like a charm.

Thanks again for passing this tip along.

~Beata

codeDawg

Inspiring

Yeah - that problem had me worried for a bit.

All I wanted to do was make a slight text change to a page I created last year.

Took me a several hours to come up with a "Fix" to the DW freeze issue, then 30 seconds to change the page

I'm still not quite sure what that option actually does - I don't see a difference in the design view.

Glad it worked for ya'!

~codeDawg

BenPleysier

Community Expert

Being able to open all other files, my guess is that it has to do with the markup in the document and/or external files linked to the document.

Open the file in Notepad (if it isn't to large) copy the markup and paste into a post so that we can have a look.

Gramps

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

B

BWoyenAuthor

Participant

Thanks for the speedy reply - here's my CSS file:

@charset "utf-8";

body {

margin: 0;

padding: 0;

background-color: #2e2e2e;

background-repeat: repeat-x;

font-family: Verdana, Arial, Helvetica, sans-serif;

font-size: 1em;

}

#logo {

z-index: 20;

float: left;

margin-top: -1.8em;

margin-left: 2%;

position: absolute;

display: block;

transform: rotate(345deg);

-webkit-transform: rotate(345deg);

-moz-transform: rotate(345deg);

}

/* ~~ this container surrounds all other divs giving them their percentage-based width ~~ */

.container {

width: 75%;

max-width: 1024px;/* a max-width may be desirable to keep this layout from getting too wide on a large monitor. This keeps line length more readable. IE6 does not respect this declaration. */

min-width: 760px; /* the auto value on the sides, coupled with the width, centers the layout. It is not needed if you set the .container's width to 100%. */

height: auto;

margin-top: 5em;

background-color: #FFFFFF;

margin-right: auto;

margin-left: auto;

clear: both;

z-index: 1;

position: relative;

overflow: hidden;

margin-bottom: 5em;

}

.header {

background-repeat: repeat-x;

height: 6em;

background-color: #8e8e8e;

z-index: 2;

}

#RRWG {

float: left;

clear: both;

margin-left: 15%;

padding-top: 0.4em;

}

#top_social_buttons {

float: right;

margin-right: 3%;

margin-top: -2.6em;

display: inline;

z-index: 8;

clear: both;

}

.nav ul li{

font-family: Arial, Helvetica, sans-serif;

color: #2e2e2e;

font-size: 1.2em;

float: left;

font-weight: bolder;

margin-left: 15%;

padding-left: 2em;

margin-top: 0.6em;

z-index: 3;

display: inline;

}

.nav ul li a:link{

font-family: Arial, Helvetica, sans-serif;

color: #2e2e2e;

}

.nav ul li a:visited{

color: #2e2e2e;

}

.nav ul li a:hover, a:active, a:focus{

color: #FFAB57;

text-decoration: none;

}

.content {

float: left;

padding-top: 4%;

padding-left: 5%;

clear: both;

position: relative;

width: 50%;

min-width: 400px;

overflow: hidden;

text-align: justify;

text-justify:inter-word;

}

.meeting {

float: left;

width: 30%;

padding-top: 4%;

font-size: 0.8em;

/* [disabled]margin-right: 3%; */

position: relative;

padding-bottom: 4%;

text-align: center;

margin-left: 3%;

}

.twitter_feed {

float: left;

width: 30%;

/* [disabled]padding-right: 3%; */

padding-bottom: 2%;

/* [disabled]margin-right: 3%; */

margin-left: 5%;

}

#ricrac {

background-repeat: repeat-x;

height: 7px;

width: 100%;

position: relative;

float: left;

}

#footer-page {

background-color: #383838;

/* [disabled]background-image: url(../_images/footerbckgd.gif); */

background-repeat: repeat-x;

clear: both;

padding-top: 3%;

padding-bottom: 3%;

font-size: 0.8em;

height: 9em;

}

#footer-page #left_column {

width: 30%;

float: left;

padding-left: 5%;

}

#footer-page #center_column {

width: 30%;

float: left;

text-align: center;

}

#footer-page #right_column {

width: 30%;

float: right;

padding-right: 5%;

}

/* ~~ This grouped selector gives the lists in the .content area space ~~ */

.content ul, .content ol {

padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */

}

/* ~~ The footer ~~ */

.footer {

position: relative;/* this gives IE6 hasLayout to properly clear */

clear: both; /* this clear property forces the .container to understand where the columns end and contain them */

background-color: #2e2e2e;

background-repeat: repeat-x;

height: 8em;

padding-top: 10px;

padding-right: 0;

padding-bottom: 10px;

padding-left: 0;

}

h1, h2, h3, h4, h5, h6, p {

margin-top: 0; /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */

padding-right: 15px;

padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */

}

/* ~~ Element/tag selectors ~~ */

ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */

padding: 0;

margin: 0;

list-style-image: none;

list-style-type: none;

}

a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */

border: none;

}

/* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */

a:link {

text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */

}

a:visited {

color: #FF9933;

text-decoration: none;

}

a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */

text-decoration: none;

}

/* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */

ul.nav {

list-style: none; /* this creates the space between the navigation on the content below */

}

ul.nav li {

border-bottom-style: none;

}

ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */

display: inline; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */

text-decoration: none;

color: #C63;

float: left;

padding-top: 5px;

padding-right: 5px;

padding-bottom: 5px;

padding-left: 15px;

text-align: center;

}

ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */

color: #FFF;

}

.clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */

clear:both;

height:0;

font-size: 1px;

line-height: 0px;

}

BenPleysier

Community Expert

There is nothing here that should stop DW from loading it.

Gramps

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

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded