-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Fatal error Installing using composer #2114
Comments
I think that is related with #1871 . Try running 'composer update' and check if fix it |
Running 'composer update' did not fix it. |
This is because of codeigniter4/devstarter#1, and it makes the devstarter unusable. The quick fix is to open app/Config/Paths.php and change this line:
to this:
("framework" to "codeigniter4") @jim-parry and I wrote about it a bit, but there's going to need to be a change to the release scripts in admin/ in order to fix this. |
devstarter is not created by the release scripts. I have updated its app/Config/Paths.php, which should fix the problem for new installs this way. Existing ones might need to manually update the path, as described aboce. |
Not hearing anything contrary in 6 days, I presume the fix works. |
Thanks Guyz |
I use linux, so this worked for me: |
I have getting the fatal error. after updating composer also getting same error. PHP Warning: require(/opt/lampp/htdocs/ci4/app/Config/../../vendor/codeigniter4/codeigniter4/system/bootstrap.php): Failed to open stream: No such file or directory in /opt/lampp/htdocs/ci4/spark on line 46 |
I got a fatal error in the browser after installing CodeIgniter using composer with the following command:
composer create-project codeigniter4/devstarter my_project_name -s dev
The error was:
Fatal error: require(): Failed opening required 'I:\\my_project_name\\app\\Config/../../vendor/codeigniter4/framework/system/bootstrap.php'
I checked the vendor folder and the "framework" folder /vendor/codeigniter4/ is missing. I only saw /vendor/codeigniter4/codeigniter4/.
I renamed the /vendor/codeigniter4/codeigniter4 to /vendor/codeigniter4/framework and there were no more errors.
The text was updated successfully, but these errors were encountered: