Base url

Thanks. Yes, clearing the MODx cache helped somewhat, but not until I did a deep clean of all browser caches was it consistently better. I was also using Coda for previews and it just would not update until I quit everything, cleaned and restarted. It would appear that there was a indeed cache issue on several fronts. I also installed a fresh copy of MODx in a new directory and the missing CSS seems to have been fixed somehow. Don’t know why, but so far so good. [crosses fingers]

When I see stuff like that, I clear the MODx cache, then load a new instance of a browser, then clear the browser cache and cookies before visiting the site.

Quote from: OpenGeek at Apr 30, 2009, 12:43 PM

Quote from: Everett at Apr 29, 2009, 11:18 PM

I think goonz is correct -- I’ve found it’s always less trouble to declare your paths absolutely: use a leading slash to identify exactly which file you are referencing.

I think this is a cop out for not coding components correctly TBH. To make portable, reusable components and content in MODx, you should ALWAYS use relative paths. That is the whole purpose of having these settings (base_path, base_url, site_url, etc.).

It happens to be that I use relative links in all of my sites, with the exception of links. You get better rankings SEO-wise with absolute links, so I always use:

It makes it a bit longer when coding, but SEO is worth it!
Also, for wayfinder, I use the following code, if you’re looking for it: