Skip to main content
Participating Frequently
January 5, 2017
Question

Dreamweaver CS 5.5 Freezing on specific part of code

  • January 5, 2017
  • 6 replies
  • 409 views

I've been editing my website for some time and out of absolutely nowhere, with no changes to the source code, DW will freeze any time I click on that part of the code, or click on where that section of the code would appear in the design section (the picture links in question are not showing up in the design area but is showing up in the source code). I have tried clearing the DW cache and freeing up space on my hard drive to no avail. I am really confused because this happened out of nowhere, I did not make any changes to the code that's giving me a problem and no other page I've been working on besides the default page is giving me an issue. I have no clue what to do because I can't click on the code in question without everything freezing.

    This topic has been closed for replies.

    6 replies

    RyneDeCapAuthor
    Participating Frequently
    January 5, 2017

    Ok so I nailed where in my code the issue is, if it isn't this I give up hope, and I'm able to edit the code in the code view.

    If you look on the website http://www.afterburnerfx.com ,the issue is coming from the rows of categories in the middle of the page (screenprinting, embroidery, wall graphics, etc.). Now the HTML for this is:

    <a href="embroidery.html">

        <article id="link" class="col span_4"> <img src="img/embroidery_hats1.jpg"alt="Embroidered Hats featuring Red Bull, Suzuki, & Knievel Designs" >

          <div class="category">Embroidery </div>

        </article>

    And the CSS is:

    article{text-align:center;background:#000;}

    NOW there are also ones using the aside property and they are coded exactly the same HTML and CSS only subsitute the word 'aside' for 'article' and '#000' for '#333' for the CSS. These go every other box as each one has a different color to it. So I took this site over, it was originally made by someone else, which is why I'm having some trouble making heads or tells of it. And I know that you aren't supposed to use the 'ID' attribute over and over again like it is and rather us the 'class' or style it in CSS. Though when I switched each 'id' to 'class' I still find the same error. So now this is where my issue stands and I don't know how I should code it to get rid of the errors. Thanks for the help so far.

    Nancy OShea
    Community Expert
    Community Expert
    January 5, 2017

    52 code errors is quite a lot. But some of these are just images that have no ALT attribute.

    Showing results for http://www.afterburnerfx.com/ - Nu Html Checker

    IDs are unique identifiers that cannot be used more than 1 X per page.   You have duplicate IDs throughout your document which is the likely source of your problems in DW.

    Work through the code errors line by line.

    Nancy

    Nancy O'Shea— Product User & Community Expert
    RyneDeCapAuthor
    Participating Frequently
    January 5, 2017

    Ok so I have now discovered that when I go from the split view to the code view, I can click anywhere in the code and edit however I want without it freezing, so it appears this could be an issue with the design view? Sorry for all these responses this is just so frustrating lol.

    RyneDeCapAuthor
    Participating Frequently
    January 5, 2017

    And how am I going to even fix the code in question if it is wrong because I can't even click on that section without it feezing?

    Jon Fritz
    Community Expert
    Community Expert
    January 5, 2017

    There's really no rhyme or reason to why certain errors cause DW to choke. It (and each browse) has been programmed to essentially "guess what you meant" when running into code errors. Most of the time, each program can sputter through without too many issues, even displaying what you meant to do in many cases, even though the code is wrong.

    I'm guessing that DW finally got to the point where it just doesn't know what to do anymore.

    I would either start over with a new clean page, or edit the file in Notepad++ then bring it back into DW, if Code View isn't accessible.

    It's still likely a code issue, even if it's Design View that's locking up on you.

    RyneDeCapAuthor
    Participating Frequently
    January 5, 2017

    Ok it's showing quite a bit of errors and warnings but why would this all of the sudden cause an issue I've been editing the same code for weeks now and it never froze.

    Nancy OShea
    Community Expert
    Community Expert
    January 5, 2017

    DW can forgive a few code errors but after a while it starts to choke on them.  So do browsers BTW. 

    Nancy

    Nancy O'Shea— Product User & Community Expert
    RyneDeCapAuthor
    Participating Frequently
    January 5, 2017

    So the validate will not work..it says my internet connection is down though it is not. I don't think I have any issues with the second solution. So I tried the third solution and it appears it might be the code because upon taking it from notepad to a whole new HTML, it froze again without me really doing anything else. I am just so confused because I didn't make any changes to this code, especially where the problem is taking place. The code is showing up but in that specific section, nothing is showing up in the design side. Though if I save and preview my page, everything shows up and works just fine.

    Jon Fritz
    Community Expert
    Community Expert
    January 5, 2017

    You can validate online at http://validator.w3.org/nu

    The problem may or may not be anywhere in the code you're clicking. Sometimes a small error earlier in the html will cause big problems later on.

    Jon Fritz
    Community Expert
    Community Expert
    January 5, 2017

    Run the validator under File > Validate > Validate current document (W3C) to see if there are any code errors to repair. DW can run into problems with code errors from time to time.

    Another item to check for is protocol relative links in your <head> section. Some of the older versions of DW have issues with links that start with //. If you have any, change them to http versions and see if it comes back for you.

    Since this is only happening on one file suddenly, I'd see if maybe the file itself wasn't corrupt by opening it in notepad, copying the code, then opening a new blank html document, pasting the code into it and saving over the original.