Memory Wiki

I'll systematically investigate both plugins. Let me start by exploring the structure of each.

Good. Let me read the key source files now.

Now let me get the rest of the FeedsController@store method and find the cron/scheduler code.

Let me search for the action handler that publishes scheduled feeds, and also check the `sanitizeAndValidateData` method for scheduled_at handling.

Let me find the listener for the scheduled action and the cron publishing logic.

Let me look at the `sanitizeAndValidateData` method to see how scheduled_at triggers 'scheduled' status, and check for any cron-based publishing.

Let me re-read the store method more carefully and look at the FeedsHelper processFeedMetaData method which might handle scheduled_at.

Excellent! Found the cron. Let me read the Scheduler handler.

Found the Pro addon code. Let me read all the key files.

Now let me check the Pro routes and look for the UI (Vue.js compose form).

Now let me find the UI side — the compose form in the Vue assets.

Let me search the compiled frontend JS for scheduling/datepicker UI patterns and check BuddyPress.

Let me search the compiled Vue app for the UI code related to scheduling in the compose form.

Let me get the remaining SchedulePostsController methods and search for any source Vue components.

Let me do a targeted search of the compiled app.js for the scheduling UI code and check the Pro action registration.

Let me check for the compose form template files that might contain the scheduling UI options.

Now I have all the information. Let me create a comprehensive findings document.

Here is my complete findings summary: --- ## 1. FluentCommunity Scheduled Posts ### 1A. Database Schema The `fcom_posts` table has a `scheduled_at DATETIME NULL` column (defined after `expired_at`). Migration in `FeedMigrator.php` handles both creation and ALTER TABLE for upgrades. ### 1B. Model `Feed.php` has `scheduled_at` in both `$fillable` and `$publicColumns`. `XProfile.php` has a `scheduledPosts()` relation querying `status = 'scheduled'`. ### 1C. Controller Flow (FeedsController@store) The controller does **not** handle `scheduled_at` directly. It sets `status = 'published'` on line 374, then passes data through `apply_filters('fluent_community/feed/new_feed_data', $data, $requestData)` on line 454. The Pro addon intercepts this filter. ### 1D. Pro Addon — SchedulePostHandler (the full scheduling logic) **`/var/www/wordpress-plugins/plugins/fluent-community-pro/app/Hooks/Handlers/SchedulePostHandler.php`** Key points: - `maybeSchedulePost()` hooks into `fluent_community/feed/new_feed_data` - Only admins/moderators (`is_admin` flag) can schedule - Changes status from `'published'` to `'scheduled'` and sets `scheduled_at` - Validates minimum 30-minute delay - Registers an **Action Scheduler** single-action at the exact UTC timestamp - `publishScheduledPost()` — the cron callback that changes status from `'scheduled'` to `'published'` and fires post-creation hooks ### 1E. Cron Mechanism Uses **WooCommerce Action Scheduler** (bundled in `vendor/woocommerce/action-scheduler/`). Each scheduled feed gets its own `as_schedule_single_action()` at the exact UTC timestamp. The hook is `fluent_community/feed/scheduled_publish`. This is NOT polled — Action Scheduler processes due actions on every WordPress request. ### 1F. API Endpoints (Pro) - `GET /scheduled-posts/` — list scheduled posts - `POST /scheduled-posts/publish/{id}` — early publish - `PUT /scheduled-posts/{id}` — reschedule ### 1G. UI The compose form uses **Element Plus** (Vue 3) with `<el-date-picker type="datetime">`. The datepicker localization strings in `PortalHandler.php` confirm date+time selection support. The source `.vue` files are compiled into minified `app.js`. --- ## 2. BuddyPress — No Activity Scheduling **BuddyPress does NOT support scheduled activity updates.** The `BP_Activity_Activity` class has no `scheduled_at` field and no scheduling logic. The activity post form (`post-form.php`) is a simple textarea + submit button with no date picker. The only "schedule" references in BuddyPress are: - `bp_activity_akismet_delete_old_metadata` — a cron job for Akismet cleanup - A deprecated function (`bp_blogs_catch_transition_post_status`, removed in 2.2.0) that handled WordPress **blog post** scheduling transitions in activity stream — this recorded scheduled *blog posts*, not scheduled *activities*. --- ## Files Created - **`/root/scheduled-posts-findings.md`** — Full document with all code excerpts and analysis.