https://bugzilla.wikimedia.org/show_bug.cgi?id=32486
--- Comment #4 from Voyagerfan5761 / dgw <[email protected]> 2011-11-22 00:00:34 UTC --- (In reply to comment #3) > By any chance is your $wgArticlePath set to "/$1"? Yes, it is. The relevant config block: $wgScriptPath = ""; $wgScriptExtension = ".php"; $wgScript = "$wgScriptPath/index.php"; $wgArticlePath = "/$1"; I don't remember having this problem the last time I set up a personal wiki site, but then again that was with version 1.11 or so. (I was also using a stable release, instead of checking out the latest development version every so often.) Current .htaccess: RewriteEngine on RewriteCond %{REQUEST_FILENAME} !\.[a-z]{2,4}$ [OR] RewriteCond %{REQUEST_FILENAME} [:] RewriteCond %{REQUEST_FILENAME} !^(index|img_auth|api)\.php RewriteRule (.*) index.php?title=$1 [NC] Is there a different .htaccess configuration that will avoid this issue? (I'd rather that than keep rewriting img_auth.php) > We may want to add handling that will intelligently understand what the real > .php file being referenced in the URL is and make use of that instead of ONLY > checking for $wgScript. If not auto-detection then maybe we should add a $wg > variable that lists all known php script paths. Then we can add img_auth.php > and api.php to it, users who do things like i.php can add both to it, and > extensions that define new .php files can add theirs as well in case. That sounds like a good idea in theory, but wouldn't it have the potential for causing problems if someone wants a page in NS_MAIN that has the same name as a core file listed in that array? -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
