Title: fatal error from secpay plugin
Last modified: September 14, 2020

---

# fatal error from secpay plugin

 *  Resolved [shokid](https://wordpress.org/support/users/shokid/)
 * (@shokid)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/)
 * Hi guys,
 * can’t use your plugin. See the error message down.
 * **Warning:** require(vendor/autoload.php): failed to open stream: No such file
   or directory in ***/wp-content/plugins/secpay-bitcoin-payment-gateway/gateway-
   secpay.php on line 13
    ** 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
 * What to do?
 * Oh, I see now, my whole shop crashed even after deactivation the plugin. I will
   load a backup and wait until this error is fixed.
    -  This topic was modified 5 years, 10 months ago by [shokid](https://wordpress.org/support/users/shokid/).
    -  This topic was modified 5 years, 10 months ago by [shokid](https://wordpress.org/support/users/shokid/).

Viewing 8 replies - 1 through 8 (of 8 total)

 *  Plugin Author [tobiaszander](https://wordpress.org/support/users/tobiaszander/)
 * (@tobiaszander)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13129507)
 * Hi,
 * thus actually sounds like composer was not executed sucessfully.
 * Could you please tell us how you installed the plugin and which WordPress-version
   you’re using?
 * Did you encounter any log messages during install?
 * Best,
    Tobias.
 *  Thread Starter [shokid](https://wordpress.org/support/users/shokid/)
 * (@shokid)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13129644)
 * 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.
 *  Plugin Author [tobiaszander](https://wordpress.org/support/users/tobiaszander/)
 * (@tobiaszander)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13131594)
 * Thanks we’re now able to reproduce the issue and will release a fixed version
   early next week.
 *  Plugin Author [tobiaszander](https://wordpress.org/support/users/tobiaszander/)
 * (@tobiaszander)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13145487)
 * [@shokid](https://wordpress.org/support/users/shokid/) Can you please upgrade
   to version 1.0.1 which was just released? This fixes the dependency issue.
 * Best,
    Tobias.
 *  Thread Starter [shokid](https://wordpress.org/support/users/shokid/)
 * (@shokid)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13148538)
 * 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.
 *  Plugin Author [tobiaszander](https://wordpress.org/support/users/tobiaszander/)
 * (@tobiaszander)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13148968)
 * [@shokid](https://wordpress.org/support/users/shokid/) I’m sorry for the experience
   you had. The plugin was automatically deactivated on your first try when using
   v1.0.0. v1.0.0 required to install the composer-dependencies manually, which 
   is a good practice in the PHP world, but we also understand that it’s more convenient
   for some users to get the dependencies packaged in the repository.
 * v1.0.1 contains now the dependencies also in the repository which should ease
   up the installation process.
 * The plugin is already running in production for our reference customers, safe,
   secure and tested. But we can definitely improve the first-time-installation-
   experience, point taken.
 *  Thread Starter [shokid](https://wordpress.org/support/users/shokid/)
 * (@shokid)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13150084)
 * [@tobiaszander](https://wordpress.org/support/users/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).
 *  Plugin Author [tobiaszander](https://wordpress.org/support/users/tobiaszander/)
 * (@tobiaszander)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13150106)
 * There’s no need anymore to install the dependencies manually. 1.0.1 is covering
   that for you.
 * You can simply activate the plugin by clicking “Activate” in the Installed Plugins
   menu. No need for an extra issue.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘fatal error from secpay plugin’ is closed to new replies.

 * ![](https://ps.w.org/secpay-bitcoin-payment-gateway/assets/icon-256x256.jpg?rev
   =2331298)
 * [SecPay](https://wordpress.org/plugins/secpay-bitcoin-payment-gateway/)
 * [Support Threads](https://wordpress.org/support/plugin/secpay-bitcoin-payment-gateway/)
 * [Active Topics](https://wordpress.org/support/plugin/secpay-bitcoin-payment-gateway/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/secpay-bitcoin-payment-gateway/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/secpay-bitcoin-payment-gateway/reviews/)

 * 8 replies
 * 2 participants
 * Last reply from: [tobiaszander](https://wordpress.org/support/users/tobiaszander/)
 * Last activity: [5 years, 10 months ago](https://wordpress.org/support/topic/fatal-error-from-secpay-plugin/#post-13150106)
 * Status: resolved