Creator Assistant Hub

Changelog

1.2.0

• New: a single manager for changes to post content, for add-ons (filter creator_assistant_hub_content_injectors).
• New: action creator_assistant_hub_post_vectorized.
• New: Qdrant_Client::scroll_points() accepts a filter and can skip the vectors.
• New: OpenAi_Client::get_structured_response() accepts the model, reasoning effort and timeout (filter creator_assistant_hub_openai_structured_options).
• New: action creator_assistant_hub_cluster_batch_received, fired once per POST .../clusters after the per-cluster creator_assistant_hub_clusters_received actions, with array( 'collection', 'source_service', 'clusters' ) (the raw top-level clusters, children and members included, so a listener can read a hierarchical tree).
• New: GET .../collections/{collection}/points accepts match[<field>]=v1,v2 query parameters to restrict the points to those whose payload field equals one of the values.
• New: Clients\Clustering_Client (trigger and task status of the clustering Lambda) and the CREATOR_ASSISTANT_HUB_CLUSTERING_LAMBDA_URL constant, shared by the add-ons that cluster a collection.
• Changed: the clustering job identifies itself as clustering-job; the previous name planner-clustering-lambda is still accepted until the deployed image is rebuilt.

1.1.0

• New: creator_assistant_hub_menu_positions filter (menu slug => integer position, lower first) to order the entries of the Creator Assistant admin menu. Each add-on declares the position of its own entry and the Hub sorts the menu; the Hub page always stays first, so the top-level menu keeps opening it, and entries without a position go last, in the order they were added. Before, the order was the order of registration, and a post type added under the menu came even before the Hub page.
• Changed: the text passed to the vectorizers, and to the creator_assistant_hub_post_vectorizer_text filter, is now lightweight Markdown: headings, paragraphs, lists, quotes, code blocks and tables keep their structure instead of being flattened into one line. Classic-editor content (no <p> tags) keeps its paragraphs too. Parts returned by that filter are joined as separate paragraphs, so Document::normalize_array() now returns separate paragraphs instead of one line. New helpers Document::html_to_markdown() and Document::normalize_markdown(); Document::html_to_text() is unchanged.
• Changed: post summaries are now 3-5 sentences of plain prose, stating the topic, angle and subtopics of the post, without lists, Markdown or opening phrases like “This article”. The instructions are exposed as OpenAi_Client::SUMMARIZE_INSTRUCTIONS, and the summary cache key includes them, so a prompt change never returns a stale summary. A truncated response (status incomplete) is still returned, but is not cached.
• Note: after updating, every collection must be re-indexed with the “force reindex” action of the Tools tab, because both the vectorized text and the summaries change. Summaries are longer, so the OpenAI output cost per post roughly doubles. Product summaries of creator-assistant-search-pro go through the new prompt too. If you use creator-assistant-planner, re-tune its similarity thresholds after re-indexing.
• Fixed: a post with a code example containing HTML (for instance <div> in a code block) is no longer left without chunks. The chunk that contains markup now has its tags stripped before it is indexed, instead of the whole post being discarded and retried by the cron on every run.
• Fixed: post summaries were never generated when the configured chat model is a reasoning model (for example gpt-5-nano). The request allowed 300 output tokens, reasoning included, and the model spent them all thinking and returned no text. It now allows 2000.
• Changed: every option, transient, admin-post action, query argument, CSS class and Qdrant collection now carries the plugin’s full prefix (creator_assistant_hub_*, creator-assistant-hub-*) instead of cah_*, ca-* or no prefix. Custom CSS targeting the old .ca-* classes needs the new names.
• New: several WordPress sites can share one Qdrant cluster. Every collection name now carries a random identifier of the site (creator_assistant_<id>_hub_post_chunk), created the first time it is needed and stored in an option, so it does not change when the domain does and two sites never write into the same collection. It can be overridden with the creator_assistant_hub_qdrant_namespace filter, and a new one can be generated from the Tools tab, which a copy of a site (staging) should do. The creator_assistant_hub_qdrant_namespace_changed action fires when it changes.
• Changed: Qdrant cannot rename a collection, so on the first admin page load after updating the old ones (post_chunk, post_summary) are deleted and every post is indexed again into the new ones by the hourly cron; the cost is one more round of OpenAI embeddings.
• New: REST endpoints GET /wp-json/creator-assistant-hub/v1/collections/{collection}/points and POST /wp-json/creator-assistant-hub/v1/clusters, both authenticated via an RS256 JWT bearer token. Intended for a future external clustering service; not yet part of the public plugin, as no service is authorized to call them until its key pair is generated and registered.
• New: filter creator_assistant_hub_authorized_cluster_services (service name => PEM public key) to add or remove the external services allowed to call those two endpoints. A service signs its JWT with its own private key, with its name as iss and creator-assistant-hub as aud.
• New: extensibility hook creator_assistant_hub_clusters_received, fired once per top-level cluster after POST .../clusters stores it, with payload array( 'id', 'collection', 'source_service', 'centroid_point_id', 'aggregate', 'core_points' ), forwarded as the clustering job sent it (Hub does no Qdrant reads here: resolving a label or the text of the core points is up to the listener).
• Changed: label in that payload is no longer an OpenAI-generated paraphrase of the whole cluster, and the hook no longer carries label or member_queries at all – saves one OpenAI call per cluster. OpenAi_Client::generate_label() has been removed as a result.
• New: the “Google Connection” settings section now shows a plain-language description of what connecting a Google account is for. New filter creator_assistant_hub_google_connected_services (default: empty array) lets add-ons that use the Google connection list, in their own words, why the site owner should enable it; when the filter returns a non-empty array, an intro sentence and the list are shown above the connect/disconnect button.
• Fix: in SCRIPT_DEBUG mode, the two Sass-authored stylesheets (ai-animated-border, settings-tabs) threw a fatal error instead of loading — their compiled dist file is the only browser-usable form, but the asset loader always looked for a same-named file in src first. It now falls back to dist for them.
• New: extensibility hooks creator_assistant_hub_google_connected and creator_assistant_hub_google_disconnected, fired after a Google account is connected or disconnected, so add-ons that cache data read through the connection (property lists, account info, …) can drop that cache instead of serving it stale until its own TTL expires.
• Fixed: a payload index declared by an add-on through creator_assistant_hub_post_chunk_required_payload_indexes or creator_assistant_hub_post_summary_required_payload_indexes (the lang index of creator-assistant-hub-pro, the product fields of creator-assistant-search-pro) was created only by the next post vectorization. Activating or updating the add-on on a site already indexed made every filtered search fail with “Index required but not found” until some post was saved. The indexes are now synced on the next admin page, cron run or WP-CLI command, with no Qdrant call while the declared indexes are unchanged. An index Qdrant rejects is no longer marked as created: the next vectorization tries again, and the sync after 15 minutes. New method Post_Vectorizer::sync_payload_indexes(); a strategy declares its indexes by overriding Post_Abstract::get_required_payload_indexes().
• Changed: Qdrant_Client::collection_exists() now returns null not only without credentials but also when the request fails (network error, non-2xx status, unreadable body), instead of false: false now always means Qdrant answered that the collection does not exist. Compare the result with true/false explicitly. New Qdrant_Client::is_configured() tells the two null cases apart. A failed check no longer makes the payload-index sync, the collection creation before a vectorization or the upgrade of the collection names treat an existing collection as missing.
• Fix: a failed Google connection attempt (consent denied, the OAuth proxy unreachable, no refresh token in its response, …) silently bounced back to the same “Connect with Google” button with no indication anything went wrong — the only trace was a WP_DEBUG-gated log line. The “Google Connection” settings section now shows an error notice in that case.

1.0.2

• New: CreatorAssistantHub\Utils\Settings_Tabs, a shared renderer for the family’s tabbed settings pages. It owns the tab markup, the CSS classes, the tab-switching script and the validation of add-on-supplied tab definitions, so every add-on with its own settings page gets the same behaviour without copying it. Enqueue Settings_Tabs::ASSET_HANDLE (or declare it as a dependency of your own handle) to pull in the stylesheet and script.
• Fix: a settings section that no tab claims is now rendered in the first tab instead of being dropped. Dropping it removed its fields from the form entirely, so the value could never be saved and the add-on author got no hint why.
• Change: a tab can declare hide_submit => true to hide the Save button while it is active. Replaces the previous hard-coded list of tab slugs in the script.

1.0.1

• Fix: added Plugin::run_at_init(), a helper that defers a callback to the init hook (or runs it immediately if init has already fired). Creator Assistant Search 1.0.0 already calls this method for its theme-aware registration logic (depends on wp_is_block_theme()); without this update, sites running both plugins hit a fatal error.

1.0.0

• Initial release.
• Automatic post and page vectorization using OpenAI text-embedding-3-small.
• Qdrant Cloud integration for vector storage and retrieval.
• Settings page with TOS acceptance, OpenAI, Qdrant, and cache configuration.
• Block editor sidebar panel showing per-post vectorization status.
• Post list column (“Vector Status”) with per-vectorizer status indicators.
• Hourly background batch cron to automatically vectorize existing content.
• Site Health integration reporting service status.
• Daily Qdrant keep-alive cron for free-tier clusters.
• Extensibility hooks for add-ons, by category. Settings: creator_assistant_hub_loaded, creator_assistant_hub_after_register_settings, creator_assistant_hub_settings_tabs, creator_assistant_hub_sanitize_settings; OpenAI models: creator_assistant_hub_openai_embedding_model, creator_assistant_hub_openai_chat_model, creator_assistant_hub_embedding_dimension; vectorizer control: creator_assistant_hub_post_vectorizer_post_chunk, creator_assistant_hub_post_vectorizer_post_summary, creator_assistant_hub_skip_vectorizer, creator_assistant_hub_post_vectorizer_text, creator_assistant_hub_post_vectorizer_chunks; post types: creator_assistant_hub_additional_post_types, creator_assistant_hub_excluded_post_types; Qdrant payloads: creator_assistant_hub_post_vectorizer_post_chunk_payload, creator_assistant_hub_post_vectorizer_post_summary_payload, creator_assistant_hub_post_vectorizer_post_chunk_search_filter; collection lifecycle: creator_assistant_hub_post_vectorizer_post_chunk_collection_created, creator_assistant_hub_post_vectorizer_post_summary_collection_created.