Significance of design view

In the design view the right column doesn't float up to take its place next to the left column (there's enough space for both; together their width is still less than the wrapper), but when I look at it in Live view and preview it in browsers, they appear next to each other, as I intended.
Does it matter that it doesn't look right in design view (apart from the fact that it makes designing more difficult)?
Thank you.

Without seeing your page, it's impossible to know why the float isn't being rendered in Design view. Normally, it should be. However, the only thing that matters in the end is what it looks like in a browser.
Live View lets you work in the underlying code, so that can help if Design view isn't rendering your page as expected. Press F5 to update what's displayed in Live View.

Similar Messages

Design view is significantly different from output in Robohelp 10

This may be normal for Robohelp 10. I am not sure.
I am applying a new CSS to my company's help project as part of a major update to the design. The CSS includes table styles, and list styles - something that was signficantly lacking from the previous design.
I have noticed that there are significant differences between what I see in the design view and what I see in the output, and this causes a lot of confusion.
When applying the bullet style, in the design view I see a numbered list. However, the output displays bullets as I specified.
When applying a table style, the table looks unformatted until I view it in preview mode or generate the project.
My roman numeral list style appears as decimals in design view, but looks fine in the output.
This is very confusing to work with, and initially led me t make many manual changes before I realized that what I am seeing in the design editor is completely misleading.
Any suggestions are welcome.
Yehoshua

This is how it appears when I edit the style in Robohelp:
This is how it appears when I apply the style in design view:
However, when previewing the page (and also when generating ouput):
As I said, it is very confusing and misleading.

Significant difference within design view Dreamweaver CC

Hi all
I am making a site in Dreamweaver CC and if honest, I have just noticed something that has stopped me in my tracks that I am hoping is a common occurrence. The site in question is using Dreamweaver's media queries and I have not touched the boilerplate.
Design view pre CSS styling;
Live view seems to ignore this arrangement and puts everything on the page to 100%
The HTML for this section is;

<div class="light_grey_backround">
<div class="gridContainer clearfix">
    <div class="fluid mortgage_choices_title">
      <h1 class="dk_blue_text">Which type of new mortgage are you most interested in?</h1>
    </div>
    <div class="fluid mortgage_choices_subtitle">
      <h2 class="dk_grey_text">Simply pick the category that you fall into for more information on how we can help you with your mortgage. </h2>
    </div>
    <div class="fluid mortgage_choices_box zeroMargin_tablet zeroMargin_desktop">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_htb.jpg" alt="Help to Buy Mortgages"/>
        </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES</h3>
        </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div><div class="fluid mortgage_choices_box">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_mortgage_ftb.jpg" alt="First Time Buyer Mortgages"/>
        </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES</h3>
        </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div><div class="fluid mortgage_choices_box zeroMargin_tablet">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_mortgage_ntb.jpg" alt="Next Time Buyer Mortgages"/> </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES </h3>
    </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div>
    <div class="fluid mortgage_choices_box">
    <figure class="fluid mortgage_choices_image">
        <img src="_images/newhomesmortgages_mortgage_b2l.jpg" alt="Buy to Let Mortgages"/> </figure>
    <div class="fluid mortgage_choices_title">
        <h3>HELP TO BUY MORTGAGES</h3>
        </div>
    <div class="fluid mortgage_choices_copy">
        We specialise in the Governament backed Help to Buy mortgage scheme and the fantastic mortgage schemes available with it. Enjoy the huge
        </div>
        <div class="fluid mortgage_choices_action">
        TELL ME MORE...
        </div>
    </div>
</div>
</div>

The CSS
@charset "UTF-8";
/* Simple fluid media
   Note: Fluid media requires that you remove the media's height and width attributes from the HTML
   http://www.alistapart.com/articles/fluid-images/
img, object, embed, video {
width: 100%;
/* IE 6 does not support max-width so default to width 100% */
.ie6 img {
width:100%;
Dreamweaver Fluid Grid Properties
dw-num-cols-mobile: 4;
dw-num-cols-tablet: 8;
dw-num-cols-desktop: 12;
dw-gutter-percentage: 25;
Inspiration from "Responsive Web Design" by Ethan Marcotte
http://www.alistapart.com/articles/responsive-web-design
and Golden Grid System by Joni Korpi
http://goldengridsystem.com/
.fluid {
clear: both;
margin-left: 0;
width: 100%;
float: left;
display: block;
.fluidList {
    list-style:none;
    list-style-image:none;
    margin:0;
    padding:0;
/* Mobile Layout: 480px and below. */
.gridContainer {
margin-left: auto;
margin-right: auto;
width: 85.5%;
padding-left: 2.25%;
padding-right: 2.25%;
clear: none;
float: none;
#div1 {
.title_index {
.subtitle_index {
.content_introduction {
.content_introduction_para_2 {
.mortgage_choices_title {
width: 100%;
margin-left: 0;
.mortgage_choices_subtitle {
.mortgage_choices_box {
background-color: #FFFFFF;
margin-bottom: 40px;
border-radius: 7px;
overflow-x: hidden;
overflow-y: hidden;
-webkit-box-shadow: 1px 1px 1px 1px #797979;
box-shadow: 1px 1px 1px 1px #797979;
width: 100%;
clear: both;
margin-left: 0;
.mortgage_choices_image {
width: 100%;
margin-left: 0;
.mortgage_choices_copy {
width: 100%;
margin-left: 0;
.mortgage_choices_action {
width: 100%;
margin-left: 0;
.rate_slider {
.rate_slider_header_title {
.rate_slider_subtitle {
.ratetitle {
font-family: 'Source Sans Pro', sans-serif;
font-size: 30px;
color: #0F232A;
margin-top: 35px;
font-weight: 300;
width: 90%;
margin-left: 5%;
line-height: 35px;
margin-bottom: 10px;
text-align: center;
.rate {
font-family: 'Source Sans Pro', sans-serif;
font-size: 30px;
color: #3FB0B9;
font-weight: 600;
width: 90%;
margin-bottom: -10px;
text-align: center;
margin-left: 5%;
.dealterm {
font-family: 'Source Sans Pro', sans-serif;
font-size: 22px;
color: #666666;
margin-bottom: 10px;
width: 90%;
margin-left: 5%;
line-height: 23px;
text-align: center;
.ltv {
font-family: 'Source Sans Pro', sans-serif;
font-size: 20px;
color: #666666;
margin-bottom: 10px;
width: 90%;
margin-left: 5%;
text-align: center;
.costs {
font-family: 'Source Sans Pro', sans-serif;
font-size: 17px;
color: #ccc;
font-weight: 300;
width: 49.1525%;
width: 90%;
margin-left: 5%;
margin-bottom: 10px;
text-align: center;
.erc {
font-family: 'Source Sans Pro', sans-serif;
font-size: 17px;
color: #ccc;
font-weight: 300;
width: 66.1016%;
width: 90%;
margin-left: 5%;
line-height: 20px;
margin-bottom: 10px;
text-align: center;
.revert {
font-family: 'Source Sans Pro', sans-serif;
font-size: 17px;
color: #ccc;
font-weight: 300;
width: 90%;
margin-left: 5%;
line-height: 20px;
text-align: center;
margin-bottom: 30px;
.protection_choices_title {
color: #3FB0B9;
width: 100%;
margin-left: 0;
.protection_choices_subtitle {
.protection_choices_box {
background-color:#0F232A;
margin-bottom: 40px;
width: 100%;
clear: both;
margin-left: 0;
.protection_choices_image {
width: 100%;
margin-left: 0;
.protection_choices_copy {
color: #FFFFFF;
overflow-y: hidden;
overflow-x: hidden;
border-radius: 7px;
-webkit-box-shadow: 1px 1px 1px 1px #666666;
box-shadow: 1px 1px 1px 1px #666666;
width: 100%;
margin-left: 0;
.protection_choices_action {
color: #3FB0B9;
width: 100%;
margin-left: 0;
.protection_question {
.protection_subquestion {
margin-bottom:40px;
.contact_us_number {
.contact_us_email {
.contact_us_form {
.whole_of_market_title {
.whole_of_market_subtitle {
.whole_of_market_lenders {
.downloads_library_title {
.downloads_library_subtitle {
.download_cover {
.zeroMargin_mobile {
margin-left: 0;
.download_cover_container {
.download_cover_graphic {
width: 100%;
clear: both;
margin-left: 0;
.zeroMargin_mobile {
margin-left: 0;
.hide_mobile {
display: none;
/* Tablet Layout: 481px to 768px. Inherits styles from: Mobile Layout. */
@media only screen and (min-width: 481px) {
.gridContainer {
width: 87.75%;
padding-left: 1.125%;
padding-right: 1.125%;
clear: none;
float: none;
margin-left: auto;
#div1 {
.title_index {
.subtitle_index {
.content_introduction {
.content_introduction_para_2 {
.mortgage_choices_title {
width: 100%;
margin-left: 0;
.mortgage_choices_subtitle {
.mortgage_choices_box {
width: 48.7179%;
margin-left: 2.5641%;
clear: none;
.mortgage_choices_image {
width: 48.7179%;
margin-left: 0;
.mortgage_choices_copy {
width: 100%;
margin-left: 0;
.mortgage_choices_action {
width: 100%;
margin-left: 0;
.rate_slider {
.rate_slider_header_title {
.rate_slider_subtitle {
.ratetitle {
.rate {
.dealterm {
.ltv {
.costs {
.erc {
.revert {
.protection_choices_title {
width: 100%;
margin-left: 0;
.protection_choices_subtitle {
.protection_choices_box {
width: 48.7179%;
margin-left: 2.5641%;
clear: none;
.protection_choices_image {
width: 100%;
margin-left: 0;
.protection_choices_copy {
width: 100%;
margin-left: 0;
.protection_choices_action {
width: 100%;
margin-left: 0;
.protection_question {
.protection_subquestion {
.contact_us_number {
.contact_us_email {
.contact_us_form {
display: block;
.whole_of_market_title {
.whole_of_market_subtitle {
.whole_of_market_lenders {
.downloads_library_title {
display: block;
.downloads_library_subtitle {
display: block;
.download_cover_container {
.download_cover_graphic {
width: 100%;
clear: both;
margin-left: 0;
.hide_tablet {
display: none;
.zeroMargin_tablet {
margin-left: 0;
/* Desktop Layout: 769px to a max of 1232px. Inherits styles from: Mobile Layout and Tablet Layout. */
@media only screen and (min-width: 769px) {
.gridContainer {
width: 78.6666%;
max-width: 1232px;
padding-left: 0.6666%;
padding-right: 0.6666%;
margin: auto;
clear: none;
float: none;
margin-left: auto;
#div1 {
.title_index {
.subtitle_index {
.content_introduction {
.content_introduction_para_2 {
.mortgage_choices_title {
width: 100%;
margin-left: 0;
.mortgage_choices_subtitle {
.mortgage_choices_box {
width: 23.7288%;
clear: none;
margin-left: 1.6949%;
.mortgage_choices_image {
width: 100%;
margin-left: 0;
.mortgage_choices_copy {
width: 100%;
margin-left: 0;
.mortgage_choices_action {
width: 100%;
margin-left: 0;
.rate_slider {
.rate_slider_header_title {
.rate_slider_subtitle {
.ratetitle {
.rate {
.dealterm {
.ltv {
.costs {
.erc {
.revert {
.protection_choices_title {
width: 100%;
margin-left: 0;
.protection_choices_subtitle {
.protection_choices_box {
width: 23.7288%;
clear: none;
margin-left: 1.6949%;
.protection_choices_image {
width: 100%;
margin-left: 0;
.protection_choices_copy {
width: 100%;
margin-left: 0;
.protection_choices_action {
width: 100%;
margin-left: 0;
.protection_question {
.protection_subquestion {
.contact_us_number {
.contact_us_email {
.contact_us_form {
display: block;
.whole_of_market_title {
.whole_of_market_subtitle {
.whole_of_market_lenders {
.downloads_library_title {
display: block;
.downloads_library_subtitle {
display: block;
.download_cover_container {
.download_cover_graphic {
width: 15.2542%;
margin-left: 1.6949%;
clear: none;
.zeroMargin_desktop {
margin-left: 0;
.hide_desktop {
display: none;
Any help is appreciated as I am happy with what I have in design view, but it's live view that I am publishing...
Thanks in advance

Thank you for looking, I have resolved this issue. I was to do with the image %'s. When I changed this, it all fell into place.

What is it about this markup that breaks DW CS3 Design View Editing?

Folks:
I'm attaching very simple --and apparently completely valid-- markup that generates the text shown between the markers below:
------------start----------------
yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda badda.
------------end----------------
As you can see by examining the file, it contains only an span enclosing text and spaces, and some following breaks. This file passes DW validation: no errors or warnings.
If I open this file in DW CS3 Design View, select and delete the last word, "badda", the entire text --every "yadda"-- is also deleted. All that text is really gone -- if I immediately save the file and re-open it, there is no text content at all, just the span pair, spaces, and the trailing breaks. This is completely repeatable.
When you edit this file, do you get the same result?
The attached file is a cut-down, simplified version of a production file that exhibits this issue. (That file also passes validation.)   When I delete single words, entire content paragraphs disappear.   So this is not just a point of curiosity. I need to figure out how to fix the production code and avoid this problem in the future.
What is it about the attached markup that causes this issue? I've fooled around with this code quite a bit and the best I can figure out is that DW is confused when both the start- and end- span tags are followed immediately by a line break. Inserting a space in either place makes the issue go away.   But the production code doesn't have any occurances of this pattern. And, anyway, line-breaks have no significance to html, just for source-code formatting, right?
Am I missing something incredibly obvious?
TIA
hen3ry

Nancy O:
Thank you for your response, which gave me valuable clues to understanding the issues.   (Specifically, it led me to re-read and understand better the nitty-gritty of the HTML4 specs, section 7, "The global structure of an HTML Document", especially 7.5.1 The BODY element.)
I believe you are saying --in sum-- that to be reliably edited in DW, each source file must comprise a syntactically correct and complete HTML Document.
I am attaching a second file, "badcode2.html", modified substantially as you suggest. It passes the DW validator, the validator.w3.org test, and the www.totalvalidator.com test.    No errors or warnings.
I do this:   Launch DW, open this file, choose Design View if necessary, select the final word of text, "badda", and activate Edit-->Cut (or Delete).   As before, all the other text is deleted as well. This is repeatable.
It seems to me this sample code satisfies your general principle. Could I be misapplying the three validation tests? Or that passing these tests does not assure the document is syntactically correct and complete?   Can you recommend other tests?
I'd like to add the following two points as a matter of background and a bit of niggling:
--I'm aware that complete HTML pages must contain <html> , <head>, and <body> tags, although the HTML4 specification seems to say <body> tags are optional.   All my production pages, as served, contain these tags.   My underlying design is a php template with individual content files incorporated by inclusion.   There may be only one set of <html> , <head>, and <body> in a page. The "outer" template code provides these tags, and individual content files cannot contain a nested set -- so they must be "bare" markup.   Is DW able to support this design, in which "bare markup" files are seemingly unavoidable?    Is there a mechanism analogous to DW Design-Time Style Sheets to provide virtual existence of these tags so "bare markup" files can be successfully edited? I've looked for such a mechanism but not found one.    Or some completely different method?
--You specify the inclusion of <p> or <h1> tags within the body.    Is there some special significance of <p> or <h1> with respect to stable editing in DW? My reading of the HTML4 spec indicates that a single block element is the minimal requirement for body content. Either of these tags qualify, right?   But so does <div>, and that's what I use in my current example.    Am I misunderstanding something?
Bottom line, I'm looking for a pragmatic solution for my problem:   Once in a while, among hundreds of structurally similar "bare markup" pages I edit in DW without any problem, I lose data.   If inserting an additional tag into all my content include files eliminates these occasional problems, I'm willing to do that, as long as: (1) There is an arguable technical basis for the addition, (2) the added tag does not produce anything visible on the served page, and (3) the validators don't flag the extra tag.
Suggestions, please!
Thanks,
hen3ry

Design View Removed?!

You've said Design View has been removed in your FAQ, but not said why. I use it to preview certain parts of my application instead of having to launch the app, then drill down to the point where that part of the app is visible.
It's a bit pointless saying Flash Builder 4.6 supports Design View since it is incompatible with the newer versions of Flex SDK. So if I created an application with Flex 4.8 and wanted to preview it in Design View, Flash Builder 4.6 would complain the SDK is not compatible and would not display the application.
Why did you remove Design View? Are there any plans to introduce it or something similar at a later date?

With all respect as former grouper at adobe i believe that you are taking aside here. Nothing wrong with that Don, but as iwas reading i got mixed messages... anyhow
The point i want to make clear, as i also believe some would agree and diagree is that adobe is simply gibing up with their one of the biggest inventions, JUST because a big *ss company such apple thinks inother way.
I would NOT call adobe as leader, a leader would NEVER give up on its team, which is us... developers... users and so on.
What adobe is now doing.... well they fall pretty much into a dictator mark. Why think this way is that now every company looks up to apple, the biggest company out there and they do so... they dictate users and developers and seems like everyother companie now believes that this is the thing.
It used to be, company having discussions with users and developer what should the COMPANY do, what do you developers want to see and what do users want to see and experience, but thats not the case anymore.
So basically, Adobe is no leader, they would NOT have given up on flex nor fb. A leader would have at least done some changes that makes us as the developers to feel comfortable with the transition, but they didnt... or did they ?
Now that thing with the html5... thats not gonna be the big I in this world. For instance, take C and c# they are used WIIIIIIIIDELY.... consoles, PCs, surely some customized motherboards before compilation, well i dont know that sh*t but what i know, they have been around long time one of e oldest languages BUT STILL there are alternatives which people prefer.
That leads us to one thing only, yea html5 will probably be some ones new beloved comfortable relationship-like thingy but tghere will be others who still love the kinky stuff, such as3,mxml,haxe,c,c#,xcode,python and so on...
So DONT narrow down the opportunities..... you dont see that kind of transitions in stores where all these serials suddenly start to dissappear.
As leader one would strenghten the users behind him nowthrowing them onto a thins ice where there future will be unsecure, cause that happend to me.
Andone more thing with that dictatorism thing, its not only adobe, sony and ubisoft allready have shown such indicators and also applied some of them on their products where ive seen many and pretty threattening post and also EA seems to follow that pattern.
A leader would make you comfortable with your choises cause leader belived it himself in the product, but when leader gives up, then you truly see the "leadership".
Html5 is not for everyones taste, surly not for mine,ill stay with as3 and fb4.6 till they die, then im gonne become an unemployee and will live on the government cause ive payd my taxes for long time and cause of my leader fcks up, im gonna get those taxes back. Pathetic i know, like giving up, yes... thats what adobe does on us!
Skickat från Samsung TabletDon Kerr <[email protected]> skrev:Re: Design View Removed?!
created by Don Kerr in Flash Builder 4.7 - View the full discussion
It is clear from this reaction that most people haven't been following Adobe's abandonment of Flex, over the past two years, and their total investment in other technologies and services. It is business.
My point is ... you should not expect any significant investment from Adobe in Flash Builder. So, complaining about design view, or any other features, right now is not seeing the forest for the trees.
I WAS an Adobe User Group manager for years and a huge advocate of Flash Builder. Now, I've concluded that that 4.6 is the last true version of Flash Builder.
Handwriting has been on the wall for two years now folks. Time to wake up and smell the coffee. Time to invest in other technologies like your leader, Adobe, is doing.
If you really like design views/drag n drop interface, I recommend you take a look at http://www.sencha.com for designing HTML5 rich apps. Very nice design view interface.
I've chosen not to follow Adobe into their next big thing ... because most likely they will abandon it too like they did ColdFusion and Flex/Flash Builder.
With that said, Flash Builder 4.6 for Air desktop and mobile apps is a great thing to focus on for the next two years until HTML5 begins to come even remotely close to what Flex was capable of.
My two cents ... and clearly I have emotional issues that I need therapy for.
Don Kerr
Former manager, Space City Adobe User Group at NASA
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4683950#4683950
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4683950#4683950. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Flash Builder 4.7 by email or at Adobe Forums
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

CS4 and CS6 design views

When viewing the same index file I see significant differences between the design views of Dreamweaver CS4 and Dreamweaver CS6. The index file was created in CS5. My CS4 displays it correctly while CS6 design view is not even close. The live views are correct with both.

Here is the original .php doc. (Does not contain any php because that was the exercise to insert it).
<!DOCTYPE html>
<html dir="ltr" lang="en-US">
<head>
<meta charset="UTF-8">
<title>Explore California</title>
<link rel="profile" href="http://gmpg.org/xfn/11">
<link rel="stylesheet" type="text/css" media="all" href="style.css">
</head>
<body class="home blog">
<div id="wrapper" class="hfeed">
<div id="header">
    <div id="masthead"> <a href="http://localhost/explore_ca/index.htm"><img src="images/logo.gif" width="192" height="237" alt="Explore California Home"></a></div>
    
</div>

<div id="main">
    <div id="container">
      <div id="content" role="main">
        <div id="templateID" >
          <h1>Heading</h1>
        </div>
      </div>
      
    </div>
    
    <div id="primary" class="widget-area" role="complementary">
      <ul id="baseNav">
        <li><a href="http://www.explorecalifornia.org/tours.htm" title="Explore our tours" class="tours">Tours</a></li>
        <li><a href="http://www.exlorecalifornia.org/mission.htm" title="What we think" class="mission">Mission</a></li>
        <li><a href="http://www.explorecalifornia.org/contact.htm" title="Contact and support" class="contact">Contact</a></li>
        <li><a href="http://www.explorecalifornia.org/resources.htm" title="Guidance and planning" class="resources">Resources</a></li>
        <li><a href="http://www.explorecalifornia.org/explorers.htm" title="Join our community" class="explorers current">Explorers</a></li>
      </ul>
      
    </div>
    
</div>

<div id="footer" role="contentinfo">
<div id="footerContent">
    <div id="footerMenu">
<h3>Quick Nav</h3>
    <ul id="quickNav">
      <li><a href="../tours.htm" title="Explore our tours">Tours</a></li>
      <li><a href="../mission.htm" title="What we think">Mission</a></li>
      <li><a href="../contact.htm" title="Contact and support">Contact</a></li>
      <li><a href="../resources.htm" title="Guidance and planning">Resources</a></li>
      <li><a href="../explorers.htm" title="Join our community">Explorers</a></li>
    </ul>
</div>
<div id="footerBody">
<div id="footerMidCol">
      <h3><a href="../resources/faq.htm">FAQ</a></h3>
      <p>Find out more about our tours</p>
      <h3><a href="../contact/support.htm">Support</a></h3>
      <p>Need help? It's just a click away!</p>
      <h3><a href="../resources/legal.htm">Legal Disclaimer</a></h3>
    </div>
    <div id="footerRightCol">
      <h1>Explore California</h1>
      <p>5605 Nota Street<br />
        Ventura, CA 93003</p>
      <p class="phone">866.555.4310</p>
    </div>
    </div>
</div>
          <p class="support clearBoth">Explore California © 2010 All Rights Reserved
          </p>
</div>

</div>

</body>
</html>
And here is the related css with reset code
Theme Name: Explore California
Theme URI: http://explorecalifornia.org/
Description: A new theme.
Author: Joe Lowery for Lynda.com
Version: 1.0
Tags: Western
/* =Reset default browser CSS. Based on work by Eric Meyer: http://meyerweb.com/eric/tools/css/reset/index.html
html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
          background: transparent;
          border: 0;
          margin: 0;
          padding: 0;
          vertical-align: baseline;
body {
          line-height: 1;
h1, h2, h3, h4, h5, h6 {
          clear: both;
          font-weight: normal;
ol, ul {
          list-style: none;
blockquote {
          quotes: none;
blockquote:before, blockquote:after {
          content: '';
          content: none;
del {
          text-decoration: line-through;
/* tables still need 'cellspacing="0"' in the markup */
table {
          border-collapse: collapse;
          border-spacing: 0;
a img {
          border: none;
/* =Layout
LAYOUT: Two columns
DESCRIPTION: Two-column fixed layout with one sidebar right of content
#container {
          float: right;
          margin: 0 -260px 0 0;
          width: 100%;
#content {
          margin: 0 280px 0 20px;
#primary,
#secondary {
          float: left;
          overflow: hidden;
          width: 250px;
#secondary {
          clear: right;
#footer {
          clear: both;
          width: 100%;
LAYOUT: One column, no sidebar
DESCRIPTION: One centered column with no sidebar
.one-column #content {
          margin: 0 auto;
          width: 640px;
LAYOUT: Full width, no sidebar
DESCRIPTION: Full width content with no sidebar; used for attachment pages
.single-attachment #content {
          margin: 0 auto;
          width: 900px;
/* =Fonts
body,
input,
textarea,
.page-title span,
.pingback a.url {
          font-family: Georgia, "Bitstream Charter", serif;
h3#comments-title,
h3#reply-title,
#access .menu,
#access div.menu ul,
#cancel-comment-reply-link,
.form-allowed-tags,
#site-info,
#site-title,
#wp-calendar,
.comment-meta,
.comment-body tr th,
.comment-body thead th,
.entry-content label,
.entry-content tr th,
.entry-content thead th,
.entry-meta,
.entry-title,
.entry-utility,
#respond label,
.navigation,
.page-title,
.pingback p,
.reply,
.widget-title,
.wp-caption-text,
input[type=submit] {
          font-family: "Helvetica Neue", Arial, Helvetica, "Nimbus Sans L", sans-serif;
pre {
          font-family: "Courier 10 Pitch", Courier, monospace;
code {
          font-family: Monaco, Consolas, "Andale Mono", "DejaVu Sans Mono", monospace;
/* =Structure
/* The main theme structure */
#access .menu-header,
div.menu,
#colophon,
#branding,
#main,
#wrapper {
          margin: 0 auto;
          width: 930px;
#wrapper {
          background: #fff;
          margin-top: 25px;
          padding: 0;
/* Structure the footer area */
#footer-widget-area {
          overflow: hidden;
#footer-widget-area .widget-area {
          float: left;
          margin-right: 20px;
          width: 220px;
#footer-widget-area #fourth {
          margin-right: 0;
#site-info {
          float: left;
          font-size: 14px;
          font-weight: bold;
          width: 700px;
#site-generator {
          float: right;
          width: 220px;
/* =Global Elements
/* Main global 'theme' and typographic styles */
body {
          background: #e1d8b9 url(images/page_background.jpg) repeat-x left top;
body,
input,
textarea {
          color: #666;
          font-size: 12px;
          line-height: 18px;
hr {
          background-color: #e7e7e7;
          border: 0;
          clear: both;
          height: 1px;
          margin-bottom: 18px;
/* Text elements */
p {
          margin-bottom: 18px;
ul {
          list-style: square;
          margin: 0 0 18px 1.5em;
ol {
          list-style: decimal;
          margin: 0 0 18px 1.5em;
ol ol {
          list-style: upper-alpha;
ol ol ol {
          list-style: lower-roman;
ol ol ol ol {
          list-style: lower-alpha;
ul ul,
ol ol,
ul ol,
ol ul {
          margin-bottom: 0;
dl {
          margin: 0 0 24px 0;
dt {
          font-weight: bold;
dd {
          margin-bottom: 18px;
strong {
          font-weight: bold;
cite,
em,
i {
          font-style: italic;
big {
          font-size: 131.25%;
ins {
          background: #ffc;
          text-decoration: none;
blockquote {
          font-style: italic;
          padding: 0 3em;
blockquote cite,
blockquote em,
blockquote i {
          font-style: normal;
pre {
          background: #f7f7f7;
          color: #222;
          line-height: 18px;
          margin-bottom: 18px;
          padding: 1.5em;
abbr,
acronym {
          border-bottom: 1px dotted #666;
          cursor: help;
sup,
sub {
          height: 0;
          line-height: 1;
          position: relative;
          vertical-align: baseline;
sup {
          bottom: 1ex;
sub {
          top: .5ex;
input[type="text"],
textarea {
          background: #f9f9f9;
          border: 1px solid #ccc;
          box-shadow: inset 1px 1px 1px rgba(0,0,0,0.1);
          -moz-box-shadow: inset 1px 1px 1px rgba(0,0,0,0.1);
          -webkit-box-shadow: inset 1px 1px 1px rgba(0,0,0,0.1);
          padding: 2px;
a:link {
          color: #0066cc;
a:visited {
          color: #743399;
a:active,
a:hover {
          color: #ff4b33;
/* Text meant only for screen readers */
.screen-reader-text {
          position: absolute;
          left: -9000px;
/* =Header
#header {
          padding: 30px 0 0;
          background: url(images/blog_banner.jpg) no-repeat;
          height: 187px;
          position: relative;
#masthead {
          position: absolute;
          left: 42px;
          top: -20px;
#site-title {
          float: left;
          font-size: 30px;
          line-height: 36px;
          margin: 0 0 18px 0;
          width: 700px;
#site-title a {
          color: #000;
          font-weight: bold;
          text-decoration: none;
#site-description {
          clear: right;
          float: right;
          font-style: italic;
          margin: 14px 0 18px 0;
          width: 220px;
/* This is the custom header image */
#branding img {
          border-top: 4px solid #000;
          border-bottom: 1px solid #000;
          clear: both;
          display: block;
/* =Menu
#access {
          background: #000;
          display: block;
          float: left;
          margin: 0 auto;
          width: 940px;
#access .menu-header,
div.menu {
          font-size: 13px;
          margin-left: 12px;
          width: 928px;
#access .menu-header ul,
div.menu ul {
          list-style: none;
          margin: 0;
#access .menu-header li,
div.menu li {
          float: left;
          position: relative;
#access a {
          color: #aaa;
          display: block;
          line-height: 38px;
          padding: 0 10px;
          text-decoration: none;
#access ul ul {
          box-shadow: 0px 3px 3px rgba(0,0,0,0.2);
          -moz-box-shadow: 0px 3px 3px rgba(0,0,0,0.2);
          -webkit-box-shadow: 0px 3px 3px rgba(0,0,0,0.2);
          display: none;
          position: absolute;
          top: 38px;
          left: 0;
          float: left;
          width: 180px;
          z-index: 99999;
#access ul ul li {
          min-width: 180px;
#access ul ul ul {
          left: 100%;
          top: 0;
#access ul ul a {
          background: #333;
          line-height: 1em;
          padding: 10px;
          width: 160px;
          height: auto;
#access li:hover > a,
#access ul ul :hover > a {
          background: #333;
          color: #fff;
#access ul li:hover > ul {
          display: block;
#access ul li.current_page_item > a,
#access ul li.current-menu-ancestor > a,
#access ul li.current-menu-item > a,
#access ul li.current-menu-parent > a {
          color: #fff;
* html #access ul li.current_page_item a,
* html #access ul li.current-menu-ancestor a,
* html #access ul li.current-menu-item a,
* html #access ul li.current-menu-parent a,
* html #access ul li a:hover {
          color: #fff;
/* =Content
#main {
          clear: both;
          overflow: hidden;
          padding: 40px 0 0 0;
#content {
          margin-bottom: 36px;
#content,
#content input,
#content textarea {
          color: #333;
          font-size: 16px;
          line-height: 24px;
#content p,
#content ul,
#content ol,
#content dd,
#content pre,
#content hr {
          margin-bottom: 24px;
#content ul ul,
#content ol ol,
#content ul ol,
#content ol ul {
          margin-bottom: 0;
#content pre,
#content kbd,
#content tt,
#content var {
          font-size: 15px;
          line-height: 21px;
#content code {
          font-size: 13px;
#content dt,
#content th {
          color: #000;
#content h1,
#content h2,
#content h3,
#content h4,
#content h5,
#content h6 {
          color: #000;
          line-height: 1.5em;
          margin: 0 0 20px 0;
#content table {
          border: 1px solid #e7e7e7;
          margin: 0 -1px 24px 0;
          text-align: left;
          width: 100%;
#content tr th,
#content thead th {
          color: #888;
          font-size: 12px;
          font-weight: bold;
          line-height: 18px;
          padding: 9px 24px;
#content tr td {
          border-top: 1px solid #e7e7e7;
          padding: 6px 24px;
#content tr.odd td {
          background: #f2f7fc;
.hentry {
          margin: 0 0 48px 0;
.home .sticky {
          background: #f2f7fc;
          border-top: 4px solid #000;
          margin-left: -20px;
          margin-right: -20px;
          padding: 18px 20px;
.single .hentry {
          margin: 0 0 36px 0;
.page-title {
          color: #000;
          font-size: 14px;
          font-weight: bold;
          margin: 0 0 36px 0;
.page-title span {
          color: #333;
          font-size: 16px;
          font-style: italic;
          font-weight: normal;
.page-title a:link,
.page-title a:visited {
          color: #888;
          text-decoration: none;
.page-title a:active,
.page-title a:hover {
          color: #ff4b33;
#content .entry-title {
          color: #000;
          font-size: 21px;
          font-weight: bold;
          line-height: 1.3em;
          margin-bottom: 0;
.entry-title a:link,
.entry-title a:visited {
          color: #000;
          text-decoration: none;
.entry-title a:active,
.entry-title a:hover {
          color: #ff4b33;
.entry-meta {
          color: #888;
          font-size: 12px;
.entry-meta abbr,
.entry-utility abbr {
          border: none;
.entry-meta abbr:hover,
.entry-utility abbr:hover {
          border-bottom: 1px dotted #666;
.entry-content,
.entry-summary {
          clear: both;
          padding: 12px 0 0 0;
#content .entry-summary p:last-child {
          margin-bottom: 12px;
.entry-content fieldset {
          border: 1px solid #e7e7e7;
          margin: 0 0 24px 0;
          padding: 24px;
.entry-content fieldset legend {
          background: #fff;
          color: #000;
          font-weight: bold;
          padding: 0 24px;
.entry-content input {
          margin: 0 0 24px 0;
.entry-content input.file,
.entry-content input.button {
          margin-right: 24px;
.entry-content label {
          color: #888;
          font-size: 12px;
.entry-content select {
          margin: 0 0 24px 0;
.entry-content sup,
.entry-content sub {
          font-size: 10px;
.entry-content blockquote.left {
          float: left;
          margin-left: 0;
          margin-right: 24px;
          text-align: right;
          width: 33%;
.entry-content blockquote.right {
          float: right;
          margin-left: 24px;
          margin-right: 0;
          text-align: left;
          width: 33%;
.page-link {
          color: #000;
          font-weight: bold;
          margin: 0 0 22px 0;
          word-spacing: 0.5em;
.page-link a:link,
.page-link a:visited {
          background: #f1f1f1;
          color: #333;
          font-weight: normal;
          padding: 0.5em 0.75em;
          text-decoration: none;
.home .sticky .page-link a {
          background: #d9e8f7;
.page-link a:active,
.page-link a:hover {
          color: #ff4b33;
body.page .edit-link {
          clear: both;
          display: block;
#entry-author-info {
          background: #f2f7fc;
          border-top: 4px solid #000;
          clear: both;
          font-size: 14px;
          line-height: 20px;
          margin: 24px 0;
          overflow: hidden;
          padding: 18px 20px;
#entry-author-info #author-avatar {
          background: #fff;
          border: 1px solid #e7e7e7;
          float: left;
          height: 60px;
          margin: 0 -104px 0 0;
          padding: 11px;
#entry-author-info #author-description {
          float: left;
          margin: 0 0 0 104px;
#entry-author-info h2 {
          color: #000;
          font-size: 100%;
          font-weight: bold;
          margin-bottom: 0;
.entry-utility {
          clear: both;
          color: #888;
          font-size: 12px;
          line-height: 18px;
.entry-meta a,
.entry-utility a {
          color: #888;
.entry-meta a:hover,
.entry-utility a:hover {
          color: #ff4b33;
#content .video-player {
          padding: 0;
/* =Asides
.home #content .category-asides p {
          font-size: 14px;
          line-height: 20px;
          margin-bottom: 10px;
          margin-top: 0;
.home .hentry.category-asides {
          padding: 0;
.home #content .category-asides .entry-content {
          padding-top: 0;
/* =Gallery listing
.category-gallery .size-thumbnail img {
          border: 10px solid #f1f1f1;
          margin-bottom: 0;
.category-gallery .gallery-thumb {
          float: left;
          margin-right: 20px;
          margin-top: -4px;
.home #content .category-gallery .entry-utility {
          padding-top: 4px;
/* =Attachment pages
.attachment .entry-content .entry-caption {
          font-size: 140%;
          margin-top: 24px;
.attachment .entry-content .nav-previous a:before {
          content: '\2190\00a0';
.attachment .entry-content .nav-next a:after {
          content: '\00a0\2192';
/* =Images
#content img {
          margin: 0;
          height: auto;
          max-width: 640px;
          width: auto;
#content .attachment img {
          max-width: 900px;
#content .alignleft,
#content img.alignleft {
          display: inline;
          float: left;
          margin-right: 24px;
          margin-top: 4px;
#content .alignright,
#content img.alignright {
          display: inline;
          float: right;
          margin-left: 24px;
          margin-top: 4px;
#content .aligncenter,
#content img.aligncenter {
          clear: both;
          display: block;
          margin-left: auto;
          margin-right: auto;
#content img.alignleft,
#content img.alignright,
#content img.aligncenter {
          margin-bottom: 12px;
#content .wp-caption {
          background: #f1f1f1;
          line-height: 18px;
          margin-bottom: 20px;
          padding: 4px;
          text-align: center;
#content .wp-caption img {
          margin: 5px 5px 0;
#content .wp-caption p.wp-caption-text {
          color: #888;
          font-size: 12px;
          margin: 5px;
#content .wp-smiley {
          margin: 0;
#content .gallery {
          margin: 0 auto 18px;
#content .gallery .gallery-item {
          float: left;
          margin-top: 0;
          text-align: center;
          width: 33%;
#content .gallery img {
          border: 2px solid #cfcfcf;
#content .gallery .gallery-caption {
          color: #888;
          font-size: 12px;
          margin: 0 0 12px;
#content .gallery dl {
          margin: 0;
#content .gallery img {
          border: 10px solid #f1f1f1;
#content .gallery br+br {
          display: none;
#content .attachment img { /* single attachment images should be centered */
          display: block;
          margin: 0 auto;
/* =Navigation
.navigation {
          color: #888;
          font-size: 12px;
          line-height: 18px;
          overflow: hidden;
.navigation a:link,
.navigation a:visited {
          color: #888;
          text-decoration: none;
.navigation a:active,
.navigation a:hover {
          color: #ff4b33;
.nav-previous {
          float: left;
          width: 50%;
.nav-next {
          float: right;
          text-align: right;
          width: 50%;
#nav-above {
          margin: 0 0 18px 0;
#nav-above {
          display: none;
.paged #nav-above,
.single #nav-above {
          display: block;
#nav-below {
          margin: -18px 0 0 0;
/* =Comments
#comments {
          clear: both;
#comments .navigation {
          padding: 0 0 18px 0;
h3#comments-title,
h3#reply-title {
          color: #000;
          font-size: 20px;
          font-weight: bold;
          margin-bottom: 0;
h3#comments-title {
          padding: 24px 0;
.commentlist {
          list-style: none;
          margin: 0;
.commentlist li.comment {
          border-bottom: 1px solid #e7e7e7;
          line-height: 24px;
          margin: 0 0 24px 0;
          padding: 0 0 0 56px;
          position: relative;
.commentlist li:last-child {
          border-bottom: none;
          margin-bottom: 0;
#comments .comment-body ul,
#comments .comment-body ol {
          margin-bottom: 18px;
#comments .comment-body p:last-child {
          margin-bottom: 6px;
#comments .comment-body blockquote p:last-child {
          margin-bottom: 24px;
.commentlist ol {
          list-style: decimal;
.commentlist .avatar {
          position: absolute;
          top: 4px;
          left: 0;
.comment-author {
.comment-author cite {
          color: #000;
          font-style: normal;
          font-weight: bold;
.comment-author .says {
          font-style: italic;
.comment-meta {
          font-size: 12px;
          margin: 0 0 18px 0;
.comment-meta a:link,
.comment-meta a:visited {
          color: #888;
          text-decoration: none;
.comment-meta a:active,
.comment-meta a:hover {
          color: #ff4b33;
.commentlist .even {
.commentlist .bypostauthor {
.reply {
          font-size: 12px;
          padding: 0 0 24px 0;
.reply a,
a.comment-edit-link {
          color: #888;
.reply a:hover,
a.comment-edit-link:hover {
          color: #ff4b33;
.commentlist .children {
          list-style: none;
          margin: 0;
.commentlist .children li {
          border: none;
          margin: 0;
.nopassword,
.nocomments {
          display: none;
#comments .pingback {
          border-bottom: 1px solid #e7e7e7;
          margin-bottom: 18px;
          padding-bottom: 18px;
.commentlist li.comment+li.pingback {
          margin-top: -6px;
#comments .pingback p {
          color: #888;
          display: block;
          font-size: 12px;
          line-height: 18px;
          margin: 0;
#comments .pingback .url {
          font-size: 13px;
          font-style: italic;
/* Comments form */
input[type=submit] {
          color: #333;
#respond {
          border-top: 1px solid #e7e7e7;
          margin: 24px 0;
          overflow: hidden;
          position: relative;
#respond p {
          margin: 0;
#respond .comment-notes {
          margin-bottom: 1em;
.form-allowed-tags {
          line-height: 1em;
.children #respond {
          margin: 0 48px 0 0;
h3#reply-title {
          margin: 18px 0;
#comments-list #respond {
          margin: 0 0 18px 0;
#comments-list ul #respond {
          margin: 0;
#cancel-comment-reply-link {
          font-size: 12px;
          font-weight: normal;
          line-height: 18px;
#respond .required {
          color: #ff4b33;
          font-weight: bold;
#respond label {
          color: #888;
          font-size: 12px;
#respond input {
          margin: 0 0 9px;
          width: 98%;
#respond textarea {
          width: 98%;
#respond .form-allowed-tags {
          color: #888;
          font-size: 12px;
          line-height: 18px;
#respond .form-allowed-tags code {
          font-size: 11px;
#respond .form-submit {
          margin: 12px 0;
#respond .form-submit input {
          font-size: 14px;
          width: auto;
/* =Widget Areas
.widget-area ul {
          list-style: none;
          margin-left: 0;
.widget-area ul ul {
          list-style: square;
          margin-left: 1.3em;
.widget_search #s {/* This keeps the search inputs in line */
          width: 60%;
.widget_search label {
          display: none;
.widget-container {
          margin: 0 0 18px 45px;
.widget-title {
          color: #3B6B91;
          font-weight: bold;
.widget-area a:link,
.widget-area a:visited {
          text-decoration: none;
.widget-area a:active,
.widget-area a:hover {
          text-decoration: underline;
.widget-area .entry-meta {
          font-size: 11px;
#wp_tag_cloud div {
          line-height: 1.6em;
#wp-calendar {
          width: 100%;
#wp-calendar caption {
          color: #222;
          font-size: 14px;
          font-weight: bold;
          padding-bottom: 4px;
          text-align: left;
#wp-calendar thead {
          font-size: 11px;
#wp-calendar thead th {
#wp-calendar tbody {
          color: #aaa;
#wp-calendar tbody td {
          background: #f5f5f5;
          border: 1px solid #fff;
          padding: 3px 0 2px;
          text-align: center;
#wp-calendar tbody .pad {
          background: none;
#wp-calendar tfoot #next {
          text-align: right;
.widget_rss a.rsswidget {
          color: #000;
.widget_rss a.rsswidget:hover {
          color: #ff4b33;
.widget_rss .widget-title img {
          width: 11px;
          height: 11px;
/* Main sidebars */
#main .widget-area ul {
          margin-left: 0;
          padding: 0 20px 0 0;
#main .widget-area ul ul {
          border: none;
          margin-left: 1.3em;
          padding: 0;
#primary {
#secondary {
/* Footer widget areas */
#footer-widget-area {
/* =Footer
#footer {
          margin-bottom: 20px;
          background: url(images/footer_back.gif) no-repeat center top;
          height: 600px;
#colophon {
          overflow: hidden;
          padding: 45px 0;
          font-weight: bold;
          color: #FFF;
          text-align: center;
#site-info {
          font-weight: bold;
#site-info a {
          color: #000;
          text-decoration: none;
#site-generator {
          font-style: italic;
          position: relative;
#site-generator a {
          background: url(images/wordpress.png) center left no-repeat;
          color: #666;
          display: inline-block;
          line-height: 16px;
          padding-left: 20px;
          text-decoration: none;
#site-generator a:hover {
          text-decoration: underline;
img#wpstats {
          display: block;
          margin: 0 auto 10px;
/* =Mobile Safari ( iPad, iPhone and iPod Touch )
pre {
          -webkit-text-size-adjust: 140%;
code {
          -webkit-text-size-adjust: 160%;
#access,
.entry-meta,
.entry-utility,
.navigation,
.widget-area {
          -webkit-text-size-adjust: 120%;
#site-description {
          -webkit-text-size-adjust: none;
/* =Print Style
@media print {
          body {
                    background: none !important;
          #wrapper {
                    clear: both !important;
                    display: block !important;
                    float: none !important;
                    position: relative !important;
          #header {
                    border-bottom: 2pt solid #000;
                    padding-bottom: 18pt;
          #colophon {
                    border-top: 2pt solid #000;
          #site-title,
          #site-description {
                    float: none;
                    line-height: 1.4em;
                    margin: 0;
                    padding: 0;
          #site-title {
                    font-size: 13pt;
          .entry-content {
                    font-size: 14pt;
                    line-height: 1.6em;
          .entry-title {
                    font-size: 21pt;
          #access,
          #branding img,
          #respond,
          .comment-edit-link,
          .edit-link,
          .navigation,
          .page-link,
          .widget-area {
                    display: none !important;
          #container,
          #header,
          #footer {
                    margin: 0;
                    width: 100%;
          #content,
          .one-column #content {
                    margin: 24pt 0 0;
                    width: 100%;
          .wp-caption p {
                    font-size: 11pt;
          #site-info,
          #site-generator {
                    float: none;
                    width: auto;
          #colophon {
                    width: auto;
          img#wpstats {
                    display: none;
          #site-generator a {
                    margin: 0;
                    padding: 0;
          #entry-author-info {
                    border: 1px solid #e7e7e7;
          #main {
                    display: inline;
          .home .sticky {
                    border: none;
/* -------- sidebar region --------*/
#sidebar .sidebarContent {
          padding-left: 45px;
/* base navigation */
ul#baseNav {
          float: left;
          list-style: none;
          margin:0;
          padding:0;
          margin-bottom: 30px;
ul#baseNav li {
          margin: 0;
          padding: 0;
ul#baseNav li a{
          display: block;
          width: 272px;
          height: 70px;
          text-indent: -1000em;
ul#baseNav li a.tours {
          background: url(images/tours_main.gif) no-repeat left top;
ul#baseNav li a.mission{
          background: url(images/mission_main.gif) no-repeat left top;
ul#baseNav li a.contact {
          background: url(images/contact_main.gif) no-repeat left top;
ul#baseNav li a.resources {
          background: url(images/resource_main.gif) no-repeat left top;
ul#baseNav li a.explorers {
          background: url(images/explorers_main.gif) no-repeat left top;
ul#baseNav li a.current, ul#baseNav li a.current:hover {
          background-position: right top;
          border: none;
          cursor: default;
ul#baseNav li a:hover {
          background-position: -272px 0;
          border: none;
/* ------- footer region ------- */
#footer h1 {
          padding: 0;
#footer h3 {
          font: normal 1.3em Arial, Helvetica, sans-serif;
          color: #fff;
          margin-bottom: 0.5em;
          letter-spacing: 0.1em;
          margin-top: 0px;
#footer p{
          font: normal 1em Georgia, "Times New Roman", Times, serif;
          color: #fff;
#footer p.support {
          font-size: 0.8em;
          text-align: center;
          padding-top: 250px;
#footer p.support a{
          color: #147;
#footer p.support a:hover{
          color: #147;
          border-bottom: 1px dashed #147;
          text-decoration:none;
#footer ul#quickNav {
          list-style: none;
          margin: 0;
          padding: 0;
#footer ul#quickNav li {
          margin: 0 0 .5em 0;
          padding: 0 ;
#footer ul#quickNav li a{
          text-decoration: none;
          color: #fff;
          font-size: 1em;
          font-family: Georgia, "Times New Roman", Times, serif;
#footer ul#quickNav li a:hover {
          color: #193742;
          border-bottom-color: #193742;
#footer #footerMenu {
          float: left;
          width: 230px;
#footer #footerBody {
          float: right;
          width: 540px;
#footer #footerBody a {
          text-decoration: none;
          color: #fff;
#footer #footerBody a:hover {
          color: #193742;
          border-bottom-color: #193742;
#footer #footerBody #footerMidCol {
          float: left;
          width: 270px;
#footer #footerBody #footerMidCol p {
          margin-bottom: 2em;
#footer #footerBody #footerRightCol {
          float: right;
          width: 270px;
#footer #footerBody #footerRightCol h1{
          font: bold 1.6em Georgia, "Times New Roman", Times, serif;
          color: #fff;
          letter-spacing:.1em;
          text-align:right;
          margin-bottom: .25em;
#footer #footerBody #footerRightCol p{
          color: #fff;
          letter-spacing:.1em;
          line-height: 1.2;
          text-align:right;
          margin-bottom: 1em;
#footer #footerBody #footerRightCol p.phone{
          font: bold 1.6em Georgia, "Times New Roman", Times, serif;
          color: #fff;
          letter-spacing:.1em;
/* Page template rules */
#templateID h1 {
          text-align: center;
          font: 4em "Trebuchet MS", Arial, Helvetica, sans-serif;
#footer #footerContent {
          padding: 45px 30px 0px;
          overflow: hidden;

Can not see two fields in Crystal 2008 Developer explorer/designer view

I am currently developing crystal 2008 reports against the salesforce.com database using version 12.0.0.683 CR Developer Full version. I am using an updated driver that was provided in July or Aug 08 in order to view self referencing fields. The problem is that when I try and report against one of the tables (lead history) I cannot view two of the fields (New Value and Old Value)? I can see these two field (New Value and Old Value) in the database expert as the last two fields in the actual table, but the two fields are missing when I go into the explorer/designer view. In Salesforce, these two fields can not be filtered on, but I can export all the values in this table using Salesforece Apex data loader.

Please re-post if this is still an issue to the OnDemand Forum or purchase a case and have a dedicated support engineer work with you directly

Unable to view php files in Design View?

Need help! I cannot select design view when working with a PHP document, the DesignView option is disabled?
My information.
- Dreamweaver CS5
- Mac OSX 10.6 snow Lepoard
I have searched online and I also went through the FAQ but couldn’t find anything relating to this particular issue and my Professor at school said that I need to contact Adobe directly as design view should always be available but all that I would see in Design View are the HTML elements within the PHP file.
The Design View button is disabled, I can not click on it all and so for my class assignments. I have to copy the PHP code into a new HTML document and only then am I able to view the html/php and edit the HTML elements, and then copy and paste it back into the PHP file once I have the html elements/design set up correctly.
I did a similar “Set up PHP for Mac OS X – MAMP” to the version available here, could I have set this up incorrectly and that is why Design View is disabled?
Thanks I appreciate your guys expertise and any help!

Kanjan wrote:
Need help! I cannot select design view when working with a PHP document, the DesignView option is disabled?
Go to Dreamweaver > Preferences, and select File Types / Editors from the Category list on the left. Make sure that .php is NOT listed among the filename extensions in "Open in code view".
Adding a filename extension to that list prevents files from being opened in Design view.

Can not see the design view nor the java file in CentOS

Hi all. I've recently installed JSC2 in CentOS. I find this tool really useful. But I have a problem with the design view and the java file view. At the beginning, when I first create a Page1.jsp, I can see the design view and the java view with no problem. I run apps correctly. But after a while, I get a "null pointer exception" error and I am able to see only the jsp view, not the others. I don't even have the option to see the Design and Java views. And the page icon in the project window appears to be darker than a well working page. I'm not really sure what sequence of actions I do to get this error, it just suddenly happens. What I've done so far in JSC2 is to link to pages in the Page Navigation view. It works fine for a while, but after a while I get the error I've described.

Yes, if I do that It happens the same. I've tried everything. Now I'm using Window$ 2000 and it works properly. Thanks anyway.

Images broken in design view on new computer paths leading to old harddrive?

I recently got a new imac and installed cs5 dreamweaver ( I was using dreamweaver 8 but it no longer works in mountain lion) . I redfined the site all was fine then I must have done something and now suddenly all my images are broken in design view and in brower and live view! The site shows the images online from the server but everything is broken in design view. The directory is a mess as I used way too may subfolders when I first did the site but it's too large to start over. I tried deleting the site from my harddrive all together and creating a new folder for it and just getting the entire site from the server but the images still don't show. I don't want to have to go to every page on the site and fix broken links! I can pull an image into a page by browsing to the folder on my harddrive but they are not appearing anymore on their own. If the images were uploaded originally from another computer and the folder being used now for the site on my harddrive is different that won't break the image paths will it? It all worked fine until a few days ago. What I don't understand is I thought the images wouldn't show if they were only on the server and not on my harddrive but since I just GOT the site from the server, all the images ARE now on my harddrive in the new folder so why still nothing showing? I I tried right clicking the broken images and showing design notes they seem to be lookin for a path to my old computer where the harddrive was named differently than it is now. Is there ANY way to fix this? What about renaming my harddrive to the old name?
Greatful for any advice but I am very much a newbie so not sure I will be able to do what I need to.
Mary Ann

Spaces in folder/filenames are not a good practice. Space are converted to %20 on the server. DW's Design View often can't reconcile this. Best advice is to remove the spaces and use underscores _ or hyphens -
Rename this:
http://www.thedqtimes.com/Jane_site/Lake%20Effects/lakeeffectsjdaughters.jpg
http://www.thedqtimes.com/Becky%20H%20stories/Untitled-1.jpg
To this:
http://www.thedqtimes.com/Jane_site/Lake_Effects/lakeeffectsjdaughters.jpg
http://www.thedqtimes.com/Becky_H_stories/Untitled-1.jpg
Also, you have a misplaced <head> tag. It needs to be above the Dynamic drive Javascript code.
<head>
<script> </script>
<style> <style>
</head>
Some pages are missing an HTML doc type declaration. This sends browsers into Quirks Mode.
Use validation tools to check for other code errors.
Code Validation Tools
CSS - http://jigsaw.w3.org/css-validator/
HTML - http://validator.w3.org/
Nancy O.

Images and styles not showing in Design view on CS3

Hi all,
I am playing around with a CSS website template that I downloaded and
opened in DW-CS3. I am just using this to learn and play around with. It
came with the style sheet, jpg images etc.
I just noticed that when in Design view for the index page, that the images
and styles, menus are not displaying, only the html text is visible in Design view.
When I preview the site with a browser like IE or FF, it displays fine along with
any changes I have made.
Does anyone have any ideas?
Regards,
dano

In DW, View > Style Rendering > Display Styles on?
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Design view and browser view in DW are different than when I view from local folder

I'm brand new to Dreamweaver CS5.5 and here is my problem:
I've made an html page in dreamweaver with a banner, with an additional graphic and some text on top of the banner. It displays just fine in every browser when I view from the local folder, but when I open DW and view, it displays incorrectly in all three design, live and browser views within DW. If I make changes to the css file until it views correctly in design view, it no longer displays correctly from the local folder and it still doesn't view correctly in live or browser view within DW. If what I'm doing isnt going to display accurately in any of the views provided by Dreamweaver as compared to the live server, whats the point in having this software? I could just keep building webpages in notepad and uploading with CoreFTP.
Any suggestions? Is it some setting that I dont know about that I need to change within DW? Please help.

align="center" is deprecated (obsolete) code in XHTML & HTML5 doc types. Instead of styling markup with HTML, you should be using CSS.
CSS
.center {text-align:center}
HTML
<p class="center">some centered text here</p>
With respect to break tags, in XHTML doc types the correct syntax is <br /> not <br>. However your usage of line breaks is inconsistent with good symantic markup. Use headings <h1> <h2> <h3> <h4> for important keywords. Use <p> for descriptive paragraphs. Use <ul> <li> or <ol> <li> for lists. Line breaks should be used minimally if ever.
XHTML doc types require all tags to be lowercase. Uppercase tags will throw errors.
Your design is too rigid. When text size is increased in browsers, your content is unreadable. See screenshot.
SOLUTIONS:
1) DO NOT USE POSITION ABSOLUTE. You don't need it. Absolute positioning removes content from the normal document flow resulting in a jumbled mess. Use default CSS positioning (none) with margins, padding & floats to align elements.
2) Remove HEIGHT values from all CSS containers. Height limits a container's capacity to hold more content when needed. Container height should always be determined by the amount of content it holds; not explicit values. If required to reveal a background image, for example, use CSS min-height instead of height.
CSS Box Model
http://www.w3schools.com/css/css_boxmodel.asp
CSS Floats
http://www.w3schools.com/cssref/pr_class_float.asp
CSS min-height
http://www.w3schools.com/cssref/pr_dim_min-height.asp
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb
http://alt-web.blogspot.com/

How to add addtitional pages in design view?

How do I create additional pages in design view? I have tried using NEW PAGE AFTER, but that doesnt add another page in design view, like I need.
I am creating a report that uses 8 subreports per page to dynamically create labels. Currently I have a report header, and am using the page header to arrange the subreports so the top of each subreport prints on the top of each label. The fields in the subreports can grow, and fill in the label from the top down.
I need to create a multiple pages using this format, but I dont know how to add more pages in design view. Essentially I need subreports 1-8 on page 1, 9-16 on page 2, etc. I would like to preserve the formatting I have created thus far, but I can always change it if I have to.

In attempting to create the label sheets I needed, I ended up creating 14 separate reports (which report on 6 individual queries), because there are 14 pages worth of labels that need to be created. What I wish to accomplish is to condense these 14 reports down to 6 reports. One for each query. What I absolutely cant find a way to do, is to get Crystal Reports to allow me to customize subreports on consecutive pages. Again, I have 8 subreports on each page, which have been formatted to fit on 8 labels when printed. Each subreport is identical in design, but has a different range selected (i.e. my driving value in each subreport has been modified with Select Expert to be between 1 and 5, or 6 and 10, or 11 and 15). This is how I have been able to return 5 consecutive results on each label, with the next label returning the following 5 results.
My ultimate question: Is it possible to create a multi-page report using this method?

Is it possible to print from design view in CS3

I've got a summary print out / display page for a CF application that I'd like to be able to print out in Design view.
DW CS3 only seems to print the code page and I don't want to print from a browser as that will only show the options currently selected - I'm after having all options displayed.
Is it possible? Any suggestions other than printScreen?

No, you can't print from Design view. It seems as though screen capture is your best option,

Design view is empty

I'm able to see the html/cf code in the code view, but in the
design view I don't see anything, to include tables, etc. I'm using
DWMX2004.
Any ideas?
Thanks.
Force

Does the page validate? If not, then fix the validation
errors. That's the
best way to approach troublesome pages.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"n h c" <[email protected]> wrote in message
news:er02tr$g93$[email protected]..
>
quote:
Originally posted by:
Newsgroup User
> > if that makes any sense.
>
> It doesn't really. If the page is valid HTML, you will
see it in DW.
> Even
> when it is a combination of some scripting language and
HTML, you will see
> something.
>
>
> well, maybe that's how it should be. but this website
defies all reason
> and
> convention. i think most people would have quit/suffered
a nervous
> breakdown/killed my boss by now. the people who worked
here before me left
> quite a mess, i must say.
>
> i think the code probably isn't valid. but i really
don't know enough
> about
> coding yet to fix it. and it works, it just makes it
hard to figure out
> where i
> need to edit things sometimes.
>
> but we're not discussing my ridiculous website here! not
anymore, at
> least.
>
> -courtney
>
>

Significance of design view

Similar Messages

Maybe you are looking for