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.

Email notifications blank and user notifications stopped

  1. Since I upgraded to the most current revision, all the forms I host on my company's website (http://www.globalcache.com) are not functioning properly. The admin notifications used to contain all the form data and now are blank. The notification that used to be mailed to users that filled out the form are no longer being sent. The only think that has changed on my site is the version of Gravity forms.

    Posted 13 years ago on Thursday March 31, 2011 | Permalink
  2. In order to look into this we would need a WordPress admin login for your site to take a look. It's possible WordPress didn't process the automatic update properly.

    It's also possible if notifications aren't being sent anymore that something changed on your web server related to your web host that you weren't aware of. Server configuration, etc.

    If you can send us an admin login via our Contact Us form and reference this forum post in your message we can take a look.

    Posted 13 years ago on Thursday March 31, 2011 | Permalink
  3. Great, thanks! I'll do that right now.

    Posted 13 years ago on Thursday March 31, 2011 | Permalink
  4. Gravity Forms-Version: 1.5

    We have a similar problem. Admin notification emails are blank and no new form-entries appear in the wordpress backend.

    We checked the table hiranu21_rg_lead_detail in our wordpress database and found the last form entry where the fields lead_id were set to zero.

    It looks like there a 2 columns missing in our hiranu21_rg_lead table (currency and created by, because the last insert for this tables fails with ERROR 1054 (42S22): Unknown column 'currency' in 'field list'

    How could these fields be restored.

    Posted 13 years ago on Friday April 1, 2011 | Permalink
  5. @Gerhard It sounds like your database tables were not created properly when you installed Gravity Forms. Your database may have encountered an issue and didn't create them properly.

    You could try forcing Gravity Forms to re-run it's setup process again. You would do this by accessing your wp_options table and look for the option Gravity Forms adds that sets the current installed version.

    - Go to plugins

    - Deactivate Gravity Forms

    - Edit your database (i'm assuming you are comfortable doing this given your post above) and edit the wp_options table and change the values of the options named rg_gforms_version and rg_form_version to 1.0 from what is probably currently 1.5

    - Go to plugins

    - Activate Gravity Forms

    Go to the Settings page of Gravity Forms after doing so. It should re-run it's setup process thinking v1.0 was previously installed and that may correct the issue... unless it's unable to update the database because the mysql user it runs as (wp-config.php) doesn't have that capability.

    If that doesn't work you may need to uninstall and re-install Gravity Forms from scratch to correct this. If you have existing forms and entries, you would want to export the entries to CSV and your forms to XML before doing so. It sounds like things weren't updating properly by your database server or web server during the update process.

    To install Gravity Forms completely you would go to the Settings page (Forms > Settings) and click the uninstall button.

    Posted 13 years ago on Friday April 1, 2011 | Permalink
  6. Carl, I'm still having the same issue and losing customer feedback every minute. Did you login with the information I sent you?

    Thanks,
    Rusty

    Posted 13 years ago on Friday April 1, 2011 | Permalink
  7. I have, and I just responded to you. This appears to be a plugin conflict. Something is hijacking the form submission process and the POST action which results in Gravity Forms not submitting. This isn't a surprising situation as you have 49 active plugins which is quite a lot. The more plugins you use, the greater the chance you have of running into issues such as this.

    In order to determine the problem you would have to do a plugin conflict resolution test. This would involve deactivating ALL your plugins except Gravity Forms, and then testing to narrow down which plugin is causing the issue and from there determining why.

    Here is how you determine which plugin is interfering:

    To test for a plugin conflict:

    - Deactivate ALL plugins
    - Activate Gravity Forms
    - Check to see if the issue occurs

    If it does not, then one of your plugins is causing a with Gravity Forms. To narrow it down follow the steps below:

    - Activate each plugin one by one
    - Check to see if the issue occurs after each one

    A way to speed this process up is instead of activating them one by one, activate them in groups... say 5 at a time... and then when you encounter a group that causes the issue to occur, deactivate that 5 and then activate them one by one and test after each one.

    Let me know how it goes. We can't prevent themes or plugins from causing conflicts, it's just a fact of life with WordPress themes/plugins, especially when running large numbers of them from a wide variety of sources. This can happen when the plugin or theme doesn't isolate when and where it executes code.

    If it doesn't work with ALL other plugins deactivated then it sounds like a server related configuration issue. If your server runs Windows (and not linux) then your host could have changed something with how URL rewriting functions, which can cause this type of problem to occur. But it sounds more like a plugin conflict.

    Posted 13 years ago on Friday April 1, 2011 | Permalink
  8. This really doesn't make much sense since nothing has changed in the time that all my forms were working and then weren't working. I have spent sometime this morning doing as you suggested without too much success, especially since our corporate site depends on some of the plugins and will break if I turn them off. I can't afford to spend much more than an hour on this before I remove Gravity forms completely and recreate all my forms using something less complex.

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  9. @Rusty That is up to you. I'm just trying to help you resolve the issue.

    Because you updated to a new version of Gravity Forms, that means one of your other plugins may be causing a conflict with it. Without deactivating them all and then testing, you won't be able to determine which one.

    We can only do so much to prevent another plugin from causing a problem. We follow best practices, but the vast majority of plugins do not and that is when conflicts and issues arise.

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  10. I deactivated every plugin except Gravity and updated my WooTheme and framework (just in case) and am still having the same issues.

    Suggestions?

    Thanks!

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  11. I can look into it again. One thing I noted in my original email to you was in regards to the type of web server you are running. Are you using a Windows server or Linux to host your site? Because as I mentioned int he email, this behavior can also appear on Windows servers who don't implement URL Rewriting properly.

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  12. Linux...our host is Media Temple (grid service)

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  13. I had this same issue, and Carl's suggestion above to edit the database worked for me. I wasn't able to find rg_gforms_version, but I did change the value in wp_options for rg_form_version to 1.0 from 1.5, and when I reactivated GF everything was kosher. Like Rusty, I had done the plugin test and found no conflicts.

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  14. @Heather It sounds like the 1.5 setup didn't run properly the first time then, and making that change would force it to run again so thats good to know.

    @Rusty It's possible this could very well be the same issue you have encountered. I could make this change for you if I can access your PHPMyAdmin to update the option value. I would need control panel access to your hosting to fix this, unless you want to take a stab at it yourself... but i'd be glad to help you with it. If so you can send us this info via our Contact Us form.

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  15. Yay! That did the trick...I was a little uncomfortable messing with the database, but I made the change and it's working just fine. Thanks so much for sticking with me!

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  16. @Rusty No problem, i'm glad we figured it out.

    Posted 13 years ago on Tuesday April 5, 2011 | Permalink
  17. splendid
    Member

    I had the EXACT same issue -- I was running GF 1.3. I did a complete update of the plugin and it did not correct the issue. After the upgrade to 1.5 and still no luck, I tried the DB hack of changing the entry from 1.5.1.1. to 1.0, yet it did nothing for me, even though hitting the Gravity Forms settings page did update the db back to 1.5.1.1. Once I did a complete uninstall and reinstall everything is back to working.

    The curious piece of this is that it broke w/o anything being modified. I have not updated this site in over 6 months and everything broke in march of this year. Not 1 plugin, nor wordpress was updated and somehow this just stopped working out of nowhere. Hoping this doesn't happen out of nowhere again...

    Posted 13 years ago on Wednesday April 13, 2011 | Permalink
  18. treuter
    Member

    Same issue here. We reverted all the way back to version 1.4.3.1 to resolve the issue (Versions 1.5.1 and 1.5 broke).

    At this point, hopefully the next release will allow us to upgrade.

    Posted 13 years ago on Wednesday April 13, 2011 | Permalink
  19. @treuter Can you inspect your wp_options table and see what version is listed in the Gravity Forms options that store the version number? It's probably the same issue outlined above. We haven't been able to replicate it. If you would allow us to check out your site and look at it, that would help us debug the issue.

    Posted 13 years ago on Wednesday April 13, 2011 | Permalink
  20. I'm having the same issue too. We've been using GF for almost a year with no issues, and this latest version has caused quite a stir among our clients. :(

    Just checked the wp_options table and found the following--
    - rg_gforms_version: <no entry by this name>
    - rg_form_version: 1.5.1.1

    I changed rg_form_version to 1.0, then re-activated the GF plugin and went to settings. Still no luck. I also checked the wp_options table again, but it still says 1.0 -- I don't think any auto-updater ran.

    We have a WP Multi-site install with multiple clients and hundreds of form entries. Uninstalling everything is really not an option for us... What can we do?

    Posted 13 years ago on Wednesday April 13, 2011 | Permalink
  21. @skyrocket Can you send us a WordPress admin login for this site so we can take a look? It will need to have super admin access. You can send this to us via our Contact Us form.

    We may need additional access (such as PHPMyAdmin access) in order to debug this further and determine what is going on. Also include a link to a form that we can see having the issue so we can see what is happening prior to. Because if the above didn't work, you have something else going on.

    Posted 13 years ago on Thursday April 14, 2011 | Permalink
  22. @Carl - I don't think that's really possible. We have a multi-DB setup, so it's rather complicated to figure out which databases contain blogs that have the GF plugin enabled, and we cannot allow root access to the whole WP network.

    Is there no script we can run to force the auto-updater to run?

    Posted 13 years ago on Friday April 15, 2011 | Permalink
  23. There is no script that can be run, it's based on the version number. Something is preventing the auto-updater to run. The only way for us to debug this is to be able to access the site and see the issue happening and then debug it. We can't replicate this issue locally, which means we can't debug something we can't replicate. We would need access to the site in order to take a look because we need to see it happening on the site that is having the issue.

    Posted 13 years ago on Friday April 15, 2011 | Permalink
  24. rplatner
    Member

    I have a similar issue. So far we are using gravity forms on a development server so we don't have any data we care about. We set it up in March of this year and made a few test forms. Those worked perfectly and the entries were correct, etc.

    We updated Gravity Forms recently and wanted to get back to learning more about it and now the entries are not being logged in the backend or in the database. This problem exists with existing forms as well as new forms we have created to test the problem.

    We have a network installation with multiple sites and each site is a directory domain. We do a network activation of the Gravity Forms plugin and then setup for each blog.

    I tried the above fixes, but they have not worked for us. There are seven sites, each with their own wp_options. I reset rg_form_version to 1.0 in the root of wp_options, but there are wp_options file for each site and they each have an rg_form_version. Should I have reset this in every site?

    Since there is not any data in our gravity forms yet that we care about I next tried to uninstall gravity forms. Under the network admin, there are no settings for Gravity Forms. I went to the main site and went to the form settings page and hit "Uninstall Gravity Forms". This didn't uninstall the plugin, because it was still available in the plugin directory. I imagine this is because it is network activated. None of the forms or entries were removed either. Again I'm guessing this has to do with the network issue.

    Next I just deleted the plugin, got a new version from your site, and tried it, but it still has the same issue of not logging the entries.

    I think the fix of "Uninstall Gravity Forms" is meant to clean up the database, but it doesn't seem to work with a network of sites.

    We are running PHP 5.33, MySQL 5.0.77, WordPress 3.1.2, Gravity Forms 1.5.2.2 on a Linux server.

    Any ideas??

    The URL won't be useful, but here it is http://blogsdev.ucs.uri.edu/testsite/?page_id=80
    Notice we have also tried using the 2010 theme, disabling pretty premalinks, and everything else you have suggested.

    Posted 13 years ago on Friday May 20, 2011 | Permalink
  25. I'd have to look at the Uninstall as far as deleting all the tables across a multi-site installation. It should, but the issue has never come up so i'd have to test on my end to make sure.

    If you have a multi-site install you'd have to make that change in every options table for each site because each site has their own options table.

    Posted 13 years ago on Friday May 20, 2011 | Permalink
  26. rplatner
    Member

    I went through the wp_nn_options (where nn = the site number) for every site and set rg_form_version to 1.0 for all that existed. Then I went to only one site and activated. I created a new form with two one line text entries for name and number. I made a new page and put the form there. I filled in the form and submitted. I see the entered name and number show up in wp_nn_rg_lead_detail. But when I go to the backend of WordPress it tells me there are no entries for this form. I filled out the form a second time, saw the data entered into wp_nn_rg_lead_detail again and again the backend tells me there are no entries. With this site as the only site where Gravity Forms was activated I went to forms settings and hit the Uninstall Gravity Forms button. Gravity Forms deactivated for this site, but it didn't remove the plugin. It also didn't remove any of my forms and I still see the data in wp_nn_rg_lead_detail.

    Posted 13 years ago on Monday May 23, 2011 | Permalink
  27. @rplatner When you inspect wp_nn_rg_lead does it have a Currency column? If not, the database user your WordPress site is configured to use may not have Alter permissions which prevents Gravity Forms from being able to add this new column to the lead table and will prevent entries from being saved due to a database error. Also try turning WP_DEBUG mode On and submitting a form and see what errors occur (note: errors are what you need to look for, not warning or notices).

    Posted 13 years ago on Monday May 23, 2011 | Permalink
  28. rplatner
    Member

    We gave the wordpress user Alter permissions, when that didn't make a difference we gave all permissions. That had no effect. lead_detail consistently shows the most recent entry, but rg_lead remains empty. After giving all permissions, I created a new simple form with two one line text entries. Each entry, as it occurs, shows up in lead_detail, but as I said rg_lead has zero rows. In the Structure I see the following columns: Field, Type, Collation, Attributes, Null, Default, Extra, Action

    Any ideas?

    Posted 13 years ago on Tuesday May 24, 2011 | Permalink
  29. @rplatner The problem is the rg_lead table wasn't updated because when it was installed the database user did not have the correct permissions. Your WordPress database user should always have all permissions, plugins and WordPress need to be able to make changes to the database and without the proper permissions it causes issues.

    So what is happening is the update happened, rg_lead was not updated with the new columns, and now it can't be written to because of an error because columns that should be there don't exist. If the database user had full permissions prior to the update, this wouldn't have happened because the table would have been updated properly.

    You need to reset the form version in the options table again so Gravity Forms tries to re-run it's setup to create the new columns now that your database user should have proper permissions.

    Posted 13 years ago on Tuesday May 24, 2011 | Permalink
  30. rplatner
    Member

    Seems to be working now thanks!

    Posted 13 years ago on Tuesday May 24, 2011 | Permalink

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