New eForm version (1.4) - ready for testing

It is, Ryan; names were changed to protect the innocent.

I figured , but I’m wondering why we don’t make this a stock part of the codebase. There’s clearly a use for it, and it could be made optional.

Ah, I see what you mean. No, I hard-coded a loop for the specific customization. But you are correct, it could be done that way easily enough. Or even use a chunk or TV in the snippet option for the list might be better.

Quote from: rthrash at Oct 17, 2006, 01:17 AM

I figured , but I’m wondering why we don’t make this a stock part of the codebase. There’s clearly a use for it, and it could be made optional.

Just popping in at the right moment Yeah, I totally agree.. I’m just about to have my testing session... I will add something like this to the code.

What should happen if you have $_SESSION and $_POST var with the same name you think? Which should take precedence?

I’d tend to put the priority as an additional parameter, or even better, pull the prefix the placeholder with ’sn’ like [+snMyPlaceholder+] to mean explicitly pull the one from the session and [+MyPlacehoder+] to get the one from the POST (in the event there were two)... just a thought... I don’t know really! lol

I like that idea, Ryan, although in my case I have custom values stored in the session, in a sub-array, and the code loops through the sub-array. So it would be a little complicated, needing logic to know to loop if the value given is itself an array. Interesting.

I’m not sure about the security implications of using session variables inside a form but I would say that session variables should take precedence over post variables.

Quote from: xwisdom at Oct 17, 2006, 09:22 AM

I’m not sure about the security implications of using session variables inside a form but I would say that session variables should take precedence over post variables.

Yes, you’re right and you would only hope that people would consider those implications before using it (and properly validate vales) but I can see great advantages in being able to transport values from one form to another for instance.

I’ve added it in to the final 1.4 version which I’ll be uploading to the repository tomorrow. I’ve made session vars to take precedence unless set otherwise by (yet another) parameter

I’ve added the final 1.4 version to the repository.

For a list of all changes see the repository or in the support topic.

maybe add email as tag i search for email in repository but it did not come up