
We’re pleased to announce the release of Advanced Post Creation 1.6.2 with the following updates…
- Added security enhancements.
- Added Post Editing column to the feeds list page.
- Added a filter hook, gform_advancedpostcreation_meta_fields, to modify the meta keys shown on the Feed.
- Updated the APC Post List block to Block API v3.
Turn form submissions into published content
A submitted form usually just sits in an entry list, waiting for someone to act on it. The Gravity Forms Advanced Post Creation Add-On skips that step entirely. It turns each submission into a real WordPress post, page, or custom post type automatically.
Titles, content, and custom fields all get filled in using the data from the entry itself. Categories, tags, and other taxonomies can be assigned the same way, without anyone touching the WordPress editor by hand.
If a form collects file uploads, those files land directly in the Media Library and attach to the new post. Contributors can even view and manage their own submissions from the front end. They use the APC Post List block, so dashboard access is never required.
Key features of Advanced Post Creation
- Multi-post-type support – Create standard posts, pages, or any registered custom post type from a single form.
- Automatic taxonomy assignment – Assign categories, tags, and custom taxonomies to a post as soon as it’s created.
- Merge tag field mapping – Use merge tags to populate post titles and content, and map data into custom fields.
- Media Library integration – Add uploaded files to the Media Library automatically and attach them to the new post.
- Front-end editing – Let contributors view and edit their submissions from the front end using the APC Post List block.
For more information about setting up Advanced Post Creation, be sure to check out the Gravity Forms documentation.
Note: Advanced Post Creation is available with the Gravity Forms Elite and Nonprofit licenses. Visit our pricing page for more information on the features and other add-ons available on each plan.
Advanced Post Creation 1.6.2 changelog
- Added security enhancements.
- Added Post Editing column to the feeds list page.
- Added a filter hook, gform_advancedpostcreation_meta_fields, to modify the meta keys shown on the Feed.
- Updated the APC Post List block to Block API v3.
- Updated the appearance of the Signature field when you are editing a post to hide the “Reset Signature” button when the field is not editable.
- Fixed an issue where the gform_apc_shared dependency was triggering a console error.
- Fixed wording for the feed conditional logic tooltip.
- Fixed a compatibility bug with Divi Theme where the pagination buttons in the APC block display list markers.
- Fixed an issue where the get_forms() function is called on pages that have no Gravity Forms elements.
- Fixed a bug that prevented post meta from being saved to the initial revision when a post is created.
- Fixed a console error in the block editor when an APC block is present.
- Fixed an issue where the Dropbox field remains enabled even when it is not selected as editable in the Edit Post settings.
- Fixed an issue that causes APC assets to be enqueued on frontend pages where no APC features are used.
- Fixed an issue where a warning appears when importing a form that contains an APC hook.
- Fixed an issue where a non-editable Paragraph RTE field remains editable via keyboard navigation.
- Fixed an issue where the APC grid is not displaying correctly in the block editor in mobile view.
- Fixed an issue that allowed readonly fields to be modified in frontend post editing.
- Fixed an error caused by the get_current_screen() function returning null in certain admin contexts.
If you are an Elite or Nonprofit Gravity Forms license holder, Advanced Post Creation 1.6.2 can be updated in your WordPress dashboard, or downloaded manually from your Gravity account.
Note: After updating, clear your site’s cache to ensure you’re running the latest version. We also recommend excluding pages that include Gravity Forms from caching and script optimization, as cached form pages can interfere with dynamic population, field validation, honeypot, and add-ons that rely on time-sensitive tokens.
Read our FAQ on Cache and Script Optimizer Issues for details and exclusion steps by host/plugin.


