sunrises

Yes, I believe that spam robots are clever these days. But it would be good if there was a way to at least reduce the problem without transferring data to other servers abroad. hCaptcha is certainly more data protection-friendly than Google, but according to European data protection laws, both are to be avoided because data is transferred to the USA. Thank you for your work!

I can activate the “BCC to me” option and make the click field invisible via CSS (opt-in default: true). The signatory then receives the message that is specified in the “Petition description” tab. However, there are two problems with this:

1) The name of the signatory appears as the sender of the email instead of the name of the petition starter.

2) It is not possible to change the e-mail signature. The data that the signatory has entered in the form always appears under the e-mail.

If these two points could be improved, then it would be possible to automatically send the signatory instructions on how to find and write to the MP for their district and to provide them with a draft text for the letter to the MP at the same time.

It would be a luxury if, depending on the zip code area specified (e.g. 70000 to 79999), a message tailored to the region could be sent. Or if you could include a list of e-mail addresses as a PDF attachment.

Yes, with CSS it is possible to adapt the appearance of the success message to the error message. In order to better comply with European data protection laws, it would still be good if there was a solution on the plugin side, so that it is not possible to read whose e-mail address is in the database from the page source code.

Another suggestion for improvement – also due to data protection, because the user’s consent is required when transferring data to the USA – would be to offer a PHP-generated captcha as an alternative to Google’s captcha: https://code.tutsplus.com/build-your-own-captcha-and-contact-form-in-php–net-5362t

Thank you for developing this great plugin!

The e-mail address should not be entered twice in the database, but the process should be canceled without the person signing the petition noticing.

The reason is data protection. It should not be possible to find out who has already signed the petition with their e-mail address with malicious intent.

Dear ?eslav,

now it works without any problem.

I have found that I only need to remove three characters from the request uri part of the 7g firewall:

Before:

fla|git|gz|hg|inc|ini|

After:

fla|git|hg|inc|ini|

You have to remove “|gz”.

Now I can use the disk cache method with the cachify rules in the .htaccess file. No idea why I had previously stated that there must be other conflicts besides the one in the request uri part.

Thank you!

• This reply was modified 3 years, 4 months ago by sunrises.

Dear ?eslav,

thank you for your reply.

I had already tried what happens when you remove the request-uri part in the firewall. The result is that the 403 forbidden error no longer appears. But still no cached website is delivered, the directory /wp-config/cache/cachify is not created. I had also tried replacing the 7G firewall with the 6G firewall, but that doesn’t work together with Cachify either. Do you have any more ideas about this? If I can’t solve the problem, maybe I should go for the database cache method?

Best wishes and thank you!