Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FatalErrorException when registering service provider on workbench package #15

Closed
akuzemchak opened this issue Jan 12, 2013 · 2 comments

Comments

@akuzemchak
Copy link

I ran through the workbench utility to create a new package (Foo\Bar), ran composer install, and registered the Foo\Bar\BarServiceProvider in my app.providers config array.

Upon loading the site up in a browser, I get the following error:

FatalErrorException: Error: Class 'Foo\Bar\BarServiceProvider' not found in /Users/aaron/Sites/laravel-4/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php line 123

I've re-read the docs and tried creating a few different packages, but get the same result each time. Also tried tracking down what could be the issue, but no luck. Am I missing a step, or is this a confirmed bug? I'm using MAMP Pro 2.1.1 and PHP 5.4.4.

Thanks for any help or input!

@taylorotwell
Copy link
Member

Did you run composer install from the root of your package? Alternatively use the "--composer" switch on the workbench command.

On Jan 12, 2013, at 11:31 AM, Aaron Kuzemchak notifications@github.com wrote:

I ran through the workbench utility to create a new package (Foo\Bar), ran composer install, and registered the Foo\Bar\BarServiceProvider in my app.providers config array.

Upon loading the site up in a browser, I get the following error:

FatalErrorException: Error: Class 'Foo\Bar\BarServiceProvider' not found in /Users/aaron/Sites/laravel-4/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php line 123
I've re-read the docs and tried creating a few different packages, but get the same result each time. Also tried tracking down what could be the issue, but no luck. Am I missing a step, or is this a confirmed bug? I'm using MAMP Pro 2.1.1 and PHP 5.4.4.

Thanks for any help or input!


Reply to this email directly or view it on GitHub.

@akuzemchak
Copy link
Author

Ah, I didn't catch that it had to be run from the package's root folder! I'll put in a PR on the docs to bold that line momentarily.

Thanks Taylor!

taylorotwell pushed a commit that referenced this issue Feb 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants