Troubleshooting

This article covers the most common issues with Super Speedy Coming Soon Products and how to fix them.

The coming soon form does not appear on the product page

Check that the product is marked as Coming Soon. Edit the product in WooCommerce and confirm the Mark as Coming Soon checkbox is ticked under Product data > General. The setting is saved as “yes” or “no” — if the product was imported or duplicated, the meta value may be missing entirely.

Check that you’re viewing a single product page. The coming soon template only replaces the add-to-cart button on single product pages (is_product()). It does not apply on shop archives, category pages, or search results.

Check for theme compatibility. The plugin replaces the standard WooCommerce add-to-cart hook (woocommerce_template_single_add_to_cart on woocommerce_single_product_summary at priority 30). If your theme moves that function to a different hook, the plugin scans all registered hooks as a fallback. In rare cases where a theme renders the add-to-cart through a completely custom mechanism (bypassing woocommerce_template_single_add_to_cart entirely), the plugin cannot detect and replace it.

If this happens, you can add your theme’s hook to the known locations list in the plugin code. In super-speedy-coming-soon.php, find the $known_locations array inside sscs_maybe_replace_add_to_cart() and add your theme’s hook name and priority:

$known_locations = array(
    array( 'woocommerce_single_product_summary', 30 ),
    array( 'your_theme_custom_hook', 10 ), // your theme's hook
);

The countdown timer shows NaN or does not count down

Check that the Arrival Date is set. Edit the product and make sure the Arrival Date field has a valid date in YYYY-MM-DD format (e.g. 2025-03-15). If the field is empty, the JavaScript countdown receives an empty string and displays NaN.

Check that the arrival date is in the future. If the date has already passed, the countdown timer hides itself automatically. This is expected behavior — if you still want the coming soon form to display without a countdown, set a future date or leave the product marked as coming soon.

Signups are not reaching MailerLite

Check your API key. Go to WooCommerce > Super Speedy Settings and verify the MailerLite API key is entered correctly. If the key is empty or invalid, signups are saved locally in the wp_sscs_signups table but never sent to MailerLite.

Check the MailerLite Group ID on the product. Each product needs its own MailerLite Group ID in the product settings. If this field is empty, the MailerLite API call has no group to assign the subscriber to and the signup will fail.

Check the debug log. Enable WordPress debug logging by adding these lines to wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Then trigger a test signup and check wp-content/debug.log for lines starting with MailerLite API error. Common messages:

• “Unauthorized” — the API key is incorrect or expired. Generate a new one in MailerLite under Integrations > API.
• 422 response — usually an invalid group ID or malformed email. Double-check the group ID on the product.
• Timeout — the MailerLite API took longer than 15 seconds to respond. This is typically a temporary issue on MailerLite’s end. The signup is still saved locally.

Customer sees share buttons instead of the signup form

This is expected behavior. After a customer signs up, a cookie (sscs_mailerlite_user_id) is set for one year. When they return, the plugin shows share buttons instead of the signup form so they can refer others.

To reset this during testing, clear the sscs_mailerlite_user_id cookie from your browser, or open the page in a private/incognito window.

The signup form submits but nothing happens

Check your browser’s developer console (F12 > Console tab) for JavaScript errors. The signup form submits via AJAX — if another plugin or theme causes a JavaScript error earlier on the page, it can prevent the form submission from completing.

Check that the AJAX endpoint is accessible. The form posts to wp-admin/admin-ajax.php. Some security plugins or server-level rules block POST requests to admin-ajax.php for logged-out users. If you see a 403 or 405 error in the Network tab, check your security plugin settings or .htaccess rules.

Check whether a spam/abuse protection layer rejected it. The form shows a message in these cases — see the next section.

The form shows a “spam”, “too many attempts”, or “verification” error

These messages come from the built-in spam and abuse protection. See the Spam & Abuse Protection article for full detail on each layer; here’s what each message means and how to resolve it:

• “Spam detected” — the hidden honeypot field was filled in. Real users never trigger this, but an aggressive autofill tool or page builder occasionally can. If genuine signups are affected, test with honeypot disabled under WooCommerce > Super Speedy Settings.
• “Too many attempts. Please try again in a few minutes.” — the per-IP rate limit was hit (default 5 submissions per 10 minutes). This is expected during testing if you submit repeatedly from the same connection; wait a few minutes, or raise the limit with the sscs_rate_limit_max filter (see the Developer Hooks reference).
• “Verification failed. Please try again.” — Cloudflare Turnstile rejected the submission. Confirm both the Site Key and Secret Key are entered correctly in settings, that the keys belong to the same Turnstile widget, and that the widget’s allowed domains include your site.

The form shows “This product is not accepting signups” or “Signups are not configured for this product”

The handler validates the product before accepting a signup:

• “This product is not accepting signups.” — the submission targeted something that isn’t a published product marked Mark as Coming Soon. In normal use this only happens if the product was un-marked, unpublished, or the request was tampered with.
• “Signups are not configured for this product.” — the product is coming soon but has no MailerLite Group ID set. Add the group ID under Product data > General (or switch the product to the Super Speedy Emails provider, which doesn’t use this field).

The coming soon template appears in the wrong position

Some themes render the product page layout differently and the coming soon content may appear above or below where you’d expect it. The plugin replaces whatever hook is responsible for the add-to-cart button, so the coming soon content appears in the exact same position the add-to-cart button would have occupied.

If your theme splits the product page into custom sections (e.g. tabbed layouts, accordion panels), the coming soon content follows wherever the theme places the add-to-cart. This is by design — the plugin respects the theme’s layout.

Referral tracking is not working

The share buttons include a ?shared_by= URL parameter tied to the subscriber’s MailerLite ID. When someone clicks a shared link, the plugin sets a sscs_shared_by_id cookie so the referral is recorded if that visitor later signs up.

If referrals are not being tracked:

• The shared link must include the ?shared_by= parameter. Check that the share buttons are generating URLs with this parameter. If the subscriber’s MailerLite ID cookie is missing, the share URL falls back to the plain page URL with no referral tracking.
• The visitor must sign up in the same browser session (or at least before the cookie expires). The sscs_shared_by_id cookie is a session cookie scoped to the site path.

Super Speedy Emails (SSE) form does not appear

If you’ve selected Super Speedy Emails as the email provider on a product but the form doesn’t show:

• Confirm the Super Speedy Emails plugin is installed and activated. The SSE option only appears in the provider dropdown when the SSE_Forms class is available.
• Confirm you’ve selected an active SSE form in the SSE Form dropdown on the product. If no forms appear in the dropdown, create one in the SSE plugin settings first.
• If the SSE plugin was deactivated after the product was configured, the plugin falls back to the MailerLite form. Re-activate SSE and the form will reappear.