Closed nilesjohnson closed 2 months ago
Not sure if you already figured this out, but if you debug
on the Controller then it interferes with the Request/Response objects, and the cookie won't write.
Lol, no I didn't know about the debug issue. After more fiddling, I figured out that the problem was the 'domain' entry, pulled from config. Removing that made the cookie work. Could be it failed silently because the domains didn't match; whatever, leaving that out is fine.
There are two remaining issues, both of which could be optional.
[domain]/conferences/curator_cookie
; it just redirects to the index. But if I go to [domain]/conferences/curator_cookie/anyargument
, then that works. Maybe this is some conflict with the tags? As a lame workaround, I could just tell people to use a url with some extra item, like [domain]/conferences/curator_cookie/set
or something. I guess this could go in a separate controller but, is that worth the trouble?Ok, I think we can call this one good enough!
I don't know why I had url problems before, but it's working fine for me now too.
I made a simple controller and view, following these instructions but it's very broken :/