So, I have three tables: farms, crops and harvests. When I want to register a harvest on my web page, I use pluck to display a dropdown list for farms and another dropdown list for crops in the same view. The thing is, when I select a farm from the dropdown, I can still see and select crops related to other farms, and das not good. How can I list only crops related to the previously selected farm? My HarvestController looks like this:
public function create()
{
$farms = Farm::where('users_id', Auth::id())->with('alias')->pluck('alias', 'id');
$crops = Crop::where('users_id', Auth::id())->pluck('id', 'id');
return view('harvest.create')
->with('farms', $farms)
->with('crops', $crops);
}
The relationships in models:
class Farm extends Model
{
public function crops(){
return $this->hasMany('App\Crop');
}
}
class Crop extends Model
{
public function farm(){
return $this->belongsTo('App\Farm');
}
public function harvest(){
return $this->hasOne('App\Harvest');
}
}
And the view looks like this:
<div class="form-group">
{!! Form::label('farms_id', 'Farm') !!}
{!! Form::select('farms_id', $farms, null, ['class' => 'form-control', 'required']) !!}
</div>
<div class="form-group">
{!! Form::label('crops_id', 'Crop ID') !!}
{!! Form::select('crops_id', $crops, null, ['class' => 'form-control', 'required']) !!}
</div>
Any help will be highly appreciated, constructive roasting too
Related
In my Laravel model controller I have this:
public function guestInfo($id)
{
$guests = Person::where('id', $id)
->with('languages')
->get();
return view('layouts.visitor', ['guests' => $guests]);
}
in my blade file I have this:
#foreach ($guests as $guest)
some html stuff in here
{!! Form::select('name', $guest->languages->pluck('name')->all(), ['class' => 'form-control']) !!}
more html
#endforeach
Person is a model to a db table "persons" and "languages" is a relative model "belongs to" Person.
In my languages table I have different rows for languages: "english, spanish, etc" each is in it's own row with it's own id.
My goal is to get all the languages to show up. However currently with the above code I only get one language to show up.
Any ideas?
your code will retrieve only that languages which associated with persons. if you want to show all languages, just retrieve them as id => name pairs and pass to your view.
$guests = Person::where('id', $id)->get();
$languagess = Language::pluck('name', 'id);
and then do foreach with $languages
#foreach ($languages as $key => $val)
{!! Form::select('name', $key, ['class' => 'form-control']) !!}
#endforeach
I ended up doing it like this with some help from #devnull Ψ. Not exactly as he suggested but it gave me some direction.
Controller:
public function guestInfo($id)
{
$guests = Person::where('id', $id)
->with('languages')
->get();
$languages = Language::pluck('name')->toArray();
return view('layouts.visitor', ['guests' => $guests, 'languages' => $languages]);
}
Then in my blade:
{!! Form::select('name', $languages, 'name', ['placeholder' => '<select>','class'=>'form-control']) !!}
I am working on a laravel 5.2 project. I am referencing category_id from Posts.
My Post model looks like
class Post extends Model
{
protected $fillable=['category_id '];
public function category(){
return $this->belongsTo('App\category');
}
}
Also, my form looks like
<div class="form-group">
{!! Form::label('category_id','Category:') !!}
{!! Form::select('category_id', $categories, '1',['class'=>'form-control']) !!}
</div>
My table data
#foreach($posts as $post)
<tr>
<td>{{$post->category['name']}}</td>
</tr>
#endforeach
The Problem is, whenever I create a new post, the category name doesn't save in the database nor does it show on the front end.
My Post Schema table
public function up()
{
Schema::create('posts', function (Blueprint $table) {
$table->increments('id');
$table->integer('category_id')->index()->unsigned()->nullable();
});
Even when I dd() the input field for the category id on the post table, its empty. Can someone help me with this, it's making me go crazy. Thanks
I am using a resource contoller,heres my create request controller
public function store(Request $request)
{
$user=Auth::user();
$input = $request->all();
Post::create($input);
return redirect('admin/posts');
}
It is because the fillable field only is the category_id try to add the category name field on your fillable like this.
//this are the fields that is fillable
protected $fillable=['category_id','name'];
With this the category name field will be able to catch and save data.
In continuation of my comment. Your migration should look like this.
public function up()
{
Schema::create('posts', function (Blueprint $table) {
$table->increments('id');
$table->integer('category_id')->index()->unsigned()->nullable();
$table->string('category_name')->nullable();
});
Your model,
class Post extends Model
{
protected $fillable=['category_id','category_name'];
}
Form
<div class="form-group">
{!! Form::label('category_id','Category:') !!}
{!! Form::select('category_id', $categories, '1',['class'=>'form-control']) !!}
{!! Form::input('category_name',old('category_name'),['class'=>'form-control', 'id' => "input_name"]) !!}
</div>
and lastly your table data should look like this.
#foreach($posts as $post)
<tr>
<td>{{$post->category_name}</td>
</tr>
#endforeach
Double check your fillable and input fields if they are the same.
your given concern you only show this one.
<div class="form-group">
{!! Form::label('category_id','Category:') !!}
{!! Form::select('category_id', $categories, '1',['class'=>'form-control']) !!}
</div>
how about the other fields. We expect you already had this on your form too.
<div class="form-group">
{!! Form::label('input_name','Name:') !!}
{!! Form::input('name',old('name'),['class'=>'form-control', 'id' => "input_name"]) !!}
</div>
In your store method it should look like this
$new_post = new Post;
$new_post->category_id = Input::get(‘category_id’);
$new_post->name = Input::get(‘name’);
$new_post->save();
Just in case you’re not using the fill method of $request
In order to access your relationship's attributes, you should do:
$post->comment->name;
And try to use 'fill()' when saving
$post = new Post;
$post->fill($request->all());
$post->save();
I fixed the error using this in my form.
{!! Form::select('category_id', [''=>'choose Categories'] + $categories,['class'=>'form-control']) !!}
and this on my table.
<td>{{$post->category['name']}}</td>
Thanks all for your effort.
I'm trying to save to database my data, but I get error "Array to string conversion". It's my controller
public function create()
{
$listapacjentow = Patient::pluck('nazwisko','id');
return view('leczenie.create')->with('listapacjentow', $listapacjentow);
}
public function store(CreateOperacjaRequest $request)
{
$operacja = new Operacja($request->all());
$PacjenciIds = $request->input('PacjentList');
$operacja->user()->associate($PacjenciIds);
$operacja->save();
return redirect('leczenie');
}
It's my form
<div class="form-group">
<div class="col-md-4 control-label">
{!! Form::label('PacjentList','Wybierz pacjenta:') !!}
</div>
<div class="col-md-6">
{!! Form::select('PacjentList[]', $listapacjentow); !!}
</div>
When I return $operacja is everything ok, but I can't save it to database
Try with this approch in your store method.
$operacja = new Operacja($request->all());
$operacja->user_id = $request->input('PacjentList.0');
$operacja->save();
$operacja->user()->saveMany($patients);
If you want to associate only one user with Operacja, do this:
{!! Form::select('user_id', $listapacjentow); !!}
$operacja = Operacja::create($request->all());
If you want to add many users to the Operacja, you'll need to revert one to many relationship, so User will have operacja_id and Operacja will not have user_id.
If you want to make Operacja have many users and a user could have many Operacja, use many to many relationship.
I have made the following migration in Laravel:
<?php
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
class QualityCheckTable extends Migration
{
/**
* Run the migrations.
*
* #return void
*/
public function up()
{
Schema::create('quality_check', function (Blueprint $table) {
$table->increments('id');
$table->boolean('favicon');
$table->boolean('title');
$table->boolean('image-optimization');
});
}
/**
* Reverse the migrations.
*
* #return void
*/
public function down()
{
Schema::drop('quality_check');
}
}
I have the following controller method that runs when the form in the frontEnd is submitted:
public function store(CreateArticleRequest $request) {
// $input = Request::all();
Article::create($request->all());
return redirect('articles');
}
My form looks like , so:
{!! Form::open([ 'action' => 'QualityCheckController#validateSave' , 'class'=>'quality-check-form' , 'method' => 'POST' ]) !!}
<div class="input-wrpr">
{!! Form::label('favicon', 'Favicon') !!}
{!! Form::checkbox('favicon', 'value' ); !!}
</div>
<div class="input-wrpr">
{!! Form::label('title', 'Page Title') !!}
{!! Form::checkbox('title', 'value'); !!}
</div>
<div class="input-wrpr">
{!! Form::label('image-optimization', 'Image Optimization') !!}
{!! Form::checkbox('image-optimization', 'value'); !!}
</div>
{!! Form::submit('Click Me!') !!}
{!! Form::close() !!}
So when the method runs the values of the checkboxes are saved to the database.
As of now , all entries are showing as 0 , Like so:
Now how to make it such that when the checkbox is checked , 1 is saved and when the checkbox is left unchecked the value in is left at 0 ??
When a checkbox is ticked, it's value is present in the posted data. When it is unticked, it's value is not present. This means when you do $request->all() it will contain only the checkboxes that were ticked. So in your case, if you leave all 3 checkboxes unticked, your $request->all() could yield an empty array (Assuming that no other fields are posted).
When you run Article::create($request->all()); with no checkboxes ticked you would be essentially passing it an empty set of data, which means that your database is going to be populated with the default values for the fields that you didn't provide.
Since you didn't provide a default in your migration, MySQL is going to guess what the default should be based on the field type, which in the case of a boolean will be 0. You may see some warnings/errors though.
There are loads of ways you can get this to work so that a 1 is saved when a checkbox is ticked or 0 when it is not ticked. The easiest way in your scenario would be to set the value of each checkbox to be 1 and explicitly set up default values in your migration i.e.
Migration:
$table->boolean('favicon')->default(0);
Form:
{!! Form::checkbox('title', '1'); !!}
This way, when the title checkbox is ticked, your $request->all() returns an array containing an item 'title' => '1' and this is saved in your database. All of the unticked boxes are defaulted to 0 as per your migration.
I prefer however to be more explicit when I write my method for handling the store.
$article = new Article();
$article->title = $request->has('title'); // Will set $article->title to true/false based on whether title exists in your input
// ...
$article->save();
Have you remembered to pass them in the $fillable array in the Article Model?
protected $fillable = [
'favicon',
'title',
'image-optimization'
];
and as a sidenote to the checkboxes thing. You can just make a hidden input with the same name, and make it false. That way, if the checkbox is unchecked, it will be false, but if it is checked, it will return true, as it is the last value:
<div class="input-wrpr">
{!! Form::label('title', 'Page Title') !!}
{!! Form::hidden('title', false); !!}
{!! Form::checkbox('title', 'value'); !!}
</div>
With VUE you can do it like this:
Add this line to your table
$table->boolean("image-optimization")->default(0);
Add this to your model, it will modify the value inserted in the database
protected $casts = ['image-optimization' => 'boolean'];
You don't have to modify the request with this method
Docs: https://laravel.com/docs/8.x/eloquent-mutators
You can check if checkbox is set with isset($request->favicon) or empty($request->favicon) or ->has('favicon'):
public function store(CreateArticleRequest $request) {
foreach (['favicon', 'title', 'image-optimization'] as $box) {
$request($box) = $request->has($box);
}
Article::create($request->all());
return redirect('articles');
}
How i do the query to works like this example:$model->model2->attribute
<div class="form-group">
{!! Form::label('Route name') !!}
{!! Form::text('name', ( isset($climb->route->name) ? $climb->route->name : null ), array('class'=>'form-control' )) !!}
</div>
You could try using your model in the view as in a dictionary, add something like this in your controller.
$model = Model::find($id);
$model['model2'] = $model->model2;
return view('your_view', ['model' => $model]);
For this I assume you already prepared your relationship in your model, doing that for your real models should make the view work this way
<div class="form-group">
{!! Form::label('Route name') !!}
{!! Form::text('name', ( isset($climb['route']['name']) ? $climb['route']['name'] : null ), array('class'=>'form-control' )) !!}
</div>
Create a relation:
Having:
class Comment extends Model
{
/**
* Get the post that owns the comment.
*/
public function post()
{
return $this->belongsTo('App\Post');
Then thou shall call lika:
$comment = App\Comment::find(1);
echo $comment->post->title;
https://laravel.com/docs/5.2/eloquent-relationships#one-to-many
It's one many, not one one I think