SocraNext
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. – Template-based rendering for single/archive article views (plu
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. – Template-based rendering for single/archive article 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.
Article URL prefixes with WPML WPML determines the canonical URL of an existing article. To change an articles prefix for a language, first configure it in WPML for the SocraNext post type, then enter the same prefix for that language in the SocraNext platform. The platform does not automatically configure WPML’s translated post type prefixes.
After saving, check the final article and overview URLs, including redirects from old URLs. Saving an unchanged platform value does not start another URL synchronization.
Publishing on the existing WordPress blog New articles use the SocraNext post type by default. In the platform’s project settings, choose the existing WordPress blog to publish new articles as ordinary WordPress posts, with the site’s theme and a selected native blog category. Existing articles retain their post type, URL and locally edited native categories. The selected category must have a translation before publishing a translated article.
SocraNext continues to manage its own translations. Managed article saves are excluded from WPML’s automatic translation queue; WPML’s initial “Translate Everything” bulk run does not honor this per-post exclusion, so exclude managed articles from that initial batch. Native posts are rendered by the active theme, not the SocraNext article styler.
Moving existing articles into the blog Changing the destination does not move existing content automatically. In the platform settings, preview and move one existing article at a time. The same WordPress post ID, publication date, content, comments, image and platform binding are retained. WordPress assigns the final native permalink and resolves slug collisions; no second article is created. The active theme controls the presentation, including which custom fields it displays.
Linked Polylang translations move together, each into the translated native category. A group containing an unpublished or unmanaged translation is rejected before any changes. WPML migrations are explicitly blocked pending a supervised migration; new publication into the WordPress blog remains supported.