You are not logged in.
Version 0.3 is now released.
You may now specify a “success_form”. Tags have been provided to output and compare posted values. See plugin help for full details.
Thanks for the reply Manfre.
I’m gonna look into that.
Last edited by velograph (2009-02-11 01:58:29)
I don’t have too much experience working with plugins, so forgive me if this is a dumb question. I’ve been using zem_contact and a few others on my sites with no need to alter/add/change a thing. This is new territory for me.
I was thinking the simplest way of acheiving what I want would be to have an onclick event that sends the user one of two places.
Or would I need to add that into the plugin where the submit button is defined? This seems rather unlikely, but then again, I’m fairly new.
Jason, you can use the newly added success_form. In the success_form, you could use
I would like to redirect the user after the form has been submitted. It appears that I need to use success_form to accomplish this, however, I have attempted virtually every combination of tag syntax and am unable to get it to work under TxP 4.0.8.
The following tag syntax is the only one that does not throw tag errors on page load:
There is one exception. I am required to identify a table. I assume that I am supposed to identify the txp_form table to properly find the form I want to have displayed after the HTML form is submitted. Unfortunately, I get an error stating that “no data was submitted with form”.
<txp:mem_simple_form table="txp_test_users" name="success_form_test_success" />
If I remove the success form tag, it works as expected and properly writes to the database. I think I must have the success_form syntax wrong but every other combination seems to throw a tag error. I have even tried variations using the mem_form tag since there are examples of that in the plugin description and mem_simple_form relies on that plugin to function.
Can someone please post an example of what the complete success tag should look like so that I may correct mine or I can compare to see if I should be looking at some other cause for the failure of my form.
Solved my own problem. Now it seems quite obvious what I did wrong. For others who may have also had problems, here is the solution: I thought the success_form was invoked by using the name attribute as I posted above. The following is an example of the proper way to redirect to a success_form after your mem_simple_form is submitted.
<txp:mem_simple_form table="txp_test_users" id_field="user_id" id_insert="0" success_form="mem_simple_test_success" >
So, I now have this working to take user input, post it to a specific DB table and redirect the user to the downloadable content they are seeking in exchange for their email address.
However, I would like the user to continue to have access to the downloadable content during the remainder of the browser session without the need to re-enter their information to gain access. Even better would be the option to save info to a cookie that would provide users who have already provided their information the ability to access the downloads during subsequent browser sessions.
Does anyone have any recommendations to accomplishing this with mem_simple_form with or without additional plugins or will this kind of feature need to be custom coded?
This looks like what I am looking for but I can’t test it since it seems that his server is not allowing public access for download. Any other sources for chs_cookie download?