https://legacy.forums.gravityhelp.com/topic/block-form-access-based-on-advanced-user-authentication Gravity Support Forums Topic: Block Form Access Based on Advanced User Authentication en-US Mon, 20 Apr 2026 04:52:49 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/block-form-access-based-on-advanced-user-authentication#post-362041 Thu, 04 Jul 2013 19:15:21 +0000 devEdge 362041@https://legacy.forums.gravityhelp.com/ <p>Ok, I guess I asked the question too quickly. I was right about using the gform_pre_render filter. Here's basically what I did...</p> <pre><code>add_filter( &quot;gform_pre_render&quot;, &quot;block_user_render_form&quot;, 100, 1 ); function block_user_render_form( $form ) { //Put your form ID instead of 6 if ( $form[&#39;id&#39;] != 6 ) { return $form; } //test for authorization if ( !$authorized ) { echo &quot;&lt;p&gt;You are not authorized to do this.&lt;/p&gt;&quot;; return null; } return $form; }</code></pre> <p>The only caveat to returning a null form, is that GF will also output the following after the unauthorized message:<br /> "Oops! We could not locate your form."</p> <p>Which didn't bother me. But might for some...'</p> <p>Cheers! </p> https://legacy.forums.gravityhelp.com/topic/block-form-access-based-on-advanced-user-authentication#post-361993 Thu, 04 Jul 2013 17:55:18 +0000 devEdge 361993@https://legacy.forums.gravityhelp.com/ <p>Hello,</p> <p>I have a business directory website that allows a user to edit their business listing details (partially, at least). Each business listing (a custom post) is assigned the user as author. I use GF basically as a frontend editor, pulling in the post field values on the edit post form. Then, I've locked all these users out of the WordPress admin area. It's pretty cool actually...</p> <p>Here's the problem though. GF, by default, is only capable of creating new posts - not editing existing posts. Thus, when the edit form is called with an invalid post to edit (or none at all), GF defaults to creating a new post rather than displaying an unauthorized message. I need to change that.</p> <p>Is there a hook or filter I can use to add my own authentication logic and block the form when it is called? I was thinking the gform_pre_render filter might do the trick. Can I do my permissions check there and unset the form or something? Then echo an unauthorized message instead? How can I block the form from displaying (rendering at all actually)?</p> <p>By the way... GF does not respect the publish_posts capability in WordPress.</p> <p>Any thoughts? </p>