698 comments found.
Hi,
I am wondering I can get a refund for my purchase? I found a solution that does not require the plugin. Your plugin is good and does what it says but I just don’t need it as I thought I would. Sorry for the trouble.
Thanks, Jamie
Hello
No trouble!
You may request a refund at any time through your Envato account under your purchases. Refunds are not issued by author support contact. Once a refund has been issued the plug-in will become deactivated and will no longer function to view your encrypted data , so be sure to decrypt any data you want to have viewable past deactivation.
Hi, I need of support related to plugin configuration/installation as I have configured it as per tutorial mentioned in docs/videos guide, but its still not working.
Hello
We can check the overall setup, but can you explain the specific functionality you are trying to set up for us to be able to assist beyond proper basic setup and meeting system requirements.
initially we are required basic setup as I did and once I submit new entry then all values are still not encrypted. How I can share my website credentials privately.
Hello
It sounds like the plug-in is working properly, but you may be missing how the plug-in works.
Did you carefully complete ALL of the numbered steps in order in the setup and operation instructions, including the encryption testing and verification?
if your user has view permissions to see the encrypted data (from either not setting any view restrictions, or giving yourself or your role view permissions). It is not going to show up encrypted for you when you are logged in. It is going to be decrypted for you automatically, so you would have to use encryption verification to see it is encrypted in the database, or one of the other encryption verification methods in the instructions. This is all covered in the setup instructions
The first thing to check if the data was actually not being encrypted, is that setup was done properly. You should go through ALL setup numbered instructions in order and be sure you have set it up properly. The system check to meet all system requirements along with the encryption testing and verification would be of main concern, but as verified.. everything is met for system requirements and the encryption test is working, so the encryption is functioning, and the forms/fields just need to be properly set up as you intend for your needs functionality.
Assuming your form fields are already properly set up for encryption for the specific functionality you want with the plugin, and you are running test entries on a test form, you can continue the setup instructions from #14. VERIFYING THE DATA IS ENCRYPTED. (Using the login credentials you provided we have already checked your test form data with encryption verification mode and it IS properly encrypted), but this points to a key miss on completing the setup and operation instructions to understand how the plugin works and how to use it.
You should go over the FULL setup and operation instructions again to understand how the plugin works and how to use it etc. there are some key points at the beginning covering HOW THE PLUGIN WORKS, and other key points throughout on specific setup and/or functionality
Hope this helps 
Ok, Please can you tell me little about the key points for working with gravity PDF and querystring. As in gravity PDF its only showing encryption for all users.
Hello
There is a section on using with gravity PDF detailed in the plug-in instructions including a basic decrypted pdf template
Yes, I have already read that and after that I contact to your about it. It was not working as we was required.
Hello
What are you looking to set up? Are you looking to show the fields decrypted in the .pdf? You can use the provided decrypted pdf template or modify it to your liking to show the data decrypted in the .pdf. Modifying the templates is in the realm of the gravity pdf plugin so you would refer to that plugins guide on that. In our instructions on gravity pdf there is a direct link to gravity pdf’s template creation/modification instructions for customization of our template or creating your own.
It is unclear what you are asking for direction on doing in regard to the use of query strings, but both our plugins decrypted and encrypted merge tags are available for use in page redirects which make use of query strings, so you can pass forward encrypted or decrypted information to other gravity forms. Our merge tags are covered in our setup instructions, and query string composition is covered in the core Gravity Forms documentation
You wrote”It was not working as we was required.” Can you can describe exactly how you are looking to have things work in order that we can assist?
Hi,
I am trying to pass data from one form to another using an html link. For example https://mysite.com/?passon=emailaddress
I want the email address to be encrypted. I can pass the data no problem but now once I encrypted the field it only passes the Encrypted Field message. I tried putting the merge tag for description on the field on the second form but it just show the merge tag. Any help would be great. I don’t want people being able to see the email address in the url and its the easiest way to set up the forms so the person who’s email address thats being passed gets a notification email. Any help would be great.
Hello
If you already have this email address from the first form you can use an encrypted merge tag to pass the data as an encrypted string in the URL query string.
You can set the field you are passing data to in the second form to encrypted as well and it should not double encrypt the data as it checks if it’s already encrypted.
Then use a decrypted merge tag for the email address in the “send to” email field for the notification.
You will need to use the decrypted merge tags anywhere you need encrypted data to be readable by merge tag.
Setting up the encrypted and decrypted merge tags is covered extensively along with images and video tutorial in the plugin instructions.
Hope this helps
Thanks for your help.
Hello,
I’m looking to use this along with Gravity Flow, Gravity Perks, Gravity View …. and so on.
But the most important is that the encryption doesn’t hinder my Gravity Flow processes. For example, I need to store an API public and secret key in some fields of the entries of a form. For example, I need to be able to use these keys in a Gravity Flow webhook step. Will that be possible or complicated?
Thanks Michael
Hello
You can decide which specific fields are encrypted per individual form, so you can always simply not use encryption on any fields that you need to be passing/processing any certain custom data on,
or pending your flow you may not need to consider it. The plugins you mention also include hooks you could use to add small snippets of code to run our developer decryption function on for any data you need to decrypt before processing by the system when a user with access permissions isn’t performing the actions (which would ago decrypt the data being pulled/processed)
With so many possible scenarios with those plugins it’s hard to say whether encryption would ever be an issue, but we find that most users either use some custom code to decrypt when needed or use other non encrypted fields to pass custom data
Hello! Can you confirm the license fee for Gravity Forms Encryption plugin (single license) is $42 one time fee (not $42 annually)?
Hello
It is currently a lifetime (one time) fee. You can get all updates through your envato account or use the free Envato Market plugin for auto updates
Also, can this plugin be used for some fields and not others within a form? Or for some forms and not others? Or does it automatically apply to all of your Gravity forms?
Hello
All encryption options are per individual field in each form. Check the full plugin description for a list of supported field types and encryption options
Hi – I am considering purchasing this plug-in, but I wanted to be sure it works in the way I expect first.
We want to be able to complete a Gravity Form that’s data entries transfer to our EHR via a webhook. Some of this info would be PHI. If we purchase this plug-in will we be able to do this in a HIPAA-secure manner or is the data only available somewhere else?
Thank you,
David
Hello
Mainly the plug-in secures the data stored in your own server for access from your own server/WP backend and front end. So regardless of your transfer of data you would want the plugin to secure the data while it is on your server/database. This is a critical HIPPA compliant component.
From there, the gravity forms webhooks use open data via url query strings (passing in field data by merge tag) and although you can encrypt that data your EHR would then have no idea how to decrypt the data to make use of it unless you write some custom script on that end to do it.However , if you are passing the open data via an https authenticated webhook. Your data is technically already secure transferred to your EHR. For reference this is the same security of the data in transfer as when the client computer initially fills out the form over https. The keystroke data is sent from browser to server via https etc.
Typically speaking, webhooks overall are not as secure as use of an API where your EHR would pull data from gravity forms using an authenticated user with decryption access. Gravity forms does have a web API and this is the recommendation if your EHR can do it. But again, user authenticated https data transfer is considered secure on the front end. You could chat with a HIPPA compliance specialist as to if it would be considered adequate for a secondary transfer.
Hi, I am getting a new error on form submission
Fatal error: Uncaught Error: substr(): Argument #1 ($string) must be of type string, array given in /var/www/wp-content/plugins/gravity-forms-encrypted-fields/gfef.php
from Chatgpt
The error message you received points to a problem in the code where a function substr() is being called incorrectly. Here’s a breakdown of the error:
Fatal error: A serious error that causes the script to stop executing.
Uncaught Error: The error wasn’t caught or handled by any error-handling mechanism, so it stopped the script.
substr() function: This is a PHP function that is used to extract a part of a string. It takes at least two arguments:
The string from which you want to extract a part. The starting position of the substring. Argument #1 ($string) must be of type string, array given: This means that the first argument passed to substr() is an array, but the function expects a string.
/var/www/wp-content/plugins/gravity-forms-encrypted-fields/gfef.php on line 864: This indicates that the issue occurred in the gfef.php file in the gravity-forms-encrypted-fields plugin on line 864.
How to fix it: Check the code at line 864: Look at the gfef.php file around line 864, and find the line where the substr() function is being called.
Ensure the first argument is a string: Before calling substr(), make sure the variable passed as the first argument is a string and not an array. You can add a check like this:
php Copy code if (is_string($yourVariable)) { $substring = substr($yourVariable, $startPosition); } Debug the source of the array: If an array is being passed instead of a string, figure out why the array is being passed and correct the source of that data.
This error could be related to how form data is being processed in the gravity-forms-encrypted-fields plugin, so you may also want to verify the form input handling if it’s receiving data in an unexpected format (e.g., an array instead of a string).
Hello
What version of the plugin are you running?
Hello,
We have the encrypted fields plugin installed and it is working fine apart from one field still showing encrypted in the back end (i.e. when checking entries section of the gravity form). Is there some common problem/fixes we can try. Thanks
Hello
What tour of field is it? What are the encryption settings for that specific field?
data type is single line of text and encryption setting is ‘Encrypt Field Value’ – the same as all other fields
Are you setting access on individual fields or globally from the plug-in settings page?
individually, would you recommend setting global?
If it’s just one or two people or a role that need access to every single encrypted field, then yes it’s much easier to set permissions globally.
I would check the permissions set for that singular field and make sure it is set correctly. You could copy in what is in another working field. -optionally , you could just put the usernames/role desired to have access to all encrypted fields in the global user access list, and put “lockdown” in the user lockout list.
i just saved the form id to the “Global Form Encryption Switch” area and saved, I checked the User/Role View Permission area of the field and it’s empty (like all other fields), i am logged in as an admin and still can’t see it
1. Is this pre-existing data, or new data submitted after setting up the plugin?
2. Is this one singular field from one single entry , or all entries for the same field?
3. Is it giving you the encrypted restricted text or the hidden restricted text?
new data after plugin setup, only one field from the whole form is still showing encrypted (can see all others fine), it shows something like “GFENCRYPT: 7EDBB3EB8…”(with more numbers and letters)
Do you have encryption verification mode turned on in the settings ( at top under encryption verification and testing)
no it’s not turned on
What other plugins are affecting/processing this single line text field?
Or other custom code..
have just noticed that it is the only encrypted value being stored fully in caps so will look into that
Ok, essentially you should NEVER see the encryption strings that are actually in the database. You should either see the decrypted data or the encrypted or hidden display text. If you are seeing an encryption string when you should be seeing decrypted data it is almost always because your actual data has become that encrypted string. This generally only ever happens when a plugin or code pulls the data from the DB but does not do it through the GFAPI where it does not get the decrypted data as entered in the form but pulls it still encrypted since it didn’t pass through the gravity forms api and thus also our plug-in for decryption. Then when the field data is re-saved it of course saves the raw encrypted string instead of the decrypted data it should be. If it hands it to our plug-in our plug-in encrypts the already encrypted string.
It is rare to see it but custom code or plugins not pulling gravity forms data properly can have this effect. By default our plugin does not use all caps so something must be affecting this field. Of course can work it out before taking the form live etc.
Hopefully this helps
yep found some custom code that was converting values to uppercase, something like “add_filter( ‘gform_save_field_value_2_50’, ‘make_uppercase’)” so just commented it out
Just tested and that was the problem, thanks for everything
Sounds good.
If that field needs to be uppercase you could probably still run that custom filter but set the priority much earlier. It’s running after our encryption runs so it’s making the encrypted strings all uppercase which of course corrupts the encryption. If it runs before it to uppercase the raw input data then the uppercase data would just be encrypted. Or encryption runs extremely late in priority to strenuous to always run last so I assume the filters priority is wildly long like 999999999999999 but maybe try changing it to 999 and it should likely be fine
I’ve got the following question regarding the functionality of the plugin, we’ve bought the plugin, but noticed from the provided documentation while setting it up, that the plugin encrypts the data sent via email, which is good of course. But that the data thats used by the Gravity Forms WEB API is already encrypted via the SSL of the website, correct?
So currently we’re having a third-party using the gravity forms web API and want to have the data secured/encrypted in that layer. So they could get the data securely on their side. However if the data is already securely transferred through the WEB API through the SSL. Do we really need the plugin for any encryption? As we most likely then do not use it to its intended purpose and we already provide an enough secure data transfer to the third-party via the SSL. Do let me know.
Thanks in advance.
With kind regards.
Hello
The web API protects the data during the transfer if you are using SSL on your site and it also cannot be accessed via standard http. You do not need the plugin to secure this method over using https. But only As far as the actual transfer is concerned. The api over ssl is like an armored car transporting your cash from the bank to another bank.
The plugin main function is that it encrypts the data at rest in your database so it is secure to begin with as it sits waiting to be accessed in any manner. It also gives security access controls to limit who has authorization to access that store encrypted data. The encryption is like actually locking your vault in your bank instead of the door sitting wide open and no banking protocol as to what employees can walk in and out of the vault to begin with as it waits for the armored car.
Hope this helps
I need a refund, product didn’t comply with HIPAA compliance
Hello
I can assure you that our plug-in fully meets/exceeds the specific portions of HIPPA compliance that it directly addresses. (Encryption of the data at rest + secure access control to the at rest data). If you are not meeting full HIPPA compliance it would be based on your other protocols/server access/standards/practices/etc. because HIPPA is a holistic standard and not based solely on encryption and data access control. You should speak with a compliance officer to bring the other areas up to acceptance standards.
However, may request a refund at any time through your ENVATO account. Your plug-in will no longer retain functionality once the refund is issued and will be deactivated. You may want to decrypt any encrypted data before the refund is issued.I have a question about the different types of encryption. When I select, “Hide Field Value” AND “Encrypt After Submission is Processed,” it automatically changes to be “Encrypt Field Value.” Is this because selecting those two is the same as “Encrypt Field Value” or is this an error that we need to fix? Here is a video showing the issue we are having https://drive.google.com/file/d/1YSF7ZcW8W06WHWVJcJwD2ganhkUEJSkM/view?usp=sharing.
Hello
Those two options are directly conflicting. You cannot both only hide the field value and use actual encryption the same time. You should take the time to follow the complete setup and operation instructions in the plugin settings page to learn how the plugin and its options work, and how to set the plugin up for your environment and desired results.
When you select to encrypt after the submission is processed it requires you to be using encryption. The option to do it after the submission is processed is only a selection of when the encryption is performed.
The “hide field value” option is an option to merely hide the fields displayed value on the back and front end to users without view permissions ..without actually using encryption on the store value.
Hope this helps
how do I deactivate my older sites? They don’t exist anymore. Is there another way to deactivate?
https://boyertruckmonth.com https://mydriveupgrade.comIt seems that the second URL still resolves, so it does exist. If you can still log in you can deactivate the plugin from there. The first url does not resolve and when you go to activate on a new site it will give you the option of removing the unresolved url activation.
If you need help deactivating the second site you can click out user name and use the author contact form to send us a message with your purchase code to deactivate it. DO NOT list your purchase code in a public comment
Hello, I have two websites that use this plugin and neither are receiving email notifications from the forms (gravity forms) that have encrypted fields. All other gravity forms on the sites work correctly. It looks like I have the latest version. Do you have a fix for this?
Hello
Without any further information to go on than they are not receiving notification emails, I would assume that you are sending the notifications to an encrypted email address field.
If this is the case please refer to the plugin setup and operation instructions. Specifically step 12 , which covers in detail with images / video etc, using a decrypted merge tag to send notifications to an email field that is encrypted.
If another person set up the plugin for you, you may want to review the rest of the setup instructions as well to be sure no other items were skipped or missed.
I am getting this error code
Fatal error: Unparenthesized `a ? b : c ? d : e` is not supported. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in /home/spagir5/academicfundingcorp.com/wp-content/plugins/gravity-forms-encrypted-fields/gravity-forms-encrypted-fields.php on line 2503
What can I do to fix this problem I am not able to activate the plug in because of this error
Hello
Is this the latest plug-in version? What php and WORDPRESS version?
plug in version Version 4.4.7 php version PHP 8.1 wordpress version 6.6.1
Please update to the latest plug-in version Version 6.2.2
You can be notified of plug-in updates through selecting to be emailed about updates in the plugin down field section here on code canyon or using the envato market plugin
Thank You for your quick response. Do you know when the update will be released
It has already been out for a while now.
The version you are trying to install 4.4.7 is years old. Please check your envato purchases and download the latest version.
Hi,
I am interested in your plugin and have a few questions:
How can I encrypt existing entries? Is there an option within the plugin to do this, or would it require a database query?
Once a field is encrypted, will I still be able to search data using GravityView?
Is the plugin compatible with GravityView, Gravity Wiz, and the miniOrange SMS Verification plugin?
Thank you!
Hello There is batch encryption for existing entries.
Encrypted field value Search is supported in gravity forms native entries list view. Some compatibility may exist with gravity view as well but is not explicitly supported. You can always search bar on non encrypted values
The plug-in plays nice in general with the others you mentioned but full compatibilitty with all those plugins possible features and extensions is not guaranteed.
Feel free to try the plugin in your dev site and simply request a refund of it does not meet your needs within a reasonable timeframe. The plugin will be deactivated upon refund.
My web host sent me the following:
I wanted to reach out to you as we were reviewing your site and noticed, we could do more to keep the SSN of site user’s safe. We want to make sure we’re protecting the user’s data so someone can’t log into the admin and pull someone’s SSN.
With that said, can you please contact the plugin provider, PluginOwl, and ask them to change the URL to the production site?
https://www.rollstonebank.com/wp-admin/options-general.php?page=gravity-forms-encrypted-fieldsCan you help me with this?
Hello
The user/role based permissions would disallow someone from simply logging into WP admin to view encrypted information as well as gravity forms permissions for viewing entries. You can also password protect the plugin settings page to prevent high level admins from changing permissions and/or use asynch mode which requires a logged in user with permissions and an additional password to log into synch mode to view any encrypted data.
On the side with “changing the URL” we cannot change anything with your web host. Are you referring to changing your plugin license url? you can deactivate it from the old site and activate on the new one. Or if the old url does not exist at all (cannot be resolved as an actual reachable address) you can disable it when you go to activate the new site if both license slots are full.
Or if the url is still reachable and just was not deactivated before switching sites you can send us an email using our contact form (click our user name) and fill out the author contract form including your purchase code and the EXACT url to deactivate . You can activate on new site after license is clear. Do not list your purchase code here publicly. Only on the author contact form
The web host said: “the old sites that are registered are not accessible so we need them to remove both sites so we can register the correct production and staging links.”
If that is something I need to do, please tell me how to do so. Thank you.
if the old url does not exist at all, not just not manageable but the domain is not on the internet (cannot be resolved as an actual reachable address) you can disable it when you go to activate on the new site if both license slots are full.
Or if the url is still reachable and just was not deactivated before switching sites you can send us an email using our contact form (click our user name) and fill out the author contract form including your purchase code and the EXACT url to deactivate . You can activate on new site after license is clear. Do not list your purchase code here publicly. Only on the author contact form
I just emailed the purchase key and URLs to be deactivated. Thank you.
Complete
Thank you for taking care of it so quickly!
One more thing … Can you remove this?
https://www.rollstonebank.com/wp-admin/options-general.php?page=gravity-forms-encrypted-fieldsMy web host thinks that’s what’s causing the issue. (Issue being we can’t see fields we need even when we’re logged in to WordPress.)
? There’s no “removing” that unless you uninstall the plugin.
Did you transfer / clone your site to a new url?
If you did that you need to check your encryption keys. The auto key will not be the same between 2 different Wordpress sites unless you made a EXACT complete clone of the site including the old sites Wordpress core files.
If this is the case Check your encryption key and change it to what it it was on the old site. It will be a custom key instead of auto.
We recommended you then manually decrypt all your form data and then change the key to the new auto key and manually re-encrypt it. That way you can use the auto key and don’t have to check it after every plugin update like you would if you stick with using the custom key
I shared that with the web host. Thank you.
My client is running your plugin and we continually get this error in the log. We are using version 6.2.2 of your plugin.
PHP Fatal error: Uncaught Error: Call to undefined function do_settings_sections() in /public_html/wp-content/plugins/gravity-forms-encrypted-fields/gfef.php:3489
I searched the comments and see this comes up a lot, but have not seen a solution.
Hello
I see your site is having issues running the “do_settings_sections()” function. All references in the comments to that error you are referring to are from over 3 years ago and were resolved/ mainly do to actions taken on WP environment setup outside of our plugin. This function is actually a core Wordpress function which our plugin call as part of the WordPress plugin settings page API. This is likely why you have not seen any resolution on it, because it does not stem from our plugin trying to load, but rather from something else preventing our plugin from loading its settings page using the WP settings API which is the standard for loading plugin settings pages etc.
https://developer.wordpress.org/reference/functions/do_settings_sections/We may be able to help see why WP isn’t recognizing one of its core functions, but the only related information we have on it is that the error may be resulting from a server timeout and potentially a conflict with the YOAST SEO plugin. if you are running that plugin try disabling it to see results. can also try increasing server timeouts if they are strict. However the error mainly seems to result from another plugin error or server timeout. This can result in our plugin receiving an error while trying to call a base Wordpress function because Wordpress isn’t fully able to load the API to utilize. The first things to try are disabling other plugins in your test environment and testing ours. and then seeing which one is causing conflict by turning them back on one at a time and continuing to test after each one is turned on.
It could help to know the following as well.
What version of WP is your client running?
What version of PHP?
What version of Gravity Forms?
Hi, thank you for this info. This gives me a good place to start tracking down the conflict. We are using the most recent versions of WP and GF. PHP 8.1.27. The fatal error has been present in the log for over a year (through different versions of WP and PHP), but without noticeable affect on the frontend, so we’ve just let it go. There are no other errors or woocommerce orderes happening at the same timestamp, so I don’t know what the trigger is. We do have Yoast installed. Also have Woocommerce Gravity Forms Product-Addons. I’ll start there. Thank you!
Hi, We’re using Encrypted Fields alongside the Legal Signing plugin which turns a completed GF application into a legally signed document saved as a pdf. The Encrypted Fields is used to ensure security as we’re asking for a SSN from a company owner looking for services in the application.
The issue we’re facing is the Legal Signing is a multi-step process that needs to verify an email address prior to the signing can be completed. An email token is sent upon submission, but when Encrypted Fields is enabled, the entry data is updated for some reason so the token doesn’t match with what was just submitted.
Turning off Encrypted Fields, the verification works without an issue, but once enabled, it fails every time.
I’m letting the Legal Signing plugin devs understand the issue, but they’re not going to motivated to help as a vanilla setup works without any issues. Our current setup has been working for the last few months but in the last 2 weeks, it’s failing.
Any insight you have would be helpful. Thanks!
Hello
Is the email field also being encrypted?
No, just the SSN. The “Encrypt after submission is processed” checkmark is on. I’m unsure if this should be turned on but I do see it can affect notifications.
Are you recording any error that you can report from PHP or is there any error message given onscreen by legal signing or anywhere on the process?
This is the error they were seeing in the GF log while testing:
2024-07-12 17:28:18.867933 – ERROR—> ForGravity\Legal_Signing\Utils\Token::action_after_setup_theme(): Entry hash in the session data does not match entry #91.
”.... when the entry with the workflow is viewed later on, we run a check to make sure the current entry hash for the entry matches what we have saved as the entry hash from the last time the signing workflow was updated in the database, aka we make sure the entry hasn’t been changed by anything other than us since we last touched it…”
They didn’t mention what could and couldn’t be changed so it seems that the delayed encryption may be part of the problem.
Since we’re saving SSN data, should I a) turn off the delayed encryption, or b) rely solely on the SSL certificate to do the heavy lifting for the encryption and not use Encrypted Fields?
1. Yes it seems you should try to turn the delayed encryption off. Unless you actually need that for some other delayed processing where you cannot use a decrypted merge tag to pass the SSN decrypted to any feed or add-on that processes the SSN on submission. ( This would NOT include notification emails or gravity pdf creation.. you can use the decrypted merge tags for that functionality)
The delayed encryption functionality delays encryption until after the entry has been processed. Presumably they are creating a hash of it during that processing .. likely at the end. By turning it off, The SSN entry data may possibly then be encrypted before the entry is hashed vs being encrypted afterwards which changes the entry making the hashes not match.
2. I think you may have some confusion about what SSL does vs our encryption plugin. SSL only encrypts the data in transit between the client machine and your server where it is then auto decrypted and used as readable data after secure transmission to the server. Our plugin then encrypts it for storage on your servers database. You should use both.
Hi,
We are having this fatal error after recent update:
PHP Fatal error: Uncaught TypeError: substr(): Argument #1 ($string) must be of type string, array given in /wp-content/plugins/gravity-forms-encrypted-fields/gfef.php:235
Is there a quick fix for it?
Thanks, rrota
Hello
Are you with keeping your plug-in updated? The latest is Version 6.2.2
Please update and let us know if issue is occurring still.
Hello,
Yes we have already the 6.2.2 version installed and in long forms with various fields we get this fatal error!
Are you running any custom code using our developer decrypt functions or using any special field or form types that may not be supported. (IE: nested forms , or special or custom field extensions or types)?
