brow42 Lv 1
I've had trouble with this as a new scripter, but not recently, so I think I'm doing it correctly now. Basically:
Save (and re-share) = bug fix, which updates the original web page (you can change the name). This works pretty reliably for me now.
Save As (and share) = child recipe with a new web page. Haven't tried to do this for a while, though.
Also, I had deleted a shared recipe that I wrote, then downloaded it, and it had no 'shared' status, so I thought I couldn't edit it….but eventually I tried anyways and it let me apply a bug fix to the existing recipe, without making a child.
So, I think it's working…it's just easy to make mistakes. Also, it seems to auto-unshare when you save a change, which is confusing to new coders. I guess it's to remind you to upload your new version. But easy to forget to do so, until somebody tells you that they can't find your script anymore.
Worst cookbook problem I've had is when editing with multiple clients that have been open for days, and losing a script.
