Not sure why i never thought of this before - but obviously AS needs to work for the node/add case - i.e. when a user is editing a new node which has yet to be submitted.
I am not sure if the version 5.1 of this module (prior to 5.2 where we now save forms instead of node revs) took this into account - but it certainly isnt their in the new and improved 5.2 version.
I think approach would be something like on first AS call do a drupal_execute(). The first issue would then be that the current edit session is still about to do a node_add() even though now there is a node already and i suspect that wont go over very well.
If anyone has some insight into how to handle this; please toss in your suggestions. Failing that i will likely come up with something and code this in the next week or so.
Comments
Comment #1
liquidcms commentedmy bad.. it already does do this :)
so i'll set as closed.