What os are you using locally?

Just tried php artisan route:list and it returns the same error. In Container.php line 879: Target class [] does not exist. In Container.php line 877: Class "" does not exist

Mac Mojave : 10.14.6 (making the most of my Adobe CS6 licences!)

Make sure that in your routes/admin.php items have the correct capitalization.

I thought they were all lowercase, I have Route::module('sections'); Route::module('sections.pages'); Route::module('sections.pages.areas');

Then models are Section, SectionPage and SectionPageArea

Found it, thanks for the help. It was the $modelName in admin controller protected $modelName = 'SectionPageArea';

I had it set to protected $modelName = 'sectionPageArea'; before

glad you found it!

Thanks @User @User .

Hi, how can enable uploading .webp image format in the medias form field? any suggestions?

Hi @Bibo, check this config https://github.com/area17/twill/blob/64f5857675f2c8d26ea52e2dc2e2e4d86f749060/config/media-library.php#L29

Thanks 👍

Hi all = Is it possible to use Twill without a title field? It works great for things like pages / news etc - but I need a module for a price override so it doesn't have a title nor anything like a title

Hi @adams you can use any field other than title, but you have to use one. You can compose multiple fields for display if you need.

Thanks for the reply @User - I'll make something custom as I dont need a title. I've not done much vue - is it easy to reuse some of the will components (e.g. data table , date pickers etc etc)?

a lot of them can be used but some might be trickier. In this article from a community member you can see how to use date pickers in a custom page: https://blog.izetmulalic.com/twill-cms-excel-export-custom-pages/

lovely - thanks

Hi, this may have been asked a million times, but i really cannot find anything online that would guide me how to do it. Does anyone have some example of how to deploy laravel application with twill using laravel envoy ? Because from what i see, i'd need to run the artisan command twill:install which then asks me for super user account input and that is not very suitable for CI :/ Maybe i'm missing something here ?

Hi @User you certainly don't need to run twill:install during deployment, that's a one time command you run when installing Twill in your application. There are no specific command to run during deployment for Twill outside of a regular Laravel deployment. The only thing would be if you don't version Twill assets in git, you'd need to run

php artisan twill:update

or

php artisan twill:build

if you use custom Vue components.

Hmm, thats strange, because i dont see any new migrations or seeds for super user, so how does it work exactly ?

you can create your super user however you'd like, could be by ssh'ing into your instance/container, or by running the twill:superadmin command from your CI (you can pass email and password as arguments), but you don't want that to happen on every deployment obviously

well I guess it wouldn't let you create another user with the same email in future deployments, but I just find it silly to run a command that is going to fail every single time you deploy

That is indeed silly and i dont want that :D I think we misunderstood each other a bit :) let me explain more: afaik deploy consists of: 1. Cloning repo to new folder 2. Running composer install 3. Running npm/yarn install 3. Running migrations

You are suggesting to me that i need to SSH into the server and run the twill:install first time manually and then just let it be ?

not at all

I was talking about

php artisan twill:superadmin

you don't ever have to call twill:install on a deployment

twill:install publishes files in your repo like any other Laravel package and it runs the superadmin command for you to setup your first user locally

and what about the twill migrations ? where do they come from on a deployment ?