1 person found this helpful
The table structure on this page is badly formed. Check the validator report -
and see if you can figure out how to rehabilitate that table layout. It will take some work. There are many errors....
Thanks for that. I will look into that, but I still want to fix the reason why dreamweaver is not showing the page in design view. It was showing it yesterday, then today it is just a black screen, but the code is all there and the page is showing fine online.
DW is not showing design view because the table structure is so damaged. DW cannot figure out how to render the table contents. DW is very focused on standards compliant code - when it is given pages with many errors on them it often cannot properly render the contents.
I took the time to read your question properly and noticed that you are new to DW. Do you happen to have a backup of your files? It is as simple as loading up your backup page and saving it over the one that is not showing the design view. As for the validator site, don't worry too much about it. It is good if you can fix the errors, that is IF you can, you just need to look at other sites, such as www.coca-cola.com and notice that even they have errors on there pages.
i actually had a back up and did what you said and thank you so much because it worked great.
Validating your code is one of the most important steps in troubleshooting a layout problem. It makes *no* sense to troubleshoot a page's layout when you know that it is invalid code. Citing professionally built pages that do not validate is a red herring and doesn't apply in this situation. Someone who knows how to code also knows what can cause layouts to explode and can decide what to worry about and what to ignore.
Clearly this page has a badly damaged table - if it did not, then DW could render the page. It needs to be fixed before DW will display it properly.
I have to second Murray on this.
I will go a step further and say ignoring errors on your site because someone else's site has some is extremely poor advice, especially considering the volume of people visiting this forum alone with a random display problems that are solved by simply correcting the errors found in the validators.
Restoring from a backup may work this time, but why did it work? That's where validation, and understanding what the validator is telling you, pays off. You somehow inadvertantly mangled your table code, will that ever happen again? What happens if your backup also has the same mangled code next time?
Some validation errors are never going to affect display and can be completely ignored from a "how does this affect my design" point of view, like missing an alt attribute on an image for instance. Others, like missing or improperly nested html elements, can kill your design in browsers or rendering engines that can't handle major errors (like most versions of IE or DW's Design View) while everything looks fine in a browser better programmed to handle problems (like Chrome or Firefox).
Bottom line is, the validators are extremely useful tools, do not ignore the error report unless you understand which errors can be ignored.
I understand that it had badly damaged tables but he did state that it was
displaying on DW prior to this happening and it is happening on that page
only. I have gone through the that site and noticed that he had pretty
similar table structures throughout it and yet this has happened to one of
his pages. Easy solution, load a back up if you have one, replace the file
that is not displaying in design view, enjoy. For someone who is a novice
and trying to run a business it's the least we can do to help.
A single inadvertant code edit can trigger a whole raft of table error instances. I suspect that's what happened here. Restoring from a backup of the file is a good solution, but if the backup file also contains table errors, I wouldn't walk away feeling like I had solved the problem.
The only way to be certain of good, cross-browser rendering is to start with a page that validates (or at least one that fails for reasons you understand). That's not to say that valid pages don't also experience cross-browser rendering differences, but you at least have started from solid ground.
thanks again to all the reply' s, if i knew how to do that side of things i would go through and perfect it myself.
The site is back http://www.exclusivewindowtint.com.au/car-window-tinting.html and its showing up. What would it take and who could fix my site and how much would it cost is it very$$$$ at the end of the day im a window tinter and its winter so if its a pricey thing to do i might have to leave it for now but let me know.
Are you looking at just this one page?
Email me offlist at msummers at great-web-sights dot com.