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.

Clash between cron job and Gravity Forms

  1. antonsamper
    Member

    hi there,

    I have a cron job setup on my server which was working on WordPress RC3 up until i installed Gravity Forms. The cron job pulls in the wp-blog-header.php file from my blog, the rest of the script is custom built. When the cron job runs now i get the following error:

    Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /path/to/blog/wp-content/plugins/gravityforms/gravityforms.php on line 46

    Has anyone come across this before?

    Posted 9 years ago on Monday June 14, 2010 | Permalink
  2. Yes, it's a common question.

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

    http://forum.gravityhelp.com/search.php?q=t_string

    This is usually due to your PHP version. Gravity Forms requires PHP 5 or higher to function properly. Make sure you're running PHP 5 on your installation. Many hosts still default to PHP 4 for some reason and you have to enable PHP 5 in your hosting admin panel.

    Posted 9 years ago on Monday June 14, 2010 | Permalink
  3. antonsamper
    Member

    Thanks kevin.

    For some silly reason php4 is set to default and although i had changed this to php5 for my site, the cron job script was outside the site directory so it wasnt reading that i wanted to use php5.

    Just for anyone else that needs to do a cron job, i eventually just changed the prefix of the cron job from just 'php' to 'php5'. that did the trick. I'm not sure if that just with my host but hopefully someone will find that useful

    Posted 9 years ago on Tuesday June 15, 2010 | Permalink
  4. Thanks for the update. Glad you got it working.

    Posted 9 years ago on Tuesday June 15, 2010 | Permalink

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