Plugin Breaks All Woocommerce Invoice Functionality

Hi @joyryde,
Please note that the swcfpc=1 is only mandatory when you are using the default Page Rule mode. If you are having issues with that, I will highly recommend you to enable the Worker mode inside the plugin settings which does not uses any Cache Buster whatsoever.

So, there is no MAJOR issue with the plugin. If you are having issue with the cache buster, use the worker mode which does not uses any cache buster query parameter.

We have switched that setting to Worker Mode even though it says it’s not recommended, we will let you know if customers continue to complain about Woocommerce Invoices.

We have switched that setting to Worker Mode even though it says it’s not recommended

– I don’t know where it says that it’s not recommended. The worker is n to 100% free like page rules and instead have a 100,000req/day limit in the free version. Check: https://workers.cloudflare.com/#plans

we will let you know if customers continue to complain about Woocommerce Invoices

– If the issue was coming from the the swcfpc query parameter then the issue will be resolved as the worker mode does not uses any cache buster query parameter.

If you don’t know where you say it’s not recommended we are happy to point it out for you!

it’s in the plugin settings under “Cloudflare Workers” and it says:

This mode is only recommended if there are conflicts with the current web server or other plugins.

It’s disabled by default.

Since it breaks Woocommerce, you might want to resolve that as Woocommerce says this plugin is the cause of the failure of their invoicing system.

• This reply was modified 2 years, 11 months ago by joyryde.

This mode is only recommended if there are conflicts with the current web server or other plugins.

– This is because the worker mode is not 100% free which is also mentioned there. So, we don’t want people to use the worker mode and unnecesarily pay for it when they can just use the 100% free page rule mode. So, the worker mode is there for cases like yours.

Since it breaks Woocommerce, you might want to resolve that as Woocommerce says this plugin is the cause of the failure of their invoicing system.

– The plugin is fully compatible with woocommerce and is being used on thousands of woocommerce sites. The plugin is causing issue with woocommerce invoice in the page rule mode due to the extra query parameter added and for situations like that the worker mode is there.

You should definitely put a huge warning in the settings page that it breaks Woocommerce then, if that many people are using it and none of them can send invoices to customers u less they disable it.

You should definitely put a huge warning in the settings page that it breaks Woocommerce then, if that many people are using it and none of them can send invoices to customers u less they disable it.

– As I said above the plugin does not break WooCommerce. It is breaking only the WooCommerce Invoicing Extension as that extension is expecting the query parameters in the URLs to be specific and not extra added. As I said before for situations like these the worker mode is there. So, that people who do not want the extra query parameter to be added to their site URL or that extra query parameter is causing issue on their site, they can just use the worker mode and not the page rule mode.

Woocommerce invoices are not an extension. Woocommerce invoices are when Woocommerce store owners click ADD ORDER from within the Woocommerce plugin, and then send that order to the customer to pay. It’a part of Woocommerce. There is no extension or plugin.

In that case I will add a notice in the plugin saying:

If you are using WooCommerce, you might face some issues in some WooCommerce features when using the default page rule mode. So, if you are using WooCommerce on your site, it would be a better choice to use the Worker mode instead.

I hope that will be helpful to people.

That would be PERFECT; we’ve had numerous issues with that query string so this would be a great notice to have in the settings. Thank you.

Yes I will also link to the thread you have opened in the WooCommerce forum as an example issue.

On another note, any thoughts on this issue?

https://www.ads-software.com/support/topic/some-headers-missing/#post-15189539

Hi @joyryde,
Yes definitely. First of all, it’s not the plugin. While caching pages WP removes all these extra response headers by default. This is why when using this plugin under the fallback cache section (when the fallback cache is enabled) you will see an option to save the response headers [Screenshot: https://i.imgur.com/xdIGu2c.png ] so that the fallback cache stores those headers and make sure they are added to the response when the page is provided.

Hope this helps.

• This reply was modified 2 years, 11 months ago by iSaumya.

OK, thank you!

I enabled “Save response headers”.