DiluxOne Offload – Media Storage

Descripción

DiluxOne Offload moves your WordPress media library to Azure Blob Storage or to any S3-compatible service (Amazon S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Wasabi, Google Cloud Storage, Hetzner, Akamai (Linode), Vultr, Scaleway, OVHcloud, IDrive e2, MinIO) and serves files directly from the cloud — without breaking the Media Library UI, plugins, or existing content.

El plugin usa un stream wrapper de PHP personalizado para interceptar cada lectura y escritura en /wp-content/uploads/, de modo que WordPress, WooCommerce, los constructores de páginas, los editores de imágenes y cualquier plugin que use funciones estándar del sistema de archivos (fopen, file_get_contents, unlink, etc.) siguen funcionando sin cambios.

Características principales

  • Azure Blob Storage or S3-compatible storage — bring your own storage account or bucket; nothing is shared with anyone else. For S3-compatible services, pick the service and the plugin fills in the endpoint and the public URL; a CDN or a custom domain goes in the Public URL field.
  • Stream wrapper transparente: sin reescritura de URLs, sin expresiones regulares sobre el contenido de las entradas, sin necesidad de migración de base de datos para las URLs.
  • Sincronización con máquina de estados reanudable: iniciar, cancelar, reanudar tras una interrupción, reintentar archivos fallidos, resincronizar desde cero.
  • Modo offloading: después de una sincronización exitosa puedes eliminar las copias locales para liberar espacio en disco; el stream wrapper mantiene todo funcionando.
  • Monitoreo del estado de la conexión: cuando la nube no está disponible, las subidas nuevas se rechazan con un error claro en lugar de terminar en otro lugar, y un aviso en las páginas de administración del plugin explica el motivo hasta que se recupera.
  • Sin datos del plugin en el disco: no hay archivos de caché, registro ni datos en ningún lugar del servidor. La única vez que el plugin escribe en el directorio de subidas (uploads) es cuando te desconectas, para copiar tus propios archivos multimedia de vuelta a donde WordPress los espera.
  • Large files don’t need large memory — a download goes straight to disk, and an upload is sent in blocks (4 MiB on Azure, 5 MiB parts on S3-compatible services, larger only for a file too big for the service’s limit on parts, past about 5 GB on Scaleway or 48 GB elsewhere), so PHP never holds more than one block of a file at a time and a video does not trip memory_limit.
  • Compatible con multisitio: admite activación de red; cada sitio conserva su propia configuración y seguimiento de archivos, y sus objetos viven bajo su propio prefijo en el contenedor (uploads/ para el sitio principal, uploads/sites/<id>/ para los demás, el mismo esquema que usa WordPress en el disco), así que varios sitios pueden compartir un contenedor sin compartir nunca una clave.
  • Silencioso por defecto: con WP_DEBUG desactivado y el interruptor de Settings desactivado, el plugin no escribe nada en el registro de errores de PHP, en ningún nivel. WP_DEBUG activa errores y advertencias; el interruptor agrega las líneas informativas.

Por qué un stream wrapper en lugar de reescritura de URLs

La mayoría de los plugins de offload reescriben las URLs de los archivos multimedia en el contenido de las entradas, lo que se rompe cuando cambias de proveedor, mudas de dominio o restauras desde una copia de seguridad. DiluxOne Offload deja las URLs intactas y reescribe las lecturas y escrituras en la capa del sistema de archivos, así que tu contenido se mantiene portable.

Limitaciones conocidas

  • The media must be publicly readable where it is stored: on Azure, a container whose public access level is Blob; on S3-compatible services, a bucket that lets anyone read its objects. Test Connection checks it and refuses a private one.
  • La sincronización inicial se ejecuta en la pestaña de tu navegador y se detiene si la cierras; se reanuda donde quedó. Nada se ejecuta en segundo plano ni por cron.
  • Los archivos que superan el valor configurado en Maximum File Size (20 MB por defecto, hasta 500 MB) se omiten en la sincronización inicial.
  • Mientras la nube no esté disponible, las subidas nuevas fallan. Deliberadamente no hay ningún método de respaldo local.
  • On Azure, media is served from the storage account’s URL; on S3-compatible services the Public URL field is where a CDN or custom domain goes.
  • Disconnect from Cloud necesita un directorio de subidas (uploads) con permiso de escritura y suficiente espacio en disco para tus archivos multimedia.

Servicios externos

This plugin connects to one cloud storage service, the one you choose: Azure Blob Storage, or an S3-compatible service (Amazon S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Wasabi, Google Cloud Storage, Hetzner Object Storage, Akamai (Linode) Object Storage, Vultr Object Storage, Scaleway Object Storage, OVHcloud Object Storage, IDrive e2, or a server whose address you type). It uses it to store and serve your media files. Nothing is sent anywhere until you configure it yourself in the Cloud Provider tab, with an account and credentials you supply. The plugin contacts no other service: it sends no telemetry, no usage data and no licence check to the author or to anyone else.

Azure Blob Storage

Para qué se usa: para almacenar tus archivos multimedia de WordPress fuera de tu servidor y servirlos desde la nube.

Adónde van las solicitudes: la API REST de Azure Blob en blob.core.windows.net, específicamente el host de tu propia cuenta, https://ACCOUNT.blob.core.windows.net, donde ACCOUNT es el nombre de la cuenta de almacenamiento que ingresas en la configuración.

Qué datos se envían: tus propios archivos multimedia, junto con su ruta relativa, tamaño y tipo MIME. La clave de la cuenta de almacenamiento que ingresaste nunca sale de tu servidor: se usa localmente para calcular la firma que autentica cada solicitud. No se envía ningún dato personal sobre tus visitantes ni sobre los usuarios de tu sitio, y nada relacionado con tu sitio llega al autor del plugin.

Cuándo ocurren las solicitudes:

  • Durante la sincronización inicial: al subir los archivos existentes de /wp-content/uploads/ a tu contenedor.
  • En cada subida nueva de un archivo multimedia: al escribir el archivo en la nube a través del stream wrapper.
  • Al leer o eliminar: cuando WordPress, o cualquier plugin que use las API del sistema de archivos contra /uploads/, lee o elimina un archivo. Este es también el único tráfico de front-end: un formulario o una reseña que sube un archivo pasa por el mismo stream wrapper.
  • Cuando el plugin lista tu contenedor: para las estadísticas de Overview (en caché durante cinco minutos) y para el escaneo que precede a Disconnect from Cloud.
  • Una verificación de estado de la conexión (un GET pequeño para las propiedades de tu contenedor) al abrir una de las páginas de administración del plugin, como máximo una vez cada 5 minutos, y otra vez tras una escritura que sigue a tres fallos consecutivos, para que las subidas se reanuden solas cuando la nube vuelva a estar disponible. Nada se ejecuta por cron.
  • Durante Disconnect from Cloud: al descargar tus archivos de vuelta al servidor.

Esta es tu propia cuenta de Azure, bajo tu propio acuerdo con Microsoft. Ni DiluxOne ni el autor del plugin son parte de ese acuerdo, y ninguno de los dos tiene acceso a tus datos. El uso que hagas del servicio está sujeto a los términos de Microsoft:

S3-compatible storage

What it is used for: the same as above, on the S3-compatible service you choose.

Where requests go: the endpoint of the service you chose, which the form fills in for each service and you can change: Amazon S3 at https://s3.REGION.amazonaws.com (requests address https://BUCKET.s3.REGION.amazonaws.com), Cloudflare R2 at https://ACCOUNT_ID.r2.cloudflarestorage.com, Backblaze B2 at https://s3.REGION.backblazeb2.com, DigitalOcean Spaces at https://REGION.digitaloceanspaces.com, Wasabi at https://s3.REGION.wasabisys.com, Google Cloud Storage at https://storage.googleapis.com, Hetzner Object Storage at https://REGION.your-objectstorage.com, Akamai (Linode) Object Storage at https://REGION.linodeobjects.com, Vultr Object Storage at https://REGION.vultrobjects.com, Scaleway Object Storage at https://s3.REGION.scw.cloud, OVHcloud Object Storage at https://s3.REGION.io.cloud.ovh.net, IDrive e2 at https://s3.REGION.idrivee2.com (or the endpoint of your own its dashboard shows), or the address you type under Custom. Browsers load your media from the Public URL you set, which can be the service’s own address, a CDN or a custom domain.

What data is sent: your media files themselves, together with their relative path (the object key), size and MIME type, and a signature of each request computed from your secret access key. The secret itself never leaves your server. No personal data about your visitors or your site’s users is sent, and nothing at all about your site reaches the plugin’s author.

When requests happen: the same moments as for Azure above. The connection check is different: when you press Test Connection, and at most every five minutes while you browse the plugin’s admin pages, the plugin writes a 32-byte probe object under your site’s prefix, reads it back from the Public URL without credentials (to prove browsers can load your media) and deletes it.

This is your own account with that service, under your own agreement with its provider. Neither DiluxOne nor the plugin’s author is a party to it and neither has any access to your data. Your use of the service is subject to its provider’s terms:

Amazon S3:

Cloudflare R2:

Backblaze B2:

DigitalOcean Spaces:

Wasabi:

Google Cloud Storage:

Hetzner Object Storage:

Akamai (Linode) Object Storage:

Vultr Object Storage:

Scaleway Object Storage:

OVHcloud Object Storage:

IDrive e2:

Custom endpoint: the plugin talks only to the server whose address you typed (MinIO, Ceph or any other that speaks the S3 API). No third party is involved unless that server belongs to one you chose.

Capturas

Instalación

  1. Sube la carpeta diluxone-offload a /wp-content/plugins/, o instálalo desde la pantalla de Plugins de WordPress.
  2. Activa el plugin desde la pantalla Plugins de WordPress.
  3. Abre el nuevo menú DiluxOne Offload en la barra lateral de administración.
  4. Go to Cloud Provider, select Microsoft Azure Blob Storage (enter the storage account, container and access key) or S3-compatible storage (pick the service, then enter the region, bucket, keys and, if it is not filled in, the public URL), and click Test Connection.
  5. Guarda la configuración.
  6. Ve a Sync & Offloading, ejecuta la sincronización inicial y activa el offloading cuando la sincronización termine.

Requisitos

  • WordPress 5.1 o superior.
  • PHP 7.4 o superior.
  • ext-curl y ext-openssl habilitados.
  • Un directorio de subidas (uploads) con permiso de escritura, solo para Disconnect from Cloud, cuando tus archivos multimedia se copian de vuelta. Las transferencias usan el directorio temporal de PHP para sus archivos de trabajo, nunca uploads/.
  • An Azure Blob Storage account, a container whose public access level is Blob (anonymous read access for blobs, so browsers can load your media straight from it), and the account’s access key; or a bucket on an S3-compatible service that lets anyone read its objects, and an access key pair allowed to put, get, delete and list objects in it. Test Connection refuses a private container or bucket and says so.

FAQ

¿Este plugin modifica las URLs de mis archivos multimedia existentes en la base de datos?

No. The stream wrapper intercepts filesystem calls transparently — your post content, the wp_posts table, and the wp_postmeta table are never rewritten.

¿Qué pasa si la nube no está disponible temporalmente?

El plugin monitorea el estado de la conexión. Mientras la nube no esté disponible, una subida nueva falla con el propio error de WordPress «no se pudo mover el archivo» y no se guarda nada en ningún lado, así que nunca terminas con un archivo que parece subido pero no lo está. Un aviso en las páginas de administración del plugin explica la falla. Los archivos que ya están en la nube se siguen sirviendo desde la URL de la cuenta de almacenamiento. El plugin vuelve a comprobar la conexión como máximo cada cinco minutos, y las subidas se reanudan solas en cuanto vuelve a estar disponible.

¿El plugin escribe algún archivo en mi servidor?

No para sí mismo: no tiene archivos de caché, registro ni datos en el disco; todo lo que necesita vive en la tabla de opciones de WordPress y en su propia tabla de base de datos. Tus archivos multimedia son escritos por el núcleo de WordPress a través del stream wrapper del plugin hacia la nube, pasando por un archivo temporal en el directorio temporal de PHP que se elimina justo después de la subida.

The one operation that writes to the server is Sync & Offloading Disconnect from Cloud. It copies your media back from the container to the exact uploads-directory paths WordPress has on record (resolved at runtime with wp_upload_dir()), so the Media Library works again without the plugin. It restores only what sits under the uploads/ prefix of your own container, never a script or executable file name (PHP, JavaScript, HTML, shell or Windows executables) whatever put it there, and it runs only when you click it.

What if the container or bucket already holds files?

Before the first sync, Sync & Offloading › Sync looks under this site’s folder in it (uploads/, or uploads/sites/<id>/ for a site of a network). If something is there, from an earlier install or a staging copy, it says how many files and how much, and lets you continue with them, empty that folder (you type the container’s or bucket’s name to confirm) or connect another one. Emptying deletes only this site’s folder, never anything else in the container or bucket, and only before the first sync.

¿Puedo pasar a otra cuenta de almacenamiento o contenedor más adelante?

Yes, including from Azure to an S3-compatible service or back. Remove the current provider configuration from the admin, enter the new account, container or bucket, run a full resync, and the plugin starts serving from the new location. No URL rewriting required.

¿Funciona con WooCommerce / Elementor / editores de imágenes?

Yes. Because the stream wrapper operates at the filesystem layer, any plugin that reads or writes files under /uploads/ using standard PHP functions works unchanged.

¿El plugin elimina mis archivos locales automáticamente?

Only if you explicitly opt in. After a successful sync you can click Delete Local Files in Sync & Offloading › Offloading. Until you do that, files are kept in both locations. A file that is empty (0 bytes) when the sync scans it is skipped: it is neither uploaded nor tracked, so Delete Local Files leaves it alone.

Si elimino un archivo de la Biblioteca de medios, ¿se elimina también de la nube?

Yes, while offloading is active: the stream wrapper turns the deletion into a delete on your container, thumbnails included. If you have synced but not yet enabled offloading, WordPress deletes only the local copy; the copy already in your container is not removed automatically.

¿Qué pasa cuando desinstalo el plugin?

Eliminar el plugin desde la pantalla de Plugins borra todo lo que creó en tu base de datos: sus opciones (todas con el prefijo diluxone_offload_), sus transients y su tabla de seguimiento de archivos (diluxone_offload_files, con el prefijo de tus tablas), en todos los sitios de una red. Desactivarlo únicamente conserva todo eso, así que puedes desactivarlo y reactivarlo sin perder tu configuración.

Your media files are never touched by uninstalling: whatever is in /wp-content/uploads/ stays there, and whatever is in your container stays in your container. The only thing uninstalling cancels in the storage is an S3 multipart upload the sync left unfinished, which could no longer be completed and would keep being billed. If offloading was active and local copies had been deleted, download them first with Sync & Offloading Disconnect from Cloud, otherwise WordPress will be pointing at files that are no longer on the server.

¿Cómo activo el registro de depuración detallado?

Ve a DiluxOne Offload Settings Enable detailed debug logging. Los registros se escriben en el destino estándar de PHP error_log. Desactívalo en producción salvo que estés solucionando un problema activamente: puede afectar el rendimiento.

Con esa opción desactivada y WP_DEBUG desactivado, el plugin no escribe nada en el registro de errores de PHP, en ningún nivel. Con WP_DEBUG activado escribe errores y advertencias; la opción agrega el resto.

¿Es compatible el plugin con multisitio?

Sí. Se puede activar a nivel de red; cada sitio tiene entonces su propia configuración de Cloud Provider y su propia tabla de seguimiento de archivos, de modo que distintos sitios pueden usar distintos contenedores o cuentas, o compartir uno: los objetos de un sitio se guardan bajo uploads/sites/<id>/ (el sitio principal bajo uploads/), y cada sitio únicamente lista, sincroniza y restaura su propio prefijo.

¿Cómo se almacenan mis credenciales de Azure?

The Azure access key and the S3 secret access key are encrypted with AES-256-GCM before they are written to the WordPress options table (the S3 access key ID, like a user name, is not a secret and is stored as it is). The encryption key is derived from your site’s WordPress salts (AUTH_KEY / SECURE_AUTH_KEY and the corresponding salts in wp-config.php), so as long as those salts are defined in wp-config.php (as WordPress recommends) a database dump on its own is not enough to recover the credentials — the attacker also needs filesystem access to wp-config.php.

Si alguna vez rotas las claves salt de WordPress, las credenciales cifradas existentes dejan de poder leerse; el plugin mostrará el proveedor como «no configurado» y simplemente tienes que volver a introducir las credenciales en la pestaña Cloud Provider. No existe, intencionalmente, ningún método alternativo en texto plano.

Requisitos: PHP ext-openssl (habilitado por defecto en prácticamente cualquier hosting).

Reseñas

No hay valoraciones para este plugin.

Colaboradores y desarrolladores

«DiluxOne Offload – Media Storage» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«DiluxOne Offload – Media Storage» está traducido en 2 idiomas. Gracias a los traductores por sus contribuciones.

Traduce «DiluxOne Offload – Media Storage» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

2.1.0

  • Enable Offloading looks for files added since the last sync first: it says how many there are and uploads them before offloading is turned on. A file added between the end of the sync and enabling offloading used to stay off the cloud, a broken image once offloading was on. A synced library also offers Scan and Complete Sync on Sync & Offloading › Sync.
  • Opening Sync & Offloading › Sync more than 90 seconds after a sync finished no longer resets the plugin to «configured», which turned offloading off without a word.
  • Complete Sync uploads the files added to uploads/ since the last sync; it used to report success and leave them out.
  • Deleting an attachment while offloading is on removes its copies left on this server too, not only the objects in the cloud.
  • Deactivating the plugin before the first sync keeps its state; it used to come back as «synced».
  • A site whose server path has a folder named cache, temp or tmp above uploads/ syncs its files; every file used to be skipped. Those folders inside uploads/ are still left out.
  • Cloud Provider › Credentials shows the answer of Test Connection; it was written but stayed hidden.
  • Clear List empties the failed files list on Sync & Offloading › Sync; it used to say so and leave the list as it was.
  • A browser tab that lost the sync to another tab stops when the sync finishes, instead of asking the server again and again.
  • The size of a file that is only in the cloud is its real size (the Media Library shows it for files without a stored size); it used to be 0.
  • The DiluxOne Offload menu sits at the end of the admin menu, after Settings, where WordPress places a plugin’s menu by default.
  • A sync or download request keeps to its time limit when the server’s clock is corrected while it runs. Before, a clock set back made the limit look untouched, and the request kept starting uploads past it.
  • A delete or an upload the storage service asks to slow down (a 429; Google allows one change a second to the same file) is tried again after a second. Before, deleting an image right after editing it could leave its files stored, and billed, in the cloud.
  • Uninstalling cancels the S3 multipart uploads a sync left unfinished, so the bucket stops billing parts nobody can complete any more.
  • Before the first sync, Sync & Offloading › Sync checks this site’s folder in the container or bucket. If something is already there (an earlier install, a staging copy) it says how many files and how much, and lets you continue with them, empty that folder (typing the container’s or bucket’s name) or connect another one. Emptying never touches anything outside this site’s folder.
  • A sync whose uploads go through ends a pause the connection health had recorded (a key that failed and was fixed since), instead of showing «Paused» for up to five more minutes.
  • An upload, a delete or a check that meets a temporary error from the storage service (a 500 or 503, a dropped connection) is tried up to three times in all, instead of failing at once. Backblaze B2 answers that way to about one upload in a hundred, which could leave an image without one of its thumbnails.
  • The initial sync uses every parallel upload from the start: a library that begins with large files used to send them one at a time, and now sends them alongside small ones, each upload starting as soon as another finishes.
  • A large file’s parts (above 10 MB) now go up in parallel, like the other files, instead of one after another while the rest of the sync waited. A part that meets a temporary error from the storage service is sent again instead of failing the file. A very large file no longer has to go up within one request of the sync: the next one takes it up where it was left, sending only the parts the storage service does not have yet.
  • The sync and Disconnect from Cloud reuse their connections to the storage service from one group of files to the next, instead of opening a new one, with its secure handshake, for every file.
  • Status › Health names the storage service in use (Cloudflare R2, Amazon S3, …) and no longer shows a card that repeated the plugin’s state. Screens that speak of the storage say «container or bucket», and a hostname too long for its card (Cloudflare R2’s public one) is shortened, with the whole name on hover.
  • The Sync, Offloading and Disconnect screens and their windows are built on WordPress’ own buttons, notices and cards, and take the accent of your admin colour scheme. Offloading’s bar shows, in one full bar, the files only in the cloud and, striped, the ones that still have a copy on this server (the disk Delete Local Files can free). While a sync has files pending, the ones that already failed show as a red part of its bar. Messages these screens showed in English only are now translated.
  • Six more services in the S3-compatible provider’s Service list: Hetzner Object Storage, Akamai (Linode) Object Storage, Vultr Object Storage, Scaleway Object Storage, OVHcloud Object Storage and IDrive e2. Each fills in the endpoint and, where the service has one, the public URL, and says where its keys come from and how to make the bucket readable.
  • A file too large for the storage service’s limit on parts goes up in larger parts instead of failing: past about 5 GB on Scaleway (1,000 parts), past about 48 GB elsewhere.
  • Settings › Serving › New uploads: browser caching, on by default, stores Cache-Control: public, max-age=604800 (one week, editable, or off) with every new upload, so browsers and CDNs keep your media instead of asking the storage again. And a storage class for new uploads: Standard, or the cheaper infrequent-access class (Azure’s Cool tier, STANDARD_IA on Amazon S3 and Cloudflare R2), which charges per read and bills a minimum of 30 days. Files already in the cloud keep what they were stored with.
  • The notices after saving settings, the provider or new credentials are translated.
  • Settings › Transfers › Folders the initial sync leaves out: one folder per line under wp-content/uploads/ (backups, caches); the scan skips them and lists them on the Sync screen. Files uploaded through the site while offloading is on still go to the cloud.
  • An e-mail to the site’s administrator address when uploads pause (the storage failed three times in a row) and one more when they resume, never one per failure. On by default; Settings › Logging turns it off.
  • Tools › Site Health has a test for the connection to your storage, critical with the reason when uploads are paused, and an Info section with the provider, the service, the state and the version (never a key).

2.0.0

  • S3-compatible storage: besides Azure Blob Storage, the media can live on Amazon S3, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Wasabi, Google Cloud Storage (HMAC keys) or any server that speaks the S3 API, such as MinIO. Pick the service and the plugin fills in the endpoint and the public URL; the Public URL field is also where a CDN or a custom domain goes. Test Connection proves the keys can write to the bucket and that browsers can read what is stored, and refuses a private bucket. Large files go up in 5 MiB parts; the secret access key is encrypted like the Azure key. «Force HTTPS for cloud storage URLs» leaves alone a Public URL that is plain http on purpose, such as a server on a private network.
  • Only a configuration that passed Test Connection can be saved, now checked on the server too: a key other than the tested one is refused.
  • The admin is one menu with a screen per submenu (Overview, Cloud Provider, Sync & Offloading, Settings, Status) and tabs only where a screen needs a second level: Connection and Credentials; Sync, Offloading and Disconnect; Transfers, Serving and Logging; Health and System. Every screen is headed «DiluxOne Offload | Screen», shows the site’s state at a glance in a column beside the content, and the open tab follows your admin colour scheme. Old links to the tabs keep working.
  • Status › Health shows the connection health the plugin already recorded (status, last check, last success, consecutive failures) and how many files the tracking table knows, with a «Check now» button that asks the provider right away; Status › System shows the free disk.
  • The screens say what is where: Sync shows how many files are synced, how many still have a local copy, how many live in the cloud only, the last upload made through the site and what the last scan left out (and why); Offloading shows where the media is served from, where the bytes are and since when; Disconnect shows what it would bring back and whether the disk has room; Cloud Provider shows since when it is connected.
  • Files uploaded through the site while offloading is on are now counted like the ones the initial sync moved, and deleting the local copies no longer empties the plugin’s tracking table, so those figures stay right on the sites that use offloading. A very long list of failed files shows its first 50 rows and says how many there are.
  • The Overview shows three state cards (the fourth repeated them); Cloud Provider › Connection offers «Rotate the key» and «Delete Cloud Provider» as buttons; every button with an icon has the icon and its label on one line, and the sync window’s buttons read at their size.
  • The «Upload Timeout» setting is now «Transfer Timeout» and governs every upload request: the single upload, each block and its commit, and the sync’s parallel transfers. Before, block commits waited a fixed 300 seconds whatever the setting said. Downloads keep waiting at least the 300 seconds they always had; a higher setting raises that too.
  • A transfer that runs past the timeout is reported as such: the connection-health banner says «Cloud Transfer Timed Out» and links to Settings, instead of showing a made-up error code.
  • With debug logging on, every successful upload through the stream wrapper writes one line (path and size).
  • The suites now prove what each setting does, not only that it is saved.

1.0.0

Primera versión pública.

  • Proveedor de Azure Blob Storage con tu propia cuenta y clave; archivos multimedia servidos desde https://<account>.blob.core.windows.net.
  • Stream wrapper de PHP transparente en /wp-content/uploads/: sin reescritura de URLs, sin migración de base de datos.
  • Sincronización con cancelar, reanudar y reintentar; eliminación opcional de las copias locales una vez sincronizadas; Disconnect from Cloud trae todo de vuelta.
  • Estado de la conexión: cuando la nube no está disponible, una subida falla con un error claro y no se escribe nada en ningún otro lado.
  • Transferencias en streaming: las descargas van directo al disco y las subidas se envían en bloques de 4 MiB, así que los archivos grandes no necesitan mucha memoria.
  • Opción «Force HTTPS for cloud storage URLs»; multisitio con configuración por sitio; credenciales cifradas en reposo (AES-256-GCM, clave derivada de las claves salt del sitio); silencioso a menos que WP_DEBUG o el interruptor de depuración estén activados.
  • Al desinstalar se eliminan las opciones, los transients y la tabla del plugin; los archivos multimedia nunca se tocan.