spatie/laravel-activitylog 4.7

is installed

Oke i downgraded to 3.17 because php 7.4 and 4.7 need 8^ i got a new error instead 😛 Error retrieving credentials from the instance profile metadata service. (cURL error 28: Connection timed out after 1001 milliseconds (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://169.254.169.254/latest/meta-data/iam/security-credentials/) (View: /home/bkcmediaeu/domains/bkcmedia.eu/4000_byondis_website/vendor/area17/twill/views/layouts/dashboard.blade.php)

@jefsev Same issue I think.

got it 😛

yes that was it.

https://twill.io/docs/3.x/ At installation it still says composer require area17/twill:"^2.0", even on /3.x/ docs.

yes we are working on those updates

Oke it's not my day 😛 Now i do get in twill admin but nothing comes up. I added a module news, alle files are created like controller, model, view/admin. I migrated, added everything in admin routes and twill config. I get a blank page, media library is not opening and my module shows an empty page.

Any idead?

sounds like a js error, check the console

no errors, also non in the network tab.

hmm, did you run

php artisan twill:update

after changing from v2 to v3?

Im still on v2

😛

Ok!

Content Security Policy of your site blocks the use of 'eval' in JavaScript` The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site. To solve this issue, avoid using eval(), new Function(), setTimeout([string], ...) and setInterval([string], ...) for evaluating strings. If you absolutely must: you can enable string evaluation by adding unsafe-eval as an allowed source in a script-src directive. ⚠️ Allowing string evaluation comes at the risk of inline script injection. 1 directive Source Location Directive Status chunk-vendors.3abec3c2.js:36 script-src blocked Learn more: Content Security Policy - Eval

that's all i get

oh I see

no console errors or anything in the network tab

very strange

there's an open issue for that. Your have a local CSP preventing inline js and eval calls

are you on a corporate network or something?

I am. But the weird thing is that i have build more sites using twill whilst working here and did not have any issues. Other sites are fine. I do see the other sites are using Version 2.9.1 And this one is 2.12.4 Do you think that makes any difference?

not that I'm aware of, especially since the issue has been reported for much older than 2.9. Could the CSP have changed recently? I think we should address it in any case as CSPs are becoming more standard everywhere

found something else 😛 - league/glide 2.0.x-dev requires php ^5.4 | ^7.0 -> your php version (8.1.12) does not satisfy that requirement. - league/glide-laravel 1.0.0 requires league/glide-symfony ^1.0 -> satisfiable by league/glide-symfony[1.1.0]. - area17/twill 2.12.4 requires league/glide-laravel ^1.0 -> satisfiable by league/glide-laravel[1.0.0]. - league/glide-symfony 1.1.0 requires league/glide ^2.0 -> satisfiable by league/glide[2.0.x-dev]. - area17/twill is locked to version 2.12.4 and an update of this package was not requested.

But to be clear the CSP is blocking the views in de admin dashboard?

It's blocking loading Twill's javascript build