I also think you're convinced it's an absolute path issue but it's not.
You get an error message because I'm a WP and it's PHP driven and
directories just work a little differently - people just cant get direct
access to a directory on WP, just because it exist - it just doesn't
work that
Dear Elli,
thanks for your remark. However, the CSS is from a standard template and
it works in the pages where only a single article is shown, e.g.
http://run-united.com/?page_id=489. If you look at the html structure
and the css there, the #content div still has this big margin, but
neverthless
On Wed, Jan 4, 2012 at 9:10 PM, Elli Vizcaino wrote:
> I also think you're convinced it's an absolute path issue but it's not. You
> get an error message because I'm a WP and it's PHP driven and directories
> just work a little differently - people just cant get direct access to a
> directory o
I want to thank everyone who posted back on this issue. Now I have a
couple of ways to do it.
My next task is to understand how they work and what I did wrong .
Thanks again, and sorry that my original message was html; it was an
accident.
Barry Brevik
__
>Really you had two issues going on. First was your pathing issue
>which prevented the rest of us from seeing the problem (unless we had>the font
>installed) and you did get that corrected for creampuff and I
>was able to verify that the font is now downloading properly with no
>errors.
The
