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.

Call to undefined method GFSqlSrvSync::lead_detail_long

  1. knguyen
    Member

    We have been getting many complaints from our visitors, where they all report the same error:
    Fatal error: Call to undefined method GFSqlSrvSync::lead_detail_long() in /[...removed...]/wp-content/plugins/gfsss/gfsss.php on line 1238

    It is not happening most of the time, and we haven't been able to replicate this error with any consistency. We have even tried filling out the form with the same exact fields as the visitor who got the error, and it will work. We have tried duplicating the form and tying the page to the new form and we still get the complaints.

    We are using Gravity Forms v1.6.11, Wordpress v3.5, mySQL v5.0.95, PHP v5.3.19.
    Here is the form:
    [...removed...]

    Any assistance you can provide is very much appreciated. Thank you.

    Posted 13 years ago on Friday December 21, 2012 | Permalink
  2. David Peralty

    Are you using any third party add-ons for Gravity Forms? Any other unique things in your set-up?

    Posted 13 years ago on Friday December 21, 2012 | Permalink
  3. knguyen
    Member

    Yes. Unfortunately, there is a custom plugin created by the previous developer on this site. It looks like the only purpose of the plugin was to store the GF tables on a MSSQL db that is separate from the normal mySQL db that houses the rest of the Wordpress. I'm not sure why.

    I was really hoping it wasn't an issue with this custom plugin, because I know you can't help with that. Is there anything about this error that looks familiar?

    Posted 13 years ago on Friday December 21, 2012 | Permalink
  4. David Peralty

    No, it definitely looks like a conflict with whatever gfsss is, and as such, if you could disable it, and test to confirm, that would be appreciated.

    Posted 13 years ago on Friday December 21, 2012 | Permalink
  5. knguyen
    Member

    I'll have to figure out why they felt the need to setup this custom plugin in the first place. Hopefully it is not necessary and we can disable it. If it is, I suppose I'll have to update it.

    Thank you for your time. Feel free to delete this topic.

    Posted 13 years ago on Friday December 21, 2012 | Permalink
  6. David Peralty

    Good luck, and all my best!

    Posted 13 years ago on Friday December 21, 2012 | Permalink

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