laravel-5.2

I'm learning Laravel, and I'm using Laravel 5.2. I want to know about Eager Loading, Constraining Eager Loads, and Lazy Eager Loading. What are the similarities and differences between those three? Can you give an example for each of them? I have read Laravel documentation, but I still don't understand. I hope you can give clearer explanation. Thanks. Nutshell: Eager Loading allows you to get the relationships for some Models efficiently. Constraining Eager Loads Again makes it efficient but you can limit your results e.g. date range, specific id etc Lazy Eager Loading Is for when you already

I just started an laravel 5.2 application. Every route I take (/register, /logout, login,...) redirects me to the homepage. Here are my routes <?php Route::group(['middleware' => ['web']], function () { //Register Route::get('/register', 'Auth\AuthController@getRegister'); Route::get('/register/success', 'Auth\AuthController@getRegisterSuccess'); Route::post('/register', 'Auth\AuthController@PostRegister'); //Login Route::get('/login', 'Auth\AuthController@getLogin'); Route::post('/login', 'Auth\AuthController@PostLogin'); //Password Reset Route::get('/password/reset/email', 'Auth

So I have used this format again. In my routes.php I have Route::controller('datatables', 'HomeController', [ 'PaymentsData' => 'payments.data', 'getIndex' => 'datatables', ]); In my HomeController.php I have public function getIndex() { return view('payments.index'); } /** * Process datatables ajax request. * * @return \Illuminate\Http\JsonResponse */ public function Payments() { return Datatables::of(DB::table('customer'))->make(true); } Anytime I try php artisan I get [BadMethodCallException] Method controller does not exist. Question, is this form of doing it Deprecation or why anyone spot

My registration form is working and it store users to db but when user login then Auth::attempt() return false. Here is my code for login. I store the password in db in sha1 encription. Route::post('login',function(){ $creds=array( 'email' => Input::get('email'), 'password' => sha1(Input::get('password')) ); $auth = Auth::attempt($creds); dd($auth); Even though you can implement a Service provider as describe in this post , You can do it manually by with using other auth method This means you can do like so: //.... try{ $user = User::where('email', Input::get('email')) ->where('password', sha1

When I protect routes in Laravel 5 it works well when I'm not logged in because it redirects the protected routes to the login page but once I login and try to access the protected routes it redirects me to the root route. For example if I try to access /people or /people/1 it will redirect me to / Here's my routes.php file: Route::get('/', function () { return view('welcome'); }); Route::group(['middleware' => ['auth']], function () { Route::resource('people', 'PeopleController'); Route::resource('people.checkins', 'CheckinsController'); Route::model('checkins', 'Checkin'); Route::model(

The simplified scenario is the following: I have a few pages in the database (ideally not more than 10-20, but there is no hard limit). They all have some content and a "slug" (there are slugs that contain a forward slash, if that matters). I'm trying to register route(s) to these slugs to a PageController that displays the content of the given page. Here are my ideas about the approach: Register a single "catch 'em all" route (which should be the very last registered route). This is definitely bad. Query all links from the database and register individual routes to them. This is easy, but I

I have a shared hosting service hostinger. as I can upload my laravel 5.2 and configure project? and I tried using: namespace App\Providers; use Illuminate\Support\ServiceProvider; class AppServiceProvider extends ServiceProvider { /** * Bootstrap any application services. * * @return void */ public function boot() { // } /** * Register any application services. * * @return void */ public function register() { $this->app->bind('path.public', function () { return base_path() . '/public_html'; }); } } but still nothing. I guess easiest and better approach in this situation will be creating of a

I have a Laravel 5.2 app which sends a few emails when a user buys a product. The email view includes references to some images, like so: <img src="{{ asset($purchase->image) }}"> This works fine in all 3 environments I have - local, staging, and production. asset() correctly constructs the fully qualified URLs to the appropriate image, using the configured APP_URLs in each environment. I decided to switch to using Laravel queues to send the emails. I changed the QUEUE_DRIVER in .env to database php artisan queue:table php artisan migrate php artisan queue:listen Changed \Illuminate\Support