Common print preview and PDF export failures.
/print does nothing for anonymous users
Cause: Staff-beta access model — browser print requires a logged-in WordPress user. Anonymous /print requests 404 (no login redirect).
Fix: Sign in, or use server-side PDF generation (machine-fetch ticket) for automated export.
/print opens an unrelated chart or print-* post
Cause: Research-team permalinks do not register a /print rewrite endpoint. Core 404 permalink guessing 301s /…/print to any post whose slug starts with print (for example a chart at /chart/print-books-…).
Fix: Print Engine intercepts /print before that guess: logged-in users get the print document; everyone else gets a 404. After deploy, purge any cached 301 for the report’s /print URL.
Generate PDF returns service_not_configured
Cause: Firebase render endpoints are not configured (Pdf_Export::is_configured() false).
Fix: Deploy render functions and ensure client-mu-plugins/firebase-render.php exposes prc_platform_firebase_render_endpoints. See the plugin README deploy commands.
Generate PDF returns action_scheduler_unavailable
Cause: Action Scheduler is not loaded.
Fix: Confirm post-publish-pipeline / Action Scheduler are active on the environment.
PDF stays pending
Cause: Async job queued but Firebase call failed or worker not running.
Fix: Check Action Scheduler for prc_print_engine_generate_pdf, review Firebase function logs, and confirm the post is published, public, and supports prc-print-engine.