webCOMAND 3.0.29 Released
webCOMAND 3.0.29 Improves repository backup, restore and audit trail retention options.
Backup and Restore
The backup process is now more storage and time efficient because large database table backup files are split, which improves ZIP compression and speed. It is also more memory efficient, so it can backup massive repositories, even on systems with limited memory available.
The Restore process now writes File+ objects to the file system according to any restored File Settings, to ensure Package files are also restored to the file system.
Content Log Retention
It is now possible to configure how many and/or how long to retain content logs by content type and folder to reduce storage requirements while maintaining an audit trail where it is important. For more information, see Content Log Settings in the Docs.
Mutation Queries in the API App
- Copy Formatting - A new Copy Formatting option is now available in the Rich Text Editor.
- PHP API Batch Object Delete - A new 'batch_delete' option is available for the collection::delete() method to more efficiently delete many objects of the same type(s).
- New Backup Options - A couple of additional configuration options have been added to customize how webCOMAND repository backups are created. large_file_size can be used to adjust the maximum size of files to compress within a backup ZIP archive. The default is 10MB. If files larger than this size are added to the ZIP archive, they will not be compressed to reduce memory and processing requirements. enable_zip64 was added to enable Zip 64 compression. Default is TRUE. FALSE will use Zip 32 compression instead.