Skip to main content

error while running Laravel crud app

 1. Fatal error: require(): Failed opening required 'C:\wamp64\www\laravel\Laravel-Vue-First-CRUD-master/vendor/autoload.php' (include_path='.;C:/laragon/etc/php/pear') in C:\wamp64\www\laravel\Laravel-Vue-First-CRUD-master\artisan on line 18

run these two commmands

composer update --no-scripts 
composer update
Use the `composer fund` command to find out more!

With this command, you will re-create the vendor folder in your project and after that your project will start working normally.

2. db migrate error

i was accessing it without creating db. after that i migrated and it worked 


Routing issue: clean installation of Laravel apps

It's nowhere mention either in docs or twitter posts.

Symfony\Component\Routing\Exception\RouteNotFoundException

Route [users.store] not defined. (View: C:\wamp64\www\laravel\crud\resources\views\create.blade.php)

http://localhost/laravel/crud/public/insert

C:\wamp64\www\laravel\crud\vendor\laravel\framework\src\Illuminate\Routing\UrlGenerator.php:431


PS C:\wamp64\www\laravel\account> php artisan serve

Starting Laravel development server: http://127.0.0.1:8000

[Wed Sep 16 13:43:30 2020] PHP 7.4.10 Development Server (http://127.0.0.1:8000) started

[Wed Sep 16 13:43:34 2020] 127.0.0.1:60822 Accepted

[Wed Sep 16 13:43:34 2020] 127.0.0.1:60823 Accepted

[Wed Sep 16 13:43:34 2020] 127.0.0.1:60823 Closing

[Wed Sep 16 13:43:35 2020] 127.0.0.1:60822 [200]: GET /favicon.ico

[Wed Sep 16 13:43:35 2020] 127.0.0.1:60822 Closing

[Wed Sep 16 13:43:38 2020] 127.0.0.1:60827 Accepted

[Wed Sep 16 13:43:38 2020] 127.0.0.1:60828 Accepted

[Wed Sep 16 13:43:38 2020] 127.0.0.1:60827 Closing

[Wed Sep 16 13:43:38 2020] 127.0.0.1:60828 [200]: GET /favicon.ico

[Wed Sep 16 13:43:38 2020] 127.0.0.1:60828 Closing



Comments

Post a Comment

Popular posts from this blog

HOW-TO:- Solve Moodle 2.7 on MySql 5.7.x Installation

The reason of doing this is I configured my apache for local virtual hosting rather than localhost (available in the next post). I found the error as mentioned below, and I tried different solution to solve it. I did few of the things to solve, they are as follows: Removed and installed MySQL server. Installed mysql 5.7v Installed Moodle 2.7+ stable version  configured and deleted Moodle config.php few times. created and deleted database naming moodle(default created when initialized) and few other names. Gave permission to php5.6 instead of php7.0.2 in Ubuntu 16.04 Here's the Solution, find below lines(183 - 191) or search for " SELECT @@storage_engine " and then replace it from "SELECT @@default_storage_engine" . =======Code Snippets(183 - 191):  =======         // get the default database engine         $sql = " SELECT @@default_storage_engine";         $...
Post a Comment
Read more

Software Versions You Must Have..!

Google Chrome       Version 29 and Version 37 of Google Chrome works much better than any other version.I updated my Google Chrome but it was lagging,not responding, crashed,contents were loaded very slow and few more.So,finally I found Google Chrome 37 working better,bugs fixed and you can download this to fix the previous problems. 2. KM Player Really awesome player to watch HD Videos,movies.Compatible with all extensions of videos you want to watch whether it is mkv,3gp,flv,HD,4K etc.KM Player has very good 3D mode.You can watch multiple videos at a time.I found version 3.6 & 3.9 useful,but in between versions were very Ads providing, lagging every time when you open the Player. 3. iTunes & Quick Time Player  Hats off to the creator 'Apple Inc.'. iTunes- name is enough.I use default audio player as iTunes.You can feel the sound clarity when you are changing it to other mode like Pop,Rock,Acoustic,Bass etc. iT...
Post a Comment
Read more

#EspoCRM #Business #Open_Source

Since last few weeks I'm working on EspoCRM - open source business software. I'll edit the post with explanation. just a quick backup. Ref. here:  ORM, How to manage entities and perform queries - EspoCRM Documentation Here are some steps to get started: Here's how you can incorporate your custom search.js script for the Lead entity in a "upgrade safe" way while your pull request is approved: Define your own search.js class in the custom namespace. for example: client/custom/src/views/record/search.js Code: define('custom:views/record/search', 'views/record/search', function (Dep) { return Dep.extend({ WRITE HERE ALL YOUR CUSTOM SEARCH CODE }); }); Define a custom header list view class that will invoke the custom search instead of the core class, for example: client/custom/src/views/header/list.js Code: define('custom:views/header/list', 'views/list', function (Dep) { return Dep.extend({ searchView: 'cu...
Post a Comment
Read more