M
Mechphisto
I have an annoying issue in Dreamweaver CS3 that I was hoping I could
get some help on.
I have a site I'm working on. The file structure is:
W:/site/
-- contains page.php which is the bare frame for all the pages. The
styles.css link and all head info, etc. is in this page.
W:/site/includes/
-- contains styles.css which has all the styles
W:/site/data/
-- contains all the actual data pages that get included into page.php
via PHP (that it's PHP is not important)
Now, when I'm working on, say, W:/site/data/123.php, the DW GUI has no
idea what styles are available as all 123.php is is text with DIV id's
and SPAN classes attributed. On the Web site, the contents of this
page would simply get included into page.php.
So the DW preview shows everything in default appearance.
If I link the styles.css into the file, sure I edit it and it'll let
me use the styles in the GUI instead of my having to keep looking at
the styles page and hand-typing in ...class="blah"....
But the link will be put in as "../includes/styles.css" which works
while I'm in DW, but doesn't while it's on the Web as...you get it,
because 123.php doesn't technically exist when it's rendered to the
browser...it's embeded in page.php so "../" becomes meaningless.
Does this make sense?
Bottom line: Is there some DW tip that will allow me to either make it
recognize PHP includes so it logically knows where everything will be
when it's rendered by the browser, or, universally apply a CSS page to
everything I'm working on without having to worry about link paths
that work fine locally but foobar on the remote?
Thanks for any suggestions.
-Liam
get some help on.
I have a site I'm working on. The file structure is:
W:/site/
-- contains page.php which is the bare frame for all the pages. The
styles.css link and all head info, etc. is in this page.
W:/site/includes/
-- contains styles.css which has all the styles
W:/site/data/
-- contains all the actual data pages that get included into page.php
via PHP (that it's PHP is not important)
Now, when I'm working on, say, W:/site/data/123.php, the DW GUI has no
idea what styles are available as all 123.php is is text with DIV id's
and SPAN classes attributed. On the Web site, the contents of this
page would simply get included into page.php.
So the DW preview shows everything in default appearance.
If I link the styles.css into the file, sure I edit it and it'll let
me use the styles in the GUI instead of my having to keep looking at
the styles page and hand-typing in ...class="blah"....
But the link will be put in as "../includes/styles.css" which works
while I'm in DW, but doesn't while it's on the Web as...you get it,
because 123.php doesn't technically exist when it's rendered to the
browser...it's embeded in page.php so "../" becomes meaningless.
Does this make sense?
Bottom line: Is there some DW tip that will allow me to either make it
recognize PHP includes so it logically knows where everything will be
when it's rendered by the browser, or, universally apply a CSS page to
everything I'm working on without having to worry about link paths
that work fine locally but foobar on the remote?
Thanks for any suggestions.
-Liam