Zum Inhalt springen
WooCommerce & WordPress Plugin Docs

FAQ

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Does it require WooCommerce?

Section titled “Does it require WooCommerce?”

Yes. Registry extends WooCommerce and does nothing without it active, it shows an admin notice and stops. It needs WooCommerce 8.0+, WordPress 6.5+ and PHP 8.1+.

Who can create a registry?

Section titled “Who can create a registry?”

Any logged-in customer, from the My Account → Gift Registries area. Guests cannot create registries, but they can view and buy from any registry shared with them, no account needed.

How does purchase tracking work?

Section titled “How does purchase tracking work?”

When a gift is bought through a registry, the registry ID is carried from the buy link onto the cart item, then saved to the order line item at checkout. When the order reaches processing or completed (or fires payment_complete), the bought quantity is added to the registry’s purchased count and the public page subtracts it from what’s still needed. Each order is counted only once, even if you change its status repeatedly.

Can guests buy directly from the shared page?

Section titled “Can guests buy directly from the shared page?”

Yes, if Allow direct purchase is on in WooCommerce → Gift Registries (it is by default). With it off, or when an item is out of stock or not purchasable, the button reads View product and sends the guest to the product page to buy normally. That route still records the registry on the order.

Do guests need an account to view or buy from a registry?

Section titled “Do guests need an account to view or buy from a registry?”

No. The public registry page is a read-only link anyone can open, and guests can buy without an account. Only creating and editing registries requires a logged-in customer.

What is the registry’s public URL?

Section titled “What is the registry’s public URL?”

Each registry lives on its own permalink under /gift-registry/ (for example /gift-registry/annas-wedding/). The post type is publicly readable but excluded from site search and archives, so a registry is only reachable by its direct, shareable link. If the link 404s after a manual install, re-save Settings → Permalinks to flush rewrite rules.

Is there a shortcode or block to embed a registry?

Section titled “Is there a shortcode or block to embed a registry?”

No. Registry has no shortcode and no block. The public page renders automatically on the registry’s own permalink; you share that link rather than embedding the registry inside another page.

Can one customer see or change another’s registry?

Section titled “Can one customer see or change another’s registry?”

No. Ownership is checked before every create, edit, quantity change, item removal and delete, so registries never leak between customers.

What event types are supported?

Section titled “What event types are supported?”

Five, chosen per registry: wedding, baby shower, birthday, housewarming and other. Each registry also carries an optional event date, shown on the public page in your site’s date format.

Does it use JavaScript or jQuery?

Section titled “Does it use JavaScript or jQuery?”

No. The public page, the My Account area and the add-to-registry control are server-rendered and submit via plain form posts, so they work with scripting disabled. The only front-end asset is a stylesheet, loaded only on pages that render a registry.

What happens to my data if I uninstall?

Section titled “What happens to my data if I uninstall?”

Deleting the plugin removes its two options (registry_settings and registry_db_version). Customer-created registries and their purchased counts are left in place on purpose, as user content that should survive a reinstall, remove them manually if you want them gone.

Section titled “Related”