Hi forks, I am newbie in Laravel Twill.

What i am trying is to make settings page like as demo in below screen. could anyone help me?

Hey! I think I found a bug or I am too stupid to use checkboxes. 😉 Maybe someone can help me: In the admin backend I use create.blade.php and form.blade.php. If I put a checkbox or a select field in both of these it ends in a infinite loop of the change Event in the Vue Component. This happens every time I change a checkbox/select the second time. Workaround was to rename the field in one of these files and and write the content back again in the original field with overriding the function prepareFieldsBeforeSave() in the ModelRepository. Is this a known Issue? Attached are 2 screenshots of the loop and the frozen CMS.

settings-page

Hi @xbille am I getting correctly that.you currently have the same field in both create and form? If so I would suggest to only include it in the create file when creating (by checking that

$item

is not set)

that way when you're on the form it's not duplicated

I got a question regarding the WYSIWYG Editors. Is it correct that just the tiptap type can handle Tables correctly? And only the Quill one can be configured to use font-sizes? So there is no way to have one WYSIWG Editor to handle Tables and (!) font-sizes?

Hi @Andrej you're correct about tables. I'm unsure about tiptap font sizes, so that's probably right as well at the moment. Does tiptap outside of twill offer that functionality?

Thanks for that fast reply. As far as I understand tiptap should be able to handle font-sizes: https://www.tiptap.dev/api/marks/text-style/#textstyle But that extension isn't loaded by twill.

it seems to be released in v2, which is in beta phase 😦 So not officially supported yet, I guess

ha so yeah the thing with tiptap is that a lot of extensions do not ship a UI. I would welcome a PR, but I'm afraid the UI work is going to be a bit difficult, though we could take inspiration from how it's looking on the Quill implementation

alright, thanks for your input. 🙂

Hey @User, yes its the same field. Ok, thats another workaround. Will this never work?

Hello guys! I'm new to Twill and I'm diving the docs before trying it. I was wondering if I can plug Twill in an application with existing models and migrations.

Hi @User , yes this totally possible! Would your goal be to manage existing models/records from the Twill UI?

Yeah! That's actually what I'm looking for

Twill models are really just standard Eloquent models with some sugar on top. I can think of 2 ways to go about it. Generate a Twill module and: 1. create a relationship between the Twill model and the existing model (easier but more "wiring things up") 2. swap out the generated model with your existing model (more difficult, need to be familiar with what a Twill model does through behaviors)

Thanks for your feedback. What do you mean with "Create a relationship between the Twill model and the existing model"? If I have a model "Video" and I generate a twill module "Video", will it overwrite the old model? Or it will create a new, different, one?

By "Create a relationship", I mean create a new Twill model that will be attached to your original model. This won't cover all use cases but an example I can think of: create a Profile model to be attached to an existing User model.

I believe if you run

php artisan twill:make:module videos

with an existing Video model, Twill will generate all of the other parts of the module (view, controller, etc.) but will not override your existing model.

thanks @User! I believe I will go to the other solution (swapping models) since the ones I want to manage from Twill are quite simple

Will do some tests and let you know 🤟

Cool, yeah, please do! As far as I can tell, not many people are doing this. I'm super curious 🙂

Hi there, is there a repo that contains the Demo app featured in Twill page? Thank you.

Hi @User , the source for the Pentagram demo is not available unfortunately, but there are 2 starter projects I can think of, in case this can help you: https://github.com/cwsdigital/cws-twill-base https://github.com/croustille-io/twill-boilerplate

@User Thank you

I want to create a template in admin from where I can send a custom email. in the admin form, there will be a static input box where the admin can add multiple emails and a textarea box. After submitting an email sent to all the email ids added in that box. But I can't find any documentation for that. can anyone pls help me with this?

Hi @User , have a look at the Laravel documentation for configuring & sending emails: https://laravel.com/docs/8.x/mail

On the Twill side, I can think of 2 ways to approach this: 1. Create a new module with all your required fields in

form.blade.php

. Then, send the email from the

afterSave()

hook in the module repository. You could mark the message as "sent" in a boolean or datetime DB column, to avoid sending a message multiple times. This is probably the easier option. 2. Create a custom CMS page to build your form, with a custom controller to receive the data and fire up the email. I think this option is more flexible but harder than 1.

We would like to translate twill-navigation.php title so that the navigation in the cms is not only in englisch. Is there a way to do translations for stuff like navigation item titel or block title for example?