there's no way for line 169 to execute if that variable is not true

ok

what i will do is amend the .env to false so its verbosely set

one thing I'm curious about is why you are building Twill on the server. You can push the Twill build to your git repository. It doesn't change unless you're updating Twill so unless you make sure that the server is using exactly the same node version you can't guarantee that the build is going to be the same as your local. You also don't need to build at all if you're not using custom Vue components.

php artisan twill:update

is sufficient to get the new build in that case.

ok that makes sense, So if i have managed to get this working locally and deploy to git and then deploy through git actions to our server we wont need to rebuild at all

exactly

however we have chnaged the version from 2.6 to 2.12.4 due to updating to laravel 9

which is a large jump

it's a large jump but not on a major version so there shouldn't be anything breaking as long as you run artisan twill:update after composer update

ok

thank you for your help

i will get dev to try this out and come back inf any other questions

hi @ifox we are still now getting this error after checking the files mentioned before all files match and we have this working locally on our own machines with no errors. on the cms front end we see this error in the console and also this on the page.

Config cached?

ill try and clear it

could be views cache too. I'd just go for a optimize:clear

hi both, i have tried cache and views and optimize clear and all cleared but still the same issue

no issues with the exact setup on local machine but on server its not liking it

I managed to find the issue. There is one file being modified outside of the main layouts and a line of code is missing for the publishDateDisplayFormat in the amended file but exists in the vendor. I have now added the code that was missing and this is now working. Thanks @ifox and @Harings Rob for your help

@ifox is it possible to change the layout of the form fields in edit view? like 50/50 or tabs?

@EpicKau yes you can use columns. Are you on Twill 2 or 3?

3

thanks

hmm am I doing it wrong? The fields don't get value / updated and in preview I receive

this.editor.setContent is not a function

you have duplicate field names

I guess you want to remove the ones outside the columns as they are the same?

only for testing, same result without the bottom ones

alright. and they work fine outside of columns?

is this in a block or module controller?