it worked on the project without twill

the difference is that twill uploader is doing direct upload from your browser to the object storage

it doesn't go through the Laravel app outside of getting a signature for the frontend request

that's why cors rules are important to get right

I have no experience with contabo unfortunately

I think the problem is something else, the bucket url is something like https://usc1.contabostorage.com/my-bucket but the public sharing url is https://usc1.contabostorage.com/281158c2879744c0a32493bac29d8ac6:my-bucket

testing with curl I discovered that when I make a request to https://usc1.contabostorage.com/my-bucket it will always respond with 401, but with the other url it gives 403

I have tried to make twill be able to set the public url but it always ends up adding

my-bucket

as subdomain, if I set the PATH_STYLE_ENDPOINT to true it overrides the path I need I had the idea to directly change the code that generates that URI to see what would happen, however what I get is a 503 error

maybe this is why i get Unauthorized? (this is from contabo's doc)

Has anyone here had any success in using a Cloudflare R2 bucket in Twill? I'm currently bumping into a CORS error — OPTIONS request throws a 400 and the subsequent POST throws the CORS error. I have published a CORS policy to the bucket, but this doesn't appear to make a difference at all.

Ok I think this is actually a CF issue. https://community.cloudflare.com/t/problem-with-settings-cors-policies-on-r2/432339/7

May I know if there is a solution to handle this case (Twill 3): I have a block "Slide" and I want to have two very similar repeaters "left links" & "right links" so I am going to write this on block definition blade:

php
    <x-twill::repeater
        type="links-repeater"
        name="left_links"
        label="Left links"
        :max="5"
    />
    <x-twill::repeater
        type="links-repeater"
        name="right_links"
        label="Right links"
        :max="5"
    />

However the name & label are not working on backend, I guess "type" is keep using in the repeater. And conflicts are happening between two repeaters due to same "type" is using. So in short, can I override the name of "type", by overriding name, to define two repeater separately in the same form.

Unfortunately at the moment that wouldn't work indeed. I would suggest creating 2 repeater files that include the same partial view to avoid repeating yourself. Then in the above code you case use the 2 different types. But I agree this would be better if we supported reusing the same repeater type in the same form.

Hi @ifox Do we have any news about condition fields? I was writing here a week ago, that value of hidden fields are still saving

If values of hidden values are still saving, you can overwrite that behaviour by

php
// Your repository
public function afterSaveHandleBlocks(Model $object, array $fields)
{
  unset($fields['your_hidden_input_fieldname');
  return parent::afterSaveHandleBlocks($object, $fields);
}

Thanks for answer, but this behaviour right now in all blocks. I don't think, that I will describe all fields in this method 🙂

I would like to understand, where do you use those hidden fields values if you dont want them saved?

@kalle This fields are under condition, and sometimes they are hidden if condition is false. So if they were filled before condition is false , it's still will be saved even if it's hidden

@BA7YA when using

_connected_fields

in a block, you need to pass

'renderForBlocks' => true

Yeah. But even that renderForBlocks will not fix my issue

yea I'm not saying it will fix it but you still need it for it to work properly

Ok, I get you. But if those were module fields, you would still need to define them in the Model, so idk, but you can treat them ignored if they dont have values, or unset like in example above if xx fields is false, ignore else leave the fields. But this should be default behavior in blocks, or Im missing something.

he's talking about hidden fields from the connected fields util, they are not supposed to be kept and saved in the block data if

keepAlive

is not set to true

Exactly

Im not so experienced with blocks, so Ill leave it to the pros 😄

😁

Is it possible to create a module that does not have a "draft/live" toggle?

Yes, I think it is better to allow reusing the same repeater type in the same form. Thanks so much.

Hello, I have a question about slug & permalink. When using HasSlug, can I set the permalink to be "not translatable", and keep sync the permalink in the same Page among languages?

@DKC you can use a getPermalinkBaseUrl to override it in the modulecontroller