Dec 24th, 2009, 10:59 AM
I had to mull this one over a bit - neat scenario!
I think what may be happening is this: the Submission Pre-Parser module uses a hook in the ft_update_submission function to process your code at the right spot. Since you're calling that function within the Pre-Parser it's getting confused somehow. At first I thought you'd get a infinite loop, but if you're updating a different form it shouldn't do that.
I think you may be stuck manually updating the submission via an SQL query rather than with using the ft_update_submission function. Crappy, I know.
Other solutions.... hmm. What we really need is a "form mapping" module or something like that, that on a meta-data level creates foreign key relationships between tables and lets you map data in one form to another. But that's a pretty whopping job. Probably your best bet is to continue with the Submission Pre-Parser for now, or possible creating a custom module to do the same thing.
Sorry I don't have any great ideas.
- Ben
I think what may be happening is this: the Submission Pre-Parser module uses a hook in the ft_update_submission function to process your code at the right spot. Since you're calling that function within the Pre-Parser it's getting confused somehow. At first I thought you'd get a infinite loop, but if you're updating a different form it shouldn't do that.
I think you may be stuck manually updating the submission via an SQL query rather than with using the ft_update_submission function. Crappy, I know.
Other solutions.... hmm. What we really need is a "form mapping" module or something like that, that on a meta-data level creates foreign key relationships between tables and lets you map data in one form to another. But that's a pretty whopping job. Probably your best bet is to continue with the Submission Pre-Parser for now, or possible creating a custom module to do the same thing.
Sorry I don't have any great ideas.
- Ben