[Plugin: Networks for WordPress] Verify: Site 1 has an invalid meta value…

  • Rolf Allard van Hagen

    (@ravanh)


    12 years, 8 months ago

    Hi David,

    I noticed the new Verify Network feature and tested it on all my networks. And all the secondary networks created with Networks for WordPress passed the test… But not the main network!

    There, the test result page shows at the bottom:

    Checking hosted sites for correct Network-related meta values:

    Site 1 has an invalid meta value in home. This may prevent access to this site or disable some features.

    Site 1 has an invalid meta value in siteurl. This may prevent access to this site or disable some features.

    What does that mean? I checked home and siteurl in the wp_options table and they are similar to siteurl (for site_id 1) in the wp_sitemeta table and correspond to the domain set (for blog_id 1) in wp_blogs and (for id 1) in wp_site… I notice there are no siteurls set for all the created secondary networks in wp_sitemeta.

    Should I be worried? Can it be fixed?

    Thanks for any tips 🙂

    http://wordpress.org/extend/plugins/networks-for-wordpress/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author David Dean

    (@ddean)

    12 years, 8 months ago

    Is that site working as expected?

    If you checked out the values in the options table against those in the sites table and they correspond, it may be a sign that WordPress can’t find your options table for site 1. That would cause problems if you try to move that site. Out of curiosity, is it wp_1_options or wp_options?

    The siteurl meta key in the sitemeta table isn’t really used by WordPress. I don’t know if it’s a deprecated key or if it’s something new, but I appreciate the heads up and I’ll look into it.

    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    12 years, 8 months ago

    Hi David,

    This occurs on two separate installations. In both cases on the main network. In one case the DB table prefix is customized, the other just the default wp but both use _options, not _1_options.

    I should note: the main sites are working just fine. There is no panic 😉

    The domain for ID 1 in the wp_site (no s at the end, is that correct?) checks out against home and siteurl in wp_options (except for the http:// ofcourse)

    .Allard

    woccax

    (@woccax)

    12 years, 5 months ago

    Just FYI, I am seeing the same “issue” here.

    In fact, for EVERY single domain (5). However, there are not any obvious problems, the sites are working as expected.

    This is, even though I get bold red notifications saying that domain/home/siteurl are invalid for each TLD when verifying.

    So maybe this is related to some setup specific details?

    For example, I assume this is because of my setup, which is basically like this:

    vps12.myhost.com

    WP/MU set up in root: vps12.myhost.com/

    Now, whenever I add a new site “siteXY”, it is automatically added as:
    siteXY.vps12.myhost.com

    This is working and not showing ANY errors when verifying.

    Next, I use the domain mapping plugin to map TLDs (with properly set DNS) to the corresponding sub domain:

    http://www.myTLD.com -> siteXY.vps12.myhost.com

    (The IP is properly pointed to the IP of vps12 in the mapping plugin.)

    Now, regarding domain mapping, there are two mappings set up for each TLD:

    myTLD.com
    http://www.myTLD.com (primary)

    Like I said, this is working without any obvious problems – yet verification is “failing”.

    Finally, this is just a small suggestion: I’d suggest to show the website’s domains/names instead of just their IDs, this’d make things much more intuitive.

    Thanks & all the best

    – woccax

    Plugin Author David Dean

    (@ddean)

    12 years, 5 months ago

    woccax: Domain mapping sounds like the culprit here. It must change the meta keys that we’re checking. I’ll see what I can do to change the message to reflect this possibility.

    And showing more info on the affected sites is a good idea.

    iinet

    (@iinet)

    12 years, 4 months ago

    I have the same issue. I just installed a clean install of 3.2.1 and the “Networks for WordPress Plugin”. I get these two errors on the main site only.

    Site 1 has an invalid meta value in home. This may prevent access to this site or disable some features.

    Site 1 has an invalid meta value in siteurl. This may prevent access to this site or disable some features.

    Note, I setup the main site to use subdirectories for multi-sites. Does this make a difference? Can someone smarter advise on this issue? I can’t figure this one out.

    Thanks!

    Thread Starter Rolf Allard van Hagen

    (@ravanh)

    12 years, 4 months ago

    @all

    After opening the main sites /wp-admin/options.php and adding a trailing slash to the URLs in both siteurl and home field values, the verification error did not occur anymore…

    Plugin Author David Dean

    (@ddean)

    12 years, 4 months ago

    @ravanh – thanks for finding this! I’ll work on making the check for these values more flexible in the next release.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: Networks for WordPress] Verify: Site 1 has an invalid meta value…’ is closed to new replies.