Troubleshooting¶
Routes return 404¶
Symptom: /settings/, /subscribe/, a stream archive, or a subscriber feed
returns a 404.
Cause: The rewrite rules have not been rebuilt since the theme was activated.
Fix: Visit Settings → Permalinks and click Save Changes. Nothing needs to change on the screen; saving triggers the flush.
Digest emails are not sending¶
Work through these in order:
- Is cron running? Check
wp cron event listforlss_process_subscriber_digests. See Cron. - Is mail working at all? Send a test email. If nothing arrives, the problem is the transport, not Loveshack. See Email delivery.
- Is there accessible new content? If a subscriber's window contains no posts they can access, no email is sent by design — and their timestamp is left unchanged so the window stays open.
- Is the subscriber confirmed? Only confirmed subscribers are processed.
A subscriber paid but has the wrong tier¶
Cause: The Stripe webhook did not reach the site, or its signature could not be verified.
Fix:
- Check the Stripe dashboard's webhook log for failed deliveries to your endpoint.
- Confirm the webhook signing secret in LoveShack → Subscriptions matches the one Stripe shows for that endpoint.
- Use the reconciliation path to resync the subscriber's record against Stripe.
See Tiers and Stripe.
Sign-in links are not arriving¶
Because authentication is passwordless, this is a mail problem, not an auth problem. Go through Email delivery, and check the spam folder first — a sender address that fails SPF alignment is the usual cause.
Theme updates are not offered¶
- Confirm the update credentials are set, either under Loveshack → Theme Updates or
as constants in
wp-config.php. - Remember that constants override anything saved in the admin — if a stale constant is defined, the admin values are ignored.
- Force a check with
wp theme update --dry-run loveshack.
See Updates.
The stream looks wrong in one color scheme¶
Most color settings are paired light/dark. A value set on only one of the pair leaves the other at the theme default. Check that both halves are set for the setting in question. See Color schemes.
Scrolling is janky on mobile¶
Turn off Enable card background blur first, then Enable single panel glass blur. Backdrop blur is expensive on low-powered devices and is the most common cause of stream scroll jank.
Analytics shows 404s on deeply nested stream URLs¶
Symptom: 404s on URLs like
/image/first-tweet/second-tweet/third-tweet/, where each segment looks like a
fragment of post content.
Cause: Those segments are post slugs. Stream post types were hierarchical before 1.1.11, so a threaded item's permalink included every ancestor's slug, and slugs are generated from the text of items that have no title. A thread can mix status, image, and video items, and a hierarchical permalink only resolves when every ancestor shares the item's post type — so mixed threads always 404.
Fix: Update to 1.1.11 or later. Permalinks are flat from that release, and old nested URLs redirect to the flat permalink of the deepest item that still exists. Nothing in the content needs editing.
Nothing on the site links to these URLs, since the stream shows only top-level items, so they reach you through feeds, sitemaps, and crawlers rather than visitors.
A post type disappeared from the admin¶
Each stream post type is registered only while its setting is enabled. Check
enabled_status, enabled_image, and enabled_video. Existing content is not
deleted when a type is disabled — re-enabling restores access to it.
See Stream post types.