wpseahorse

Hi and thank you very much for your review. We do understand that users find it difficult to decipher between source & destination sites so we are working on a release (3.2.* – mid-April 2022) that will alleviate this issue. We have been taking our lead on this issue from user feedback so any input you may have (via our support portal: https://www.seahorse-data.com/wp-on-aws-support-portal/) will be considered and would be much appreciated.

Regards

The Seahorse Team

Hi

This is a limitation of the shared hosting platform as opposed to anything within WordPress. The software reads what is output from the server, so WordPress (and its associated plugins/themes) is not aware whether this is a local/global setting (it’s the only one available) so without control of this parameter our software will not run. Hope this makes sense?

We do offer custom migration services for edge cases however and would be happy to have a look at this one for you? Having this little control of the server is unusual and my concern would be there are other limitations that may restrict a seamless automated process e.g. can the site run on latest versions of PHP etc.

This case needs some investigation and if this is something you would like to pursue please raise a ticket here: https://www.seahorse-data.com/wp-on-aws-support-portal/ quoting the forum thread title and we will pick it up there.

Thanks – Seahorse Team

Hi,

We have had reports from some users where this directive is showing on phpinfo() but is being overwritten by another parsed php.ini file(s)

On both occasions this was because of multiple versions of PHP on the same server. Can you review any additional .ini files parsed: e.g. /path/to/php/php7*/etc/php.ini and make the change there also.

This should resolve the issue but if you need further support, please feel free to raise a ticket with our support team who can offer more hands on assistance: https://www.seahorse-data.com/wp-on-aws-support-portal/

As per ticket discussion support is being handled on our internal system

Hi,

The fopen directive must be enabled to run this plugin and is associated with the current running version of PHP. When you output phpinfo(), can you see the directive ‘allow_url_fopen’ set to ‘on’?

If so, there is a misconfiguration in the PHP versions available on the server (suspect this is due to multiple versions)

Our support team has just picked up a ticket you have raised. We can discuss further options there via email

Hi @futureyoon
Sorry for late reply as we are not receiving notification about support tickets, our plugin is active and working ,we have updated it to latest version yesterday,
Let us know if there is any further issue you faced while using it,
Thanks
Seahorse

Thanks