It seems in Twill 2.8, /area17/twill/src/Services/Cloud/Aws.php still uses

League\Flysystem\AwsS3v3\AwsS3Adapter

despite Laravel 9 requiring Flysystem 3 which replaces that class with the new

League\Flysystem\AwsS3V3\AwsS3V3Adapter

. Just checking I'm correct here before I write a workaround.

That's correct. Twill internals do not use this class so we missed Laravel 9 support on it.

@ifox When you plan to release version 3 or implement support for Laravel 9?

Laravel 9 is supported by 2.8 which has been tagged earlier this week. We're working on communicating that. Check our GitHub roadmap project to learn more.

Thanks

ok! We are doing with Twill everything we used to do with ACF, and much more, so I feel like it should work for you.

https://spectrum.chat/twill/tips-and-tricks/recipe-form-repeater-that-persists-as-json~c163f8c0-b11c-44d1-8d66-b3c1d814315d Does anyone know how to do the above?

1. Add HandleJsonRepeaters trait to module repository 2. Add repeaters to property jsonRepeaters

@Johnny Maynne Thankyou! I can see it saved into the database, but after I refresh the form, it doesn't load the saved repeaters values.

@formField('repeater', ['type' => 'product'])

@twillRepeaterTitle('Product')
@twillRepeaterTitleField('name', ['hidePrefix' => true])
@twillRepeaterTrigger('Add Product')

@formField('input', [
'name' => 'name',
'label' => 'Name',
'translated' => true,
])

<?php

namespace App\Repositories;

use App\Models\About;
use A17\Twill\Repositories\ModuleRepository;
use A17\Twill\Repositories\Behaviors\HandleFiles;
use A17\Twill\Repositories\Behaviors\HandleSlugs;
use A17\Twill\Repositories\Behaviors\HandleBlocks;
use A17\Twill\Repositories\Behaviors\HandleMedias;
use A17\Twill\Repositories\Behaviors\HandleRevisions;
use A17\Twill\Repositories\Behaviors\HandleTranslations;
use A17\Twill\Repositories\Behaviors\HandleJsonRepeaters;

class AboutRepository extends ModuleRepository
{
    use HandleBlocks, HandleTranslations, HandleSlugs, HandleMedias, HandleFiles, HandleRevisions, HandleJsonRepeaters;

    protected array $jsonRepeaters = [
        'product'
    ];

    public function __construct(About $model)
    {
        $this->model = $model;
    }
}

{
  "product": [
    {
      "id": 1650792423141,
      "name": {
        "en": "Product Apple"
      },
      "blocks": [],
      "medias": [],
      "browsers": []
    },
    {
      "id": 1650792424665,
      "name": {
        "en": "Product Orange"
      },
      "blocks": [],
      "medias": [],
      "browsers": []
    }
  ]
}

fillable

@Johnny Maynne Fillable for what? Sorry

you need to add

product

in the model's fillable

and obviously create a JSON column named product in your table

it might not be your issue though, as it seems like you're able to save

I have created a

Singleton

called

About

, within that module, I want to use a repeater.

yes, that makes sense, and everything looks good in the snippet you shared

The saved data is from table

about_revisions

,

payload

column

That's not really the "saved" data, that's just the revisions for history/audit trail

Your abouts table should have a JSON column

as in, you need to create that column in a migration

thankyou! working now.

For singleton module, you have to define column for every field?

if the field you're using needs it, yes, a singleton module is a regular module, it is just meant to have a single record

some fields like

medias

,

files

or

block_editor

don't need fields in the model as they are polymorphic

I see, it's like that too for normal modules (stage column)

if you're looking for something where you don't have to create anything, check settings pages, but not all fields are supported on them as the moment.

I thought the cms will just grab the data from latest revision's payload column

no, it is using those to preview and restore, but you wouldn't want your model to be stored as such when you query it for your frontend