• Resolved MicahRicah

    (@micahricah)


    Hi,
    I used your pluugin for many years but suddenly its not working after the update?
    I usually go to Export and to replace the database urls of the dev site to the destination ones but now your plugin does not read the url of the current (dev) site and when I manage to read the url from your help tab I try to place the destination urls and click Export it gives me an error:
    Migration Failed
    Internal Server Error

    This is on the hosting account I used to migrate many sites with your old plugin.
    Also the video on your plugin page does not reflect the new version of the plugin?

Viewing 3 replies - 1 through 3 (of 3 total)
  • I have the problem with the urls too …

    The fields “Find” and “Replace” are empty

    Plugin Contributor Kevin Hoffman

    (@kevinwhoffman)

    Hi @micahricah and @pixx,

    The URL and Path fields were removed from 2.6.0 but will be returning in 2.6.2, which is scheduled for release next week.

    You can read the full discussion about why the fields were removed in this support thread, but in short, we removed the fields because many import tools, such as Local and WP Migrate, handle the URL and Path updates for you when importing the database. However, we realize that this was a misstep and that there are other workflows that depend on these fields.

    So we will be bringing back the URL and Path fields for exports in 2.6.2.

    In the meantime, you can download an older version of WP Migrate Lite 2.5.0 from this page if you need those fields back today: https://wordpress.org/plugins/wp-migrate-db/advanced/

    Plugin Contributor Kevin Hoffman

    (@kevinwhoffman)

    For anyone following along, I wanted to let you know that the URL and Path fields are once again available in WP Migrate 2.6.2 which was released earlier today. The screenshot below shows that these values are pre-populated with the current site’s details when beginning a new export.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘What happened to this plugin? Its not working?’ is closed to new replies.