This is a major update and contain breaking changes

• drops PHP 7.x support and adopt the new PHP 8.0 syntax

• changed method signature of getFormGroup() to not get the

ErrorException: Required parameter $wrapperElement follows optional parameter $label

error [see this link for reference]. You need to update calls to getFormGroup() method from this example:

BootForm::getFormGroup('name','label','<div><button type="submit" class="btn btn-default">Submit</button></div>')

to this

BootForm::getFormGroup('<div><button type="submit" class="btn btn-default">Submit</button></div>','name','label')

For now all labels are escaped. This allow us to include HTML code inside it without escaping:

// A label with HTML code using array notation
BootForm::text('username', ['html' => 'Username <span class="required">*</span>']);

// A label with HTML code using HtmlString object
BootForm::text('username', new Illuminate\Support\HtmlString('Username <span class="required">*</span>'));

This fix #72 both using HtmlString object and array.

With PHP 8 it shows following error:

 Required parameter $wrapperElement follows optional parameter $name

  at vendor/watson/bootstrap-form/src/BootstrapForm.php:830
    826▕      * @param  string  $label
    827▕      * @param  string  $element
    828▕      * @return string
    829▕      */
  ➜ 830▕     public function getFormGroup($name = null, $label = null, $wrapperElement)
    831▕     {
    832▕         if (is_null($label)) {
    833▕             return $this->getFormGroupWithoutLabel($name, $wrapperElement);
    834▕         }

In Laravel 5.4,

If you create a input field like this: {!! BootForm::text('address') !!}

And in your controller, validate:

        $rules = [
            'address'=>'required',
        ];
        $validator = Validator::make($request->input(), $rules);

        if ( $validator->fails() ) {
            return redirect()->route('post-company-create')
                ->with(['errors'=>$validator->errors()]);
        }

You'll receive this error if you submit a blank 'address': Undefined property: Illuminate\Support\MessageBag::$default

This reverts the change to the getFormGroup signature introduced with the PHP 8.0 changes.

I've decided to change this because after further review I think it looks awkward from an API perspective. The field name and label should come first when getting a form group - a wrapper should be the last consideration.

Clearly the test coverage is lacking here, so I'll try and follow that up next.

hi BootForm::radio('node[check]', 'Check', 0) render <label for="node[check]"><inpu name="node[check]" id="node[check]" type="radio" value="Check">Check</label> maybe change $value = $value ?: $label; to$value = is_null($value) ? $label : $value; in public function radioElement($name, $label = null, $value = null, $checked = null, $inline = false, array $options = []) it will happen when use BootForm::radios() with values ['0'=>'No', '1'=>'Yes'] Thanks you.

This allows to use nested resources by adding support of routes/action in array form as mentioned in issue https://github.com/dwightwatson/bootstrap-form/issues/43

Example:

BootForm::open([
    'model' => $application,
    'store' => array('ApplicationController@store', $project),
    'update' => array('ApplicationController@update', $project)
])

in "Bootstrapform.php" in the open function is a check on $options['model'], if this exists then the (protected) model function wil be used.

In the model function is another check on model but this will have no effect because it would'nt go in there in the first place if no model is passed. If it doesn't go in there it wont take the $options['store'] and will give the url of the current page as a default. This will result in POSTing to the /create page wich will throw the MethodNotAllowedHttpException error.

So either the check if model is set schould be in the open method firing either $this->form->open() or the model function, OR the model function should be public, this way it would make sense that the check is done twice.

Hey man this is awesome! However I can not seem to render a standard form....

Doing this in my blade template:

{{ BootstrapForm::openStandard()}} {{BootstrapForm::text('username')}} {{ BootstrapForm::submit('Login') }} {{ Form::close() }}

Produces the fields like: `

`

The expected result would have been `

I don't know if this is the expected behavior or what, but seems odd to me:

Let me know if anyone can reproduce this.

• When updating an already registered record

• The Model has a field with required validation

• Submit the form with this field empty

• Validate at controller and redirect back with old inputs

• The field now should be empty, with error messages. It have the error messages, but its filled with the registered value from database.

// myController

$model->save($request->all());
if ($model->isInvalid()) {
      return redirect()->back()->withInput()->withErrors();
}

// myView

{!! BootForm::open(['model' => $model, 'update' => 'admin.models.update']); !!}
{!! BootForm::text('field', 'myField') !!}

To add some information, the old value is filled normally after validation IF it's not empty, like when we are validating string length.

If the following is entered in:

echo BootForm::text('meta_description', null);

It outputs the label as: "Meta_Description"

Rather than "Meta Description"

Please feel free to assign this issue to me and I will solve it.

As on version 2.3.

If I set à label to "false" to avoid having a label, I always get label. Think forcing label to string result to à $label value to "" (empty) to $lable, in facto, $this->getLabelTitle($label, $name) never return null !

With this pull request the package is now compatible with the latest versions of PHP 8.*. The HTML labels were not rendered due to non-compatible type declarations in label-related methods. Enjoy!

Hi, It will be good if you could add an attribute into config file to manager error class. Something like this : config.php

...
'error_class' => 'has_error'; // default
...

Then, edit this function :

protected function getFieldErrorClass($field, $class = config_value)
    {
        return $this->getFieldError($field) ? $class : null;
    }

Is there any plan to implement method chain behaviour? I like it because easy to customize element. I used to use adamwathan/bootform. So sad it is abandoned.

I already take a look at watson/bootstrap-form source code and tinkering to make it method-chaining-able 🤣 . I can make it without breaking original behaviour.

So, what do you think guys?