https://twill.io logo
Powered by
# ❓questions
  • i
    Copy code
    public $mediasParams = [
        'project' => [
            'flex' => [
                [
                    'name' => 'free',
                    'ratio' => 0,
                ]
            ],
        ]
    ];
  • u
    i'm retarted.. geez
  • u
    thanks..
  • c
    I have a question around slugs/slugAttributes. I have an Events module, and i know there will be title collisions, so I need slug suffixes. What I was hoping to be able to do would be to use the event date as the suffix. So first event with slug 
    my-event
    , if there is a collison beyond that, use 
    my-event-{d-m-Y}
    .
  • c
    My firsta ssumptionm was to use the $slugAttributes array but as per this (https://github.com/area17/twill/discussions/860) discussion thread, thats not what $slugAttributes appears to do. (What does it do?)
  • c
    As I won't always have the date at the point of slug creation (events can be created manually and programatically). I have overridden 
    getSuffixSlug
    from the 
    HasSlug
    trait in my Model:
  • c
    Copy code
    protected function getSuffixSlug()
    {
        return $this->startsAt ? $this->starts_at->format('d-m-Y') : $this->id;
    }
  • c
    This, I think would work, except for the 
    $nb_variation_slug
    private property, which seems to use a simple incrementor suffix until it reaches that value, then fall back to getSuffixSlug.
  • c
    Any way to work around this? Or am I going about this totally the wrong way?
  • p
    Hi @User, I think you're on the right path. I'm curious to know if you have experimented with overriding 
    suffixSlugIfExisting()
    in your model? (it's technically private but should work since 
    HasSlugs
    is a trait and not a base class). I haven't tested but I think this line can be adapted to skip the check on 
    nb_variation_slug
    and proceed directly with `getSuffixSlug()`: https://github.com/area17/twill/blob/2.x/src/Models/Behaviors/HasSlug.php#L223 Does this make sense?
  • c
    yeah, this is what I've got so far:
  • c
    Copy code
    private function suffixSlugIfExisting($slugParams)
    {
        $slugBackup = $slugParams['slug'];
        $table = $this->getSlugsTable();

        unset($slugParams['active']);

        $qCheck = DB::table($table);
        $qCheck->whereNull($this->getDeletedAtColumn());
        foreach ($slugParams as $key => $value) {
            $qCheck->where($key, '=', $value);
        }

        if ($qCheck->first() != null) {
            if (!empty($slugParams['slug'])) {
                $slugParams['slug'] = $slugBackup."-".$this->getSuffixSlug();
            }
        }

        return $slugParams['slug'];
    }

    protected function getSuffixSlug()
    {
        return $this->startsAt ? $this->starts_at->format('d-m-Y') : $this->id;
    }
  • p
    Looks good! So this gives you a first version of the slug untouched (eg. 
    lorem-ipsum
    ), then suffix every duplicate with the item's ID (or date)... Did you run into any issues when updating existing slugs?
  • c
    and in posting that spotted the bug/typo that was stopping the start date working
  • c
    Yeah, this gives the first instance the raw slug 
    my-event
    , then if a second is created manually in the ui it would give it 
    my-event-{$id}
    (as the starts_at date wouldn't be set). but if created programatically (when all the data is present) would give 
    my-event-{d-m-Y}
  • c
    need to test on updating exsiting slugs
  • c
    Seems to all be working... updating a suffixed the slug to something unique worked - ended up with a unique slug
  • c
    and then if I altered it back to a collision, it correctly suffixed it with the date
  • p
    Nice! This is a cool use case and I think 
    HasSlugs
    could be refactored to make it a bit more obvious what needs to be adapted for custom slug suffixes...
  • c
    yeah, its definitely not the most obvious. Can you shed any light on what $slugAttributes actually does? It seems to add columns on to the query for the slug table....
  • i
    @chrispymm this is so that the slug can be duplicated as long as it has different dependencies. that would be for something where the routing on the frontend depends on a relationship for example
  • i
    say you have event categories and your event detail pages are rendered under /category-slug/event-slug. In that case if you want the same slug across multiple categories, you'd put the category_id column in slug attributes
  • c
    Ah ok, thanks for the explanation 👍
  • i
    Greetings. Please help me connect the capsule model to the backets. I get this error now
  • i
    I tried to use this documentation item, but I disabled the display of all content blocks
  • i
    This approach helped me
  • p
    Hi, is there a way to safely remove a module? If not, is there a way to remove media support from a module? I have created a module with the wrong parameters and I don't need medias support. Anyway, I want to know how to remove a module for the future.
  • p
    Hi @User, I think the absolute minimum to disable a module would be to remove it from 
    routes/admin.php
    and 
    twill-navigation.php
    . From there, you can be sure that users can't interact with it. Then, you can remove all the associated views and classes (model, controller, repository, etc.)
  • i
    Hi @pazunino! a module consists of a controller, form request class, repository, model classes, a form view and of course the registration of the routing in admin.php and twill-navigation.php. there are no automated way to remove those things currently. Capsules are modules self contained in a single folder, so they do have that benefit to remove in a single step.
  • i
    ha @pboivin beat me to it
1...165166167...484Latest