So I need to add a field to the database?

However, it saves the title and the URL, just not the media fields..

You need a table actually, see https://twill.io/docs/form-fields/repeater.html#using-repeater-fields

Repeaters saved in a JSON column won't save medias fields. you'll to setup a module for the repeated items and setup a hasMany relationship for it as documented

Ok

Hi i upgraded to twill 3 🙂 My singletons stopped working: Route [twill.home] not defined. (View: /var/www/html/vendor/area17/twill/views/partials/navigation/_secondary_navigation.blade.php) (View: /var/www/html/vendor/area17/twill/views/partials/navigation/_secondary_navigation.blade.php) (View: /var/www/html/vendor/area17/twill/views/partials/navigation/_secondary_navigation.blade.php)

The problem only seems to exist when a singleton is nested

Any suggestions?

You should be using the TwillRoute facade to register those in Twill 3. Laravel implemented a singleton macro on the framework router so we can't use that anymore. We have twillSingleton now on Twill 2 because of that...

I am just getting started with Twill and installed 3.x for a new project. I am following along with the video tutorials to get familiar. Created a simple module with a couple of fields. Added it to the admin nav and created my first record. However when I click the record to edit I get the error

Unable to create a directory at /var/app/current/mfa-twill/app/View/Components/Twill/Blocks.

I'm running on a local server in my lab ubuntu/nginx/mysql . I have checked and triple checked the permissions on the folder, nginx ect. Have even set the folder to

777

but can't seem to work around it. Feel like I'm missing something required for 3.x that is maybe not documented? Any suggestions?

Hi @kerkness welcome! I wouldn't recommend the videos as a reference to start with Twill 3 as they are a bit old now. Make sure you use https://twill.io/docs/3.x or GitHub for the latest documentation. We're going to update the website and docs site soon to avoid any confusion.

that folder shouldn't be required unless you are using the new block component classes, so if you aren't, this might be a regression in the last RC

I'm not reproducing in a project without that folder though so I'm not sure why you're getting this yet

Thanks for the info. I created the module using cli option and did say "yes" to using blocks and pretty much all options as I'm experimenting. I'll wipe and try fresh with just the basics and refer to the 3.x docs.

Ah yes thx!

@kerkness do you still have the Unable to create a directory at error?

It does save the media’s field but it does not keep its media data if you resave the page in the backend.. I don’t think I fully understand how it works.. Do I have to create a whole new model just to save an entry of a media’s field..?

yes you do. You need to think about the repeated rows as a full blown twill module (eg if you need translated fields, a module with HasTranslations, if you need media fields, a module with HasMedias and $mediasParams configured). In your case you would create a Video module which corresponds to TeamMember in the documentation

All this just to save a medias field..? It does save all the text values without a problem..

Yes because text values are fine to save in a JSON column, but not a polymorphic relationship storing crops and such

Haha ok 😅

Yeah so I am still getting this. I wiped and started fresh. Created a laravel project with

composer create-project laravel/laravel mfa-twill

Added Twill with

composer require area17/twill:3.x-dev
php artisan twill:install
php artisan storage:link

Then logged into admin console and tried to access my profile at

https://content.crid.ca/admin/users/1/edit

and get

Unable to create a directory at /var/app/current/mfa-twill/app/View/Components/Twill/Blocks. (View: /var/app/current/mfa-twill/vendor/area17/twill/views/layouts/form.blade.php) (View: /var/app/current/mfa-twill/vendor/area17/twill/views/layouts/form.blade.php)

The only thing I can think of is that I create the project as a sudoer user and not as

www-data

which is the nginx user. However that isn't an issue with any of my other laravel projects. Changing user:group of folders and paths doesn't seem to resolve the issue anyway.

strange.. Can you make an issue on github for this? I can check it later, may be a bug I introduced.

YUp. indeed. SHould I try a different branch/tag besides

3.x-dev

?

oh. I guess. I'll try

3.0.0-rc3

Interesting. Same error with

3.0.0-rc3

. I will create an issue and also try rc2

It is trying to load the blocks from that directory, but I may just have missed a check to see if the directory even exists

I created an issue. I was able to work around the error by setting both

app

folder and

vendor

folder to

777

permissions. Error goes away. Reverting the permissions back to

775

and the error DOES NOT return. So possibly just exists first load of the form

Will try and create a module now with normal permissions

Issue does not return after creating a basic module