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

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,

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.

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.

Thanks, much appreciated.

Hi,

Would it be possible to add the update to dropbox again. It seems to have been removed.

Many thanks,

Thanks very much for the quick response.

I have uploaded the new plugin and it seems to be working now. I will keep monitoring it and let you know if the problem reoccurs.

Really appreciated.

Same, rolled back and working again. No error showing, just doesn’t work.

Ah ok, now I understand it. Thanks for the help.

Thanks for your reply but that didn’t really answer the question. Can you clarify that bypass cache means that the the page is not cached or that the already cached page is not viewed.

The reason is that after adding the cookie to the filter I am still seeing a cached page. The cookie is a date which is not showing when the page is revisited. I confirm that the cookie is present.

Ok, the fix is simple. Should have thought of it before. Add this to your css and the problem is fixed.

@media (max-width: 921px) { #ast-desktop-header {
display: none !important;
}
}

@media (min-width: 922px) { #ast-mobile-header {
display: none !important;
}
}

I reported this to Astra support and this is the answer.

After reviewing the website, it seems that the issue you are facing is likely related to CSS media queries. I’d like to clarify that Astra uses two Header markups – one for desktop and one for mobile devices – and their visibility is controlled by CSS Media queries. If the CSS loading speed is slow, it can impact the markup, causing both headers to appear.

To resolve this issue, I recommend reaching out to your hosting provider or the support team of any cache plugin you might be using. They can help you improve the loading speed of the CSS on your website. For more information, you can refer to the attached article. [Link to article]

My website is pretty quick, sometimes depending on connection speed pages can take 2 or 3 seconds to load. Unfortunately now, since 4.3 if your website does not load instantaneously then you will have some CLS caused by the desktop header flash on mobile view. Not really sure what I can do about this. Does anyone have any suggestions other than changing the theme?

I agree that this problem exists since 4.3

I can confirm there is no optimization or caching being used on the site and the same problem exists.

Hi hassadr, does the top bar of the desktop menu remain visible or does it flash up briefly and then disappear on page load like in the video link i posted?