Skip to content

Conversation

@obilodeau
Copy link
Contributor

@cgx @dereksky can one of you guys review please?

guest template updated
config / doc updated
also presenting the options in the signup page a little more cleanly
like we recently did with the billing stuff
rewritten most of the form validator too:
- proper email validation from pf::web::util
- proper phone number validation from pf::web::util
- performing per-guest-mode field validation
replaced all token, pid, username, etc. to guest_pid (avoid clash in sessions)
got rid of an extra test in sms reg that was no longer required
other little things
moved templates around and their refering constants
renamed an api call
also I'm pretty sure I avoided a bug in the eval error handling (a $msg redefinition)
it can send emails to the sponsor
extracted in it's own sub (easier to override)
localdomain requirement extracted in a configuration parameter
easier for users to override and way more flexible
will also be tied to the authentication portion once I integrate that
This is a beginning of adding configuration options to the categories.

To better reflect its use, node categories were moved out of the node tab into configuration tab on the Web Admin
This naming is more coherent with to-be-introduced self pre-registration.
- SMS was decided to be out of scope
- email will not work as-is (for now)
- Firewall / Apache ACLs still to be done
When requesting the footer you can say whether or not you want the footer's
help. This allows for easy turn off in guest pre-registration workflows.
increases attack surface
- firewall opens https on mgmt interface
- apache ACLs allows access to /signup
extract all subjects into i18n to allow easy overloading
so one not satisified with it can replace the string with an appropriate msgstr "..." in conf/locale/
This allows us to use format strings (i18n_format) in the calling code and benefit from translatable errors, etc.
…-site

Useful if the sponsor requests himself the access.
@obilodeau
Copy link
Contributor Author

We plan on releasing 3.3 this week. This would need to be acknowledged by one of you soon.

@cgx
Copy link
Contributor

cgx commented Apr 11, 2012

Approved. Go!

@obilodeau obilodeau merged commit f753efc into stable Apr 12, 2012
@fdurand fdurand mentioned this pull request Oct 18, 2025
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants