Vectoron

Vectoron provides three main features:
1. REST API Endpoints
Secure REST API endpoints for external content management, perfect for integrating with automation platforms like Superblocks, Zapier, or custom applications.
<ul>
<li>Create and update posts programmatically</li>
<li>Manage categories</li>
<li>Upload media (file upload, base64, or URL)</li>
<li>Full authentication support (Basic Auth or custom headers)</li>
</ul>
2. Content Shortcodes
The <code>[vectoron_article]</code> shortcode provides:
<ul>
<li>Automatic wpautop disabling for custom HTML content</li>
<li>Built-in GA4 event tracking</li>
<li>FAQ accordion styling support</li>
</ul>
3. ACF Integration
Automatically sync post content to Advanced Custom Fields:
<ul>
<li>Settings page under Settings > Vectoron</li>
<li>Auto-detect WYSIWYG fields in ACF field groups</li>
<li>Support for Flexible Content, Repeaters, and Groups</li>
<li>ACF sync triggered by Vectoron API or X-Vectoron-Sync header</li>
<li>Works with both custom Vectoron API and native WP REST API</li>
</ul>
4. Page Builder Integrations
Seamless integration with popular WordPress page builders:
<ul>
<li>Elementor: Auto-sync content to Elementor’s text-editor widgets</li>
<li>Beaver Builder: Auto-sync content to Beaver Builder’s rich-text modules</li>
<li>DIVI: Auto-sync content to DIVI’s shortcode format (sections, rows, columns, text modules)</li>
<li>WP Bakery: Auto-sync content to WP Bakery’s shortcode format (rows, columns, column_text)</li>
<li>Configurable sync modes: Auto (detect existing builder posts), Always (convert all posts), or Disabled</li>
<li>Cache clearing for immediate visual updates</li>
</ul>
5. SEO Plugin Integrations
Automatic SEO metadata sync with popular SEO plugins:
<ul>
<li>Yoast SEO: Sync meta description, SEO title, and focus keyword</li>
<li>SEOpress: Sync meta description, SEO title, and target keyword</li>
<li>Rank Math: Sync meta description, SEO title, and focus keyword</li>
<li>All SEO fields set via API are automatically synced to the active SEO plugin</li>
</ul>
<h3>API Endpoints</h3>
All endpoints use the namespace <code>vectoron/v1</code>:
<ul>
<li><code>POST /wp-json/vectoron/v1/posts</code> – Create a new post</li>
<li><code>PUT /wp-json/vectoron/v1/posts/{id}</code> – Update an existing post</li>
<li><code>POST /wp-json/vectoron/v1/categories</code> – Create a category</li>
<li><code>POST /wp-json/vectoron/v1/media</code> – Upload media</li>
<li><code>GET /wp-json/vectoron/v1/status</code> – Health check (no auth required)</li>
</ul>
<h3>Authentication</h3>
Three authentication methods are supported:
<ol>
<li>HTTP Basic Auth – Standard username:password</li>
<li>Authorization Header – <code>Authorization: Basic <base64></code></li>
<li>Custom Headers – <code>X-WP-Username</code> and <code>X-WP-Password</code></li>
</ol>
<h3>ACF Sync Header</h3>
When using the native WordPress REST API (<code>/wp-json/wp/v2/posts</code>) instead of the Vectoron custom API, you can trigger ACF sync by adding the <code>X-Vectoron-Sync</code> header:
<pre><code>X-Vectoron-Sync: true
</code></pre>
This is useful when:
<ul>
<li>You want to use WordPress’s native post creation/update endpoints</li>
<li>Your integration already uses the WP REST API</li>
<li>You need features only available in the native API</li>
</ul>
Without this header, native WP REST API requests will NOT trigger ACF sync, ensuring Gutenberg and other WordPress interfaces don’t interfere with ACF content.
<h3>Security Features</h3>
<ul>
<li>Rate limiting (60 requests/minute per IP)</li>
<li>Capability-based permission checks</li>
<li>SSRF protection for URL uploads</li>
<li>Input sanitization and validation</li>
<li>Protected meta key filtering</li>
</ul>

A WordPress REST API plugin for external content management with authenticated API endpoints, GA4 tracking shortcodes, and ACF integration.

5 Star Plugins (Rob)

This plugin tracks form abandonment to the form field level, firing Google Analytics (GA4) events (via ga(‘send’) Javascript calls) using the existing Google Analytics code installed on your site. Each form will be tracked using it’s ID name, with each field using the field name, and each change of the field focus fires an event to Google Analytics tracking whether the field was empty (skipped) or not (completed). Submit is tracked as a separate event as well. In Google Analytics, these events will generate stats on number of fields completed, number skipped, and submits, with percentages, for each form on your web site.
Be sure to give all your forms an ID with a specific name you choose, the events will be sent using the form ID name, and if not set, it will be sent as “form-without-id”, which will not be as useful.
The javascript is loaded into the footer of the site, and uses jQuery to detect the form field focus change, and requires that the Google Analytics (GA4) code is already added to the site.
If this plugin saved you time, please send a <a href="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=R4SE22RQ4CB2E" rel="nofollow ugc">donation</a> with an amount you feel your time is worth, to ensure continued support and encourage future development.
Feel free to submit a <a href="https://wordpress.org/support/view/plugin-reviews/form-abandonment-tracking?rate=5#postform" rel="ugc">rating and review</a>, I’d really appreciate your feedback.
Wish it did something else as well? Use the <a href="https://wordpress.org/support/plugin/form-abandonment-tracking" rel="ugc">Support</a> tab to submit your thoughts.

Form Abandonment Tracking for Google Analytics GA4

Tracks form abandonment to the form field level as Google Analytics GA4 events, including form submits.

Vectoron vs Form Abandonment Tracking for Google Analytics GA4