Akeeba Backup Pro pour WordPress 9.0.6

[sarisan]

LeAkeeba Backup Pro for Wordpressa a été soumis et est maintenant disponible gratuitement pour téléchargement. Merci beaucoup de la contribution de notre membre @sarisan!

Afficher la pièce jointe 112230
Un clic de sauvegarde​

C'est tout ce qu'il faut pour créer une sauvegarde complète du site. L'archive comprend votre base de données, les fichiers et le script de restauration.

Formats disponibles​

Archives ZIP standard, archives JPA optimisées ou archives JPS AES-128 sécurisées. C'est à vous de choisir.

Profils de Sauvegarde personnalisables​

Vous choisissez ce qui ne devrait pas être inclus dans la sauvegarde. Fichiers ou tables...

Read more about this resource...

 

[sarisan]

A new update for Akeeba Backup Pro for Wordpress 9.0.6 is now available for free download. Big thanks to the contribution from our member @sarisan !
changelog

v9.0.6

New features​

• More inline text explaining the concept of backup profiles throughout the interface
• Using IMDSv2 for getting the credentials off EC2 instances

Removed features​

• Remove platform check from updates due to confusing results in some cases

Bug fixes​

• [HIGH] "Normalise character set" can break the restoration

v9.0.0

New features​

• ...

Read the rest of this update entry...

 

[Zafro]

Akeeba Backup for WordPress 9.1.7​

Released on: 2026-06-17 22:48 CDT

This release includes two important bug fixes and two notable changes.

BackBlaze B2 v4 API. BackBlaze has released version 4 of their B2 cloud storage API and deprecated the older versions. This release updates the integration to use the v4 API, ensuring continued compatibility with BackBlaze B2 as a remote storage destination.

File scanner compatibility (OVH and similar hosts). The Site Transfer Wizard places a kickstart.txt file on the remote server. Certain broken server-side file scanners, including OVH's, incorrectly flag this file as malicious content and quarantine or delete it, causing the wizard to fail. This release obfuscates the file so it is no longer misidentified.

Bug fix: Site Transfer Wizard was not working. A regression caused the Site Transfer Wizard to fail entirely. This has been fixed.

Bug fix: DirectFTP erroneous directory permissions. DirectFTP was setting incorrect permissions on remote directories, which could cause backup transfers to fail. This has been fixed.

Changelog​

Bug fixes​

• [HIGH] DirectFTP would not work due to setting erroneous directory permissions
• [HIGH] The Site Transfer Wizard was not working

Miscellaneous changes​

• Obfuscate kickstart.txt so that broken file scanners (OVH) don't cause problems by misidentifying it as "malicious"
• Switched to BackBlaze B2 v4 API

 

[Zafro]

Akeeba Backup for WordPress 9.1.8​

Released on: 2026-07-29 21:27 CDT

This release adds a Site Transfer Wizard improvement, fixes a data-integrity issue in database dumps, resolves numerous remote storage bugs, and hardens several areas of the application.

Site Transfer Wizard: transfer any backup archive. The wizard previously only offered the most recent backup archive on the server. You can now pick and transfer any backup archive still present on the server, not just the latest one.

Bug fix: database dumps silently lost precision on DOUBLE columns. When dumping databases with the PDO MySQL or PostgreSQL drivers, values stored in DOUBLE columns could lose precision without any warning. This has been fixed.

Bug fix: Box, Dropbox, OneDrive stored files under the local temp name. Files uploaded to these three remote storage providers could end up stored under their local temporary filename rather than their intended name. This has been fixed.

Bug fix: uploads failed with a bucket-restricted BackBlaze B2 key. Using a BackBlaze B2 application key restricted to a single bucket caused uploads to fail. This has been fixed.

This release also includes a broad pass of medium and low priority fixes across Box, Dropbox, Google Drive, Google Storage, OneDrive, RackSpace CloudFiles, S3, WebDAV, and BackBlaze B2 — covering error reporting, token refresh timing, pre-signed URL generation, and pagination. See the changelog for the complete list.

Bug fix: FTP/FTPS connection test ignored the "Use FTP over SSL" setting. A configuration key mismatch caused the connection test to always test a plain FTP connection, even when FTP over SSL was enabled, causing it to fail against FTPS-only servers. This has been fixed.

Security hardening. Access control checks for the profiles and user management pages were hardened, anti-CSRF token coverage was broadened across AJAX and maintenance actions, and several comparisons involving secret words and two-factor authentication now use constant-time comparison.

Changelog​

New features​

• Site Transfer Wizard: transfer any backup archive present on the server, not just the latest one (gh-239)

Bug fixes​

• [HIGH] Box, Dropbox, OneDrive stored files under the local temp name
• [HIGH] Database dumps silently lost precision on DOUBLE columns (PDO MySQL and PostgreSQL)
• [HIGH] Uploads failed when using a bucket-restricted BackBlaze B2 key
• [LOW] Additional two-factor authentication and anti-CSRF token comparison hardening
• [LOW] BackBlaze cancelUpload sent the request body as form-data, not JSON
• [LOW] BackBlaze downloadFileById used the wrong API path (404)
• [LOW] Box folder listing paginated incorrectly
• [LOW] Broadened anti-CSRF token coverage across AJAX and maintenance actions
• [LOW] Front-end backup and post-backup check endpoints now use constant-time secret word comparison
• [LOW] Legacy (hard-disabled) SFTP directory browser model used the wrong option keys for key-based authentication
• [LOW] Removed the unused, legacy FTP/SFTP directory browser
• [LOW] WebDAV options() dropped capabilities from repeated DAV headers
• [LOW] WordPress: the control panel is no longer rendered when the application files are accessed directly
• [MEDIUM] Box reported an expired authorisation as an opaque HTTP 401 error
• [MEDIUM] Box, Dropbox, Google Drive, OneDrive token refresh raced expiry
• [MEDIUM] Dropbox did not explain a missing or lapsed Download ID
• [MEDIUM] Dropbox public download URL embedded the access token
• [MEDIUM] FTP/FTPS connection test ignored the "Use FTP over SSL" setting due to a config key mismatch, causing it to fail against FTPS-only servers
• [MEDIUM] Google Storage pre-signed URLs duplicated the bucket name (403)
• [MEDIUM] Hardened access control checks for the profiles and user management pages
• [MEDIUM] OneDrive for Business signed download URL was broken on Graph
• [MEDIUM] RackSpace CloudFiles validated the username, not the API key
• [MEDIUM] S3 v4 pre-signed URLs failed (403) on path-style non-AWS hosts
• [MEDIUM] WebDAV did not surface failed upload reason to the UI or the log file