PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

All_fields text-only submission for osTickets...

  1. Hello,

    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?

    Thanks in advance!

    --Jon

    Posted 8 years ago on Friday August 24, 2012 | Permalink
  2. You can use the gform_notification_format filter to specific text rather than HTML for the notification email format: http://www.gravityhelp.com/documentation/page/Gform_notification_format

    Posted 8 years ago on Friday August 24, 2012 | Permalink
  3. Awesome... I'll try that in a moment... One question, though: Will this change be overwritten with an update to the plugin?

    Posted 8 years ago on Friday August 24, 2012 | Permalink
  4. 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).

    Posted 8 years ago on Friday August 24, 2012 | Permalink
  5. Are you sure about that? I followed the instructions in that link to modify common.php directly, which is one of the plugins' files.

    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...

    Posted 8 years ago on Tuesday August 28, 2012 | Permalink
  6. David Peralty

    You should never edit any of Gravity Forms' core files. Using hooks and filters should go into your theme's functions.php file.

    http://www.gravityhelp.com/documentation/page/Where_Do_I_Put_This_Code%3F

    Posted 8 years ago on Tuesday August 28, 2012 | Permalink
  7. 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?

    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.

    Posted 8 years ago on Tuesday August 28, 2012 | Permalink
  8. You should use a child theme so that updates from the theme provider do not overwrite your custom functions.php file.

    http://codex.wordpress.org/Child_Themes
    https://www.google.com/search?q=why+use+a+wordpress+child+theme
    http://wordpress.org/support/topic/why-use-a-child-theme?replies=5

    Posted 8 years ago on Wednesday August 29, 2012 | Permalink
  9. 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?

    Posted 8 years ago on Thursday August 30, 2012 | Permalink
  10. This is the accepted way of making modifications to your theme. It's not an unusual or unreasonable request.

    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.

    I see your feature request here, so I will close this topic.

    Posted 8 years ago on Friday August 31, 2012 | Permalink

This topic has been resolved and has been closed to new replies.