I know this may be my funny request, but ended up spending all weekend for it.
Is your feature request related to a problem? Please describe.
There was a conflict with other plug-in so that the request to /wp-json/wp-offload-media/v1/state/ got redirected to /wp-json/wp-offload- and ended up with 404 error.
Thus WP Offload Media couldn't properly validate the settings.
Since it may be "intentional" redirect by a unknown plugin, no debug log was recorded, but just 302 and 404.
Describe the solution you'd like
When you check "Check again",
it will conduct storage or delivery validation via traditional click-page-reload way, not using REST API.
Describe alternatives you've considered
I was asked to install WP Offload Media Lite, I've configured everything right including AWS settings.
It worked fine with the fresh and plain install of WordPress.
So I knew it was other plug-in causing the strange error, it is obviously other plug-in's fault.
But unfortunately, I didn't have enough time budget to investigate other plug-ins.
Additional context
I've set-up another WP instance on the same server, validate the settings, then, copied the wp-options transient data to the troubled existing site.
It started to work fine. I don't want to do another manual copy of wp-options data.
I know this may be my funny request, but ended up spending all weekend for it.
Is your feature request related to a problem? Please describe.
There was a conflict with other plug-in so that the request to
/wp-json/wp-offload-media/v1/state/got redirected to/wp-json/wp-offload-and ended up with 404 error.Thus WP Offload Media couldn't properly validate the settings. Since it may be "intentional" redirect by a unknown plugin, no debug log was recorded, but just 302 and 404.
Describe the solution you'd like
When you check "Check again",
it will conduct storage or delivery validation via traditional click-page-reload way, not using REST API.
Describe alternatives you've considered
I was asked to install WP Offload Media Lite, I've configured everything right including AWS settings. It worked fine with the fresh and plain install of WordPress. So I knew it was other plug-in causing the strange error, it is obviously other plug-in's fault.
But unfortunately, I didn't have enough time budget to investigate other plug-ins.
Additional context
I've set-up another WP instance on the same server, validate the settings, then, copied the wp-options transient data to the troubled existing site.
It started to work fine. I don't want to do another manual copy of wp-options data.