but if I give them 5 crops, there always will be 5 crops

I mean they might want to use 2, and the others will be set by default

right

I'll think about it but we definitely don't have a UI for this at the moment

I think I'll just use multiple roles

not the nicest way neither in UI nor in code later but it's gonna work nicely

Hey folks. Concerning translations: say I decided to enable translations after I've already created a module. Is there a recommended way to transfer translatable data in the database from the main table to the _translations table or should I run a SQL query?

Hey @User I guess it could be a nice new command but at the moment you'd have to do it yourself

Hmmmm. Sure indeed. Thanks @User

specific-key-was-too-long-in-migrations

Hi, i have simple question how can i display field from settings for all views in front? thanks

it's something like {{ $settings->key('phone'); }} ?

Hi @User that's something you can do with a view composer to inject the settings value you need in all views

in the view itself you can always use

app(\A17\Twill\Repositories\SettingRepository::class)->byKey('phone')

but that will be cleaner in a PHP class like a view composer.

see at the bottom of this page: https://twill.io/docs/settings-sections/?#settings-sections

<?php

namespace App\View\Composers;

use A17\Twill\Models\Setting;
use Illuminate\View\View;



class SettingsComposer
{
    protected $settings = [];

    public function __construct()
    {
        foreach (Setting::all() as $setting) {
            $this->settings[$setting->key] = $setting->value;
        }

        $footer_email = $setting->email;
    }

    public function compose(View $view)
    {
        $view->with('settings', $this->settings);
    }
}

something like that?

yes, that works if you want to have all settings available

still i have undefined veriable ;/

did you register the view composer in a service provider?

yes

footer_email = $setting->email;

did you remove this line?

ok nvm just took a closer look at your code

did you check that $this->settings is what you need?

did you try to

@dd($settings)

in a view?

Yes, it show some arrays with values

so you should be able to use that to render in your view, no? if the structure isn't what you'd like, you can do things differently within the view composer

{{ $settings['email'] }} it is works. thanks

Hey guys is it possible for two admins to see and edit the same drafts?

hey @wicky possible, yes. A good idea, no, they will step on each other. Content locking and real time collaboration are in the roadmap.

hi is it possible to resend invitational mail if the previous expired ?