From: Martyn D. <ma...@dr...> - 2002-11-22 14:46:20
|
Hi, I'm attempting to install phpwiki-1.33 into the root directory of my virtual web server (which is running Apache 1.3.27). Note that it is the root directory and not some kind of /wiki or /phpwiki derivative. The problem is that the themes are not being picked up. There are broken images and no background image is displayed. However, the Wiki appears to be fine in all other respects. Installing phpwiki-1.33 into a subdirectory from the web server's root, all themes and images work fine. Is there anything that can be done to ensure that the theme funtionality works within the server's root directory as well as whatever subdirectory that is chosen? I'd ideally like to use my Wiki as the frontend to my web site. Many thanks, Martyn |
From: Jeff D. <da...@da...> - 2002-11-22 16:16:51
|
> I'm attempting to install phpwiki-1.33 into the root directory of my > virtual web server (which is running Apache 1.3.27). Note that it is > the root directory and not some kind of /wiki or /phpwiki derivative. I think I remember hearing some reports of some people being at least partially successful doing that, but I'd recommend against it. Where PhpWiki is installed (assuming USE_PATHINFO is on), it takes over the entire URL-space. If you install PhpWiki under /wiki, every URL beginning with /wiki is a wiki page (or operation on one). If you install PhpWiki under /, then every URL on your host refers to a wiki page. There's no place left (without hackage) to put style sheets, icons, or anything else that's not a wiki page. (A request for /phpwiki.css is interpreted as a request for the wiki page titled 'phpwiki.css'.) Certainly PhpWiki was not designed with that usage in mind. That said, here's a couple ideas: Idea 1: Recognize certain extensions (.css, .gif, .jpg) as non-wiki page. Use mod_rewrite rules to differentiate between those special URLs, and everything else. Idea 2: Put all the non-wiki page things on a different (possible virtual) host. (Or a (virtual) server running off a different (non-standard) port.) Not having attempted either, I like the second idea better... In either case, you'll have to become familiar with the configure options in part 5 ("URL options") of index.php --- most of them will probably require manual configuration... Write back if you get stuck. If you get it to work, please write up a short howto... |
From: Martyn D. <ma...@dr...> - 2002-11-22 16:39:16
|
Jeff, Firstly many thanks for your reply. Based on what you've said below, I think the easiest thing that I can do would be to install PHPwiki under it's own subdirectory of /wiki and in the root directory have an immediate HTTP redirect to point to http://xxx/wiki. This way, everything remains nice and neat and doesn't involve any hacking about with the files, etc. Regards, Martyn -----Original Message----- From: Jeff Dairiki [mailto:da...@da...] Sent: 22 November 2002 16:17 To: Martyn Drake Cc: php...@li... Subject: Re: [Phpwiki-talk] Root directories vs. subdirectories > I'm attempting to install phpwiki-1.33 into the root directory of my > virtual web server (which is running Apache 1.3.27). Note that it is > the root directory and not some kind of /wiki or /phpwiki derivative. I think I remember hearing some reports of some people being at least partially successful doing that, but I'd recommend against it. Where PhpWiki is installed (assuming USE_PATHINFO is on), it takes over the entire URL-space. If you install PhpWiki under /wiki, every URL beginning with /wiki is a wiki page (or operation on one). If you install PhpWiki under /, then every URL on your host refers to a wiki page. There's no place left (without hackage) to put style sheets, icons, or anything else that's not a wiki page. (A request for /phpwiki.css is interpreted as a request for the wiki page titled 'phpwiki.css'.) Certainly PhpWiki was not designed with that usage in mind. That said, here's a couple ideas: Idea 1: Recognize certain extensions (.css, .gif, .jpg) as non-wiki page. Use mod_rewrite rules to differentiate between those special URLs, and everything else. Idea 2: Put all the non-wiki page things on a different (possible virtual) host. (Or a (virtual) server running off a different (non-standard) port.) Not having attempted either, I like the second idea better... In either case, you'll have to become familiar with the configure options in part 5 ("URL options") of index.php --- most of them will probably require manual configuration... Write back if you get stuck. If you get it to work, please write up a short howto... |
From: Jeff D. <da...@da...> - 2002-11-22 16:50:19
|
> I think the easiest thing that I can do would be to install PHPwiki > under it's own subdirectory of /wiki and in the root directory have an > immediate HTTP redirect to point to http://xxx/wiki. As long as you're only redirecting requests for / (or /index.*) to /wiki/FrontPage, that will work fine. If you're thinking of trying to redirect _everything_, then, of course, you're back to the same problem. (If you redirect everything except for requests for /*.{gif,css,jpg}, then that's Idea 1.) |
From: Philip J. H. <ph...@ho...> - 2002-11-22 20:13:23
|
I have my phpwiki in the root at http://www.hollenback.net, and everything works fine. I did have to futz with it a bit to make it pick up the themes correctly, but it was long enough ago that I don't remember what I did. Check the bug reports on the sourceforge site, I filed the info there. Now having said that, I don't think the situation is anywhere near as complicated as Jeff suggests. For one thing, there is no namespace issue because every wiki operation has to go through index.php. So to take the example of my site, my main css page is at http://www.hollenback.net/hollenback-style.css. A wiki page is at http://www.hollenback.net/index.php/HelpfulMuttHints (for example). So there's really no issue of the wiki getting in the way. index.php for all things wiki, start from the root (/) for everything else. Unless I'm missing something? I see the following in the url options part of my index.php: define('DATA_PATH', ''); define('PHPWIKI_DIR', '.'); This is phpwiki 1.3.3. P. On Sweetmorn, the 34th of The Aftermath, Jeff Dairiki spoke: > > I'm attempting to install phpwiki-1.33 into the root directory of my > > virtual web server (which is running Apache 1.3.27). Note that it is > > the root directory and not some kind of /wiki or /phpwiki derivative. > > I think I remember hearing some reports of some people being at least > partially successful doing that, but I'd recommend against it. > > Where PhpWiki is installed (assuming USE_PATHINFO is on), it takes > over the entire URL-space. If you install PhpWiki under /wiki, every > URL beginning with /wiki is a wiki page (or operation on one). > If you install PhpWiki under /, then every URL on your > host refers to a wiki page. There's no place left > (without hackage) to put style sheets, icons, or anything > else that's not a wiki page. (A request for /phpwiki.css > is interpreted as a request for the wiki page titled > 'phpwiki.css'.) > > Certainly PhpWiki was not designed with that usage in mind. > > That said, here's a couple ideas: > > Idea 1: > > Recognize certain extensions (.css, .gif, .jpg) as non-wiki page. > Use mod_rewrite rules to differentiate between those special > URLs, and everything else. > > Idea 2: > > Put all the non-wiki page things on a different (possible virtual) > host. (Or a (virtual) server running off a different (non-standard) > port.) > > > > Not having attempted either, I like the second idea better... > > In either case, you'll have to become familiar with the > configure options in part 5 ("URL options") of index.php > > > Write back if you get stuck. > If you get it to work, please write up a short howto... > > > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk -- Philip J. Hollenback ph...@po... http://www.hollenback.net |
From: Jeff D. <da...@da...> - 2002-11-22 20:53:09
|
> Now having said that, I don't think the situation is anywhere near as > complicated as Jeff suggests. For one thing, there is no namespace > issue because every wiki operation has to go through index.php. So to > take the example of my site, my main css page is at > http://www.hollenback.net/hollenback-style.css. A wiki page is at > http://www.hollenback.net/index.php/HelpfulMuttHints (for example). I believe Martyn wanted to eliminate the index.php part, e.g. http://www.hollenback.net/FrontPage You're quite right, that as long as you're happy with the 'index.php' in the URLs, there's no problem. |