-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
user registration #83
Comments
also, when a new user is created, the header image in the welcome email is not working and displays a broken image in the email. |
@deltaforce Can I request you to post your issues separately. In that way, it's easy to manage and refer things whenever necessary. I'm answering this one only:
Actually, we're using WordPress' way wherever possible. Hence we used the WordPress checkbox "Anyone can Register" (code here).
But if enable Registration in the ticketing arena, it will behave the same as the WordPress' one. How can we restrict 'em? We have an Open issue (Issue #16) regarding the security of the embedded registration system, and we agree. Until a proper fix, the system would be "Beta". But bypassing the WordPress registration, enabling another registration in the ticketing arena, I think the SPAM issue would be the same. We need to solve the #16 first, then we can think of a new checkbox for enabling registration other than the WordPress registration checkbox. PS. And I would like to request you to open a new issue for the email header image, please. 😃 But the primary finding is: we cannot replicate the issue. The image is working as a header image (Proof: http://prntscr.com/ovpuq0) |
I cannot answer your question, as I am not a WordPress or PHP developer. RE the header image, It only seems to affect windows mail, when I sent to my gmail address it seems fine. |
Hi,
In order for tickets to work I have to enable "anyone can register", which I don't really want to do, as this attracts loads of SPAM BOT registrations.
Is there any way I can restrict this to the ticket system only?
The text was updated successfully, but these errors were encountered: