Archives: Technical Notes

Found via user feedback in a ChatGPT transcript reviewing the Phase 9 report: the Quick Actions buttons’ text blended into their own background and was unreadable.

Root cause

A global rule, .passlee-mc a { color: var(–cc-blue); }, has higher CSS specificity (one class + one element type) than the single-class rule .passlee-cc-action-btn { color: #fff; }. Specificity always wins over source order, so every Quick Action button (an <a> tag) rendered blue text on its own blue background – invisible regardless of which rule was written first or last in the stylesheet.

Fix

Changed the button selector to .passlee-mc a.passlee-cc-action-btn (and its :hover variant), giving it higher specificity than the general link rule so the white text colour applies correctly. Verified live after purging the site’s LiteSpeed page cache.

Related discovery: LiteSpeed Cache is active on this site

While diagnosing why the fix wasn’t appearing live, discovered that the LiteSpeed Cache plugin is now active on knowledge.passlee.com (litespeed-cache/litespeed-cache.php), alongside backup and novamira – this was not the case when the plugin list was last checked in Phase 1, so it was likely added automatically by the host at some point. Any future PHP edits to files under wp-content/novamira-sandbox/ should be followed by do_action(‘litespeed_purge_all’) (or a manual purge from the LiteSpeed Cache admin screen) before assuming a fix has failed – the .htaccess LSCACHE block confirms server-level page caching is genuinely active, not just a plugin option.

A post-launch SEO review was conducted via Google Search Console (accessed through the same browser instance used for other admin work) after the passlee.com staging-to-production deployment.

Findings

• Average position sits on page 2 of results overall.
• The best-performing content is local landmark junction/roundabout guide pages, not the core service pages – suggesting local, hyper-specific content outperforms generic service pages for this site.
• 7 apparent 404s were investigated and confirmed to be legacy crawl history from a previous occupant of the domain, not a current site problem.
• www to non-www 301 redirects are correctly configured.
• Rank Math SEO is installed and connected to Search Console, with a local analytics database (wp_rank_math_analytics_gsc); a connection error was noted during the review and may need re-checking.
• A Malvern-focused page had previously been removed from the site.

Implication for content strategy

Since local landmark guide pages outperform core service pages, future content investment may be better directed toward more hyper-local, landmark-specific pages rather than expanding generic service page content.

passlee.com runs a three-layer caching stack: FastPixel caches full-page HTML, ShortPixel CDN caches static assets, and Avada compiles its own fusion-styles CSS separately. All three must be understood together when diagnosing why a change isn’t appearing live.

Known issue and fix

The staging environment’s FastPixel advanced-cache.php had hardcoded paths pointing at the production directory – a leftover artifact from cloning production to create staging. This was fixed by resolving paths dynamically via WP_CONTENT_DIR on both staging and production, rather than hardcoding either path.

Operational notes

• Correct FastPixel purge method: FASTPIXELFASTPIXEL_Backend_Cache::get_instance()->purge_all().
• Cached files live under the fastpixel-website-accelerator directory; there is a separate index_local.html specifically for local-cache.
• The ShortPixel CDN’s cdn_purge_version integer should never be bumped manually – doing so causes 404s on CDN-proxied CSS URLs.

The Avada theme’s hero image floats behind the .fusion-tb-header on desktop, but on mobile this floating behaviour breaks down and exposes a solid black header background instead of the hero image, since the header treats mobile differently from desktop by default.

Fix

Rather than relying on Avada’s Dynamic CSS pipeline (found to be unreliable for this scoped fix), a must-use plugin was added at wp-content/mu-plugins/mobile-header-fix.php, injecting scoped CSS at max-width: 800px. The same mu-plugin also handles: hiding the desktop logo on mobile, correcting hamburger menu icon visibility, and a margin-top / padding-top fix removing a white gap that appeared above .hero-banner-contain on mobile.

This is a placeholder technical note used to test the Technical Note architecture. Replace with real technical documentation.