Opened 6 years ago
Last modified 3 years ago
#44418 new defect (bug)
fs_unavailable while auto-updating plugins
Reported by: | ecomevo | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | 4.9.6 |
Component: | Upgrade/Install | Keywords: | needs-patch has-screenshots reporter-feedback |
Focuses: | Cc: |
Description
This is a follow-up to #38024.
This happens when plugins are updated automatically in the background (see attached screenshot).
Attachments (1)
Change History (3)
#2
@
3 years ago
@ecomevo Similar to the question from @afragen: Have you experienced this problem again since you opened this ticket?
Looking at your screenshot, it appears that after successfully updating Woo, your system attempted to update it again in the same "session"...which would result in an "error" because no update was needed that 2nd time.
If that 2nd attempt was a result of a bug in core, I suspect we would have received many other reports of people having this problem. So, like, Andy, I suspect some other plugin you had activated at the time caused the 2nd update attempt.
Granted, the "Could not access filesystem" error message is not the most helpful in that case, but I think that's what happened.
Is there something else particular to your installation? I don't see this for auto-updates.