703 comments found.
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)?
Hi, I accidentally purchased the plugin twice – I would like to keep the plugin with 12 month support.
Can you refund the other purchase for me?
Hello
You can request a refund through your envato account. The plug-in functionality will be disabled after refund is issued.
Hello,
As per your license management we are having issues with our website license activation.
We are seeing you don’t have any interface to manage the sites of the licenses.
We build a website at the production environment and after finalizing it we pushed it to live site. Now when we tried to activate the license – http://freshy.cc/zgQqh000 its still showing that dev site is activated where the dev domain is replaced by the live domain. And we can’t go back to the dev site – https://rouserpcinc.freshy.dev to deregister the license.
Can you please remove the license from here https://rouserpcinc.freshy.dev so that we can activate the license on the live site – https://rouserpcinc.org.
Please let us know urgent.
Thanks!
Hello
Click our user name and send an email using the author contract form and include your plugin purchase code there and the EXACT url to deregister.
DO NOT respond to this comment and list the purchase code publicly.
The licensing activation does allow for one dev site AND one live site to be active at the same time. Do you already have more than one site active?
Got it! I removed the screenshot and emailed through author. The code was used 2 website where one of them is the dev production site. and the production site is now live. But we can’t delete that production site license since the production one is basically pushed to live now 
Hope you understand.
Thanks!
We have deactivated the dev site, and an activation is ready to use. However, note that this license is already active on a production website.
Your license through envato dues NOT allow installation on 2 live sites. It allows for a single live end product production website only. We make concessions for a second activation only for dev purposes of the same live site.
You should purchase another copy to run which would allow a dev site for each. If these are web clients, they should also be privy to their own discreet purchase code/licenses.
Hope this helps.
Hello how can I decrypt a field value with php while using some gravity forms core hook and actions?
Hello
In the plug-in setup and use instructions at the very bottom you will find a link to our available developer functions with documentation for each function. You can use the gfef_developer_decrypt($entry_id, $field_id, $format) function within or outside of any gravity forms hook or action as long as you have the necessary variables for the function (entry id and field id) as it uses the GFAPI for retrieving the data already.
There are samples in the documentation.
As a note, we do not assist with your custom programming.
Hello, thanks for your reply! This does not seem to work for me. For example, using the gform_after_submission gravity form action, the code $first_name = rgar($entry, $field->id . ’.3’); returns the first name properly if the field is not marked as encrypted, but if encrypted from the field settings, advanced section, the code $first_name = gfef_developer_decrypt($entry, $field->id . ’.3’); returns an empty string. What I am missing here?
Hello
Are you using asynch mode?
If so, as documented you cannot access the data without logging in to asynch mode.
Hello, thanks again! How can I find that out? The only thing I see about asynch mode is that I may not need to add an encryption pass. I have already set up an encryption pass, fyi.
Hello
View the plug-in settings page and look at what “encryption type” option is set. Asynch is either turned on or not turned on.
Encryption Type: YES OpenSSL ON Encryption Turned On: YES ENCRYPTION ON
Merge Tag Filter On: YES MERGE TAG FILTER ON
Hello
Scroll down to the option that is named “encryption type” and check if asynch mode is on
No it is not, should I click “ALLOW ASYNCH”?
Sorry, why would you select it?
We are checking to see if it is turned on which would prevent you from using programatic access to decrypted field values because asynch decryption requires login authentication.
I have not turned it on! I only see OpenSSL (Strongly Recommended) ticked. Below, the Async / Strict Access Mode – Read Option Instructions is not ticked!
Hello
That is good. it should not be selected. I see now looking at your code that it is likely not working because you are not using the correct variable parameters as requested by the function.
our function is as follows:
gfef_developer_decrypt($entry_id, $field_id, $format)
note that as listed in the documentation the first parameter is the entry ID and not the complete entry object. This can be accessed from your entry object like this: $entry[‘id’]
Your function should be as follows:
gfef_developer_decrypt($entry[‘id’], $field->id . ’.3’);
Hope this helps
You rock! That did the trick for me! Sorry I missed that and ruined your time! Btw, and when you have some time, can you also explain why I am getting an empty string for those same fields for which I am using the decrypt merge tags per your instructions on a custom notification I have set up from the gravity forms settings which is activated when form is saved using the save and continue functionality? I cannot make them work. Just an idea of what I should check at. I have already decrypted the tags using the value 5:1.3, 5:1.6 and also found and placed the new generated tags on the notification body content. However, they do not work. I guess if this cannot be fixed, I can run a custom wp_mail() function and use the above solution you gave using the dev function to decrypt again the fields.
The save and continue entry is encrypted as a whole to comply with how gravity forms stores it because it is a single json object. It is not done as usual per field.
You can check the simple encryption for save and continue functionality in our plugin (search save and continue) and use it to decrypt the entry object retrieved first, then if able to access the merge tag functionality at that point via gravity forms normal operations you can access as needed. Only need to decrypt the json object first.
hi there, is there an option to set time/age of entries/fields/signatures when they should be Deleted instead of immediately being deleted? Eg. Delete X field entry data after 2 weeks of submission? And how can the previously submitted data be Deleted instead of only data submitted after option to Delete was enabled in plugin settings (the first question/option, if available, would actually address this too). thank you.
Hello
There is no time delay option for deletion of entries or specific field data. It is only an option to be deleted immediately after the submission is processed.
Hello, I would like to purchase your plugin but I’m curious if it will be able to pass entries to Zapier if they are encrypted? We have our entries going to Zapier right now that are processed and then sent to a CRM.
Hello
You can select to process feeds and add ons before encrypting . This passes normal data to all your plugins needing it belle the data of encrypted at rest after submission
Hello, I want to purchase this plugin but first I would like to test it to see if it does meet all our requirements. Is there a way we can try it first in a dev environment before purchasing? We are interested in the encryption of Gravity Forms confirmation email, if that data could be encrypted.
Thank you.
Hello
As in the plug-in description, Our plugin is for encryption of the data at rest and does not encrypt the notification emails. You can do this simply by sending them over TLS/SSL using an SMTP service to send your Wordpress emails. This is implicit encryption that all emails use over TLS like Gmail etc.
If you want explicit encryption that requires further action from the user to decrypt the email for reading please check out a plugin like the PGP mail
You CAN use or plugin to send encrypted strings in the email, but you would need to build a decryption service on the v v other end for client decryption. You may want to consider just sending out the entry links in the email and enforcing website login to view the entries. Then you can control which specific logins have access to specific field data with our plugins access controls. Giving those users the ability to only view entries allows them to authorize first by logging in to view and can then be further restricted to specific data view ability of encrypted data with our plugin.
Plugins have no trial from envato. You can purchase and request a refund from your envato account if the plugin does not meet your needs. Once the refund is issued the plugin activation will cease to function.
can i use the plug-in for multiple domains?
Hello
No. the licensing from envato allows one single domain install per license/purchase code (our license manager allows 1 additional install on a dev/test domain for that same live site)
I need to know if there’s a way for the “Print Entry” to show the fields when logged in. We have the userrole set up properly so that only specific persons with that role can view the information but when you go to “Print Entry”- the fields are hidden?
Hello
The print entry permissions and view are the same as normal entry viewing. Normally anyone with view permissions sees entry print screen and resulting print as normal. There is no extra step required.
Can you confirm that the same user is able to see the data in the entry view screens?
If they can there must be an error or conflict somewhere. Please make sure you are running the latest plug-in version (6.2.2) and try again. If this does not correct the issue try disabling all other plugins and trying again. If it works then, Activate other plugins one at time checking each time until you find the conflict. If you could let us know any results if there is a plugin conflict found, we can work on any resolution.
Please also check that the users in that role have the ability to print GF entries
Hallo,
I want to offer every user who signs up the opportunity to create their professional profile, including a telephone number, via a form on my website. The telephone number should be encrypted, and users should be able to edit their telephone number using Gravity View. Only the owner of each entry should be able to view and edit their telephone number on the frontend side of Gravity View, and then save it back into the database in encrypted form. Is it possible to implement this functionality with your plugin?
best regards Robert
Hello
Yes this is possible. Lots of people set up scenarios like this. The main thing to do is to pull the profiles from GF entry data and not from WP user data. Gravity view already has options to only let users view thier own data which limits viewing of the submitted data to only people who submitted it. From there it is just a matter of which encryption permissions to use.
You specified that only the owner /user who submits the entry should be able to view/edit the phone data. Are the site admins also supposed to be able to view the phone number at any point? You can encrypt it so only the owner can see/ edit it or you can do it so admins AND the owner can do it. Or you can make it only for the user but it sends an initial confirmation to admins to see etc.
..generally speaking if admins do not need it there is no point to store it since the user already knows their own phone number and has no need to store the own information for no further use, but there are scenarios where initial entry or printing etc are beneficial.
Anyway , yes it is possible and gravity view is a complex and amazing tool for creating “user profiles” and other data that isn’t actually stored in the WP user meta or basic info. That way you can encrypt it and handle it with view permissions both from gravity view and our plug-in.
As a head start you can popluaye the view using GV permissions , AND/OR use our custom user decrypted merge tags which then filter through our plugin view permissions.
Reading and Understanding how both systems work is important since they can both possibly be complex in permissions if set up that way
Ist not WP user data, it’S GF entry. With Gravity View-Frontend the user can edit their phone number, but when they save the entry (phone number) again, it’s not encrypted.
And administrators need access to the phone number data.
Is the field set to encrypt after feeds/ad-ons?
Do you mean “Encrypt After Submission is Processed”?
Yes, apologies. That is the old name of the setting
I’ll record a screen video tomorrow and send it to you.
Ok that would be helpful. Normally encryption occurs on any saving or updating of the field data as it is tied directly to the gravity forms hook for saving field data to the database. Unless you are using an additional add-on or custom code or something has changed in GV that we are unaware of, Gravity View adheres to using the gravity forms API and uses that to pull/save data so it should be passing the data back through gravity forms functionality to save which in turn runs our functionality attached.
In the Gravity Forms form, I have 2 fields, “First Name” and “Phone Number” (which should be encrypted). Then, in the frontend form, for example, in the phone number field, I entered “78945”. In the Gravity View frontend, this field shows the following data in the view: GFEFU[[[b420e9d4f0b53b3b9f990a506f7c0d22]]]GFEFU78954. Then, I edited the phone number in the Gravity View to “0000123”, and then Gravity View shows in the frontend: GFEFU[[[b420e9d4f0b53b3b9f990a506f7c0d22]]]GFEFU0000123.
You are using “user owned fields” which are ONLY visible to the original submitting user, so unless you log in as them you do not have view permission to the data.
The proper solution would be to use the “original submitting user view permission” option which gives the original submitting user view permissions to their own data IN ADDITION to any view permissions already set elsewhere.. such as “administrator” in the global user access list.
I assume you want to lock other users out from viewing those so if you check the tooltip for that setting it gives details on how to do this.
However, Beyond that is the issue of you seeing the encrypted string instead of the restricted display message.
Are you using a standard GV display, or a custom one utilizing merge tags where you can use our “user decrypted merge tags”?
.. after further review it’s not the entire string but just the user tag associated. What are these fields showing when you look at the actual data in the GF entry?
Hello
Sorry to disrupt other answer , but before you dive too deep into permissions with our plugin to work with GV permissions have you tried just standard encrypting everything and just using the GV view access to control who can see what?
GV lets you create views where users can only see their own data, so you don’t need to further restrict viewing on our plug-in end unless your users have access to admin where they could potentially see other users data. That said , you can do both if desired
Hello
Has this setup issue been resolved?
Sorry for the late reply, I was ill. I have to test a few options and settings with the permissions first and then I’ll get back to you…
Hello I am facing the same issue as other people mentioned. I update everything on the website and this plugin is also updated to latest version 6.2. I am facing a 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:757
When we have the plugin deactivated the contact forms send fine. Please let me know how to fix this so we can keep using this plugin.
Hello
Our team is already working on it. Do you also have the user registration plugin installed?
Hi, Thanks for the update. Yes we have Gravity Forms User Registration Add-On installed Version 5.3.0
Thank you. Please evaluate ver 6.2.1 which was just released. we have tested on latest version of WP and gravity forms with User registration add-on and are not having any error, but Your confirmation of this would help as subtle environment difference could be a key issue.
Thank you for the update. Everything works well now on my website after testing. Thanks for getting this update out so quickly.
Happy to help.
Hi, there seems to be a conflict with this plugin and the Gravity Forms User Registration Add-On though I can’t get more than a generic “There has been a critical error on this website.” Can you help in any way or point me in the right direction on how to solve this?
Thanks!
Ah, helps if I turn debug on:
Fatal error: Uncaught TypeError: substr(): Argument #1 ($string) must be of type string, array given in /code/wp-content/plugins/gravity-forms-encrypted-fields/gfef.php:758
Hello
It would be helpful to know how this error is coming up. As in when exactly is the error occurring?
To our knowledge there is no direct conflict between the plugins, but If it is occurring on submission because you are trying to encrypt user registration data. As in the instructions, you cannot do that. WP does not know how to decrypt it to utilize it for users. You can use the plugin to delete the gravity forms field data used for user registration data after the submission is complete where the user is already created, but you cannot try to pass encrypted data to WP to use for users information. WP has no native way of understanding or handling that encrypted data.
This happened on a different form completely. I tried to turn off encrypt for the registration form but it didn’t work. I just put a strval() on the variable and it seemed to work.
Ok. What was the indicator that there was a conflict with the user registration plugin?
Also, what version of the plugin are you using? The latest is ver 6.2. Should definitely update if not on this version.
If I turn the user registration plugin off, it works fine. Or vice versa.
And yes, updated but still the same error: Fatal error: Uncaught TypeError: substr(): Argument #1 ($string) must be of type string, array given in /code/wp-content/plugins/gravity-forms-encrypted-fields/gfef.php:757
Thank you. Please evaluate ver 6.2.1 which was just released. we have tested on latest version of WP and gravity forms with User registration add-on and are not having any error, but Your confirmation of this would help as subtle environment difference could be a key issue.
Everything is good!
Happy to help
Hi, Could you please send me confirmation or documentation that this plugin will help make my forms HIPPA compliant
Hello
Our plugin can certainly cover a few aspects of HIPAA compliance. Namely encryption of the data at rest and access controls to the data. But it can only cover meeting one or more of multiple parts required to achieving full HIPPA compliance in any environment.
We cannot give you general confirmation that simply using our plug-in would help meet hippa compliance as it could potentially be used incorrectly or set up without actually enforcing the helping factors for your specific scenario.
What we CAN confirm for you is that the encryption and data access controls available in it are generally more than acceptable to meet those portions of compliance if properly configured. There are plenty of companies using it for collection of sensitive data currently, but for confirmation you need to work with HIPPA compliance personnel to discuss your specific case and requirements.
For more information on HIPPA compliance please reference the HIPPA compliance guidelines and compliance white papers.
Hi there,
I was wondering if you could help us debug in issue with the encryption plugin on one of our sites. We have been using GF encrypted fields on two of our sites for awhile. We’ve noticed that the Encryption Password textfield and login button are not showing up for one of the sites and were wondering if you might have an idea why that might be. The password has been set for the site but we can’t find a way to enter it so that we can view the encrypted values.
Thanks, David Boutin
Hello
Does your site meet all the system requirements in the system check? (Top of the settings page)
If not, which items are flagged?
Hi there, thank you for the quick response! Here’s the info it shows: Click Here for System Check
Server Encryption Support: YES OpenSSL Encryption Supported! Mcrypt Encryption NOT Supported! Mcrypt is legacy(old) and requires server install in PHP 7.2+ . This is NOT needed if using Open SSL.
PHP Version: 7.4.11 PHP Version Supported!
Wordpress Version: 6.4.3 Wordpress Version Supported!
Gravity Forms Version: 2.8.6 Gravity Forms Version Supported!
Website Key: YES Auto unique website key generated and will automatically regenerate after plugin updates.
Encryption Password: YES Encryption password active.
Encryption Type: YES OpenSSL ON
Encryption Turned On: YES ENCRYPTION ON
Merge Tag Filter On: YES MERGE TAG FILTER ON
Also, from the encryption testing:
SAMPLE ENCRYPTED DATA STORED IN DATABASE: GFEncrypt: d4f1c422da24f741e4c9777151OGhwQjlJVkJpTDdSazlLOVlvMnBER0t5UlQ3eDRrczRLNkM5SUZ4Uld4OD0=
ENCRYPTION SUCCESSFULSAMPLE DECRYPTED DATA: USERS WITH PERMISSION SEE THIS IN ADMIN. YOU MUST LOG IN IF USING ASYNC.
my personal info 123-45-6789
DECRYPTION SUCCESSFULHello
Ok that looks good. I also want to verify that you are using Asynch mode on this site. You can verify this by checking your encryption type in the plugin settings page. Both the Open SSL and the Asynch /Strict Access mode options must be used in order to get Asynch mode login required for decryption.
If this is not the case, do not just turn it on. You will likely want to decrypt any existing data from standard open ssl before re-encrypting it using Asynch mode if that is how you want the data to be accessed. You may need to check your confirmation and notifications set up to be sure they are set up for Asynch mode as well. This should all be done with available encrypting forms turned off momentarily.
Thank you! This helped solve the problem (one site used async mode and the other didnt) .
Hi, I have setup the plugin and it works well with new submissions. I have 1677 older entries that I need to encrypt. I can see that it gets encrypted if I open and save the entry but I can’t do this 1677 times. Any solution? Thank you.
Hello
Yes, this is covered in the plugin setup and operation instructions under “ENCRYPTING / DECRYPTING PREVIOUSLY SUBMITTED FORM DATA”
Please use the manual encrypt/decrypt tool at the bottom of the plugin settings page. Carefully follow the instructions. You can encrypt in batches of up to 200 at a time in a few seconds each. Just increase the batch offset number by 200 each time. Start this number at the number of NEWER entries you already want to skip over for processing going backwards chronologically. It does not have to be exact, if data is already encrypted it will be skipped. You can specify the exact fields to encrypt or just encrypt all supported field types for the form.
You should have all 1677 old entries encrypted in a couple minutes once you get started.
Hope this helps
Thank you! It was indeed clear on the instructions but I had missed that.
Happy to help!
Hi,
Our site is getting hammered by cron jobs.
What can i do about this?
Best regards!
Hello
It appears you are using a very outdated plug-in version.
Please update your plug-in version and keep updated for new features and fixes according to updating instructions in the plug-in settings page or plugin readme.txt. Current version is 6.2
You can get auto updates and notifications using the ENVATO MARKET plugin. Or select to receive notice of this plug-in’s updates via email in your envato account under your purchase of this plugin.
