I have a Laravel project, where I allow people to subscribe to specific campaigns. There is a button "Subscribe", and once pressed, I write the information in the pivot table.
The relation between User and Campaign is belongsToMany both ways.
The question is, how could I disable such button, so client's couldn't subscribe to the same campaign many times? In my thoughts, after the button click, it would get disabled, and would show "Subscribed".
Current button:
<x-button>
Subscribe
</x-button>
EDIT:
So I had an idea, to check if this specific combination of campaign_id and user_id exists within the pivot table, and get a boolean.
Controller
public static function button(Request $request)
{
$campaignUser = User::find($request->user()->id);
$hasCampaign = $campaignUser->campaigns()->where('id', $request->id)->exists();
return $hasCampaign;
}
I do receive a proper response, either 1 or something else.
Now I am trying to call it from the view (still checking if it would work):
#if(App\Http\Controllers\SubscribeController::button() == 1)
echo "Yes";
#else
echo "No";
#endif
The current issue, is that of course, I need to somehow pass the Request $request into the function, though, not sure if it is even possible.
If it would work like that, I would try to adjust my button code by example:
<input type="hidden" name="status" value="{{ $post->status == 1 ? 0 : 1 }}"/>
#if($post->status == 1)
<input type="submit" value="Subscribed"/>
#else
<input type="submit" value="Subscribe"/>
#endif
So the current question, is if I am even doing it correctly, and if so, how to pass the Request into the function?
There are many many questions here on SO about how to properly persist checkbox fields in Laravel after form submission (
example,
example,
example
), this question is not about that.
Please note I am also well aware of Laravel's old() method, and that it accepts a default value. My question is about a particular case where old() does not seem to work for a checkbox.
I'm working on an edit form, updating data already in the DB. The form will initially be populated with the values from the DB.
The standard approach to re-populating form inputs after failed validation is to use old(). For most input types, something like the following works:
<input type='text' name='unicorns' value='{{ old('unicorns', $model->unicorns) }}'>
On initial page load (before the form is submitted) this works fine. As nothing has been submitted yet, old('unicorns') is null, so the default of $model->unicorns will be used, and the text field's value reflects the current DB state.
After submitting a new value, which fails validation, old('unicorns') will be the new value, even if the new value was an empty string, and again the text field's value reflects the submitted state, as we want.
However this breaks down for checkboxes, when the unchecked checkbox does not appear in the request at all. Consider:
<input type='checkbox' name='unicorns' value='1' #if old('unicorns', $model->unicorns) checked #endif>
On initial page load this works fine, just like for text fields. But after failed validation, for the 2 cases where the checkbox is changed from its initial state:
Case 1: DB state 0 (unchecked), submitted state checked. old('unicorns') will be 1, so the test evaluates true, the checkbox is checked - OK!
Case 2: DB state 1 (checked), submitted state unchecked. Since old('unicorns') is null, old() falls back to the default value $model->unicorns (1), so the test evaluates true, and the checkbox is checked - but we just unchecked it! FAIL!
(There is no problem in the other 2 cases, where the checkbox is not changed from the state in the DB).
How to solve this?
I initially thought the best way around this would be to test if there has been a validation error - if so, use the old() value, with no default fallback; if not, use old() with default fallback. One way to test for failed validation is to check $errors. This seems to work, but it only works within a view AFAICT, as (from the Laravel docs):
Note: The $errors variable is bound to the view ...
I'd like to create a global helper for this, and $errors won't work there. Anyway, this approach feels ... clunky and too complicated.
Am I missing something? Is there a neat Laravel way of solving this? It seems odd that old() simply does not work for this particular case.
This is not a new problem, how do others handle this?
This is the solution I referred to in my question. It works well, and 6 months later, it does not seem as clunky as when I posted the question. I'd be happy to hear how others are doing this though.
I have an Html helper, created as described in this question, and aliased in config/app.php as described in the first part of this answer to that question. I added a static method to it:
namespace App\Helpers;
use Illuminate\Support\ViewErrorBag;
class Html {
/**
* Shortcut for populating checkbox state on forms.
*
* If there are failed validation errors, we should use the old() state
* of the checkbox, ignoring the current DB state of the field; otherwise
* just use the DB value.
*
* #param string $name The input field name
* #param string $value The current DB value
* #return string 'checked' or null;
*/
public static function checked($name, $value) {
$errors = session('errors');
if (isset($errors) && $errors instanceof ViewErrorBag && $errors->any()) {
return old($name) ? 'checked' : '';
}
return ($value) ? 'checked' : '';
}
}
Now in my views I can use it like so:
<input type='checkbox' name='unicorns' value='1' {{ \Html::checked('unicorns', $model->unicorns) }}>
This correctly handles all combinations of DB and submitted state, on initial load and after failed validation.
I came across the same problem and found this old post. Thought to share my solution:
<input type="checkbox" name="unicorns" class="form-check-input" id="verified" {{ !old()?$model->unicorns:old('unicorns')?' checked':'' }}>
{{ !old()?$model->unicorns:old('unicorns')?' checked':'' }}
Nested ternaries: The first ternary provides the condition for the second:
When there is no old() array, there is no post, thus the DB value $model->unicorns will be used as the condition like so:
{{ $model->unicorns?' checked':'' }} will correctly evaluate on a value of either 0 or 1
If however old() array is present, we can use the existence of the old('unicorns') variable as the condition like so:
{{ old('unicorns')?' checked':'' }} will correctly evaluate on a value of on or no value.
It's a bit of type juggle and you have the nested ternary, but it works well.
I had a similar situation and my solution was to add a hidden field just before the checkbox field. So, in your case it would be something like:
<input type='hidden' name='unicorns' value='0'>
<input type='checkbox' name='unicorns' value='1' {!! old('unicorns', $model->unicorns) ? ' checked' : '' !!}>
That way, when the checkbox is not ticked, a value of 0 for that field will still be present in the post request. When it is ticked then the value of the checkbox will overwrite the value in the hidden field, so the order is important. You shouldn't need to use your custom class with this approach.
Does that work for you?
From Don't Panic 's answer, you could do it like this in blade:
<input type="checkbox" class="form-check-input" value='true'
#if ($errors->any())
{{ old('is_private') ? 'checked' : '' }}
#else
{{ isset($post) && $post->is_private ? 'checked' : '' }}
#endif
>
Hope it helps.
I do this
<input id="main" class="form-check-inline"
type="checkbox" name="position" {{old('position',$position->status)?'checked':''}}>
I actually do a simple ternary operator when persisting checkbox states:
<input name='remember' type='checkbox' value='1' {{ old('remember') ? 'checked' : '' }}>
Edit:
<input name='remember' type='checkbox' value='yes' {{ old('remember') == 'yes' ? 'checked' : '' }}>
I have a checkbox in my form which looks like this:
<input class="form-control" type="checkbox" id="showCTA" name="showCTA" <?php echo $block['showCTA'] ? 'checked' : ''; ?> />
Everything works fine with this mark up....unless the PHP value equals 1(already checked). If this is the case, I can check and uncheck the box in the from end visually, but the actual html attribute does not change resulting in the same value of 1 being saved to my database on submit.
How can I work around this in a clean manner? I assume the issue is since the PHP value is absolute until submitted, it means the condition around my "checked" attribute is also absolute, therefore I cannot change the attribute.
If the checkbox is not checked and you post the form, the $_POST['showCTA'] will be undefined. So you should use the isset($_POST['showCTA']) method which will return true if the checkbox is checked and if not, false.
I have searched a lot but didn't find any solution. I have some select box in my HTML form for which I need to keep the old values after redirecting back post input validations.
Here is my redirect code in controller
redirect()->back()->withInput()->withErrors($validator->messages());
I have tried using value={{old('somefieldname')}} But it only works for inputs and textareas.
PS : I also need to set old values in multiple="multiple" select.
Any help will be really appreciated.
If you are iterating in a loop then directly old will not work for select option
For example if you have something like that in your blade file
then you can try this for selecting the current option after redirect
<select id="someId" name="someName">
#foreach($someData as $data)
<option value="{{ $data->id }}" #if(old('someName') == $data->id) selected #endif> {{ $data->name }} </option>
#endforeach
</select>
Then it will select your current option.
If this is your problem then it might help.
In select you have to place selected=selected when option=value is equal to old. Also please consider using laravelcollective/html package. You can use it in this way:
{!! Form::select('type', ['' => 'Types'] + $options) !!}
And package automatically will take care about old values after redirecting back with after validation fails.
Recently I started learning Laravel by following the Laravel From Scratch cast(https://laracasts.com/series/laravel-5-from-scratch).
Right now I'm trying to add additional functionality to the registration form(starting with error feedback) and I already ran into a problem.
Is there a (native) way to check wether the form has been submitted or not?
I tried to use:
{{ Request::method() }}
But even after pressing Register on the default scaffold generated by running the command php artisan make:auth it returns GET while the action of the form is POST and it triggers a route with a POST Request type.
The reason for all of this is that I want to add a CSS class to a element based on the following requirements.
if form is submitted
if $errors->has('name') //is there an error for name(example)
add 'has-error' class
else
add 'has-success' class
endif
endif
Does anybody know a solution for it?
I think you want to achieve this:
if( old('name') ){ // name has been submitted
if( $errors->first('name') ){ // there is at least an error on it
// add error class
}else{ // has been submitted without errors
// add valid class
}
}
That in a input field is something like this:
<input name="name" class="validate{{ old('name') ? ( $errors->first('name') ? ' invalid' : ' valid') : '' }}" type="text" value="{{ old('name') }}">
Rick,
You can validate you should have a look at the validate function in Laravel. You can validate the input you sent in and when there are errors send them back into your view.
For examples look at the url: https://laravel.com/docs/5.1/validation
Hope this helps.