Shortcode fallback<\/h4>\n\n[wt_waitlist product_id=\"123\"] \u2014 use this if your custom product template does not fire the standard hooks.\n<\/code><\/pre>\n\nWhat WT Waitlist does NOT do (by design)<\/h4>\n\n\n- No SMS, no Mailchimp\/MailerLite integrations in the free version.<\/li>\n
- No double opt-in (minimal flow \u2014 leave email, get notification).<\/li>\n
- No WYSIWYG editor for email templates (HTML template lives in the plugin file, override with the
wt_waitlist\/notification_context<\/code> filter).<\/li>\n<\/ul>\n\nThese features are planned for the Pro edition. The free edition covers 100% of the core waitlist flow.<\/p>\n\n\n
\n- Install and activate WooCommerce (required).<\/li>\n
- Install WT Waitlist<\/strong> via WP Admin \u2192 Plugins \u2192 Add new, or manually over FTP (folder
wt-waitlist<\/code> in wp-content\/plugins\/<\/code>).<\/li>\n- Activate the plugin.<\/li>\n
- Open the WT Waitlist<\/strong> menu in the admin panel and configure data retention plus the administrator notification email address.<\/li>\n<\/ol>\n\n
On first activation the plugin creates its database tables and schedules a daily job that purges old subscriptions.<\/p>\n\n\n
\nHow does the form appear on the product page?<\/h3><\/dt>\nAutomatically \u2014 the plugin hooks into the standard WooCommerce action (woocommerce_single_product_summary<\/code>) for classic themes and into the render_block<\/code> filter for block themes (FSE). The form is shown only when the product is out of stock.<\/p><\/dd>\nWhat if my theme or template does not fire WooCommerce hooks?<\/h3><\/dt>\nUse the shortcode [wt_waitlist product_id=\"123\"]<\/code> \u2014 it works everywhere, from page builders to custom single product templates.<\/p><\/dd>\nHow many emails are sent at once?<\/h3><\/dt>\nAction Scheduler processes batches of 50 subscribers per tick. For a product with 1000 subscribers we queue 20 batches, each processed asynchronously, without blocking the PHP request.<\/p><\/dd>\n
Do emails go through my WP Mail configuration?<\/h3><\/dt>\nYes. We use wp_mail()<\/code> \u2014 if you have WP Mail SMTP, SendGrid, Amazon SES etc. configured, the mail travels through them. The plugin does not hardcode any provider.<\/p><\/dd>\nWhat happens to the data after uninstalling the plugin?<\/h3><\/dt>\nThe uninstall.php<\/code> file drops the tables and deletes the options. Clean. If you deactivate without deleting, the data stays \u2014 you can reactivate without losing subscriptions.<\/p><\/dd>\nGDPR compliance?<\/h3><\/dt>\nThe plugin stores anonymized IPs (last octet zeroed), consent timestamp and user agent. It integrates with WordPress Privacy Tools \u2014 a customer can request data export or deletion through the standard WordPress flow.<\/p><\/dd>\n
The signup form does not appear on my product page. What now?<\/h3><\/dt>\nFirst check whether the product is actually out of stock \u2014 the form replaces the Add to cart<\/strong> button only when stock is zero (or the variation is unavailable). If the product is out of stock and the form still does not appear, your theme likely uses a custom single-product template that bypasses the standard WooCommerce hooks. Drop the shortcode [wt_waitlist product_id=\"123\"]<\/code> directly into the product description or template. The shortcode also works inside page builders (Elementor, Bricks, Divi).<\/p><\/dd>\nCustomers submit the form but no notification email arrives.<\/h3><\/dt>\nOpen WT Waitlist \u2192 Settings<\/strong> and click Send test email to admin<\/strong>. If the test email arrives \u2014 wp_mail()<\/code> works and notifications will be delivered as soon as the product returns to stock (give Action Scheduler 1\u20132 minutes to process the batch). If the test email does not<\/strong> arrive, the problem is on your mail pipeline, not on the plugin. Install the free WP Mail SMTP<\/strong> plugin and route mail through a transactional provider (SMTP2GO, Brevo, SendGrid, Amazon SES). Shared hosting often blocks mail()<\/code> silently.<\/p><\/dd>\nHow do I check whether stock notifications are queued?<\/h3><\/dt>\nOpen WooCommerce \u2192 Status \u2192 Scheduled Actions<\/strong> and filter by hook wt_waitlist_*<\/code>. You will see pending and completed jobs with timestamps. If nothing appears after a stock change, check the System status<\/strong> panel inside WT Waitlist \u2192 Settings<\/strong> \u2014 it shows whether Action Scheduler is available and how many wt_waitlist_*<\/code> jobs are pending.<\/p><\/dd>\nSomething is broken and I want to send a support ticket.<\/h3><\/dt>\nOpen WT Waitlist \u2192 Settings<\/strong>, click Copy diagnostic info<\/strong> and paste the resulting block into your email to support. It includes plugin\/WP\/WC\/PHP versions, theme info, table state, subscription counts, recent email log, Action Scheduler status and a sample of out-of-stock products with their purchasable \/ backorders state \u2014 everything we need to diagnose the issue without going back and forth.<\/p><\/dd>\nI use Flatsome \/ Avada \/ Enfold \/ Porto and the form does not appear.<\/h3><\/dt>\nThemes with custom product-page templates (Flatsome UX Builder, Avada Builder, Enfold templates, Porto) often replace the standard WooCommerce single-product template, which bypasses the hooks WT Waitlist uses to attach the signup form. As of v1.0.3<\/strong> we ship multiple compatibility layers, including a wp_footer<\/code> JS DOM-injection fallback that should handle most of these themes automatically. The plugin also detects these themes and shows a compatibility note inside WT Waitlist \u2192 Settings \u2192 System status<\/strong>.<\/p>\n\nIf the form still does not show:<\/p>\n\n
\n- In Flatsome, switch the product template to Default<\/strong> in Flatsome \u2192 Theme Options \u2192 WooCommerce \u2192 Product Page<\/em>.<\/li>\n
- Or place the shortcode
[wt_waitlist product_id=\"123\"]<\/code> directly inside the product description \/ UX block \/ Custom HTML block.<\/li>\n<\/ul><\/dd>\nMy product is marked out of stock but customers can still add it to the cart, and the waitlist form does not appear.<\/h3><\/dt>\nThat means the product has backorders enabled<\/strong> (Product \u2192 Inventory \u2192 Allow backorders). WooCommerce treats it as purchasable even though is_in_stock()<\/code> returns false \u2014 and your customers see the standard \"Add to cart\" button alongside a backorder notice. WT Waitlist still renders its signup form for such products (so both signup paths coexist), but if the form is missing on a backorder-allowed product, check the Sample out-of-stock products<\/strong> section inside the diagnostic info (button Copy diagnostic info<\/strong>) \u2014 it lists is_purchasable \/ backorders_allowed \/ subscribers<\/code> per OOS product so you can see exactly how WooCommerce treats each item.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.4<\/h4>\n\n\n- Fix: signup form rendered twice<\/strong> on most themes. Two of the rendering layers shared one callback that did not check the \"already rendered\" guard, so the form appeared duplicated. Resolved \u2014 the form now renders exactly once.<\/li>\n
- Fix: signup form not appearing on variable products<\/strong> when a selected variation is out of stock or on backorder. The variation-aware JavaScript relied on
is_in_stock<\/code>, which is true<\/code> for onbackorder<\/code> variations. The plugin now tags each variation server-side (woocommerce_available_variation<\/code>) with an explicit waitlist flag, so the form shows correctly for every non-instock<\/code> variation.<\/li>\n- New: Editable signup form text<\/strong> \u2014 the form heading, description, button label and success message can now be customized under WT Waitlist \u2192 Settings \u2192 \"Signup form text\". Leave a field empty to keep the built-in translated default.<\/li>\n
- i18n: translated the last two hardcoded Polish fallback strings in the frontend script (connection \/ generic error messages).<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Fix: signup form was not appearing on backorder-allowed products.<\/strong> WooCommerce has three stock statuses \u2014
instock<\/code>, outofstock<\/code> and onbackorder<\/code> \u2014 and WC_Product::is_in_stock()<\/code> returns true<\/code> for both instock<\/code> and onbackorder<\/code>. The previous version's check !is_in_stock()<\/code> therefore skipped backorder products entirely. We now use get_stock_status() !== 'instock'<\/code> so the form is rendered (and accepts signups) for both true-OOS and backorder products. This is the primary fix in 1.0.3 \u2014 strongly recommended for any store using WooCommerce backorders.<\/li>\n- New: Two additional rendering layers for theme compatibility<\/strong> \u2014
woocommerce_after_single_product_summary<\/code> (Layer 4) and wp_footer<\/code> + JS DOM injection (Layer 5). Fixes \"signup form does not appear\" on themes that bypass the standard WooCommerce summary hooks (Flatsome UX Builder, Avada Builder, Enfold, Porto and similar page-builder driven themes).<\/li>\n- New: Sample out-of-stock products<\/strong> section in System status \u2014 for the first 5 OOS products shows
is_in_stock \/ is_purchasable \/ backorders_allowed \/ subscribers<\/code> so backorder vs. waitlist conflicts are immediately visible.<\/li>\n- New: Theme compatibility hints<\/strong> \u2014 System status now reports the active theme template slug and surfaces a known-incompatibility note for Flatsome \/ Avada \/ Enfold \/ Porto.<\/li>\n
- i18n: All user-facing strings translated to English<\/strong> (admin Settings labels, signup form, error messages, email templates, unsubscribe page, admin list table). Polish-only release is over \u2014 the plugin now ships in English by default.<\/li>\n
- Docs: new FAQ entries covering Flatsome\/builder-theme rendering and backorder-vs-waitlist behavior.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- New: System status<\/strong> panel inside WT Waitlist \u2192 Settings \u2014 versions, DB tables, subscription counts, Action Scheduler state and recent email log at a glance.<\/li>\n
- New: Send test email to admin<\/strong> button \u2014 one-click verification that
wp_mail()<\/code> works on this site (surfaces PHPMailer error string on failure).<\/li>\n- New: Copy diagnostic info<\/strong> button \u2014 generates a paste-ready support snippet so you do not have to copy values by hand.<\/li>\n
- New: Quick start<\/strong> panel at the top of the settings page explaining the out-of-stock \u2192 form \u2192 Action Scheduler \u2192 email flow in four lines.<\/li>\n
- Tweak: fixed
WT_WAITLIST_VERSION<\/code> constant that still reported 0.1.0<\/code> in cached environments.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n\n- Fix: replaced inline
<style><\/code> block in the unsubscribe page with wp_register_style()<\/code> + wp_print_styles()<\/code> (WP guideline compliance).<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
First public release.<\/p>\n\n
\n- Waitlist form on product pages (simple + variable), classic and block theme support.<\/li>\n
- Custom database tables (
{prefix}_waitlist_subscriptions<\/code>, {prefix}_waitlist_email_log<\/code>).<\/li>\n- Stock-status change detection through WooCommerce hooks.<\/li>\n
- Notification queue through Action Scheduler with 5 min throttle and batches of 50.<\/li>\n
- One-click unsubscribe with SHA-256 token.<\/li>\n
- Admin panel: subscriber list with filters and CSV export.<\/li>\n
- Product-edit widget showing waitlist count.<\/li>\n
- Integration with WordPress Privacy Tools (export + eraser).<\/li>\n
- Shortcode
[wt_waitlist]<\/code> as fallback.<\/li>\n- Honeypot plus rate limiter (10\/hour per IP).<\/li>\n
- Automatic purge of old subscriptions (configurable retention).<\/li>\n<\/ul>","raw_excerpt":"Lightweight waitlist for WooCommerce \u2014 automatic email notifications when an out-of-stock product (or variation) is back in stock.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/309015","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=309015"}],"author":[{"embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/webmastersteam"}],"wp:attachment":[{"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=309015"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=309015"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=309015"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=309015"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=309015"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/az.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=309015"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}