Forum Replies Created

Viewing 15 replies - 1 through 15 (of 105 total)
  • Thread Starter confusedneedhelp

    (@confusedneedhelp)

    You are also calling this 3 times in the same function. I cannot see a reason for it.

    Lines 1343, 1365, 1391

    $responseBody = wp_remote_retrieve_body($responseSending)

    If there is a reason for this then I apologise.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Hi Daniela,

    I am 99% sure that this is the issue I am having. It seems that my site has grown too large for memcached to work efficiently.

    I highly recommend you to include information such as this last post (re 2MB limit) within your documentation. If I have missed it then I am sorry. I believe the best way you will avoid so many questions in the future is to give people the information to consider such as “If memcached is causing your site to be slow here are a list of things to check”.

    I think that the standard query caching in WordPress is now very good and my site has never been faster.

    Many thanks for your help and quick responses.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Hi again,

    The specific query I am looking at is returning around 6MB of data (nearly 4000 posts). I have read somewhere that memcached values are limited to 1MB. The smaller queries seem ok. So what I am thinking is that due to the size of this specific query it is not getting saved in Memcached and is therefore being requested by the database.

    Then, when I turn memcached off, the query is able to access the WP query cache and return the results without using the database.

    Could this be the issue? Is there a limit on the value size in memcached on your server?

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    On initial page load there is no problem. Memcached is working well. I have tested it with Query Monitor and Object Cache hits increase from about 70% (Memcached off) to 100% (Memcached on). I also think the initial page load is slightly quicker as per these values.

    However, as discussed earlier, the major issue I’m having is that the subsequent ajax query which loads the posts and filters takes double the time with Memcached on. I can’t really see how a plugin or theme problem could cause this but I will continue trying to figure it out.

    Thanks for your continued help. I will move onto the help desk if I cannot figure it out myself.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Ok many thanks,

    I confirm that with memcached switched on the admin ajax requests are taking almost twice as long to complete. I can see that it is almost impossible to determine the cause of this due to the lack of documentation available on this function.

    I’ll leave it switched off for now.

    Many thanks for your help.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Ok, can you clarify this sentence “WordPress has a built-in object cache that can be backed by Memcached”.

    When you say “can” do you mean that it is not the standard operation of memcached within your plugin? So do I have to change something to make this happen?

    It seems like the standard wordpress query cache is working without memcached with an ajax request but when memcached is switched on there is no caching, although I am determining this purely based on the timings supplied in the earlier post.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Ok, would you be able to clarify one more thing please.

    Would a database query (e.g. get_posts) called from an ajax function check the memcache storage?

    If the answer is yes, is there any way to stop it from doing that?

    My best guess is that the queries are being searched for in memcache but do not exist because they are not cached due to being ajax requests.

    Alternatively is there a way to store these requests in memcached?

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Hi,

    Thanks for your assistance with this. It is appreciated.

    I have been doing some more investigation and I now see that the specific query which is being affected by Memcache is an admin ajax query. (My site loads posts and archive filters by admin ajax on page load.) I understand that admin ajax queries are not cached but I was wondering why having Memcache active would slow down this query?

    Actual timings for the server response for the ajax query are:

    Without Memcache – 869ms

    With Memcache – 1.69 secs

    These values are very consistent each time I load the page.

    Any help or explanation you can offer would be appreciated.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Ok, many thanks. I understand now that a memcache process is working even with the plugin option switched off. This makes sense. Is there any technical documentation which explains what switching memcache on in the plugin does extra to the process that is already running?

    I have 5 websites which vary greatly in size and theme / plugin make up. All of them are faster with the plugin option switched off so at the moment it seems the best option for me.

    Thanks again for your help, it is much appreciated.

    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Just to add that with Memcached switched off in the plugin options it is still showing as active in phpinfo.

    Hi,

    I am searching for a plugin that will enable me to use PayPal Expanded Checkout. Can you confirm that this plugin supports this?

    For comparison the current checkout methods are listed here:

    https://developer.paypal.com/docs/checkout/

    Many thanks

    Forum: Plugins
    In reply to: [Zoho ZeptoMail] PHP Error
    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Hi again,

    The problem still exists. The line 1346

    if($responseSending['body'] != '') {

    will produce an error if $responseSending is a WP_Error. The result is that you will get a PHP Fatal error and the rest of the code will not process. Most importantly the insert_failed_email function will not run and so the email is lost forever. Your server was down for hours last night and many emails were not sent and I had no way to know which ones had failed.

    Happy to give this another week and then I will look for a more professional option.

    Thanks

    Forum: Plugins
    In reply to: [Zoho ZeptoMail] PHP Error
    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Hi,

    I see the latest update 3.2.5 incorporates the fix I mentioned earlier. However, it will still produce an error. I had to make further changes which I did not document here but it seems your team didn’t bother to check this.

    I am not going to tell you what to do but I will say that with the current code there will still be an error based on line 1346 if $responseSending is a WP_error it will not work. $responseSending[‘body’] will not exist.

    Please check the code and kindly remark this topic as unresolved.

    Thanks,

    Forum: Plugins
    In reply to: [Zoho ZeptoMail] PHP Error
    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    Hi,

    I have updated to the latest version 3.2.4 and this error has still not been fixed. It is incredible how long your developers take to address these issues.

    I will continue using my original fix and hope that one day in 2025 this is officially fixed.

    Forum: Plugins
    In reply to: [Zoho ZeptoMail] PHP Error
    Thread Starter confusedneedhelp

    (@confusedneedhelp)

    At line 1310 the same command is written as:

    if(!is_wp_error( $responseSending )) {
    update_option('transmail_test_mail_case', $responseSending['body'], false);
    }

    I have updated 1337 as the same as a temp fix. Hopefully this will solve the problem.

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