• Resolved francescopanco

    (@francescopanco)


    Hi All,

    I don’t understand why the plugin doesn’t replace properly…

    Consider this configuration on WP Migrate …

    http: -> https:

    localhost:10053 -> studiopanellagiuliana.it

    /Users/francesco/Local Sites/studiopanellagiulianauncode/app/public -> /home2/studiopanella/public_html

    I found in the SQL file AFTER the replacament

    it does not take in consideration URL encoding

    link="url:http%3A%2F%2Flocalhost%3A10053%2Fblog-list%2F|title:Blog%20Grid"

    it doesn’t replace at all sometimes

    89:"/Users/francesco/Local Sites/studiopanellagiulianauncode/app/public/wp-content/mu-plugins";i:6;s:85:"/Users/francesco/Local Sites/studiopanellagiulianauncode/app/public/wp-content/themes";}
    # URL: //localhost:10053

    Am I doing something wrong here or it’s just the plugin not working?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Kevin Hoffman

    (@kevinwhoffman)

    Hi, I can address the examples you mentioned below.

    link="url:http%3A%2F%2Flocalhost%3A10053%2Fblog-list%2F|title:Blog%20Grid"

    When performing a find and replace, WP Migrate matches the value exactly as it was entered, so if you need to match a URL and the encoded version of that URL, you should use two rows in the Find & Replace panel—one for the URL and one for the encoded version of the URL.

    We suspect this is a plugin storing the encoded URL since WordPress core does not tend to store the encoded version of URLs in the database, and it’s not usually necessary to search for an encoded URL when doing a find and replace.

    89:"/Users/francesco/Local Sites/studiopanellagiulianauncode/app/public/wp-content/mu-plugins";i:6;s:85:"/Users/francesco/Local Sites/studiopanellagiulianauncode/app/public/wp-content/themes";}

    It’s not immediately clear why this was skipped. If you can provide the table name and field where this data was skipped, we can look into it further. If you know whether a specific plugin generated this data, that would be helpful to know, too.

    # URL: //localhost:10053

    This is a MySQL comment which typically appears at the top of an exported database dump. It indicates the URL of the site where the export was generated. It is not part of the find and replace, so this is nothing out of the ordinary.

    Hope that helps answer your questions. If you can provide more info on the second example, we can look into that for you.

    Plugin Contributor Kevin Hoffman

    (@kevinwhoffman)

    It’s been 2 weeks since my last reply, so I’m going to mark this resolved, but please follow up if you can provide more context. Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Replacement not reliable’ is closed to new replies.