Recently Browsing 0 members
No registered users viewing this page.
This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.
The development of this module is sponsored by schwarzdesign.
The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)
Screenshots (hCaptcha widget)
This module is (yet another) way for implementing a cookie management solution.
Of course there are several other possibilities:
- ... and so on ...
In this module you can configure which kind of cookie categories you want to manage:
You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
Currently there are four possible cookie groups:
- Necessary (always enabled)
- External Media
All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
If you want to give the users the possibility to change their consent, you can use the following Textformatter:
[[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
You can also add a custom link to output the banner again with a link / button with following class:
<a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
You find it here: PrivacyWire Git Repo
Download as .zip
I would love to hear your feedback 🙂
I have need to dynamically set InputFieldMultiSelect to selected on page load based on the status of some items within a database table.
However I keep running into issues when trying to do this via InputfieldSelect::setOptionAttributes()
Going by the above it sounds like it should be pretty straight forward, and for certain values it seems to work but not when I wanted to set it to 'selected'.
$f->setOptionAttributes(1030,['foo' => 'test']); The above works as I would have wanted, in that it updates the option with the value 1030, to include the attribute foo="test"
But the same code above edited to the following:
$f->setOptionAttributes(1030,['selected' => 'selected']); Doesn't seem to do anything?
I assume I'm missing something or trying to implement the 'selected' wrongly but I'm not sure how else I should approach this, any advice would be much appreciated.