mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #521] Error with fresh install of v3.5.0 #369
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#369
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @grath90 on GitHub (Jan 17, 2017).
Original GitHub issue: https://github.com/koel/koel/issues/521
Trying to set up a fresh install of koel v3.5.0 on Ubuntu forge server. When I run 'php artisan koel:init' I get the following error:
PHP Fatal error: Uncaught ReflectionException: Class sentry does not exist
I've tried updating composer but still get the same results. Sentry is listed in the config/app.php file and in the config.json file so I'm really not sure what to do from here.
Thanks in advance!
@phanan commented on GitHub (Jan 18, 2017):
Can't reproduce this. What happens if you manually
composer require sentry/sentry-laravel?@grath90 commented on GitHub (Jan 18, 2017):
It says it's using version ^0.5.0.
Here is the error and stack trace:
It then repeats that stack trace and after that gives these errors:
@X-Ryl669 commented on GitHub (Jan 18, 2017):
Got this too.
I fixed it by
Then I've edited composer.lock to remove all section concerning pusher (I'd installed it previously, it was a leftover):
Then did a
composer updateThen did a
composer install@grath90 commented on GitHub (Jan 19, 2017):
I just deleted the repository from my server and reinstalled it. No issues the second time.