[wp-hackers] A request.
h0bbel at p0ggel.org
Fri May 19 19:19:35 GMT 2006
This is the exact behaviour the Gallery project uses. A user files a ticket
with details (gallery version and so on). A unique code is generated and
displayed to the user (as well as emailed to him). When someone from the
support team contacts the user, we copy the details the user submitted in
the email including the unique identifier.
We have a very basic admin interface where all tickets are listed, and we
can change the status of the tickets like open/pending/in
progress/abandoned/invalid/completed. When someone changes a status for a
ticket from open to pending it gets assigned that user and removed from the
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com
> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Podz
> Sent: 19. mai 2006 18:50
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] A request.
> Vogel, Andrew (vogelap) wrote:
> > I swear by
> > pr ess/. It may be able to do what you require.
> Sort of - but the other way round.
> The end result is that the user authenticates us because they
> will be giving us all their webhost details.
> User completes form and is shown a unique code '56789'
> They get a confirmation email that also has that code.
> We get the completed form and that unique code as well.
> The installer then emails saying "Here is the code 56789, you
> can trust me."
> -so we are proving who we are.
> How that code is passed from the form to us (email /
> database) is up for discussion - I only thought email because
> it's simple and straightforward.
> But generating, displaying and then distributing the code to
> the two parties is beyond what we have been doing. If we can
> get this going and tested then we can launch the project -
> it's the final piece of the jigsaw.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers