I’ve put in a multisite community in WordPress on my check server and it was working superb however after I did the identical on my manufacturing server it isn’t working correctly. When I attempt to login in wp-admin it opens completely superb however when I attempt to open dashboard of subsite, its dashboard masses with out css and not one of the hyperlinks opens (each hyperlink displaying file not discovered) whereas the default dashboard working completely superb. This setup is working superb on my check server.
Beneath is my htaccess:
RewriteEngine On
RewriteBase /pages/
RewriteRule ^index.php$ - [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 material|admin|contains).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]
# for recordsdata that finish with ".py"
<FilesMatch .css$>
SetEnv no-gzip 1
</FilesMatch>
right here is my wp-config:
/**
* The bottom configurations of the WordPress.
*
* This file has the next configurations: MySQL settings, Desk Prefix,
* Secret Keys, WordPress Language, and ABSPATH. You could find extra data
* by visiting {@hyperlink http://codex.wordpress.org/Editing_wp-config.php Enhancing
* wp-config.php} Codex web page. You will get the MySQL settings out of your internet host.
*
* This file is utilized by the wp-config.php creation script in the course of the
* set up. You do not have to make use of the web page, you may simply copy this file
* to "wp-config.php" and fill within the values.
*
* @bundle WordPress
*/
// ** MySQL settings - You will get this information out of your internet host ** //
/** The title of the database for WordPress */
outline('DB_NAME', 'xxxxx');
/** MySQL database username */
outline('DB_USER', 'xxxxx');
/** MySQL database password */
outline('DB_PASSWORD', 'xxxxx');
/** MySQL hostname */
outline('DB_HOST', 'localhost');
/** Database Charset to make use of in creating database tables. */
outline('DB_CHARSET', 'utf8');
/** The Database Collate kind. Do not change this if unsure. */
outline('DB_COLLATE', '');
/**#@+
* Authentication Distinctive Keys and Salts.
*
* Change these to completely different distinctive phrases!
* You'll be able to generate these utilizing the {@hyperlink https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You'll be able to change these at any time limit to invalidate all current cookies. This can power all customers to should log in once more.
*
* @since 2.6.0
*/
outline('AUTH_KEY', 'xxxxx');
outline('SECURE_AUTH_KEY', 'xxxxx');
outline('LOGGED_IN_KEY', 'xxxxx');
outline('NONCE_KEY', 'xxxxx');
outline('AUTH_SALT', 'xxxxx');
outline('SECURE_AUTH_SALT', 'xxxxx');
outline('LOGGED_IN_SALT', 'xxxxx');
outline('NONCE_SALT', 'xxxxx');
/**#@-*/
/**
* WordPress Database Desk prefix.
*
* You'll be able to have a number of installations in a single database when you give every a singular
* prefix. Solely numbers, letters, and underscores please!
*/
$table_prefix = 'wp_';
/**
* For builders: WordPress debugging mode.
*
* Change this to true to allow the show of notices throughout development.
* It's strongly really useful that plugin and theme builders use WP_DEBUG
* of their development environments.
*/
outline('WP_DEBUG', false);
/* That is all, cease enhancing! Comfortable running a blog. */
/* Multisite */
outline('WP_ALLOW_MULTISITE', true);
outline('MULTISITE', true);
outline('SUBDOMAIN_INSTALL', false);
outline('DOMAIN_CURRENT_SITE', 'www.instance.com');
outline('PATH_CURRENT_SITE', '/pages/');
outline('SITE_ID_CURRENT_SITE', 1);
outline('BLOG_ID_CURRENT_SITE', 1);
/** Absolute path to the WordPress listing. */
if ( !outlined('ABSPATH') )
outline('ABSPATH', dirname(__FILE__) . '/');
/** Units up WordPress vars and included recordsdata
Please assist..!!