Forum Replies Created

Viewing 15 replies - 1 through 15 (of 27 total)
  • Thread Starter Dade

    (@dade88)

    Kindly share the repo, I couldn’t find it before and that’s why I was posting here.

    It hooks wpa_handle_spammers directly, so it’s pretty straight forward.

    Dade

    (@dade88)

    @antonaleksandrov Actually reading your message I am wondering how a Docket Cache in RAM disk would compare to Redis plugins, if I have some (unlikely) spare time I will test and share the results. I was particularly intrigued by the results because they were essentially the same when using PHPRedis instead of Predis, but also when using Docket Cache itself

    @wav3front Redis Object Cache by Till Kruss (I was lazy to try other Redis plugin by Pantheon). Also consider there has been a lot of tuning on the dedicated server itself.

    Thanks for taking a look into it Anton.

    I have just tesed, with the following report: https://report.wpbenchmark.io/plHYnBPlke/

    While obviously I am happy with the score, I might ask a few questions.

    If I understand correctly, you just raised the threshold for test “Persistent object cache read”, is that right? If so, my main concern was the OC reads at 4,2s, do you currently consider this stat also not reliable?

    Thanks for taking care of this tool, it’s always good to fine-tune Dedicated Servers or VPS meant to server WordPress

    I am running into a similar issue, so I would like to be sure if there are improvements on my custom performance server (nginx, php-fpm and mariadb compiled from source with optimization flags), it’s simply a bug on the benchmark side or a limitation in my actual setup.

    Currently testing on PHP 8.3.26 and Redis Server 8.2.2. These are some reports:

    I might add, the site is meant for testing and I can tell using Redis have improved the already fast generation of the pages.

    Might be relevant to point some Redis plugin constants:

    define(‘WP_REDIS_CLIENT’, ‘phpredis’);
    define(‘WP_REDIS_PREFIX’, ‘XXX25’);
    define(‘WP_REDIS_DATABASE’, 2 );
    define(‘WP_REDIS_SCHEME’, ‘unix’ );
    define(‘WP_REDIS_PATH’, ‘/tmp/redis.sock’ );

    Also worth mentioning, OPCACHE and OPCACHE.JIT are enabled and configured.

    • This reply was modified 7 months, 2 weeks ago by Dade.
    Thread Starter Dade

    (@dade88)

    This looks awesome!

    Since I am, finally, not getting many errors from the Webhooks, could you please confirm if ignoring errors on submit still send the error mail to the admin?

    Thread Starter Dade

    (@dade88)

    Sure, is it public somewhere?

    Thread Starter Dade

    (@dade88)

    Issue still not resolved, unfortunately on the affected sites I have no other chance than completely disable the plugin.

    Thread Starter Dade

    (@dade88)

    I will look into it, but should a translation plugin has the very document language declaration solved for good according to best practices?

    I will share a viable solution if I found a usable one.

    Thread Starter Dade

    (@dade88)

    We are currently testing the implementation, so I would not feel honest asking for a feature of something we may not even use in the near future. But, I am glad you found a possible way to improve the plugin.

    As for the data, it seems pretty damn fast! Can’t wait to test it on some sites with decent traffic and security needs.

    Congratulations on your detailed answer and this awesome software.

    Thread Starter Dade

    (@dade88)

    That would be great, thanks you!

    Thread Starter Dade

    (@dade88)

    Security is not my area of expertise, so maybe this could raise more issues than benefits, but wouldn’t cookies be the solution for this?

    Kind of: if the user is not in blacklist (or pass the captcha), a temporary cookie is created on user browser, valid for X amount of time. If the cookie is present, the whole process is skipped until the cookie is invalidated. As this is intended for high traffic sites, a nonce could be created every X, so the server only has to ask the browser for the cookie nonce of the given time.

    Even for a very short time, this can save up a lot of checks, but I truly don’t know if this is acceptable from a security perspective.

    Thread Starter Dade

    (@dade88)

    It’s great to have such a complete and sincere answer, thank you!

    From what I can understand about the “every incoming request” part, it will make the check again when the user browse to the next page. If I am right, maybe there should be a “grace period” after the first check in order to reduce stress on the server (I know I am kind of exaggerating, but…) and on the user’s speed.

    Probably won’t be the best security approach, but if sensible areas of the site are covered with other security measures (for example, request certificate for wp-admin) we can add the extra layer of CrowdSec without fear of getting legit users out from the site with close to 0 impact.

    Doing some tests with CrowdSec implementations meanwhile, great software overall!

    Thread Starter Dade

    (@dade88)

    Could you give a link or an example of your first sentence?

    Regarding second sentence, that’s why I specified (WebPage “isPartOf” referring to WebSite @id) as it would simply refer to the WebSite Google has crawled on the homepage.

    The whole point of schema and knowledge graphs is about being explicit, it’s not a matter of redundancy but specificity. See this as an example https://stackoverflow.com/a/43234992. To be completely fair, ItemPage is even more appropiate than WebPage for an Article.

    I completely understand your point, and I am sure this plugin is very effective on making sure users have a lot of green ticks in Google Schema Markup, but this is not the focus of my question. Can this plugin, paid version or extension, deliver this level of specificity?

    Thread Starter Dade

    (@dade88)

    I will look closer into that. Thanks for your answer and your excellent plugin!

    In 8.0 I attempted a quick change and it worked.

    For example, in wp-content\plugins\wpcf7-redirect\classes\class-wpcf7r-leads-manager.php change line 352
    public static function insert_lead( $cf7_form_id, $args, $files = array(), $lead_type, $action_id ) {
    for
    public static function insert_lead( $cf7_form_id, $args, $lead_type, $action_id, $files = array() ) {

    If you can’t wait for the next version, you can try to fix the files this way. I didn’t test this changes, but Deprecation messages were gone.

Viewing 15 replies - 1 through 15 (of 27 total)