Skip to main content

Issues Fixed in Laravel

--------------------------------------------------------------------------------------
1. Missing routes.php File in New Laravel Project
--------------------------------------------------------------------------------------
The lastest version of Laravel doesn't have a routes.php file.

This 'routes.php' file was located in \app\Http in the older versions.

In the newer version, Laravel 5.3, we have a folder named 'routes', where we can find the following files:

api.php
console.php
web.php
For this new version, the routes for your controllers, you can put inside web.php file

See the documentation about routing here

https://laravel.com/docs/5.3/routing#basic-routing

The video lesson you are watching may be outdated.

--------------------------------------------------------------------------------------
2. Could not open input file: artisan
--------------------------------------------------------------------------------------
You need to first create Laravel project and if you already have one you need to go to this project dir using cd command in terminal for example cd myproject.

Now you will be able to run any artisan commands, for example running php artisan will display you list of available commands.

Comments

Popular posts from this blog

vagrant up not working windows 10 | Stderr: VBoxManage.exe: error: Failed to get device handle and/or partition

 vagrant up not working windows 10 If you get an error message during  vagrant up  or when starting a VirtualBox machine, telling you that VT-x is not available, a reason may be that you have enabled Hyper-V on your Windows 10 machine: VirtualBox and Hyper-V cannot share the VT-x CPU: $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'thesteve0/openshift-origin' is up to date... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 8443 (guest) => 8443 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command an

Create a Plugin in the in Windows for Processmaker 3.0

**************************************************************************   To Create a Plugin in the in Windows for Processmaker ************************************************************************** Now let us create the plugin using windows os for the processmaker. The main Steps to Plugins cannot be created on Windows servers, because Windows does not support symbolic links; however, there is an experimental script for Windows servers available at <INSTALL-DIRECTORY>/workflow/engine/gulliver-win.bat which can be tested. http://wiki.processmaker.com/3.0/Plugin_Development The steps given below as a step by step please follow this any query just post commands. Step :1 ============ C:\Bitnami\processmaker-3.1-1\apps\processmaker\htdocs\workflow\engine>gulliver-win.bat new-plugin deleteCases using DSN Connection The plugin deleteCases exists in this file C:\Bitnami\processmaker-3.1-1\apps\pr ocessmaker\htdocs\workflow\engine\plugins\deleteCases\class.deleteCas

HTML to Office Word header and footer generation

Here is an HTML to Office Word header and footer generation code Below: fwrite($oFile, <html xmlns="http://www.w3.org/TR/REC-html40" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> <title> </title> <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Print</w:View> <w:Zoom>100</w:Zoom> </w:WordDocument> </xml><![endif]--> <style> <!-- /* Style Definitions */ p.MsoHeader, li.MsoHeader, div.MsoHeader{ margin:0in; margin-top:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; } p.MsoFooter, li.MsoFooter, div.MsoFooter{ margin:0in 0in 1in 0in; margin-bottom:.0001pt; mso-pagination:widow-orpha