Common Issues

“Requires WooCommerce to be installed and active” notice#

Symptom: A red notice appears in the admin and the settings page is missing.

Cause: WooCommerce is not installed or not activated.

1. Go to Plugins → Installed Plugins.
2. Install and activate WooCommerce (version 7.1 or newer).
3. Reload the admin; the WooCommerce → Order Tracking menu appears.

The shortcode shows as plain text on the page#

Symptom: Visitors see [leet_order_tracking] instead of the form.

Cause: The plugin is inactive, or the block or builder element does not process shortcodes.

1. Confirm the plugin is active under Plugins → Installed Plugins.
2. In the block editor, put the shortcode in a Shortcode block (or a Paragraph block), not in a Code or Preformatted block.
3. In page builders, use a text or shortcode element rather than a raw HTML element.

“Order not found” for an order that exists#

Symptom: A customer (or you) gets “Order not found” although the order number is correct.

Cause: The email entered does not match the order’s billing email, or the order is a refund, draft or trashed order.

1. Open the order under WooCommerce → Orders and check the Billing email. The email entered must match it exactly (capitalisation does not matter).
2. Make sure the customer is using the billing email, not the shipping email or the account email if they differ.
3. Check the order is not in the trash and is a real order, not a refund.
4. If you are logged in as a shop manager, you can look the order up with any email; this is expected and does not mean the email check is broken for customers.

“Too many failed attempts” while testing#

Symptom: You see the rate-limit message after trying several wrong combinations.

Cause: Ten failed lookups from your address, or for that order number, within 15 minutes.

1. Wait 15 minutes; the counters expire on their own.
2. Alternatively, a developer can clear the transients starting with leet_ot_fail_ or raise the limit with the leet_ot_max_failed_attempts filter while testing.

All visitors are rate limited at once#

Symptom: Several customers report “Too many failed attempts” shortly after one another.

Cause: Your site is behind a proxy or CDN, so every visitor shares the proxy’s IP address.

1. Confirm that all traffic to your server passes through the proxy or CDN.
2. Add define( 'LEET_OT_TRUST_PROXY', true ); to wp-config.php.
3. See Privacy and rate limiting for the security implications.

The tracking number is shown without a link#

Symptom: The number appears as plain text on the result card.

Cause: No template applies to that carrier, or the template was cleared.

1. On the order, check how the Carrier is spelt. It must match a name in the Carriers list (case does not matter).
2. Under WooCommerce → Order Tracking → Carrier tracking links, check the carrier’s line has the form Name | https://...{tracking_number}.
3. Check the Generic link template is not empty and starts with http:// or https://; templates without a scheme are cleared on save.

The tracking number line is missing entirely#

Symptom: The result card has no “Tracking Number” line.

Cause: The order has no tracking number, or the field is switched off.

1. Open the order and make sure the Tracking number under Shipment tracking is filled in and the order was updated.
2. Under WooCommerce → Order Tracking, make sure Tracking number and carrier link is ticked under Fields shown on the tracking result.

The form looks unstyled or out of place#

Symptom: The form has no card border or button styling.

Cause: The stylesheet is not loaded, usually because of an aggressive optimisation or caching plugin, or the shortcode is rendered outside normal page content.

1. Clear your page cache and any CSS optimisation cache.
2. Exclude the leet-ot-frontend stylesheet from CSS combining or delaying.
3. Override the CSS custom properties described in Design & Layout if your theme’s colours clash.

License will not activate#

Symptom: Clicking Activate returns an error.

Cause: The key is mistyped, the activation limit is reached, or the server cannot reach technoleet.dev.

1. Copy the key again from License keys in your technoleet.dev account and paste it without spaces.
2. Check the number of activations remaining in your account; deactivate the key on a site you no longer use.
3. Ask your host whether outbound HTTPS requests to technoleet.dev are blocked by a firewall.