Describe the bug
During the pre-flight check, we set a 5-minute transient boldgrid_backup_wp_size to avoid too many recursive directory size calculations. This is a reasonable time, but the core recurse_dirsize function we use also has its own transient, dirsize_cache, that does not expire.
We should delete this transient before we run pre-flight checks to avoid stale information, especially on REST calls.
To Reproduce
Steps to reproduce the behavior:
Run a pre-flight check
Modify the file size by a noticeable amount
Re-run the preflight check, and note that it has not changed
Run wp transient delete dirsize_cache
Re-run the preflight check and note that it has changed
Additional context
This issue is important for automatic migrations to InMotion Central
Describe the bug During the pre-flight check, we set a 5-minute transient
boldgrid_backup_wp_sizeto avoid too many recursive directory size calculations. This is a reasonable time, but the core recurse_dirsize function we use also has its own transient,dirsize_cache, that does not expire. We should delete this transient before we run pre-flight checks to avoid stale information, especially on REST calls.To Reproduce Steps to reproduce the behavior:
wp transient delete dirsize_cacheAdditional context This issue is important for automatic migrations to InMotion Central