I can use checkbox in settings section ?

You should be able to since 2.0.2 https://github.com/area17/twill/commit/d62d303fba5e3ea0e6bcd8e838933bdab0c270cc

like I've said in the past the settings section was initially made for key-value pairs and is being used much more than intended. We've added support for a couple more fields but ultimately the feature needs to be refactored to behave like a regular twill module so that any field would be supported.

are you seeing this error by just adding a simple checkbox field to a settings page, checking it and saving?

no, I just see the error if I change de value of checkbox to true

how? by clicking on it? Or do you mean as default value? Can you share the formField snippet you use?

When I change to True and want to update the settings give the error this is my file @extends('twill::layouts.settings', [ 'contentFieldsetLabel' => "Manutenção", 'additionalFieldsets' => [ ['fieldset' => 'seo', 'label' => 'SEO'], ['fieldset' => 'contacts', 'label' => 'Contactos'], ['fieldset' => 'links', 'label' => 'Links'], /* ['fieldset' => 'attributes2', 'label' => 'Attributes 2'], */ ] ]) @section('contentFields') @formField('checkbox', [ 'name' => 'maintenance', 'label' => 'Em manutenção' ]) @stop @section('fieldsets') @formFieldset(['id' => 'seo', 'title' => 'SEO']) @formField('input', [ 'name' => 'meta_title', 'label' => 'Título', ]) @formField('input', [ 'type' => 'textarea', 'name' => 'meta_description', 'label' => 'Descrição', ]) @endformFieldset @formFieldset(['id' => 'contacts', 'title' => 'Contactos']) @formField('input', [ 'name' => 'telefone', 'label' => 'Telefone/Telemovel', ]) @formField('input', [ 'name' => 'email', 'label' => 'Email', ]) @endformFieldset @formFieldset(['id' => 'links', 'title' => 'Links']) @formField('input', [ 'label' => 'Facebook', 'name' => 'facebook', ]) @formField('input', [ 'label' => 'Instagram', 'name' => 'instagram', ]) @formField('input', [ 'label' => 'Política privacidade', 'name' => 'privacy_policy', ]) @formField('input', [ 'label' => 'Termos e condições', 'name' => 'terms_conditions', ]) @formField('input', [ 'label' => 'Livro reclamações', 'name' => 'livro_reclamacoes', ]) @endformFieldset @stop

I was able to replicate this on my end. Just added a checkbox to my settings page, default to

false

. Click it, then save. Got the same error.

Interesting... @User a quick workaround would be to use a radio with yes/no.

ok I will use that, no problem, thanks for your help guys

Hi Everyone, I wish a great day for all of you, I wonder if I can get a help on a small point: I am building a news website in Arabic Languages ( RTL Direction ) The RTL Slugs are not being stored correctly in database, it is a little bit weird, here is an example: lets say a category slug in RTL ( Arabic ) is : تصنيف twill is storing it as : "tasnif" in database - it is converted to the same pronunciation using English characters, the problem is building the URL structure using this way will confuse the google bots. just want to know how to store the slug characters as it is in the database. please any ideas on how to deal with this, I will be so thankful.

Hi @Bibo, check this out: https://github.com/area17/twill/blob/17390bb6f5c5f14f92d97ec5a7881f5e5d382a45/src/Models/Behaviors/HasSlug.php#L127

if you add locale codes to this configuration, you should get what you are looking for.

Thanks a lot I will check that immediately :))

I've copied the updateOrNewSlug function to the model, then added the rtl language code as this config('twill.slug_utf8_languages', [ 'ar' ]) and it worked perfect. just one thing, the permalink line is not showing under the title, when I open the title / slug update modal, the slug shows empty, when I hit update it is fine, just not showing the slug value. I attached screenshot

you don't have to copy the code, just use the config in your

config/twill.php

file

I did that, I added it to config/twill.php, please on update lets say I changed the slug, it does not save the new updated slug, and if I change the category name, it adds a new slug to the db but the new slug active = 0 In the screenshot, the same category_id just changed the title multiple times, every time it create a slug, but slug active is 0

okay I found it, I forgot to change the app locale in config/app.php to 'ar', once I did that, now everything works fine. Thanks a lot for Help 🙂

Yes I’ve tried that. Some of my models have a relationship with slug. The foreign key name also predefined and I dont wanna change that “ex: slug_id”. So changing my getForeignKey() while having relationship with “slug” will cause an error. So I only made a modification “updateRepeater()” 🤣

I'm doing

app(PostsRepository::class)->update($post->id, $data);

And instead of just updating all fields on

$data

variable the repository is actually deleting everything (translations, fields, blocks...), because, probably, it needs

$data

to contain the whole model data (original + new). But to have that I would have to reconstruct what the CMS frontend send to the repository, which (I've been there) it's huge. Anyone did this differently here?

@User Not directly related, but I reached a similar conclusion while investigating how the "duplicate" feature uses revisions under the hood. (The revisions data is generated on the frontend and is difficult to recreate manually on the backend.) Anyway, your problem makes me think — could you use revisions data to "hydrate" or "backfill" your $data before updating it?

@antonioribeiro what are you sending in

$data

?

I was sending only some fields @User

Came up with a new update method to fix it:

public function updateOnly($id, $updateFields)
{
    DB::transaction(function () use ($id, $updateFields) {
        $object = $this->model->findOrFail($id);

        $fields = $this->prepareFieldsBeforeSave($object, $updateFields);

        $fields = $this->removeMissingFieldsFromUpdate(
            $fields,
            $updateFields,
        );

        $object->fill(Arr::except($fields, $this->getReservedFields()));

        $object->save();
    }, 3);
}

private function removeMissingFieldsFromUpdate(
    array $fields,
    $updateFields
): array {
    $locales = locales();

    $updateFields = collect($updateFields);

    foreach ($fields as $name => $field) {
        if ($updateFields->has($name)) {
            continue;
        }

        if ($locales->contains($name)) {
            $fields[$name] = $this->removeMissingFieldsFromUpdate(
                $field,
                $updateFields,
            );

            if (count($fields[$name]) === 0) {
                unset($fields[$name]);
            }

            continue;
        }

        unset($fields[$name]);
    }

    return $fields;
}

This is very particular to my use case as it doesn't take in consideration blocks and other stuff, so we probably need a way better solution for this

Hi! What is the recommended Twill development environment setup if I wanted to run things like

php artisan twill:dev

I use Docker/Laradock at the moment and it's not agreeing with my setup and was wondering what you guys use: Homestead?, Valet?, Docker?, etc.

Hey @User, I use Homestead for pretty much everything. I've heard a lot of good things about Valet on macOS (and Linux). Never used Docker for Twill development specifically, but it seems to trip people up occasionally...

yup! sounds good and thanks for the response:: gonna have to use Homestead as Docker is just another beast

Out of curiosity, have you tried Sail? (It's the Docker kit from Laravel.)

Nope: I used Laradock