Correct the entry.
Keep its published record current.

Give staff an entry-editing page that also updates the WordPress post created from that submission.

See the plugins See how it works

Rune archive records Staff view

The entry and its post stay together.

Record WY7K9N3Q Description corrected

Entry saved

Published record Mapped content updated

Post updated

Entry edit → Associated post updated

Illustrative experience

Edit from a front-end page
Keep the source entry
Update its associated post

The finished experience

One edit reaches the record people see.

Staff can update the form entry from the front end while the associated post stays in step through the required snippet.

A good fit for
Teams maintaining published records that were created by Gravity Forms Advanced Post Creation.

1

Create the post from its source entry.

Use the Gravity Forms Advanced Post Creation add-on to create your post or custom post type record from the submitted entry. Keep that original entry as the source staff will edit.

Gravity Forms
2

Give staff a focused editing view.

Build an Entry Blocks list with an edit view, showing the fields staff need to correct. Restrict the page and entries to the staff who should have access.

GP Entry Blocks
3

Connect entry edits to post updates.

Install Update Post on Entry Edit so Advanced Post Creation updates the associated post. Add Process Feeds on Edit to rerun the feed when the entry is edited, and configure its excluded feed IDs so unrelated actions are not repeated.

GP Entry Blocks

Inspired by a real build

Spotlight: Updating Custom Post Types with Entry Blocks September 2025 See how Josh built an all-encompassing custom post type update workflow for his team using Gravity Forms. Read the spotlight

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

GP Entry Blocks

Gives staff a front-end list and editing form for the source entries.

Explore GP Entry Blocks

Before you start

GP Entry Blocks and the separate Advanced Post Creation add-on.
The free Update Post on Entry Edit and Process Feeds on Edit snippets. Configure feed exclusions deliberately; delayed feeds are not processed by the latter snippet.
Posts created from the source entries by Advanced Post Creation, with staff access rules on the editing views. Test the update with every feed enabled on the form.

Free snippets it also uses

Snippets are free, and each one carries its own instructions in the Snippet Library .

Works alongside

Gravity Forms Advanced Post Creation Creates the WordPress post from the form entry and supplies the mapping used by the update snippet.

Sold and supported by their makers, not by us.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

GP Entry BlocksPerks

Gravity Perks Basic $59 /year

Covers this on one site. More sites need Advanced or Pro.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

Does Entry Blocks update posts by itself?

No. Entry Blocks edits the entry. Advanced Post Creation supplies the post mapping, Process Feeds on Edit reruns its feed, and Update Post on Entry Edit targets the associated post instead of creating a new one.

Can this edit any existing WordPress post?

The demonstrated workflow updates posts created from their source entries through Advanced Post Creation. It is not a general front-end editor for unrelated existing posts.

Will an edit rerun other form actions?

Process Feeds on Edit loops through registered add-ons and processes their feeds, except the feed IDs you exclude; delayed feeds still do not run. Configure exclusions and test so an edit does not repeat actions you only intend on the original submission.