?
avatar proman24
proman24
15 Oct 2018

Steps to reproduce the issue

  1. Clone joomla-cms/4.0-dev branch.
  2. npm install in the CMS directory.
  3. composer install in the CMS directory.

Expected result

CMS should be accessible through web browser.

Actual result

CMS is not accessible rather this issue is being showed.
screen

System information (as much as possible)

OS : Ubuntu 18.04.1 LTS

Additional Comments

I have tried this command too but the result remains the same
alias jinstall="rm -rf administrator/templates/atum/css; rm -rf templates/cassiopeia/css; rm -rf media/; rm -rf node_modules/; rm -rf libraries/vendor/; composer install; npm install; git checkout -- libraries/vendor/.htaccess"

avatar proman24 proman24 - open - 15 Oct 2018
avatar joomla-cms-bot joomla-cms-bot - change - 15 Oct 2018
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 15 Oct 2018
avatar TobsBobs
TobsBobs - comment - 15 Oct 2018

I already had this problem. I just ran npm again and then it worked.

avatar brianteeman brianteeman - change - 15 Oct 2018
Status New Closed
Closed_Date 0000-00-00 00:00:00 2018-10-15 08:22:19
Closed_By brianteeman
avatar brianteeman
brianteeman - comment - 15 Oct 2018

As per the instructions it is git, composer and then npm. If you still have problems then look in your error log and post back

avatar brianteeman brianteeman - close - 15 Oct 2018
avatar proman24
proman24 - comment - 15 Oct 2018

@TobsBobs I tried npm install again this log is being popped up in the console, but the status remains the same.
npm install

avatar mbabker
mbabker - comment - 15 Oct 2018

You need to check and fix your system permissions. Generally, you should not be using sudo with npm.

Just a blind guess, but what is probably happening is the various tasks that are executed with an npm install on the repo are failing because those are NOT being executed with sudo and it is failing since those are trying to be run as your own user yet the node_modules directory is owned by root.

avatar proman24
proman24 - comment - 15 Oct 2018

Thank you @mbabker, Problem resolved :-)

Add a Comment

Login with GitHub to post a comment