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.

Cannot add Paragraph Text to Form

  1. I'm experiencing an issue when adding a "Paragraph Text" style element using GravityForms Other field element types seem to work fine.

    I have an existing form here:

    Symptoms: I click the "Paragraph Text" button and visually nothing happens.

    When I press the button, my developer tools show the following javascript exception:

    Uncaught SyntaxError: Unexpected token < in file tw-sack.js:1

    The details of the exception are:

    runResponse tw-sack.js:1
    Posted 9 years ago on Thursday December 13, 2012 | Permalink
  2. @illinoisharley This is still an issue that we are struggling with. Any thoughts on how this can be fixed. Everything on the site works except for this one feature which raises a javascript error. To me that would indicate a bug in gravity forms.

    Have you been able to reproduce?

    Posted 9 years ago on Monday December 17, 2012 | Permalink
  3. I cannot reproduce this problem. Does this occur with the default twenty ten or twenty eleven theme? How about with all other plugins deactivated? Have you already followed these steps

    Can you post your complete functions.php to or please?

    Posted 9 years ago on Monday December 17, 2012 | Permalink
  4. Also, this user had an identical issue, and found it was a PHP memory error.

    Can you see how much RAM is available to both PHP and WordPress?

    Posted 9 years ago on Tuesday December 18, 2012 | Permalink
  5. @illinoisharley This morning I followed all of the steps in I received the error while using the Twenty Ten theme, so it's not a theme level conflict. I then de-activated ALL plugins (including gravity forms). I re-activated gravity forms so that it was the ONLY active plugin. I did this while the Twenty Ten theme was enabled. I still received the javascript exception on tw-sack.js in that environment. Therefore this is not a theme level or plugin level conflict.

    I have asked the hosting environment for the RAM available to both PHP and WordPress, I'll post that back here when I hear back from them. I can't see why an out-of-RAM error would occur on a vanilla WordPress site, with no plugins, and the stock Twenty Ten theme. Furthermore, as a javascript developer I have never seen a javascript exception caused by the server running out of RAM. The Javascript files are served to the client properly with no 404 exceptions occurring, and the javascript exception occurs on the client's machine, so I'm not sure how RAM could play a role in this. I'm open to it being the cause, I just don't understand how it could be.

    What other ideas do you have that I should look into because I don't believe RAM is the root cause of this javascript exception.

    Thanks in advance for your thoughts on this.

    Posted 9 years ago on Friday January 4, 2013 | Permalink
  6. @illinoisharley The RAM available to PHP and wordpress is 512M. Because of where it is hosted It cannot be changed, and should be sufficient for any vanilla site. I don't believe this has anything to do with the javascript error.

    Posted 9 years ago on Friday January 4, 2013 | Permalink
  7. David Peralty

    So just to confirm, in the form builder, you can add other fields, but when you try to add the paragraph field, you get that JS error?

    Posted 9 years ago on Friday January 4, 2013 | Permalink
  8. Because of the way WP Engine works, I know you can't upgrade WordPress as they will handle that for you.

    I did see two versions of jQuery in the public-facing page. I'm not sure why that would be, but if that is happening in the admin, that could create a problem.

    <script type="text/javascript" src=""></script>
    <script type='text/javascript' src=''></script>

    Other than that, without logging in, I'm not sure what the problem can be. I have not heard of any other people having this issue on WP Engine. If you would like me to take a look, please email a WordPress administrator login to and I will take a look.

    Thank you.

    Posted 9 years ago on Friday January 4, 2013 | Permalink