[GH-ISSUE #368] issues while installing v2.2.0 #267

New issue

Closed

opened 2026-02-26 02:32:37 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 02:32:37 +03:00

Owner

Originally created by @grandvizier on GitHub (Jun 28, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/368

I ran into a few issues during the install that took a bit of debugging to work through, only to determine that v2.2.0 isn't functional at this time.

These first points are simply things that might make other peoples install process a little smoother:

First issue is that it would be nice if npm & composer were listed in the Server Requirements section.
Second problem faced was that node needed to be a symlink for nodejs, this was discovered after retrying npm install because the first run through with php artisan koel:init made that error hard to find.

This is were I had specific version issues:

In resources/assets/sass/vendor/_plyr.scss, $plyr-control-color-hover wasn't defined at line 289. To get passed this I just modified the if-clauses around line 39. Then after running the init command again, I was finally able to load a login page.
After input of my email/password, I was then left on a blank page suggesting me to be patient for a long long time. I looked into the logs, but there was no interesting output. I opened the web browser console and there was a js error about this.player.setVolume is not a function. At this point I reverted to the branch 2.0 and everything is now working.

Note: since I still had the .env file setup, I was using php artisan koel:init to re-initialize after code changes. I suppose it might be possible that npm install & composer install as per the release instructions may have had different results.

Originally created by @grandvizier on GitHub (Jun 28, 2016). Original GitHub issue: https://github.com/koel/koel/issues/368 I ran into a few issues during the install that took a bit of debugging to work through, only to determine that v2.2.0 isn't functional at this time. These first points are simply things that might make other peoples install process a little smoother: - First issue is that it would be nice if `npm` & `composer` were listed in the _Server Requirements_ section. - Second problem faced was that node needed to be a symlink for nodejs, this was discovered after retrying `npm install` because the first run through with `php artisan koel:init` made that error hard to find. This is were I had specific version issues: - In `resources/assets/sass/vendor/_plyr.scss`, `$plyr-control-color-hover` wasn't defined at line 289. To get passed this I just modified the if-clauses around line 39. Then after running the init command again, I was finally able to load a login page. - After input of my email/password, I was then left on a blank page suggesting me to be patient for a long long time. I looked into the logs, but there was no interesting output. I opened the web browser console and there was a js error about `this.player.setVolume is not a function`. At this point I reverted to the branch `2.0` and everything is now working. Note: since I still had the `.env` file setup, I was using `php artisan koel:init` to re-initialize after code changes. I suppose it might be possible that `npm install & composer install` as per the release instructions may have had different results.

kerem closed this issue

2026-02-26 02:32:37 +03:00

kerem commented

2026-02-26 02:32:38 +03:00

Author

Owner

@phanan commented on GitHub (Jun 29, 2016):

Any reason why it's 2.2.0 and not the latest stable 2.2.1? Before v2.2.1, plyr was required as ^1.5.13 and later minor versions from this package had backward incompatibilities that broke Koel. In v2.2.1, we specify 1.5.x to eliminate these problems.

For the nodejs symlink, I don't think that's a Koel-issue per-se, but yours is an edge-case (maybe you've run into something like http://stackoverflow.com/questions/18130164/nodejs-vs-node-on-ubuntu-12-04?)

@phanan commented on GitHub (Jun 29, 2016): Any reason why it's 2.2.0 and not the latest stable 2.2.1? Before v2.2.1, `plyr` was required as `^1.5.13` and later minor versions from this package had backward incompatibilities that broke Koel. In v2.2.1, we specify `1.5.x` to eliminate these problems. For the `nodejs` symlink, I don't think that's a Koel-issue per-se, but yours is an edge-case (maybe you've run into something like http://stackoverflow.com/questions/18130164/nodejs-vs-node-on-ubuntu-12-04?)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#267

No description provided.

Rows
Columns