• oldcode

    (@coconutcoder)


    This plugin worked for me just a few weeks ago. I even made a custom form, using the defined form fields, and when a web visitor submitted it, their contact data was saved to my SuiteCRM. Since then, I think there was a WordPress update, and I also moved my WordPress site to the root directory for production. Every other plugin I migrated works, but not this one.

    Now I get this error when trying to activate the plugin:

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

    Parse error: syntax error, unexpected ‘{‘ in /home/***/public_html/wp-content/plugins/wp-widget-sugarcrm-lead-module/Common-functions.php on line 1

    I tried fiddling with the code, but it just led to other errors, so it’s basically not working in my WordPress.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Dipesh Patel

    (@dipesh_patel)

    No one reported this type of bug yet. Did you changed anything in my code?

    1 star due to configuration errors? – tut tut!

    Thread Starter oldcode

    (@coconutcoder)

    1 star because it’s not my job to rewrite your plugin.

    Thread Starter oldcode

    (@coconutcoder)

    I didn’t change anything, but I did stop using it because I couldn’t get it to work. Used to work, then it stopped working. The only change was upgrading WordPress.

    First of all the error you are showing is syntax error. Developer is not a fool to upload a plugin with a silly syntax error nor the 400 active users are fool using a plugin with syntax error.

    Just because you made some silly changes in the code and it didn’t work for you the plugin does not deserve a 1 Star.

    Thread Starter oldcode

    (@coconutcoder)

    You know what’s silly? You saying that I made some changes to the code, even after I already explained that I didn’t change the code. You’re reacting emotionally because I am reporting that your plugin is broken? So lame.

    Thread Starter oldcode

    (@coconutcoder)

    I upgraded WordPress. The plugin broke. Your move.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.