CS4 to CS3 Design View Preview
Is it possable to to preview Dreamweaver CS4 in CS3 Design View? I only have CS4 on my machine and a customer with CS3 wants to make changes to my work. The CSS styles do not render correctly. Is there anything I can do to to correct this? Everything works in the browsers.
Nope. Some show - some don't.
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
==================
"jhabrix" <[email protected]> wrote in
message
news:faom5n$9ku$[email protected]..
> Bump....
>
> Anyone have a solution to the above problem???
Similar Messages
-
CS3 - Design View not showing externally linked images
In CS3 Design View, externally linked images are not showing
up... i am only getting the place holder.
To prempt some questions:
1/ Links are correct and complete - apart from the fact that
they show up when previewing in the browser(s) - i have
crosschecked
2/ There are no spaces in the url
3/ In the 'View' menu, 'Display External Files' is checked
I had this problem before and escargo suggested saving and
rebooting. It worked then but strangely, today, that file is again
showing some of the externally linked images but not all. And on a
new file, created today, none of the externally linked images are
showing up... :(
I'm sure there's a simple solution to the problem... anyone
have any idea what it could be?
Thanks and cheers,
JJNope. Some show - some don't.
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
==================
"jhabrix" <[email protected]> wrote in
message
news:faom5n$9ku$[email protected]..
> Bump....
>
> Anyone have a solution to the above problem??? -
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
hen3ryNancy 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 -
Can't edit text in CS3 design view
Hi,
I have a big absolutely positioned DIV tag in most of my
pages, practically the whole page content is inside it.
In DW CS3 design view very often (maybe 50% of all times) if
I click inside it to edit the text, DW selects the entire DIV tag.
The cursor becomes like a cross with arrows, the DIV border becomes
outlined with a thick blue line, and I can't edit the text no
matter how much times I click. If I move the mouse with left button
pressed, this moves the DIV and changes the .css file where the
position is defined. DIV can't be de-selected with Escape, left or
right clicking.
The only way to get out of this is to click somewhere in the
code view, then go back to design view where hopefully text can be
edited. Sometimes I have to repeat this twice or even 3 times ,
it's extremely annoying and time consuming.
Is there any workaround?
Like to disable selection of containers in design view, or at
least a quick way to deselect the current selection?
This problem does not appear in DW8 when editing the same
files.
thanks> I have a big absolutely positioned DIV tag in most of my
pages,
> practically
> the whole page content is inside it.
Nasty. Why?
Do you have an overflow style on this div?
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
==================
"harpo_" <[email protected]> wrote in
message
news:f0igi1$3dn$[email protected]..
> Hi,
>
> I have a big absolutely positioned DIV tag in most of my
pages,
> practically
> the whole page content is inside it.
> In DW CS3 design view very often (maybe 50% of all
times) if I click
> inside it
> to edit the text, DW selects the entire DIV tag. The
cursor becomes like a
> cross with arrows, the DIV border becomes outlined with
a thick blue line,
> and
> I can't edit the text no matter how much times I click.
If I move the
> mouse
> with left button pressed, this moves the DIV and changes
the .css file
> where
> the position is defined. DIV can't be de-selected with
Escape, left or
> right
> clicking.
> The only way to get out of this is to click somewhere in
the code view,
> then
> go back to design view where hopefully text can be
edited. Sometimes I
> have to
> repeat this twice or even 3 times , it's extremely
annoying and time
> consuming.
>
> Is there any workaround?
> Like to disable selection of containers in design view,
or at least a
> quick
> way to deselect the current selection?
>
> This problem does not appear in DW8 when editing the
same files.
>
> thanks
>
> -
Font sizes render too small in DW CS3 design view?
I have recently upgraded to DW CS3 from DW8 (which is still
installed) on my Vista Ultimate system.
For some reason CS3 occasionally renders fonts smaller than
they 'should' appear. This can be replicated using the below code
(I realise this code is not 'best practice' by any measure but it
is the simplest way I could demonstrate the problem). In DW8 design
view it renders exactly as it outputs in IE5, 6, 7, and Firefox
(with default viewing settings) but in DW CS3 the font appears much
smaller! I realise this is probably a standards issue, with CS3
probably sticking to the standards more firmly than the browsers
and DW8 but I need the design view to render as the browser will or
it is no use to me
Please do not say that I should amend my code to be more
'Standards Compliant' as my main use of DW is coding a large
PHP/MySQL invoicing system which is used within a controlled LAN on
IE6 only. It was originally written by someone else and has been
added to and updated by myself. It is very large and certainly
doesn't need rewriting just to render correctly in DW CS3 design
view.
Any help greatly appreciatedThanks, Malcom
Here is a screen shot of DW CS2 andn how the fonts are
displayed:
http://www.jlynnewines.com/images/purge_fontexample.gif
~~~
The page is:
http://www.jlynnewines.com/newsletter_archive.htm
~~~
Here is the code:
<td height="114" align="center"
valign="top"><p><font size="2" face="Arial, Helvetica,
sans-serif"><strong>December,<strong><strong>
2007</strong></strong><font size="2"
face="Arial, Helvetica, sans-serif"><strong><font
size="2" face="Arial, Helvetica,
sans-serif"><strong><br>
<br>
</strong></font></strong><font size="2"
face="Arial, Helvetica, sans-serif"><a href="
http://www.jlynnewines.com/newsletters/JL_News_Q4_2007.htm"
target="_blank">View
HTML Presentation</a><a
href="newsletters/pdf/JL_newsletter_Q2_2007.pdf"
target="_blank"><br>
</a><a href="
http://www.jlynnewines.com/newsletters/pdf/JL_newsletter_Q4_2007.pdf"
target="_blank">Printable
PDF
Version</a></font></font></strong></font></p>
<p><font size="2" face="Arial, Helvetica,
sans-serif"><strong><font size="2" face="Arial,
Helvetica, sans-serif"><strong>August,
2007<br>
<br>
</strong></font></strong><font size="2"
face="Arial, Helvetica, sans-serif"><a href="
http://www.jlynnewines.com/newsletters/JL_News_Q3_2007.htm"
target="_blank">View
HTML Presentation</a><a
href="newsletters/pdf/JL_newsletter_Q2_2007.pdf"
target="_blank"><br>
</a><a
href="newsletters/pdf/JL_newsletter_Q3_2007.pdf"
target="_blank">Printable
PDF Version</a></font></font></p>
<p><font size="2" face="Arial, Helvetica,
sans-serif"><strong><font size="2" face="Arial,
Helvetica, sans-serif">May,
2007<br>
</font></strong><font size="2" face="Arial,
Helvetica, sans-serif"><a href="
http://www.jlynnewines.com/newsletters/JL_News_Q2_2007.htm"
target="_blank">View
HTML Presentation</a><a
href="newsletters/pdf/JL_newsletter_Q2_2007.pdf"
target="_blank"><br>
Printable PDF
Version</a></font></font></p>
<p><font size="2" face="Arial, Helvetica,
sans-serif"><strong>February,
2007</strong><br>
<a href="
http://www.jlynnewines.com/newsletters/JL_News_Q1_2007.htm"
target="_blank">View
HTML Presentation</a><br>
<a href="newsletters/pdf/JL_newsletter_Q1_2007.pdf"
target="_blank">Printable
PDF
Version</a></font></p></td> -
I just upgraded to Dreamweaver CS3 from MX2004. I edit a web
page and all was OK with MX2004 but with CS3 the font size in
"Design View" is so small it is unreadable and uneditable.
Previewing or publishing the page in IE or FF and the font sizes
are normal.
I have seen others mentioning this problem on other
discussion boards but with no proper resolution.
How can I get "Design View" to display the proper size
without fudging the settings?This is a code/usage issue. Without seeing your code, we can
only guess
what you have on the page that is making this happen.
CS3 is 2 generations further along in its support of
standards and best
practice usages. As a result it is much more reliably in
rendering of CSS
layouts than DMX2004 was. Along with this increased
reliability and
standards compliance comes a much heavier emphasis on VALID
code. DMX2004
was a bit loose in what it would tolerate. In many cases, it
would ignore
things that CS3 cannot. To know where you stand with this,
try validating
your page. Does it validate?
http://validator.w3.org
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"WizardOfZo" <[email protected]> wrote in
message
news:frr5hs$ep1$[email protected]..
>I just upgraded to Dreamweaver CS3 from MX2004. I edit a
web page and all
>was
> OK with MX2004 but with CS3 the font size in "Design
View" is so small it
> is
> unreadable and uneditable. Previewing or publishing the
page in IE or FF
> and
> the font sizes are normal.
> I have seen others mentioning this problem on other
discussion boards but
> with
> no proper resolution.
> How can I get "Design View" to display the proper size
without fudging the
> settings?
> -
Server Side Includes not displaying in DW CS3 design view
I have this code in my page (see below):
When I open the file in Dreamweaver MX 2004 in design view,
the page displays correctly. That is, I see the correct styles from
the style sheet contained in Head_Standard.html and the logo/menu
in Logo_TopMenu.html
When I open the page in DW CS3, I do not see the effects of
the style sheet and I do not see the logo/menu.
However, when I change the code for the first include from:
virtual="/ServerSide
to
virtual="
../../ServerSide
then the page renders correctly in Dreamweaver CS3.
My first reaction was: what?! And my question is: how do I
use a root reference inside the head and get it to display properly
in DW CS 3?"Go to Edit > Preferences > Invisible Elements >
Server-Side Includes (Check this box) to show contents of included
file"
I already do this.
For me:
/ServerSide... does NOT work
../../ServerSide... works
So, a relative reference works and a reference to the root
does not. I have over 20 websites with root references and I need
this to work in DW9. -
Paste Doesn't Work in DW CS3 Design View
What's up with this now?
This is a fresh installation of CS3 on a Mac Pro G5. Pasting
in text from Word or Excel won't work in Design View, but it does
in Code View.
I've been doing this for a while now on another machine,
using CS2.
What am I missing? Did I overlook something? I've checked in
the Preferences, but besides the usual choices for pasting, I don't
see why this won't work.
Ideally, I'm trying to improve my process of placing tabular
data from Excel. It's a pain to paste in information cell by cell.
Why can't I paste-in ANY text of any kind in Design View?
Thanks!http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=dd550772
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"thanser" <[email protected]> wrote in
message
news:g8klm8$74k$[email protected]..
> What's up with this now?
>
> This is a fresh installation of CS3 on a Mac Pro G5.
Pasting in text from
> Word or Excel won't work in Design View, but it does in
Code View.
>
> I've been doing this for a while now on another machine,
using CS2.
>
> What am I missing? Did I overlook something? I've
checked in the
> Preferences, but besides the usual choices for pasting,
I don't see why
> this
> won't work.
>
> Ideally, I'm trying to improve my process of placing
tabular data from
> Excel.
> It's a pain to paste in information cell by cell.
>
> Why can't I paste-in ANY text of any kind in Design
View?
>
> Thanks!
> -
CS3 Design View blank when body in Editable area
Anyone run into this? It appears to be a bug, possibly new in
DW CS3 (9.0 build 3481)
When a <body> tag is put in an editable region, DW does
not recognize subsequent editable regions and Design View is blank.
When saving this template, an error appears "This template does not
have any editable regions..." However, Code Validation and Template
Syntax Check return no errors. Moving the body tag out of the
editable region corrects the problem. Here is a sample template:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
<title>Sample Template</title>
</head>
<!-- TemplateBeginEditable name="body" -->
<body id="foo">
<!-- TemplateEndEditable -->
<h1>This is template text</h1>
<!-- TemplateBeginEditable name="bodytext" -->
<p>Text does not show in Design view</p>
<!-- TemplateEndEditable -->
</body>
</html>On Wed, 27 Aug 2008 19:14:34 +0000 (UTC), "Peter Siebert"
<[email protected]> wrote:
>Anyone run into this? It appears to be a bug, possibly
new in DW CS3 (9.0 build
>3481)
> When a <body> tag is put in an editable region, DW
does not recognize
>subsequent editable regions and Design View is blank.
When saving this
>template, an error appears "This template does not have
any editable
>regions..." However, Code Validation and Template Syntax
Check return no
>errors. Moving the body tag out of the editable region
corrects the problem.
>Here is a sample template:
<body> tags are not permitted in editable regions.
If you want to add something to the body tag on individual
pages use:
search help for:
Specify editable tag attributes in a template
~Malcolm~*...
~* -
Dreamweaver CS3 design view fonts
We have installed DW CS3 and users are complaining the fonts
in design view are too small and difficult to read. It appears to
be picking this up from the stylesheet used in the site. Is there a
way to change this behavior? Obviously we do not want to change the
stylesheet to make DW happy. This doesn't appear to make much
sense.Check the Adobe technotes on how to fix this.
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
==================
"steveblevins" <[email protected]> wrote in
message
news:f46ijd$7ij$[email protected]..
> We have installed DW CS3 and users are complaining the
fonts in design
> view are
> too small and difficult to read. It appears to be
picking this up from the
> stylesheet used in the site. Is there a way to change
this behavior?
> Obviously
> we do not want to change the stylesheet to make DW
happy. This doesn't
> appear
> to make much sense.
> -
CS3 Design View And Invisible Elements
Hello, CS3 Dreamweaver often doesn't shown hidden divs. I
have an
absolutely positioned div and it seems the only way to see it
in design
view is to go to code view select the div and switch back to
design view
and with luck it will appear. View - Visual Aids - Invisible
Elements is
checked. Are there any settings I have missed or are
invisible elements
buggy in design view?
Thanks,
Chris (Hunt)DW's Design view (in any version of DW) will not show
elements with the
visibility:hidden attribute enabled unless you select the
element. An easy
way to do that would be to select it in the AP ELEMENTS
panel. Have you
tried that?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Chris (Hunt)" <[email protected]>
wrote in message
news:g70q5f$kpl$[email protected]..
> Hello, CS3 Dreamweaver often doesn't shown hidden divs.
I have an
> absolutely positioned div and it seems the only way to
see it in design
> view is to go to code view select the div and switch
back to design view
> and with luck it will appear. View - Visual Aids -
Invisible Elements is
> checked. Are there any settings I have missed or are
invisible elements
> buggy in design view?
>
> Thanks,
>
> Chris (Hunt) -
Dreamweaver CS3 Design view is gone
I did a full page layout and everything looked great. I uploaded the site and it looks fine but there are a few things I need to change. I went back to Dreamweaver and the design view image is gone. All that shows is a gray image witha small box in the upper left corner that shows a small box that looks like a missing image icon? Anyway, nothing else. The code is still there and when I go to preview in browser, it still shows the site. I do most of my work in both design view and code so would really like to find a resolve to this. Thanks!
Link: http://www.jfusekdesign.com/index2.htmlYou have a problem with the markup of your page.. viewing the page in FFox I could see a line of stray 'text' at the very top of the page...
You need to fix the syntax here:
<body class="twoColFixRtHdr" onload="MM_preloadImages('images/print_button_f2.jpg','images/web_button_f2.jpg','images/emarketing_button_f2.jpg','images/portfolio_button_f2.jpg','images/contactButton_f2.jpg','images/printOffer2.jpg','images/webOffer2.jpg','images/flash_images/print.gif','images/flash_images/Web.gif','images/flash_images/emarketing.gif')" tracingsrc="Firewo<meta name="description" content="J Fusek Design offering customized, quality print and web design at very affordable prices." />
rks/JFD_Web_FINAL_2009.png" tracingopacity="0">
See the line before: <div id="container">
rks/JFD_Web_FINAL_2009.png" tracingopacity="0"> <------this is the line that is not closed correctly and is seen in the browser. Looks like it belongs to another line and somehow, maybe deleting something or other and this has been left behind.
Once you fix that section of the code, then put the page through the validator and check to see if there are other problems:
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
You have a few errors in the lightbox stylesheet that need correcting
http://jigsaw.w3.org/css-validator/validator?profile=css21&warning=0&uri=http%3A%2F%2Fwww. jfusekdesign.com%2Findex2.html
Hopefully once all the errors are eliminated the page will show correctly in DW. It only takes an unclosed tag for example, for the page to fail to show up in design view :-) -
Dreamweaver CS3 Design View Problem
I am trying to edit a Dreamweaver site using Dreamweaver CS3 on a Windows XP workstation at work. The site structure was developed by an outside vendor and has been designed using CSS for positioning -- no tables. It is my responsibility to finish the site using template pages provided. When viewing the site in several browsers -- both Mac and PC, everything is fine. When I open the site in Dreamweaver CS3 Windows, all of the positioning is off -- the menus that should be flush left of the text colum, instead, appear at the top of the text column. This issue is repeated throughout the site. Since I am using existing pages as templates for new ones, I'm forced to make edits in code view, upload and then view in my browser. My outside vendor, so far, does not have an answer to this.
This weekend at home, I've installed an old Dreamweaver 8 trial version on my Macintosh. I downloaded the site and everything looks fine in Design View. Any ideas? Is this a settings issue on my Windows version of Dreamweaver? I do have the Style Rendering setting set to Screen Media type.Hi,
I found this thread after searching and searching for an answer as to why my Design View in DW CS3 started disappearing (even in split view). It will show a partial view, but never the entire view all at once, even after restarting my PC. I have been using CS3 for a few years now and it just started having this issue. When this issue started, nothing had changed on my computer. There has to be a fix for this. Why did it work fine all these years and now, no design view???? -
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>
<!-- #masthead -->
</div>
<!-- #header -->
<div id="main">
<div id="container">
<div id="content" role="main">
<div id="templateID" >
<h1>Heading</h1>
</div>
</div>
<!-- #content -->
</div>
<!-- #container -->
<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>
<!--<ul class="xoxo">
<li id="search-2" class="widget-container widget_search"><form role="search" method="get" id="searchform" action="http://localhost/explore_ca/">
<div><label class="screen-reader-text" for="s">Search for:</label>
<input type="text" value="" name="s" id="s">
<input type="submit" id="searchsubmit" value="Search">
</div>
</form></li> <li id="recent-posts-2" class="widget-container widget_recent_entries"> <h3 class="widget-title">Recent Posts</h3> <ul>
<li><a href="http://localhost/explore_ca/?p=4" title="Mountain Biking Rules">Mountain Biking Rules</a></li>
<li><a href="http://localhost/explore_ca/?p=1" title="Hello world!">Hello world!</a></li>
</ul>
</li><li id="archives-2" class="widget-container widget_archive"><h3 class="widget-title">Archives</h3> <select name="archive-dropdown" onchange="document.location.href=this.options[this.selectedIndex].value;"> <option value="">Select Month</option> <option value="http://localhost/explore_ca/?m=201008"> August 2010 </option>
</select>
</li><li id="categories-2" class="widget-container widget_categories"><h3 class="widget-title">Categories</h3> <ul>
<li class="cat-item cat-item-1"><a href="http://localhost/explore_ca/?cat=1" title="View all posts filed under Uncategorized">Uncategorized</a>
</li>
</ul>
</li> </ul>-->
</div>
<!-- #primary .widget-area -->
</div>
<!-- #main -->
<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>
<!-- #footer -->
</div>
<!-- #wrapper -->
</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; -
Dreamweaver CS3 Design View messed up
I'm not quite sure why, but the design view is all messed up
when I am
editing my webpage.
Here is what it looks like.
http://img257.imageshack.us/img257/4749/sammesseduphl2.jpg
but as you can see by going here
http://sdsusammys.com/rush.php
that
the page works perfectly.
I was reading some of the other peoples posts and I noticed
people who
Include php files usually have this same problem.
The beginning of the code for my rush.php page is as follows
<?php
include("includes/header.html");
?>
<?php
include("includes/navbar.php");
?>
Would that have anything to do with it?
ThanksSammy,
As for "viewing" your web page inside Dreamweaver, it is not
a good idea. Dreamweaver is a basically a HTML editing application.
Ideally speaking, best if you view your web page with any web
brower. Also check with your web page with many browsers, where you
will notice some beheavior or such difference in those two or many
browsers. It depends on how you code your HTML code per se.
Hope that helps.
Cheers, Brian
quote:
Originally posted by:
Sammy.BE
I'm not quite sure why, but the design view is all messed up
when I am
editing my webpage.
Here is what it looks like.
http://img257.imageshack.us/img257/4749/sammesseduphl2.jpg
but as you can see by going here
http://sdsusammys.com/rush.php
that
the page works perfectly.
I was reading some of the other peoples posts and I noticed
people who
Include php files usually have this same problem.
The beginning of the code for my rush.php page is as follows
<?php
include("includes/header.html");
?>
<?php
include("includes/navbar.php");
?>
Would that have anything to do with it?
Thanks
Maybe you are looking for
-
Xml Publisher Report Without RDF
Hi experts, I need to customize the seeded XML publisher report.Till now i developed XML publisher reports by developing rdf only. But here i didn't see any rdf for it.. without rdf how we can create the xml publisher report. I need to insert a field
-
Loops to a seperate partition?
Hi, I have a couple partitions on my hard drive and I want to move all my media files to a seperate partition. The is a big chunk, say 2GB of garage band in my root library>application support>garageband . Is there anyway I can move these to a sepera
-
I Have an iPhone 5 runnig ios 7.0.4. It wont start as the apple logo keeps on blinking when i connect to wall charger or itunes. I even tried to restore it but an error 21 is being displayed. Any one can help me in this situation
-
Album artwork/cover flow not showing up?
I added my own artwork to some of my songs but they are not showing up in cover flow or when I'm playing the songs. Even the songs I didn't add my own artwork to (the iTunes ones), they don't show up either. Help? =P
-
I Can't download 10G images from the site!!!!!!!!!!
for more over 2 days i'm trying to download the 10G images but i can't. it seems that is a broken links