everone.bsky.social
Just a regular guy. Micah 6:8.
38 posts
194 followers
262 following
Prolific Poster
Conversation Starter
comment in response to
post
That's the way my grandmother likes it. Just a little bit.
comment in response to
post
Hey, thanks for following up. It didn't work. 😅
Cleared all cache, re-did db, only file driver works. And I'm still puzzled why that's the case.
comment in response to
post
Yeah, changed it back to database and the issue returned. I'm gonna try to do a database refresh later today and see if that resolves the issue.
comment in response to
post
On form submit, but we found what the issue is. Seems something is wrong with the sessions table. Changed to session driver to file and I no longer had issues.
bsky.app/profile/ever...
comment in response to
post
Yeah, I'm using sqlite and I'm seeing the session table right now. But there are 9 sessions sitting though. I'm wondering if there is some sort of limitation there.
comment in response to
post
Changed the session driver*
comment in response to
post
OMG, I changed it from database to file, and now it's working???? Huh??
comment in response to
post
yeah, the token shows up in the request, but not the response. Checking out the doc now.
comment in response to
post
Running Inertia with React. Started from a Laravel Breeze Starter kit and making changes as I go. Using PHP 8.3.13 and Node v20.14.0.
comment in response to
post
🔥🔥
So I'm using useForm's post from Inertia. (using Inertia with React)
Session driver is set to database. Didn't change much from starter kit for those configs.
Link to the login form: pastebin.com/S11XEjgk
comment in response to
post
I'll check this out today and see if anything in here works.
comment in response to
post
Yeah, I have been reading this for a while now, the only thing that helps is excluding the urls in VerifyCsrfToken. But I don't see why I need to do that for the login and sign pages.
comment in response to
post
From the reading I've been doing, it related to the CSRF issues. The only thing that seems to help is excluding the urls in VerifyCsrfToken. But I don't see why I need to do that for the login and sign pages. And those are the only places it's happening it seems.
comment in response to
post
Ohhh, interesting. I'll check it out and see. If not, I guess waiting a bit longer won't be too bad.
comment in response to
post
lol, I think it's been 2 weeks already? But hopefully I get some soon to get some folks on here.
comment in response to
post
Facts.
comment in response to
post
Thanks @sarahbrynm.bsky.social
comment in response to
post
Thanks @tempsthoughts.bsky.social
comment in response to
post
Thanks @pariss.blacktechpipeline.com 😌