search

deliciousbrains / wp-migrate-db

WordPress plugin that exports your database, does a find and replace on URLs and file paths, then allows you to save it to your computer.
https://wordpress.org/plugins/wp-migrate-db/
341 stars 515 forks source link

v2.3.0 - #146 - scope: ajax_verify_connection_to_remote_site #136

Closed mrkaluzny closed 2 years ago

mrkaluzny commented 2 years ago

After updating to 2.3.0 error (#146 - scope: ajax_verify_connection_to_remote_site) is thrown

Striffly commented 2 years ago

Same here

philwp commented 2 years ago

@mrkaluzny @Striffly when you ran the update did you do it via the admin UI?

We are trying to replicate the issue on our end. When the ajax_verify_connection_to_remote_site error is thrown did it seem like the connection process was taking longer than normal before the error message?

Thanks for the help.

mrkaluzny commented 2 years ago

I've updated using wp-cli, the message is returned basically instantly after trying to connect, works fine after downgrade, I had WP Media Migrate plugin installed as well

Striffly commented 2 years ago

The update was done with composer (stack Roots). Yes there is a small delay before the error is displayed (but not more than the other times I had mistakes).
Downgrade to 2.2.x fix the issue.

Striffly commented 2 years ago

Still have issue after upgrade to 2.3.2

Steps to reproduce :

philwp commented 2 years ago

Hey @Striffly, we are not able to reproduce this on our end. Can you please open a support ticket through the help tab of the plugin, so we can help you to resolve this issue?

Thanks.

eugenf commented 2 years ago

I've experienced the same issue and was able to find this error when running the CLI command.

If the debug mode is disabled the error disappears.

Screen Shot on 2022-04-13 at 12:00:07 d

mrkaluzny commented 2 years ago

@eugenf nice find I noticed when the additional plugins were working the errors are caused. I’ll try with fresh install today

AhmedTheGeek commented 2 years ago

@eugenf Thanks for posting the debugging output here. I can confirm that there's a bug in this piece of code and we're working on fixing it in the next release.

Striffly commented 2 years ago

Hello

Has this issue been resolved with version 2.3.3 ? I don't see a reference in the changelog

AhmedTheGeek commented 2 years ago

Hi @Striffly,

This issue wasn't fixed in version 2.3.3. However, we already worked a fix for it, and it's going to be a part of the upcoming 2.4.0 release.

Striffly commented 2 years ago

Hi @Striffly,

This issue wasn't fixed in version 2.3.3. However, we already worked a fix for it, and it's going to be a part of the upcoming 2.4.0 release.

Ok ! Thanks for the update

alexandre-tobia commented 2 years ago

@AhmedTheGeek Hi, Any news ? Almost five month without any fixes .. :(

Thanks

AhmedTheGeek commented 2 years ago

@alexandre-tobia We have a fix ready for this issue, and it's going to be included with the next major release 2.4.

alexandre-tobia commented 2 years ago

@AhmedTheGeek Thanks for your reply. When the 2.4 will be out ?

AhmedTheGeek commented 2 years ago

@alexandre-tobia I don't have an exact date. But it's not going to be a long wait 🙏.

mrkaluzny commented 2 years ago

@AhmedTheGeek Any update? The issue is persisting on many installs, making this plugin completely useless. Any quick workarounds?

alexandre-tobia commented 2 years ago

The only workaround i've found is to switch the theme (to use an official) on the remote before trying to pull/push. But i agree, it's been too long since the issue has been reported, hard to understand for a paid product.

philwp commented 2 years ago

@mrkaluzny

WP Migrate 2.3.4 was released today with a fix for this issue.

alexandre-tobia commented 2 years ago

Thanks !