How to Let Users Edit Their Posts From the Frontend
By Aleksan Aharonyan ·
To let users edit their posts from the front end, open the same submission form in edit mode for the post’s author and save over the original post instead of creating a new one. The author fixes a typo, swaps an image or corrects a category on a normal page of your site, and the post updates in place without anyone opening wp-admin.
Key takeaways
- Frontend editing is your submission form in edit mode: the fields come back filled with the post’s current values and saving updates that post rather than creating a second one.
- Permission follows the WordPress rule you already have. A user edits their own posts; an Editor or Administrator can edit anyone’s.
- The author needs a page where their posts are listed with an edit icon, otherwise the edit link is a URL nobody remembers.
- Decide the redirect, the update message and the button text before you tell anyone editing is open, then add a time lock so posts stop accepting changes after a set number of hours.
What editing from the front end actually means
Frontend editing means a logged-in user opens a page on your site, sees a post they wrote loaded into a form with its current title, content and terms, changes something and saves, and the post is updated in place.
Two things have to be true for that to work. The edit link has to identify the post, usually by carrying the post ID in the URL, and the form has to check that the person who opened it is allowed to edit that post. Without the second check, changing the number at the end of the URL would let any logged-in visitor open anyone’s draft.
The reason to build editing on the submission form rather than a separate edit screen is that the author already knows the form. Same fields in the same order, same editor, same category picker. They are not learning a second interface, and you are not maintaining two sets of field settings.
You could also send authors into wp-admin. WordPress will restrict a Contributor to their own unpublished posts, so the permissions work. What you get with that is the whole admin: dashboard widgets, menus, notices, and a post editor that looks nothing like the form they submitted with. For a site whose contributors are volunteers or one-time guest authors, that is a lot of surface for a one-line correction.
Who should be allowed to edit which posts
The post’s own author should be able to edit it, and anyone whose WordPress role can edit that post should be able to edit it too. WordPress already answers this with capabilities, and the front end should follow the same answer rather than invent a second rule.
In wp-admin: Subscribers cannot edit posts. Contributors can edit their own unpublished posts, which is what you want while a submission sits in Pending. Authors can edit their own posts after publication. Editors and Administrators can edit anyone’s. A front-end form can be more generous to the author: in Front User Submit, the post’s author can always open their own post in the form, whatever their role, while everyone else needs a role that can edit that post in WordPress.
Post status matters here more than people expect. The point of a Pending post is that the author can still fix it while you review; if your form locks the moment a post leaves Draft, the review loop turns into an email exchange. In wp-admin a Contributor loses edit access once their post is published, so a front-end form that lets authors edit their own posts covers that typo fix without promoting anyone to Author.
If you accept guest posts, those posts have no author account behind them. Nobody can log in and open the edit form for a post that was never tied to a user. Plan for that: either ask guests to email corrections, or require an account before submitting.
Step 1: Turn on frontend editing for the form and point it at an edit page
Turn editing on in the form’s settings and choose the page that holds the form as the edit page, so the edit link has somewhere to send the author.
In Front User Submit, a free plugin for frontend post submission and guest posting forms, the same form opens in edit mode for the post’s own author, with the fields they submitted already filled in. Editing is a per-form setting, which is useful: your main submission form can allow edits while a short announcement form stays closed. The edit post settings collect the edit page, redirect, update message, button text and time lock in one place.
Set the edit page to the page that actually contains the form’s shortcode or block. If that page changes later, come back and point the setting at the new one, because an edit link that lands on a page without the form leaves the author staring at a normal page with nothing to edit.
Step 2: Give users a place to find their posts and the edit link
Give each user a dashboard page that lists their own posts with an edit icon next to each one, and link to it from your navigation or from the confirmation message after a submission.
In Front User Submit the [fe_fs_user_admin] shortcode renders that dashboard with Publish, Pending and Draft tabs, and every post in the list has edit and delete icons. The user dashboard settings explain the tabs and the delete behavior, which follows the WordPress role: Subscribers cannot delete, Contributors can delete their own unpublished posts, Authors their own posts.
Two things to watch. First, make the dashboard page easy to reach, because a user who cannot find their post cannot edit it. Second, if you send a notification email when a post is submitted or published, include a link back to the dashboard, not just a link to the post.
Step 3: Set the edit screen’s redirect, update message and button text
Decide where the author lands after saving an edit, what the page tells them, and what the button says, then set all three in the form’s edit settings.
The redirect is the important one. The usual choices are staying on the edit page, opening the updated post, or returning to the dashboard. Returning to the dashboard is clearest for most sites: the author sees the post in its current status, which answers “did that save?” without another click.
The update message should say plainly that the post was updated, and the button should read something like “Update post” rather than “Submit”. The same form serves both creating and editing, so the wording is the only signal the author gets that they are changing an existing post and not adding a new one.
Step 4: Add a time lock so old posts stop accepting changes
Set the time lock to a number of hours after the post was created, and the form stops opening for edits once that window passes.
The time lock sits in the same edit settings: it closes frontend editing a set number of hours after the post was created, and it applies to editing from the front end rather than to your own changes in wp-admin.
The window depends on the content. A news or events site can close editing after a short period, because after that a change is usually a correction request that needs a human. A directory or listing site should keep the window open much longer, since opening hours and prices change. An evergreen tutorial can stay open indefinitely, as long as you keep an eye on what gets changed.
The lock is not a security feature on its own. It limits late edits, it does not replace review: if a form publishes straight away, a user who edits inside the window still publishes straight away. Keep sensitive forms on Pending and review there.
Testing it: what the author sees, what the editor sees, what happens after the edit
Test with two accounts that have the same role your contributors have, plus your own administrator account, and check the same post from all three sides.
As the first test user, open the dashboard, click the edit icon, change the title and save. Then check three things: the post page shows the new title, wp-admin shows one post and not two, and the status and the other fields (featured image, categories) are what they were before.
As the second test user, open the edit link for the first user’s post. The form should not load someone else’s content. Log out and open the same link: you should get the restricted message, or the login form if you chose that option (Pro).
As the administrator, confirm you can still edit any post in wp-admin, published or not, regardless of the time lock. That is the fallback when an author asks for a change after their window has closed.
Finally, test the lock itself. Set a short window in the form settings, create a test post through the form, wait for the window to pass, then try to edit. If the form still opens, the lock is measuring something other than what you expect, and it is worth fixing before real posts age out of it.
FAQ
Do users need an account to edit their posts?
Yes. Editing is tied to the post’s author, so a post submitted without an account has nobody to attach the edit link to. Either require registration before submitting, or let guests send corrections by email to an address you actually monitor.
What stops one user from editing another user’s post?
The form checks the post against the logged-in user before it loads anything. A signed-in visitor who changes the post ID in the edit URL does not get another author’s content, and a logged-out visitor gets the restricted message or, on Pro, the login form. WordPress roles decide the rest.
Should I just give contributors the Contributor role and let them use wp-admin?
That works, and WordPress already limits a Contributor to their own unpublished posts there. The trade-off is the admin itself: menus, notices and a post editor that looks different from the form they submitted with. A front-end form keeps occasional contributors on the public site, and you can still use wp-admin for the regulars you trust.