No assets in public/assets folder


(Mark) #1

Getting a black screen after login. At the login screen inspecting the page shows there are no files being found in the assets folder.

Situation
Using a clean CentOS 7 install with PHP 7.2 and clean clone of OpenEMR

OpenEMR Version
Latest github

Browser:
I’m using: Chrome

Operating System
I’m using: 10

Logs

GET http://.../openemr/public/assets/bootstrap/dist/css/bootstrap.min.css?v=60 net::ERR_ABORTED 404 (Not Found)
login.php:10 GET http://.../openemr/public/assets/jquery-ui-themes/themes/ui-darkness/jquery-ui.min.css?v=60 net::ERR_ABORTED 404 (Not Found)
login.php:11 GET http://.../openemr/public/assets/font-awesome/css/font-awesome.min.css?v=60 net::ERR_ABORTED 404 (Not Found)
login.php:13 GET http://.../openemr/public/assets/jquery/dist/jquery.min.js?v=60 net::ERR_ABORTED 404 (Not Found)
login.php:14 GET http://.../openemr/public/assets/bootstrap/dist/js/bootstrap.min.js?v=60 net::ERR_ABORTED 404 (Not Found)
login.php:15 GET http://.../openemr/public/assets/jquery-ui/jquery-ui.min.js?v=60 net::ERR_ABORTED 404 (Not Found)
login.php:14 GET http://.../openemr/public/assets/bootstrap/dist/js/bootstrap.min.js?v=60 net::ERR_ABORTED 404 (Not Found)
login.php?site=default:15 GET http://.../openemr/public/assets/jquery-ui/jquery-ui.min.js?v=60 net::ERR_ABORTED 404 (Not Found)

(Stephen Waite) #2

hi @madmax, after you clone you have to follow this to build it


(Mark) #3

Hi there, I did run all those, and re-ran when i recloned 2/3 times, but each time no files are getting generated in the assets folder.


(Stephen Waite) #4

ok, nice, so the

npm install
npm run build

ran without any errors just warnings?


(Mark) #5

That is correct, just warnings no errors.


(Mark) #6

Was able to work around this issue by manually copying all the folders from node_modules into ./public/assets folder.

I cannot see/find why these are not being copied over when I run the npm command.

I also notice that jquery-ui does not get downloaded/installed in any form with the npm command either.


(ViSolve) #7

Hello Mark

We guess you have executed "npm install " as a root user.

When the command is executed as a root user, we may get the following warning which will avoid running the npm postinstall commands :

The solution will be either:

  1. Donot run the “npm install” using root user and try running with other user
  2. Or execute the below command with root user:
    "npm install --unsafe-perm"

Thank You
ViSolve-105