Closed gpenglase closed 2 months ago
Hi @gpenglase could you please test with the latest 3.6.7 version?
This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.
ERROR: Exception caught in Error: Call to a member function close() on null
All sites using 3.5.0 since upgrade are reporting the above error when trying to compress the individual parts (XML, WXR, pluginlist etc.) prior to final archiving - disabling that and saving the Job seems to resolve this. (I actually don't see the benefit in compressing individual files prior to archiving the whole lot - it just adds time to the backup process for no reason.)
Also, when I do a manual backup I notice the "Running for: 524 seconds" appears on the wrong job in Job list (I always have a separate DB and a Full backup in the list) and is also reporting the wrong length of time. Additionally, the time it states under the "Last Run" heading when you click a new job run is incorrect, and then the time the progress bar says it took (84secs) is different than what it saves under the "Last Run" heading (May 21, 2018 at 3:21 pm Runtime: 136 seconds) - ie. it updates the job datetime but not the run time.