I guess 1) is most interesting, 2) is Twill standard and 3) is maybe spatie/laravel-permissions

for 1) you need a form with @can() structure?

not sure if you already saw that one @KUS

i read this yes

oh well, i see you're looking to use Twill 3 permissions

you can still do some of it programmatically though

like using @can in the form

lets assume I have setup the roles, the question is more how do i control the UI that the user can edit text input but not delete image

right, ok

most fields have a disabled/read-only attribute

that you could toggle depending on the current user

must be probably a glocal config or controlller extending

ah i see

one could also do translator forms and switch them based on role ?

yes

EDIT: nevermind, I found the solution

Hi, new here. I have a question about secondary navigation. I have this navigation array in twill-navigation.php *return [ 'welcome' => [ 'title' => 'Welcome', 'singleton' => true, 'primary_navigation' => [ 'projects' => [ 'title' => 'Testemonials', 'module' => true, ], ], ], ];* admin.php looks like this: *Route::singleton('welcome'); Route::module('testemonials');* When I load the admin page I get PHP error: Undefined variable $_primary_active_navigation (View: ./vendor/area17/twill/views/partials/navigation/_primary_navigation.blade.php)

Im not sure you can use singleton as a main routing group. I would try like this.

php
return [
    'group' => [
        'title' => 'Group',
        'route' => 'admin.group.singleton',
        'primary_navigation' => [
             'singleton' => [
                'title' => 'Welcome',
                'singleton' => true
            ],
            'projects' => [
                'title' => 'Testemonials',
                'module' => true,
            ],
        ],
    ],
];

php
Route::group(['prefix' => 'group'], function () {
    Route::singleton('singleton');
    Route::module('projects');
});

Group

is just an example keyword, you can use own grouping keyword

Awesome, thanks @kalle. That works.

If modules are capsulated

Route::group(['prefix' => 'options'], function () {
    Route::group(['namespace' => '\App\Twill\Capsules\Headers\Http\Controllers'], function () {
        Route::singleton('header');
    });

    Route::group(['namespace' => '\App\Twill\Capsules\Footers\Http\Controllers'], function () {
        Route::singleton('footer');
    });
});

return [
    'options' => [
        'title' => 'Options',
        'route' => 'admin.options.header',
        'primary_navigation' => [
            'header' => [
                'title' => 'Header',
                'singleton' => true,
            ],
            'footer' => [
                'title' => 'Footer',
                'singleton' => true,
            ],
        ],
    ],
];

Hello, I have a question: I have setup a settings functionality in v3.0 and see the form and the translation fields correct. I can enter data and they land in the setting_translations table as expected. But: my form is always empty after reload and so. What do I miss here?

Hello, can we please discuss this in #989876822323908608 since that version is still in testing phase 😄

ok

Hi, when working with Browser fields as related items it doesn't seem to link back to the edit page of the related item. Is this true or am I missing something? Setting it up as not a related item, I can see its correctly linking to the edit page.

HEy @valhalla14 twill 2 or 3?

Hey, its twill 2.6

Will check in a bit

So on the latest 2.x release this should work (just tested).

Hello guys. I want to completely remove the content part and leave only SEO. Is there any way? This is form.blade.php @extends('twill::layouts.form', [ 'additionalFieldsets' => [['fieldset' => 'metadata', 'label' => 'SEO']], 'sideFieldsetLabel' => twillTrans('twill::lang.nav.settings'), ]) @section('fieldsets') @metadataFields @stop @section('sideFieldset') @endsection