johnmmackey

<p>This WordPress plugin is designed to be used when WP is deployed as a Headless CMS.</p>
<p>Using <a href="https://www.advancedcustomfields.com" rel="nofollow ugc">Advanced Custom Fields</a> provides fine-grained control for content modeling;<br />
this plugin disables the default ‘content’ field as well as excerpts, trackbacks, comments and other unneeded fields from<br />
the default page edit view.</p>


Headless Pages

Disable the default Wordpress page editor when using custom fields.

Elementor

<p>Sticklight Connector provides a structured way to use the WordPress user system in external or React-based applications.</p>
<p>The plugin extends the WordPress REST API with additional endpoints that allow authenticated clients to retrieve user context and interact with WordPress data, while fully respecting core authentication methods, roles, and capability checks.</p>
<p>Sticklight does not replace WordPress authentication. It relies on <code>wp_authenticate</code> for credential validation and WordPress Application Passwords for API access, and follows standard permission checks (<code>current_user_can</code>) for all requests.</p>
<h4>Typical use cases</h4>
<ul>
<li>React applications connected to a WordPress site</li>
<li>Headless or hybrid WordPress setups</li>
<li>Admin or user dashboards built outside wp-admin</li>
<li>External tools that require authenticated access to WordPress data</li>
</ul>
<h4>Features</h4>
<ul>
<li>Authenticates via <code>wp_authenticate</code> and issues Application Passwords for API access</li>
<li>Adds REST endpoints for login, logout, and retrieving current user context</li>
<li>Enforces WordPress capability checks on all requests</li>
<li>Supports cross-origin headless setups</li>
<li>Extensible via WordPress hooks and filters</li>
</ul>
<h3>Usage</h3>
<h4>Login</h4>
<p>Authenticate with username (or email) and password:</p>
<pre><code>POST /wp-json/sticklight/v1/auth/login
</code></pre>
<p>On success the response includes an Application Password for subsequent API requests and the authenticated user:</p>
<pre><code>{
  "app_password": "XXXX XXXX XXXX XXXX XXXX XXXX",
  "user": {
    "user_id": 1,
    "username": "admin",
    "display_name": "Admin",
    "email": "admin@example.com",
    "roles": ["administrator"]
  }
}
</code></pre>
<p>Use the returned <code>app_password</code> with HTTP Basic Authentication for all further requests.</p>
<h4>Current user</h4>
<p>Retrieve the current authenticated user:</p>
<pre><code>GET /wp-json/sticklight/v1/auth/me
</code></pre>
<h4>Logout</h4>
<p>Revoke the current Application Password session:</p>
<pre><code>POST /wp-json/sticklight/v1/auth/logout
</code></pre>
<h4>User registration</h4>
<p>User creation is handled through the built-in WordPress REST API (<code>POST /wp-json/wp/v2/users</code>) and requires administrator authentication.</p>
<h4>Accessing protected data</h4>
<p>Requests to any endpoint must pass standard WordPress permission checks. Sticklight does not bypass or override these checks.</p>
<h3>Security</h3>
<p>Sticklight follows WordPress security practices:</p>
<ul>
<li>Authenticates via <code>wp_authenticate</code>, which respects all security plugin hooks (rate limiting, two-factor authentication, brute-force protection)</li>
<li>Issues Application Passwords scoped to individual sessions</li>
<li>Does not provide user registration — accounts must be created by an administrator</li>
<li>Applies capability checks (<code>current_user_can</code>) on all endpoints</li>
<li>Does not expose private data without proper permissions</li>
</ul>
<p>For external applications, it is recommended to:</p>
<ul>
<li>Use HTTPS</li>
<li>Restrict allowed origins</li>
<li>Avoid exposing sensitive endpoints unnecessarily</li>
</ul>


Sticklight

Use WordPress authentication and permissions in external React applications via secure REST API endpoints.

Headless Pages vs Sticklight