@elkex you mean to add addresses?

No, just to get Twill users to send a notification to

But I want to send them through the model

I would like to understand your usage. What you want to send trough model? In which format? You provided insufficent informations.

I want to send a notification to the Twill backend users if a user registers in the frontend so that they can accept that user 🙂

I can get the frontend users by doing User::all() ; but is there something similar for the Twill backend users?

\A17\Twill\Models\User::all()

? Its so simple that Im thinking that I get the wrong idea.

Aha oké, just as easy as 1 2 3

Is there also a backend form function for tracking changes to a form field? I am accepting the users in the Twill backend and once a user has been approved, he will receive an email.. But I don't want that email to send everytime something changes to the user's profile in the backend..

Logic is bad per this example you provided. You can make a better logic with some action like dropdown in which you choose to notify user or not via email on activation.

That's actually a good idea, thanks

Can I hide this in my dashboard?

& how can I add data to the all activity tab here

Hello could you please help me to solve N+1 problem in my Twill app Found the following N+1 queries in this request: Model: App\Models\Page => Relation: App\Models\PageMeta - You should add "with('App\Models\PageMeta')" to eager-load this relation. Model: App\Models\Menu => Relation: A17\Twill\Models\RelatedItem - You should add "with('A17\Twill\Models\RelatedItem')" to eager-load this relation. Model: App\Models\Menu => Relation: A17\Twill\Models\RelatedItem - You should add "with('A17\Twill\Models\RelatedItem')" to eager-load this relation. Model: App\Models\Service => Relation: App\Models\Slugs\ServiceSlug - You should add "with('App\Models\Slugs\ServiceSlug')" to eager-load this relation. Model: App\Models\Service => Relation: App\Models\ServiceMeta - You should add "with('App\Models\ServiceMeta')" to eager-load this relation. Model: App\Models\Service => Relation: A17\Twill\Models\Media - You should add "with('A17\Twill\Models\Media')" to eager-load this relation. Model: App\Models\Menu => Relation: A17\Twill\Models\RelatedItem - You should add "with('A17\Twill\Models\RelatedItem')" to eager-load this relation. Model: App\Models\Technology => Relation: App\Models\Slugs\TechnologySlug - You should add "with('App\Models\Slugs\TechnologySlug')" to eager-load this relation. Because I have 50 queries and my corp website works slow....

@Abdullahi if you disable create in all your modules configured for the dashboard that dashboard should disappear

to add data to the activity tab you need to enable activity on your configured dashboard modules. Make sure to define a morphmap or use the FQCN of your model

Hi @crupko93 which request is that? Are you building the query yourself? Did you use the

with

feature to load some of them? Regarding related items, they are not the most optimized way to store browser fields for that reason. They will always end up creating n+1 queries because they are stored in a polymorphic table.

Now if what you are building is a corp site there's a high chance that you can cache a lot of things, if not the whole response, either using a package like response-cache, and/or a CDN.

@ifox I'm using with in Page Model

Hello together. Does twill have the possibility to build forms in the frontend?

I Need a simple contact form 🙂

Ok i have build a normal laravel form 🙂

And pass the options from the twill settings

hi @beardcoder there are many ways you can work with forms and twill. For simple use cases, what you did sounds great. You can use a singleton module if you need more capabilities, or even create a form builder for your admins with a block editor field. You can also create a twill module for the submissions if you want to review them in the CMS

Big thx 🙂

Hi guys, thanks for fixing the locale setting problem in this issus https://github.com/area17/twill/issues/2074#issuecomment-1404509377 But the mediable fields still cannot be show properly. I have add some more information about the mediable fields settings. Is there are problem in the settings?

right missed that because it was a comment not the issue itself 😄 Will check tomorrow

Thank you!👍

Hi 🙂 Is there a way to add two seperate block editors to a module, let's say one set for the header and another set for the page?

Hi @jefsev yes, by using a different

name

on the block editor field