I’m experiencing the same issue!
Sticky List 1.4.1
Wodpress: 4.4.2
Edit: Also when editing a form the submit button does not change to ‘update’ it still says submit. I believe the code should change the button text, correct?
tdtmusic – is this happening to you as well?
This error is accompanying it: Notice: Undefined index: gform_submit in /plugins/gravity-forms-sticky-list/class-sticky-list.php on line 833
Thanks for reporting this. I’ll take a look. If this is in fact a bug it must have been introduced by some change in Gravity Forms.
In my case, the button correctly says Update. AND it works as it should IF I edit an entry that I previously created on the same computer/IP. Basically I created a bunch of entries and assigned users to them, so they can edit them as they wish, but they get the issue above. If I edit any of these entries, it’s fine.
Ok. How exactly did you assign users to entries that you created?
I used the Edit link on the Entries page. Each entry has View, Edit, etc., and if I choose to edit it, I can assign a WordPress user as the form creator.
Any updates on this topic?
I would also like to know if there’s a solution. I think it has something to do with the IP check of the plugin. If I login as an entry creator from the same IP where I completed the form, I can edit it just fine, without any duplicates. But the actual user, obviously, logs in from a different IP and maybe the plugin sees the submission as a new thing. Is there any way to disable this check?
I cannot find a way to edit the entry creator. Could you please provide screenshots?
I could provide access to the staging server in a direct message if that would help.
Hello,
I’ve got the same problem. Is there a solution already?
I can provide login if necessary!
Greets Jeen
Did you find anything that would help us solve this issue? Or at least can you give us a way to disable the IP check for the forms? Thanks!
Hello tdtmusic,
I’ve disabled ajax in the form itself and solved my problem.
Greets Jeen
To everyone following this issue: I have not been able to recreate this bug.
Please describe, in detail, how to reproduce this bug in a vanilla install.
Thanks
