Skip to content

Store management

Configure caching, scheduled tasks and hosting

Avoid cached private workspaces and keep cleanup, indexing, notifications and licence checks running.

PressFlow 1.25.3 · 2 min read

Guide source reviewed for PressFlow 1.25.1.

PressFlow uses WooCommerce sessions, private customer workspaces, AJAX price refreshes and WordPress scheduled tasks. Public catalogue caching is useful, but personalised forms, decisions and file downloads must reach the current session.

Cache exclusions to review with your host

  • Cart, checkout, My Account and signed-in/customer-session traffic, following WooCommerce's normal exclusions.
  • PressFlow's private guest job and quote routes.
  • URLs carrying pfw_edit, pfw_saved, pfw_reorder, pfw_duplicate, pfw_job, pfw_quote or pfw_access.
  • Requests with a pfw_job_access_* cookie or WooCommerce session cookies.
  • Upload, artwork/proof download and customer-decision handlers; do not cache their responses or strip their nonces.

PressFlow sends private/no-store instructions for its private routes, but a CDN can serve a cached page before WordPress runs. Configure the CDN and page cache themselves. Do not put private tokens into analytics, search indexes or public cache keys that are logged widely.

Both VAT amounts can exist in compatible server HTML without varying cached pages by the browser's saved display preference. Customer-location pricing/tax and personalised sessions still need the appropriate shop cache policy. Do not confuse the VAT preference with a tax-calculation cache strategy.

Scheduled tasks

WordPress cron supports artwork cleanup, job indexing, licence validation and queued customer notifications. Its normal trigger depends on site requests; a host-managed scheduler can be more reliable for quiet shops. Ask your host to configure the normal WordPress cron runner rather than disabling cron with no replacement. See WordPress's cron overview.

Relevant events include pfw_cleanup_artwork, pfw_index_print_jobs, pfw_check_licence, pfw_refresh_customer_order, pfw_send_customer_update and pfw_send_quote_email. These names help a developer inspect scheduling; they are not customer-facing buttons or instructions to fire arbitrary events manually.

Upload capacity

Private file bytes and resumable chunks contribute to database usage. MySQL packet size and PHP memory can reduce the configured file limit. Unfinished transfers expire after 24 hours. Test real files at the expected size and ask your host about database capacity before raising upload limits.

For an unsupported large file, use an accessible transfer link and manual review. Do not expose private artwork through a public uploads folder to work around a limit.

Production queue indexing

The queue uses a derived job index populated in bounded scheduled batches from WooCommerce records. A newly rebuilt/restored index can need time to catch up. Refresh through supported controls and confirm cron works; do not delete source order items to fix a missing queue row.

Related: Emails, Artwork storage, Developer data/security.

Need a hand?

Contact the PressFlow team with details of what you are trying to do.

Keep exploring