https://twill.io logo
Powered by
# ❓questions
  • i
    which field do you want to provide a default for?
  • a
    a select
  • i
    ha I see it's not documented for selects, but it is available, 
    default
    is an option on the 
    formField
    instruction. it takes a value.
  • a
    thanks
  • d
    Sorting Index Column troubleshooting
  • i
  • a
    thanks!!!
  • a
    can i make a block nested?
  • h
    Afaik a block cannot contain another block, but, a block can contain repeaters
  • h
    There is an ongoing effort to have repeaters allow multiple types here: https://github.com/area17/twill/pull/1245
  • i
    correct, at the moment nested blocks are of a single repeater type
  • k
    I'm rendering a browser block by looping through this $posts array, but the order does not seem to be correct. Do I need to order by some sort of key before I get the correct order in the frontend?
    Copy code
    $selected_items_ids = $block->browserIds('posts');
$posts = App\Models\Post::find($selected_items_ids);
  • i
    try 
    $block->getRelated('posts')
    instead
  • k
    That did the trick, thanks!
  • a
    Hi, can't I create lqip with glide?
  • a
    I am getting this error when using php artisan twill:lqip command.
    k
    • 2
    • 3
  • k
    Pretty sure you should be able to
  • k
    LQIP
  • k
    Is there documentation or an example on how to seed a model with blocks using a Seeder? I need to migrate over a pretty substantial amount of Models from a non-twill application to a Twill one.
  • h
    I am not aware of any examples myself, but since blocks are just models I think you can accomplish it by seeding your model and then link a set of blocks. You could look at the blocks table to see how the content json looks like based from some examples you make.
  • h
    Gave it a quick test and this works:
    Copy code
    php
<?php

namespace Database\Seeders;

use App\Models\ScheduledContent;
use Illuminate\Database\Seeder;

class PageSeeder extends Seeder
{
    public function run()
    {
        $page = ScheduledContent::create([
            'title' => 'page title seeded',
            'active' => true,
        ]);

        $page->blocks()->create([
            'editor_name' => 'default',
            'type' => 'example',
            'position' => 1,
            'content' => [
                'text' => ['en' => null],
                'title' => ['en' => 'test title'],
            ],
        ]);
    }
}
  • k
    This would definitely work in my case. Thanks!
  • f
    Hi folks, does anyone have a working example of using S3 and glide together in production? I've followed various bits of advice on here which essentially boiled down to having this in my `.env`:
  • f
    Copy code
    MEDIA_LIBRARY_ENDPOINT_TYPE=s3
MEDIA_LIBRARY_IMAGE_SERVICE=A17\Twill\Services\MediaLibrary\Glide
  • f
    Along with my AWS creds
  • f
    And then in my AppServiceProvider:
  • f
    Copy code
    if (!$this->app->runningInConsole()) {
            $s3 = app(Glide::class)->makeCloudSource('s3');

            config()->set('twill.glide.source', $s3);
            config()->set('twill.glide.cache', $s3);
        }
  • f
    With this in place I have images that save to S3 and glide_cache images are being generated. I'm less sure about whether the glide_cache images are being served though. Basically the first load of any image is pretty slow (2-3 seconds) and subsequent loads are much faster as the image is now in the browsers cache. I'm not able to tell whether that initially slow loading is because the image is being recomputed by glide or if that's just expected slowness as a result of pulling from S3.
  • f
    If the latter, my understanding is that I probably need to use Cloudfront in front of the /img path but that's where my research starts to dry up a bit. I know that this is a little outside the scope of Twill per se but I'd be hugely grateful for any advice on this
  • i
    Hi @User your configuration looks correct. To make sure the performance improvements you're seeing on subsequent requests are not just browser cache, I'd suggest using curl or something like that in the terminal
1...216217218...484Latest