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

    Baymac

    07/23/2021, 12:22 PM
    Hi folks, wondering if you could help me with an issue I am facing with my Twill install. In my local environment, I am seeing the "CMS Users" menu option on the top right, however, in my production environment, this is not appearing. Also on production, when trying to add/edit a user the "role" field has disappeared, even though it is appearing in my local environment. Any thoughts as to why this might be?
  • i

    ifox

    07/23/2021, 12:27 PM
    Hi! it sounds like you're not using a superadmin/admin user on production?
  • b

    Baymac

    07/23/2021, 12:28 PM
    Hey @User! I am, and have checked that the user I am logged into has the superadmin role assigned in the database table 🤔
  • i

    ifox

    07/23/2021, 12:29 PM
    uh, interesting
  • b

    Baymac

    07/23/2021, 12:30 PM
    I also have other users set up as admins and they are seeing the same issue, even though their users in the database table are showing as "admin" too
  • i

    ifox

    07/23/2021, 12:32 PM
    did you implement any custom gates or something like that?
  • b

    Baymac

    07/23/2021, 12:34 PM
    nope nothing like that, just out of the box
  • i

    ifox

    07/23/2021, 12:34 PM
    dang ok
  • i

    ifox

    07/23/2021, 12:35 PM
    which database engine and version are you running? Same question for Laravel and PHP
  • b

    Baymac

    07/23/2021, 12:46 PM
    MySQL 5.7.34, Laravel Framework 5.8.38, PHP 7.4, Twill 2.1.1
  • b

    Baymac

    07/23/2021, 12:49 PM
    This matches what I am running locally too
  • i

    ifox

    07/23/2021, 12:51 PM
    ok great, that's helpful
  • i

    ifox

    07/23/2021, 12:52 PM
    at first i was going to say this might be a L5.8 related issue but since you're not experiencing that locally...
  • b

    Baymac

    07/23/2021, 1:04 PM
    Have just updated to Twill 2.4.0 to see if that could be a cause, but doesn't seem to be the case
  • p

    pboivin

    07/23/2021, 2:42 PM
    @User do you have any kind of caching strategy that could be applied in production only? (just brainstorming...)
  • p

    pboivin

    07/23/2021, 2:44 PM
    special packages like laravel-gate-cache, etc.
  • d

    Defenestrația

    07/24/2021, 12:02 AM
    What am I doing wrong with my crops? How do I get my block editor 'medias' input to use a default crop? I can't seem to figure out how those tie together so I can configure a crop for a particular image field...
  • i

    ifox

    07/24/2021, 12:11 AM
    add the crops configuration to
    twill.block_editor.crops
  • i

    ifox

    07/24/2021, 12:11 AM
    in the same format you would in a model
    $mediasParams
  • d

    Defenestrația

    07/24/2021, 12:14 AM
    I think I'm not naming things correctly...
  • d

    Defenestrația

    07/24/2021, 12:15 AM
    I have an 'events' block, and an 'events_item' repeater
  • d

    Defenestrația

    07/24/2021, 12:15 AM
    In the 'events_item' repeater, I have a 'medias' formField called 'event_item_feature'
  • d

    Defenestrația

    07/24/2021, 12:20 AM
    OHHHHHH, in 'blocks_editor' then 'crops'... Nevermind, thanks that solved it!
  • d

    Defenestrația

    07/24/2021, 12:21 AM
    @User You're killing it man! Thanks for all the support! 🙂
  • j

    jamel

    07/24/2021, 9:07 AM
    Hello everyon ! I was wondering if it is possible to have files input in settings ? I’ve noticed that the setting model and SettingRepository don’t have the HasFile/HandleFiles, but even when i had these two and put the « $fileparams » it still doesn’t save my data on update
  • i

    ifox

    07/24/2021, 9:26 AM
    hi @jamel where did you put the "fileParams"?
  • i

    ifox

    07/24/2021, 9:27 AM
    For settings you need that inside of
    twill.settings.files
  • i

    ifox

    07/24/2021, 9:28 AM
    in the twill config file I mean
  • j

    jamel

    07/24/2021, 10:31 AM
    i also tried that, but it didn’t make any differences
  • i

    ifox

    07/24/2021, 10:48 AM
    my bad. that works for blocks, not for settings. Settings still need to be refactored to be compatible with all fields. In the meantime a regular module would be the alternative.
1...676869...484Latest