so I have user model in laravel project. and I would like to show users list and set some actions on the user table using twill.

is it possilble to do it using twill.

you can do something like this or make your frontend user extends from Twill's model so that you can configure it as a module in the CMS

this PR might be interesting for you too

well you got what I want to do?

Yes, you want to list your Laravel user model in Twill's CMS listing UI

or, you want to display a list of twill users on the frontend?

thanks, there was one \' in my block blade file, as you pointed out

the first one.

the first link is exactly about that

> This is a simple solution to allow site administrators to manage frontend user profiles from the CMS

thanks, I will check.

Hey everyone! Been using Twill for a few weeks now, and am quite impressed so far. I've bumped into the need to add a custom button to a model's edit form, just under the update button. The idea is that the model in question is created via the frontend by users, but goes through an approvals process. An admin can make any changes to the submitted model, as so required, and then "Approve" it. I'd normally settle for a checkbox or something, but the backend code needs to soft delete the model as well, as approval creates a new model in a different table for presentation on the site. How does one go about doing this?

I'm guessing one cannot add buttons to the sidebar, so I'd be happy to add it to a fieldset at the bottom too. Just not sure on the best approach regarding the backend (thinking about auth and what not).

try

sideFieldset

or

publisherRows

Thanks, managed to get a nice button in there, above the update button, but still good. Will try figure out the rest with the endpoint and what not.

Hi @User , custom actions and sidebar items come up regularly on the chat. I took a quick stab at it:

@extends('twill::layouts.form')

@section('contentFields')
    {{-- Regular fields here --}}
@stop

@section('sideFieldsets')
    {{-- Something to approximate Twill's fieldset --}}

    <div style="
        display: flex;
        flex-direction: column;
        align-items: stretch;
        padding: 10px;
        background: white;
        border: 1px solid #e5e5e5;
    ">
        <a17-button type="button" variant="primary" size="small" @click="$root.$refs.actionApproveBtn.click()">
            Approve
        </a17-button>
    </div>
@stop

@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>
        <button type="submit" ref="actionApproveBtn">Approve</button>
    </form>
@stop

A bit hacky but I personally like the simplicity. You could also go with a custom Vue component if you have time 🙂

hi @User I checked the git rm. file.

so if I want to manage one model in origin laravel, I should make twill module and make relationship between 2 models?

Thanks so much, will give that a bash

@User before I answer your question, please read #811986108820357140 and avoid pinging me in private message when you don't get an answer quickly enough, this is not how open source support works.

Works great!

@pboivin @MikeR one thing that would need to be fixed is the side effects of using multiple fields in the side fieldset because of the sticky publication sidebar above it

that's one way of approaching it yes, which works great

@User Good to know, thanks. I have a few models that could use sideFieldsets. In this case, publisherRows works perfectly.

nice!

another way would be to override

submitOptions

to hook into the existing button