01-31-2017, 11:02 AM
Paul, can you join our gitter group?
https://gitter.im/corebos/discuss
that will probably be more agile for you
In any case, this separation of concern that Smarty3 has imposed on the developers is the correct way to go. It is what a templating system is for, it makes no sense to invest in a templating system just to go out and start using php as a templating system.
In any case, the correct way to do what you want is not adding that to the Login template, it is adding it to the authentication process. Right now coreBOS has IP bloocking for admin users by defining the global variable Application_AdminLoginIPs. I didn't answer your email because I wanted to enhance that validation with your IP detection code (which is more complete than ours) and also add normal user IP blocking. That way the application will simply return the correct login error message and you won't have to modify the template at all unless you want to change the layout
A little patience, we will get to it
https://gitter.im/corebos/discuss
that will probably be more agile for you
In any case, this separation of concern that Smarty3 has imposed on the developers is the correct way to go. It is what a templating system is for, it makes no sense to invest in a templating system just to go out and start using php as a templating system.
In any case, the correct way to do what you want is not adding that to the Login template, it is adding it to the authentication process. Right now coreBOS has IP bloocking for admin users by defining the global variable Application_AdminLoginIPs. I didn't answer your email because I wanted to enhance that validation with your IP detection code (which is more complete than ours) and also add normal user IP blocking. That way the application will simply return the correct login error message and you won't have to modify the template at all unless you want to change the layout
A little patience, we will get to it
Joe
TSolucio
TSolucio