Name Content

<textarea>
    </div>
    
    
    <div class="tab-pane fade" id="tab-bg" role="tabpanel" aria-labelledby="tab-bg">
        <label class="form-control-label" for="input-name">Name</label>
        <input type="text" name="name[bg]" class="form-control" />
        
        <label class="form-control-label" for="input-name">Content</label>
        <textarea name="description[bg]" class="tinymce form-control"><textarea>
    </div>

<div class="tab-pane fade" id="tab-de" role="tabpanel" aria-labelledby="tab-de">
        <label class="form-control-label" for="input-name">Name</label>
        <input type="text" name="name[de]" class="form-control" />
        
        <label class="form-control-label" for="input-name">Content</label>
        <textarea name="description[de]" class="tinymce form-control"><textarea>
    </div>
</div>
```

The function will also add "has-danger" class if a validation of a field has failed.

It will also populate the `value=""` attribute (or content of a `<textarea>` field) automatically when editing a model. Hence why you need to specify the variable name of the model as a second parameter:

```markup
{!! language_fields($fields = array(), $product ?? null !!}
```

{% hint style="info" %}
Say you have a method called `edit()` in your `ProductController.php`. In this method we get the product from the database, pass the `$product` variable to the template and return the product.blade.php view. However you may also have a `create()` method, that will return the same view. But this time we don't have to get a product from the database. We will create a new one. Hence the `$product` variable is not defined. To not get an error "***unidentified variable name $product***" when using calling `language_fields()` you can add**`$product ?? null`** as the second parameter.
{% endhint %}

When the form is submitted, the content of the request will be this:

Now in your `store()` method you can do this:

```php
Product::create($request->all());
```

Of course  when using Eloquent's `create()` or `update()` methods you will need to specify the `fillable` or `guarded` attribute on the model.

```php
public $translatable = ['name', 'description'];
protected $fillable = ['name', 'description', 'price'];
```

Whenever you need to display the content of the product for example you can just do this:

```php
$product->content; // Returns value of content field in the current app locale.
```

If you want to get the content field in a specific locale:

```php
$product->getTranslation('content', 'bg'); // Returns value of content field in Bulgarian.
```

{% hint style="success" %}
To learn more about translating models visit <https://github.com/spatie/laravel-translatable>
{% endhint %}

---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://taffo.gitbook.io/hotcoffee/customization-and-logic/multilanguage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

New Product