awesome! Thanks!

I figured out a way by manipulating store and using a mutation

sorry. That error message should be inside an array.

Just to confirm,

php
    'projects' => [
        'can' => 'custom-permission',
        'title' => 'Projects',
        'module' => true,
    ],

this will only prevent this specific role to acces this route or it will invisible to the logged in user with

custom-permission

?

this will be only visible to users with

custom-permission

for it to be only accessible by those users, you also need to do this on the route

Great explanation, just what I needed, thanks. 😄

But on the rest of the navigation items I need to append other guards like admin or publisher per default so users with this

custom-permission

cant see it?

you want users with

custom-permission

to only see that entry in the navigation, and other users should see everything else?

Yeah, I want to split roles since I will only need this for translators which are third party people, so they cant use rest of the CMS.

I see

Also something like disabling dashboard just for them would be good, but I only see global cvar for that.

My first idea was to create external access to the routes, but since Twill offers this I would gladly stick with it.

you could disable it dynamically from a middleware

Ill dig deeper in this when the time comes, but tnx for the idea.

hello everyone -- is there a standard or recommended way of sorting records in a model/repository? it was created with

HasPosition

, so the field is there in the db and everything, but i'm not sure what widget or CMS UI to use to actually sort them

hi @User did you add

'reorder' => true

to your controller's

$indexOptions

?

if you do that, you should get a drag and drop thing on each row

that did it! i knew it had to be something simple

Hello Everyone, I am experiencing a problem in twill content editor after I ran composer update, the content blocks section appears empty, and the content editor screen is empty too. any suggestions how to solve this? Note: when I ran composer update, Twill package has been updated to version 2.6.0

Hi @Bibo did you run

php artisan twill:update

?

no only composer update, shall I run php artisan twill:update ?

yes

after

composer update

,

twill:update

will publish its new compiled assets

Many thanks, I ran the command and it worked 👍

awesome, glad to hear!

one more question please, after twill:update it prints these error in log, the first error belongs to twill

Also I tried to save content but there is problem in validation. refuses to save.

this is your wysiwyg field crashing. Are you sure you didn't have this error before the update? The error on saving is different though, can you check your Laravel logs?

No I did not have that error before update, the last version I was using Twill 2.4 and it was fine, I will check laravel logs