Stealth Forwarding & {$siteurl}
-
Comments:
- here.
I’ve got my own domain (http://schinckel.net), which just so happens to point towards this blog. It would be cool if I could replace the http://schinckel.net _with _http://schinckel.net _everywhere it appears. I have gotten ever so close to achieving this. I have made it so that {$siteurl}
is equal to _http://schinckel.net, using a hidden options page. This means that all of the links and so forth on my blog now look like: http://schinckel.net/2006/03/15/coffee-physics/ Then, in theory, if I make http://schinckel.net “Stealth Forwarding” instead of “Standard Forwarding”, then it will keep these addresses in the address bar, and people copy-pasting them would grab my nicer address. However, there is on issue. Stealth forwarding actually uses a frameset to work, and this interferes with the proper passing through of data. Thus, on http://www.schinckel.net/, which does use Stealth forwarding, when I click on a link that goes to another page, the original URL stays in the address bar. If I turn on Stealth for http://schinckel.net, this bug seems to go away - clicking on a link to another page puts the correct address into the page, but since the frameset exists, then two other problems appear: Cookies for logging into the site fail (as it’s actually a different site), and the StyleSheet file fails to load, as instead of it being http://schinckel.net/templates/wp-layout.css, which is a CSS file, it is a page, in HTML, with a frame with the CSS file inside of it that loads. Which fails to be interpreted by the browser, resulting in dodgy looking pages. I could overcome the second issue by hard-coding the CSS file path into my template, but the first one is a biggie. I can’t just login to http://schinckel.net/wp-admin/, as all of the links inside of the page that use {$siteurl}
now point to http://schinckel.net/wp-admin/yada-yada-yada.php, which the login session isn’t valid for. So, I can’t access anything inside the Dashboard. I’ve settled on a middle ground for now: I’ve set the {$siteurl}
to http://schinckel.net, but left forwarding mode as Standard. Now, anything in the page which writes a URL as src="/yada"
will give a schinckel.net address, but anything that uses {$siteurl}
will give a nice schinckel.net address. I might be able to post-process some stuff so it looks even nicer, but the address bar will always be http://schinckel.net/yada/. Unless I can outsmart the cookies. The outsmarting can be done one of two ways: firstly using JavaScript, and secondly using Smarty Tags. I think JavaScript will be better, as it will automatically get every location, whereas the Smarty Tag solution would requires some serious {capture} ... {$var|replace}
action. The bestmethod may be to tweak my DNS settings, so that the location of schinckel.net is the same as that of schinckel.net, however I don’t yet know enough about this to even try.