Tag
The WooCommerce ecommerce plugin.
WooCommerce
The filter decides which gateways a shopper sees and which ones the checkout accepts on submit. A condition that reads differently at those two moments produces an Invalid payment method error instead of a hidden option.
WooCommerce
Whatever you return from this filter becomes part of the cart item's identity, is saved in the session with it, and is empty in the block add-to-cart request unless you fill it from the Store API request yourself.
WooCommerce
The hook runs every time WooCommerce recalculates the cart, which can be several times in one request and not at all in another. Price changes made here have to be idempotent, and the mini cart needs its own answer.
WooCommerce
WooCommerce blocks the order with this message when the cart needs shipping but it has no country to ship to, or when shipping costs are hidden until an address is complete and the address never becomes complete.
WooCommerce
The notice is not about broken product data. It means the archive query for this exact URL returned zero rows, and the cause is usually visible in the URL, the visibility terms or a stale lookup table.
WooCommerce
WooCommerce says a payment method is invalid when the gateway the shopper picked is no longer in the list of available gateways by the time the order is submitted. Here is how to find out what removed it.
WooCommerce
WooCommerce shows the expired-session notice when the checkout arrives with an empty cart, usually because the session cookie never reached the server or a cached page carried someone else's nonce.
WooCommerce
WooCommerce does not track abandoned carts out of the box. Fix the checkout causes first, then decide how you will capture an email, time the reminders and measure the rate honestly.
WooCommerce
A store has two halves: catalogue pages that can be cached like any site, and cart, checkout and account pages that never can. Speed each half with different tools.
WooCommerce
Renaming, removing and reordering entries is a one-filter job. Adding a new entry is not: the filter only prints a link, and a link to an endpoint that was never registered is a 404 the filter cannot fix.
WooCommerce
The filter hands you every calculated rate for a package, which makes hiding and repricing trivial — and the result is cached against the cart contents, so a rule that depends on anything else looks random until you know why.
WooCommerce
The hook changes the main product query on the shop and archive pages, and nothing else: not shortcodes, not product blocks, not the REST API. Each of those has its own filter, and the usual complaint is a rule that works on the shop page and nowhere else.