@uwascan Do you find side fieldsets useful in your case? You can adjust this callback to make a redirects (JS navigation or post request to custom endpoint which should redirect user to specific url).

I am not sure side fieldsets are useful in my case and I do not know what callback you are referring to here. I have a read only module whose records are created from the frontend contact page. I can view those records from the Twill admin panel in read only mode, but I need to provide a feature that allows admins to reply to those messages through email. I just needed a way to provide UI that the they can type their replies in and click a button to send.

You can check message which I replied to. It can serve the same purpose which you want to achive.

Thanks. I will do just that

Wonderful. Twill is powerful no doubt but tricks like these needs to be documented to make discovery a lot easier.

Thanks again because around the answer you pointed me to, I found information to for how to solve another problem about managing frontend users in twill. back to my previous issue. How would you get the value of a field in the twill form to be submitted along with custom form? I have a reply_message field in my twill form I need to submit along with the from to basically send a mail. I tried using v-model to link to a hidden field. that did not work

@section('content')
    @parent

    {{-- Add a form for the custom POST action, outside of Twill's main form --}}
    <form action="/admin/my-custom-action" method="POST" hidden>
        <input type="hidden" ref="replyData" v-model="reply_message" />
        <button type="submit" ref="actionApproveBtn">Approve</button>
    </form>
@stop

Latest change route

Route::get('/locations/{slug}', [LocationController::class, 'page'])->name('location');

controller

use A17\TwillTransformers\ControllerTrait;

    public function page($slug, LocationRepository $repo)
    {
        $data = $repo->published()->forSlug($slug)->first();

        return $this->view($data ?? null);
    }

This is what working for me, please point me in the right direction if you know a 'better' way.

This looks good

you can still simplify to just

$data = $repo->forSlug($slug);

for the same result

I dont have any idea which could help you here since Im not familiar that much with Vue. Those components are already compiled and it makes harder to apply some additional logic. For this usage of yours you can create custom Vue component which would resolve this usage easily. cc @pboivin for possible help 🙂

Thanks. I will look for a way out

custom-form-action

I am trying to use native Twill vue input component in a custom vue component but I cant figure out how v-model works.

<a17-textfield name="message" label="Message Body"
           type="textarea" :rows="5" v-model="form.message">
        </a17-textfield>

Two way binding with v-model is not working. Is there any documentation of the Vue components of Twill?

Ended up using @change event for now to manually sync data

Hi guys. Is there any chance to get name of parent block in repeater blade without using any helpers?

Good afternoon! Please advise on my question. You need to sort the records in descending order by the created_at field. By default, I see that there is already a code protected $defaultOrders = [ 'created_at' => 'desc', ]; But for some reason it doesn't sort properly. Has anyone experienced this? There must be a newer entry first.

I see on your screenshot that reordering is enabled on your module. It won't sort by a column if you are enabling reorder, it will sort by position.

Parent block in repeater

@ifox Should I then remove HasNesting and HandleNesting?

Well that depends if you need it or not, but you can't combine it with ordering since ordering is controlled manually

What's the easiest way to turn a non-translatable module into a translatable module?

I am afraid there is no "easy" way, you will have to write a manual migration to do that. To start with, I would generate a similar module and compare so you know which additional classes you have to create on top of your model.

Good afternoon! Can you tell me if the following can be done? A user with a certain role can go to the article. He is only allowed to publish it, but not to edit it (I have blocks). I only have thoughts to do it through the blade

Hey @Hip-Hop didnt you make a support post about this?

@Harings Rob Wrote. But I'm interested in the point that the user with the role could not change the text in the blocks.

you can disable the field, but there's no global way.

I guess if you want to only publish you could disable edit entirely for that role at the route level, and they can still publish on the index. It's a bit of a weird use case though, why would someone be allowed to publish but not have the ability to edit the content?

@ifox Such a task came that there are two roles. One allows you to create articles, while the other allows you to view and publish them but not edit them. I don't really like it either, but I'll have to do it for now.

Please tell me, Input has a default option. I'll add an example like this

@formField('input', [
     'name' => 'test',
     'label' => 'test',
     'default' => 'text text',
     ])

But the field is empty.

If there is any value in the db for the field, even if it is an empty string, the default might not kick in.