The theme directory "[THEME]/resources" does not exist

cleanboy · August 9, 2019, 9:01pm

Hi guys,

So I am deploying a site to a staging environment so my clients can view before we go live…locally everything has been fine…I follow the documentation to get everything online but I am greeted with a blank page.

I try to log in and that seems to work, I go back to the front page of the website and get the error that is the title of this post:

The theme directory “THEME_NAME/resources” does not exist.

The only difference between that and local is that online it seems to want capitals, so I go ahead and rename the folder on the server to the same thing but uppercase. This seems to fix the problem however this seems to break things being pulled from the /dist/vendor folder inside my theme.

I’m hoping there is a quick fix where I can just change the theme name somewhere it is being incorrectly referred to in capitals?

Any help would be greatly appreciated…

Thanks!

knowler · August 10, 2019, 6:53pm

Make sure to update the publicPath key to match your production environment or if this path differs between environment you can use the SAGE_DIST_PATH environment variable when your build for production:

github.com

roots/sage/blob/9100cea66b8ad1b98056954e742d259d276ddfc3/resources/assets/build/config.js#L43-L60


      
          /**
           * If your publicPath differs between environments, but you know it at compile time,
           * then set SAGE_DIST_PATH as an environment variable before compiling.
           * Example:
           *   SAGE_DIST_PATH=/wp-content/themes/sage/dist/ yarn build:production
           */
          if (process.env.SAGE_DIST_PATH) {
            module.exports.publicPath = process.env.SAGE_DIST_PATH;
          }
          
          /**
           * If you don't know your publicPath at compile time, then uncomment the lines
           * below and use WordPress's wp_localize_script() to set SAGE_DIST_PATH global.
           * Example:
           *   wp_localize_script('sage/main.js', 'SAGE_DIST_PATH', get_theme_file_uri('dist/'))
           */
          // Object.keys(module.exports.entry).forEach(id =>
          //   module.exports.entry[id].unshift(path.join(__dirname, 'helpers/public-path.js')));

Once you’ve done that, you need to rebuild the theme assets (for production), since the URIs for the linked assets (in stylesheets or scripts) are absolute not relative.

cleanboy · August 15, 2019, 9:16pm

Hi,

Thanks for your time and your reply.

I have updated it and renamed the folder locally to all caps instead of lower case but now I Have the problem that git doesnt seem to recognise the folder re-name and still pushes with lower case theme folder name…

I know this isnt the right place to ask for git help but…Help!

knowler · August 15, 2019, 9:33pm

Use these:

# This removes the files from Git, but keeps the files (unstaged).
$ git rm -r --cached <relative/path/to/your/theme>
# Re-stage the files.
$ git add <relative/path/to/your/theme>

system · September 20, 2019, 9:10pm

This topic was automatically closed after 42 days. New replies are no longer allowed.