Version
6.0
What did you expect to happen?
optimize:clear to actually clear all caches.
What actually happens?
Presented " Done" but it never removed cached blade views.
Steps to reproduce
This was on a shared hosting so paths were a little different I set "/tmp/sage-cache" however the cache wasn't there I couldn't even find it on the server.
Shouldn't any of the clearing cmds, check that XYZ exists first, then is the dir writeable THEN actually run the clear cmd.
Then that way if I run optimize:clear I can get a warning saying "Error blade view cache at X/Y doesn't exists: Current path :
"
That way I would know to just update config/view.php?
System info
No response
Log output
INFO Clearing cached bootstrap files.
config ............................................................................................................................... 1.36ms DONE
cache ................................................................................................................................ 3.37ms DONE
compiled ............................................................................................................................. 1.81ms DONE
events .............................................................................................................................. 15.42ms DONE
routes ............................................................................................................................... 0.51ms DONE
views ................................................................................................................................ 1.44ms DONE
blade-icons .......................................................................................................................... 0.17ms DONE
acf-composer ......................................................................................................................... 0.38ms DONE
Please confirm this isn't a support request.
Yes
Version
6.0
What did you expect to happen?
optimize:clear to actually clear all caches.
What actually happens?
Presented " Done" but it never removed cached blade views.
Steps to reproduce
This was on a shared hosting so paths were a little different I set "/tmp/sage-cache" however the cache wasn't there I couldn't even find it on the server.
Shouldn't any of the clearing cmds, check that XYZ exists first, then is the dir writeable THEN actually run the clear cmd.
Then that way if I run optimize:clear I can get a warning saying "Error blade view cache at X/Y doesn't exists: Current path :
"That way I would know to just update config/view.php?
System info
No response
Log output
Please confirm this isn't a support request.
Yes