Sage 9 assets path in wordpress subfolder installation

[Ale_Prieto]

I’m doing yarn build:production for a deploy in a production server that is in a subfolder installation (/v2) but in local I’m running in /

Is there a way to tell webpack to build the assets path to that /v2/ folder?

I’m getting /wp-content/themes/fedesam/dist/images/image.png in my dist/style files but I need to be /v2/wp-content/themes/fedesam/dist/images/image.png

Thanks!

[cordial]

Edit the public path field in your config.json to be /v2/wp-content/themes/themeName. If u want different paths setup for each one then this may help

publicPath (dev vs. prod)

Set it in config.js with a conditional statement or something. Delete this line from config.json. Add some sort of condition to this property Like this: const config = mergeWithConcat({ // ... publicPath: isProduction ? '/wp-content/themes/sage/' : '/website.com/wp-content/themes/sage/', // ... }, userConfig) Or if you’d like to keep the option in config.json, then you can adjust the logic in some other way, obviously. This is simply an example of how you can do it.

[alwaysblank]

You can set the public path dynamically from the command line without modifying Sage’s build process by setting SAGE_DIST_PATH:

roots/sage/blob/f3e794a09374d2f110742d15b9b975490fcddbee/resources/assets/build/config.js#L43-L48

[pallan]

Hi. This is exactly what I’ve been looking for as my staging is in a sub folder and assets that are called from CSS (fonts and bg images) are missing the subfolder name in the path. I feel rather awkward asking, but how do you implement this. I tried uncommenting this section in the config file but of course this errors. I’m sure it’s simple. Cheers.

What do I do with this?
SAGE_DIST_PATH=/subfolder/wp-content/themes/sage/dist/ yarn build:production

[Ale_Prieto]

Hi pallan! In the file package.json you have to modify that line in the script section:

"scripts": {
...
    "build:production": "SAGE_DIST_PATH=/subfolder/wp-content/themes/fedesam/dist/ webpack --env.production --progress --config resources/assets/build/webpack.config.js",
...
}

[pallan]

Thanks. Much appreciated.