Mustafa Uysal

@bakiyisite en son baktigimda calisiyordu, resmi amp eklentisi eskiden sadece post sayfalari icin calisiyordu, artik cogu sayfayi otomatik AMP formatina donusturebildiginden bu eklentiye gerek kalmadi genel olarak.

What do you mean with ‘ double-check that the paths for location /_static/ are correct.’?

I meant fastcgi_pass path “unix:/var/run/fastcgi.sock;” and include path “/etc/nginx/fastcgi_params;” is correct.

Perhaps Plesk configured to use a port instead unix socket, I don’t know the specs and I can’t provide server management level of support.

Hi @stefacchio,

Please double-check that the paths for location /_static/ are correct. If you’re using Nginx with Apache in proxy mode, you may need to handle rewrites in the .htaccess file rather than in the Nginx configuration. (If I remember correctly, in Plesk environments, Nginx passes dynamic requests to Apache while serving static assets directly.)

But I get error 404 on file resources…why?

This is likely due to a configuration issue, as the setup may differ slightly from standard Plesk settings.

If you don’t feel comfortable adjusting settings, don’t turn on the rewrite option for file optimizer.

Hi @alexboiler2

PaddlePress is not a payment gateway for WooCommerce, it’s a standalone plugin.

Can’t you add a hook that empties the cache when you deactivate the plugin?

Not with hook, but technically we can drop the cache before unlinking object cache drop-in, however, this would not be an ideal decision for busy websites.

It is really frustrating as a problem.

Caching is a frustrating problem in general.

Also, could you add a button that deactivates all the cache types in the plugin, but without deactivating the plugin? Or some sort of developing mode.

I could, but I’d prefer not to add that — at least for now. You can use bypass functionality when testing pages: https://docs.poweredcache.com/bypass-functionality-in-powered-cache/

You’re welcome, and if you’re happy with the plugin, I’d greatly appreciate it if you could leave a review.

After disable it, When I reactive the plugin the notification appears activated, but actually remains deactivated. In order to reactivate it, I have to deactivate and reactivate another plugin, after which powered cache is also activated

I’m not totally sure if I’ve got this right ??. But object caching is often the usual suspect here — if it’s enabled, try purging it to clear out any stale data.

If Powered Cache is adding defer, you can enter wp-api(.*) in the exclusions. This allows you to disable defer for specific resources, so you can still benefit from it on others. Generally, deferring inline scripts can cause issues, so I suggest double-checking to avoid breaking any functionality on your site.

I think the problem is caused by deferring, https://share.cleanshot.com/f3xHF7D0

Disable defer for wp-api resources and try again. (probably your site makes the requests for relative path /wp/….` when the base url is not set before making ajax calls.

Could you share the link to the page you see this problem? If you prefer to not share publicly feel free to share via email (support[at]poweredcache[dot]com)

Hi @stefacchio,

Could you provide more details about the problem? Where has the /wp-json part been removed? removed in cached results? or general?

Hi @torren1112,

comment_* cookies only work when you enable the logged-in user cache. Since these are known cookies we don’t cache them, and it’s not something you can change easily.

(I’ve replied your email too)

hey @stefacchio,

often when I click ‘UPDATE ALL SETTINGS AND CLEAR ALL CACHE’ the settings are saved but the cache is not emptied

That button works similarly to the admin bar purge. If your website holds too many cached pages, it can take some time. If you have enabled async purging, it can lead to a delay in purging operations.

Please check the size of cache folder before/after you click on the button.

Also could you add all the cache emptying buttons that are in the WP bar also in a section of the plugin page? Not everyone has the WP bar.

Update settings and clear all cache button is enough for that.

hi @stefacchio,

I’ve released a new update and I think this problem has been fixed with the new version. Could you give it a try?

(marking as resolved for now, feel free to update this thread)

Yes! If you want to have to cache and count properly working you can also implement a custom solution that updates badge-cart-items-count with an AJAX call.

Or, instead of rejecting the cookie you can add it as vary cookie – https://docs.poweredcache.com/advanced-options/#vary-cookies

I’m marking this thread as resolved, since the question is not particularly related to Powered Cache, it’s how the caching layer works.

Hey @stefacchio,

Could you please add woocommerce_items_in_cart to the Rejected Cookies section under Advanced Options? This should help because when items are added to the cart, the cart updates dynamically, but cached pages don’t reflect these changes. By serving a dynamic version of the page for users with items in their cart, the issue should be resolved.

Give it a try, and let me know how it goes!