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.

caspio

<p>The Caspio Deployment Control plugin disables wptexturize and convert_chars filters on the_content for Caspio Bridge PHP SEO deployment support.</p>
<p>This plugin prevents WordPress from modifying the Caspio Bridge SEO deployment code. In order to deploy Caspio Bridge SEO DataPage in WordPress, you must have:</p>
<p>*Caspio Bridge account with activated SEO deployment and properly configured DataPage *Installed and activated a PHP execution plugin for WordPress such as Exec-PHP (https://wordpress.org/extend/plugins/exec-php/).<br />
*Installed and activated the Caspio Deployment Control plugin for WordPress.<br />
*Caspio PHP SEO deploy code for your DataPage placed in your WordPress post or page.</p>
<p>For compatibility with SEO deployment code, the Caspio Deployment Control disables the following WordPress content filters on the_content:</p>
<ul>
<li>wptexturize</li>
<li>convert_chars </li>
</ul>
<p>See details about these filters at <a href="https://codex.wordpress.org/How_WordPress_Processes_Post_Content" title="How WordPress Processes Post Content" rel="nofollow ugc">https://codex.wordpress.org/How_WordPress_Processes_Post_Content</a></p>
<p>For information about Caspio Bridge see the Caspio official site at <a href="http://www.caspio.com" title="Caspio official site" rel="nofollow ugc">http://www.caspio.com</a></p>


Caspio Deployment Control

The Caspio Deployment Control plugin disables wptexturize and convert_chars filters on the_content for Caspio Bridge PHP SEO deployment support.

Posts Bridge – Remote CMS vs Caspio Deployment Control