Hello

This is because {all_fields} is not a decrypted merge tag. It is a standard GF. Merge tag. Please read the full instructions and use the decrypted merge tags you presumably unlocked to get decrypted results.

These are selectable directly in the merge tag drop down lists in your notifications/confirmations after unlocking them.

Most users prefer the {gfef_decrypt_ALL} tag as a replacement for the standard {all_fields} tag.

There are extensive and complete instructions for using the tags including examples and video tutorials directly in the instructions for the decrypted merge tag options. Please click the “click here for instructions” button there to expand them.

Hello

The short answer is all of this is possible, but it seems you will be doing some custom programming that would be needed to go with it. We do not provide custom hooks into the encryption system as a precaution, but you can could use the system as designed for most of this. For encrypting within your custom programming you could call the encryption functions directly. However it should be stated clearly that we do not assist with custom programming.

There are a few documented developer encryption/decryption functions we provide to call at will which you could also use within your own ecosystem

Thank you for these answers,

But where can I find the documentation for the encryption/decryption functions you mention? You haven’t answered, is it possible to set your own password for encryption?

Hello

You can use your own explicit pass directly with the custom functions, and you always indirectly set a psuedo password using the plugin normally.

Yes

Hello

Yes you can use it plugin with gravity pdf. We include a simple custom pdf template for decrypting the field data, but you can write one to meet whatever your pdf formatting requirements are.

ok thanks

Normally yes. It sounds like you don’t have the proper write permissions to that directory as you normally would on a web server environment for WP.

licensing requires internet access.

You can remove the internet access after successful licensing, or install /activate on web dev environment and then clone/port the install to a local environment after licensing.

Hello

Authors can not issue refunds. As Envato Marketplace is the seller, please request it through your Envato account from item purchases.

Hello

Please follow the instructions on settings page for ENCRYPTION TYPE option under “Open SSL / Strict Access Mode :”

These instructions are listed before the ability to turn on asynch mode. Complete details of this mode including details to send decrypted data in anonymous notifications with asynch mode are listed there. I believe you may have to also use the “process feeds and add-ons before encrypting” option on the individual fields to use the method described there. A new version with this instructional addition has just been released. 6.1.8

Hello

This plug-in does not encrypt file uploads.

You can use the Dropbox or google drive add-ons for this or likely zapier for a number of other solutions. Those file storage solutions offer encrypted storage and have great sharing permissions for access control. The add ons allow for auto deleting of your server side copy after transfer as well.

Ahh. I was looking for a form wide setting for this. Is it possible to loop through all forms (and fields within) and set the “encrypt after submission is processed” flag to true on supported fields? I used a similar approach to set all supported fields to encrypt. IE: $field->encryptField = true;

$field->delayedencryptField = true

Thanks!

Hello

It appears you are using a very outdated plug-in version.

Please update your plug-in version according to updating instructions in the plug-in settings page or plugin readme.txt. Current version is 6.1.7

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.

Looks like the error is because of invalid SSL on my local machine. By any chance, are there other way where I can activate the plugin?

It would be really helpful for our scenario as internet is disabled on our servers, the only way to install/update is via FTP.

Looking forward for your recommendation, thank you!

Hello

You have to have internet connection to license. Fixing or removing your invalid SSL should help licensing communication with your server.

We are looking to update plugin to account for the error and give message of invalid SSL.

The settings page password only accepts 16 characters. If you pasted in something longer when setting it it is truncated to the first 16 chars. This is documented in the instructions for the lockout password.

The lockout page input accepts up to 32 chars. If you did this, just paste in the first 16 of your password you are using.

Okay, thank you!

Oh OK, Do you sign BAA regarding your service ?

Hello

The nature of the question is a little unclear. We do not offer any 3rd party service including handling or processing of your PHI therefore we would not enter into any BAA. Essentially, being only a tool to provide encryption, it is not operated by us, but by your org. This is the same as Gravity Forms , other plugins etc, or Wordpress software itself being only software your org is utilizing and has access to as part of your PHI intake and handling.

The software is self/user managed, and you configure and run on your own WP server. It provides encryption of your Gravity Forms data at rest on your own SQL server as well as provides security access restrictions for anything from very simple to complex data access protocols for your sites users/admin users.

Hope this helps

ok thank you

Hello

Did you recently migrate /restore/ modify the site or change servers or php versions?

Standby, I believe the issue may have been on our end. This should now be resolved, but please let us know if the issue persists

I am using your plugin. I set up a custom cron job to run through the gf_meta_entry table and used the “gfef_text_encrypt” function to encrypt each entry. All the data that was converted was un-encrypted to begin with.

The odd thing is that all meta in the database does have the right encoding (IE: GFEncrypt: aa91545966defec7b1dce6ea01TGRQdmZPZ0pGbWJYSU8yOHVtT0lSWWRwalRiY2tNRkk0RFdYaWpoYlpxST0=) but when i go to view the data within the entires section is displays it in differently (IE: enx1:QYkDZwXwsjJVJdWTs4aRRzm+suqwrH+1cWzE+f1u/FjmYBA0CI…).

Oddly enough too is that the email field within that form i just referenced is in the GFEncrypt: xxx format, but it is the only field. All fields besides one are single line text fields.

Gotcha.

Once you carefully set up the plug in following the numbered instructions you should be able to view your data as long as it was encrypted properly according to our plugins supported field types etc.

With running encryption from custom code it’s possible to encrypt basically anything, but I see you are using the custom “string” encryption to encrypt field data now. It is best to do this using the built in batch encryption after fully setting up the plugin to be sure that all field types are encrypted properly and of supported type. I see you have an extraordinary amount of preexisting entries and this would be slow overall. In general if you are not running new data processes on the old data is best to just archive it and start fresh with new entries moving forward as far as storage. but if using the dev encryption for fields to re-encrypt quickly,  just be sure the field types are supported by our plug-in for field data encryption.

Thanks for the explanation. I had missed a check to see if the field has been set to encryptField. I will add this flag and try again. Thanks for the explanation and the quick replies. Really appreciate it.

Hello

Please read on the asynchronous encryption mode. This requires both a logged in user with also entering single encryption password.

This is built in to the plug-in, and is enabled in the encryption type selection options further instructions.

It does come with some caveats due to no decryption being possible without logged in user and entered pass, so anonymous user notifications etc need to be accounted for and the instructions go over this.

Hello

The encrypted values are not updated unless they are actually changed when editing entries using the standard Gravity Forms entry edit interface.

..This however depends on the way the entries are being edited. The plug-in or custom solution they are using to edit entries must adhere to gravity forms same method of editing. If it saves over all data regardless of if it was changed or not then it will overwrite the encrypted data strings with whatever is in the field during the edited submission.

Suggested solutions:

1. Have them Use the gravity forms entry editor 2. Use a compliant entry editing method and/or only edit the fields that need editing so the restricted field data is not displayed or overwritten with the edit. 3. If appropriate, give the editor field view permissions in the existing setup so the information is displayed or hidden decrypted and just submitted for encryption again. 4. Write a small snippet to skip over saving encrypted field data if the submitted data matches your restricted display for that form. (This would allow new data entry on original submission or changing forms data with new field data on edit, but if the restricted display is submitted it would just keep whatever data is already there if anything.) This solution has been suggested by one of the devs who has it posted for a possible additional selectable plugin option for later release. Basically this would prevent the exact match of the restricted display from being submitted and actually saved initially, or over any existing or blank data at any following point if turned on.

Hello

Are you using the latest version of the plug-in? 6.1.7 If not please upgrade.

You can click our user name to send us an email via our author page contact form and include the purchase code there in private so we can assist.

I’ve written to you. Thanks!

Oh, and yes—I did update to 6.1.7 yesterday, before I submitted my tests. Was there anything in that update that would relate to this issue?

Hello

No. Updating never deletes any data. The most that can happen is if for some reason you are using a custom website key against all instructions, the key can fail to regenerate, and the auto key will take over for any new entries. A custom key needs to be checked and potentially re-entered after every update or site migration etc. which of course leads to failure to do so. This would result in your old encrypted data under the custom key not showing up in your entries displays, but the entries themselves would still be displayed and any non encrypted data in them would still display normally. Changing the key back to the custom key would display both again.

Again though, this wouldn’t ever delete any data from the database. It would just be sitting there encrypted and would read/display correctly again when the custom key it was encrypted under is entered again. Deleting data has to be done quite deliberately.

Ok, thank you. We are using the auto key. And sounds like spam filters are not the issue. Will keep digging.