Unfortunately your post got me thinking (after I had replied). My
component is utter garbage, sorry.
When I looked at it, I saw that all it was, really, was a wrapper to
the Ticket model.
I moved all code into the model yesterday and I have the same
functionality without a component.
The reason
Thanks Martin.
Looks like the same concept, I noticed some things that made me
curios.
In implementation did you include the functionality within a users
component or a separate one dedicated to tickets? Do you have a
different method to let logged in users change their credentials?
I am going
You got some nice functionality there. I think it could be reorganised
a bit. At least from how I see a ticket system. I went with a slightly
different approach a few years ago when I needed similar
functionality. It is the same basic functionality but the code has a
different organisation from y
Allowing users the ability to change passwords is a no brainer.
But what do you do if a user losses their password? Several months
ago I wrote a very simple component that works in conjunction with my
user model to issue tickets to user emails.
The ticket can be retrieved via email and allows u
