mrjarbenne

Has this been solved? I’ve double-checked my server and the time is correct there, but in the Jetpack Stats area people from the future are visiting my site.

4 hours into the future to be exact. I’m in Eastern standard time.

Is this still the case? I’m excited about 1.5, but Following is a must.

I was hoping that would work for me, but the site wouldn’t load once I made all these changes (just a blank screen).

I was thinking of attempting a bit of a hybrid of two methods mentioned here: the mu-plugin php script the confirms WPMU suggested by Curtiss, but I assume it being posted 8 months ago it’s probably not compatible with the 3.1 Network Admin menu. I’m wondering if I change the first admin_menu mentioned in In file /active-directory-integration/ad-integration.php:

In public function _construct(): to network_admin_menu if that would be enough to fix it.

I hate screwing around with this as the site is live and AD users are currently content to return to the main domain to login when faced with a subdomain login fail (although it is clunky and confusing).

Would the redirect in wp-login.php suggested by kristianjohansen:

if ($_SERVER['REQUEST_URI'] != "/wp-login.php") {
        wp_redirect('https://'.$_SERVER['HTTP_HOST'].'/wp-login.php');
}

need to be changed at all to work on a subdomain setup?

On further reflection, in this particular instance, I think I can probably block/hide the moderation link in the CSS on a case by case basis. Plugin management is a nice solution for the embedly issue I’d been running into though,in which the plugin needs to be activated site by site in order to work.

I think that’s the solution. The plugins menu is already hidden from users, so deactivation isn’t an issue. It’s the granular switching off I’m looking for, without having to individually manage the plugins on each site. I’ll look into the plugin management plugins; that looks like the best route. I do obviously prefer the network enable/mu-plugins route as it makes deactivating for updates easier. I’ll end up with a hybrid of the three solutions I imagine. Thanks for batting this issue about with me. Incredibly helpful.

The hidden part I assume is a given, out of virtue of the plugin being Network Enabled.

Ipstenu is correct, I want the plugin to be enabled 99% of the time, on the numerous elementary student blogs hosted on my network, given it’s a MODERATION plugin that is keeping tabs on the content “multi-site-wide”; but I don’t want it to appear on sites like this: : On sites like that I know the content is appropriate, and the “Flag if Inappropriate” links on the bottom of each post seem ill-placed.

New user looking for a quiz solution. Have you loaded this into the repo as an update, or should I DL the plugin and make the changes manually?

– if the BP activity stream shows all the blog posts from across the network, then why are you also using SWT?

I’m a sucker for a pretty tag cloud, and the sitewide blog feeds a twitter account so that users can subscribe to blogs without creating tweets about every update, group activity etc.

I’ll try the BP forums again. Thanks for the support.

Thanks much. So I’m not worried about the line referring to the BASE needing to be changed in wp-config to “/” or “/blogs”? “die” sounds so ominous.

Here it is. There is a line that looks problematic referring to BASE, and VHOST is defined as yes, which is referred to lower in the code as requiring some tweaks so that it redirects correctly.

Thanks for any help you can provide.

<?php
/** Enable W3 Total Cache **/
define('WP_CACHE', true); // Added by W3 Total Cache

/**
 * The base configurations of the WordPress.
 *
 **************************************************************************
 * Do not try to create this file manually. Read the README.txt and run the
 * web installer.
 **************************************************************************
 *
 * This file has the following configurations: MySQL settings, Table Prefix,
 * Secret Keys, WordPress Language, and ABSPATH.
 *
 * This file is used by the wp-config.php creation script during the
 * installation.
 *
 * @package WordPress
 */

define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '/');
define('COOKIEHASH', 'xxxxxxxxxxxxxxxxxxxxx');

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', '');

/** MySQL database username */
define('DB_USER', '');

/** MySQL database password */
define('DB_PASSWORD', '');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');
define('VHOST', 'yes');
$base = '/';
define('DOMAIN_CURRENT_SITE', 'litcircuits.com' );
define('PATH_CURRENT_SITE', '/' );
define('SITE_ID_CURRENT_SITE', 1);
define('BLOGID_CURRENT_SITE', '1' );

/**#@+
 * Authentication Unique Keys.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/ www.ads-software.com secret-key service}
 *
 * @since 2.6.0
 */
define('AUTH_KEY', '');
define('SECURE_AUTH_KEY', '');
define('LOGGED_IN_KEY', '');
define('NONCE_KEY', '');
define('AUTH_SALT', '');
define('LOGGED_IN_SALT', '');
define('SECURE_AUTH_SALT', '');
/**#@-*/

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each a unique
 * prefix. Only numbers, letters, and underscores please!
 */
$table_prefix  = 'wp_';

/**
 * WordPress Localized Language, defaults to English.
 *
 * Change this to localize WordPress.  A corresponding MO file for the chosen
 * language must be installed to wp-content/languages. For example, install
 * de.mo to wp-content/languages and set WPLANG to 'de' to enable German
 * language support.
 */
define ('WPLANG', '');

// double check $base
if( $base == 'BASE' )
	die( 'Problem in wp-config.php - $base is set to BASE when it should be the path like "/" or "/blogs/"! Please fix it!' );

// uncomment this to enable wp-content/sunrise.php support
//define( 'SUNRISE', 'on' );

// uncomment to move wp-content/blogs.dir to another relative path
// remember to change WP_CONTENT too.
// define( "UPLOADBLOGSDIR", "fileserver" );

// If VHOST is 'yes' uncomment and set this to a URL to redirect if a blog does not exist or is a 404 on the main blog. (Useful if signup is disabled)
// For example, the browser will redirect to https://examples.com/ for the following: define( 'NOBLOGREDIRECT', 'https://example.com/' );
// define( 'NOBLOGREDIRECT', '' );
// On a directory based install you can use the 404 handler.

// Location of mu-plugins
// define( 'WPMU_PLUGIN_DIR', '' );
// define( 'WPMU_PLUGIN_URL', '' );
// define( 'MUPLUGINDIR', 'wp-content/mu-plugins' );

// Uncomment to disable the site admin bar
//define( 'NOADMINBAR', 1 );

define( "WP_USE_MULTIPLE_DB", false );
define( 'NONCE_SALT', '' );

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 */
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** WordPress absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
?>

I didn’t realize such a magical place existed. Thanks for the tip.