https://twill.io logo
Join Discord
Powered by
# ❓questions
  • i

    ifox

    09/02/2022, 8:12 AM
    well I'm not going to do anything with this, this is your build. I'm asking you to compare with what your browser is loading
  • i

    ifox

    09/02/2022, 8:14 AM
    main-free.94ff6746.js especially
  • i

    ifox

    09/02/2022, 8:14 AM
    if you view source or check the network tab, do you see the exact same filename?
  • o

    onepiece

    09/02/2022, 8:15 AM
    yep
  • i

    ifox

    09/02/2022, 8:16 AM
    ok, now if you grep that file, do you find app-leads?
  • i

    ifox

    09/02/2022, 8:17 AM
    why is your Vue file named Leads but you use app-leads in the markup? Is the component exporting a different name?
  • o

    onepiece

    09/02/2022, 8:18 AM
    if i delete it from manifest.json??
  • i

    ifox

    09/02/2022, 8:18 AM
    what? Where did I say delete anything?
  • i

    ifox

    09/02/2022, 8:19 AM
    grep = search
  • i

    ifox

    09/02/2022, 8:19 AM
    as in, search inside the js file if you see the compiled code of your custom component
  • h

    Harings Rob

    09/02/2022, 8:20 AM
    I just did a quick test on 2.x Added a file test.vue with simple content in resources/assets/js/components Run artisan twill:build Add to a form Displays correctly in the body of the form.
  • h

    Harings Rob

    09/02/2022, 8:21 AM
    If the file shows up in
    vendor/area17/twill/frontend/js/components/customs
    then you should be able to refer it by it's filename prefixed with a17. HelloWorld becomes a17-hello-world as it is explained in https://twill.io/docs/guides/creating_custom_components_form_fields_and_blocks.html#part-1-setup-twill-for-development
  • h

    Harings Rob

    09/02/2022, 8:22 AM
    if your custom component is not in that vender folder above, something else is going on and it might be a windows issue.
  • h

    Harings Rob

    09/02/2022, 8:23 AM
    @Sami I added a fix here that you can try out https://github.com/area17/twill/pull/1797
  • o

    onepiece

    09/02/2022, 8:43 AM
    I did everything as you said. But the component does not appear in local/area17/twill/frontend/js/components/customs. And yes I am using windows
  • i

    ifox

    09/02/2022, 8:44 AM
    local/ ? Do you mean vendor/ ?
  • o

    onepiece

    09/02/2022, 8:44 AM
    yep
  • o

    onepiece

    09/02/2022, 8:44 AM
    sorry
  • i

    ifox

    09/02/2022, 8:45 AM
    that means the copy step of the build is not working on your machine. You can manually copy them before running the build
  • o

    onepiece

    09/02/2022, 8:46 AM
    Ok, I'll try
  • s

    Sami

    09/02/2022, 11:35 AM
    Applied patch and it works! Thanks!
  • s

    Sami

    09/02/2022, 11:45 AM
    forgot to answer - yes, that was the case
  • b

    bmau

    09/02/2022, 2:49 PM
    Hi guys, quick question. I'm trying to move the admin assets to a different location so I have added this to config/twill.php
    Copy code
    'public_directory' => 'assets/cms/admin',
  • b

    bmau

    09/02/2022, 2:50 PM
    But for some reason twill will still use
    assets/admin
    when I run php artisan twill:build. What am I missing?
  • j

    JeremyStewart

    09/04/2022, 4:20 AM
    Hi Guys, I'm desperate to test out TwillCMS however my local installation is driving me nuts! Admittedly the process is a little out of my comfort zone 😆 I thought it might be 'easiest' to use mamp. I have managed to get through 99% of the process however trying to access the admin via the browser (on my local with http://twill-cms.test/admin) I am getting the following error " Warning: opendir(/Users/username/code): failed to open dir: No such file or directory in /Users/username/.composer/vendor/laravel/valet/server.php on line 132 404 - Not Found"
  • b

    bmau

    09/05/2022, 8:43 AM
    Are you running on mac? Have you try to install valet through composer globally?
  • j

    JeremyStewart

    09/05/2022, 9:06 AM
    Hi Mate, yep also trying with Valet but just having so many issues getting that up and running on my mac 🥺 just running into so many command line errors!
  • i

    ifox

    09/05/2022, 9:12 AM
    Hi @JeremyStewart, I think you should try to run a Laravel project on your Mac before trying Twill, to avoid mixing up steps and errors. Are you following the Laravel docs? Let's go step by step: 1. Is PHP installed correctly? confirm that with
    php -v
    2. Is composer installed correctly? confirm that with
    composer -v
  • j

    JeremyStewart

    09/05/2022, 9:13 AM
    Hi ifox it appears PHP 8.1.10 is installed after running php -v I got "PHP 8.1.10 (cli) (built: Sep 1 2022 15:40:39) (NTS) Copyright (c) The PHP Group Zend Engine v4.1.10, Copyright (c) Zend Technologies with Zend OPcache v8.1.10, Copyright (c), by Zend Technologies"
  • i

    ifox

    09/05/2022, 9:13 AM
    ok good!
1...383384385...484Latest