Hello, I successfully built my Sage theme with version 11, and after activating the theme on WP-Admin, I am getting the following error. Is there any option to fix it? Thanks for your help! Error message shows on the page: Fatal error: Uncaught Exception: The C:\Users\Adrian\Local Sites\sagetheme\app\public/wp-content/themes/sage\C:\Users\Adrian\Local Sites\sagetheme\app\public/wp-content/cache/acorn/framework\cache directory must be present and writable. in C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\PackageManifest.php:179 Stack trace: #0 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Roots\Acorn\PackageManifest.php(91): Illuminate\Foundation\PackageManifest->write(Array) #1 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\PackageManifest.php(108): Roots\Acorn\PackageManifest->build() #2 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\PackageManifest.php(91): Illuminate\Foundation\PackageManifest->getManifest() #3 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\PackageManifest.php(80): Illuminate\Foundation\PackageManifest->config(‘aliases’) #4 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Roots\Acorn\Bootstrap\RegisterFacades.php(25): Illuminate\Foundation\PackageManifest->aliases() #5 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\Application.php(342): Roots\Acorn\Bootstrap\RegisterFacades->bootstrap(Object(Roots\Acorn\Application)) #6 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\Http\Kernel.php(187): Illuminate\Foundation\Application->bootstrapWith(Array) #7 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Roots\Acorn\Application\Concerns\Bootable.php(114): Illuminate\Foundation\Http\Kernel->bootstrap(Object(Illuminate\Http\Request)) #8 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Roots\Acorn\Application\Concerns\Bootable.php(40): Roots\Acorn\Application->bootHttp() #9 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Roots\Acorn\Configuration\ApplicationBuilder.php(149): Roots\Acorn\Application->bootAcorn() #10 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\functions.php(38): Roots\Acorn\Configuration\ApplicationBuilder->boot() #11 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-settings.php(672): include(‘C:\Users\Adrian…’) #12 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-config.php(103): require_once(‘C:\Users\Adrian…’) #13 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-load.php(50): require_once(‘C:\Users\Adrian…’) #14 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-admin\admin.php(34): require_once(‘C:\Users\Adrian…’) #15 C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-admin\index.php(10): require_once(‘C:\Users\Adrian…’) #16 {main} thrown in C:\Users\Adrian\Local Sites\sagetheme\app\public\wp-content\themes\sage\vendor\roots\acorn\src\Illuminate\Foundation\PackageManifest.php on line 179
There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.
There’s some bugs in Acorn with Windows right now. You’ll need to use a WSL-based dev environment for the moment.
Work in progress to get things fixed: 🩹 Use `DIRECTORY_SEPARATOR` for fallback storage path by Log1x · Pull Request #441 · roots/acorn · GitHub — this isn’t working 100% just yet
Make sure to read https://discourse.roots.io/t/how-to-best-ask-questions-on-this-forum/24582 and put in some more effort with your posts (more details, proper formatting, versions of everything)
Thank you for your response! I tried with WSL, but I have the same problem. There is any other option?
It’s impossible to have that problem on WSL with the paths
Describe your setup.
I have installed Ubuntu 22.04 as WSL2. I have installed Volta, and I installed Composer with Linuxbrew. I am not using the root account on WSL
I’m not participating in this back and forth anymore
You did nothing to explain how your site is being served from a WSL environment
I promise you won’t be having this issue if you are serving a site from WSL
Feels like you didn’t read How to best ask questions on this forum whatsoever