Twill

<@!750287421773578240> are you using the HandleNesting trait or not?

ok so you need to call `setNewOrder` from the trait not the parent class

https://andy-carter.com/blog/overriding-extending-a-php-trait-method

Thanks! Going to look into it tomorrow 🙂

Is it possible to use a browser field in a settings section?

Hey <@!344701191000948736> there is currently no option for this. There is a workaround available that "mimics" this behaviour: https://github.com/area17/twill/issues/743

also you might want to use buckets for that <@!344701191000948736>  https://twill.io/docs/featuring-content/

Hi <@!369183845238571010>, I've tried to change to Homestead as adviced. I managed to setup, but when I want to make it for twill I again don't know how to reach the admin site, it gives me back the home laravel page for each try
/hosts:
192.168.56.56 homestead.test
192.168.56.56 admin.homestead.test

192.168.56.56 is my Homestead.yaml ip

To not spam whole support channel with notifications. <@!742300291365339137>

Sure. Sorry.
So, no, I thought that's optional, for ADMIN_APP_PATH

But each time I change something in .env I have to re-run the vagrant?

Can you try with this .env var 
```
ADMIN_APP_URL=admin.homestead.test
```

You dont need to reload Vagrant for env edit actions.

Have you tried on normal route without subdomain?

In the documentation is written:
"In development, make sure that the admin subdomain is available and pointing to your app's public directory."
Am I have to do something with this?

Yes. For homestead.test it gives me the classic laravel page. But for admin.homestead.test the same

Oh yes. Probably bcs I didn't gave the map in .yaml for admin

Thats same since alias is for same Homestead host

You can access to it from `homestead.test` and from `admin.homestead.test`, so thats 2 diffrent named hosts for same host

And per .env it should work by default on admin.homestead.test

You can try to rename admin. to some other subdomain like manager.homestead.test

Or use same domain access point for Twill, since I never used this type of Twill serve with subdomains.

I've changed it to .manager but the result is the same.

Do you see routes if you run php artisan route:list

Serving twill on homestead.test/admin for example?

```
APP_URL=homestead.test
ADMIN_APP_PATH=admin
ADMIN_APP_URL=homestead.test
```

APP_URL needs to be with those params, do you have it in env?

Soory, I cant help with this since probably something is Twill regarded error.
Maybe <@!479379745856028705>  can help you furher.

Do you have .env vars setuped properly for Twill?

<@!742300291365339137>  maybe you need to still add the subdomain to your homestead.yaml? Copy the definition of your main domain and add the admin. prefix.

<@!385142776674910238> I've added it, and to hosts as well 192.168.56.56 admin.homestead.test. But still directs me to classic laravel home page

When you run `php artisan route:list | grep admin.` do you see the correct url in the left column?

<@!385142776674910238> <@!369183845238571010> Oh. It stored the previous domain there. I've run php artisan optimize, now it's okay.

For development I would recommend not using the optimize. You can run `php artisan optimize:clear` to get rid of the caches 🙂

Is it possible to have a published revision of a resource and work on an unpublished draft? So for example have revision 3 currently published and visible; then start new drafts / revisions until you publish a specific revision again.

not yet, but it is definitely something we want to implement

alongside workflow features like assignments and approvals

i try to upload a image with the media form field

i want to upload the images in the storage folder

Hi <@!713238304954384404>, this is because Imgix is the default image rendering service, try with Glide:
```
MEDIA_LIBRARY_ENDPOINT_TYPE=local
MEDIA_LIBRARY_IMAGE_SERVICE=A17\Twill\Services\MediaLibrary\Glide
```

hi everyone, i am having some trouble with sorting an index column that uses a many-to-many relationship. i'm on Twill v2.6, and using the new many-to-many logic that was added in issue `#1174` https://github.com/area17/twill/pull/1174

i'm attempting to follow the example here: https://twill.io/docs/crud-modules/controllers.html#example-sorting-by-a-relationship-field

but my sorting doesn't seem to work. when i log the query and run it manually, it seems correct, but the JSON response does not correspond to that query result

can i set a default value for a form field?

Hi <@!597948601897058305>, interesting, can you share what you did in the repository and model scope?

here's my `Product` model scope, I'm wondering if I am maybe doing too much

```
public function scopeOrderByCategory($query, $sort_method = 'ASC') {
        return $query
            ->join('category_product', 'products.id', '=', 'category_product.product_id')
            ->join('categories', 'categories.id', '=', 'category_product.category_id')
            ->join('category_translations', function ($join) {
                $join->on('category_translations.category_id', '=', 'categories.id')
                    ->where('category_translations.locale', '=', 'en');
            })
            ->select('products.*', 'categories.id', 'category_translations.title')
            ->orderBy('category_translations.title', $sort_method);
    }
```

and here is the Repository change

```
public function order($query, array $orders = [])
    {
        if (array_key_exists('categoriesTitle', $orders)){
            $sort_method = $orders['categoriesTitle'];
            // remove the unexisting column from the orders array
            unset($orders['categoriesTitle']);
            $query = $query->orderByCategory($sort_method);
        }
        // don't forget to call the parent order function
        return parent::order($query, $orders);

    }
```

hmm, you might want to use/look into this scope to order by translations https://github.com/area17/twill/blob/2.x/src/Models/Behaviors/HasTranslation.php#L65

would i use that instead of the custom code above?

i've added it, but i'm not sure how i get it to use the category translations instead of the product translations

in other words, it is now sorting by the product title instead of the category title. 

here's the updated Model code:

```
public function scopeOrderByCategory($query, $sort_method = 'ASC') {
        return $query
            ->select('products.*', 'categories.id', 'category_translations.title')
            ->join('category_product', 'products.id', '=', 'category_product.product_id')
            ->join('categories', 'categories.id', '=', 'category_product.category_id')
            ->orderByTranslation('title', $sort_method, 'en');

    }
```

i've got it figured out, i think. my original code i was `select()`ing `categories.id` and that seemed to be throwing off the translation layer by having two `id` fields in the query results

I'm always curious, what are you building with Twill?

looks like it has products and categories haha

the company i work for has several audio brands and i am building a proper CMS for them with Twill, along with a new frontend for each

let us know in <#811986244748705875> when it's live, we can feature it on https://twill.io/made !

<@!713238304954384404> yes, though not all fields support a default