I'm developing for a situation where we want users to be able to start a long CCK form, save it in a partially-finished state (using the skip_validate module), log out, and come back hours/days/weeks later to resume their work; the final 'Submit' button will trigger the usual validation and node creation routines.

I've POC'd this workflow with object cache tools functions and it's about 99% perfect, except that objects are bound to the user's session and the user will lose all of their work on logging out... this is probably fine for most cases, but I'm wondering if anyone else would find it useful to be able to associate a cached object with a user ID instead of a session ID.

I'm probably going to throw together a quick custom module to move my own development forward, but I'd be happy to work on a patch for CTools if it would be well received.

Comments

merlinofchaos’s picture

merlinofchaos commented

Binding to a user ID without a session has some issues (in particular it won't work at all for anonymous users filling out forms, which admitteldy is a fairly rare case) so I've shied away from it. That said making it an option might be plausible.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (fixed)

I'm guessing this isn't going to happen at this point.