Asteris for WordPress — Troubleshooting
Asteris for WordPress — Troubleshooting
Licence key won’t activate
Check: is the licence key entered exactly as it appears in the email? Keys are case-sensitive. Copy-paste directly from the email.
Check: is the licence already active on another domain? Each tier has a site limit. Deactivate from the old domain before activating on the new one (Asteris for WordPress → Licence → Deactivate).
Check: is your server able to make outbound HTTPS requests? Licence activation calls asterisforwordpress.com. Some servers block outbound connections. Ask your host.
If none of these resolve it, email support@ with your licence key (last 4 characters only, for privacy) and domain.
Module not showing on the frontend
- Confirm the module is toggled ON in Asteris for WordPress → Modules
- Clear your caching plugin’s cache (WP Rocket, W3 Total Cache, etc.)
- Check your theme isn’t overriding the module’s CSS with a more specific rule (browser inspect tool → look for overridden styles)
- Check for JavaScript errors in the browser console (F12 → Console) — a JS conflict from another plugin can prevent modules from initialising
White screen or PHP fatal error after activation
Check the error log: wp-content/debug.log (if WP_DEBUG_LOG is enabled) or your host’s PHP error log.
Most common cause: PHP version below 8.1. Asteris for WordPress requires PHP 8.1+.
Second most common: memory limit below 128MB. Increase in wp-config.php:
define('WP_MEMORY_LIMIT', '256M');Module works on desktop but not mobile
Check for CSS z-index conflicts (common with Side Cart and sticky header themes). Also check your mobile breakpoints — some module settings have mobile-specific display options.
A plugin update broke my site — how do I roll back?
Asteris for WordPress auto-updates through WordPress’s standard update mechanism (your site → Plugins → Updates). If a new version causes a problem on your specific theme + WP + WC combination, you can roll back in two ways:
Option 1 — Roll back via plugin (recommended). Install WP Rollback from the WP.org plugin directory. After activation, Plugins → Asteris for WordPress → Rollback lets you pick any previous version we’ve shipped. Your licence + settings are preserved across the rollback.
Option 2 — Roll back manually. Download the previous version’s .zip from your customer portal at /account (versioned downloads are available for the last 10 releases). Delete the current Asteris for WordPress plugin folder via FTP/SFTP, upload the older .zip via Plugins → Add New → Upload. Re-paste your licence key.
While rolled back, please email support@ with what broke + what you rolled back to. We treat rollback reports as P1 bug reports — they tell us a release shipped with a regression and we’ll patch within the SLA for your tier. Every paid release goes through 6-theme local-site testing before ship, but every customer environment differs — your report fills the gap our test fleet can’t.
The 14-day refund window does NOT reset on a problematic update — refunds run from the original purchase date. If you’ve passed the 14-day window and a release breaks something for you, your remedy is the rollback path above + a P1-priority fix from us, not a refund. (Your statutory consumer-law rights for “major failure” remain available under ACL s260 if the issue is unresolvable within a reasonable time — see Refund Policy §2.)
Is asterisforwordpress.com down?
Check status.asterisforwordpress.com for live status of: marketing site, licence activation server, plugin download CDN, and customer portal. Status page updates within 60 seconds of an outage and shows historical uptime.
If the status page itself is down: that’s the worst kind of outage and you should email founder@ — we monitor that inbox even during outages.
Still stuck?
Email [email protected] with:
- WordPress version, PHP version (and WooCommerce version if Asteris for WooCommerce is also installed)
- Asteris for WordPress version
- What you expected vs what happened
- Any error messages from the browser console or PHP log