Darklyte

Nope, changed nothing. Awesome news however, I FINALLY solved the problem.

First the for files. Apparently since I have my subdomain named files the .htaccess in my root directory was rewriting any attempt to access anything in that directory to essentially point it no where. The line that was causing the error was:

RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

Since this .htaccess is in the root directory is cascades into the subdirectories and thus the subdomain. How did I fix this? It was as simple as adding this line to the .htaccess in /files/

RewriteEngine off

For the redirecting issue I was at a lost. I figured there must have been some hook that was redirecting my mediawiki’s index.php back to wordpress’ index.php. I tried renaming it to wiki.php and noted that it did NOT redirect then. So I backed up the file and started deleting lines until I found the one that I could remove to stop the redirect. After going through a few more files it came to localsetting.php, the main configuration file for mediawiki. In this file it was the inclusion of the firestats extension (plugin). I can easily disable this extension without losing anything. I believe the problem had to do with firestats actually having a directory called /php.

Success! Thanks for your help. You definitely helped me narrow it down.

Oh no, sorry. A friend of mine asked me if I could set up a mediawiki for her so that is a separate installation. The only wiki that isn’t working is the subdomain install at wiki.project-saros.com.

It wasn’t a complicated hack, it just made it so it spit out the proper .htaccess code for the subdirectory install. Here is what was added to functions.php:

add_filter( 'allow_subdirectory_install',
	create_function( '', 'return true;' )
	);

This is what multisite had me add to wp-config:

define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', false );
$base = '/';
define( 'DOMAIN_CURRENT_SITE', 'www.project-saros.com' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );

And this is the .htaccess code put in the root directory, where wordpress is installed:

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
# END WordPress

It is much different than the subdomain information. The hack I added merely allowed wordpress to install using subdirectories since my database is over 30 days old. Sorry for the confusion.

I’ve tried blanking the .htaccess to see if that fixes the issue, but it doesn’t. It seems to only redirect from that wiki as well. http://www.project-saros.com/korvazor/wiki/Main_Page still works.