2010-09-05, 21:22:14
The only fail-safe relative path is a path relative to the domain: “/GetSimple_2.01/data/uploads/041.jpgâ€Â. Starting with a forward slash means this path will be followed starting from the domain’s root.
The problem with relative paths is that you have to think about how visitors are going to see your page in their browser. Thinks about this:
The problem with relative paths is that you have to think about how visitors are going to see your page in their browser. Thinks about this:
- On the main page (http://example.ms/GetSimple_2.01/) the relative URL should be: data/uploads/041.jpg.
- On any page (http://example.ms/GetSimple_2.01/pageslug) the relative URL should be data/uploads/041.jpg.
- On any page followed by a slash (http://example.ms/GetSimple_2.01/pageslug/) the relative URL should be ../data/uploads/041.jpg.
- On any sub page (http://example.ms/GetSimple_2.01/pageslug/subpage) the relative URL should be ../data/uploads/041.jpg.
- On any sub page followed by a slash (http://example.ms/GetSimple_2.01/pageslug/subpage/) the relative URL should be ../../data/uploads/041.jpg.
“Don’t forget the important ˚ (not °) on the a,†says the Unicode lover.
Help us test a key change for the core! ¶ Problems with GetSimple? Be sure to enable debug mode!
Help us test a key change for the core! ¶ Problems with GetSimple? Be sure to enable debug mode!