Composer Message Package illuminate/html is abandoned, you should avoid using it. Use laravelcollective/html instead.

This is an article which relates with the article mentioned about using Form class. An error generated when the ‘composer update’ command is executed. The error is specifically mentioned as the title which is ‘Package illuminate/html is abandoned, you should avoid using it. Use laravelcollective/html instead’.

This is happened in order to use Form class in a blade view template file to define a form. To use Form class, normally the illuminate/html package can be utilized to fulfill this purpose. But since the development of Laravel framework has been progressing in this context, the usage of Laravel version 5.3.0 is not applicable for the illuminate/html package. It needs another package to fill that role or position in order for the Form class to be defined. The package called ‘laravelcollective/html’. Below is the output of the command ‘composer update’ execution shown :

Continue reading “Composer Message Package illuminate/html is abandoned, you should avoid using it. Use laravelcollective/html instead.”

Laravel Error Message Call to undefined method Collective\Html\Formfacade::open()

This is an article where an error generated as specified in the title “Call to undefined method Collective\Html\Formfacade::open()”. This error specifically exist whenever the execution of a blade view template file which is called or rendered upon accessing a web-based application using Laravel framework through URL which has been defined in a file named routes/web.php on Laravel 5.3.

To be more detail, it happens when a blade view template defines a Form as follows :

{{Form::open(array('url'=>'test/store)}}
...
{{Form::close}}

It is actually defining a form which is going to process anything exist in a form and submitted in the URL specified as ‘test/store’. But an error suddenly is triggered as shown in the title of this article, ‘Call to undefined method Collective\Html\FormFacade::open()’ as shown in the following image :

Continue reading “Laravel Error Message Call to undefined method Collective\Html\Formfacade::open()”

ReferenceError: $ is not defined using jquery for bootstrap

In this article, an error which is locatedĀ  or it is similar with the one defined in the title ‘ReferenceError: $ is not defined’ using jquery for bootstrap’. It is happened in the context when a Laravel based web page is being executed. Using Bootstrap to arrange the elements exist in the web page to look better using the grid system, it needs JQuery library so that it can be functioned properly.

The JQuery library needed is in a form of Javascript file. But in this context, the function of a JQuery file based on Javascript type is not only for supporting the usage of Bootstrap but also to support the execution of JQuery snippet code itself.

For an example, disabling a tab so that it cannot be accessed, it is actually can be done with the help of JQuery. For an example, if there is a file importing JQuery where in this context, it is in the form of blade view template executed based on Laravel framework, after defining as shown below :

<script src="{{ URL::asset('js/jquery-3.2.1.min.js') }}"></script>

Below is how to do it in a blade view in order to block the tab for being accessed :

Continue reading “ReferenceError: $ is not defined using jquery for bootstrap”

Bootstrap’s javascript requires jquery version 1.9.1 or higher, but lower than version 4

This is an article written to discuss an error shown because of a certain execution of page developed using Laravel framework based on PHP Programming Language. It is actually simple error based on the usage of Bootstrap which is inappropriate because of lacking of something. Below is the image depicting on the situation or the condition relate to the error stated in the title of the article, “Bootstrap’s javascript requires jquery version 1.9.1 or higher, but lower than version 4 :

Bootstrap's javascript requires jquery version 1.9.1 or higher, but lower than version 4
Bootstrap’s javascript requires jquery version 1.9.1 or higher, but lower than version 4

The above error page is not directly represent the actual page of the page where Bootstrap is used but it is actually a plugin installed in Mozilla Firefox called ‘Firebug’ specifically useful for Javascript debugging on Web browser. It is focusing on editing, debugging and monitoring the test and implementation of CSS, HTML and Javascript real-time on a web page. It is integrated with Mozilla Firefox and it can be activated at any time as long as it has already been installed.

Continue reading “Bootstrap’s javascript requires jquery version 1.9.1 or higher, but lower than version 4”

How to use Bootstrap in Laravel Framework

This is an article where the main purpose of it is to explain on how to use Bootstrap grid framework system in Laravel framework. It is based on the following image :

How to use Bootstrap in Laravel Framework
How to use Bootstrap in Laravel Framework

The above image display is actually in not an arranged display or not in a well-formed position. It is because the library used for Bootstrap grid framework system responsible in arranging the position of all elements exist in the page is not properly functioning.

One of the cause which is might be the reason for this to be happened is because the .js and .css file needed to execute so that Bootstrap can properly performs its function is nowhere to be found.

There is a specific way to define how to import all those files needed in blade view template file. Below is how to correctly import those files :

First of all, check the content of the folder named ‘public’ :

Continue reading “How to use Bootstrap in Laravel Framework”

View index not found Laravel Error Message

This is an article where an error generated accessing a part of URL named ‘test’. The full URL is shown below :

http://localhost/public/test

Using an already defined route for using a resource from a controller named ‘TestController’ by the following line added in a file named web.php in folder routes :

Route:resource('test','TestController');

The next part is just create a method named ‘index()’ in the already created controller through the following process and it is executed in the bash prompt:

user@hostname:~$ php artisan make:controller TestController

But to be able to return or to display the right view, it needs to be defined and created first. The one which is needed to be defined is the target of the view which is returned by the controller as shown below :

public function index(){

     return view('index');

}

But in the end, it is still generating an error as shown below :

View [index] not found.

But whenever the snippet code is changed into the following :

Continue reading “View index not found Laravel Error Message”

Laravel error Controller::index() does not exist

Laravel error Controller::index() does not exist

In this article, there will be an information written on how to solve the problem simply arise when an error specified in the title ‘Controller::index() does not exist’. It can be shown on the following image :

Laravel error Controller::index() does not exist
Laravel error Controller::index() does not exist

As shown in the image above, there is specifically error mentioned on the page that in this context, a controller named TestController doesn’t have any index method. Off course the error is generated since the route defined in routes/web.php defined on executing TestController when part of the URL named ‘test’ is accessed. The following is the content of file named web.php located in routes folder :

Route::resource('test','TestController');

The URL accessed in this context is :

http://localhost/public/test/

For further information, below is the log’s content shown similar error :

Continue reading “Laravel error Controller::index() does not exist”