https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets Gravity Support Forums Topic: All_fields text-only submission for osTickets... en-US Sun, 19 Apr 2026 20:14:45 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-73375 Thu, 30 Aug 2012 21:40:27 +0000 Chris Hajer 73375@https://legacy.forums.gravityhelp.com/ <p>This is the accepted way of making modifications to your theme. It's not an unusual or unreasonable request.</p> <p>Child themes are a good idea whenever you are modifying a theme which might get updated, not only for this small amount of code in functions.php. A child theme is not a lot of work and need only contain a style.css and whatever templates or functions you want to override (for example, a small functions.php file in this case). Those changes in your child theme will persist no matter what the theme author updates.</p> <p>I see your feature request <a href="http://www.gravityhelp.com/forums/topic/text-only-all_fields-output" rel="nofollow">here</a>, so I will close this topic. </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-73318 Thu, 30 Aug 2012 14:50:32 +0000 CoastalData 73318@https://legacy.forums.gravityhelp.com/ <p>I've looked at child themes briefly before, but it seems like overkill just to add 5 little lines of code, wouldn't you agree? </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-73153 Wed, 29 Aug 2012 17:08:33 +0000 Chris Hajer 73153@https://legacy.forums.gravityhelp.com/ <p>You should use a child theme so that updates from the theme provider do not overwrite your custom functions.php file.</p> <p><a href="http://codex.wordpress.org/Child_Themes" rel="nofollow">http://codex.wordpress.org/Child_Themes</a><br /> <a href="https://www.google.com/search?q=why+use+a+wordpress+child+theme" rel="nofollow">https://www.google.com/search?q=why+use+a+wordpress+child+theme</a><br /> <a href="http://wordpress.org/support/topic/why-use-a-child-theme?replies=5" rel="nofollow">http://wordpress.org/support/topic/why-use-a-child-theme?replies=5</a> </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72971 Tue, 28 Aug 2012 15:33:09 +0000 CoastalData 72971@https://legacy.forums.gravityhelp.com/ <p>Right on, that makes more sense. Unless, of course, you're using one of the updatable themes for WordPress... wouldn't they suffer from the same problem, if you're editing functions.php?</p> <p>As it so happens, I'm not worried about that for this current site, but I have a couple more sites to work on, and at least one of them uses an updatable theme. </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72946 Tue, 28 Aug 2012 13:51:05 +0000 David Peralty 72946@https://legacy.forums.gravityhelp.com/ <p>You should never edit any of Gravity Forms' core files. Using hooks and filters should go into your theme's functions.php file. </p> <p><a href="http://www.gravityhelp.com/documentation/page/Where_Do_I_Put_This_Code%3F" rel="nofollow">http://www.gravityhelp.com/documentation/page/Where_Do_I_Put_This_Code%3F</a> </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72899 Tue, 28 Aug 2012 09:37:35 +0000 CoastalData 72899@https://legacy.forums.gravityhelp.com/ <p>Are you sure about that? I followed the instructions in that link to modify common.php directly, which is one of the plugins' files.</p> <p>Did I miss in there somehow that there's some other file to edit to add that filter? Hmmm, read it again, and I still see only that it says at the very end that the filter is located in common.php, but it doesn't say anything about making a change in some other place... </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72509 Fri, 24 Aug 2012 14:23:03 +0000 Rob Harrell 72509@https://legacy.forums.gravityhelp.com/ <p>No it won't - that's the beauty of us offering these types of hooks/filters - so you don't have to worry about things getting overwritten or modifying the plugin files directly (which would get overwritten). </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72497 Fri, 24 Aug 2012 10:43:06 +0000 CoastalData 72497@https://legacy.forums.gravityhelp.com/ <p>Awesome... I'll try that in a moment... One question, though: Will this change be overwritten with an update to the plugin? </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72417 Fri, 24 Aug 2012 01:41:49 +0000 Chris Hajer 72417@https://legacy.forums.gravityhelp.com/ <p>You can use the gform_notification_format filter to specific text rather than HTML for the notification email format: <a href="http://www.gravityhelp.com/documentation/page/Gform_notification_format" rel="nofollow">http://www.gravityhelp.com/documentation/page/Gform_notification_format</a> </p> https://legacy.forums.gravityhelp.com/topic/all_fields-text-only-submission-for-ostickets#post-72399 Thu, 23 Aug 2012 22:22:14 +0000 CoastalData 72399@https://legacy.forums.gravityhelp.com/ <p>Hello,</p> <p>I've discovered that the HTML submission created by GF gets "lost" when I use GF to send submissions to osTickets, an open source ticket/support management system. If I take the time to manually craft the response with each of the submitted fields, it works fine, but I was just wondering if there was some way to create a text-only version of the response created by the all_fields shortcode? I think osTickets just doesn't like the table-ified output... Anybody got any ideas?</p> <p>Thanks in advance!</p> <p>--Jon </p>