WP Staging Pro 6.1.3

* New: Compatible up to WordPress 6.2
* Enh: Improves the look of the update notice #2294
* Fix: Remove double `www` prefix if network is cloned to a `www` prefixed hostname but subsite already has `www` prefix #2284
* Dev: Add more unit tests to increase reliability of the backup plugin #2273
* Dev: Refactor backup terms `Export` to `Backup` and `Import` to `Restore` for consistency #2265
* Dev: Move src/Pro/Backup to src/Backup as a first step to allow basic Backup feature to be added in Free version of WP Staging #2287 #2297

New: Add filter wpstg.restore.tmp_database_prefix to use custom temporary database prefix used during backup restore. Using this filter is useful in cases when (1) there are already tables with default WP Staging temp prefix (wpstgtmp_), or (2) restore fails because of 64 characters table name length limit for database identifiers #2217
New: Add filter wpstg.backup.directory to save backups in a custom location #2247
Enh: Improve message if there is not enough free disk space while creating a backup #2193
Enh: Add better logging for backup creation #2257
Enh: Improve the error message on the front-end when the backup directory is not available #2130
Enh: Show in knowledgebase block only articles of plugins that are actually installed on users website #2176
Enh: Show specific error message on backup listing page if backup is corrupted
Enh: Refactoring of admin notice for better performance #1573
Fix: Improper use of the Translation function #2259 #2260
Fix: Prevent fatal errors on rare edge cases where a file lock can not be released #2254
Fix: Clear wpstg_* scheduled hooks on plugin deactivation #2256
Fix: Images URLs are now correctly formed when a backup is restored from http to https and vice versa #2111
Fix: Allow + character in PuTTY SFTP key format, fixing the issue where PuTTY generated keys are not working #2155
Fix: Improper use of the translation function #2260
Fix: Sometimes a warning can appear indicating the backup file would be broken and contains a broken backup file index although the backup file is 100% intact #2269

* New: Major change of the User Interface #2197 #2208
* New: Add an option to send an email error report. You can enable this option in the settings and use a separate email to receive error reports #2205
* Enh: Show a notice if site contains backup(s) with invalid files-index #2205
* Enh: Add a retry mechanism to backup restore if a backup restore fails due to 404, 429 or 503 errors #2094
* Enh: Clean up log files and don't show necessary information #2124
* Enh: Show notice how to enable permalinks depending on whether the server is Apache or another. #2143
* Enh: Explain what to enter in the 'version' field of Generic S3 provider #2172
* Enh: Show notice how to fix cron issue when using Litespeed server #2170 #2226
* Enh: Better notification message when there are no files to backup #2175
* Enh: Take sub folder into account when testing location for Google Drive Storage #2197
* Enh: Include the current date and time in the database filename when the backup is a "Multipart Backup" #2126
* Fix: Staging site database tables can not be pushed if staging site settings contain different table prefixes #2151
* Fix: Support adding "+" sign in the name of the backup folder by FTP, the name of backup and in the name of clone #2160
* Fix: Check if WP_ENVIRONMENT_TYPE is already defined before adding it to wp-config.php. (Solve conflict with local flywheel). #2165
* Fix: Oldest multipart backups were not deleted during remote upload #2129
* Fix: Prevent fatal error on push when there is no theme installed on production site #2185
* Fix: Continue database restore by using shorter name for identifiers name exceeding maximum allowed characters #2114
* Fix: Add a check to prevent warning undefined variable: jobId #2196
* Fix: Better error handling if folder or file is not writeable #2190
* Fix: Handle errors for PHP 8.x during Database Restore Task when max_packet_size is bigger than the actual sql result #2125
* Fix: Convert utf8mb4 to utf8 when restoring database in MySQL < 5.7 to prevent MySQL Error 1071 because MySQL < 5.7 has max key length of 767 bytes. By converting utfmb4 to utf8 it reduces the size by 1/4 and allows restoring a backup. #2203
* Fix: Restore of backup blocked due to incorrect permission check #2228
* Fix: WP Staging log files could not be deleted #2222
* Fix: Prevents a rare edge case where scheduled backups are continuous started over by implementing a better clean up routing #2231
* Fix: Unable to upload backup files to more than one remote storage in single backup job #2245
* Fix: Fetch google drive backup files in ascending order by time to fix a backup retention issue for google drive #2245
* Dev: Revert all usage of isWritable and isExecutable #2232
* Dev: Broken test _04PushCest after implementing #2199 #2216 #2238