tarun80

That is how a standard HTML paypal donation button works. Nothing wrong with it. It needs to be that way for the PayPal button to work correctly.

Maybe you can try a different plugin.

This is wrong. You do not need to expose an email address in plain text.

You can see that here: https://www.lunarsoft.net/donate

Google’s business is targeting users with advertising. Cloudflare’s is not. We have strict privacy commitments.

Earlier this year, Google informed us that they were going to begin charging for reCAPTCHA. That is entirely within their right. Cloudflare, given our volume, no doubt imposed significant costs on the reCAPTCHA service, even for Google.

Google spies on way too much to begin with, so it’s a valid reason to switch away from reCaptcha. Any time a captcha is issued by them they will see what site it goes to and your IP, so you can technically be tracked. With that, they can serve you ads relating to where you are, too.

Perfect. That is exactly what I needed. Thank you!

Perhaps under the live traffic area when we expand the details a whitelist button could get added?

Cerber is blocking redirects that I have within the Redirection plugin.

Example of what should happen:
domain.com/donate.php -> domain.com/donate/
domain.com/forums/index.php -> forums.domain.com

Proper redirects are a part of healthy SEO. Unfortunately Cerber is blocking these links because they do not exist and are seen as probing for vulnerabilities. A 301 redirect is “Moved Permanently” – telling web spiders that the page has permanently moved to a new URL destination and to properly update it’s records.

With an admin controlled whitelist, 301s and other admin made redirects would work once again.

Yes, I know that no such option is available. That’s why I started this topic prefixed with [Request]. And, as in my original post, I’m requesting an option be built in to disable the addition of your WPDM generator. I’m not sure why a download manager plugin even needs to insert a generator tag to begin with.

I already have code in my functions.php file to remove the generator tags.

// Remove generators.
remove_action('wp_head', 'wp_generator');

• This reply was modified 8 years ago by tarun80.

I believe that is how the Fix-W3TC came to be, however I could be mistaken. I do know they were making a push to try and get Fix-W3TC as an official plugin here on the WordPress plugin repository. Funny though, when they made the push Fredrick starts to appear, and now has disappeared once again after raising the prices you find in his plugin. It was also interesting to read about how this plugin took some of the code from Fix-W3TC and put it into W3TC itself.

There’s a fork of this project (Fix-W3TC) that does an excellent job, you may want to check it out.

I see, checking out all the nice new things now. Love the addition of reCaptcha. That reduces the number of plugins I need.

If you guys want a working alternative, I’d recommend checking out Fix-W3TC. It may solve issues and even some you may not have been aware of too.

@shaon, awesome, thanks for the reply!

Thanks for posting this. I came searching for the same information. This might be worth pinning or announcing in case others use that same plugin to check for PHP7 compatibility?

I’ve noticed some warnings/errors too. I’m running a checker for PHP7 errors/warnings and have this output upon testing:

FILE: /http/dev.example.com/wp-content/plugins/download-manager/libs/class.Crypt.php
--------------------------------------------------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 10 WARNINGS AFFECTING 5 LINES
--------------------------------------------------------------------------------------------------------------------------------
 19 | WARNING | Extension 'mcrypt' is deprecated since PHP 7.1 - use openssl (preferred) or pecl/mcrypt once available instead.
 19 | WARNING | Function mcrypt_get_iv_size() is deprecated since PHP 7.1; use OpenSSL instead
 21 | WARNING | Extension 'mcrypt' is deprecated since PHP 7.1 - use openssl (preferred) or pecl/mcrypt once available instead.
 21 | WARNING | Function mcrypt_create_iv() is deprecated since PHP 7.1; use OpenSSL instead
 23 | WARNING | Extension 'mcrypt' is deprecated since PHP 7.1 - use openssl (preferred) or pecl/mcrypt once available instead.
 23 | WARNING | Function mcrypt_encrypt() is deprecated since PHP 7.1; use OpenSSL instead
 43 | WARNING | Extension 'mcrypt' is deprecated since PHP 7.1 - use openssl (preferred) or pecl/mcrypt once available instead.
 43 | WARNING | Function mcrypt_get_iv_size() is deprecated since PHP 7.1; use OpenSSL instead
 53 | WARNING | Extension 'mcrypt' is deprecated since PHP 7.1 - use openssl (preferred) or pecl/mcrypt once available instead.
 53 | WARNING | Function mcrypt_decrypt() is deprecated since PHP 7.1; use OpenSSL instead
--------------------------------------------------------------------------------------------------------------------------------

FILE: /http/dev.example.com/wp-content/plugins/download-manager/libs/class.Pagination.php
--------------------------------------------------------------------------------------------------------------
FOUND 2 ERRORS AFFECTING 1 LINE
--------------------------------------------------------------------------------------------------------------
 136 | ERROR | Extension 'ereg' is deprecated since PHP 5.3 and removed since PHP 7.0 - use pcre instead.
 136 | ERROR | Function eregi() is deprecated since PHP 5.3 and removed since PHP 7.0; use preg_match instead
--------------------------------------------------------------------------------------------------------------

Quite welcome.

Perhaps it can be a new option to disable the DNS resolution completely? Or somehow make it a link that says click to resolve, and the resolves it in the current fashion for that row?

Looking into the differences with MyISAM and InnoDB I completely understand why it’s set up what way. The speed and efficiency, plus the difference in resources plus full text search.

Encoding changes sounds good as well, looking forward to it.

Thank you for the excellent discussion. ??

Having to wait 20 seconds for it to finish loading is an issue. Especially when the setting to resolve the IP addresses has been unchecked, that was the reason I unchecked it. Because I did not need every single IP address to be resolved.

Then can you explain why it’s somehow acceptable to not use the same collation and database type for the tables of your plugin?

InnoDB performs better than MyISAM and also does not need to be optimized to get rid of overhead. When you get a lot of brute force attempts and the logs are regularly cleaned out, yet no optimization occurs, the overhead adds up especially on large websites. This is why it should honor what WordPress sets forth in the config.

utf8mb4_unicode_520_ci allows for any type of character to be recognized, which is a plus. Considering WordPress is a multilingual CMS, being able to support any and all characters is a plus, too. Accuracy and performance are two more major benefits to using a good collation over the older generic utf8_general_ci.

If you’d like to learn more about it, this stackoverflow is a great read.

Time can vary between 5-20 seconds. Checked by counting myself and with Inspect Element -> Network in Firefox.

The tables Cerber uses should be based upon the values that WP itself uses. If WP is using InnoDB, so should Cerber. If WP is using table prefixes, so should Cerber unless you specifically have an option asking if it’s a multi-site install.