Customising the Event registration

[MikeZ]

Hi there,

First off, nice product.
But there are to many fields required here, such as company..
How can i easily (since i am not a Plone programmer, though i am an
experienced web programmer) modify this ?

Other things i miss/noticed:
-Show how many seats there are left on event, using the maximum no. of
attendees:
-easy list of email-address of registrants,
-possibility to hide registrants for normal users
-if admin/reviewer edits the registrant it sends out an email to the
registrant again, this should happen only once.
-email message should be configurable at the event level also, not only
on the zmi level.

rgrd Mike

[Jason McVetta]

On 10/4/05, MikeZ <mrei...@gmail.com> wrote:

First off, nice product.

Thanks.  :)   But it still has a lot of room for improvement.

But there are to many fields required here, such as company..
How can i easily (since i am not a Plone programmer, though i am an
experienced web programmer) modify this ?

Edit the schema in Event.py -- to make a currently-required field optional, change its "required = True," to "required = False,". 

Other things i miss/noticed:
-Show how many seats there are left on event, using the maximum no. of
attendees:

Support for  max num attendees is not  yet complete.  Probably it will  not be complete in 0.6, unless someone wants to step up to bat & add it. 

-easy list of email-address of registrants,

"Export  List of Registrants" includes this.

-possibility to hide registrants for normal users

If I understand your meaning correctly, you are concerned that any anonymous user can edit any anonymously-created registrant object, if only they know its name.  This is definitely undesirable, but check out past list discussion on it -- it's decidedly non-trivial to fix.

-if admin/reviewer edits the registrant it sends out an email to the
registrant again, this should happen only once.

I totally agree.  This should be pretty easy to fix, so it will probably be resolved in 0.6.  Here's how I'm planning to cure it:  add a hidden bool field to the schema, something like "have_sent_confirmation_email".  When the save hook is called to send the confirmation message, it checks this field.  If the field is false, it sends the mail then sets the field to true. 

I can think of two possible rational behaviors if it finds the value already set to True:  Send nothing; or, send an alternate email saying something along the line of "your info has been updated".

-email message should be configurable at the event level also, not only
on the zmi level.

Sure, that would be cool.  Wanna contribute it?  (If you do, please work off the https://svn.plone.org/svn/collective/EventRegistration/branches/jmcvetta-atct_and_location/ branch.)

Jason
(still on vacation, now in the vast wifi-free wastelands of outer-suburban Cleveland)

[Jason McVetta]

On 10/4/05, MikeZ <mrei...@gmail.com> wrote:

First off, nice product.

Thanks.  :)   But it still has a lot of room for improvement.

But there are to many fields required here, such as company..
How can i easily (since i am not a Plone programmer, though i am an
experienced web programmer) modify this ?

Edit the schema in Event.py -- to make a currently-required field optional, change its "required = True," to "required = False,". 

Other things i miss/noticed:
-Show how many seats there are left on event, using the maximum no. of
attendees:

Support for  max num attendees is not  yet complete.  Probably it will  not be complete in 0.6, unless someone wants to step up to bat & add it. 

-easy list of email-address of registrants,

"Export  List of Registrants" includes this.

-possibility to hide registrants for normal users

If I understand your meaning correctly, you are concerned that any anonymous user can edit any anonymously-created registrant object, if only they know its name.  This is definitely undesirable, but check out past list discussion on it -- it's decidedly non-trivial to fix.

-if admin/reviewer edits the registrant it sends out an email to the
registrant again, this should happen only once.

I totally agree.  This should be pretty easy to fix, so it will probably be resolved in 0.6.  Here's how I'm planning to cure it:  add a hidden bool field to the schema, something like "have_sent_confirmation_email".  When the save hook is called to send the confirmation message, it checks this field.  If the field is false, it sends the mail then sets the field to true. 

I can think of two possible rational behaviors if it finds the value already set to True:  Send nothing; or, send an alternate email saying something along the line of "your info has been updated".

-email message should be configurable at the event level also, not only
on the zmi level.