Error on submission, functionality does not seem to work with new version of gf

Issue #3 resolved
Matthew Hunt created an issue

Hi Jake,

Thanks for stepping up on this one. I am not a php developer myself or I would have taken over this update a while ago. Ideally this plugin should show a thumbnail of the image, not just the file name.

I'm testing out this update and I can't seem to get this version to work. Have you ran into this error at all?

Warning: call_user_func_array() expects parameter 1 to be a valid callback, class 'GFUpdatePost' does not have a method 'gform_after_submission' ...../wp-includes/plugin.php on line 406

I followed instructions in the readme file and still ended up with that error after form submission.

I am using Gravity forms Version 1.7.9

I'm going to see if my team can look into this issue as well. Any insight you have would be awesome! Thanks again!

-Matt

Comments (8)

  1. Jacob Snyder repo owner

    Thanks. There is a bug. I have a new version that fixes that. and adds thumbnails. I need to test it a little more and release. i got insanely busy the past two weeks and was unable to release it. It should come out this week though.

  2. Matthew Hunt reporter

    Thanks Jake. I appreciate the quick reply. I am working with another php developer on a project that really needs this feature. Is there anyway we can assist in the testing? Can you commit this to a new branch or something? If there is anything I can do to help this along please let me know. We need this feature for this plugin asap so we are will to help. We can even get in touch directly if you like. I seen that you have done a lot of work with ACF and so do we. Thanks so much!

    -Matt

  3. Jacob Snyder repo owner

    Yeah. I am going to put up the new version today. soon.

    I am curious. My new version is a decent change to the previous version. I pretty much rewrote it. I ripped out the delete posts stuff because I felt like it was outside of the scope what I think this plugin should be and it really doubled the size of the code.

    My question for you. Is the delete post portion something you want? or were using?

  4. Matthew Hunt reporter

    Hi Jake,

    Thanks for putting out a new version! We really appreciate all your hard work. I'm really happy someone stepped up on this plugin.

    I did not notice you had this feature. Do you mean you are giving them the ability to delete the post as they update it or delete images?

    I have never had a use case where I needed users to have the ability to delete the post they are editing. For the most part if anyone who needed to remove a post they made they would contact the admin. For the new project we have, we will never give them the ability to delete it. One way to easily do this would be to create a form field on the gravity form that asks if they are requesting deletion or requesting the page to be unpublished. We may do that. Instead of allowing users to delete the post, I would vote for allowing them to unpublish and publish the post at will. I've setup sites before that give users a list of their posts so they could manage them. Deleting a post should be something admins have to do. But it also depends on the site. I'm willing to bet there are not a lot of sites out there that will need that.

    -Matt

  5. Matthew Hunt reporter

    Another thing I noticed about this plugin was that the plugin author had a a bug where the category of the post was also disappearing on the next edit of the post the same way the images were. That was one was not so important to me, but did you notice that as well? -Matt

  6. Jacob Snyder repo owner

    Categories should work in this version. Also multiselects and checkboxes. Let me know what issues or ideas you come up with. I am not sure I will be able to do much more than small bug fixes this week though.

    Check out the new version.

  7. Jacob Snyder repo owner

    I have it running with the lastest version now. I think what happened before was that Gravity Forms removed support for a function that was deprecated a while back. But since the plugin hadn't really been updated in such a long time, the function was still hanging around. It is all cleaned up and new now.

  8. Log in to comment