Error during installation
Created 5 years ago by dexter1I have already downloaded everything locally, but when installing it from the web, when I want to start it from the browser, either I get a 404 error, or if I write in the navigation bar the address with the "index.php", I get this:
"Error 500 An exception has been thrown during the rendering of a template ("file_get_contents(C:\xampp\htdocs\pyrocms\public/pyrocms/public/app/default/assets/core/anomaly/select-field_type/resources/scss/search.css): failed to open stream: No such file or directory"). Internal Server Error What does this mean? Something went wrong on our side while we were processing your request. An error has occurred and this resource cannot be displayed.
This occurrence has been logged. We're really sorry about this, and will work hard to get this resolved as soon as possible.
This error can be identified by 76fbeddb-5d97-45a8-8ffa-d6e44de1eadf. You might want to take a note of this code.
Perhaps you would like to go to our home page?"
From the route: "http://localhost/pyrocms/public/index.php/installer"
Looks like you need to route a host for your installation. Try routing example.dev
to your public
path and try again. PyroCMS requires a hostname.
where is it example.dev?
It can be ANY hostname. Just route some hostname to your public directory and try again. PyroCMS request a hostname.
Not sure if this is the same issue you are facing or not: https://pyrocms.com/forum/channels/everything/instalation-or-no
But from the looks of it not being able to access select.css
- I would guess compiling assets failed - in which case I would look at directory permissions. While 777 is not preferable in production - you can safely rule out permissions by running the following commands:
chmod -R 777 storage
chmod -R 777 public/app
chmod -R 777 bootstrap/cache
I assume you're referring to the 777
part? Either way it's very likely permissions are the issue. Those directories need to be recursively writable by the system.
Haha sorry I wasn't aware chmod was linux specific - again though it's a permissions issue. @edster is our resident windows pro - maybe he has something to add here and here: https://pyrocms.com/forum/channels/everything/instalation-or-no
I assume you're referring to the
777
part? Either way it's very likely permissions are the issue. Those directories need to be recursively writable by the system.