A problem with your RewriteRules is that you can't create a page called "api.php" on your wiki
You can't create a page called api.php anyway, since it'd have to be Api.php unless I'm mistaken. :) But seriously, given the way I use MediaWiki that's not a big problem for me, the nice urls are way higher priority given my use cases.
Simetrical wrote:
I recently added an Official Developer-Recommended Rewrite Rule System (TM) section to the page on mediawiki.org:
You should not rewrite articles to be in the document root.
Thanks, but bummer. Well, I guess I'll just hope it doesn't get broken by future releases, because MediaWiki currently makes a great CMS for a "regular looking website", and it would be a shame if everything had to be in a subdirectory for it to work in the future since that's a bit more limiting for the site design. I guess I will live on the edge for a while and hope for the best.
but the former causes a variety of problems, including problems with robots.txt, favicon.ico, and script paths.
I understand the problem with the robots.txt and favicon.ico (or any file in the root), but what do you mean by "script paths"?
Chris
Roan Kattouw wrote:
<div class="moz-text-flowed" style="font-family: -moz-fixed">Chris Hecker schreef: > Assuming this doesn't have big unfixable problems (and if it does we > should update the mediawiki doc pages on this subject), I would > definitely say it's worth the trouble because a) it wasn't much > trouble, and b) it's just so nice to have the squeaky clean URLs. > > Using Alias /wiki /w/index.php and putting all your stuff in /w is *much* easier. You just have to adjust $wgArticlePath and $wgScript in LocalSettings.php to make it work. A problem with your RewriteRules is that you can't create a page called "api.php" on your wiki (or anything ending in ".php", really).
Roan Kattouw (Catrope)
</div>