wpopal

KhanhHV

<p>Boost your media workflow in WordPress using S3-compatible object storage. This plugin allows you to offload media files to Amazon S3 for better performance and scalability. Optionally, you can configure Amazon CloudFront as a CDN to serve your media files faster.</p>
<h3>Features:</h3>
<p><strong>Main Features</strong>:<br />
– <strong>Manual or Automatic Media Scan</strong>: Scan your media library manually or automatically using WP-Cron. You can configure the cron schedule to fit your needs.<br />
– <strong>Manual or Automatic Upload</strong>: Upload scanned media files to S3 manually or automatically, with customizable scheduling similar to the scan feature.<br />
– <strong>CloudFront Integration</strong>: Easily integrate Amazon CloudFront to serve media files via CDN, improving delivery speed.<br />
– <strong>Post Type Filtering</strong>: Support scanning and uploading media files associated with specific post types only.<br />
– <strong>WP CLI Support</strong>: Provides WP CLI commands for fast and bulk operations if you have command line access.</p>
<p><strong>Configuration Required</strong>:<br />
– <strong>AWS S3 Access key:</strong>: Access key provided by S3 Service.<br />
– <strong>AWS S3 Secret key:</strong>: Secret key provided by S3 Service.<br />
– <strong>Bucket Name</strong>: The name of your S3 bucket where media files will be stored.<br />
– <strong>Region</strong>: The AWS region where your S3 bucket is located.<br />
– <strong>CloudFront URL (Optional)</strong>: If you use Amazon CloudFront, provide the distribution URL for faster delivery.</p>
<p><a href="https://wpopal.com/contact/" rel="nofollow ugc">Free Support</a></p>
<h3>External Services</h3>
<p>This plugin connects to Amazon S3 and optionally Amazon CloudFront to offload and serve media files. Below is detailed information about the external services:</p>
<ol>
<li>
<p><strong>Service Name</strong>: Amazon S3 (amazon.com)</p>
<ul>
<li><strong>Purpose</strong>: Used to store and serve media files (images, videos, documents, etc.) uploaded to the WordPress media library.</li>
<li><strong>Data Sent</strong>: Media files (e.g., images, videos, documents) and metadata (e.g., file names, paths) are sent to the configured S3 bucket.</li>
<li><strong>When</strong>: Data is sent when a file is uploaded to the WordPress media library or when the plugin syncs existing files to S3.</li>
<li><strong>Configuration Required</strong>:
<ul>
<li>Bucket Name</li>
<li>AWS Region</li>
</ul>
</li>
<li><strong>Terms of Service</strong>: <a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">Amazon S3 Terms of Service</a></li>
<li><strong>Privacy Policy</strong>: <a href="https://aws.amazon.com/privacy/" rel="nofollow ugc">Amazon Privacy Policy</a></li>
</ul>
</li>
<li>
<p><strong>Optional Service</strong>: Localstack (for testing environments localstack.cloud)</p>
<ul>
<li><strong>Purpose</strong>: Simulates Amazon S3 locally for testing purposes.</li>
<li><strong>Data Sent</strong>: Media files and metadata are sent to the Localstack instance running on the developer’s machine.</li>
<li><strong>When</strong>: Data is sent when <code>OAWS_LOCALSTACK_MODE</code> is set to <code>true</code> in the plugin configuration.</li>
<li><strong>Configuration</strong>: To enable Localstack, set the constant <code>OAWS_LOCALSTACK_MODE</code> to <code>true</code> in your WordPress configuration file.</li>
<li><strong>Documentation</strong>: <a href="https://docs.localstack.cloud/" rel="nofollow ugc">Localstack Documentation</a></li>
</ul>
</li>
<li>
<p><strong>Optional Service</strong>: Amazon CloudFront (if configured)</p>
<ul>
<li><strong>Purpose</strong>: Used as a Content Delivery Network (CDN) to serve media files faster by caching them closer to users.</li>
<li><strong>Data Sent</strong>: URLs of media files stored in S3.</li>
<li><strong>When</strong>: Data is sent when the plugin generates URLs for media files.</li>
<li><strong>Configuration Required</strong>:
<ul>
<li>CloudFront Distribution URL</li>
</ul>
</li>
<li><strong>Terms of Service</strong>: <a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">Amazon CloudFront Terms of Service</a></li>
<li><strong>Privacy Policy</strong>: <a href="https://aws.amazon.com/privacy/" rel="nofollow ugc">Amazon Privacy Policy</a></li>
</ul>
</li>
</ol>


Opal Sync Media to Amazon S3

This plugin uploads files from the WordPress media directory to an AWS S3 bucket and replaces their original URLs with the corresponding S3 or CloudFr …

Takayuki Miyauchi

Okamoto Hidetaka

AMIMOTO

DigitalCube Inc.

wokamoto

John Blackbourn

Bartosz Gadomski

Hinaloe

Sander van Dragt

jepser

<p>This is simple plugin that clear all cloudfront cache if you publish posts.<br />
You can easy use CloudFront in front of WordPress.</p>
<h3>Fixtures</h3>
<ul>
<li>
<p>wp_is_mobile()<br />
Check device viewer type by CloudFront header.<br />
Now supports <code>HTTP_CLOUDFRONT_IS_MOBILE_VIEWER</code> and <code>HTTP_CLOUDFRONT_IS_TABLET_VIEWER</code>.</p>
</li>
<li>
<p>preview url<br />
In preview page, plugin add <code>post_date</code> query to avoid CloudFront cache.<br />
And set <code>wordpress_loginuser_last_visit</code> cookie for avoid CloudFront cache too.</p>
</li>
</ul>
<p>The <code>wordpress_loginuser_last_visit</code> cookie will be removed if user sign out.</p>
<h4>Invalidation(Clear Cache) Page URL</h4>
<p>This plugin send following page url to CloudFront Invalidation API.</p>
<ul>
<li>TOP page URL</li>
<li>Published Post Page URL</li>
<li>Category Archive Page URL</li>
</ul>
<h3>AWS IAM Policy Example</h3>
<pre><code>{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudfront:GetDistribution",
                "cloudfront:ListInvalidations",
                "cloudfront:GetStreamingDistribution",
                "cloudfront:GetDistributionConfig",
                "cloudfront:GetInvalidation",
                "cloudfront:CreateInvalidation"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}
</code></pre>
<p><strong>Note:</strong> The <code>cloudfront:GetInvalidation</code> permission is required for viewing detailed invalidation information. If this permission is not granted, the detail view feature will be disabled gracefully without affecting other plugin functionality.</p>
<h3>Adding your configuration through env vars</h3>
<p>The plugin can be configured by defining the following variables:</p>
<ul>
<li><code>AWS_ACCESS_KEY_ID</code></li>
<li><code>AWS_SECRET_ACCESS_KEY</code></li>
<li><code>C3_DISTRIBUTION_ID</code></li>
</ul>
<p>You can put these variables like the code into the wp-config.php</p>
<pre><code>php
define( 'AWS_ACCESS_KEY_ID', '' );
define( 'AWS_SECRET_ACCESS_KEY', '' );
define( 'C3_DISTRIBUTION_ID', '' );
</code></pre>
<h3>Cookie</h3>
<p>This plugin set a Cookie named <code>wordpress_loginuser_last_visit</code> to the user.<br />
It prevents CDN caching when the user is previewing his posts or contents.<br />
Once logging out from Dashboard, plugin removes this cookie from user.</p>
<h3>7.1.0</h3>
<ul>
<li>[Feature] Add invalidation detail view with modal popup showing invalidation paths, caller reference, and status</li>
<li>[Fix] Fix invalid path returned for post type without archive page</li>
</ul>
<h3>7.0.1</h3>
<ul>
<li>[Update] Improved AWS API call processing for better security and PHP 8.x compatibility</li>
</ul>
<h3>7.0.0</h3>
<ul>
<li>[Breaking Change] Remove AWS SDK dependency and implement custom HTTP CloudFront API client</li>
<li>[Update] Add comprehensive invalidation logging with c3_log_invalidation_list filter</li>
<li>[Update] Add configurable CloudFront region and HTTP timeout settings</li>
</ul>
<h3>6.1.6</h3>
<ul>
<li>[Fix] Fixed PHP 8 syntax errors by adding nullable type hints</li>
<li>[Fix] Fixed deprecation warnings about creation of dynamic properties in Invalidation_Service.php</li>
<li>[Fix] Fixed deprecation warnings about creation of dynamic properties in Cron_Service.php</li>
<li>[Fix] Fixed PHP 7.4 syntax errors in test files</li>
</ul>
<h3>6.1.5</h3>
<ul>
<li>[Fix] Changed to install the AWS SDK using composer instead of aws.phar.</li>
</ul>
<h3>6.1.4</h3>
<ul>
<li>[Update] Support post_type_archive_link</li>
</ul>
<h3>6.1.3</h3>
<ul>
<li>[Fix] Lost filter c3_invalidation_items From v6.0.0</li>
</ul>
<h3>6.1.2</h3>
<ul>
<li>[Fix] php version compare issue</li>
</ul>
<h3>6.1.1</h3>
<ul>
<li>[Fix] Plugin deactivation issue</li>
</ul>
<h3>6.1.0</h3>
<ul>
<li>[Update] Flush cache by post_ids</li>
</ul>
<h3>6.0.0</h3>
<ul>
<li>[Breaking Change] Re-write entire code</li>
<li>[Update] Add <code>c3_log_cron_invalidation_task</code> filter to show cron job Logs</li>
<li>[Update] Add <code>c3_aws_sdk_path</code> filter to change or remove bundled AWS SDK path</li>
</ul>
<h3>5.5.1</h3>
<ul>
<li>[Update] Replace the top level menu with a Settings submenu</li>
</ul>
<h4>5.5.0</h4>
<ul>
<li>[Update] Can use defined variables for AWS Credentials</li>
</ul>
<h4>5.4.2</h4>
<ul>
<li>[Bug fix] Set cookie path in preview page</li>
</ul>
<h4>5.4.1</h4>
<ul>
<li>[Bug fix] Undefined Paths index in invalidation query cron event</li>
</ul>
<h4>5.4.0</h4>
<ul>
<li>[Update] Update preview fix plugin</li>
</ul>
<h4>5.3.4</h4>
<ul>
<li>[Bug fix] Small bug fix</li>
</ul>
<h4>5.3.3</h4>
<ul>
<li>[Change SDK] replace sdk</li>
</ul>
<h4>5.3.2</h4>
<ul>
<li>[Bug fix] Use EC2 role if using as AMIMOTO Managed hosting</li>
</ul>
<h4>5.3.1</h4>
<ul>
<li>[Add filter] Can select AWS SDK version by filter</li>
</ul>
<h4>5.3.0</h4>
<ul>
<li>[Update SDK] Use AWS SDK v3 when you using php 5.6 or later</li>
</ul>
<h4>5.2.1</h4>
<ul>
<li>[For AMIMOTO Managed] bug fix to run by WP-CLI</li>
</ul>
<h4>5.2.0</h4>
<ul>
<li>[Add filter] We can disable to register wp-cron that retry request invalidation.</li>
<li>[Readme] Update readme to see IAM Policy example.</li>
</ul>
<h4>5.1.0</h4>
<ul>
<li>[Update preview fixture] Set cookie to avoid CloudFront cache if user sign in</li>
<li>[Update preview fixture] Unset cookie for avoide CloudFront cache if user sign out</li>
</ul>
<h4>5.0.0</h4>
<ul>
<li>Support CloudFront viewer params on <code>wp_is_mobile()</code>.(4.9.0 or later)</li>
</ul>
<h4>4.4.0</h4>
<ul>
<li>Fix small bug</li>
<li>Add some feature for AMIMOTO Managed hosting user</li>
</ul>
<h4>4.3.1</h4>
<ul>
<li>Fix cron interval</li>
<li>add filters <code>'c3_invalidation_interval</code>, <code>c3_invalidation_cron_interval</code>, <code>c3_invalidation_item_limits</code>.</li>
<li>update default invalidation interval & items.</li>
</ul>
<h4>4.3.0</h4>
<ul>
<li>Schedule cron event if you published many post at the same time</li>
</ul>
<h4>4.2.1</h4>
<ul>
<li>Fix ‘c3_credential’ filter position</li>
</ul>
<h4>4.2.0</h4>
<ul>
<li>Support AMIMOT Dashboard</li>
</ul>
<h4>4.1.0</h4>
<ul>
<li>Show Invalidation Logs</li>
</ul>
<h4>4.0.3</h4>
<ul>
<li>Auto Deploy by Travis</li>
</ul>
<h4>4.0.2</h4>
<ul>
<li>Add WP-CLI param check ( wp c3 flush)</li>
<li>change transient_key</li>
</ul>
<h4>4.0.1</h4>
<ul>
<li>Bug fix ( conflict Nephila Clavata )</li>
</ul>
<h4>4.0.0</h4>
<ul>
<li>Support AWS SDK Version3</li>
<li>Remove action hook -> ‘c3_add_setting_before’<br />
use ‘c3_after_title’ filter hook instead.</li>
<li>Remove action hook -> ‘c3_add_setting_after’<br />
use ‘c3_after_auth_form’ filter hook instead.</li>
</ul>
<h4>3.0.0</h4>
<ul>
<li>Include CF Preview Fix plugin</li>
<li>Rename</li>
</ul>
<h4>2.4.3</h4>
<ul>
<li>Fix Catch Exception BUG</li>
</ul>
<h4>2.4.2</h4>
<ul>
<li>Fix CLI BUG</li>
</ul>
<h4>2.4.1</h4>
<ul>
<li>Fix CLI BUG</li>
</ul>
<h4>2.4.0</h4>
<ul>
<li>Add WP-CLI Command ( Update Settings )</li>
</ul>
<h4>2.3.0</h4>
<ul>
<li>Add WP-CLI Command</li>
</ul>
<h4>2.2.2</h4>
<ul>
<li>Force Invalidation</li>
</ul>
<h4>2.2.1</h4>
<ul>
<li>Fix Typo</li>
</ul>
<h4>2.2.0</h4>
<ul>
<li>Add Filter for using EC2 Instance Role.</li>
<li>Translationable in t.w.org</li>
</ul>
<h4>2.1.1</h4>
<ul>
<li>Fix too many invalidation url error.</li>
</ul>
<h4>2.1.0</h4>
<ul>
<li>Add hook to customize invalidation URL</li>
<li>support new invalidation url, terms.</li>
<li>Manualy invalidation button added</li>
</ul>
<h4>2.0.2</h4>
<ul>
<li>Change AWS SDK</li>
<li>code refactoring by wokamoto</li>
<li>Invalidation URL</li>
</ul>
<h4>2.0.1</h4>
<ul>
<li>Change AWS SDK</li>
<li>code refactoring by wokamoto</li>
<li>Invalidation URL</li>
</ul>
<h4>1.0</h4>
<ul>
<li>Initial released.</li>
</ul>
<h3>6.1.0</h3>
<ul>
<li>[Fix] Plugin deactivation issue</li>
</ul>


C3 Cloudfront Cache Controller

This is simple plugin that clear all cloudfront cache if you publish posts.

Opal Sync Media to Amazon S3 vs C3 Cloudfront Cache Controller