Franky

<p><strong>Images Sync for Cloudflare</strong> automatically uploads your WordPress images to Cloudflare Images and stores optimized delivery URLs directly in post meta. Perfect for headless setups, JAMstack sites, or anyone who wants fast, globally-distributed images without changing their workflow.</p>
<h4>Why Use This Plugin?</h4>
<p>Headless frontends need stable, cacheable CDN URLs. This plugin makes WordPress the source of truth while Cloudflare Images handles delivery and optimization. No custom resolvers needed — just query the meta field.</p>
<h4>Features</h4>
<ul>
<li><strong>Flexible Mappings</strong> — Map any image source (Featured Image, ACF fields, post meta) to Cloudflare Images with customizable delivery URL storage</li>
<li><strong>Preset System</strong> — Define reusable presets for OG images, thumbnails, heroes, squares — consistent URLs across your site</li>
<li><strong>Preview Studio</strong> — Visually test how images look with different presets before going live</li>
<li><strong>Auto-Sync</strong> — Images sync automatically on post save, or bulk-process existing content via Action Scheduler</li>
<li><strong>Flexible Variants</strong> — Smart detection prevents broken images and 9429 errors</li>
<li><strong>Headless-Ready</strong> — URLs stored in post meta, perfect for GraphQL/REST API consumption</li>
<li><strong>WP-CLI Support</strong> — <code>wp cfimg sync</code> commands for scripted workflows</li>
<li><strong>Secure Storage</strong> — API token encrypted with libsodium (AES-256 fallback)</li>
<li><strong>No Lock-in</strong> — Your images stay in WordPress Media Library; Cloudflare URLs are plain meta values</li>
</ul>
<h4>Security</h4>
<p>Your Cloudflare API token is encrypted at rest using modern cryptography (libsodium or AES-256-CBC with HMAC). The token is never stored in plain text and is only decrypted when making API requests.</p>
<h4>Requirements</h4>
<ul>
<li>Cloudflare account with <a href="https://www.cloudflare.com/products/cloudflare-images/" rel="nofollow ugc">Cloudflare Images</a> subscription</li>
<li>API Token with “Cloudflare Images: Edit” permission</li>
</ul>
<h3>External services</h3>
<p>This plugin optionally connects to external Cloudflare services to upload, manage, and deliver images. No connection is made until the user configures API credentials and explicitly triggers a sync, test, or preview action.</p>
<h4>Cloudflare Images API</h4>
<p>This plugin sends requests to the <a href="https://api.cloudflare.com/" rel="nofollow ugc">Cloudflare API</a> (<code>api.cloudflare.com</code>).</p>
<p>Data sent to Cloudflare (only when the user configures credentials and triggers actions):</p>
<ul>
<li>API token — for authentication (sent as a Bearer token header, never logged or stored in plain text)</li>
<li>Image files — binary content of WordPress media attachments</li>
<li>Image metadata — WordPress attachment ID and a purpose label (e.g. “preview”)</li>
<li>
<p>Configuration updates — Flexible Variants enable/disable flag</p>
</li>
<li>
<p><a href="https://www.cloudflare.com/terms/" rel="nofollow ugc">Cloudflare Terms of Service</a></p>
</li>
<li><a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare Privacy Policy</a></li>
<li><a href="https://developers.cloudflare.com/api/" rel="nofollow ugc">Cloudflare API Documentation</a></li>
</ul>
<h4>Cloudflare Image Delivery</h4>
<p>Delivery URLs use the <a href="https://imagedelivery.net/" rel="nofollow ugc">Cloudflare Image Delivery</a> CDN (<code>imagedelivery.net</code>). These URLs are stored in post meta and served directly to site visitors by their browsers. The plugin itself makes one request to this service to detect Flexible Variants support (canary check).</p>
<p>No visitor data, IP addresses, cookies, or personal information is ever sent to Cloudflare by this plugin.</p>
<ul>
<li><a href="https://www.cloudflare.com/terms/" rel="nofollow ugc">Cloudflare Terms of Service</a></li>
<li><a href="https://www.cloudflare.com/privacypolicy/" rel="nofollow ugc">Cloudflare Privacy Policy</a></li>
<li><a href="https://developers.cloudflare.com/images/" rel="nofollow ugc">Cloudflare Images Documentation</a></li>
</ul>
<h3>Privacy Policy</h3>
<p>This plugin does not collect, store, or transmit any personal user data. Only image files and technical metadata (attachment IDs, image hashes) are sent to Cloudflare.</p>
<h3>Credits</h3>
<p>Developed by <a href="https://301.st" rel="nofollow ugc">301st</a> with <a href="https://claude.ai" rel="nofollow ugc">Claude AI</a>.</p>


Images Sync for Cloudflare

Auto-sync WordPress images to Cloudflare Images. Stores optimized CDN URLs in post meta — ready for headless, ACF, or classic themes.

Joe Fusco

Jason Bahl

<p>WPGraphQL IDE is a next-generation query editor for WPGraphQL, built on WordPress’s component library and CodeMirror 6. It replaces the bundled legacy GraphiQL interface with a faster, more extensible IDE that feels native to wp-admin.</p>
<p><strong>Three ways to open the IDE:</strong></p>
<ul>
<li><strong>Dedicated page</strong> at <code>wp-admin/admin.php?page=graphql-ide</code></li>
<li><strong>Drawer</strong> — slide-up panel triggered from the admin bar, available on every wp-admin and front-end page</li>
<li><strong>Public endpoint mode</strong> (opt-in) — visiting the GraphQL endpoint URL in a browser renders the IDE shell instead of returning JSON. Anonymous visitors get a read-only schema browser; signed-in administrators get the full editor.</li>
</ul>
<p><strong>Editor features:</strong></p>
<ul>
<li>Multi-tab editor with auto-save and overflow tab dropdown</li>
<li>Schema-aware autocomplete, hover-doc tooltips, and inline lint warnings (powered by CodeMirror 6 + cm6-graphql)</li>
<li>Cmd-click navigation from any field, type, or argument straight to the Docs Explorer</li>
<li>Response panes: JSON viewer, table view, status code / duration / size / resolver-count badges, request tracing, query log, N+1 detection</li>
<li>Variables and headers editors with their own autocomplete</li>
<li>Per-document settings (description, alias names, max-age cache hint, allow/deny)</li>
<li>Execution history persisted to localStorage, scoped per WordPress user and IDE context — available to anonymous public-endpoint visitors too</li>
<li>Saved Queries panel with personal collections and share links (when WPGraphQL Smart Cache is also active)</li>
<li>Full keyboard support: Cmd+Enter to execute, Ctrl+Shift+P to prettify, arrow keys to switch tabs</li>
</ul>
<p><strong>What’s new in 5.0:</strong></p>
<ul>
<li><strong>Rebuilt UI</strong> on <code>@wordpress/components</code> and <code>@wordpress/data</code>. The legacy GraphiQL wrapper is gone — see the Upgrade Notice if you have customizations.</li>
<li><strong>Smart Cache integration.</strong> Saved documents now live in <code>wp-graphql-smart-cache</code>‘s <code>graphql_document</code> post type — one canonical primitive for the WPGraphQL ecosystem. The IDE works standalone when Smart Cache isn’t installed; Saved Queries / Document Settings / share links light up when it is.</li>
<li><strong>Three render modes</strong> (above), each individually configurable.</li>
<li><strong>Schema-typed data layer.</strong> Document and collection operations run through WPGraphQL itself instead of the WordPress REST API.</li>
<li><strong>Full internationalization.</strong> Every UI string passes through <code>@wordpress/i18n</code> under the <code>wpgraphql-ide</code> text domain.</li>
<li><strong>Auto-upgrade from 4.x.</strong> Open tabs and query history saved by the legacy GraphiQL UI migrate forward on first 5.0 load.</li>
</ul>
<p>For the complete breaking-change list and 4.x <span aria-hidden="true" class="wp-exclude-emoji">→</span> 5.0 migration guide, see <code>UPGRADE-5.0.md</code> in the plugin or the project’s GitHub releases.</p>
<h3>Privacy Policy</h3>
<p>WPGraphQL IDE uses <a href="https://appsero.com" rel="nofollow ugc">Appsero</a> SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster and make product improvements.</p>
<p>Appsero SDK <strong>does not gather any data by default.</strong> The SDK only starts gathering basic telemetry data <strong>when a user allows it via the admin notice</strong>.</p>
<p>When you opt in, each telemetry request is sent to Appsero and a duplicate is sent in a non-blocking request to WPGraphQL-operated infrastructure at https://telemetry.wpgraphql.com (the same categories of data as described for Appsero below).</p>
<p>Learn more about how <a href="https://appsero.com/privacy-policy/" rel="nofollow ugc">Appsero collects and uses this data</a>.</p>


WPGraphQL IDE

Modern GraphQL IDE for WPGraphQL — schema-aware editor, execution history, saved queries, and a public endpoint mode.

Images Sync for Cloudflare vs WPGraphQL IDE