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.

Character limit

  1. HI Guys,

    Any workaround for this? I hoped updating to the latest version would solve this. I am running Wp 3.1.1 and Thesis 1.8.

    careerjourney.co.uk

    This is the structure of table wp_rg_lead_detail:
    *field name - value type*

    id - bigint(20)
    lead_id - int(10)
    form_id - mediumint(8)
    field_number - float
    value - varchar(200)

    The field named "value" has a limit of 200 chars.

    Posted 13 years ago on Friday April 22, 2011 | Permalink
  2. There is no character limit in Gravity Forms. Are you experiencing a character limit? If so you are experiencing a theme or plugin conflict.

    The database table you are inspecting does indeed limit the value of 200 characters, but that is because that isn't the full lead data. That is a lookup table. There is another table called wp_rg_lead_detail_loing where the full value is stored.

    If your text content is being truncated to 200 characters than you have another plugin or theme that is causing a code conflict and causing this issue to occur. You would have to test for plugin and theme conflicts.

    To test for a theme conflict:
    - Activate the default Twenty Ten theme
    - Check to see if the issue occurs

    To test for a plugin conflict:
    - Deactivate ALL plugins
    - Activate Gravity Forms
    - Check to see if the issue occurs

    If it does not, then one of your plugins is causing a with Gravity Forms. To narrow it down follow the steps below:

    - Activate each plugin one by one
    - Check to see if the issue occurs after each one

    A way to speed this process up is instead of activating them one by one, activate them in groups... say 5 at a time... and then when you encounter a group that causes the issue to occur, deactivate that 5 and then activate them one by one and test after each one.

    We can't prevent themes or plugins from causing conflicts, it's just a fact of life with WordPress themes/plugins, especially when running large numbers of them from a wide variety of sources. This can happen when the plugin or theme doesn't isolate when and where it executes code.

    Let me know how it goes.

    Posted 13 years ago on Friday April 22, 2011 | Permalink
  3. Thanks Carl, I get this back to my developer and I am sure he gets it sorted.

    Cheers,
    Nik

    Posted 13 years ago on Friday April 22, 2011 | Permalink
  4. Will the plugin cause errors if we change the data type for this field from "varchar(200)" to
    "text", "longtext" or "blob" thus extending its capacity to millions of
    characters?

    If that's not possible how do we best link the tables?

    Posted 13 years ago on Friday April 22, 2011 | Permalink
  5. You shouldn't need to change any tables and Gravity Forms knows to use all of it's tables and the data structure. So you shouldn't have to change anything. Gravity Forms knows only the first 200 characters are stored in the lookup table, it only uses that for certain functionality such as the entry list page. For the detail page, etc. it knows to go to the detail table for the full content.

    What exactly are you trying to do?

    Posted 13 years ago on Friday April 22, 2011 | Permalink
  6. Hi Carl,

    I am letting customer write about their life (Resumes etc) and I am reporting on that (client gets a word document emailed), when I run the report from the wp_rg_lead_detail table the longer text get's cut-off. We are using a php script to call back the data. So somehow we need to have the query look at which entries are longer then 200 characters and then go and have a look in the other table.

    Any suggestions on what the best way forward is?

    Changing the field type is obviously the easiest but will it break the plugin?

    Posted 13 years ago on Friday April 22, 2011 | Permalink
  7. You have to also query the data from the wp_rg_lead_detail_long table. So you need to get the data from this table also. The data is stored in multiple tables with the long values stored in wp_rg_lead_detail_long. They aren't all stored in the primary table for performance reasons, it makes the Entry List page perform faster for lookups, etc.

    Posted 13 years ago on Friday April 22, 2011 | Permalink