[SOLVED] Redirect on registration

Thanks. But the [post_HIDDEN_INPUT_NAME] gives "http%3A%2F%2Flocalhost%2Fkiwi%2Fde%2Flisting.html" which gives a 404. Setting "Format Functions" to yes does not help. Using [cb:userfield field="post_HIDDEN_INPUT_NAME" /] does not work either.

Ensure CB Auto Actions is up to date. Some actions were urlencoding the entire URL string when the URL was a single substitution.

I did not know I had to use url encoding.

The redirect now works on login. But when I add the onAfterSaveUserRegistration trigger the redirect goes to http://localhost/[post_HIDDEN_INPUT_NAME]. why does the trigger even matter on how the url gets handled?

That's not going to work because your string will URL encode. You need to specify strictly your URL as the substitution. Example as follows.

URL: [post_returnurl]

why does the trigger even matter on how the url gets handled?

It doesn't. That's just the appropriate trigger to be using as it's fired after all frontend registration processes have completed and is just before the registration complete message.

I dont know what that means: "That's not going to work because your string will URL encode. You need to specify strictly your URL as the substitution. Example as follows. URL: [post_returnurl]"
As I said earlier: "But the [post_HIDDEN_INPUT_NAME] gives "http%3A%2F%2Flocalhost%2Fkiwi%2Fde%2Flisting.html" which gives a 404." I updated CB today again, does not help. So for me it is impossible to figure out what that field actually requieres to get it to work.

Again, the trigger onAfterLogin puts out the correct URL, the trigger onAfterSaveUserRegistration puts out http://localhost/[post_HIDDEN_INPUT_NAME]. Again, why does the trigger matters on the output?

Can you please switch that off. It is really enoying when you edit your posts:
"Flood protection! Please wait 240 seconds before submitting an another message."

That's because it's being URL encoded. You need to ensure you've the latest CB Auto Actions release, which won't URL encode it. If it's still URL encoded then it is being encoded before it is sent to CB Auto Actions and in that case you should base64 encode the hidden value then base64 decode it using format functions in CB Auto Actions. That's how login module and all other return URL usages function (base64 encode and decode).