smoothcdn

<p>Smooth CDN Connector helps you connect WordPress media and site assets to Smooth CDN without changing your publishing workflow.</p>
<p>Use it to sync selected Media Library files, serve assets through CDN URLs, offload media from local storage, restore files when needed, and manage protected asset delivery directly from wp-admin.</p>
<p>The plugin creates or reuses a Smooth CDN connector project for your WordPress site, keeps a local record of asset sync state, and gives you clear admin views for media items, codebase assets, access management, and cleanup workflows.</p>
<p>Smooth CDN Connector is focused on real WordPress files and assets: uploads, generated image sizes, selected media files, and supported JS/CSS assets detected from active themes and plugins.</p>
<p>This plugin does not scan REST API endpoints or generate JSON snapshots. For REST API acceleration, use Smooth API Accelerator.</p>
<h3>Why use Smooth CDN Connector?</h3>
<ul>
<li>🚀 <strong>CDN delivery for WordPress assets</strong> – serve selected media and site assets through Smooth CDN</li>
<li>🖼️ <strong>Media Library workflow</strong> – manage sync state directly from wp-admin</li>
<li>🔁 <strong>URL rewriting</strong> – rewrite uploaded media and detected JS/CSS asset URLs to Smooth CDN</li>
<li>📦 <strong>Media offload</strong> – move synced media away from local storage while keeping restore flows available</li>
<li>🔒 <strong>Protected asset delivery</strong> – protect selected files and grant time-limited access when needed</li>
<li>🧹 <strong>Unused asset review</strong> – monitor synced assets and identify files that may no longer be used</li>
<li>🧩 <strong>Controlled rollout</strong> – choose which assets stay disabled, sync to CDN, or use the enabled-assets workflow</li>
</ul>
<p>Useful for:<br />
* WordPress sites with growing media libraries<br />
* Agencies and developers managing client websites<br />
* Content-heavy sites that want a cleaner asset delivery workflow<br />
* Projects that need CDN delivery without rebuilding the whole site architecture<br />
* Sites that want to offload selected media from local WordPress storage<br />
* Teams that need protected delivery for selected files<br />
* WordPress installations that want better control over synced and unused assets</p>
<h3>How it works</h3>
<ol>
<li>Connect your WordPress site to Smooth CDN using account mode or guest mode</li>
<li>The plugin creates or reuses a connector project for the current site</li>
<li>Smooth CDN Connector indexes WordPress media items and detects supported JS/CSS assets from active themes and plugins</li>
<li>You choose which assets should stay disabled, sync to Smooth CDN, or be managed through the enabled-assets workflow</li>
<li>Synced media files, generated image sizes, and supported codebase assets are uploaded to Smooth CDN</li>
<li>Depending on your settings, assets can stay local, use rewritten Smooth CDN URLs, or be offloaded from local storage</li>
<li>Offloaded media can be restored later from Smooth CDN when needed</li>
</ol>
<h3>Features</h3>
<ul>
<li>Smooth CDN account and guest authentication flows</li>
<li>Automatic connector project creation with type <code>cdn_connector</code></li>
<li>Media Library based asset management instead of endpoint scanning</li>
<li>Indexing for WordPress media files and generated image sizes</li>
<li>Detection of supported codebase JS/CSS assets from active themes and plugins</li>
<li>Manual and scheduled sync for enabled assets</li>
<li>Automatic re-sync when attachments change</li>
<li>URL rewriting for uploaded media and detected JS/CSS assets</li>
<li>Offload mode for synced Media Library files</li>
<li>Restore flow for offloaded media assets</li>
<li>Protected asset delivery with access grant and revoke flows</li>
<li>Unused assets view based on synced assets cross-checked against Smooth CDN usage logs</li>
<li>Access management for protected files</li>
<li>Maintenance tools for sync, unsync, restore, and cleanup workflows</li>
</ul>
<h3>Settings overview</h3>
<p>Key settings that affect sync behavior:</p>
<ul>
<li>Guest connection lets you authenticate the connector without choosing an existing Smooth CDN account session.</li>
<li><code>Auto sync frequency</code> controls how often scheduled WP-Cron sync runs. Available values: <code>hourly</code>, <code>daily</code>, <code>weekly</code>.</li>
<li><code>Asset mode</code> controls whether synced assets stay local, use rewritten URLs, or whether synced Media Library files are offloaded after upload.</li>
<li><code>Custom subdomain</code> lets you use your Smooth CDN custom subdomain when the connected plan supports it.</li>
</ul>
<p>When <code>Asset mode</code> is changed to offload, the plugin syncs enabled media and can remove local Media Library files after upload. When offload is turned off, the plugin restores local media files from Smooth CDN.</p>
<h3>External services</h3>
<p>This plugin connects to Smooth CDN to authenticate the site, create or reuse a connector project, upload and delete synced media assets, manage protected asset access, and optionally restore offloaded files from Smooth CDN URLs.</p>
<p>When you connect the plugin, it sends your site domain to Smooth CDN so the service can authenticate the session and create or reuse the related connector project.</p>
<p>When you sync media, it sends selected media files and related asset metadata such as filenames, paths, hashes, protection settings, and project identifiers to Smooth CDN so the assets can be uploaded, updated, delivered, and managed.</p>
<p>When you revoke, grant, or inspect protected asset access, it sends the relevant project identifiers, access identifiers, recipient email address, selected asset paths, and optional expiration date to Smooth CDN to manage protected delivery.</p>
<p>When local offload restore is used, the plugin downloads the previously synced asset file from its Smooth CDN delivery URL back to your WordPress uploads directory.</p>
<p>This service is provided by Smooth CDN:<br />
Terms of Service: https://smoothcdn.com/terms<br />
Privacy Policy: https://smoothcdn.com/privacy</p>
<h3>License</h3>
<p>GPLv2 or later</p>


Smooth CDN Connector

Sync, offload, protect, and deliver WordPress media and site assets through Smooth CDN.

Dominik Schilling

benlumley

<p>Filename based cache busting for WordPress scripts/styles using last modified date.</p>
<p>Stop telling clients or users to hard refresh / shift refresh. The url to all of the css/js files on your site will change automatically whenever the files are modified. You can set proper long cache lifetimes to help get top scores on Google Pagespeed without running into cached css/javascript problems.</p>
<p>Based on this gist https://gist.github.com/ocean90/1966227 from Dominik Schilling, I’ve enhanced it by automatically replacing the asset version with the files modification time and automatically editing htaccess – making it install + forget.</p>
<p>Includes querystring option as a fallback – which works in more scenarios.</p>
<h3>Webservers</h3>
<h4>Apache</h4>
<p>The plugin should add what it needs to your .htaccess file jsut like WP itself. But if for any reason that doesn’t work for you – here’s what it adds:</p>
<pre><code># FBACB
<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /

  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.+)\.([0-9\.]+)\.(js|css)$ $1.$3 [L]
</IfModule>

# still fbacb
<IfModule mod_expires.c>
    ExpiresActive on
    ExpiresByType text/css                            "access plus 1 year"
    ExpiresByType application/javascript              "access plus 1 year"
</IfModule>
# END FBACB
</code></pre>
<h4>NGINX</h4>
<pre><code> location ~* ^(.+)\.(?:\d+)\.(min.js|min.css|js|css)($|\?.*$) {
   try_files $uri $1.$2;
 }
</code></pre>
<h3>Host specific notes</h3>
<p>Some webhosts need a bit of custom config to get the filename based urls working.</p>
<h4>WP Engine</h4>
<p>To work on WP-Engine, you’ll need the following redirect added via my.wpengine -> installname -> Redirect rules</p>
<pre><code> Source: ^(.+)\.([0-9\.]+)\.(js|css)$
 Dest: $1.$3
 Type: break (this is under advanced)
</code></pre>
<h4>CloudWays</h4>
<p>Just works.</p>
<h4>Flywheel</h4>
<p>Just works.</p>
<h4>PHP Fallback</h4>
<p>If your webserver is failing to serve assets using url rewriting, the plugin attempts to serve them itsef (ie: via PHP). Obviously this is slow/less than ideal in production (it’ll be much slower) – so you should configure your web server correctly to serve the files. If you see this HTTP header “FBACB-Php-Fallback: yes” on your assets, this applies to you.</p>
<p>Note that hosts are increasingly configured to serve css/js directly from disk and won’t fall back to PHP + WordPress error handling – this fallback then won’t work.</p>


Filename based asset cache busting

Filename based cache busting for WordPress scripts/styles using last modified date.

Smooth CDN Connector vs Filename based asset cache busting