glindr

Glindr is a fast growing repository of content in the fashion blogging space. Now, you can be a part of it 
with the Glindr plugin.
The Glindr plugin allows you to quickly and easily apply for syndication to Glindr. Once you submit your request, 
a Glindr administrator will review your information and Approve or Decline your site. You can keep track of your 
application status right from your blog.
After your request is approved, you’ll be able to easily submit your content to Glindr for syndication and reap 
all the benefits.

Glindr

Apply for access and start syndicating your posts to Glindr today!

Sylwester Ulatowski

Post Forwarder lets you syndicate content from one WordPress site to any combination of destinations with a single click at publish time — or schedule it ahead with the built-in calendar. Configure as many portals as you need and choose per-post which ones receive each article.
Supported Destinations
<ul>
<li>WordPress sites — forwards via the REST API with taxonomy mapping, featured image upload, ACF field support, and duplicate prevention. One-click authorization using WordPress Application Passwords, or enter credentials manually.</li>
<li>LinkedIn — posts as a link-share article card with your excerpt, featured image thumbnail, and hashtags auto-generated from your WordPress post tags. Supports personal profiles and organisation pages. One-click connect — no configuration required.</li>
<li>X (Twitter) — posts the title and post URL as a tweet; the featured image attaches directly on paid API tiers or appears as a link preview card. Connect with your own free X developer app.</li>
</ul>
Plan ahead with the content calendar
Post Forwarder includes a built-in weekly calendar so you can do more than fire-and-forget on publish. Schedule posts to go out to your connected channels at the time that suits you, see everything that’s queued at a glance, and manage upcoming posts across all your WordPress sites, LinkedIn, and X from one screen. Great for keeping a steady publishing rhythm without babysitting the clock.
WordPress forwarding highlights
<ul>
<li>One-click “Save & Connect with WordPress” using the built-in Application Password flow.</li>
<li>Taxonomy mapping with automatic fallback to tags.</li>
<li>Featured image, ACF fields, and custom post types are carried across.</li>
<li>Duplicate prevention so the same post is never forwarded twice.</li>
</ul>
LinkedIn highlights
<ul>
<li>Zero-configuration connect — click “Connect with LinkedIn” and authorize in one step.</li>
<li>Featured image is uploaded directly to LinkedIn and shown as the article thumbnail.</li>
<li>WordPress post tags become LinkedIn hashtags automatically (the tag “my topic” becomes #MyTopic).</li>
<li>Supports personal profiles and organisation pages.</li>
<li>Token expiry is shown in settings, with a reconnect prompt before it lapses.</li>
</ul>
Compatibility
Tested with WordPress 7.0 and PHP 8.3.
<h3>Platform Requirements & Limitations</h3>
<h4>WordPress</h4>
<ul>
<li>The destination site must run WordPress 5.6+ with the REST API enabled (default).</li>
<li>The connecting user must have at least the Editor role on the destination site.</li>
<li>Use “Save & Connect with WordPress” for one-click Application Password authorization, or enter a username and Application Password manually.</li>
</ul>
<h4>LinkedIn</h4>
<ul>
<li>No extra configuration required — one-click connect handles sign-in.</li>
<li>LinkedIn access tokens expire after 60 days. The plugin shows the expiry date and prompts you to reconnect.</li>
<li>For organisation page posts set the Author URN to <code>urn:li:organization:YOUR_ORG_ID</code>. You’ll also need the Community Management API product approved on the LinkedIn app (not needed for personal profile posts).</li>
<li>LinkedIn needs the post URL to be publicly reachable to show an article card. Posts from localhost or <code>.local</code>/<code>.test</code> domains fall back to image-only or text+URL mode.</li>
</ul>
<h4>X (Twitter)</h4>
You need a free X developer account to post tweets. X limits write access per developer app, so each plugin user connects their own app.
Step 1 — Create an X developer account (one-time)
<ol>
<li>Go to <a href="https://developer.x.com" rel="nofollow ugc">developer.x.com</a> and sign in with your X account.</li>
<li>Click Sign up and agree to the terms — your developer account is created instantly.</li>
</ol>
Step 2 — Create an app and get credentials
<ol>
<li>In the <a href="https://console.x.com" rel="nofollow ugc">Developer Portal</a> go to Apps and click Create App.</li>
<li>Give it any name (e.g. “My Post Forwarder”).</li>
<li>Open the app, click Keys & Tokens then User authentication settings then Set up.</li>
<li>Set:
<ul>
<li>App permissions: Read and write</li>
<li>Type of App: Web App, Automated App or Bot</li>
<li>Callback URI: the callback URL shown in the plugin’s X portal settings</li>
<li>Website URL: your site URL</li>
</ul>
</li>
<li>Click Save and copy the Client ID and Client Secret (the secret is shown only once).</li>
</ol>
Step 3 — Connect in the plugin
<ol>
<li>In Post Forwarder -> Settings -> Connection Configuration, add an X portal.</li>
<li>Enter the Client ID and Client Secret you copied.</li>
<li>Click Save Portals, then click Save & Connect with X.</li>
<li>Authorize the app on X and you are redirected back with a “Connected” badge.</li>
</ol>
Notes: 
* The free tier allows 1,500 tweet writes per month. Each user’s app has its own separate quota. 
* X access tokens are long-lived and refreshed automatically before expiry. 
* Featured images on the free tier appear as link preview cards (public sites only), not as direct attachments. The X Basic plan enables direct image upload.
<h3>External Services</h3>
Post Forwarder only sends data when you choose to connect an account or forward a post — nothing is sent in the background.
To publish to LinkedIn or X (Twitter), the plugin uses a small open-source connection helper to handle the secure sign-in step, then sends the post you’re forwarding (such as its title, link, and image) to the network you connected. WordPress-to-WordPress forwarding talks only to the site you set up.
You stay in control: connect or disconnect any destination at any time, and advanced users can self-host the connection helper. Each network’s handling of the content you send is governed by its own terms:
<ul>
<li>LinkedIn — <a href="https://www.linkedin.com/legal/user-agreement" rel="nofollow ugc">Terms</a> · <a href="https://www.linkedin.com/legal/privacy-policy" rel="nofollow ugc">Privacy</a></li>
<li>X (Twitter) — <a href="https://twitter.com/en/tos" rel="nofollow ugc">Terms</a> · <a href="https://twitter.com/en/privacy" rel="nofollow ugc">Privacy</a></li>
</ul>
<h3>Technical Notes</h3>
Security: 
* OAuth tokens are stored in the WordPress database. Enable at-rest encryption on your host for best protection. 
* Sensitive fields (access tokens, client secrets, passwords) are never echoed back to the browser — submitting a blank field preserves the saved value. 
* All form inputs are sanitized and validated; WordPress nonces protect all forms and OAuth callbacks.
Tested with: 
* WordPress 7.0 
* PHP 8.3
Minimum Requirements: 
* WordPress 5.6+ 
* PHP 7.4+

Post Forwarder

Forward WordPress posts to other WordPress sites, LinkedIn, and X — automatically on publish or scheduled from a built-in content calendar.

Glindr vs Post Forwarder