leodefaveri

@wpmudevsupport14 It’s great news and I knew they would find the problem. Sometimes it’s difficult to listen to the user, but congratulations for listening to me and looking for a solution. I will be waiting for a correction and, if you want, I can give you new feedback.

Thanks!

@wpmudevsupport14 Thank you for your support and interest in understanding the problem. I’m sure they will find a solution for this and I would like you to send me that information when that happens. I’m available if you need anything.

Complementing information, Edge, after some extra tests, also sometimes experiences the problem. I was curious to understand why it worked before, but it actually happens too.

View post on imgur.com

• This reply was modified 1 month ago by leodefaveri.

Hi @wpmudevsupport13 Wow! First I need to praise this answer you gave me. This shows how committed you are to the quality of your plugins. Congratulations on that.

Well, the video test was done with the Brave browser, not Firefox. But to be able to give you a correct answer, I did the test with Firefox and it also happens, but I noticed that at times the price changes on the storefront but does not change on the product or vice versa.

So I decided to do the test on the following browsers: in addition to Brave, which I mentioned, Firefox, Edge, Chrome and Opera GX. Surprisingly the only one that works perfectly is Edge. In all others the behavior is exactly the same with the exception of Firefox as mentioned above.

So if I clear the cache and open the page before it is cached, I won’t find the hummingbird-served header. From the second visit he will be there. So without closing this browser, I clear the cache, go back to the browser, go to any other page and return, it shouldn’t have this header, because I just cleared the cache and it hasn’t been formed yet. But it will be there as served (without using preload). If I keep the browser open, go to the panel and change the entire website theme, I can continue browsing the cache with the old theme normally, while I open any other browser and I will have the new theme.
So I have two browsers open with one cached and the old theme and the other with the new theme. As long as I don’t refresh the page (f5) I will be using the browser cache with everything (except dynamic pages obviously), and it is this behavior that could not occur.

I sincerely apologize if it seems like the problem is on my side, but it’s not, I’ve actually tested all the plugins you mentioned as well as others, such as Breeze, WP Rocket, WP Optimize, Super Page Cache and Powered Cache. The problem does not occur in all of them, only with HB. I could actually just ignore it and choose any other plugin, but at the same time I’m a contributor to the WordPress community and I exceptionally enjoy your excellent work, so I wanted to pass on this information. But I also don’t want to cause you and the users too much concern, as I’m sure you’ll find something in the future. As in another user’s topic that I mentioned at the beginning of the post, I also tried using plugins that prevent the browser cache, but it didn’t work for me either.

Once again, I thank you for your commitment and dedication to excellent quality support that enriches our ecosystem!

• This reply was modified 1 month ago by leodefaveri.

Hello @wpmudevsupport12, answering your questions

“– Is it possible to temporarily disable the varnish and see if the problem is gone?”

At the time of testing when I made the video, varnish was disabled. If you accessed the url and found it activated, it is because this site is not in production, just in testing. It is currently deactivated.

“– Access the wp-content > wphb-cache folder, are the files gone when you flush all caches via the Hummingbird interface? ( We are testing the page cache here )”

Even after clearing the cache, two files remain in the folder, index.html and wphb-cache.php

– If you select the “disable cache”?https://monosnap.com/file/fGHT8YbSSASFrUZGvJlit4w1c0RCOL?keep the browser console enabled and navigate between the pages, is it gone?

Sure. If I disable the browser cache, the price changes immediately. That’s why I said before that the problem is specifically the browser’s cache, which doesn’t seem to understand that it needs to be renewed after cleaning. See the video: https://reccloud.com/pt/u/vc941yy

Thank you for your support!

Hello @wpmudevsupport11

Thanks for the support. Well, to make it easier to understand, I made a video showing what happens. It is at this link below.

https://go.screenpal.com/watch/cZ66l9VWZ6d

Note that as long as I don’t update the browser, the price doesn’t change even after clearing the cache. In the video I didn’t close the browser, but if I close it and open it again the next day (example), the price will be there unchanged (9.50) until I update the browser or the browser cache expires.

When clicking on clear all cache, the client browser needs to understand that there has been a change and when entering the product page again, the price needs to be updated immediately for that user. It is important to say that if a new user accesses the page, it will open with the updated price and generate the new cache, but the user who is already on the page (or another page) in with the old price will continue to see the old price. So I’m absolutely sure that the problem refers to the browser’s cache, which needs to be forced to update after clearing the cache, and so when you leave the page and return, the price should already appear updated, as well as on the product showcase page (shop). This does not only occur on woocommerce pages, any changes to any part of the site remain in the same condition.

To complement the information, I have already done the test in an anonymous tab, in clean and different browsers too. I have done all possible tests to understand the reason for this, and I am convinced that it is the browser cache that should be updated immediately.

Hi @wpmudevsupport3 thanks for your response.

I think you didn’t understand or I couldn’t explain it clearly. When I say persistent cache, I don’t mean the object cache, but rather that the cache remains active in the browser even after clearing.

I’m not using object caching, and even if I was, my report wouldn’t make sense. And yes, I’m using woocommerce and I don’t use Cloudflare.
There is no other caching layer, I am using a VPS server with NGINX. Do the test yourself as I said and you will understand the problem.

Understand one thing, the problem only occurs with your plugin, any other one I tested (there were several) works correctly.
I can simply disable your plugin and the browser will continue to show the cached version.

@gabrielfilippi digo isso há tanto tempo… o plugin é ruim, a integra??o tem problemas e o suporte n?o funciona. Infelizmente o plugin do Claudio parou de funcionar que era excepcionalmente perfeito. Agora é esse elefante aí.

@mariovalney sim! Mas ainda n?o há integra??o Woo, só algumas plataformas prontas. E os pre?os de frete est?o excepcionalmente bons para lojistas. Se um dia vc voltar com seu plugin, serei o primeiro a usá-lo. Desejo sucesso pra vc Mário!

@gabrielfilippi dificilmente vai ter resposta aqui, esse plugin é muito bugado e eles n?o respondem. Só no github eles respondem as vezes.

@emersongodoy obrigado por esse retorno. Vou verificar, mas se a loja estiver em HPOS vai ter algum erro? Esse plugin é horroroso, mal feito demais, tive que fazer algumas gambiarras que peguei no git porque ele altera o layout do carrinho de forma grotesca. é realmente uma pena como o woocommerce é tratado por essas empresas.

Ok, I hadn’t found the correct documentation location, I already located all the instructions, so consider this topic resolved. Thanks!

@dglite This is due to incompatibility with Woocommerce’s HPOS. It looks like they are working on this for version 7, so either you wait or you change the table schema in the settings. I’m waiting for that too!

Hi @isaumya

Thanks for the answer. Yes, I have already tested with this option activated and deactivated. It was disabled when the error started and I activated it to test but it didn’t work. It’s still not clear to me why,
but I had been using the plugin normally for over 1 year and I started receiving complaints from buyers who were unable to complete their purchase because the page was in a loop. So I was forced to deactivate the plugin. I left the DNS still active in cloudflare, everything was normal, but just activate the plugin and the problem occurs. As I said above, i did a “reset all” and momentarily everything worked, but a short time later the error returned. I also changed cloudflare’s SSL settings to full, full (strict), flex and it didn’t work.

Hello,

Well, after resetting the plugin, everything worked, but a short time later the error returned. I had to deactivate the plugin for it to work properly. Something is incompatible that is creating the console error to many redirects for ?wc-ajax=update_order_review in my ecom and just deactivate the plugin and everything will work again. I will continue investigating.

thanks