Tables of concern for mixed content errors (http->https)

  • Resolved bjf2000

    (@bjf2000)


    9 years, 4 months ago

    We’re exploring two different search&replace plugins to solve the mixed content (URL) problem now that we’re using SSL.

    I did find this:
    https://codex.wordpress.org/Database_Description

    And it suggests wp_posts is the main table, but does that mean we can ignore all the other ones as far as this particular browser warning is concerned? Searching tends to be very slow and can sometimes swamp the server, so the fewer tables to worry about the better. wp_options in particular is quite large.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator James Huff

    (@macmanx)

    9 years, 4 months ago

    Other tables may contain content that is embedded as well, like widgets and comments.

    Try this plugin: https://wordpress.org/plugins/velvet-blues-update-urls/

    Thread Starter bjf2000

    (@bjf2000)

    9 years, 4 months ago

    Great, so we really have to be concerned with all of them, though wp_options isn’t public-facing, right, so really shouldn’t be a factor?

    That plugin worries me because it doesn’t have a preview feature for changes, like Search & Replace (which has the best preview that I’ve found) and Better Search Replace (which people say does a better job in the actual replacing, while also letting you ignore GUID).

    Moderator James Huff

    (@macmanx)

    9 years, 4 months ago

    All of them, just to be safe.

    Even though the two plugins you mentioned have a preview function, I still recommend backing up first: https://codex.wordpress.org/WordPress_Backups

    Thread Starter bjf2000

    (@bjf2000)

    9 years, 4 months ago

    Yes, absolutely. phpMyAdmin works well for us, as opposed to the backup in Search & Replace, which seems to stall out and effectively hang up the site. There’s a big difference in efficiency in backup methods, it seems.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Tables of concern for mixed content errors (http->https)’ is closed to new replies.