You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This request isn't a duplicate of an existing issue
I've read the docs and followed them (if applicable)
This is not a personal support request that should be posted on the Roots Discourse community
Description
When running wp acorn optimize, the cached config is used even after clearing it. This causes the command for fail if for example the cached config contains paths that no longer exist. Running cache:clear before optimize works.
Steps to reproduce
Run optimize
Do as search-replace in /storage/framework/cache/data/config.php do replace the log paths with one that does not exist.
Run optimize again
Expected behavior: [What you expect to happen]
The command would clear all caches, reload the config, and then generate new caches.
Actual behavior: [What actually happens]
The command would clear all caches, continues using the old cached config, and throws an unhandled exception when an invalid path is encountered.
Reproduces how often: [What percentage of the time does it reproduce?]
Every time.
Versions
PHP 7.4.3
Acorn v1.1.0
WordPress 5.5.3
Additional information
Here's the stack trace from the first error that happens for me. The stack trace printed on the console is different because it covers when the logger fails to initialise when trying to log this first exception.
Description
When running
wp acorn optimize
, the cached config is used even after clearing it. This causes the command for fail if for example the cached config contains paths that no longer exist. Runningcache:clear
beforeoptimize
works.Steps to reproduce
optimize
/storage/framework/cache/data/config.php
do replace the log paths with one that does not exist.optimize
againExpected behavior: [What you expect to happen]
The command would clear all caches, reload the config, and then generate new caches.
Actual behavior: [What actually happens]
The command would clear all caches, continues using the old cached config, and throws an unhandled exception when an invalid path is encountered.
Reproduces how often: [What percentage of the time does it reproduce?]
Every time.
Versions
PHP 7.4.3
Acorn v1.1.0
WordPress 5.5.3
Additional information
Here's the stack trace from the first error that happens for me. The stack trace printed on the console is different because it covers when the logger fails to initialise when trying to log this first exception.
The text was updated successfully, but these errors were encountered: