Need the location of the style sheet be a local path rather than a full URL

I’m still trying to figure out how to resolve this – any help here would be greatly appreciated.

By the way, the 3rd URL in the previous post is incorrect – the page that is working is at:

https://news1.pandesa.com/wp-content/themes/zenful_pandesa/test1.htm

youve really made this hard to follow and much more difficult than necessary.

you cant use relative paths like this unless you start from the root directory.

why? because a page that looks like this

https://www.domain.com/categories/zzz

has a different relative path than this

https://www.domain.com/

../mystylesheet is not the same.

you need to start at the root of your install

Look at this:

https://www.village-idiot.org/css-test/test1.htm
https://www.village-idiot.org/css-test/one/test1.htm
https://www.village-idiot.org/css-test/two/three/test1.htm

All those pages are using the same stylesheet, and they all know where to find it because I have used language that tells the server to start at web-root.

<link rel="stylesheet" href="/css-test/css/style.css" type="text/css" media="screen" />

2 weeks for this?

Im for hire if that business needs someone that can actually …

Hi Whoami,
Thanks for the response. The above question is actually an attempt at a hack to fix a problem with superfish dropdowns as described here:

https://groups.google.com/group/jquery-en/browse_thread/thread/3892a06f70e46e29

As you can see, the problem with this page under IE is that superfish for some BIZARRE reason, it slows WAY down when I use an http absolute path to refer to the CSS file.

You say here that relative paths won’t work with WordPress… OK, so now I’m wondering if an absolute path that doesn’t go all the way out to the http level will work for some strange reason – I’m grasping for straws here since none of this makes sense, but its worth a try…

…the problem is that I have tried using absolute paths, but unless I use bloginfo to generate the path to the css file, it doesn’t seem to work – it can’t find my css. And bloginfo only generates paths that start with ‘http:’ which seems to be causing the problem.

You were wondering if “that business” needs help from somebody that can actually… And the answer is YES! I’m “that business” and I’m way out of my league trying to fix this issue. The original programmer for the site is no available and I’m obviously not a programmer – I’m a marketing guy. My guess is that this will only take less than an hour to fix, but I’m sure there will be other things we’ll need help with in the future. If you think you can fix this quickly without turning it into a research project, please email me at [email protected].

– John

Well, its fixed now, but it ain’t pretty. It would be much cleaner if I could figure out some way to make bloginfo return a pathname that started with “/” rather than one that starts with “https://”. Oh well.

This might be a bit late, but I think what Whoami was trying to tell you was to use a relative path starting from the web-root to your theme folder. You mentioned an absolute path that doesn’t go all the way out to ‘http/’ – the following works for me:

<link rel="stylesheet" href="wp-content/themes/my_theme/my_style.css" type="text/css" media="screen" />

I just ran into this problem as well jbadger.

dave_t, yes that works as a relative path, but it’s not dynamic. We want something like “bloginfo(‘template_directory’)” that returns a relative path and not a URL beginning with “http”.

It seems weird that this is a pretty basic thing, yet WP doesn’t have a built in function to do it?