plugin/owc-gravityforms-digid

There is no license information available for the latest version (v2.0.0) of this package.

Add a DigiD login field to GravityForms

v2.0.0 2025-10-21 14:17 UTC

Requires

• php: ^8.0
• aura/session: ^4.0
• monolog/monolog: ^3.0
• owc/idp-userdata: ^1.0
• php-di/php-di: ^7.0
• symfony/http-foundation: ^6.0
• vlucas/phpdotenv: ^5.0
• yard/samlbase: ^1.7

Requires (Dev)

• 10up/wp_mock: 0.5.0
• friendsofphp/php-cs-fixer: ^3.0
• mockery/mockery: 1.5.*
• phpunit/phpunit: ~9.0
• szepeviktor/phpstan-wordpress: ^1.1

Unknown License

• Yard | Digital Agency

README

This plugin provides a GravityForms field to retrieve a BSN (social security) number from DigiD.

Local development

DigiD is only able to connect with valid PKi certificates, for local development you can fake a session by setting the below environment variable.

DIGID_FAKE_SESSION='012345678'

Logging

Enable logging to monitor errors during communication with DigiD. Make sure to set WP_DEBUG to true in your wp-config.php to enable logging. Be cautious: the generated log file is stored in the publicly accessible upload directoy and can include sensitive information.

• Logs are written daily to gfdigid-log{-date}.json in the uploads directory.
• A rotating file handler keeps up to 7 log files by default, deleting the oldest as needed.
• You can change the maximum number of log files using the filter described below.

Hooks

Change the maximum number of log files

Use the following filter to alter the rotating file handler's max files setting:

apply_filters('owc_gravityforms_digid_rotating_filer_handler_max_files', GF_DIGID_LOGGER_DEFAULT_MAX_FILES)

Intercept exceptions for custom handling

You can intercept exceptions caught by the plugin for additional processing or custom logging using this filter:

apply_filters('owc_gravityforms_digid_exception_intercept', $exception, $method)

The $exception parameter contains the caught exception object.

Creating a new release

1. Update the version in plugin.php x2 (plugin version and metadata)
2. Ensure that CHANGELOG.md and RELEASE_NOTES.md are updated with the latest changes
3. Draft a new release