Basically, the network admin links are not pointing to the WordPress URL.
Where ARE they pointing? I’m assuming hoopsu.com/wp-admin/network (which actually is not wrong), but I like to be sure 🙂
What did you add to your wp-config?
What’s in your htaccess?
Correct, the network admin links are pointing to hoopsu.com/wp-admin/network.
htaccess:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) hoopsu/wordpress/$1 [L]
RewriteRule ^(.*\.php)$ hoopsu/wordpress/$1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
Added to wp-config:
define('WP_ALLOW_MULTISITE', true);
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'hoopsu.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
Use the code tags (right next to blockquote on the tool bar) next time 🙂
Is the .htaccess the same as you see in wp-admin/network/setup.php ?
That it has hoopsu/wordpress/ is … weird.
Thanks for the heads-up on using the code tag … missed that.
Here is what I see in wp-admin/network/setup.php
<?php
/**
* Network Setup administration panel.
*
* @package WordPress
* @subpackage Multisite
* @since 3.1.0
*/
/** Load WordPress Administration Bootstrap */
require_once( dirname( __FILE__ ) . '/admin.php' );
if ( ! is_multisite() )
wp_die( __( 'Multisite support is not enabled.' ) );
require( ABSPATH . 'wp-admin/network.php' );
No no, I mean go to the site in your browser 🙂
If someone asks “What do you see at wp-admin?” it’s shorthand for ‘Go to youdomain.com/wp-admin’
Here is what I see at hoopsu.com/wp-admin/network/setup.php.
I get a 500 Internal Server Error:
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Apache Server at http://www.hoopsu.com Port 80
If I manually type hoopsu.com/WORDPRESS/wp-admin/network/setup.php I get the original network configuration with what I copied and pasted into wp-config and htaccess.
The actual links within the admin, however, don’t point to hoopsu.com/WORDPRESS/wp-admin… The ‘wordpress’ is left out.
If I manually type hoopsu.com/WORDPRESS/wp-admin/network/setup.php I get the original network configuration with what I copied and pasted into wp-config and htaccess.
Sorry I meant that URL. Anyway.
WHERE is WP actually installed? For some reason your htaccess has added in a folder hospu, which IMPLIES you installed WP in that folder (which is not the root of your domain…). Was this an add-on domain?
In THEORY this would be the right .htaccess:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
Not sure exactly what an add-on domain is. HoopsU.com was added to a hosting account which is why the /hoopsu folder was created. WP was installed within the /hoopsu folder.
HoopsU.com was added to a hosting account which is why the /hoopsu folder was created.
That would be an add-on domain 🙂 Okay, yeah two things to try! First the version of the htaccess in my previous post. If that doesn’t work, try this one:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^(wp-(content|admin|includes).*) wordpress/$1 [L]
RewriteRule ^(.*\.php)$ wordpress/$1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
Let me know if either work! We may have found a bug 🙂
Neither worked. I get a 404 error on pages such as http://hoopsu.com/wp-admin/network/ and on pages that end in .php such as http://hoopsu.com/wp-admin/network/sites.php I get the ‘500 internal server error’
As those links above show, the network admin links still don’t include /wordpress/ folder.
And just to be clear the htaccess should be in /hoopsu/wordpress/ correct?
DANG IT!
As those links above show, the network admin links still don’t include /wordpress/ folder.
This actually isn’t a problem. I know it’s weird, but it’s not.
And just to be clear the htaccess should be in /hoopsu/wordpress/ correct?
No, the .htaccess goes in the root of your domain, so /hoopsu/ in this case. If you have a SECOND .htaccess in the wordpress folder, you should remove it.
Well, that would have saved a lot of time if I had recognized that earlier!
I had an htaccess in both the /hoopsu/ and /wordpress/ folders!
I removed the htaccess from the wordpress and tested both codes above with the htaccess in the /hoopsu/ folder. They both work!
My only question now … does it matter which of the codes you gave me to use?
i am having similur prob my domain is londonscommunitychest.com when i downloaded my wordpres from my cpanel i got email to go to my domain name with /wp-admin on the end.However i get a 404 error page as well.Driving me crazy Help Plz
@carla : Please open your own thread because the problem with your site is not related.
My only question now … does it matter which of the codes you gave me to use?
If they both work, then it means your server is set up beautifully! The reason I have two versions is some servers don’t like some types of .htaccess clauses.
