WP upgrade 3.0.5 -> 3.1.1 broke site

  • Resolved jkhongusc

    (@jkhongusc)


    13 years, 7 months ago

    We have a working WP 3.0.5 configured with multi-site. We have about 15 different hosts; and all is working well!

    I created a replication of our production site on a test system. I used the automatic upgrade to upgrade to 3.1.1. The upgrade went smoothly. After the update, I noticed differences in the wp-admin interface. I lost the “Super Admin” menu on the left and no longer see the Network configuration. To me it looks like we lost multi-site capability (network is turned off). I can still access my other sites by directly going to their admin url https://<site>/wp-admin but now I cannot create or manage new ones.

    Any ideas? Here are some of the settings I use in wp-config.php

    define( ‘NOBLOGREDIRECT’, ‘https://<myhost>/error.html&#8217; );

    define( ‘WP_ALLOW_MULTISITE’, true);
    define( ‘MULTISITE’, true );
    define( ‘SUBDOMAIN_INSTALL’, true);
    $base = ‘/’;
    define( ‘DOMAIN_CURRENT_SITE’, ‘usc.edu’ );
    define( ‘PATH_CURRENT_SITE’, ‘/’ );
    define( ‘SITE_ID_CURRENT_SITE’, 1 );
    define( ‘BLOG_ID_CURRENT_SITE’, 1 );

Viewing 3 replies - 31 through 33 (of 33 total)

  • Why not use <VirtualHost *:80></VirtualHost> and <VirtualHost *:443></VirtualHost>? Only one IP Address needed.

    I’m not going to argue further about it. I’m simply saying I have a working configuration doing *exactly* what you say is impossible. I’ll leave it at that. We’re getting beyond the scope of WordPress at this point anyway.

    Thread Starter jkhongusc

    (@jkhongusc)

    I’m not going to argue further about it. I’m simply saying I have a working configuration doing *exactly* what you say is impossible. I’ll leave it at that. We’re getting beyond the scope of WordPress at this point anyway.

    I am not saying it is impossible. It can if every site is handled exactly the same. In fact this is exactly what I want to do with WP. Sorry I have been using a different blogging production and each blog site is mapped to a specific directory. That required a separate SSL VirtualHost) for each site – which in turn required another IP address.

    Using WP sub-domain I can wildcard the SSL Virtual host. If we do WP sub-directories, can we also wildard the SSL VIrtual host? I hope so because WP sub-dir is another project we want to work on.

    Thread Starter jkhongusc

    (@jkhongusc)

    Moderators – you can mark this thread as “resolved.” I need to re-configure our WP installation.

    BTW, my multiple VirtualHost assertions were geared toward our sites at USC. A lot of them are (static) served by Apache and in different directories, hence a need for a separate VirtualHost and IP address if using ssl. But with WP, since it is dynamic where WP controls the serving of content, only 1 wildcard VirtualHost is needed (for each port).

    Thanks again for the quick feedback!

Viewing 3 replies - 31 through 33 (of 33 total)
  • The topic ‘WP upgrade 3.0.5 -> 3.1.1 broke site’ is closed to new replies.