您正在使用过期的浏览器。此浏览器可能无法正确显示本网站或其他网站的内容。
建议您升级浏览器,或使用
其他浏览器。
Akeeba Backup Pro for J!3
8.4.1.1
没有下载权限
Changelog
New features
- Support for custom Amazon S3 regions
Bug fixes
- [HIGH] Pagination in the Manage Backups page was broken
Changelog
New features
- Much improved FTP functions for uploading backup archives and transferring sites
- OneDrive for Business: you can now use Drives other than your personal
- Upload to Azure BLOB Storage now supports chunked uploads, files up to 190.7TB (up from 64Mb)
Bug fixes
- [MEDIUM] OneDrive: Uploads may fail if they are between 4Mb and 100Mb
Miscellaneous changes
- Stricter conditions for determining when to show the “Manage remotely stored files” button in Manage Backups
New features
- Option to set a really large PHP memory limit during backup
- Restoration: ANGIE now applies very high memory and execution time limits to prevent some timeout / memory outage issues on most hosts.
- Restoration: ANGIE now warns you if you leave the database connection information empty
Bug fixes
- [LOW] The JPS archiver would show warnings about unreadable files when archiving directories without any files in them.
Miscellaneous changes
- More helpful and forceful installation abortion message when you try to install this package on Joomla 4.1 or later.
Changelog
Bug fixes
- [HIGH] Uploading to OVH is broken on many servers not using a proxy
- [HIGH] Wrong RewriteBase set up in the .htaccess Maker when restoring a Joomla site with Admin Tools Professional installed
Miscellaneous changes
- Make it clearer that you need Akeeba Backup 9 on Joomla 4.
Bug fixes
- [HIGH] Wrong RewriteBase set up in the .htaccess Maker when restoring a Joomla site with Admin Tools Professional installed
Miscellaneous changes
- PHP 8.1 compatibility changes
New features
- Allow using [REMOTESTATUS] in the email subject, not just the body
- Joomla restoration: modify domains in the Admin Tools' Allowed Domains and server config maker features if necessary
Bug fixes
- [HIGH] Backing up as SQL: the query for finder_taxonomy does not use the correct prefix
- [HIGH] Backing up to SQL: indices would not have the correct table name prefix
- [HIGH] PHP fatal error on PHP 8 if the output directory does not exist
- [HIGH] Problems restoring if a table name ends in 0 when another table with an identical name EXCEPT the trailing zero is also being backed up
- [LOW] Occasional display issue on Chromium browsers with the database and file / folder filter pages.
- [LOW] RackSpace CloudFiles: some hosts change the case of HTTP headers
- [MEDIUM] Log Priorities global configuration option got mangled restoring a Joomla 4 site