<?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: Using GF as a replacement for custom post types</title>
		<link>https://legacy.forums.gravityhelp.com/topic/using-gf-as-a-replacement-for-custom-post-types</link>
		<description>Gravity Support Forums Topic: Using GF as a replacement for custom post types</description>
		<language>en-US</language>
		<pubDate>Mon, 20 Apr 2026 08:28:44 +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/using-gf-as-a-replacement-for-custom-post-types" rel="self" type="application/rss+xml" />

		<item>
			<title>Chris Hajer on "Using GF as a replacement for custom post types"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/using-gf-as-a-replacement-for-custom-post-types#post-81392</link>
			<pubDate>Tue, 16 Oct 2012 08:39:56 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">81392@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;There is no revision history for the entries in Gravity Forms.  You could keep track in the notes for the entry.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "Using GF as a replacement for custom post types"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/using-gf-as-a-replacement-for-custom-post-types#post-81388</link>
			<pubDate>Tue, 16 Oct 2012 08:29:42 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">81388@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;Thanks! That's good news. Will Gravity Form be able to keep a history of all changes to one entry?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Chris Hajer on "Using GF as a replacement for custom post types"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/using-gf-as-a-replacement-for-custom-post-types#post-81381</link>
			<pubDate>Tue, 16 Oct 2012 08:03:52 +0000</pubDate>
			<dc:creator>Chris Hajer</dc:creator>
			<guid isPermaLink="false">81381@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;That would work fine I think and would not be related to WordPress posts or custom posts at all.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "Using GF as a replacement for custom post types"</title>
			<link>https://legacy.forums.gravityhelp.com/topic/using-gf-as-a-replacement-for-custom-post-types#post-81340</link>
			<pubDate>Tue, 16 Oct 2012 03:29:50 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">81340@https://legacy.forums.gravityhelp.com/</guid>
			<description>&#60;p&#62;So, I'm wondering what your thoughts are regarding using Gravity Forms to emulate a set of custom post types. The background is as follows: While Wordpress can handle custom post types, its handling of them rather inflexible and adding new fields can be quite a chore.&#60;/p&#62;
&#60;p&#62;A customer would like to use GF to help customer support keep track of item repair status. They would like to create one form for each type of product (new products will likely be added every year).&#60;/p&#62;
&#60;p&#62;The customer support representative would then create an entry using that form, and whenever the status of the item changes (e.g. from &#34;received&#34; to &#34;repaired&#34; or &#34;sent to customer&#34;) they would like to open that specific entry to update it.&#60;/p&#62;
&#60;p&#62;I know this is not exactly intended use, but as long as we don't modify the GF plugin and use the published API:s, do you foresee any difficulties or pitfalls?&#60;/p&#62;
&#60;p&#62;Any input would be greatly appreciated!
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
