- Goal
- Minimum Requirements
- Installation
- Usage
- Warnings
- FAQ
- Why
GFE_PRESET_WEBSITE_KEY
andGFE_PRESET_ENCRYPTION_KEY
must be defined? - Should I reuse
GFE_PRESET_WEBSITE_KEY
andGFE_PRESET_ENCRYPTION_KEY
? - I have installed this plugin. Does it mean my WordPress site is unhackable?
- Will you add support for older PHP versions?
- It looks awesome. Where can I find some more goodies like this?
- This isn't on wp.org. Where can I give a ⭐️⭐️⭐️⭐️⭐️ review?
- Why
- Testing
- Feedback
- Change Log
- Security
- Credits
- License
By default Gravity Forms Encrypted Fields generate website key automatically on web servers which violates 12-factor principle and makes backing up difficult.
GFE Preset overrides the website key via PHP constants so that the key always in a known state.
Moreover, encrypting with unknown encryption keys means you can't decrypt if disasters happen. Better safe than worry. GFE Preset triggers wp_die
if required constants not defined.
Besides, GFE Preset provides similar overrides to:
- CodeCanyon license key
- encryption key (also known as encryption password)
- PHP v7.2
- WordPress v5.0
- Gravity Forms Encrypted Fields v4.4.2
$ composer require itinerisltd/gfe-preset
Define these 3 constants in wp-config.php
:
// Required:
define('GFE_PRESET_WEBSITE_KEY', 'aaa');
define('GFE_PRESET_ENCRYPTION_KEY', 'bbb'); // Also kown as **encryption password**
// Optional:
define('GFE_PRESET_LICENSE_KEY', 'zzz');
Define these 3 constants in config/application.php
:
// Required:
Config::define('GFE_PRESET_WEBSITE_KEY', 'aaa');
Config::define('GFE_PRESET_ENCRYPTION_KEY', 'bbb'); // Also kown as **encryption password**
// Optional:
Config::define('GFE_PRESET_LICENSE_KEY', 'zzz');
-
You must save Gravity Forms Encrypted Fields setting page whenever:
- installing/activating the plugins
- updating the plugins
- changing the constants
-
You should run "ENCRYPTION TESTING AND VERIFICATION" on the plugin settings page
-
You should backup all the constants
-
You should backup website key and encryption password shown on the plugin settings page
- Without both website key and encryption password, you can't decrypt the data
-
You should practice backing up and restoring the whole WordPress installation from time to time
-
Normal Gravity Forms Security Best Practices still applies
-
Gravity Forms Encrypted Fields backup, verification, usage procedures still apply
- You must read the plugin readme and notices on the plugin setting page in full, and follow the instructions
This is to prevent encrypting with unknown (not backed up) website key and encryption key, which end up with a unrestorable database (data is encrtpyed but you can't decrypt them).
No!
Each WordPress installation (enviroment) should have its own set of GFE_PRESET_WEBSITE_KEY
and GFE_PRESET_ENCRYPTION_KEY
, i.e: staging and production servers should use different keys.
No website is unhackable.
To have a secure WordPress site, you have to keep all these up-to-date:
- WordPress core
- PHP
- this plugin
- all other WordPress themes and plugins
- everything on the server
- other security practices
- your mindset
Never! This plugin will only works on actively supported PHP versions.
Don't use it on end of life or security fixes only PHP versions.
- Articles on Itineris' blog
- More projects on Itineris' GitHub profile
- More plugins on Itineris' wp.org profile
- Follow @itineris_ltd and @TangRufus on Twitter
- Hire Itineris to build your next awesome site
Thanks! Glad you like it. It's important to let my boss knows somebody is using this project. Instead of giving reviews on wp.org, consider:
- tweet something good with mentioning @itineris_ltd and @TangRufus
- star this Github repo
- watch this Github repo
- write blog posts
- submit pull requests
- hire Itineris
# Code style checks.
$ composer style:check
Pull requests without tests will not be accepted!
Please provide feedback! We want to make this library useful in as many projects as possible. Please submit an issue and point out what you do and don't like, or fork the project and make suggestions. No issue is too small.
Please see CHANGELOG for more information on what has changed recently.
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
GFE Preset is a Itineris Limited project created by Tang Rufus.
Full list of contributors can be found here.
GFE Preset is licensed under the MIT License. Please see License File for more information.