https://twill.io logo
Powered by
# ❓questions
  • u
    i nothing change in vendor or admin assets
  • p
    The bug in your video above, with the sticky sidebar. Does this happen on all admin pages of just for one specific module?
  • u
    when i remove position absolute from sidebar it is working well
  • u
    on all
  • u
    ".sticky__fixedBottom" <- fixed, ".sticky__abs" <- abosolute
  • u
    this class is active when i scroll
  • p
    Ok. What if you remove the 2 fieldsets from the sidebar temporarily. Do you still have the same bug?
  • u
    no
  • p
    Yeah ok. I think you found a bug with the sidebar...
  • u
    so.. i need to modify css from twill?
  • p
    Yes, just a sec, I think I have a workaround fo you
  • u
    Copy code
    @section('sideFieldsets')

     <a17-fieldset id="preview-img" title="thumb" :open="true">

        @formField('medias', [

            'name' => 'cover',

            'label' => ''

        ])

  </a17-fieldset>


    @endsection
  • u
    this is this fieldset
  • p
    Add this to your 
    form.blade.php
    :
    Copy code
    @push('extra_css')
<style>
    .wrapper .publisher {
        position: initial !important;
    }
</style>
@endpush
  • u
    at end?
  • p
    Sure
  • u
    huh, its working
  • u
    it isnt fixed on top but everything is working well
  • p
    Yes, you loose the sticky but it's better than the bug 🙂
  • u
    Yep, there is option to add it to all formblade? something like twill.php ?
  • p
    Yes, you can create your own 
    form
    layout
  • p
    Add file 
    resources/views/admin/layouts/form.blade.php
    :
    Copy code
    @extends('twill::layouts.form')

@push('extra_css')
<style>
    .wrapper .publisher {
        position: initial !important;
    }
</style>
@endpush
  • p
    Then use this in your module's 
    form.blade.php
    :
  • p
    @extends('admin.layouts.form')
  • l
    How can I get translated input item in frontend ?
    p
    h
    • 3
    • 20
  • m
    Thanks for the answer. I did make some progress in the end - by doing both 
    php artisan vendor:publish --provider="A17\Twill\TwillServiceProvider" --tag="views"
    and 
    php artisan view:cache
    when the container starts up. Now I run into 
    View [partials.form._] not found. (View: /var/www/html/resources/views/vendor/twill/partials/form/utils/_blocks_templates.blade.php)
    - so same error, but only when displaying a form that has blocks. Here's a very simple example of a form that fails :
    Copy code
    @extends('twill::layouts.form')

@section('contentFields')
    @formField('input', [
        'name' => 'description',
        'label' => 'Description',
        'type'  => 'text'
    ])

    @formField('block_editor', [
        'carousel_custom',
        'image',
        'image_full_width',
        'text',
        'video',
        'quote_custom',
        'list',
        'code',
    ])
@stop
    In terms of difference of env, we have something live build on an apache image, that works fine in all aspect. For performance we wanted to move to nginx and php-fpm, based on 7.4-fpm-alpine, so I think it might be related - because it is the only difference. The buiild itself is pretty straightforward - pull the image, install librairies, copy repository, manage files permission access (could something happen here?), switch user, run artisan commands to cache views/config/routes, start nginx and fpm. I think now I'm going to try to good old 'twill:blocks' command (I'm running 2.1.1 so it might be worth upgrading to 2.5 to see if things have changed as well)
  • i
    @MedvedOurs I'm sorry you're facing this issue but want to clarify 2 things: - you should not publish twill views if you do not intend to modify them. If you do, you need to keep them up to date with each Twill update. I recommend only publishing individual views as needed to avoid the maintenance burden on your side. @pboivin asked this to know if you had done it in the past to understand if you may have outdated Twill views - twill:blocks generates Vue files which are not needed on Twill 2 since the blade files are now dynamically rendered to Vue inline template tags
  • i
    can you share your 
    twill.block_editor
    config?
  • m
    Right. Clearly, publishing the view was an attempt at fixing a problem I do not fully understand 😄 I never had to do it before - and would rather not. But thanks for the clarification, it is helpful. As for the blocks command, it is indeed something I haven't used since Twill 2, but in a desperate try... it did not make any difference, obviously!
  • d
    Hi, any idea why crop button gives such errors when pressed?
1...111112113...484Latest