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.

Errors thrown after activation

  1. travisward
    Member

    Just installed Gravity forms on a Wordpress Mu 2.8.6 site and now the admin area won't load for that site.

    This error is being generated:

    PHP Fatal error: Call to undefined function set_site_transient() in /usr/share/wordpress-mu/wp-content/plugins/gravityforms/common.php on line 528

    Running:
    PHP Version 5.1.6
    MySQL Version 5.0.77
    WordPress Version 2.8.6
    Gravity Forms Version 1.3.12.2

    If I comment out line 528 in common.php, things seem to be running smoothly (so far). Is this normal?

    Thanks,
    Travis

    Posted 13 years ago on Tuesday June 15, 2010 | Permalink
  2. No, it's not normal. I think it's a bug related specifically to the 2.8x version of WordPress. This does not occur on WordPress 2.9+ or 3.0. We will look into it.

    Running older versions of WordPress is a bit like running through a field of land mines. It's asking for trouble. Just curious why you haven't upgraded yet.

    WordPress 3.0 (final) will be released any day now, possibly later tonight or tomorrow. We always highly recommend users run the latest version of WordPress for security reasons.

    In the future we aren't guaranteeing backwards support with older versions of WordPress, again for security reasons. So while we technically support 2.8 now and will be looking into this bug, future versions may not be supported by 2.8 and we may bump up the minimum requirements to WordPress 2.9 and so on as new versions of WordPress are released.

    Is there any reason why you haven't upgraded to WordPress 2.9.2?

    Posted 13 years ago on Tuesday June 15, 2010 | Permalink
  3. travisward
    Member

    We're running RHEL on our servers and our admins are only comfortable with packages blessed by the EPEL community. Long story short, they're always a few versions behind :( Wordpress less so than Mu historically.

    So, I've been anxiously awaiting the merger for months now with the hope that the EPEL folks will bless a version of 3.0 sooner than later.

    Thanks for your help!

    Posted 13 years ago on Tuesday June 15, 2010 | Permalink
  4. travisward
    Member

    Looks like the only thing that would be affected would be plugin upgrades. Everything else seems to be working. How are set_transient and set_site_transient different? How bad is the removal of set_site_transient?

    'public static function check_update(){
    //only check updates on the admin side
    if(!IS_ADMIN)
    return;

    //Setting transient data (WP 2.8)
    if (!self::$_has_set_transient){
    $option = get_transient("update_plugins");
    $option = self::get_update_plugins_option($option);

    self::$_has_set_transient = true;
    set_transient("update_plugins", $option);
    //set_site_transient("update_plugins", $option);
    }
    }
    '

    If it's not so bad, this should work until we get blessed with an EPEL upgrade.

    -t

    Posted 13 years ago on Thursday June 17, 2010 | Permalink
  5. I just uploaded gravity forms and when I tried to activate it I got this FATAL ERROR.

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

    I could use some help with this.
    Thanks

    Posted 13 years ago on Thursday June 17, 2010 | Permalink
  6. @JanPorteous This is a PHP version error message as I mentioned in my response to your Contact Us form submission. Gravity Forms requires PHP 5 and your site is running PHP 4. You need to activate PHP 5, check with your web host.

    This is covered in our FAQ, it's the 2nd item under installation:

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

    Posted 13 years ago on Thursday June 17, 2010 | Permalink
  7. travisward
    Member

    Is my assertion that this will only affect upgrading correct?

    Thanks,

    T

    Posted 13 years ago on Friday June 18, 2010 | Permalink
  8. @travisward Yes, it appears to be a bug in WordPress 2.8x when we added the fixes for 3.0 that is causing this issue. It only happens in 2.8x. It would impact automatic upgrades, so you will have to manually install updates.

    Posted 13 years ago on Friday June 18, 2010 | Permalink