Memory Wiki

Found the plugin at `/var/www/wordpress-plugins/plugins/fluent-community`. Let me explore its structure and find AJAX handlers and post creation logic.

Excellent. Found key files. Let me examine the core routing, FeedsController, and the framework's AJAX handling.

Now let me understand how the framework registers the AJAX routes, and see the rest of the `store` method:

Now let me look at the Router class and the hook prefix configuration:

Now let me look at the Route class to see how it registers with WordPress REST API, and the Feed model:

Let me now look at the `register()` method in Route.php and the remaining helper functions:

Let me also quickly check the ActivityMonitorHandler for its AJAX registration pattern, and the helpers for `sanitizeAndValidateData`:

Now I have the complete picture. Here is my comprehensive summary: --- ## Summary: How FluentCommunity Handles Posting ### What I Did I searched `/var/lib/docker/volumes/staging_wp_data/_data/wp-content/plugins/` first — FluentCommunity is **not installed there**. The actual plugin source is at `/var/www/wordpress-plugins/plugins/fluent-community/` (v2.5.0). I analyzed the full posting pipeline: route registration, AJAX/REST handler registration, feed model, controller, and helper classes. ### Architecture Overview FluentCommunity uses the **WordPress REST API**, not traditional `wp_ajax_` hooks, for its primary CRUD operations. It uses a custom framework (`WPFluent`) on top of `register_rest_route()`. --- ### 1. Route Registration (REST API) **File:** `/var/www/wordpress-plugins/plugins/fluent-community/app/Http/Routes/api.php` The posting endpoint is registered at: ``` POST fluent-community/v2/feeds → FeedsController@store ``` Key route definition (line 42): ```php $router->prefix('feeds')->withPolicy('PortalPolicy')->group(function ($router) { $router->post('/', 'FeedsController@store'); // ... }); ``` The framework registers routes via `rest_api_init` action (in `Application.php` line 497-507): ```php $this->addAction('rest_api_init', function($wpRestServer) use ($app) { $this->registerRestRoutes($app->router); }); ``` Each Route object calls `register_rest_route()` with: - **Namespace:** `fluent-community/v2` - **Callback:** `Route::callback()` → resolves to `FeedsController@store` - **Permission callback:** `Route::permissionCallback()` → resolves to policy `PortalPolicy` --- ### 2. Traditional `wp_ajax_` Handlers Only a few legacy AJAX handlers exist via direct `wp_ajax_` hooks: | Handler | Action | File | |---------|--------|------| | Nonce renewal | `wp_ajax_fluent_community_renew_nonce` | `ActivityMonitorHandler.php:39` | | User invitation (auth) | `wp_ajax_fcom_user_accept_invitation` | `InvitationHandler.php:21` | | User registration | `wp_ajax_fcom_user_registration` (+ nopriv) | `AuthModdule.php:27-28` | | User login | `wp_ajax_fcom_user_login_form` (+ nopriv) | `AuthModdule.php:29-30` | The framework's `AjaxTrait` also supports `wp_ajax_` registration with a **hook_prefix** (`fluent-community`), but the main posting routes use REST, not this path. --- ### 3. Post Creation Logic — `FeedsController@store()` **File:** `/var/www/wordpress-plugins/plugins/fluent-community/app/Http/Controllers/FeedsController.php` (lines 364-536) The full pipeline: 1. **Rate limit check** (line 368): ```php do_action('fluent_community/check_rate_limit/create_post', $user); ``` 2. **Validate input** (line 372): via `sanitizeAndValidateData()` - Enforces `message` is required - Sets `type = 'text'` - Calls `FeedsHelper::sanitizeAndValidateData()` 3. **Space validation** (lines 380-416): via `validateAndSetSpace()` - Checks space slug (`__self__post__` = profile post) - Validates user has `can_create_post` permission in that space - If space requires topics, validates topic selection 4. **Duplicate check** (line 421-423): - Checks same user hasn't posted identical message within 7 days 5. **Mentions parsing** (line 425): `FeedsHelper::getMentions()` - Replaces `@username` with mention markup - Collects mentioned user IDs 6. **Media processing** (lines 431-442): - `replaceImageUrlsWithRealMediaArchive()` — inline images - `processFeedMetaData()` — handles surveys, Giphy, video embeds, uploaded media 7. **Content rendering** (line 434): ```php $data['message_rendered'] = wp_kses_post(FeedsHelper::mdToHtml($message)); ``` - Converts Markdown to HTML via `FeedsHelper::mdToHtml()` 8. **Save** (lines 469-470): ```php $feed->fill($data); $feed->save(); ``` 9. **Topic attachment** (lines 489-496): attaches up to `max_topics_per_post` topics if posting in a space. 10. **Actions fired** (lines 500-535): - `fluent_community/feed/created` — for published posts - `fluent_community/space_feed/created` — in-space posts - `fluent_community/profile_feed/created` — profile posts - Various status-specific actions for scheduled/pending/unlisted 11. **Return** (lines 531-535): Transformed feed via `FeedsHelper::transformFeed()` --- ### 4. Feed Model **File:** `/var/www/wordpress-plugins/plugins/fluent-community/app/Models/Feed.php` - **Database table:** `fcom_posts` - **Fillable fields:** `user_id`, `title`, `slug`, `message`, `message_rendered`, `type`, `content_type`, `space_id`, `privacy`, `status`, `priority`, `featured_image`, `is_sticky`, `expired_at`, `scheduled_at`, `comments_count`, `reactions_count`, `meta`, `created_at`, `updated_at` - **Boot events:** auto-generates slug, auto-sets `user_id`, default `meta`, and `status='published'` - **Soft features:** duplicate detection, search scopes, bookmark scope, content moderation scope ### Files Examined - `/var/www/wordpress-plugins/plugins/fluent-community/fluent-community.php` — plugin entry point - `/var/www/wordpress-plugins/plugins/fluent-community/boot/app.php` — bootstrap - `/var/www/wordpress-plugins/plugins/fluent-community/config/app.php` — config (hook_prefix: `fluent-community`) - `/var/www/wordpress-plugins/plugins/fluent-community/app/Http/Routes/api.php` — REST route definitions - `/var/www/wordpress-plugins/plugins/fluent-community/app/Http/Routes/routes.php` — route file loader - `/var/www/wordpress-plugins/plugins/fluent-community/app/Http/Controllers/FeedsController.php` — **main post creation handler** (`store()`) - `/var/www/wordpress-plugins/plugins/fluent-community/app/Services/FeedsHelper.php` — feed processing helpers - `/var/www/wordpress-plugins/plugins/fluent-community/app/Models/Feed.php` — feed model (DB table: `fcom_posts`) - `/var/www/wordpress-plugins/plugins/fluent-community/app/Hooks/Handlers/ActivityMonitorHandler.php` — legacy `wp_ajax_` handlers - `/var/www/wordpress-plugins/plugins/fluent-community/app/Hooks/actions.php` — handler registrations - `/var/www/wordpress-plugins/plugins/fluent-community/vendor/wpfluent/framework/src/WPFluent/Http/Router.php` — custom router - `/var/www/wordpress-plugins/plugins/fluent-community/vendor/wpfluent/framework/src/WPFluent/Http/Route.php` — route registration via `register_rest_route()` - `/var/www/wordpress-plugins/plugins/fluent-community/vendor/wpfluent/framework/src/WPFluent/Foundation/Application.php` — `rest_api_init` hook binding - `/var/www/wordpress-plugins/plugins/fluent-community/vendor/wpfluent/framework/src/WPFluent/Foundation/Concerns/AjaxTrait.php` — AJAX trait - `/var/www/wordpress-plugins/plugins/fluent-community/Modules/Auth/AuthModdule.php` — auth AJAX handlers - `/var/www/wordpress-plugins/plugins/fluent-community/Modules/Auth/Classes/InvitationHandler.php` — invitation AJAX handler ### Issues Encountered None. The plugin was not in the expected Docker volume path but was found at `/var/www/wordpress-plugins/plugins/fluent-community/`.