Описание
What the plugin provides
— Custom Post Type socranext_post for AI-optimized articles (default URL slug artikelen-sn, configurable via the SocraNext platform).
— Custom Taxonomy socranext (hierarchical) for categorizing those articles.
— Knowledge Base page (WordPress page; default slug kennisbank-sn, configurable via the SocraNext platform).
— Template-based rendering for single/archive and knowledge base views (plugin templates via template_include).
— Admin screens under SocraNext (Overview, Articles, Categories). FAQ management is handled via the SocraNext platform.
— Cache flush on (de)activation to correctly register permalinks.
Display
The plugin renders views via bundled templates for:
— Single SocraNext articles and archive list.
— Knowledge base page with categories and Q&As.
Structured Data
— The FAQ display includes FAQPage JSON-LD to help search engines and AI systems better understand the Q&As.
REST API (for platform integration)
Under the namespace socranext/v1, routes include:
— GET /pages and GET /pages/{id} – list site pages (for adding/showing FAQ widgets).
— POST /toggle – enable/disable the FAQ widget per page.
— POST /store-aio-information and GET /aio-information/{page_id} – store/retrieve per-page FAQ data.
— POST /kennisbank and POST /kennisbank-custom – store knowledge base categories and custom markup/styles.
— POST /blog and POST /store-blog-custom – create articles and store global custom HTML/CSS/JS for article display.
— POST /collection-slugs – sync configurable articles/knowledge-base URL slugs from the SocraNext platform (rewrite flush + cache purge).
— GET /articles-list-custom – retrieve configuration for list views.
— POST /llmstxt and GET /llmstxt – publish and read llms.txt / llms-full.txt content from the SocraNext platform; served at /llms.txt and /llms-full.txt on the site.
Note: without an account/connection to app.socranext.ai, the auto-generation routes are typically not used, but the created post types, taxonomy, and pages remain available for display.
Privacy & external services
— The plugin does not call external APIs on its own; the integration is typically initiated by the SocraNext platform to your website.
— Websites: product site https://socranext.ai and platform https://app.socranext.ai.
Prefix & naming policy
- All plugin identifiers use the unique prefix family «SocraNext»:
- Functions, hooks, options, AJAX actions, REST namespace, script/style handles:
socranext_*(lowercase) - Constants:
SOCRANEXT_*(uppercase) - Human-facing labels and PHP namespaces (if used):
SocraNext(PascalCase)
- Functions, hooks, options, AJAX actions, REST namespace, script/style handles:
- We avoid reserved prefixes like
wp_,_, and__for custom identifiers. - Existing options and routes already comply; no migrations are required.
Установка
- Upload the plugin and activate it via Plugins Installed Plugins.
- (Optional) Connect your site in the SocraNext platform to automatically generate and publish content and FAQs.
Отзывы
Участники и разработчики
«SocraNext» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:
УчастникиПеревести «SocraNext» на ваш язык.
Заинтересованы в разработке?
Посмотрите код, проверьте SVN репозиторий, или подпишитесь на журнал разработки по RSS.
Журнал изменений
1.1.4
- Added
uninstall.php: when the plugin is deleted, all SocraNext content is removed from WordPress (articles CPT, taxonomy, knowledge base and articles pages, FAQ meta on pages/products/categories, options, featured images, and rewrite rules). Platform data is unchanged.
1.1.3
- llms.txt support: SocraNext can publish curated
llms.txtand fullllms-full.txtviaPOST /llmstxt; content is stored in WordPress options and served at/llms.txtand/llms-full.txt(rewrite rules, plain-text response, 404 when empty). GET /llmstxtreturns the stored content for platform sync/debugging.
1.1.2
/collection-slugsnow rejects slugs that collide with existing pages, posts, products or SocraNext articles (HTTP 409slug_conflict) instead of silently letting WordPress append-2and desyncing the URL from the saved option.- Knowledge base page rename now uses the same lookup chain as the articles page (stored option
old_knowledgebase_slugdefaultkennisbank-sn), so renames keep working when the option was lost. - Articles archive page ID is now persisted in a new
socranext_articles_page_idoption (set on activation and on rename) for deterministic future lookups.
1.1.1
/post-typesendpoint now also returns availability flags for native content types (blogs, products, categories) so the SocraNext platform can hide filter pills for content that does not exist on the site.- Availability checks: blogs use
wp_count_posts('post'), products require theproductpost type plus at least one published item (WooCommerce), categories useget_termswithhide_empty. - Response shape changed from a bare array of CPTs to
{ postTypes, availability }; the SocraNext server stays backwards-compatible with older plugin versions.
1.1.0
- Configurable URL slugs for the articles collection page and knowledge base page (defaults:
artikelen-sn,kennisbank-sn), synced from the SocraNext platform viaPOST /collection-slugs. - Article permalinks, rewrite rules, archive detection, and page paths now use the configured slugs instead of hardcoded values.
- Existing sites without custom slugs keep the same URLs; no change until slugs are updated in Website Instellingen.
1.0.4
- Added cache-purge integrations for Cloudways Breeze, WP-Optimize, NitroPack and Borlabs Cache so FAQ updates become visible to anonymous visitors immediately on these hosts/plugins.
- Added a generic Varnish/HTTP PURGE fallback that targets the page URL after every FAQ update (covers Cloudways without Breeze and other Varnish-based stacks).
1.0.3
- Restyled the SocraNext admin experience and FAQ toggles.
- Added pagination and slug/URL search support to the SocraNext REST API pages endpoint.
- Added multilingual support (WPML and Polylang) for all content listing endpoints.
1.0.2
- Fixed authentication handling for plugin REST/API integration in certain environments.
- Improved JSON handling and internal cleanup for more robust data processing.
1.0.1
- New hierarchical URL structure for SocraNext articles (
/{articles-slug}/parent/child/, defaultartikelen-sn) and improved permalink handling. - New default styling per content type (FAQ, knowledge base, articles) with dedicated CSS and JS assets.
- Centralized handling of custom HTML/CSS/JS for the FAQ sections, including improved cache invalidation.
- Expanded and refined REST API endpoints for pages, posts, products, categories and custom post types used by the SocraNext platform.
- Security and robustness improvements (escaping, sanitization, nonces, token handling) to better align with WordPress standards.
0.5.9
- Improved token handling for the REST API (more robust header parsing, support for Bearer tokens, timing-safe comparison).
- Added configurable disclaimer text for pages, products and product categories and only render it when explicitly set.
- Added FAQPage JSON-LD output for the knowledge base template.
- Fixed edge cases in blog/overview rendering so custom code is only injected once.
0.5.8
- WordPress plugin validation fixes
- Added JWT connection
- Code improvements and compatibility fixes
0.5.7
- Improved API endpoints
0.5.6
- Auth reworked
0.5.6
- Added Metadatasupport
0.5.5
- Added CPT support
0.5.4
- Added woocommerce support
0.5.3
- Added assets
0.5.2
- Initial public release: CPT+taxonomy, knowledge base page, shortcodes, admin screens, REST routes, templates, cache flush.




