Is your enhancement related to a problem? Please describe.
Yes. Currently, ClassifAI primarily focuses on standard WordPress fields like post_content and post_title for features such as automatic classification, excerpt generation, and content analysis.
In modern WordPress development, a significant portion of a post's meaningful content is often stored in Advanced Custom Fields (ACF) (e.g., flexible content blocks, text areas, or specific metadata). Because ClassifAI does not natively "see" this data, the AI-generated tags, categories, and summaries are often incomplete or inaccurate because they miss the context stored within these custom fields.
Designs
Ideally, a setting in the ClassifAI UI would allow users to select specific ACF field names to be included in the 'source material' for AI processing.
Describe alternatives you've considered
- Manual Hooking: Using filters like classifai_post_content to manually concatenate ACF values into the content stream. While functional for developers, it is not scalable for non-technical users and requires custom code for every project.
- Generic Metadata Sync: Trying to sync ACF fields to the main content area, which creates data redundancy and messes up the frontend layout.
- Other AI Plugins: Some competitor plugins offer a UI to select which meta keys (including ACF) should be included in the AI prompt, but they lack the enterprise-grade stability and ElasticPress integration that ClassifAI provides.
Code of Conduct
Is your enhancement related to a problem? Please describe.
Yes. Currently, ClassifAI primarily focuses on standard WordPress fields like post_content and post_title for features such as automatic classification, excerpt generation, and content analysis.
In modern WordPress development, a significant portion of a post's meaningful content is often stored in Advanced Custom Fields (ACF) (e.g., flexible content blocks, text areas, or specific metadata). Because ClassifAI does not natively "see" this data, the AI-generated tags, categories, and summaries are often incomplete or inaccurate because they miss the context stored within these custom fields.
Designs
Ideally, a setting in the ClassifAI UI would allow users to select specific ACF field names to be included in the 'source material' for AI processing.
Describe alternatives you've considered
Code of Conduct