<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Gravity Support Forums Topic: Gravity Form updates existing custom_ field value</title>
		<link>https://legacy.forums.gravityhelp.com/topic/gravity-form-updates-existing-custom_-field-value</link>
		<description>Gravity Support Forums Topic: Gravity Form updates existing custom_ field value</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 06:52:17 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.1</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>https://legacy.forums.gravityhelp.com/search.php</link>
		</textInput>
		<atom:link href="https://legacy.forums.gravityhelp.com/rss/topic/gravity-form-updates-existing-custom_-field-value" rel="self" type="application/rss+xml" />

		<item>
			<title>Chris Hajer on "Gravity Form updates existing custom_ field value"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/gravity-form-updates-existing-custom_-field-value#post-38492</link>
			<pubDate>Fri, 21 Oct 2011 00:48:24 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">38492@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Sounds like the post or page will already exist, and you just need to update the status on that page?&#60;/p&#62;
&#60;p&#62;Gravity Forms might be overkill for that application, but you can still do it.  You would not want to create a post at all, just collect the status change.  If there are multiple facilities to manage, then you will need to account for updating multiple posts.  How many facilities do you need to maintain the status for?  If it's just one, it will not be too bad.   The process would be:&#60;/p&#62;
&#60;ul&#62;
&#60;li&#62;Know what post you're going to update&#60;/li&#62;
&#60;li&#62;Know the custom field key and possible values&#60;/li&#62;
&#60;li&#62;Use those values in a Gravity Form (radio buttons maybe, since the status is probably exclusive)&#60;/li&#62;
&#60;li&#62;Embed that form into a page that can be accessed only by someone with proper rights&#60;/li&#62;
&#60;li&#62;Process the form submission&#60;/li&#62;
&#60;li&#62;Use the gform_post_submission hook with a function to update the meta value for one specific post&#60;/li&#62;
&#60;/ul&#62;
&#60;p&#62;It's doable, and not difficult, just a few pieces that need to be put together to make it work.  If you can post more actual details about your situation, we can help point you in the right direction.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>kinetic on "Gravity Form updates existing custom_ field value"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/gravity-form-updates-existing-custom_-field-value#post-38460</link>
			<pubDate>Thu, 20 Oct 2011 17:45:17 +0000</pubDate>
			<dc:creator>kinetic</dc:creator>
			<guid isPermaLink="false">38460@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;I am needing to build a status update tool for a local facility. For instance, in the event of inclement weather, someone can go to the site, set the status to closed and it will render on the live site.&#60;/p&#62;
&#60;p&#62;My initial thought for doing this was having a Gravity Form post to a custom post type with the values i needed in custom fields (open, closed, duration, etc). But that would mean each time they update the status, it would be creating a new post.&#60;/p&#62;
&#60;p&#62;Is there a better way to handle this that I am not seeing? Can I have the form always interact with a single post, or update a custom field value independent of a post?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
