Data Paragraph Text missing

mofx: Are you experiencing the same issue? If so follow the instructions above. Wilco hasn't responded with his results. The issue can't be replicated locally which means it is most likely a plugin conflict or server configuration issue specific to the site experiencing this issue. So far only Wilco has reported this specific issue. Illinoisharley's issue is something entirely different.

I'm not familiar with the Feedsmith plugin. All I can say is check to see if it has settings and what those settings are before you deactivate. Then when you reactivate it, check to make sure the settings are the same.

Most plugins retain settings when you deactivate them. Although some remove the settings. Some plugin developers haven't quite figured out yet that just because you deactivate a plugin doesn't mean you are uninstalling it.

We would have to take a look at it ourselves and debug the issue. This would require a WordPress admin login and possibly FTP access. You can send us the login information via the Contact Us form on this site and we will take a look and see what is going on.

We weren't aware you guys were using hooks to manipulate fields to create a post. That is why you are getting truncated data and why we couldn't recreate it on our end because we weren't manipulating the data using the gform_post_submission hook and just doing a standard form submission.

When a field consists of a long value it gets truncated. The truncated value is stored with the main entry data, and then the long value is also stored. The truncated value is used in certain areas to speed up queries where the long value isn't necessary. This comes into play in areas such as the Entry List page if you select it as one of the columns in the column customizer. It's done under the hood for performance reasons to speed interaction up in the admin.

Gravity Forms knows to pull the correct long value when displaying field data, however you were unaware this occurs and your custom code doesn't do this which is why you are getting the truncated value.

Our lead developer will be responding to this thread additional information. The truncation is by design, you just need to know where to pull the full value from.

All,
I do agree with Bart that the full value (not the truncated one) should be passed to the hooks. I will add this to my list of items for the next release. Meanwhile, you can use the following code snippet to get the full value of the fields inside the hooks.

//reading value for field 13. Replace 13 with your actual field id
$field_value = strlen($entry[13]) >= GFORMS_MAX_FIELD_LENGTH ? self::get_field_value_long($entry["id"], 13) : $entry[13];

@hgr Yes, I had sent you an email regarding this. I was unable to reproduce the issue using your form export file on the latest version which means this is probably something specific to your site configuration. In order to look into this further I would need you to send us a WordPress admin login for this site so we could take a look.

You can send this information to carl@rocketgenius.com, Danish should be fine as I know what everything is in Gravity Forms. Thanks!

@hgr I had replied to this with the issue, which I just reverified. The issue is another plugin on your site is causing the problem. The "Newsletter" plugin is interfering somehow with how Gravity Forms works. This happens when a plugin isn't built using best practices, it shouldn't be outputting code on the Gravity Forms related admin pages but it is. You can see the issue is resolved when you deactivate the "Newsletter" plugin. We are going to see if we can determine why the conflict is happening, but it isn't something we can resolve as we are doing nothing wrong. The developers of the "Newsletter" plugin would have to change their plugin.