01-06-2019, 02:24 PM
I think you may have missed the point of UserSpice. UserSpice, at its core, (from the perspective of the person using it to develop an application) is essentially 2 lines of code.
1. It's a call to an init file that sets everything up.
2. It's a call to a securePage function that enforces permissions and security.
UserSpice takes a "take it or leave it approach beyond that.
Don't like our DB class? Use meekro...write your own...do whatever you want. UserSpice doesn't care?
Want to make a login form with zero security? Write an input that literally just matches the input with the username in the db...no password, and say the person enters "admin" and you set $_SESSION['user']=1; and as far as UserSpice is concerned, you're logged in.
I can definitely appreciate MVC and all the other user management systems out there, but the reason that UserSpice has over 1.5 million downloads by people in every nation on earth is because it is so flexible. If your page has the 2 lines mentioned above...nothing else matters. You're welcome to use as much or as little of the UserSpice code as you want.
1. It's a call to an init file that sets everything up.
2. It's a call to a securePage function that enforces permissions and security.
UserSpice takes a "take it or leave it approach beyond that.
Don't like our DB class? Use meekro...write your own...do whatever you want. UserSpice doesn't care?
Want to make a login form with zero security? Write an input that literally just matches the input with the username in the db...no password, and say the person enters "admin" and you set $_SESSION['user']=1; and as far as UserSpice is concerned, you're logged in.
I can definitely appreciate MVC and all the other user management systems out there, but the reason that UserSpice has over 1.5 million downloads by people in every nation on earth is because it is so flexible. If your page has the 2 lines mentioned above...nothing else matters. You're welcome to use as much or as little of the UserSpice code as you want.