I have some data being sent to cURL through a form. I am getting an error from the server that the cURL data is being sent to, that makes me think the data is not encoded.
For example, if I have a form with an 'email' field, I assume it is url encoded when the form is POSTed, but when it's saved in the DB, it's not url encoded. I assume this means the data from the cURL action is also not encoded. If this is the case, is there anyway to encode it?
i.e. something like:
banana=name
lettuce=email
apple={name}
beetroot=urlencode({email})
Thanks!
For example, if I have a form with an 'email' field, I assume it is url encoded when the form is POSTed, but when it's saved in the DB, it's not url encoded. I assume this means the data from the cURL action is also not encoded. If this is the case, is there anyway to encode it?
i.e. something like:
banana=name
lettuce=email
apple={name}
beetroot=urlencode({email})
Thanks!
Hi grimey,
If you use my cURL [GH] action then the data is urlencoded.
http://greyhead.net/how-to-docs/cfv4-curl-gh-action
Bob
If you use my cURL [GH] action then the data is urlencoded.
http://greyhead.net/how-to-docs/cfv4-curl-gh-action
Bob
Thanks for the info Bob. I am already using your cURL GH (as well as your email GH). The problem must be with the integration with aweber. They don't really support a POST subscription, but there are ways to force it. i.e. http://stackoverflow.com/questions/8304372/aweber-integration-through-curl
However, I am getting an invalid e-mail error when I try it. I was thinking maybe it was due to the data not being urlencoded, but that must not be the case. aweber has an api, but it requires some 2 way communication. Is there anyway to do that in ChronoFroms?
Thanks
However, I am getting an invalid e-mail error when I try it. I was thinking maybe it was due to the data not being urlencoded, but that must not be the case. aweber has an api, but it requires some 2 way communication. Is there anyway to do that in ChronoFroms?
Thanks
Hi grimey,
Add a debugger action to the onSubmit event and you'll see the CURL parameters and can check if they are urlencoded or not. I'm pretty certain that they are encoded by default.
Note with cURL the debugger may give you a **lot** of output including whole web pages so only to be used for development - scroll down far enough and you'll see the values. The latest version shows an array of unurlencoded values so that they look familiar and then the actual values in a single urlencoded value string.
Bob
Add a debugger action to the onSubmit event and you'll see the CURL parameters and can check if they are urlencoded or not. I'm pretty certain that they are encoded by default.
Note with cURL the debugger may give you a **lot** of output including whole web pages so only to be used for development - scroll down far enough and you'll see the values. The latest version shows an array of unurlencoded values so that they look familiar and then the actual values in a single urlencoded value string.
Bob
This topic is locked and no more replies can be posted.