Ruffles

@megaman Yes, it is in public/index.php

There's a statement that you need to put at the top of the file for the autoloading part with Composer packages:

require __DIR__ . '/vendor/autoload.php';

If you can't see the error page, that's probably because you have an issue somewhere in the code that is blocking the rendering of the error on the page.

Try running a command like php artisan or php artisan route:list and it will probably show you the error.

Why do you need to return all of records? Why not just paginate the data?

I noticed that the list of the latest lessons seems to be cached and does not show all of the lessons. I've tried removing all of the filters but it did not help. Possible bug?

I believe that the second problem is there because the field you are trying to access is not a MySQL JSON field but a TEXT field.

For the first one, I am not sure if you can even cast it at all unless it is a MySQL JSON field.

Awesome user experience! I love it!

Why are you executing that script? Isn't it easier if you just run the code when the request gets to that route?

No, that would be a one to many relationship between vehicles and vehicle_images.

That's probably because you didn't have internet access in your dev environment (Docker Container / Vagrant VM) when you ran the command or maybe it is your PC / Mac. Try ping github.com and see if you'll be able to connect.

Did you restart the queue worker after you changed the code? It's daemon by default. Not sure if that affects the AppServiceProvider as well but that might be the problem.

You can do something like this:

$offer = Offer::find($offerId);

$errors = collect([
    'offer_expired' => $offer->hasExpired(),
    'offer_not_verified' => $offer->isNotVerified()
]);

$errors = $errors->map(function($isError, $errorType) {
    return $isError ? $errorType : null;
})->filter();

$errors ?  throw new CantApplyException($user, $offer, $errors) : return view('some view');

This is probably one way to clean it up but you should probably put this logic into a middleware or create custom validation rules and use them in a form request class.

That method is for authorization so only true or false is valid as return types, just like Form Requests and the authorize() method.

It is a simple check to see if the fields coming from the request are part of the mass assignable fields array defined in the Eloquent model(s).

Laravel supports it out of the box so all you have to do is tell your Eloquent model which fields to accept when using Model::create($arrayOfFields) by using the protected $fillable array property in your Eloquent model(s).

Check the docs for more info

What does $res return in your try block?

If it does return the data, you should probably do something like:

return json_decode($res->getBody(), true);

This is a web development forum, not an article publishing platform like Medium.

Why are you using collect.js in a PHP file?

Why not just use eloquent for that?

$users = User::orderBy('first_name', 'asc')->get();

It should work as a normal app but make sure to either add a slash before js like /js/app.js or use the asset() helper.

Why use a JQuery plugin when you could use a VueJS plugin for that?

When I am working with APIs, I use JSON Web Tokens (JWT) for authentication. It is easy to implement using a package like tymon/jwt-auth.

You would probably have a unique field (for example name) and based on that field, you could check if it exists, update it, else create a new record.

You could store the data partially in the database and have a completed field which unless it is 100, you won't show that record anywhere.

One way is to use a Fractal Transformer and customize your own response.

Look for it in the home.blade.php view file on line 1417 (wow, never seen a view file with that many lines)

What do you mean by it can't access collections?

you should be able to access your data by response.data in your javascript closure and just use a foreach statement to loop through it to display it on the page.

Another way to fix this problem is to transform the response from the controller.

Go on Upwork and apply for the job you like.

Follow this article

What are the relationships between the tables?

Customize the response the way you want it, example:

return response()->json([
    'data' => [
         'id' => $model->id,
        // .....
    ],
    'meta' => [
        'requiresAuth' => false,
    ]
]);

JSON Web Tokens is one of the possible options. The JWT Auth package is quite easy to use.

No, you shouldn't.

Lumen is mainly used for RESTful APIs since Lumen 5.2, so the views functionality was removed.

CSRF tokens are used in a session based traditional application while the RESTful APIs are stateless and do not use sessions.

Start with Wes Bos' JavaScript 30 tutorials. Also learn JavaScript to a point where you are comfortable to learn the new ES6 / ES2015 features before jumping on the framework train.

(the password is in plain text, not hashed.).

There's the problem. Laravel's login function (whichever you use) is comparing hashed passwords and that's why you can't login.

Hash the password with bcrypt($password) and it will probably work.

Sign up on Upwork, set up your profile, find a project you like and apply for it

When I want to pass an ID to the JQuery script, I usually use HTML5 data attributes on the button and just pick up the value in the script.

Example:

// The Blade file
<button type="button" id="button" data-id="{{ $model->id }}"> Button </button>

// The Script
var id = $('#button').data('id');

Most of the time I just hardcode the URL in the script but when I want to make it dynamic, I also use data attributes for the resource name similar to the example above.

Another idea that came to mind just now is that you could pass the whole URL via a data attribute, something like data-url, using Laravel's route() helper.

What's the error? Check your Chrome Dev Tools Network tab for more details.

The Laravel GitHub Repository

@theUnforgiven Try this:

return redirect('admin/users')
                  ->with('flash', 'Account updated')
                  ->with('flashType', 'success');

@fahaddsheikh I don't think that our profession (web development) is underpaid, it's just that it depends on the company and client you work for, and the complexity of the projects you work on.

If all you do is work on some projects which are simple CMSes / agency or company blogs and websites, you'll probably be paid less, because the responsibility is lower.

If you work on a bigger project, like an ERP / CRM, you would probably be paid higher because the responsibility is higher.

And to answer your question:

I didn't say that you shouldn't look for a better job position / salary, I was trying to say that it won't make much difference if you start comparing your salary with other people's salaries, because it heavily depends on the company they work for, the client they work for, the country they live in and many other things.

You just have to find the right company for you, because everyone has a different idea of what's their ideal job position.

Some people are just interested in the idea of having a job and that they can say that they work for a company and never go up the ladder or advance in their career. On the other hand, some other people care more about the organization, type of projects, how the projects are organized type of thing and can't just work for anyone and anything like me.

Get to a position where you can choose what you want and how you want, and you won't have a problem finding an amazing company.

It does not matter how much you earn, as long as you can cover the living expenses.

I have not yet run into any problems with Lumen and PHP 7.1 so I guess it's supported.

By GoDaddy server you mean shared hosting?

@endian Most of the features Laravel offers are used in bigger-than-just-a-blog projects at some point of the project's development cycle. If you work on an ERP / CRM app for a while, you'll notice that.

The only reason I am using a framework is because I wanna finish the project on time before the deadline hits. I could build everything from scratch but it will take a lot of time and effort. I might get stuck at some point but the client won't be like "Good job man, you are a serious developer. You are not using a framework".

All clients care about is a working project, they don't really care about the technical stuff. It's up to the developers to make their life easier.

I went with a different route, using group_concat and group_by, a little bit different than @jimmck 's example. Now I am getting them as strings which can be easily used in the future.

Thank you all for your contribution in this discussion!

The docs on Laravel Mix Autoloading say that it will add it to every file JQuery is required.

Hello!

I just upgraded Laravel Mix to version 0.9 and I noticed that my template stopped working because JQuery is not being initialized before Bootstrap.

The error I am getting is the following:

Uncaught Error: Bootstrap's JavaScript requires jQuery

So I searched google and saw that the default autoloading for JQuery was removed. I tried to add it back with

mix.autoload({
   jquery: ['$', 'window.jQuery']
});

but that didn't help me, I still have the same problem.

How can I include JQuery to the webpack.config.js file manually?

I have managed to figure out a way to group the output in a way Eloquent does it, using arrays and standard classes like in my example. The only problem I have now is the pagination is not consistent. Different number of results are displayed depending on the roles assigned to the users.

For example: If all users have all 4 roles (will probably never happen, they might have 3 of those 4 roles in some cases.) and I have 30 records per page set, I will get only 9 records back. If I increase the number of records per page to 200, I will have 52 users returned. This is happening because the pagination is ran against the role_user table and with the output grouping (or transformation), I cut down the array of items down.

The desired output would be:

stdClass => 
   'email' => '[email protected]',
    // some other fields go here
   'roles' => [
      stdClass => [
          'name' => 'super_admin'
      ],
       stdClass => [
          'name' => 'client_manager'
      ]
   ]

this is how eloquent outputs the query but for some reason I get the following when I use the fluent query builder with joins:

[
    stdClass => [
       'email' => '[email protected]',
        // some other fields go here
       'role_name' => 'super_admin'
    ],
    stdClass => [
       'email' => '[email protected]',
        // some other fields go here
       'role_name' => 'client_manager'
    ],
]

My table schema is simple:

users table

id
email
password
...

roles table

id
name

role_user table

role_id
user_id

I am using the same schema from the package spatie/laravel-permission

Hello there!

I am working on this project where I use the Fluent Query Builder and I am trying to recreate the same output from the eloquent relationship eager loading, User::with('roles')->get() for example, with join statements.

As a result I had duplicate rows for obvious reasons. I had a list of repeating email addresses with multiple role names for a many to many relationship.

My question is: Do I have to manually structure the objects where I have a nested object(s) for the relationships?