Sylwester Ulatowski

<p>Post Forwarder is a powerful WordPress plugin that allows you to automatically Forward posts to multiple WordPress sites using the REST API. Perfect for content syndication, multi-site networks, or distributing content across related websites.</p>
<p><strong>Key Features:</strong></p>
<ul>
<li><strong>Multi-Portal Support</strong>: Configure multiple destination WordPress sites</li>
<li><strong>Taxonomy Intelligence</strong>: Automatically maps custom taxonomies or falls back to regular tags</li>
<li><strong>Featured Image Transfer</strong>: Uploads and sets featured images on destination sites</li>
<li><strong>Custom Post Type Support</strong>: Works with any public post type</li>
<li><strong>Duplicate Prevention</strong>: Smart locking mechanism prevents duplicate posts</li>
<li><strong>ACF Integration</strong>: Transfers Advanced Custom Fields data</li>
<li><strong>Flexible Configuration</strong>: Easy-to-use interface or advanced JSON configuration</li>
<li><strong>Selective pushing</strong>: Choose which portals to push each post to</li>
<li><strong>Draft or Publish</strong>: Configure whether pushed posts are published or saved as drafts</li>
</ul>
<p><strong>How It Works:</strong></p>
<ol>
<li>Configure your destination WordPress sites (portals) with their REST API credentials</li>
<li>When editing a post, select which portals to push the post to</li>
<li>Upon saving, the plugin automatically pushs the post with all its content, taxonomies, meta fields, and featured image</li>
<li>Smart taxonomy mapping tries to preserve custom taxonomies, falling back to regular tags if needed</li>
</ol>
<p><strong>Perfect For:</strong></p>
<ul>
<li>News networks with multiple websites</li>
<li>Content syndication between related sites</li>
<li>Multi-brand companies sharing content</li>
<li>Blog networks and content distribution</li>
<li>Development/staging to production workflows</li>
</ul>
<p><strong>Technical Requirements:</strong></p>
<ul>
<li>WordPress REST API enabled on destination sites</li>
<li>Application passwords configured for API access</li>
<li>PHP 7.4 or higher</li>
</ul>
<h3>Technical Notes</h3>
<p><strong>REST API Endpoints Used:</strong><br />
* <code>/wp-json/wp/v2/posts</code> – For standard posts<br />
* <code>/wp-json/wp/v2/{post_type}</code> – For custom post types<br />
* <code>/wp-json/wp/v2/media</code> – For featured image uploads</p>
<p><strong>Security:</strong><br />
* All data is properly sanitized and validated<br />
* Uses WordPress nonces for form security<br />
* Application passwords for secure API authentication<br />
* No data is stored insecurely</p>
<p><strong>Performance:</strong><br />
* Minimal impact on site performance<br />
* Efficient transient-based duplicate prevention<br />
* Optimized API calls with proper error handling<br />
* Smart taxonomy processing to reduce API calls</p>
<h3>Support</h3>
<p>For support, feature requests, or bug reports, please visit the plugin’s support forum or GitHub repository.</p>
<p><strong>Minimum Requirements:</strong><br />
* WordPress 5.0+<br />
* PHP 7.4+<br />
* REST API enabled on destination sites<br />
* Application passwords configured for API access</p>


Post Forwarder

Forward posts to multiple WordPress sites via REST API with smart taxonomy mapping, featured image support, and duplicate prevention.

usielriedl

<p>Sparkling Appcast is a WordPress plugin. It allows you to use your WordPress site to distribute your macOS App via <a href="https://sparkle-project.org/" rel="nofollow ugc">Sparkle</a>. Sparkling Appcast supports multiple channels (alpha, beta, …).</p>
<p>Sparkling Appcast exposes a new shortcode to display a list of app builds.</p>
<pre><code>[sappcast_display_builds sappcast_channel="{channel-id-or-slug}"]
</code></pre>
<p>Configure Sparkle to ingest the appcast.xml at https://your.site/wp-json/sparkling-appcast/v1/appcast.xml. You will see something like the following XML.</p>
<pre><code><rss xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
    <channel>
        <title>MyApp</title>
        <link>/wp-json/sparkling-appcast/v1/appcast.xml</link>
        <item>
            <title>Version 1.0.1 (2)</title>
            <description><![CDATA[ This version is better but not yet released! ]]></description>
            <sparkle:channel>Alpha</sparkle:channel>
            <sparkle:version>2</sparkle:version>
            <sparkle:shortVersionString>1.0.1</sparkle:shortVersionString>
            <pubDate>Wed, 08 Jan 2025 08:56:19 +0000</pubDate>
            <sparkle:minimumSystemVersion>14.0</sparkle:minimumSystemVersion>
            <enclosure url="http://localhost:8088/wp-content/uploads/2025/01/app_v2.zip" length="4713394" type="application/octet-stream"/>
        </item>
        <item>
            <title>Version 1.0.0 (1)</title>
            <description><![CDATA[ - New features - New bugs ]]></description>
            <sparkle:version>1</sparkle:version>
            <sparkle:shortVersionString>1.0.0</sparkle:shortVersionString>
            <pubDate>Wed, 08 Jan 2025 07:43:06 +0000</pubDate>
            <sparkle:minimumSystemVersion>14.0</sparkle:minimumSystemVersion>
            <enclosure url="http://localhost:8088/wp-content/uploads/2025/01/app_v1.zip" length="4713394" type="application/octet-stream"/>
        </item>
    </channel>
</rss>
</code></pre>
<h3>Configuration</h3>
<p>To get started name the application you want to distribute on your WordPress site. You can find the settings page under the App Builds menu.</p>
</p>
<p>If you have multiple channels besides <code>stable</code>, you can should add them on wp-admin under the App Builds menu.</p>
</p>
<h3>Usage</h3>
<h3>Fastlane</h3>
<p>We recommend you use the <a href="https://github.com/Usiel/fastlane-plugin-wp_sparkling_appcast" rel="nofollow ugc"><code>wp_sparkling_appcast</code> plugin</a> to upload assets and create builds.</p>
<h3>Other</h3>
<p>To distribute a new build, you must upload the asset (1), create a build draft (2), after which you can finalize the build and publish it (3). Steps 1 and 2 are typically executed by your build server, while step 3 is done by a human.</p>
<h3>1. Uploading Asset</h3>
<pre><code>curl --location "localhost:8088/wp-json/wp/v2/media?status=publish&title=MyApp%20${VERSION}%20(${BUILD_NUMBER})" \
    --header "Content-Disposition: attachment; filename=\"myapp_v${VERSION}_${BUILD_NUMBER}.zip\"" \
    --header 'Content-Type: application/zip' \
    --user "${USER}:${APPLICATION_PASSWORD}" \
    --data-binary '@/path/to/asset.zip'
</code></pre>
<h3>2. Create Build Draft</h3>
<pre><code>curl --location 'localhost:8088/wp-json/wp/v2/sappcast_app_build' \
    --header 'Content-Type: application/json' \
    --user "${USER}:${APPLICATION_PASSWORD}" \
    --data '{
        "meta": {
            "sappcast_app_build_version": string,
            "sappcast_app_build_number": int,
            "sappcast_app_build_min_system_version": string,
            "sappcast_app_build_attachment_id": int,
            "sappcast_app_build_changelog": string,
        },
        "sappcast_channel": int,
        "status": "draft"
    }'
</code></pre>
<h3>3. Publish Build</h3>
<p>The user may now go to “App Build” on wp-admin and publish the draft after verifying the build. After publishing the build will appear on the relevant appcast (<code>/wp-json/sparkling-appcast/v1/appcast.xml</code>).</p>


Sparkling Appcast

Sparkling Appcast allows you to use your WordPress site to distribute your macOS App via Sparkle offering an appcast.xml endpoint.

Post Forwarder vs Sparkling Appcast