Changelog do MainWP Staging

Corrigido

• Unable to create compressed large backup. Extraction and validation of large database fails if it couldn't be completed in a single request.
• Cleanup staging site cache file on cancel. Fix browser console errors on staging site cancel.
• Backup cancel process doesn't cleanup temp files extracted during backup restore.
• Prevent fatal TypeError crashes during backup operations when null values are encountered in file metadata.
• Delete rest url transient after staging site creation to make background logger work on staging sites.
• Invalid ID in HTML of listed remote backup elements.
• Background logger keeps on running after deleting a large staging site.
• Escape invalid HTML entities to prevent DOMDocument parse errors during news feed validation.
• Refresh Last Saved date after saving storage settings. (Pro)
• Exclude wp-content/wp-staging folder by default while performing staging push. (Pro)
• Typo in backup and restore task – "Tmp" should be "Temp".
• Cleanup temporary validation files after backup creation and add a routine to clean the temporary validation directory.
• Prevent staging site creation from hanging when theme folder has no access permissions.
• Change "Twitter" to "X" in notification messages and social links.

Corrigido

• Misleading menu name for copying backup URL.
• Incorrect HTML encoding in log output.
• UX, missing margin in free version for pro feature demonstration text.
• Improve log wording of backup processing. Wrong usage of plural and singular.
• Modal "Another backup is running" looks broken and has sprintf error.
• Prevent possible rare race condition when purging the cache.
• Keep Advanced Options collapsed on Create Backup popup.
• Removing translations from brand names and general global known terms.
• Avoid scanner issues in the backup restore standalone tool.
• Prevent error in email masking for short usernames that have only two characters.
• Opening Settings -> Temporary Logins is slow in free version and takes seconds to load.

Corrigido

• Sanitize sftp options value to fix Uncaught TypeError
• S3 backup (remote storages) authentication process is failing. (Pro)
• Don't copy backup schedules and temporary logins while creating a new staging site. Beautify clone edit modal tooltip text.
• Unable to detect job type during WP Staging status ajax request.
• Missing pro features for the Developer Plan – 30 Active Sites plan. (Pro)
• Handle exclusion rules Other WP Root Folders backup to prevent the inclusion of unintended files/folders. (Pro)
• Empty dirs are not copied during clone, update and push which create issues with third party plugins.
• Improve error message when restore couldn't be possible using free version because server changed.
• Ensure pro features remain accessible even if the license is expired. (Pro)
• On Multisite, Restore fails during database rename task when restoring full network backup if WP Staging plugin(s) are network active. (Pro)
• The restore tool slows to load 'View backup' screen for large backup files. (Pro)
• Remove wp-login.php from staging site login links incl. Temporary Login links to prevent cloudflare restrictions.
• Backup upload failing for Dropbox backup remote storage. (Pro)

Corrigido

• Avoid fatal error after activation of free and pro version together by checking if file exist before to require it.
• Partial table cleanup on the backup restore tool. (Pro)
• Safely clean 'wpstg_version_latest' option key from codebase
• Multiple header issue when inside database content when including large database to the backup.
• Remove trailingslash from backup file path in logs.
• Server get overloaded when uploading large backup to OneDrive. Disable QuickXorHash computing for OneDrive (Pro)
• FTP connection failure due to inconsistent array key casing during backup file retrieval. (Pro)
• Endless loop when Google Drive account has no free disk space and backup uploading to it. (Pro)
• Validate total files count and recount them during backup creation.
• Adding dedicated ID attribute to input forms and making sure ID's are W3C conform in the HTML DOM following a strict standard.
• Misleading errors in backup S3 Storage Provider. Show clear error messages.
• Add margins to the swal popup modal titles for better spacing and appearance.
• AWS s3 error "Content-MD5 OR x-amz-checksum- HTTP header is required for Put Object requests with Object Lock parameters" when object lock is enabled. (Pro)
• Set all WP Staging admin page titles more consistent.
• Incorrect uploads['baseurl'] if the upload_path is outside of absolute path.
• Normalize wp-config content and replaces linefeed with new line while creating staging site.
• Console error on staging site when site is not cloneable and closing the clone delete modal.
• Only WP Staging's plugin is active after backup restore due to object-cache (SpinupWP).

Corrigido

• Some buttons were not translated.
• We've improved how WP Staging handles large files during backups. If a backup step takes too long, WP Staging will automatically allow extra time for it to finish. If it still can't complete successfully, the backup will safely stop instead of running forever.
• If a database collation is missing during table restore, use the general variant for that table restore. Also add a filter wpstg.database.importer.replace_collation to restore with a specific variant if the collation is missing during restore.
• No directories listed during staging process if wp-content folder is symlinked on Flywheel hosting. Enhanced symbolic link handling.
• Prevent unauthorized access to REST APIs on the staging site to avoid potential exploits during plugin updates. (Pro)
• Incorrect backup download URL when downloading backups on WP.com and Flywheel hosted sites.
• Automatically disable DEBUG constants on staging sites to prevent unwanted debug warnings.
• Add an alternative way to copy files during cloning and push when php native copy method fails on some system.
• Some older compressed backups couldn’t be restored due to a file header error. This update fixes the issue so those backups can now be restored properly.
• Backup older than version Pro 5.0.4 or Free 3.0.4 is considered v2 backup, thus can not be restored.
• Enhance error handling and response messaging for failed license activation attempts.
• UX: Fix the dark mode issue on the Restore Tool page.

Corrigido

• Prevent logging out Google Drive from all sites if connection of one site is removed. Don't revoke google drive token, only remove data from db. (Pro)
• Handle toggling of DB Privileges popup message while creating staging site. (Pro)
• Remove unnecessary styles and scripts on WP Staging admin pages.
• Automatically update outdated plugins on the staging site while creating, updating and resetting a staging site.
• Remove the ETA from the backup process locking modal.
• Ensure that Pro features are available for the Legacy Developer Unlimited License plan. (Pro)
• WP cron does not work on staging site - Scheduled posts aren't working on staging sites.
• Remove duplicate file headers in V2 backup files (Repair function) and allow backup restore even if there are duplicate file headers.
• Choose a unique staging site name that is not already in use.

Corrigido

• Automatically activate free version after its installation when pro version is already active. (Pro)
• Better handling the backup process elapsed time when the browser tab is inactive in background.
• Update backups retention number after deleting remote backup. (Pro)
• Backup file can't be downloaded in WordPress Playground.
• Remove warnings in backup debug logs.
• Display the ongoing progress percentage while downloading the backup from remote storage. (Pro)
• Properly handle HTML entities and preserve line breaks while sending backup email notifications.
• Show accurate tables count during staging site creation.
• Missing initial backup index to restore database with the WP Staging Restore tool.
• PHP "Uncaught TypeError" and remove useless logs for backup to Microsoft OneDrive. (Pro)
• Undefined property: stdClass::$error - File: wp-staging-pro/Pro/License/Licensing.php Line: 193. (Pro)
• Prevent duplicate file headers for database when including large database in multiple requests in the backup.
• Remove wpstg-restore.php from free version.
• Improve design of some modal.

Corrigido

• Bypass optimizer while email sending debug logs in basic version.
• Tooltip is not vertically aligned with the label text.
• Google Drive Scheduled Backup Fails Due refresh token mechanism not functioning properly. (Pro)
• Expanding Other Root Files selection is jumping. (Pro)

Corrigido

• Unexpected end tag error in Newsfeed Validator.
• Replace breakdance page builder plugin data URLs when restoring a backup to a different domain.
• Bypass additional login on the staging site when accessing it using a magic login link.(Pro)
• Display a tooltip next to the wp-content' folder if it is symlinked to another location.
• Show an admin message if the site is hosted in the elementor cloud.
• Handle type error listing staging sites due to corrupted staging site option. Also add actions to fix and report corrupted staging sites option.
• Url params do not update correctly when navigating through settings's pages
• Ensure the staging site title is truncated gracefully if it exceeds the maximum length.
• Verify user privileges for external database before creating staging site. (Pro)
• Disable symlink to the uploads folder when symlink is unavailable or restricted by the hosting provider to prevent potential fatal errors during staging site creation.(Pro)
• Restorer tool fails to restore large database files.
• Redirection to 127.0.0.1 or a custom domain after backup restore.
• Beautify Update Modal using CSS
• Root folders selection link does not work in free version (console error).
• Show the license notice exclusively on the license page of the staging site.
• Replace the base64_decode function in the restorer tool to avoid being flagged as malware.

Corrigido

• Upgrade link position broken on basic version for wp root files selection before backup.
• Ensure proper backup retention for cloud storage backups running in the background. (Pro)
• Optimize lazy loading of placeholders when rendering DOM elements.
• Selection of Other WP root folders is not intuitive during backup creation. (Pro)
• Redirect User to Install page after activating WP Staging Pro if core version not installed. (Pro)
• Log the list of Must-Use' plugins and Drop-In' files in the system information.
• Bring back Mails Settings tab on staging site Settings page. (Pro)
• Add a rule to whitelist all plugins for internal use in optimizer.
• Prevent extraction of already extracted file which could happen if a file was scanned multiple times while backup creation.
• Handle backup listing when backup is missing data in backup metadata.
• Display a message when a higher license plan upgrade is required on the temporary login page. (Pro)
• Missing semicolon in require statement threw error in php 8.1. Added phpcs rule rule to check for missing semicolons after including files.

Corrigido

• Remove wpstg-blank-loader.js from being loaded on frontend.
• Optimizer plugin is not updated when free and pro version is different.
• Exclude the root directory from scanning during the cloning process.
• Don't show cache related admin notice on staging site when WP_CACHE is set to true.
• German translation can break layout of some modals.

Corrigido

• Deleting an unfinished staging site, does not delete its folder.
• Filesystem scanner keeps on running during backup creation.
• Autosave WordPress Permalinks after creating a staging site.
• Files index error due to invalid files count in multipart backups. backup is still restorable as this is only a logging error!
• Remove wordpress.com related messages.
• Rare fatal error "Call to undefined function apache_get_modules" after the push process. (Pro)

Corrigido

• Make some missing string translatable.
• Change twitter logo to X
• Unable to create and view backups when WordPress root directory is not readable.
• Knowledgebase and What's new blocks are not looking good under Settings, System Info and License page.
• Make sure that backup is restored properly when W3 Total Cache is installed on production site.
• Download Backup Modal has broken css. (Pro)
• "PHP Fatal error: Uncaught TypeError: property_exists " with Google Drive auth. (Pro)
• A typo in I18n.php file
• Database cloning doesn't work if using mixed upper and lower cases in database prefix when MySQL uses the setting lower_case_table_names.
• Cannot restore database when the last CONSTRAINT is not correctly replaced in a CREATE TABLE query.
• Handle temporary login link creation properly after creating staging site. (Pro)
• Main menu navigation not working during development.

Corrigido

• Obfuscating log file names to avoid prying eyes.
• Make sure to dont generate login link if PRO version not defined.
• Undefined CURL constant while gathering system info.
• Use correct i18n title for delete confirm modal popup.
• Can't install core version when install WP STAGING PRO 5.8.6.

Corrigido

• Fatal error due to calling php_uname if it is disabled by hosting providers.

Corrigido

• Preserve login by link data on staging site after update process. (Pro)
• Adjust php 5.6 compatible message and disable email footer in feedback emails.
• Delete W3 Total Cache drop-in files during push job when the Push Changes > Uninstall all plugins/themes on production site option is selected.
• Stop backup creation earlier when the server disk is full.
• Global translation po & mo files are not recognized. Load translations files from wp-content/languages/plugins folder.
• Automatically send request using GET method to fire queue ajax if POST method doesn't work. Add filter wpstg.queue.request.force_get_method to force use GET method. Useful in case if somehow the POST method for ajax request is blocked by hosting provider or other plugins.
• Resolve console errors caused by duplicate and missing HTML element IDs.
• Don't use the same dropbox data for live and staging site. (Pro)
• Unable to write file header for v2 backups on Windows OS.

Corrigido

• Make clear what login credentials to use when WP Staging | Restore standalone installer is used on a new site after backup restore.
• Validate database prefix when creating a staging site to confirm it does not begin with the production site database prefix.
• Increase delay interval between backup status requests from 5 seconds to 8 seconds to reduce chances of 503 errors. Add filter wpstg.backup.interval.status_request to customize this value.
• Show actual installed free version in system information.
• Make sure that the Reset process works correctly even when the staging site database has FOREIGN_KEY_CHECKS enabled.
• Remove duplicate ajax requests for backup related operations.
• Make the validate icon displayed correctly.
• Search and replace does not work when url contains 'www.'.
• Make Ninja Forms work properly after performing backup restore.

Corrigido

• Make sure that Show Logs button should have consistent margins when rendering process logs.
• Disable email notifications when a backup successfully runs.
• Properly catch fatal errors when merging logs into single file when sending for error report.
• Make the backup restorable even when it has not correctly replaced table Constraint(s).
• Make sure to update new admin login password if account already exists while creating staging site.(Pro)
• Refresh error message when clicking the backup tab.

Corrigido

• Backup Restore failed to read the cache file of old object data when using PHP 7.2.
• Make sure to backup all other files in the WP root directory when running background backup.
• Ensure that backup process works properly when attempting to create multipart backup with free version.
• Show correct timestamp when retrieving remote backup from an FTP storage provider. (Pro)
• Google authentication throws exception when user cancels backup auth process. (Pro)
• Fatal error on activation of WP Staging Pro on PHP 7.0. (Pro)
• Sometimes warnings were generated during PUSH when trying to cleanup tmp directory for plugins and themes.

Corrigido

• WP Staging Restore failed to read the cache file with old object data when using PHP 7.2.
• Make sure to display correct time stamp when retrieving remote backups from an FTP storage provider. (Pro)

Corrigido

• Magic login link does not work when it is used more than one time. Requires updating existing staging sites to fix this. (Pro)
• Handle staging and backup creation when file name contains new line character.
• Make "copy to clipboard" button works properly in all browsers, regardless of protocol (HTTP, HTTPS).
• Show correct folder count if the staging site file structure contains multiple plugin and theme folders.
• Prevent backup retention from being modified when scheduling backup.
• Show 'Settings form' after authenticating with storage providers Google Drive and Dropbox.
• The site URL is not replaced correctly in the blog table on PUSH for network subsites that have a different domain than the main site. (Pro)
• Several PHP warnings when using RESET on an existing staging site.
• Optimize and clean up CSS. Fix X and Github icons. Remove of '!important' declarations in dark theme.
• Validate new admin account email address before cloning.
• Make sure appropriate message is displayed after successful backup.
• Some files may not be scanned and/or copied during staging site creation if their relative path to ABSPATH contains the value of ABSPATH.
• Use wp_kses instead of esc_html when logging backup message in logger, to keep json formatting for messages.

Corrigido

• Unable to restore backup when it contains huge number of files which requires extracting in multiple requests.
• Improve reliability and robustness of the background processor: Stalled actions will automatically be cancelled if they are in processing state for more than 15 mins.
• Backup by URl throws error "Invalid backup file content".
• Standalone restorer randomly terminated while restoring large files.
• The backup version of WP Staging Restore is not up to date.
• Refactor the contact form. New default options for sending backup log files and accepting privacy policy.
• Ensure listing of remote backups and uploading of local backups to cloud storage works correctly.
• Hide sensitive fields (secret key, access key...) in backup storages settings.
• Don't optimize the .htaccess as default any longer if server is litespeed. Revert to old behavior by using the filter wpstg.create_litespeed_server_config.
• Table Renaming Task fails during Restore and Push if database prefix contains capital letter(s) and database is hosted on Windows based OS system i.e. Microsoft Azure.
• Disconnect google drive account if it fails to refresh access token.
• Cloud storage options are overlapped by other elements.
• Don't load and list remote backup for dropbox as it is not supported yet. (Pro)

Corrigido

• Keep cloud storage connected to Google Drive even if files listing from remote storage fails. (Pro)
• Sync User Account feature duplicates existing user as administrator role.
• Backup restore stuck on importing users for subsite when restoring an old backup on single site.
• Make sure to handle fatal error due to missing COLLATE while creating 'wp_wpstg_queue' table for scheduled backup.
• Hide the 'wp-content/wp-staging-sites' folder from staging site directory selection, as it is always excluded during cloning.
• Show exact error message for open_basedir restriction error if destination directory does not have write permissions.
• Memory usage of the staging site is higher than of the live site.
• Make sure to only sync production site's users fields that exist in cloned site's users table.
• Send log files from last 14 days and compress them before sending. Add Contact Us button to error messages.
• Make sure to display default login link on custom login form if login is blocked by a security plugin with OTP or 2FA enabled.
• Ensure that the All in One Security Plugin (AIOS) isn't disabled by the wp staging optimizer when AIOS's salt option is enabled.
• Reconnect DB if mysql has gone away during update of queue table.
• Create backup folder in google drive, if it does not exist, before uploading to backup cloud provider.
• Make sure loading bar is removed once a WP Staging page is refreshed successfully

Corrigido

• Generated create table DDL is corrupted during backup creation if table DDL contains multiple constraints with CASCADE, SET NULL, SET DEFAULT, RESTRICT or NO ACTION referentials actions.
• Backup Type missing in scheduling options. Resulting in creation of entire multisite backup even for just subsite backup on multisite.
• Resolve browser warnings due to invalid HTML syntax.
• Make sure to remove the loading placeholder after 5 seconds if the server call experiences delays or fails due to any error.

Corrigido

• On some server files were not properly extracted. Using a fallback function now.
• Fix condition to check custom destination path for staging site on basic version.
• Warning "Indirect modification of overloaded elements" of WP_Hook.

Corrigido

• If endurance-page-cache mu-plugin is installed (on Bluehost and Hostgator) a staging site shows white page error then.
• Backup retention does not work for backups created on a staging site.
• Backup log entries could contain log entries from staging processing under certain circumstances.
• Moved tmp directory to wp-content/wp-staging/tmp to fix a cross-device link error on sites hosted on Azure.
• Make sure that there are no errors in console after uploading backup to remote storages.
• Handle complex table relation syntax on SQL dumper and restorer.
• Validate and handle null values before invoking strlen to ensure compatibility and prevent runtime errors.
• Make network cloning more robust by supporting different combination of www prefix.

Corrigido

• Remove two css files accidentially loaded on the frontpage.
• Remove standalone installer - Not ready yet.
• Make sure to not encode single and double quotes while downloading log files.

Corrigido

• Fatal error on old WordPress 4.4.32 due to using of get_current_network_id.
• Base prefix wrongly replaced for users and usermeta tables in views when creating backup of views in multisite subsite.
• Prevent error while directory listing protection due to open_basedir restriction.
• Update free version plugin meta description to "Required by WP Staging Pro".
• Remove redundant admin notices for invalid license keys during activation.
• Make sure EDD license checks are triggered only once.
• Google drive authentication not working properly under all circumstances.
• Selected custom tables on a staging site that had a different prefix than the prefix in the wp-config.php could not be pushed anymore.
• Prefix for user capabilities was not replaced when creating a backup of network subsite.
• The "Prefix" field was empty for listed staging sites if they were created in an external database and the prefix was not specified.
• The optimizer setting was shown as disabled, even if it was still active.
• Add loading icon beside 'Refresh License Status' button and adjusted loading bars on licensing page.
• Super (network) admins were not able to login with when network subsite backup was restored on a single site.
• Reference Error wpstgPro is not defined during staging site creation on FREE version.
• Make sure that backup plugin notice doesn't overlap Create Staging Site button in UI.
• List of active plugins in system info is misleading.
• Make sure that mail setting page looks good on all screen resolutions.
• Incorrect process modal title for preserving data task.
• DRY properties in BackupMetadata and remove error message "trying to hydrate dto errors BackupMetadata::setCurrentNetworkId "

Corrigido

• Can not update email address for sending error reports.
• Deprecation message about dynamic properties thrown by Google Drive Api Model class. Show exact error message when unable to get resume URI for Google Drive backup upload.
• Make sure to not check external DB credentials in free version while creating staging site.
• Editing the backup schedule sometime re-creates the schedule cron at a wrong time.
• Add filter to hide primary key changes message and include primary key details in the system information.
• Not all files are sometimes pushed under certain situation.
• Scheduled Backups unable to run when a manually created backup exists.
• The backup retention number of Google Drive backups isn't honored.
• Handle issues when unable to fetch information for external database during cloning requirements.
• Show correct version of WP Staging in backup and staging log files.
• Type error when passing multiple parameters using hooks methods.
• Reduce height of the delete staging site modal.

Corrigido

• Catch type errors on properties hydration for Backup Metadata and other backup related tasks.

Corrigido

• Handle warnings when unable to unserialize serialized data during cloning.
• Don't logout when restoring backup wp.com site on last step when database was not restored.
• PHP Fatal error: Uncaught TypeError when using Litespeed server.

Corrigido

• Although all tables were renamed correctly during backup restore, the backup restore log sometimes show incorrect number of tables restored.
• Can't serialize unserialized data that has an instance of a class in the object. Relevant for backup and backup restore.
• Make sure to execute backup performance javascript only when creating a backup.
• Installing the required free version when installing the pro version might disable all network active plugins on a multisite network.
• Improve cleaning up of cache files after pushing and backup.
• If only one file is selected for pushing, that file is not copied.
• Under rare circumstances a push could miss to copy the last file of a queue.
• On Bitnami Hosted WordPress Sites, Plugins and Themes are not replaced during PUSH due to symlinked wp-content folder.
• Undefined index of databaseSsl
• Notice "Free version required" may show up on network admin page while backup free version is not network activated.
• Don't show "Customized uploads folder notice" when host is flywheel.
• Make sure javascript events are only registered when the corresponding element is loaded in the DOM.

Corrigido

• Automatic backup repair if the backup file index is corrupted.
• Saves remote storage backup in the database for use when calculating the number of backup to keep on remote storage.
• Prevent accessing the content of backup cache files created during cloning and pushing jobs.

Corrigido

• Page loading wrapper was overlapping elements on staging page. Add a loading bar below the header menu when switching between staging and backup main tabs. Adjust the delete modal!
• Exclude unused themes filter doesn't work properly for entire multisite backup.
• Urls containing port i.e. example.com:8080 were not correctly replaced during using backup for site migration if destination site has different port.
• Due to presence of www prefix in constant DOMAIN_CURRENT_SITE on the destination site during backup restore, both source and destination weren't considered same site for updating subsites related URLs.
• Remove Type strictness from custom wp_mail function used in staging site when mail sending is blocked to avoid "Uncaught TypeError".
• Unable to create directory with correct permissions in ABSPATH when ABSPATH has wrong or custom permission i.e. 0170 but ABSPATH is writeable during staging site creation.
• Upsell welcome page shows up when pro is installed and free activated.

Corrigido

• Siteground backup related issue: file_put_contents doesn't free up resources automatically immediately, which caused error 500 during backup extraction on SiteGround hosting (due to limited resources).
• For domain based subsites during backup restore, home and site_url were not adjusted properly automatically.

Corrigido

• Warnings in WordPress 6.4 because WordPress removed property $wpdb->use_mysqli. This could lead to a backup error.

Corrigido

• Improve design of the "delete staging site" modal.
• Existing previously created backup files may be invalid under certain circumstances and can lead to a faulty website after restoration. This is a highly recommended update! Please create a new backup after installing this update to ensure that this potential error does not affect your backup file.
• Remove warnings in debug.log that say "WP STAGING: Another instance of WPSTAGING active...".