• The general topic I need help with involves the values stored in a multisite’s “options” table after it’s created.

    Using MySQL command line I did this to show a site that is working correctly:

    mysql> select * from blahlbha_123_options where option_value like “http%”;
    +———–+————-+——————————–+———-+
    | option_id | option_name | option_value | autoload |
    +———–+————-+——————————–+———-+
    | 1 | siteurl | https://sitesite.community.uaf.edu | yes |
    | 2 | home | https://sitesite.community.uaf.edu | yes |
    | 34 | ping_sites | http://rpc.pingomatic.com/ | yes |
    +———–+————-+——————————–+———-+
    3 rows in set (0.01 sec)

    We want our new multisites to have serve up content using https.

    The problem is that new sites have their option_values set as ‘http’ when we create a new site. We can fix this with the MySQL command line client easily enough, its remembering to do it.

    It used to be that The root site would dictate whether subsequent sites served up http or https. That stopped being the case perhaps in version 4.0.

    So, is there a fix to this?
    Alternatively, is there an existing bug to this? I’ve searched the bug tracker (https://core.trac.wordpress.org/search?q=https+new+site) but I’m unsure of which terms to use in my query.

    I would love to find a fix, or write a helpful bug report.

  • The topic ‘WordPress Multisite http/https does not carry over to option_name siteurl’ is closed to new replies.