• Resolved Gularis

    (@gularis)


    Hi I have just downloaded this plugin and after successful installation I want to activate it, but I am getting this error:

    Plugin could not be activated because it triggered a fatal error.

    Parse error: syntax error, unexpected end of file in C:\xxampp\htdocs\wordpress\wp-content\plugins\woocommerce-login-and-registration\woocommerce_login_signup_plugin.php on line 1284

    Have you been doing some recent changes or could it interfere with some other plugin?
    It looks like missing some friggin semicolon or something ??

    Thank you.

    https://www.ads-software.com/plugins/woocommerce-login-and-registration/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Phoeniixx

    (@phoeniixx)

    Hello,

    Have you tested the plugin online ? Everything is working fine here. You have tested the plugin in local server. In our plugin, we can’t even find line 1284. This file woocommerce_login_signup_plugin.php has only 980 line of code.

    Thread Starter Gularis

    (@gularis)

    Ok now you got me really confused. I just downloaded the file again and on the line 912 there is this commented heading
    <!----<h2>Get access to Pro Features</h2>----->
    since that the code after seems commented and the file continues until the line 1283 and it ends in
    `
    ob_clean();

    ?>
    I am running on localhost and it still gives me an error. I got the version 1.3.3. I don’t understand what going on here. Look at the screenshots please. This plugin is crusial for me.
    Thank you.
    https://imgur.com/OfbguDW

    View post on imgur.com

    Plugin Author Phoeniixx

    (@phoeniixx)

    We have found the error. Thank you for letting us know. We will update you once it’s been fixed. In return, we will give you the 30% discount coupon which you can use for all our products.

    Plugin Author Phoeniixx

    (@phoeniixx)

    We have fixed the fatal error. Now you can download the latest version 1.3.4

    Plugin Author Phoeniixx

    (@phoeniixx)

    It’s been fixed.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal error’ is closed to new replies.