Isaenko Alexei

<p>This plugin will disallow users manage them  profile on the admin page. They will have to do that on the frontend page.<br />
Activate the plugin and it will create a profile page with a shortcode, and after that users will be redirected to that page if they would like to edit their profile. Also you able to use the shortcode on any page, just insert the shortcode – [oi_frontend_profile].</p>
<p>You are able to change profile page and hide Admin bar from a frontend.</p>
<p>Supported laguages:</p>
<ul>
<li>English</li>
<li>Russian</li>
</ul>
<p>This plugin will disallow users manage them  profile on the admin page. They will have to do that on the frontend page.<br />
Activate the plugin and it creates the profile page with shortcode, and after that users will be redirected to this page if they will want to edit profile. Also you able to use the shortcode on any page, just insert the shortcode – [oi_frontend_profile].</p>
<p>In the next version of the plugin there will be an option page and you will be able to change profile page.</p>
<p>Supported laguages:</p>
<ul>
<li>English</li>
<li>Russian</li>
</ul>
<h3>Oi Frontend Profile</h3>
<p>Contributors: Isaenko Alexei<br />
Tags: profile, user, login, page, frontend, front-end<br />
Requires at least: 3.2<br />
Tested up to: 4.0<br />
Stable tag: 1.2<br />
License: GPLv2 or later<br />
License URI: http://www.gnu.org/licenses/gpl-2.0.html</p>
<p>This plugin disallow users going to the backend. They can manage theme profile on the frontend page.</p>


Oi Frontend Profile

This plugin disallow users going to the backend. They can manage theme prifile on the frontend page.

Jupitercow

Jake Snyder

Kevin Miller

Jeremy Saxey

<p><strong>Requires PHP 5.3 or greater</strong></p>
<p>Allows you to use Gravity Forms to update any post on the front end. If you use the “Gravity Forms + Custom Post Types”, you can even update custom post types and use custom taxonomies.</p>
<h4>Features</h4>
<ul>
<li>Supports custom field file uploading and deletion with thumbnails or mime type icons for existing items.</li>
<li>Fixed a bugs on multi selects and checkboxes.</li>
<li>Fixed bug on Categories.</li>
<li>Completely removed the ability to delete posts.</li>
<li>There are some filters to customize things now.</li>
<li>Adds non-query-var template method to setup a form.</li>
<li>Adds a really basic shortcode to setup a form (UPDATE: This is still supported, but it is better to use the addition, below, to the gravityform shortcode).</li>
<li>Adds an additional attribute to the gravityform shortcode: “update”</li>
</ul>
<h4>SHORTCODE</h4>
<pre><code>[gravityform id="1" update] // Loads current post for editing

[gravityform id="1" update="34"] // Loads post where ID=34 for editing
</code></pre>
<p>We worked with Rocketgenius, makers of Gravity Forms, to get a small upgrade added that allows us to extend their shortcode, so now you can simply add the “update” attribute to the normal “gravityform” shortcode. If you only add “update”, it will load the current post in to update. If you add an integer to the update attribute, it will use that to load a post by its ID.</p>
<h4>URL QUERY VARIABLE</h4>
<ol>
<li>At the heart, it is pretty similar to how it was, but now there is a nonce required to activate it.</li>
<li>
<p>So you should use the action to create your links.</p>
<p>do_action(‘gform_update_post/edit_link’);</p>
<p>do_action(‘gform_update_post/edit_link’, array(<br />
    ‘post_id’ => $post->ID,<br />
    ‘url’     => home_url(‘/edit_post/’),<br />
) );</p>
</li>
</ol>
<p><strong>Arguments (query string or array)</strong></p>
<ul>
<li><code>post_id</code> (int) (optional) The id of the post you want to edit. Default: global $post->ID</li>
<li><code>url</code> (string|int) (optional) Either the full url of the page where your edit form resides, or an id for the page/post where the edit form resides. Default: get_permalink()</li>
<li><code>text</code> (string) (optional) The link text. Default: “Edit Post”</li>
<li><code>title</code> (string) (optional) The title attribute of the anchor tag. Default: (text) parameter</li>
</ul>
<h3>Get just the URL</h3>
<p>This will return a basic edit url</p>
<pre><code>apply_filters('gform_update_post/edit_url', '');
</code></pre>
<p>Specify post to edit (post_id) and post that holds the edit form (url)</p>
<pre><code>apply_filters('gform_update_post/edit_url', 1, home_url('/edit_post/'));
</code></pre>
<h3>Shortcode to show the edit link</h3>
<pre><code>[gform_update_post_edit_link]
</code></pre>
<p>Specify post to edit (post_id) and post that holds the edit form (url)<br />
    [gform_update_post_edit_link post_id=1 url=6]</p>
<h4>IN TEMPLATE</h4>
<p>You can use the action to force a form show a specific post:</p>
<pre><code>do_action('gform_update_post/setup_form');

do_action('gform_update_post/setup_form', $post->ID);

do_action('gform_update_post/setup_form', array('post_id' => $post->ID, 'form_id' => $form_id));
</code></pre>
<p><strong>Parameters</strong></p>
<ul>
<li><code>post_id</code> (int|array) (optional) The id of the post you want to edit or an array with post id and/or form id. This allows you to specify the form id, so that update functionality does not get applied to other forms on the page. Default: global $post->ID</li>
</ul>


Gravity Forms: Post Updates

Thank you, your work is wonderfully appreciated. Makes updating content easy for users on the front end.

Does the job and great options!

Allows you to use Gravity Forms to update any post on the front end.

Oi Frontend Profile vs Gravity Forms: Post Updates