CREATES NEW NETWORK, BUT NOT SITE

  • Resolved beekoff

    (@beekoff)


    5 years, 11 months ago

    Hi – I’ve installed the WP Multisite Networks plugin, and set it up following the WPMU article:

    How to Create a Network of WordPress Multisite Networks

    Basically, I installed the plugin and changed wp-config.php to comment-out … define(‘DOMAIN_CURRENT_SITE’, ‘example.com’); … Everything has gone according to the article, until after I create a new Network, (let’s call it “Test Network”). It creates the network, but not the first site, as it displays it has “0” sites (thought it was supposed to create the first one?). So then going back to main Networks menu, if I click on the new Test Network Dashboard, I get the following message, instead of a new Dashboard:

    Our automated filters have determined that this blog signup looks like it could be by a spammer. Because of this, to complete you registration please describe in one or two sentences what you intend to use this blog for in the form below and we will review your request. Thank you for your cooperation!

    WHAT AM I DOING WRONG??

    I mean, it says that there are “0” sites on the new Test Network, which kinda gives credence to there not being a Dashboard, however, the link https://example.com/test-network has actually been created.

    Very confused.

    Network title: Test Network
    Domain: https://example.com
    Path: /test-network/
    Site name: Test Network

    define(‘WP_DEBUG’, false);
    /* Multisite */
    define( ‘WP_ALLOW_MULTISITE’, true );
    define(‘MULTISITE’, true);
    define(‘SUBDOMAIN_INSTALL’, false);
    /* define(‘DOMAIN_CURRENT_SITE’, ‘example.com’); */ <—–no, not real domain
    define(‘PATH_CURRENT_SITE’, ‘/’);
    define(‘SITE_ID_CURRENT_SITE’, 1);
    define(‘BLOG_ID_CURRENT_SITE’, 1);
    /* That’s all, stop editing! Happy blogging. */
    /** 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’);

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter beekoff

    (@beekoff)

    Oops…Sorry about the ALL CAPS title! My bad

    Thread Starter beekoff

    (@beekoff)

    The following was from support via WPMU, which resolved the issue:

    The above error seems to be part of the Anti Splog plugin. Please do note that Anti Splog plugin hasn’t been tested, nor is compatible with WP Multi networks plugin. That might be the reason for the anomalies.

    Could you please deactivate the Anti Splog plugin temporarily, and create a new Network, and see whether you still get the same issue, or not, with the new network?

    So…here is what I have discovered as well.

    In your network dashboard, you have a primary domain…it’s labeled.

    This is the only domain which can create new sites.

    So you create the new site in the primary domain…move it over to the network you want to use it in…rename it in that network, if necessary to maintain branding…and then map the domain.

    I am using a godaddy Business hosting server plan (Cpanel Linux) which comes with a dedicated IP address, but the IP does not resolve to the root folder.

    To map it, you have to add the domain in Cpanel and point it at the root directory…which should be /public_html

    Is it a lot of steps?
    Sure.

    Will it be “automated”…nope. And I honestly think it shouldn’t be at this level and at this point of where I am working because in order to automate it all, I would literally need to invest around $4500 to bump my hosting plan up to a dedicated and fully managed server…or…hire two or three devops.

    Anyhow, at the learning point I am at right now…this is how it works for me.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘CREATES NEW NETWORK, BUT NOT SITE’ is closed to new replies.