Support » Plugin: PayPal for WooCommerce » Cloudways incompatibility killed website

  • Resolved Kostas

    (@kostas-r)


    I installed the plugin on a wordpress installation in cloudways, php7, no varnish. It killed my website. Gave a white backend after activation and couldn’t access the admin area. Had to restore from server backup… Twice. Couldn’t make it work.

    Any help would be appreciated.

    Kind Regards,
    Kostas

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor angelleye

    (@angelleye)

    A blank white page in WordPress typically means there’s a PHP failure happening. For future reference, if you FTP in to your site files and rename the plugin folder it will effectively disable the plugin so your site will load again without the need to do a full restore. That goes for any plugin/theme that causes this in the future.

    You’ll need to check your PHP error log to see exactly what the failure is. Is that something you’re familiar with? Can you check it please and let us know if what failures you see in there?

    I cloned the app and recreated the issue. Here is the log.

    /***********************************************************/

    [Tue Sep 05 09:48:38.199563 2017] [proxy_fcgi:error] [pid 9568] [client 127.0.0.1:45573] AH01071: Got error ‘the log buffer is full (1024). The access log request has been truncated.\n’, referer: https://wordpress-test-324090.cloudwaysapps.com/wp-admin/
    [Tue Sep 05 09:50:14.595723 2017] [proxy_fcgi:error] [pid 9628] [client 127.0.0.1:45665] AH01071: Got error ‘the log buffer is full (1024). The access log request has been truncated.\n’, referer: https://wordpress-test-324090.cloudwaysapps.com/wp-admin/options-general.php?page=seed_csp4
    [Tue Sep 05 09:52:09.954815 2017] [proxy_fcgi:error] [pid 10027] [client 127.0.0.1:45723] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Call to undefined function WC() in /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-content/plugins/paypal-for-woocommerce/paypal-for-woocommerce.php:1080\nStack trace:\n#0 /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-includes/class-wp-hook.php(300): AngellEYE_Gateway_Paypal->angelleye_paypal_for_woocommerce_page_title(‘Home’)\n#1 /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-includes/plugin.php(203): WP_Hook->apply_filters(‘Home’, Array)\n#2 /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-includes/post-template.php(158): apply_filters(‘the_title’, ‘Home’, 30380)\n#3 /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-content/plugins/slash-admin/slashadmin.php(50): get_the_title(Object(WP_Post))\n#4 /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-content/plugins/slash-admin/options.php(450): slashadmin_get_pages()\n#5 /home/test.cloudwaysapps.com/cbqpwmgqbv/public_html/wp-content/plugins/slash-admin/options.php(30): S…\n’, referer: https://wordpress-test-324090.cloudwaysapps.com/wp-admin/plugins.php

    /**************************************************************/

    Please let me know

    Kind Regards,
    Kostas

    Plugin Contributor angelleye

    (@angelleye)

    Are you sure the site is running PHP 7? Can you verify with phpinfo()? Also, can you verify which version of our plugin you are running?

    Your plugin version is –> Version 1.4.6.2

    Wordfence verifies that PHP version is –> 7.0.22-1~dotdeb+8.1

    There must be a conflict with the slashadmin plugin. I deactivated it the way you said and I had access to the backend again. I pinged that plugin’s developer too.

    Plugin Contributor angelleye

    (@angelleye)

    Okay, so it looks like the bug was in their plugin, not ours, and he’s got it fixed for you, right?

    The dev provided an untested temporary fix. It seems to provide a solution for now.
    Thanks for your support.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Cloudways incompatibility killed website’ is closed to new replies.