https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post Gravity Support Forums Topic: gform_after_submission; inherit post en-US Tue, 07 Apr 2026 16:38:04 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-42539 Wed, 30 Nov 2011 07:38:08 +0000 hittheroadjack 42539@https://legacy.forums.gravityhelp.com/ <p>Auto-reply to my question 3 days ago : it is the move_uploaded_file() function!<br /> Transferring the files using this function converts umlauts . Since GF is not using wp_handle_upload function from WP (why?) you do not get hooks or filters short before transferring the upload. So I had to modify the plugin code(!) to get rid of this nasty thing. I hate doing that because of obvious reasons.<br /> Are there any plans to insert a hook/filter there or to use wp_handle_upload in future?? </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-42220 Sat, 26 Nov 2011 21:02:30 +0000 hittheroadjack 42220@https://legacy.forums.gravityhelp.com/ <p>Another question: When using the 'gform_pre_submission' hook you get a $Form object as hand-over parameter. This does not contain the $Entry object or the values, does it? How can I make changes to the values in the $entry[n] before submission to the database?<br /> I tried also the 'gform_post_data' and 'gform_save_field_value' but they do not seem to be fired in this case. </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-42200 Fri, 25 Nov 2011 17:41:35 +0000 hittheroadjack 42200@https://legacy.forums.gravityhelp.com/ <p>Tried it and worked well, so far!<br /> But now I have another issue maybe related to the above. I have a image file upload field in my form and whenever my users are typing German umlauts the $entry[n] contains the right representation also after submission. The file is targeted as thumbnail image for the post. When I look at the uploaded file name, it has been transferred to the standard WP upload folder and to the hashed GF upload folder, but both have the umlauts converted to HTML entities and subseqently, is not displayed as a post_thumbnail. Looking at the database the GUID of the thumbnail points to the WP standard upload folder but the file name shows umlauts. Because they are not the same, it will not display. I have traced it back to the line 1870 in forms_model.php and the target there is the GF hashed upload folder/file name with umlauts. After that may debugger won't work and crashes when the database is accessed. So ,I can't tell what happens after.<br /> Long story, short question: where happens the fault? Is it the move_uploaded_file() function?<br /> It seems to happen during the file transfer. Anything I can hook or filter into? </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41352 Wed, 16 Nov 2011 19:00:03 +0000 hittheroadjack 41352@https://legacy.forums.gravityhelp.com/ <p>Thanks!<br /> I'll try that! </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41347 Wed, 16 Nov 2011 17:54:40 +0000 Carl Hancock 41347@https://legacy.forums.gravityhelp.com/ <p>I believe the hook you would want to use would be the gform_pre_submission hook:</p> <p><a href="http://www.gravityhelp.com/documentation/page/Gform_pre_submission" rel="nofollow">http://www.gravityhelp.com/documentation/page/Gform_pre_submission</a></p> <p>This hook fires after validation but before the entry is stored and the post is created. </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41342 Wed, 16 Nov 2011 17:15:13 +0000 hittheroadjack 41342@https://legacy.forums.gravityhelp.com/ <p>Thanks for looking into my problem.<br /> Knowing all this now, another solution comes to my mind :<br /> What if I simply take [5] and write it to [2] using a hook which is fired just before the post is created. That should solve the problem because direct entry to Post Title field is taken as the postname.<br /> Is there such a hook or filter? possibly 'gform_post_data' ? </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41335 Wed, 16 Nov 2011 17:01:45 +0000 Carl Hancock 41335@https://legacy.forums.gravityhelp.com/ <p>The problem is going to be the content template is only used to create the post. It's not stored as the value for that field.</p> <p>An alternative solution to what you want to do is going to be to scrap using the Single Input that populated the Post Title and instead use the Post Title.</p> <p>Since the Post Title field doesn't currently have the No Duplicates features what you will need to do is use the gform_validation field and write some custom validation to do your own check.</p> <p>The gform_validation hook has a tutorial here:</p> <p><a href="http://www.gravityhelp.com/documentation/page/Using_the_Gravity_Forms_%22gform_validation%22_Hook" rel="nofollow">http://www.gravityhelp.com/documentation/page/Using_the_Gravity_Forms_%22gform_validation%22_Hook</a> </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41255 Wed, 16 Nov 2011 10:15:04 +0000 hittheroadjack 41255@https://legacy.forums.gravityhelp.com/ <p>Now I have set up a test. the result is: it can be reproduced!<br /> This is what I did :<br /> [5] is the single line input field<br /> [2] is the Post Title field with a merge tag in the content template like this {input:5}<br /> [3] is the body field<br /> the callback function of the gform_after_submission looks like<br /> function var_mail($entry, $form){<br /> var_dump($entry);<br /> wp_mail('dietmar@herian.de', 'Test GF', print_r($entry,True));<br /> wp_mail('dietmar@herian.de', 'Test GF', var_dump($entry,True));<br /> }<br /> this is what I get in the email:</p> <p>Array<br /> (<br /> [id] =&gt; 443<br /> [form_id] =&gt; 11<br /> [date_created] =&gt; 2011-11-16 13:51:03<br /> [is_starred] =&gt; 0<br /> [is_read] =&gt; 0<br /> [ip] =&gt; 82.135.31.79<br /> [source_url] =&gt; <a href="http://82.135.31.79/wordpress/cat_show_test/" rel="nofollow">http://82.135.31.79/wordpress/cat_show_test/</a><br /> [post_id] =&gt; 1103<br /> [currency] =&gt; EUR<br /> [payment_status] =&gt;<br /> [payment_date] =&gt;<br /> [transaction_id] =&gt;<br /> [payment_amount] =&gt;<br /> [is_fulfilled] =&gt;<br /> [created_by] =&gt; 1<br /> [transaction_type] =&gt;<br /> [user_agent] =&gt; Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0<br /> [status] =&gt; active<br /> [5] =&gt; title<br /> [3] =&gt; some text from body<br /> [1] =&gt;<br /> [2] =&gt;<br /> [4] =&gt;<br /> )<br /> $entry[2] is empty at firing the hook - it should be equal to $entry[5], if I am not wrong about the function of merge tags.<br /> And btw : you get exectly the same result when using the gform_post_submission hook </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41214 Tue, 15 Nov 2011 19:59:25 +0000 hittheroadjack 41214@https://legacy.forums.gravityhelp.com/ <p>I am not sure what you want me to do because I am using the German translations of GF. Do you mean the content template in a body field?<br /> I can check putting a Single Input and a Post Title as a tag into the content field and see what happens or I do a var_dump($entry) in the callback function of my gform_after_submission hook. I guess the latter will be more enlightening or I do both together.<br /> I am highly interested to use the Single Input field because this is a user input. They have no glue what's already in my database when they type it. Otherwise, I have to set a filter to avoid duplicates, bouncing back to user, re-enter and all that stuff.<br /> Is there a hook later in time, maybe gform_post_submission, where I can rely on the merge tags being parsed? </p> https://legacy.forums.gravityhelp.com/topic/gform_after_submission-inherit-post#post-41159 Tue, 15 Nov 2011 16:07:16 +0000 Carl Hancock 41159@https://legacy.forums.gravityhelp.com/ <p>The Post Title field doesn't have the no duplicates because of it's a unique field type and involves both entry and post interaction so it wasn't a feature that was added.</p> <p>The problem could be related to how and when post fields are executed. It's possible this code executed before the merge tags were parsed.</p> <p>Can you reliably reproduce this issue with a Single Input and Post Title field using the content template? </p>