Title: Update entry &#8211; new entry created (null)
Last modified: October 11, 2017

---

# Update entry – new entry created (null)

 *  Resolved [thierryx_22](https://wordpress.org/support/users/thierryx_22/)
 * (@thierryx_22)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/)
 * Hi,
 * I create a new topic for this issue which has not yet been corrected.
    When I
   edit and update an entry, a new empty entry in rg_lead is created.
 * [https://wordpress.org/support/topic/new-entry-in-rg_lead-when-updating-form-entry/](https://wordpress.org/support/topic/new-entry-in-rg_lead-when-updating-form-entry/)
 * Don’t hesitate to ask me for more technical informations.
 * Thanks for your help

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [fried_eggz](https://wordpress.org/support/users/fried_eggz/)
 * (@fried_eggz)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/#post-9579565)
 * I’ll take a look at this. First question: Is the entry visible in the wordpress
   backend or only in the database?
 *  Plugin Author [fried_eggz](https://wordpress.org/support/users/fried_eggz/)
 * (@fried_eggz)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/#post-9579689)
 * I have found the bug. The problem was that the GFAPI was not able to delete a
   completely empty entry (I need to empty the entry before deletion to keep attached
   files).
 * Anyways, I have fixed this and uploaded a patch. You need to download the plugin
   again from this repo (no new version number so no automatic update).
 * Thanks for finding this bug that could potentially flood your database with garbage.
   Also, if you like the plugin, please consider [writing a short review](https://wordpress.org/support/plugin/gravity-forms-sticky-list/reviews/).
 * Thanks again.
    -  This reply was modified 8 years, 7 months ago by [fried_eggz](https://wordpress.org/support/users/fried_eggz/).
    -  This reply was modified 8 years, 7 months ago by [fried_eggz](https://wordpress.org/support/users/fried_eggz/).
 *  Thread Starter [thierryx_22](https://wordpress.org/support/users/thierryx_22/)
 * (@thierryx_22)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/#post-9579731)
 * Thanks a lot for your very quick answer and for the time you spent to find a 
   fix.
    I will download and check the patch very quickly and will tell you back.
 *  Thread Starter [thierryx_22](https://wordpress.org/support/users/thierryx_22/)
 * (@thierryx_22)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/#post-9587366)
 * Great. It works.
    Thanks a lot !
 *  Plugin Author [fried_eggz](https://wordpress.org/support/users/fried_eggz/)
 * (@fried_eggz)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/#post-9587489)
 * That’s great. If you like the plugin, please consider writing a short review.
   Thanks.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Update entry – new entry created (null)’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/gravity-forms-sticky-list_9b65b3.
   svg)
 * [Gravity Forms Sticky List](https://wordpress.org/plugins/gravity-forms-sticky-list/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gravity-forms-sticky-list/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gravity-forms-sticky-list/)
 * [Active Topics](https://wordpress.org/support/plugin/gravity-forms-sticky-list/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gravity-forms-sticky-list/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gravity-forms-sticky-list/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [fried_eggz](https://wordpress.org/support/users/fried_eggz/)
 * Last activity: [8 years, 6 months ago](https://wordpress.org/support/topic/update-entry-new-entry-created-null/#post-9587489)
 * Status: resolved