Another possibility is to use a .htaccess file in the dir, with an entry or two for mod_rewrite, to translate to--> and from--> the wordpress subdirectory.
Jonathan Leighton wrote:
Yeah, I know it's possible using either <?php echo get_settings("siteurl"); ?> or absolute paths, but we don't want the *whole* site to be dependent on WordPress, and absolute paths cause problems for people testing locally, that's the problem.
Anyway, what I will do is set the site up just using querystrings for now. Then, if and when people like WordPress, we can review using either absolute paths or WordPress-depending the whole site. It isn't a life-or-death matter, so I probably shouldn't have brought it up really -- I was just bouncing ideas ;-).
Bob Jamison wrote:
From the docs, it looks like it rather takes care of itself. I had no problem installing it as http://server/blog/etc....
http://codex.wordpress.org/Installing_WordPress#In_a_Subdirectory
Jonathan Leighton wrote:
mental@...3... wrote:
Isn't it possible to substitute the relevent relative path as part of the template?
There is a settings value in WordPress that is called like this:
<?php echo get_settings("siteurl"); ?>. That returns the URI of the
site's base directory (you can also get the template's URI if you're using that). So I *could* use that in conjunction with the current relative paths to form an absolute URI for everything. But that would mean making *every* link on included pages (the header, footer, sidebar etc.) into an absolute URI (not to be confused with an absolute path -- absolute URIs start with the protocol like "http://"), and making *every* page depend on WordPress. Given that Bryce is already sceptical about using WordPress I don't think it would be the best thing to do (although I'd be happy to if people want me to).
That said, we could make a settings constant for the Inkscape website containing the base URI. However, it would still cause problems for people testing locally as they'd need to change it to suit themselves.