I am unable to add new plugins or themes on a wordpress multisite community from the first web site as tremendous administrator. It reveals this error: ERR_TOO_MANY_REDIRECTS. Nevertheless, I’m able to entry all pages, login to every web site’s dashboard and even make modifications to present codes for put in plugins or themes. I’m not capable of set up any new ones and the community is caught in a loop.
Nevertheless, the issue will be prevented if I flip off the multisite choice utilizing the next code in wp-config.php:
outline('MULTISITE', false);
outline('SUBDOMAIN_INSTALL', false);
Is there any everlasting repair to this, the place I don’t have to disable my multisite community so as to add new plugins or themes?
Here’s a copy of my wp-config.php (authentication/secrets and techniques have been eliminated for safety functions):
<?php
/**
* The bottom configuration for WordPress
*
* The wp-config.php creation script makes use of this file in the course of the
* set up. You do not have to make use of the site, you may
* copy this file to "wp-config.php" and fill within the values.
*
* This file comprises the next configurations:
*
* * MySQL settings
* * Secret keys
* * Database desk prefix
* * ABSPATH
*
* @hyperlink https://codex.wordpress.org/Editing_wp-config.php
*
* @package deal WordPress
*/
// ** MySQL settings - You may get this data out of your net host ** //
/** The identify of the database for WordPress */
outline( 'DB_NAME', '' );
/** MySQL database username */
outline( 'DB_USER', '' );
/** MySQL database password */
outline( 'DB_PASSWORD', '' );
/** MySQL hostname */
outline( 'DB_HOST', '' );
/** Database Charset to make use of in creating database tables. */
outline( 'DB_CHARSET', 'utf8' );
/** The Database Collate sort. Do not change this if unsure. */
outline( 'DB_COLLATE', '' );
/**#@+
* Authentication Distinctive Keys and Salts.
*
* Change these to completely different distinctive phrases!
* You may generate these utilizing the {@hyperlink https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You may change these at any time limit to invalidate all present cookies. This may drive all customers to must log in once more.
*
* @since 2.6.0
*/
outline( 'AUTH_KEY', '' );
outline( 'SECURE_AUTH_KEY', '' );
outline( 'LOGGED_IN_KEY', '' );
outline( 'NONCE_KEY', '' );
outline( 'AUTH_SALT', '' );
outline( 'SECURE_AUTH_SALT', '' );
outline( 'LOGGED_IN_SALT', '' );
outline( 'NONCE_SALT', '' );
/**#@-*/
/**
* WordPress Database Desk prefix.
*
* You may have a number of installations in a single database in case you give every
* a novel prefix. Solely numbers, letters, and underscores please!
*/
$table_prefix = '';
/**
* For builders: WordPress debugging mode.
*
* Change this to true to allow the show of notices throughout development.
* It's strongly really helpful that plugin and theme builders use WP_DEBUG
* of their development environments.
*
* For data on different constants that can be utilized for debugging,
* go to the Codex.
*
* @hyperlink https://codex.wordpress.org/Debugging_in_WordPress
*/
outline( 'WP_DEBUG', false );
//outline( 'WP_CACHE', true );
require_once( dirname( __FILE__ ) . '/gd-config.php' );
outline( 'FS_METHOD', 'direct' );
outline( 'FS_CHMOD_DIR', (0705 & ~ umask()) );
outline( 'FS_CHMOD_FILE', (0604 & ~ umask()) );
/* Multisite */
outline ('WP_ALLOW_MULTISITE', true);
outline('MULTISITE', true);
outline('SUBDOMAIN_INSTALL', true);
outline('DOMAIN_CURRENT_SITE', 'instance.com');
outline('PATH_CURRENT_SITE', '/');
outline('SITE_ID_CURRENT_SITE', 1);
outline('BLOG_ID_CURRENT_SITE', 1);
outline( 'COOKIE_DOMAIN', '' );
outline( 'ADMIN_COOKIE_PATH', '/' );
outline( 'COOKIEPATH', '/' );
outline( 'SITECOOKIEPATH', '/' );
/* That is all, cease modifying! Comfortable publishing. */
/** Absolute path to the WordPress listing. */
if ( ! outlined( 'ABSPATH' ) ) {
outline( 'ABSPATH', dirname( __FILE__ ) . '/' );
}
/** Units up WordPress vars and included information. */
require_once( ABSPATH . 'wp-settings.php' );
Here’s a copy of my .htaccess:
# BEGIN WordPress
# The directives (strains) between `BEGIN WordPress` and `END WordPress` are
# dynamically generated, and will solely be modified by way of WordPress filters.
# Any modifications to the directives between these markers can be overwritten.
<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 material|admin|contains).*) $1 [L]
RewriteRule ^(.*.php)$ $1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress
I’ve tried the next:
- Clearing the looking historical past, cookie, cache – didn’t work
- Disabling all energetic plug-ins from the first web site – didn’t work
- Disabling the present theme – didn’t work
- Renaming the .htaccess file to one thing else – didn’t work
I attempted operating the url by means of the redirect-checker.org and that is the message they supplied, the primary url is the url that opens after I click on on “Add new plugin” the second url is the url that wordpress is redirecting and will get caught within the loop.
http://instance.com/wp-admin/plugin-install.php
302 Discovered
http://instance.com/wp-login.php?redirect_to=httppercent3Apercent2Fpercent2Fexample.compercent2Fwp-adminpercent2Fplugin-install.php&reauth=1
200 OK
I’d recognize any your form assist and look ahead to your response.
Cheers