Topic
Step-by-step guides for getting things done in WordPress.
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.
WooCommerce
Returning false stops the product entering the cart, but it does not explain anything. The notice is a separate call, and the filter is skipped entirely when a quantity is changed on the cart page, which is the gap most validation snippets fall through.
WooCommerce
The hook belongs to the classic checkout and never fires for the checkout block. On the stores where it does fire, the common snippet writes post meta that a high-performance order store cannot see.
WooCommerce
The hook fires on every route into the completed status — admin dropdown, bulk action, REST call, automatic completion of virtual orders, and an order moved back to completed after a refund. A callback that assumes a single, first-time event is wrong on four of those.
WooCommerce
The hook fires when a gateway reports a successful payment, which is not the same as when an order is placed. Offline methods never fire it, and that is the difference between a fulfilment script that works and one that quietly skips a third of orders.
WooCommerce
A fee added here is recalculated on every cart load and never stored, which is why conditions belong inside the callback. A negative fee is a discount that bypasses coupons, and the tax on it does not always behave.
WooCommerce
The hook fires inside the cart form, which is the whole point: an input printed here is submitted with the add-to-cart request. It is also why a stray closing tag printed here breaks the button.
WooCommerce
Everything in the summary column — title, price, add-to-cart form, meta — is a callback on this one hook, each at a fixed priority. Your output lands wherever its priority says, and the add-to-cart form sits at 30.
WordPress Tutorials
The constant governs core and only core. Setting it to false stops security releases arriving on their own, which is a decision worth making deliberately rather than inheriting from a snippet.
WordPress Tutorials
Setting this to zero does not shorten the retention period. It removes the trash entirely, so Move to Trash becomes Delete Permanently and there is nothing to restore from.
WordPress Tutorials
The constant does not cache anything. It tells WordPress to load one file very early, and if that file is missing or left behind by a removed plugin, the result is a site that either ignores the setting or fails to load at all.
WordPress Tutorials
Defining these two constants overrides the database and greys out the settings fields. It is the fastest way to recover a site locked behind a wrong address, and the fastest way to lock one if the values are wrong.