PaceQuill Post Scheduler

FAQ

How do I migrate from Auto Post Scheduler or Steady Post Scheduler?

Back up your site and leave the old plugin installed while activating PaceQuill. It automatically imports settings and logs from Auto Post Scheduler, Steady Post Scheduler 1.0.0, and Steady Post Scheduler 1.0.1. No manual table renaming is needed.

Existing PaceQuill values are preserved. If both legacy settings formats exist, Steady’s independent sps_* values take priority and missing values are filled from aps_*. Both log tables are merged. Exact entries already copied by Steady are imported once; different entries with overlapping IDs are retained with independent PaceQuill IDs. Execution locks and old migration flags are not copied.

Old site-level plugins are silently deactivated and both old scheduled tasks are removed. Enabled scheduling keeps its next check time where available; disabled scheduling remains disabled. If you manually deactivated an old plugin, it may already have saved a disabled status. Review the imported status before enabling scheduling.

Wait for the migration-complete notice under Settings -> PaceQuill Post Scheduler before deleting the old plugins. Uninstalling old plugins after completion cannot remove PaceQuill’s independent copied data. Source data is retained until you uninstall its old plugin.

A failed import pauses PaceQuill and retries on a later request. Do not re-enable an old scheduler during migration. On multisite, deactivate network-active predecessors through Network Admin first. Import runs separately when each site loads; activate PaceQuill per site and review each site’s notice. Uninstall cleanup is scoped to the current site.

Why has the scheduler not published anything?

WP-Cron normally runs when visitors load your site. Low traffic can delay checks. Review the enabled status, next check, eligibility rules, weekday hours, excluded dates, and activity log. Your rules may exclude all available posts.

Can I use a server cron job?

Yes. Configure your host’s scheduler to request your site’s wp-cron.php regularly. Only disable WordPress’s normal cron triggering after confirming that your server task works. PaceQuill continues to use the WordPress scheduled task API.

Why does the dashboard report a missing scheduled task?

Another plugin may have replaced cron_schedules instead of adding its own schedule. PaceQuill attempts to restore its task when scheduling is enabled and migration is complete. Check the log and your site’s cron configuration if the warning persists.

How do eligibility and recycling interact?

PaceQuill first selects posts matching your eligibility rules. If no eligible posts are found and recycling is enabled, it looks for published posts matching the recycling rules. Selecting published posts as eligible can make the separate recycling fallback unnecessary. Random selection changes the selection order.

Will a cache clear when a post is published or recycled?

PaceQuill uses WordPress post updates. Cache invalidation depends on your cache plugin or host. If an updated post is not visible, check that system’s post-update behavior.

Are existing custom filters supported?

Historical aps_* filters remain as compatibility aliases and run before the corresponding pacequill_* filter. New integrations should use:

• pacequill_eligible_query: WP_Query arguments for eligible posts.
• pacequill_recycle_query: WP_Query arguments for recycling.
• pacequill_update_post: the post update when publishing an eligible post.
• pacequill_recycle_post: the post update when recycling a published post.
• pacequill_get_users_args: the author-selector user query.
• pacequill_get_users_max: the author-selector result limit.

Custom code directly accessing legacy functions, options, tables, or task names must be updated. PaceQuill uses the pacequill_ prefix, the site-prefixed pacequill_log table, and the pacequill_auto_post_hook task. Log IDs are internal identifiers and may change during import.