help.cloudscale.consulting<\/a>.<\/p>\n\nExternal services<\/h3>\n\n
This plugin optionally connects to third-party services when those features are configured by the site administrator. No data is sent to any external service unless the administrator has explicitly enabled the relevant integration.<\/p>\n\n
Telegram Bot API (optional notifications)<\/h4>\n\n
Service:<\/strong> Telegram Messenger, https:\/\/telegram.org\/\nWhen a Telegram bot token and chat ID are entered, the plugin sends backup,\nrestore, rollback and error alerts to that chat. A message holds the site name,\nevent status and, for errors, the PHP error, file and line. No visitor data,\npost content or backup data is sent.\nAPI endpoint contacted: the sendMessage method on api.telegram.org, addressed with\nthe administrator's own bot token.\nTerms of Service: https:\/\/telegram.org\/tos\nPrivacy Policy: https:\/\/telegram.org\/privacy\nTelegram Bot API documentation: https:\/\/core.telegram.org\/bots\/api<\/p>\n\nAmazon S3 (optional cloud backup)<\/h4>\n\n
Service:<\/strong> Amazon Web Services, https:\/\/aws.amazon.com\/\nWhen S3 settings are configured, the plugin uploads backup zips to the\nadministrator's own S3 bucket via the S3 REST API. Only the backup zip is sent.\nThe credentials are stored on the site and sent only to the AWS S3 endpoint.\nAPI endpoint contacted: the Amazon S3 host for the bucket's own AWS region, for\nexample s3.eu-west-1.amazonaws.com.\nTerms of Service: https:\/\/aws.amazon.com\/service-terms\/\nPrivacy Policy: https:\/\/aws.amazon.com\/privacy\/<\/p>\n\nGoogle Drive (optional cloud backup)<\/h4>\n\n
Service:<\/strong> Google, https:\/\/workspace.google.com\/products\/drive\/\nWhen Google Drive settings are configured, the plugin transfers backup zip files\nto the administrator's own Google Drive account using the Google Drive v3 REST\nAPI and OAuth 2.0. No data is sent unless the administrator has completed the\nOAuth authorisation flow (entered a Client ID and Client Secret from Google\nCloud Console and clicked \"Connect to Google Drive\"). Only the backup zip file\nis uploaded. OAuth tokens (access token and refresh token) are stored in the\nWordPress options table.\nAPI endpoints contacted: www.googleapis.com (Drive v3) and oauth2.googleapis.com\n(OAuth 2.0 tokens).\nTerms of Service: https:\/\/policies.google.com\/terms\nPrivacy Policy: https:\/\/policies.google.com\/privacy<\/p>\n\nDropbox (optional cloud backup)<\/h4>\n\n
Service:<\/strong> Dropbox, https:\/\/www.dropbox.com\/\nWhen Dropbox settings are configured, the plugin transfers backup zip files to\nthe administrator's own Dropbox account using the Dropbox v2 REST API and\nOAuth 2.0. No data is sent unless the administrator has completed the OAuth\nauthorisation flow (entered an App Key and App Secret from the Dropbox App\nConsole and clicked \"Connect to Dropbox\"). Only the backup zip file is\nuploaded. OAuth tokens are stored in the WordPress options table.\nAPI endpoints contacted: api.dropboxapi.com and content.dropboxapi.com (Dropbox v2\nREST API).\nTerms of Service: https:\/\/www.dropbox.com\/terms\nPrivacy Policy: https:\/\/www.dropbox.com\/privacy<\/p>\n\nMicrosoft OneDrive (optional cloud backup)<\/h4>\n\n
Service:<\/strong> Microsoft, https:\/\/learn.microsoft.com\/en-us\/onedrive\/\nWhen OneDrive settings are configured, the plugin transfers backup zip files to\nthe administrator's own Microsoft OneDrive account using the Microsoft Graph\nREST API and OAuth 2.0. No data is sent unless the administrator has completed\nthe OAuth authorisation flow (entered an Azure App Client ID and Client Secret\nand clicked \"Connect to OneDrive\"). Only the backup zip file is uploaded.\nOAuth tokens are stored in the WordPress options table.\nAPI endpoint contacted: https:\/\/graph.microsoft.com\/ and https:\/\/login.microsoftonline.com\/\nTerms of Service: https:\/\/www.microsoft.com\/en-us\/servicesagreement\/\nPrivacy Policy: https:\/\/www.microsoft.com\/en-us\/privacy\/privacystatement<\/p>\n\nCloudScale Managed Cloud Backup (optional, paid service)<\/h4>\n\n
Service:<\/strong> CloudScale Consulting, https:\/\/cloudscale.consulting\/\nWhen subscribed, the plugin asks the CloudScale broker for a short-lived,\nprefix-scoped Amazon S3 token, then uploads backup zips straight to CloudScale's\nS3 storage; backup bytes never pass through the broker. It times ten HEAD requests per storage\nregion and sends the averages, to pick the nearest region. Nothing is sent until\na licence key is entered. Storage is encrypted at rest. For extra security, Encrypt\nbackups adds AES-256 encryption with the site owner's own password before upload. Leave us a message sends the typed email and\nmessage, hostname and licence key on Send. Clicking the PayPal button sends the\nproduct name, hostname and the optional email typed above it to \/checkout-start,\nso a failed checkout can be followed up.\nAPI endpoints contacted (broker): https:\/\/api.cloudscale.consulting\/backup\/token,\nhttps:\/\/api.cloudscale.consulting\/backup\/list, https:\/\/api.cloudscale.consulting\/status,\nhttps:\/\/api.cloudscale.consulting\/checkout, https:\/\/api.cloudscale.consulting\/checkout-start,\nhttps:\/\/api.cloudscale.consulting\/recover, https:\/\/api.cloudscale.consulting\/recover\/verify,\nhttps:\/\/api.cloudscale.consulting\/refund-request and https:\/\/api.cloudscale.consulting\/contact.\nStorage and timing requests go to CloudScale's Amazon S3 storage in its ten\nregions: af-south-1, eu-west-1, us-east-1, ap-southeast-2, ap-southeast-1,\nap-south-1, sa-east-1, us-west-2, eu-central-1 and ap-northeast-1.\nTerms of Service: https:\/\/cloudscale.consulting\/terms\/\nPrivacy Policy: https:\/\/cloudscale.consulting\/privacy\/<\/p>\n\nPayPal (optional, payment for Managed Cloud Backup)<\/h4>\n\n
Service:<\/strong> PayPal, https:\/\/www.paypal.com\/us\/home\nSubscription payments for the optional CloudScale Managed Cloud Backup service are\nprocessed by PayPal on its own hosted checkout; card details never reach this plugin\nor the site. When the administrator starts a subscription, the subscriber's email and\nthe order amount ($5.00 USD) are sent from the WordPress server to the PayPal REST API\n(api-m.paypal.com) to create a checkout session. Nothing is sent unless the\nadministrator chooses to subscribe.\nAPI endpoint contacted: api-m.paypal.com (live) or api-m.sandbox.paypal.com\n(sandbox testing), the PayPal REST API: https:\/\/developer.paypal.com\/api\/rest\nBrowser-loaded script: PayPal's JavaScript SDK from www.paypal.com\/sdk\/js, loaded\ninto the plugin's admin screen only after an administrator opens the subscription\ncheckout. PayPal requires the SDK be served from its own origin so a compromised build\ncan be revoked, so it cannot be bundled with the plugin.\nTerms of Service: https:\/\/www.paypal.com\/us\/legalhub\/paypal\/useragreement-full\nPrivacy Policy: https:\/\/www.paypal.com\/us\/legalhub\/paypal\/privacy-full<\/p>\n\nAWS EC2 \/ AMI snapshots (optional, AMI snapshot feature only)<\/h4>\n\n
Service:<\/strong> Amazon Web Services, https:\/\/aws.amazon.com\/\nWhen the AMI snapshot feature is used, the plugin reads instance metadata\n(instance ID and region) from the local EC2 Instance Metadata Service at the\nlink-local address 169.254.169.254. This address is only reachable from within an EC2\ninstance and no data leaves the server at this step. AMI creation, status poll,\nderegister, and snapshot delete requests are then issued directly to the AWS\nEC2 REST API (no external tools required). The same AWS credentials\n(access key ID and secret key) used for S3 are used; if none are configured\nthe plugin attempts to use the EC2 instance role via IMDS.\nAPI endpoint contacted: the Amazon EC2 host for the instance's own AWS region, for\nexample ec2.eu-west-1.amazonaws.com.\nTerms of Service: https:\/\/aws.amazon.com\/service-terms\/\nPrivacy Policy: https:\/\/aws.amazon.com\/privacy\/<\/p>\n\nAutomatic Crash Recovery: health check probe (optional)<\/h4>\n\n
When Automatic Crash Recovery is enabled, the plugin periodically sends an HTTP\nrequest to the administrator-configured health check URL to verify the site is\nresponding. The URL defaults to the site's own home URL. No personal data is\ntransmitted. The request is a plain GET with no authentication payload. The\nsame probe is made when the administrator clicks \"Test Health Check\" in the\nplugin settings. If a system-cron watchdog script is installed on the server,\nthat script also probes this URL independently via curl. The health check URL\nis set by the administrator and is never shared with any third party.\nNo Terms of Service or Privacy Policy apply (the request goes to a URL you own).<\/p>\n\n
Gmail SMTP port check (only when sending a test email)<\/h4>\n\n
Service:<\/strong> Google, https:\/\/workspace.google.com\/gmail\/\nWhen the administrator clicks Send Test in the Notifications card, the plugin opens\na TCP connection to smtp.gmail.com on ports 587, 465 and 25 and closes it at once,\nto tell whether this server can reach an outside mail server at all. No email,\nlogin or data of any kind is sent; only the connection is attempted. Nothing\nhappens until the button is clicked.\nTerms of Service: https:\/\/policies.google.com\/terms\nPrivacy Policy: https:\/\/policies.google.com\/privacy<\/p>\n\nHelp documentation link<\/h4>\n\n
The plugin's header links to its help pages on help.cloudscale.consulting. It is\nan ordinary link the administrator may choose to open; the plugin itself never\nrequests that host and sends it no data.<\/p>\n\n
Privacy Policy<\/h3>\n\n
CloudScale Backup & Restore does not collect, transmit, or store any personal data. All backups are stored locally in the cloudscale-backups\/<\/code> folder inside your WordPress uploads directory. No telemetry or analytics are sent by this plugin. Optional cloud backup features (S3, Google Drive, Dropbox, OneDrive, AMI snapshots, CloudScale Managed) transmit data only when explicitly configured by the site administrator. CloudScale Managed backups are encrypted at rest; Encrypt backups adds the site owner's own password. See the External services section above.<\/p>\n\n\n\n- In WordPress admin go to Plugins > Add New Plugin<\/strong>, search for CloudScale Backup & Restore<\/strong>, then click Install Now<\/strong> and Activate<\/strong><\/li>\n
- Open Tools > CloudScale Backup & Restore<\/strong><\/li>\n
- Click Back up my site now<\/strong> to take your first backup<\/li>\n
- Optional: connect S3, Google Drive, Dropbox, OneDrive or Managed Cloud, then turn on a schedule<\/li>\n<\/ol>\n\n
To install by hand, upload the cloudscale-backup<\/code> folder to \/wp-content\/plugins\/<\/code> and activate it under Plugins > Installed Plugins<\/strong>.<\/p>\n\n\n\nIs restore really free?<\/h3><\/dt>\nYes. Full restore, selective table restore, single post restore, cloud restore, staging clones and automated standby restore are all in the free plugin. Only Managed Cloud storage is paid; your own cloud accounts cost nothing extra.<\/p><\/dd>\n
Will it work on a large site?<\/h3><\/dt>\nYes. The database is dumped in 500-row pages, so memory stays flat whatever its size. Backups and restores run without PHP's time limit, large uploads are sent in retried chunks, and an S3 or Managed Cloud download that stops part way resumes. A backup killed mid-run is picked up and finished or restarted. The System Info panel shows your server's limits and the methods in use.<\/p><\/dd>\n
Where are backups stored?<\/h3><\/dt>\nOn your server in wp-content\/uploads\/cloudscale-backup-<random>\/<\/code>. The random part makes the folder name unguessable, and it carries deny rules for Apache, nginx and IIS plus an index.php<\/code> and 0700<\/code> permissions. Download any backup from the admin with the Download button. Copies go to every cloud destination you enable.<\/p><\/dd>\nWhere are Managed Cloud backups stored?<\/h3><\/dt>\nIn one of ten Amazon S3 regions. Automatic picks the region nearest your site by measuring it; you can also choose one, for example to keep data in Europe. Changing region sends new backups there; backups in the old region expire within 90 days.<\/p><\/dd>\n
Can I restore only the database, or only some tables?<\/h3><\/dt>\nYes. In the Restore window choose Full restore<\/strong> (files, then database), Specific tables only<\/strong> (just the tables you tick) or Single post or page<\/strong>. Upload a .sql<\/code> file to restore a database only. On the command line, wp csbr restore<\/code> takes --db-only<\/code>, --files-only<\/code> and --components=<list><\/code>.<\/p><\/dd>\nCan I migrate to a new host or domain?<\/h3><\/dt>\nYes. Install WordPress and this plugin on the new host, then restore the backup from an upload or straight from your cloud storage. Files and database are both restored. If the domain changed, run wp search-replace 'old.example' 'new.example' --all-tables<\/code> afterwards. To copy a site onto the same server under a new URL, use Clone Targets, which rewrites URLs for you.<\/p><\/dd>\nHow does scheduling work?<\/h3><\/dt>\nChoose the days of the week and the time of day; cloud copies run a set delay after the local backup. For reliable timing, point a real system cron job at wp-cron.php<\/code> instead of relying on visitor traffic. Your server's time and timezone are shown next to the schedule.<\/p><\/dd>\nHow do I set up a standby or disaster-recovery copy of my site?<\/h3><\/dt>\nInstall WordPress and this plugin on the second server, then open the Standby & DR tab there (never on the live site). Choose a hot standby or a refreshed copy, label its alerts, type MAKE THIS A COPY and press Apply. On the Automated Restore tab connect the cloud storage the live site backs up to, choose the site to copy from, and switch on the schedule. The checklist shows anything still missing. A hot standby also needs something outside WordPress to move your DNS; the plugin's GitHub repository has a Cloudflare script for that.<\/p><\/dd>\n
How do I clone my site to a staging copy on the same server?<\/h3><\/dt>\nCreate an empty directory the web server can write to, with a wp-config.php<\/code> naming an empty database (or one your database user can create). Take a backup that includes WordPress core files. On the Clone Targets tab add the directory, its URL and that wp-config.php<\/code>, press Verify, then Clone Now. Everything in the target is replaced and every URL is rewritten. The wp-config.php<\/code> must hold literal database values, and cloning needs the PHP mysqli<\/code> extension. A clone is a complete copy, including mail settings and scheduled tasks, so block outgoing email on it before you browse it. Hook csbr_clone_post_restore<\/code> to run your own steps afterwards.<\/p><\/dd>\nWhat happens if a restore fails?<\/h3><\/dt>\nMaintenance mode is removed even when a restore fails, including on a PHP fatal or out-of-memory error, and you are alerted with the reason. The restore result lists anything that could not be written. There is no automatic rollback of a partly restored database, so take a server snapshot first (the Restore window asks you to confirm you have) and restore again or from that snapshot.<\/p><\/dd>\n
Can I run backups and restores from WP-CLI or cron?<\/h3><\/dt>\nYes. wp csbr restore <file><\/code> restores a local backup, wp csbr cloud-pull --newest<\/code> downloads the newest S3 backup, wp csbr sync-from-cloud<\/code> pulls and restores in one step, and wp csbr auto-restore<\/code> runs a standby's configured restore. Run wp help csbr<\/code> for every option.<\/p><\/dd>\nDo I need ZipArchive or a recent PHP?<\/h3><\/dt>\nPHP 8.1 or newer and the PHP zip<\/code> extension, which nearly every host includes. AES-256 encryption needs a zip<\/code> extension built with encryption support; the plugin tells you if yours is not.<\/p><\/dd>\nWhat is inside the backup zip?<\/h3><\/dt>\nThe parts you chose: database.sql<\/code>, the uploads, plugins, themes and other folders, plus backup-meta.json<\/code>, which records the plugin and WordPress versions, site URL, table prefix and components, so you can check a backup without restoring it.<\/p><\/dd>\nWhat files does the plugin write outside its own folder?<\/h3><\/dt>\nThe Automatic Crash Recovery feature writes a single file outside the plugin\nfolder when it is enabled: wp-content\/fatal-error-handler.php<\/code>. This is a\nWordPress-recognised drop-in file (documented in the WordPress Developer\nHandbook under get_dropins()<\/code>). WordPress core checks for this file on every\nrequest; if present, it replaces the default fatal-error screen with a custom\nhandler. The plugin uses this mechanism to show a branded recovery page to\nvisitors while a crash is being fixed, instead of a blank white screen.<\/p>\n\nThe file is written using the WordPress Filesystem API (WP_Filesystem). It is\nonly written when the feature is enabled, only overwritten if it was written by\nthis plugin (identified by an internal marker), and is deleted when the feature\nis disabled or the plugin is uninstalled. No personal data is stored in this file.<\/p>\n\n
The plugin also writes the following. Uninstalling removes them, except where noted:<\/p>\n\n
\nwp-content\/uploads\/cloudscale-backup-<random>\/<\/code> - the backup archives themselves,\nplus an .htaccess<\/code>, a web.config<\/code> and an index.php<\/code> that block public access to\nthem. The directory name carries a per-site random token because a fixed, guessable\nname meant sequentially-named archives could be downloaded by anyone who guessed a\nfilename. Kept on uninstall<\/strong> so a reinstall or a manual restore can still use your\nbackups; delete the folder yourself if you no longer want them. The token is kept in\n wp-content\/csbr-state\/dir-token (with the same deny rules), which also stays so a\nreinstall finds the folder.<\/li>\nwp-content\/csbr-state\/<\/code> - the plugin's hardened state directory: the automatic restore\nschedule, the backup run lock and the crash-recovery configuration. Removed on\nuninstall, apart from dir-token<\/code> and its deny rules (above).<\/li>\nwp-content\/csbr-failover-mode.json<\/code>, csbr-site-id.json<\/code> and csbr-restore-ledger.json<\/code> -\nsmall markers for the standby, failover and restore features, kept outside the database\nbecause a restore replaces the database. Removed on uninstall.<\/li>\nwp-content\/csbr-site-role.json<\/code> and wp-content\/cloudscale-alert-env-label.json<\/code> - the\nsite's role (primary or standby) and its alert label. Kept on uninstall<\/strong>, because the\nother CloudScale plugins read them too; delete them by hand if no CloudScale plugin\nremains.<\/li>\nwp-content\/maintenance.php<\/code> and wp-content\/csbr-restore-progress.json<\/code> - the visitor\npage and progress file shown while a restore runs, removed when it ends. Uninstall\nremoves maintenance.php<\/code> only if it is this plugin's copy.<\/li>\nwp-content\/csbr-secrets.php<\/code> - cloud storage credentials, the licence key and the\nbackup encryption password, held outside the database so they are not carried inside\nthe database dumps this plugin creates. It begins with a PHP exit guard so it cannot\nbe read over HTTP, is written 0600<\/code>, and is excluded from every backup. A lock file\nand a short-lived temporary file sit alongside it during a write.<\/li>\nwp-content\/cloudscale-backup-par.json<\/code> - the Automatic Crash Recovery state file,\nrecording which plugins are being monitored.<\/li>\nwp-content\/csbr-state\/csbr-auto-restore.json<\/code> - on a standby site only, the automatic\nrestore schedule and the source it pulls from. The directory carries the same deny-all\nrules as the backup directory, so the file is not readable over HTTP. Installs upgrading\nfrom an earlier version have their existing wp-content\/csbr-auto-restore.json<\/code> moved\nhere automatically.<\/li>\n<WordPress root>\/.maintenance<\/code> - WordPress's own maintenance-mode file, written only\nwhile a restore is running and removed when it finishes or fails. This is the\nmechanism WordPress itself uses during core updates.<\/li>\n- A temporary staging directory under the system temp path while a backup is built or\na restore is unpacked, deleted when the operation ends.<\/li>\n
wp-content\/csbr-state\/plugin-auto-recovery\/<\/code> - Automatic Crash Recovery only: a copy of\na plugin taken just before WordPress updates it, so a bad update can be rolled back. It is\nremoved when the monitoring window closes and otherwise after 72 hours, and on uninstall.\nIt sits outside the uploads folder because it holds PHP, and it carries deny rules.<\/li>\n- Clone Targets only, and only after an administrator adds a target and presses Clone Now\nor enables its schedule: a complete WordPress install (core, plugins, themes, uploads and\nthe
wp-config.php<\/code> the administrator named) is written into the directory the\nadministrator chose for that target, which is normally outside wp-content<\/code>, and the\ntables in that target's own database are dropped and recreated. It never writes to this\nsite's own directory, and no script is generated or run. The target list is stored in\nthe csbr_clone_targets<\/code> option.<\/li>\n<\/ul>\n\nNo personal data is stored in any of these files beyond what the site itself already\nholds.<\/p><\/dd>\n\n<\/dl>\n\n\n
3.2.858<\/h4>\n\n\n- FIX: Uninstall now removes the plugin's state files in wp-content. Backup archives, the token naming their folder, and the site-role and alert-label markers shared with other CloudScale plugins are kept on purpose.<\/li>\n
- TWEAK: Rewrote the plugin description and FAQ.<\/li>\n<\/ul>\n\n
3.2.857<\/h4>\n\n\n- TWEAK: The restore modal's \"Full database, drop and recreate all tables\" option is now \"Full restore\". It always restored the backup's files as well as its database, and the label and warning now say so.<\/li>\n<\/ul>\n\n
3.2.856<\/h4>\n\n\n- FIX: OneDrive and Dropbox uploads retry a chunk that fails on a dropped connection, a throttle (429) or a server error (5xx), up to 5 attempts, instead of losing the whole upload. They resume where the provider says it is and honour Retry-After. Google Drive follows the same rules and now retries a 429 too.<\/li>\n
- FIX: Dropbox refreshes an access token that expires during a long upload.<\/li>\n
- FIX:
wp csbr restore<\/code> and wp csbr sync-from-cloud<\/code> now run the same restore as the Restore button. The password check, file check, drop-in health check and alerts now apply to WP-CLI, and files-only backups work there.<\/li>\n- TWEAK: Removed 12 server actions that nothing in the plugin called.<\/li>\n<\/ul>\n\n
3.2.855<\/h4>\n\n\n- FIX: Test Connection for Google Drive, Dropbox and OneDrive failed to detect revoked credentials; it now shows the provider's error.<\/li>\n
- FIX: A failed cloud listing no longer erases which backups are golden, so they can't be pruned by mistake.<\/li>\n
- FIX: Delete oldest on Google Drive could delete the newest backup.<\/li>\n
- FIX: Saving the AMI card no longer resets \"Max Cloud Backups to Keep\" to 10.<\/li>\n
- FIX: Backups are verified before old ones are pruned; a corrupt or half-written backup is reported as failed and not uploaded.<\/li>\n
- FIX: Database read errors during a backup now fail it instead of producing a short dump.<\/li>\n
- FIX: Dropbox can be connected on a fresh install; cloud downloads refresh expired tokens and no longer stop at 300 seconds.<\/li>\n
- FIX: CloudScale Managed uploads once, and managed storage is pruned when S3 is unticked.<\/li>\n
- FIX: S3, Google Drive and OneDrive listings follow every page.<\/li>\n
- FIX: Restore fails if file extraction stops part way; files-only backups restore without touching the database.<\/li>\n
- FIX: Clone URL rewrite failures are reported; nested serialized values are rewritten correctly.<\/li>\n
- FIX: Crash recovery finds its settings again (alerts and recovery page), and rollback never deletes the plugin before the old version is ready.<\/li>\n
- FIX: Auto-restore fixed time is saved; an empty backup-day list stays empty; Telegram test sends once.<\/li>\n
- NEW: System Info health checks (PHP, folder, ZIP\/AES, WP-Cron, overdue schedule, last result per destination) and
wp csbr doctor<\/code>.<\/li>\n- NEW: S3 Test checks list and delete permissions and removes its test file; Managed Test checks storage credentials.<\/li>\n
- NEW: Activity log records skipped uploads, OAuth and token errors, dump\/archive timings, skipped days and undelivered alerts.<\/li>\n<\/ul>\n\n
3.2.854<\/h4>\n\n\n- FIX: Google Drive's \"Authorised redirect URI\" box now shows the URI Connect sends (admin.php), so registering it no longer fails with redirect_uri_mismatch.<\/li>\n
- FIX: OneDrive gets the pre-sync space check and Delete oldest, like Dropbox and Google Drive.<\/li>\n
- FIX: A skipped cloud upload says to tick the provider under \"Include in cloud backup\" and Save, instead of \"not configured\".<\/li>\n
- FIX: S3 Diagnose shows bucket, prefix, credentials source, last sync and the Include setting.<\/li>\n
- Changed: S3 and AMI text no longer say the AWS CLI is required; the plugin talks to AWS directly.<\/li>\n<\/ul>\n\n
3.2.852<\/h4>\n\n\n- FIX: OneDrive uploads no longer report \"OneDrive not configured\" after a successful Test Connection. The OneDrive tick under \"Include in cloud backup\" is now saved; tick it and save once after updating.<\/li>\n
- Changed: Dropbox and OneDrive Explain and Diagnose describe the built-in API connection, not rclone, which is not needed.<\/li>\n<\/ul>\n\n
3.2.848<\/h4>\n\n\n- Changed: alert-sync hooks use literal, prefixed names for WordPress.org Plugin Check.<\/li>\n<\/ul>\n\n
3.2.847<\/h4>\n\n\n- Changed: alert settings (Telegram, environment label, mute) are stored under this plugin's own prefix, migrated automatically, and kept in sync with the other CloudScale plugins.<\/li>\n<\/ul>\n\n
3.2.846<\/h4>\n\n\n- IMPROVED: The Managed card reads \"Use a password for extra security\" with a Set a password button, or confirms backups are encrypted with your password.<\/li>\n
- FIX: Saving the backup encryption password checks the request's nonce itself, not only in its callers.<\/li>\n<\/ul>\n\n
3.2.845<\/h4>\n\n\n- IMPROVED: CloudScale Managed storage adds Oregon (US West), Frankfurt and Tokyo, ten regions in all. N. Virginia now reads as US East.<\/li>\n<\/ul>\n\n
3.2.844<\/h4>\n\n