[v4.4] User Registration is not working

[Manivannan Chinnaswamy]

I tried to register as a user, however once i enter the email address and move to next field in the registration form I got a 404 response from the server. Find the attached screenshots for more information.flynax-reg-error-1.jpgflynax-reg-error-2.jpg

[Curtis]

Hello,

Can you send me your cPanel/FTP login details?
I'll check it.

[Manivannan Chinnaswamy]

Hi Curtis,

Please refer to Ticket WEQ-915975

Cheers
M

[Curtis]

Hi Curtis,

Please refer to Ticket WEQ-915975

Cheers
M

I've fixed your problem, you can check.

P.S.
Mike already explained you in ticket that this problem in server side, hosting blocked HTTP POST requests with special chars (for ex. '@' or '.').
I've replaced it hardcoded to phrases '-at-' and '-dot-'. It's a temporary fix and if you can that you need disable this protection on your webserver.

[Manivannan Chinnaswamy]

Hi Curtis

Thanks for your quick workaround. May I know the file on which file you have applied the changes?

[Curtis]

Hi Curtis

Thanks for your quick workaround. May I know the file on which file you have applied the changes?

Yes, of course.
1. /libs/javascript/flynax.lib.js, funtion registration() ~212
2. /includes/classes/rlAccount.class.php
2.1 function ajaxEmailExist() ~778
2.2 function ajaxValidateProfile() ~946
2.3 function ajaxSubmitProfile() ~1118

[Wei Hong]

So this is the server problem and not the software problem? We wont be getting this error right?

[Manivannan Chinnaswamy]

Hi Curtis

Thanks for your help. The registration process works normal. Do we need to apply the same fix to any other features of the software?

[Curtis]

So this is the server problem and not the software problem? We wont be getting this error right?

Yes, this problem on the server side only. The hosting must not block any requests (POST, GET which have special characters).

Hi Curtis


Thanks for your help. The registration process works normal. Do we need to apply the same fix to any other features of the software?

Yes, it must be same for other features, if you cannot disable this protection.
But you need to know that in other places this process can be tricky.