PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Can't Activate GF. Get Fatal Error.

  1. pkazmercyk
    Member

    Uploaded GF 1.45 to plug-ins directory. Upon trying to activate it, get the following:

    "Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home/username/public_html/wp-content/plugins/gravityforms/gravityforms.php on line 59"

    Deactivated, deleted and repeated process, but with identical results. Using StudioPress Genesis, with Platinum child theme. Have been able to successfully install GF with other test WP installations prior to this.

    Posted 11 years ago on Saturday February 19, 2011 | Permalink
  2. This is most likely a PHP version error. Here is some more information from the Gravity Forms' FAQ:

    http://www.gravityhelp.com/frequently-asked-questions/

    Why do I get an 'unexpected T_STRING' PHP error when installing Gravity Forms?

    This error typically happens because of a PHP version conflict.

    Gravity Forms requires PHP5+ and judging from this error you are probably trying to activate the plugin on a site running PHP4. Check with your web host and make sure you have PHP5 enabled.

    Posted 11 years ago on Saturday February 19, 2011 | Permalink
  3. pkazmercyk
    Member

    Thanks David. My server was already running "PHP 5.2.9", but I had the option of upgrading it to PHP 5.3.0 or PHP 6.0.0-dev. I opted for "PHP 5.3.0", logged out and back into WP admin and was able to activate GF.
    Best regards,
    Paul

    Posted 11 years ago on Saturday February 19, 2011 | Permalink
  4. Thanks for the update Paul. Glad you were able to get this resolved.

    Posted 11 years ago on Saturday February 19, 2011 | Permalink

This topic has been resolved and has been closed to new replies.