Yes, this will depend on your frontend configuration. Are you using

laravel-localization

?

Yup!

Great! So yes, this is your responsibility, but with everything setup correctly, you could use the standard route helper. Something like

route('article', $article->slug)

Ok! In that case the route helper seems like the way to go! Thanks 😃

Hello everyone I am trying to achieve something like in the demo Twill provides to be more exact the About module but I can not find anywhere in documentation some details I saw in the demo ex. 1. How to edit something in modal and not in separate page? 2. How it is possible to create something like the Overview sub page where you have only one input and one WYSIWYG and no "Add new" button? Is this achievable in the sense that this is something from Documentation or am I missing something?

@User for 1., this is

editInModal

set to

true

in the

$indexOptions

of your controller. for 2. this is a module with a single record being directly linked in the navigation

I need to deploy app to Mysql 5.6 (unfortunately). Is there a way to do it? Like overwrite

json

columns to

text

or smth?

(that app ofc uses Twill, that's why I ask 😄 ) We used database on other server, but I would still be interested if it's possible to deploy on Mysql 5.6

when I want to open Settings on production, nothing happens. On my local, it opens settings

Hey @Sami see this discussion

so the problem was that my settings section is named SEO - uppercase and my file was lowercase -

seo.blade.php

. Worked on my Windows machine, but did not on Linux webhosting

thanks!

ha yeah, makes sense. windows and case insensitivity 🤦‍♂️

Hi. I was trying to create background models and controllers in a finished capsule. Rewrote the configuration in twill.php. But all the same, the repository is not searched for at the new address.

Hi @User , could it be a cached configuration issue? Have you tried

php artisan config:clear

?

Ok, could be a deeper issue then. Just trying the usual suspects.

@User Just another thought, have you tried

composer dump-autoload

?

Looking more closely at the config, it looks like you're registering

MenuItem

as its own capsule, but it's a module contained within the

Menu

capsule. Am I reading this correctly?

Have you tried without the whole

['name' => 'MenuItem' ... ]

entry?

exactly @User. @User you don't need to register it like a capsule, you can have a another model living inside a capsule. you might need to if you need routing for that module though. do you?

Thanks. Maybe I'm looking for a bug in the wrong place.

Heya, is there a way to use one

$mediasParams

option for multiple different

medias

fields in one form? Let's say we have

php
public $mediasParams = [
    'cover' => [
        'default' => [
             [
                 'name' => 'default',
                'ratio' => 16 / 9,
            ],
        ],
    ]

and we want 3 images which have the same crop ratio but don't want to save them as "gallery" - they have a different role but same ratio. What I do now is just copy paste the

cover

option, rename new ones and set

name

of medias to the new options , but that seems a bit... ugly? I just though if there is a better way of doing it

@User you can convert all crops to constants. see https://github.com/area17/twill-capsule-base/blob/main/Crops.php

In your model, write a constant

public $mediasParams = Crops::HOMEPAGE;

that looks very good

thanks

will use it in the future

How can i create new admin user for new project?

probably

artisan twill:superadmin