well there's still some sort of web server involved. what is your local setup?

apache have no errors about this inside logs

why is your htaccess file in the public folder renamed with xxx

I mean I understand it's to disable it but why?

becouse i was using it on server directly

I'm sorry but this is all beyond the scope of the support we should be providing here. You have fundamental Laravel requirements that are not met by your environment.

I'm not going to help you figure out htaccess rules. There's a default one in Laravel that works fine but i have no idea about the rest of your apache configuration

that would be happening if you removed the configuration we talked about earlier

because as you can read Glide with the GD driver doesnt decode SVG

hi everyone! I'm trying to create a custom vue module using twill. I have managed to take the form fields from vuex state and send them to an api route through axios in the backend. Is there any way I can be able to access the twill user in that api controller? I already tried auth('twill_users')->user() but it always returns null. Please help.

hi @User, did you register the api route in

admin.php

? did you try with

$user = Auth::guard('twill_users')->user();

?

well I guess the auth helper does the same thing

sorry ifox, you have right. Goodnight all

@User I registered the route through api.php. I'll try again, thanks!

the middleware group used by api.php won't have access to the session

gotcha! thanks so much!

it works! thanks man!

awesome!

Hi again guys. I have another question, what would you guys say is the correct way to pass an error message to a17-textfield? should I just pass an error attribute?

hey @User is this field on a model? If so then you can add validation via the request controller: https://twill.io/docs/crud-modules/form-requests.html#form-requests

hi @User , unfortunately I can't use the normal module flow.. I'm doing it on a custom vue module

Ah I don't really have experience with that. There is an input wrapper component that should handle the errror display but dont know if that would fit for the case.

it's a bit tricky.. maybe I'll just display the error through a modal. But the ideal would be to actually use the error-message in the actual twill component. thanks for the help though

@IanJay you should look into the InputFrame component

you may be able to wrap your field in it and use it to render the error

awesome! thanks for the tip @User

@User . I'm looking at the InputFrame component right now. I can see the error var but I don't see it initialized anywhere?

Is error a global var?

it is part of the mixin

frontend/js/mixins/inputFrame.js