Tor N. Johnson

<p>The WP Enterprise Extension (WEX) is a multi-function plugin that adds a set of enhancements to tailor wordpress to an enterprise setting. It adds additional media upload types, customizes the post & page edit pages, and enables bulk installation of security and user management plugins (improving consistency across instances of wordpress in an organization).</p>
<p>WEX will additionally add a new page template – “Blank” which is a utility template that enables developers to create non-html pages.</p>
<h3>ACF Content Fields</h3>
<p>The centerpiece of the WEX enhancements are the modifications to the post/page system.  It adds the following sections to the post/page:</p>
<p>Head Tag Customizer<br />
Many posts/pages will need customized CSS, Java-script, or in rare cases, unique meta tags (this does NOT include the SEO meta tags).  The �Head Tag Customization� section enables the insertion of CSS and any other tags (usually Java-script) into the  of the page.<br />
The Custom CSS section will be inserted inside a  tag, output below the inclusion of the external CSS files.<br />
The Custom Meta / Java-script section will be summarily output into the  section.<br />
Both fields recognize and process shortcodes.</p>
<p>Custom Footer Code<br />
This field will inject HTML at the very bottom of the page.  While it can be used to display content, it�s real intended use is for developers to place code such as Java-script or one-off tracking pixels, or any other use where the code MUST be at the bottom of the page.</p>
<h3>Shortcodes</h3>
<p>[theme_uri] – outputs the full URL of the blog and the active theme folder<br />
[blog_uri] – shortcode equivalent of site_url()</p>


WP Enterprise Extension

The WP Enterprise Extension (WEX) is a multi-function plugin that adds a set of enhancements to tailor wordpress to an enterprise setting.

Harmedia Studios

<p>ServicePress Connector Core transforms WordPress into an enterprise operational integration edge for ServiceNow.</p>
<p>Built for enterprise WordPress environments, ServicePress provides centralized operational visibility, inventory synchronization, event-driven workflows, multisite governance, and controlled integration patterns between WordPress and ServiceNow.</p>
<p>ServicePress supports:</p>
<ul>
<li>Single WordPress installations</li>
<li>WordPress Multisite networks</li>
<li>Large distributed WordPress environments</li>
<li>Enterprise operational workflows</li>
<li>Security and vulnerability visibility</li>
<li>Controlled transport and synchronization pipelines</li>
</ul>
<p>Unlike earlier inventory-only integrations, ServicePress 2.0 introduces:</p>
<ul>
<li>Controlled outbound transport architecture</li>
<li>Queue-based synchronization workflows</li>
<li>Enterprise multisite governance</li>
<li>Scoped payload management</li>
<li>Privacy and data filtering controls</li>
<li>Role-aware administrative operations</li>
<li>Diagnostic and operational tooling</li>
<li>Optional legacy pull API compatibility</li>
</ul>
<h3>Enterprise Features</h3>
<ul>
<li>WordPress multisite inventory synchronization</li>
<li>Controlled ServiceNow integration workflows</li>
<li>Queue-based payload processing</li>
<li>Configurable transports and systems</li>
<li>Payload inspection and previewing</li>
<li>Event simulation and operational testing</li>
<li>Privacy and data scope controls</li>
<li>Multisite diagnostics and operational governance</li>
<li>Optional <code>/spnow/v1</code> compatibility layer for legacy pull integrations</li>
<li>Application Passwords disabled by default</li>
<li>Capability-protected administrative workflows</li>
</ul>
<h3>ServiceNow Integration</h3>
<p>ServicePress integrates with certified ServiceNow applications and workflows to provide:</p>
<ul>
<li>WordPress operational visibility</li>
<li>Site inventory synchronization</li>
<li>Plugin and theme visibility</li>
<li>Event-driven operational workflows</li>
<li>Vulnerability intelligence integrations</li>
<li>Enterprise observability pipelines</li>
</ul>
<p>Additional ServicePress integrations may include:</p>
<ul>
<li>Wordfence</li>
<li>WooCommerce</li>
<li>LearnPress</li>
<li>Enterprise publishing workflows</li>
<li>Operational control extensions</li>
</ul>
<h3>Security Model</h3>
<p>ServicePress 2.0 introduces a significantly hardened architecture compared to earlier releases.</p>
<p>Security improvements include:</p>
<ul>
<li>Capability-protected REST routes</li>
<li>Controlled multisite context switching</li>
<li>Optional legacy compatibility APIs</li>
<li>Application Passwords disabled by default</li>
<li>Request sanitization helpers</li>
<li>Scoped payload controls</li>
<li>Privacy-aware synchronization settings</li>
<li>Queue isolation and controlled transport workflows</li>
</ul>
<p>Legacy compatibility APIs are disabled unless explicitly enabled for migration or integration compatibility purposes.</p>
<h3>Legacy Pull API Compatibility</h3>
<p>ServicePress 2.0 optionally supports legacy <code>/spnow/v1</code> pull endpoints for backward compatibility with existing ServiceNow integrations.</p>
<p>Supported compatibility routes include:</p>
<ul>
<li><code>/spnow/v1/sites</code></li>
<li><code>/spnow/v1/networks</code></li>
<li><code>/spnow/v1/network_info</code></li>
<li><code>/spnow/v1/site_settings</code></li>
</ul>
<p>These routes are:</p>
<ul>
<li>Capability protected</li>
<li>Multisite aware</li>
<li>Governed through the new 2.0 architecture</li>
<li>Intended for migration and compatibility workflows</li>
</ul>
<h3>Enterprise Multisite Safety</h3>
<p>ServicePress 2.0 was designed specifically for enterprise and large multisite WordPress environments.</p>
<p>The platform introduces controlled multisite context handling, scoped synchronization workflows, capability-protected administrative operations, and optional compatibility APIs designed to minimize operational risk in large distributed WordPress networks.</p>
<p>ServicePress does not perform uncontrolled recursive synchronization or unmanaged background crawling across multisite environments.</p>
<h3>Legal Disclosure</h3>
<p>ServicePress facilitates operational integration workflows between WordPress and ServiceNow environments.</p>
<p>Each organization is responsible for:</p>
<ul>
<li>The configuration of synchronization workflows</li>
<li>Data governance and transport policies</li>
<li>ServiceNow operational workflows</li>
<li>WordPress administrative governance</li>
<li>Compliance and operational review processes</li>
</ul>
<p>ServicePress does not store or control customer operational data outside configured synchronization workflows.</p>
<h3>External Links</h3>
<p>ServicePress Website:<br />
https://servicepress.app</p>
<p>ServiceNow Store:<br />
https://store.servicenow.com/</p>
<p>Harmedia Studios:<br />
https://harmediastudios.com</p>


ServicePress Connector Core

Enterprise operational integration platform connecting WordPress and ServiceNow environments.

WP Enterprise Extension vs ServicePress Connector Core