shokid

@tobiaszander ,

how it could be safe or secure or tested, if the activation of the plugin fails.

How you are expecting to install composer-dependencies manually? How this should work? And how it should be done through the backend of WP?

Even if you want me to install this dependencies manually (what is not useful), please write such stuff in the installation manual.

It is one thing, if someone make a mistake and forget some dependencies. But please do not try to fool others with such a lame excuse.

Btw., will you fix the new issue or should I open a new topic for this (as you already marked it as solved).

Now I got

Plugin was deactived during an error

But when I see your changes, it is a bit horrorfiying:

1	1	{
2	 	    "require": {
 	2	    "type": "wordpress-dropin",
 	3	    "require": {
 	4	        "composer/installers": "~1.0",
3	5	        "guzzlehttp/guzzle": "~6.0",
4	6	        "guzzlehttp/streams": "^3.0"

Oh, looks like you upload this plugin totally untested!
Sorry, but this behavior has nothing to do with safe payment or security.

Hi Tobias,

thanks for the reply.

I installed the secpay.io plugin through the backend of wordpress.

During installation I didn’t see any log messages, but logging was off.

define( 'WP_DEBUG', false );

After activating your plugin, the error message appeared as above.

Fatal error: require(): Failed opening required ‘vendor/autoload.php’ (include_path=’.:/package/host/localhost/php-7.2.31/lib/php’) in ***/wp-content/plugins/secpay-bitcoin-payment-gateway/gateway-secpay.php on line 13

Unfortunately I can’t repeat the installation of this plugin with logging on, as my shop fatally crashed after it.

Luckily I had a current backup to prevent further losses.