For regular repeaters, you do need an extra column for the relationship. There's a simple example in the docs: https://twill.io/docs/#repeater You can also use JSON repeaters which are a bit more limited but easier to setup: https://gist.github.com/mcylinder/6ff7876f29cce8a23b81f3ea80e02a23

Hey, thank you @User . JSON repeaters will do just fine for me!

https://github.com/area17/twill/pull/775 How would i setup the navigation in

twill-navigation

following this approach ?

@User This is probably the most complete example for now : https://github.com/area17/twill/issues/508 In this example, you would only add the

issues

module to your

twill-navigation.php

, the

issueArticles

module will be accessed directly from the issues list. This will be added to the documentation soon.

Does twill have some kind of helper to resolve $view_active_variables inside a controller (before the view composer) ?

@Rayderxx not sure what you mean, in an admin controller?

nevermind @ifox find my answer 😉

I'm curious though haha

what did you find?

Hmm I'm trying to build a Categories capsule has a morph relationship based on the twill-navgition menu

very interesting, so that categories are kind of namespaced by CMS sections?

Yep that's the idea

Is there a recommended way to hook into Twill and perform an action only on publish? (Some processing / generation in a job/queue) I can see that the

ModuleController

dispatches events, but it appears to simply dispatch the same event (cms-module.saved) on both update and publish.

hi @chrispymm those events could definitely be improved to be more granular. The only operation that currently provides some data to work with in the event listener is create, which can help for some aspects (like not triggering the RefreshLQIP command until images have been attached when using the create modal that doesn't support medias fields). A more reliable way would be to hook into the repository's

afterUpdateBasic

and

afterSave

, through a trait you'd add to all your repositories when you want to do something on publish.

I thought that might be the case, but thought I'd double check. So I'd be checking the dirty state of the published attribute to figure out whether it's just been published?

you're definitely right to ask. that's right. but before you go in that direction, let's hear how you would have liked to implement this in your app. I'm guessing you'd like an explicit

publish

event?

Yeah, I guess what would make sense to me is a distinct publish event, that way I can simply hook into it with a listener.

makes sense, let's make it happen?

and it'd probably be good to get at least the module name as an argument so you can respond to changes on specific modules

totally

on the surface it looks like a pretty easy change to make - would there be any current side-effects to changing the events dispatched in the ModuleController? Twill doesn't look to have any built-in listeners... I guess it would still potentially be a breaking change for anyone who was listening for the generic save event.

on the same theme I'd like to improve the lack of consistency between publishing from the index view and publishing from the form

Twill won't be impacted by a change there but users could so as long as we only add to the existing, all good

So to avoid the backwards incompatibility you could fire the generic

cms-module.saved

and then add in a new

cms-module.published

exactly

If i get change I could try and put together a PR for that if it would be helpful?

*chance

P.S. Thanks for fielding some support questions relating to some of the capsules I have on GH - I've been away on holiday so wasn't on here to see/respond to them. Probably should add a WIP disclaimer to the readme for them though!

Hi I'm having an issue regarding the media library: I want to add fields like description and title to the uploaded files. Is there any way to do it ? 🙏