How not to hardcode template path?

Hello folks!
I started trying MODX just today and began reading a tutorial on template building. This suggested to hardcode the paths to the template files (css, js, images).
So the HTML would be

But now I’d rather not like to hardcode these things but store the path to my template folder (i.e. /assets/templates/mytemplate) in a variable in case it changes.
So what would be the correct place for such a variable? A TV? I haven’t really got a grasp of the overall structure so far.

Are you using MODX Revolution or MODX Evolution?

I’ve always "hardcoded" the path because I have never had the necessity of changing it, but if you have to, try one of these:
1. a Template Variable + @INHERIT binding (http://rtfm.modx.com/display/revolution20/INHERIT+Binding)
2. a Template Variable + getField snippet (http://modxcms.com/forums/index.php?topic=48794.0). With this method you can basically make a Global Template Variable and use it throughout the website, and it is probably the easiest of the two methods.

Sorry, I’m using Revolution 2.1

A related question: How do I set / get the url to the MODX root?

I use Evo, but I think the Revo equivalent is [[++base_url]] or [[++site_url]]

Thanks, your are right.
Why can’t I find them in the system settings editor?

I dunno; I don’t use Revo.

Why can’t I find them in the system settings editor?

Because then they would be hardcoded

Quote from: welop at Jul 30, 2011, 09:33 PM

Why can’t I find them in the system settings editor?

Because they are created dynamically by MODx.

I often create a new system setting ’assets_path’ which contains the relative path to my assets folder which can then be accessed in the template like:

<link rel="stylesheet" href="[[++assets_path]]css/main.css" >

Quote from: bunk58 at Jul 31, 2011, 01:48 AM

Because then they would be hardcoded

Sounds reasonable
Thx @all

Yeah, there are a couple system settings (mostly relating to paths) that are hardcoded in Revo's core/config/config.inc.php file, and it is very confusing to have them not show up in the Systems Settings GUI.  I filed a Refactor Request about this a while back:
http://bugs.modx.com/issues/3596

See also the original forum discussion:
http://modxcms.com/forums/index.php/topic,60180.msg342259.html

I'd recommend using a combination of the [[++site_url]] placeholder and an HTML base tag in your templates, then you can omit the leading slash in your assets path, e.g.



Although, I do like the alternative of using the placeholder since that would allow you to use a custom assets path, thus avoiding easy fingerprinting that would identify your site as a MODx site. [ed. note: Everettg_99 last edited this post 15 years ago.]