Savestate time property causes state to go stale?

Savestate time property causes state to go stale?

wwgraywwgray Posts: 1Questions: 1Answers: 0

I am using the save state and restore state callbacks to save the JSON state object in my database. I am using it to save the ColVis and ColReord info. It works great in the short term, however if I leave for several hours and come back to the app my restored state is ignored by Datatables, even though I am clearly sending the previously saved object. I traced this issue back to the "time" property of the JSON state object. I'm not sure it's purpose, and couldn't find any docs, but Datatables appears to use the time property to view a state as stale after several hours. I was able to work around this by forcing the time value to 9999999999999, however I am curious as to the correct usage of the time property, and if perhaps I am doing something wrong. Thanks in advance!

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 63,683Questions: 1Answers: 10,498 Site admin
    Answer ✓

    The stateDuration controls that option. It is indeed used to ignore state information.

    Allan

This discussion has been closed.