get tags from current page $tags = $this->repository->allTags()->get(); {{$tags}}

<meta name="keywords" content="[{" id":2,"namespace":"app\\models\\page","slug":"test","name":"test","count":2},{"id":3,"namespace":"app\\models\\page","slug":"content-marketing","name":"content="" marketing","count":1},{"id":4,"namespace":"app\\models\\page","slug":"strategia","name":"strategia","count":1}]"="">

public function afterSave($object, $fields) { foreach ($this->traitsMethods(__FUNCTION__) as $method) { $this->$method($object, $fields); } } 🙏 So basically I create a trait let's say HandleAdrian and in it I create a method called afterSaveHandleAdrian and in it I can tap into the system and do some operation?

Yep, that's it 🙂 All Twill behaviors hook into this system to implement some functionality on save, delete, etc.

wow! nice I am very excited by the possibilities!

I am sorry to bother you again with this "// add those 2 columns to enable publication timeframe fields (you can use publish_start_date only if you don't need to provide the ability to specify an end date)" So I am not sure I understand how it goes. Say that I publish something, that sets the publish_start_date(provided I implement it as per above suggestions), right? And publish_end_date is in case I unpublish it? Or publish_end_date may automatically unpublish something?

Ok so I am sorry again, for returning to this issue. So as far as I can tell the

that small button doesnțt create a publish start date

So I think this can be confusing to the end user(I know because I'll have to explain them how it works...)

does that small button tap into the repository infrastructure like the update/publish button inside e.g. the module record itself which we want to publish?

Indeed if you're changing the behavior of this field (which is meant to be entirely manual and disconnected from the actual published state), you need to consider this scenario. When using this button the controller calls the repository

updateBasic

method which itself calls

afterUpdateBasic

which you can leverage to achieve your use case. Poor name, I know, this will most likely be refactored in Twill 3.0 so that the publish button actually goes through a regular save action and repository lifecycle.

Thanks for the clarification this will help!

Hi, when I try to save on production I get this error. Locally everything works fine. Does someone know what it can be?

405 method not allowed

hey @User this sounds like a case sensitivity issue. check that your module name is camel case in the code.

so as far as I understand e.g. when you use the published scope in a Repository you don't need to manually write with('medias')?

you don't need to but with can help optimize your queries (reduce your n+1 queries)

oh nice thanks for the tip!

Am I allowed to make like say 2 admin settings overall? Say settings1 and settings2?

each with its own primary navigation

yet save of course in the same servicerepository

do you mean with the twill settings feature?

Thank you for the response, I have setup a clean twill project an reproduced it. I have the source code here: https://github.com/MarcelWeidum/twill-405 also I have it hosted online https://twill.webtive.dev (if you want the credentials you can dm me) so you san see it in action

yep

you might need to add custom routes but this should be possible. I'll give it a go if you're stuck

ok thnx

So indeed ifox, it wasn't hard to do, the only thing people should keep in mind is when adding another such route for settings the section blade still goes in views/admin/settings/my_section.blade.php

otherwise you just import the settings controller and have fun with your custom settings page

This is the kind of stuff that was not just very hard to do in TCG Voyager, it was basically impossible. So I was forced to use for a couple of months TCG Voyager, and they have this thing akin to a CRUD module, but you simply can't extend settings in such a manner, no translations, no custom formfields

for get translated strings from model I need to do "->translate($localte)->title" is that normal ? If I don't put that this don't translate for correct language

curious, I think I get everything translated automatically. But see, the devil is in the relation to the translation table, so maybe check that?