SocraNext

Changelog

1.1.2

• /collection-slugs now rejects slugs that collide with existing pages, posts, products or SocraNext articles (HTTP 409 slug_conflict) instead of silently letting WordPress append -2 and 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_slug → default kennisbank-sn), so renames keep working when the option was lost.
• Articles archive page ID is now persisted in a new socranext_articles_page_id option (set on activation and on rename) for deterministic future lookups.

1.1.1

• /post-types endpoint 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 the product post type plus at least one published item (WooCommerce), categories use get_terms with hide_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 via POST /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/, default artikelen-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.