Còdec

<p>Bridge your posts collections with your backend over HTTP APIs, enabling remote and automated web content management.</p>
<h3>How it works</h3>
<p>Posts Bridge treats post collections as indexes that represents your backend data and allow you to use Gutenberg, WordPress’ powerful page builder, as the frontend editor of your backend. Whether through manual or automatic synchronization —using ahead-of-time or live fetches— Posts Bridge fully integrates your backend data into the WordPress CMS system.</p>
<h3>Bridges</h3>
<p>Think of a bridge as a mapping that bounds your backend data with a post type collection on your WordPress web page. Each item on your backend database can be converted to a post, and each field on your backend tables can be mapped to a post field or taxonomy. Once a bridge is configured, you can trigger manual synchronizations, or let Posts Bridge automatically synchronize content between the two sides on the background.</p>
<h3>Addons</h3>
<p>Posts Bridge comes with free addons. Each addon adds to the plugin new bridges to work with specific APIs and bridge templates.</p>
<p>Posts Bridge has the following addons:</p>
<ul>
<li><a href="https://en.wikipedia.org/wiki/REST" rel="nofollow ugc">REST API</a></li>
<li><a href="https://wiki.dolibarr.org/index.php/Module_Web_Services_API_REST_(developer)" rel="nofollow ugc">Dolibarr</a></li>
<li><a href="https://workspace.google.com/products/sheets/" rel="nofollow ugc">Google Sheets</a></li>
<li><a href="https://www.odoo.com/" rel="nofollow ugc">Odoo</a></li>
<li><a href="https://developer.wordpress.org/rest-api/" rel="nofollow ugc">WP</a></li>
</ul>
<h3>Backends</h3>
<p>In Posts Bridge, a backend is a set of configurations that handles the information required to get your posts synchronized over HTTP requests with remote systems.</p>
<p>To register a new backend you only have to set 3 fields:</p>
<ol>
<li>A unique name for the new connection</li>
<li>The URL of your backend</li>
<li>An array of HTTP headers with connection metadata and credentials</li>
<li>Optional, an HTTP authentication credential (Basic, Bearer, etc)</li>
</ol>
<p>Once registered, you can reuse your backend connection on your post bridges.</p>
<h3>Remote Mappers</h3>
<p>Remote mappers allow you to mutate your backend’s API responses to match the WordPress post model (e.g., <code>post_title</code>, <code>post_content</code>, <code>post_name</code>). This enable automatic conversion of backend data into WordPress posts on each synchronization loop (ahead-of-time).</p>
<p>With mappers you can map backend data to post fields, custom fields and into taxonomy terms (such as categories and tags).</p>
<h3>Remote Field</h3>
<p>If you want your backend data loaded dynamically on each render, you can use the <strong>Remote Field</strong> custom block. This block lets you designate parts of your post templates as remote content. On render time, this blocks will be replaced with the data fetched from the backend.</p>
<h3>Templates</h3>
<p>To streamline the bridge setup process, Posts Bridge comes packed with templates. Templates are blueprints of bridges you can use to set up your integrations in a matter of minutes.</p>
<h3>Docs</h3>
<p>Browse the plugin’s documentation on <a href="https://postsbridge.codeccoop.org" rel="nofollow ugc">postsbridge.codeccoop.org</a>.</p>
<h3>Links</h3>
<ul>
<li><a href="https://postsbridge.codeccoop.org" rel="nofollow ugc">Official website</a></li>
<li><a href="https://gitlab.com/codeccoop/wp/plugins/posts-bridge/" rel="nofollow ugc">Gitlab</a></li>
<li><a href="https://www.codeccoop.org" rel="nofollow ugc">Còdec</a></li>
<li><a href="https://profiles.wordpress.org/codeccoop/#content-plugins" rel="nofollow ugc">Other plugins</a></li>
</ul>


Posts Bridge – Remote CMS

Bridge your posts collections with your backend over HTTP APIs, enabling remote and automated web content management.

x0DSR

<p>WP2SMFBridge is a simple one way bridge from WordPress to Simple Machine Forum (v2 tested). This means, this one uses databases of SMF Forum and sync to WP database every time a user performs login or logout action in WP. To get this working only use WP to register/login/logout. Also, WP and SMF must be installed in same domain, and should not be being accessed through a subdomain, though it still work. For example, if your website contains of WordPress for news and SMF for forum, if your news is mydomain.com, then your forums should be somewhere like mydomain.com/forum.</p>
<p>This plugin will do these following tasks:</p>
<ul>
<li>If a user log in WP, then that user will be logged in SMF.</li>
<li>If a user logout in WP, then that user will be logout in SMF.</li>
<li>If a user created/register/change password in WP, those actions happen on SMF!</li>
<li>Users that are created in SMF can be used once disabled WP plugin.</li>
<li>For a full way integration use with SMF2WPBridge plugin.<br />
https://github.com/xchwarze/SMF2WPBridge<br />
http://custom.simplemachines.org/mods/index.php?mod=4030</li>
</ul>
<h3>Notes</h3>
<p>Every time a user logged in SMF forum, same username (will be created if not exist) will be logged in  WordPress. Because SMF is placed in higher order, so user in WordPress will be changed to SMF with same role.</p>
<p>For example, you have an administrator named “admin” in wordpress, after WP2SMFBridge fully activated, the SMF user named “admin” can login as that administrator. So be careful!</p>


WP2SMFBridge

Login bridge from Wordpress to Simple Machine Forum.

Posts Bridge – Remote CMS vs WP2SMFBridge