https://twill.io logo
Powered by
# ❓questions
  • f
    Thanks for the quick reply! So basically I'd create my own helper with the same name and then perform a conditional check for the environment. If local use the twill version and if not local then use the Laravel asset helper?
  • p
    Yes, I think this could work
  • f
    OK cool - I'll give that a whirl and see where I end up. Appreciate the help!
  • z
    Hi there. I would like to create a custom form field, are there any resources out there on how I can achieve this?
  • z
    I found this while searching through various places. Haven't checked it out yet, but the title sounds promising. 😄
  • p
    Hi @User, yes I think this guide is the most up to date resource. It's not super deep but it should get you going with the 
    twill:*
    commands and a basic example of custom form field.
  • z
    Alright, thanks for the info. 👍
  • z
    If I have any questions, I'll just post them here.
  • p
    Sure, don't hesitate! Especially if you see parts of the tutorial that could be clarified.
  • b
    Hello guys! I have an problem. If my page in twill has about 5-7 blocks and 20-24 languages when Im trying to save it, then my browser tab is just stuck and I have to click on button "continue waiting" and then it's successfully saved. Is there any solution to avoid that tab stuck?
  • i
    Hey @BA7YA that's a lot of languages! We did 32 in the past without running into this though. Are your blocks very complex somehow?
  • i
    this is basically Vue struggling to compute the payload to send to the backend. It'd be interesting to reproduce for us to see what needs to be optimized in that area.
  • b
    @User Thanks for fast reply. Mostly of blocks has repeaters (usually about 3-4) . Maybe this is the reason of my problem
  • i
    i think so, but that should be something we can optimize for. Would you mind sharing the blocks blade files themselves, so we can try with your configuration.
  • b
    @User Sent to you templates
  • f
    Thanks again for the help yesterday @User - I got the admin panel assets working on Vapor using a custom helpers as advised:
  • f
    Copy code
    use A17\Twill\Services\Assets\Twill as TwillAssets;

if (!function_exists('twillAsset')) {
    /**
     * @param string $file
     * @return string
     */
    function twillAsset($file)
    {
        if(App::environment('local')){
            return app(TwillAssets::class)->asset($file);
        }

        return asset(app(TwillAssets::class)->asset($file));
    }
}
  • f
    Hope that's of help to anyone else who comes across the same issue.
  • a
    Hello, I have made some translations. But they do not work on the server. They are in English on the server.
  • a
    This is on the server.
  • a
    This is on localhost.
  • a
    Is there any way I can force the language change on these?
  • a
    Also locale in twill.php is already set to 'it'.
  • p
    @User, check your user's 
    Settings
    page, is it possible that you set the language to English?
  • a
    Looks like yes, how do I disable the selection to empty?
  • a
    Or unset it.
  • p
    It's the 
    language
    column on the 
    twill_users
    table. You can set this to 
    NULL
    to unset the language preference for a specific user.
  • p
    You can change the available languages in the config : https://github.com/area17/twill/blob/2.x/config/twill.php#L199
  • a
    funy thing is I tried your last solution by settings English on my localhost first. Now also the localhost went to english. Even after changing the language to 'it' in the twill_users table, it stayed in english.
  • a
    Ok, I was able to fix it. But I think I got only one button left to translate.
1...195196197...484Latest