WP-Stateless – Google Cloud Storage

Description

Upload and serve your WordPress media from Google Cloud Storage (GCS) with the WP-Stateless plugin. In as little as two minutes, you will be benefitting from serving your media from Google Cloud’s distributed servers.

New to Google Cloud? Google is offering you a $300 credit to get you started.

Benefits

  • Store and deliver media files on Google Cloud Storage instead of your server.
  • Google Cloud Storage is geo-redundant, meaning your media is delivered by the closest server – reducing latency and improving page speed.
  • Scale your WordPress website across multiple servers without the need of synchronizing media files.
  • Native integration between Google Cloud Storage and WordPress.
  • $300 free trial from Google Cloud. Nice!

Modes

  • Backup – Upload media files to Google Storage and serve local file urls.
  • CDN – Copy media files to Google Storage and serve them directly from there.
  • Ephemeral – Store and serve media files with Google Cloud Storage only. Media files are not stored locally, but local storage is used temporarily for processing and is required for certain compatibilities.
  • Stateless – Store and serve media files with Google Cloud Storage only. Media files are not stored locally.

Features

  • Setup assistant makes getting started fast and easy.
  • No need to manually create service accounts or buckets – handled automatically.
  • Settings panel provides you with further GCS configuration and file url customization.
  • Mask the default GCS URL with your own custom domain.
  • Automatically replace hardcoded media URLs with GCS equivalents in post editor and meta.
  • Batch image thumbnail regeneration.
  • Synchronization tools for uploading existing files and images.
  • All settings supported with wp-config constants and network setting overrides.
  • Multiple modes: Backup, CDN, Ephemeral, Stateless.
  • All files served in HTTPS mode.
  • Serverless platform compatible, including Google App Engine.
  • Multisite compatible.

Support, Feedback, & Contribute

We welcome community involvement via the GitHub repository.

Custom Development

Looking for a unique feature for your next project? Hire us!

Screenshots

  • Settings Panel: Supports network setting and wp-config constant overrides.
  • Setup Assistant
  • Setup Assistant: Google Login
  • Setup Assistant: Approve Permissions
  • Setup Assistant: Project & Bucket
  • Setup Assistant: Complete
  • Edit Media: Image stored on Google Cloud Storage.

Installation

  1. Search, install, and activate the WP-Stateless plugin via your WordPress dashboard.
  2. Begin WP-Stateless setup assistant at Media > Stateless Setup and click “Get Started Now.”
  3. Click “Google Login” and sign-in with your Google account.
  4. Set a Google Cloud Project, Google Cloud Storage Bucket, and Google Cloud Billing Account and click “Continue.”
  5. Installation and setup is now complete. Visit Media > Stateless Settings for more options.
    For a more detailed installation and setup walkthrough, please see the manual setup instructions on Github.

FAQ

What are the minimum server requirements for this plugin?

Beyond the official WordPress minimum requirements, WP-Stateless requires a minimum PHP version of 5.6 or higher and OpenSSL to be enabled.

What wp-config constants are supported?

For a complete list of supported wp-config constants, please consult the GitHub documentation.

How do I manually generate the Service Account JSON?

The WP-Stateless setup assistant will create the Service Account JSON automatically for you, but you can follow these steps if you choose to create it manually.

  1. Visit Google Cloud Console, and go to IAM & Admin > Service accounts.
  2. Click Create Service Account and name it wp-stateless.
  3. Set the role to Storage > Storage Admin.
  4. Check Furnish a new private key and select JSON as the key type.
  5. Open the JSON file and copy the contents into the Service Account JSON textarea within the WP-Stateless settings panel.

Where can I submit feature requests or bug reports?

We encourage community feedback and discussion through issues on the GitHub repository.

Can I test new features before they are released?

To ensure new releases cause as little disruption as possible, we rely on a number of early adopters who assist us by testing out new features before they are released. Please contact us if you are interested in becoming an early adopter.

Who maintains this plugin?

UDX maintains this plugin by continuing development through it’s own staff, reviewing pull requests, testing, and steering the overall release schedule. UDX is located in Durham, North Carolina and provides WordPress engineering and hosting services to clients throughout the United States.

Reviews

April 28, 2021
Every time I do saves anywhere on my site I get the error message "There has been a critical error on this website." and it only goes away when I deactivate the plugin. I've tried the plugin against all my other plugins and even when that's the only one active, it does the same thing.
April 9, 2021
Sometimes it works, sometimes it doesn't. On some upload links it uploads the content to Google cloud... On others upload links it loads it up to the local wp-content/uploads folder. The idea is great, but this plugin has too many bugs to be functional. I tried 3 different versions of WP but none worked. A true disappointment !
Read all 38 reviews

Contributors & Developers

“WP-Stateless – Google Cloud Storage” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

3.1.1

  • ENHANCEMENT – Notification for the administrator about finished synchronization. GitHub issue #576.
  • FIX – Fixed an issue with PDF thumbnails. GitHub issue #577.
  • FIX – Fixed an issue with synchronization in Stateless mode. GitHub issue #575.
  • COMPATIBILITY – Changed the way compatibility files are stored on Multisite. GitHub issue #588.

3.1.0

  • NEW – Completely rewritten the synchronization tool. GitHub issue #523.
  • NEW – New configuration constant WP_STATELESS_SYNC_MAX_BATCH_SIZE. Sets the maximum size of a background sync batch of items to be saved in a single row in the database. More details.
  • NEW – New configuration constant WP_STATELESS_SYNC_LOG. Sets a path to a log file where to output logging information during the background sync. More details.
  • NEW – New configuration constant WP_STATELESS_SYNC_HEALTHCHECK_INTERVAL. Defines an interval in minutes for a cron task that periodically checks the health of a particular background sync process. More details.
  • FIX – Fixed an issue when original files were not deleted from the server in the Ephemeral mode. GitHub issue #484.
  • FIX – Fixed an incorrect behavior of image srcset attribute in the Backup mode. GitHub issue #558.
  • COMPATIBILITY – Litespeed Cache – Fixed an incorrect upload folder determination. GitHub issue #527.

3.0.4

  • FIX – Fixed inability to use dashes in the upload folder name. GitHub issue #565.
  • COMPATIBILITY – Elementor – Fixed wrong upload directory. GitHub issue #560.

3.0.3

  • FIX – Fixed an incorrect file URL in Stateless mode on Edit Media screen. GitHub issue #544.

3.0.2

  • FIX – Refactored the way files are being uploaded to GCS when WP_STATELESS_MEDIA_UPLOAD_CHUNK_SIZE constant is defined. GitHub issue #553.
  • FIX – Fixed the process of upgrading to 3.0 for multisite installations. GitHub issue #549.

3.0.1

  • FIX – Fatal Error in Stateless mode. GitHub issue #546.

3.0

  • Before upgrading to WP-Stateless 3.0, please, make sure you tested it on your development environment. It may have breaking changes.
  • NEW – Setup assistant rewrite. GitHub issue #477.
  • NEW – Recreate attachment metabox panel using metabox.io. GitHub issue #470.
  • NEW – Updated the Stateless mode to not use local storage at all. Current Stateless mode setting mapped to new Ephemeral mode. GitHub issue #482.
  • NEW – Files are now uploaded to GCS in chunks and chunk size will be determined based on free memory available. GitHub issue #478.
  • NEW – File upload chunk size can be controlled with WP_STATELESS_MEDIA_UPLOAD_CHUNK_SIZE constant. GitHub issue #478.
  • FIX – Changed the default value for the Cache-Busting setting. GitHub issue #361.
  • FIX – Fixed network override of Cache-Busting. GitHub issue #468.
  • FIX – Fixed “Passing glue string after array is deprecated.”. GitHub issue #444.
  • FIX – Fixed Compatibility default value in multisite. GitHub issue #464.
  • FIX – Fixed multisite wrong GCS path. GitHub issue #407.
  • FIX – Don’t check for Google Cloud Storage connectivity in stateless mode unless uploading. GitHub issue #442.
  • COMPATIBILITY – Google App Engine – Added new compatibility support for Google App Engine. #486
  • COMPATIBILITY – Elementor – Fixed wrong MIME type for CSS files. GitHub issue #395.
  • COMPATIBILITY – Polylang – Fixed missing metadata issue. GitHub issue #378.
  • COMPATIBILITY – EWWW – Fixed mime type for WEBP images. GitHub issue #371.
  • COMPATIBILITY – Simple Local Avatars – Added new compatibility support for Simple Local Avatars. GitHub issue #297.
  • COMPATIBILITY – BuddyPress – Fixed BuddyPress compatibility. GitHub issue #275.
  • COMPATIBILITY – Divi – Fixed Divi cache issue. GitHub issue #430.
  • COMPATIBILITY – Gravity Forms – add compatibility for Gravity Forms Signature Add-On. #501.
  • COMPATIBILITY – Litespeed – Fixed fatal error and warnings. #491.
  • COMPATIBILITY – Imagify – Added support for webp. #403.
  • ENHANCEMENT – Update Client library for Google APIs. #446.
  • ENHANCEMENT – Wildcards for bucket folder settings. GitHub issue #149.
  • ENHANCEMENT – Better CLI integration. GitHub issue #447, #450 and #451.
  • ENHANCEMENT – Sync media according to new Bucket Folder settings. GitHub issue #449.
  • ENHANCEMENT – Moved Bucket Folder setting in the File URL section. GitHub issue #463.
  • ENHANCEMENT – Hide Regenerate and Sync with GCS when the mode is Disabled. GitHub issue #440.
  • ENHANCEMENT – New endpoint for the Google Cloud Storage JSON API. GitHub issue #384.
  • ENHANCEMENT – Renamed current Stateless mode to Ephemeral. GitHub issue #481.

2.3.2

  • FIX – Fixed video file doesn’t get deleted from the server in Stateless mode. GitHub issue #418.
  • FIX – Fixed file size doesn’t show under attachment details in Stateless mode. GitHub issue #413.
  • FIX – Fixed Cache-Busting feature works even if the Mode is Disabled. GitHub issue #405.
  • COMPATIBILITY – Fixed Gravity Form Post Image didn’t include Bucket Folder. GitHub issue #421.
  • COMPATIBILITY – Fixed Divi Builder Export. GitHub issue #420.
  • COMPATIBILITY – Fixed BuddyBoss pages breaking after updating to 2.3.0. GitHub issue #417.

2.3.1

  • Fix – Fixed fatal error, undefined function is_wp_version_compatible. GitHub issue #414.

2.3.0

  • FIX – Fixed problem with WordPress 5.3. GitHub issue #406.
  • FIX – Fixed problem with the Cache Busting feature. GitHub issue #377.
  • COMPATIBILITY – Added compatibility support for WP Retina 2x pro. GitHub issue #380.
  • COMPATIBILITY – Enhanced compatibility support for LiteSpeed Cache. GitHub issue #365.
  • COMPATIBILITY – Enhanced compatibility support for ShortPixel Image Optimizer. GitHub issue #364, #398.
  • COMPATIBILITY – Fixed Gravity Form export. GitHub issue #408.
  • ENHANCEMENT – Improved upon add_media function for better compatibility support. GitHub issue #382.

2.2.7

  • FIX – WP-Smush compatibility enhanced. GitHub Issue #366.
  • FIX – Fixed multisite installation support. GitHub Issue #370.
  • FIX – Fixed settings UI problems related to Cache-Busting option. GitHub Issue #373.
  • FIX – Other minor fixes.

2.2.6

  • FIX – Multisite Network Settings page fixed. GitHub Issue #369.
  • FIX – Fixed incorrect Compatibilities behavior when Bucket Folder is set. GitHub Issue #368.
  • FIX – Other minor fixes.

2.2.5

  • NEW – Added ability to start sync process from specific Attachment ID. GitHub Issue #360.
  • COMPATIBILITY – Added compatibility support for LiteSpeed Cache plugin. Especially to support optimized .webp images. GitHub Issue #357.
  • FIX – Other minor fixes.

Earlier versions

Please refer to the separate changelog.txt file.