HeadHodge
Active member
I'm creating an add-on that contains information I would like to persist between multiple pages from the users web browser.
I've been studying the cookies that xenforo uses for statefulness and I'm confused. When at I look at a submit form, it uses _xftoken, in the header cookie there is also xf_session, and when searches are performed there is a searchid that is used to page through search results.
So for my data, what is the recommended way to persist data across multiple pages?
I've successfully used in my controller the Xenforo_Session "get session" function, the "set session key" function, and the "save session" function across multiple pages. But I'm not sure if that's the way to go because I don't understand the other cookies being passed from the browser to the controller. Especially the _xftoken.
I've been studying the cookies that xenforo uses for statefulness and I'm confused. When at I look at a submit form, it uses _xftoken, in the header cookie there is also xf_session, and when searches are performed there is a searchid that is used to page through search results.
So for my data, what is the recommended way to persist data across multiple pages?
I've successfully used in my controller the Xenforo_Session "get session" function, the "set session key" function, and the "save session" function across multiple pages. But I'm not sure if that's the way to go because I don't understand the other cookies being passed from the browser to the controller. Especially the _xftoken.