-
Hi, It would be convenient for us and I think for people in general to register send_listen_mail on the plone site root, in addition to having it registered on the zope root as it currently is. So: =================================================================== --- browser/configure.zcml (revision 65270) +++ browser/configure.zcml (working copy) @@ -193,6 +193,13 @@ /> <browser:page + for="Products.CMFPlone.interfaces.IPloneSiteRoot" + name="send_listen_mail" + class="Products.listen.utilities.list_lookup.MailDeliveryView" + permission="zope2.Public" + /> + + <browser:page for="Products.listen.interfaces.IHaveSubscribers" name="manage_membership" class=".manage_membership.ManageMembersView" Does anyone see how this might cause problems for anyone else if I check this in? (For instance, I know the opencore registration that does exactly this would need to be deleted to avoid conflicting registrations.) Chris- Thread Outline:
-
Chris Abraham wrote: > Hi, > It would be convenient for us and I think for people in general to > register send_listen_mail on the plone site root, in addition to having > it registered on the zope root as it currently is. So: > > =================================================================== > --- browser/configure.zcml (revision 65270) > +++ browser/configure.zcml (working copy) > @@ -193,6 +193,13 @@ > /> > > <browser:page > + for="Products.CMFPlone.interfaces.IPloneSiteRoot" > + name="send_listen_mail" > + class="Products.listen.utilities.list_lookup.MailDeliveryView" > + permission="zope2.Public" > + /> > + > + <browser:page > for="Products.listen.interfaces.IHaveSubscribers" > name="manage_membership" > class=".manage_membership.ManageMembersView" > > > Does anyone see how this might cause problems for anyone else if I check > this in? (For instance, I know the opencore registration that does > exactly this would need to be deleted to avoid conflicting registrations.) +1. in virtual hosting situations, the SMTP server would be able to call http://yourpublicurl.com/send_listen_mail (rather than http://###.##.##.###:PORT/send_listen_mail, as is currently required). -r
-
ok, checked in r65281. On May 20, 2008, at 2:37 PM, Rob Miller wrote: > Chris Abraham wrote: >> Hi, >> It would be convenient for us and I think for people in general to >> register send_listen_mail on the plone site root, in addition to >> having it registered on the zope root as it currently is. So: >> =================================================================== >> --- browser/configure.zcml (revision 65270) >> +++ browser/configure.zcml (working copy) >> @@ -193,6 +193,13 @@ >> /> >> <browser:page >> + for="Products.CMFPlone.interfaces.IPloneSiteRoot" >> + name="send_listen_mail" >> + >> class="Products.listen.utilities.list_lookup.MailDeliveryView" >> + permission="zope2.Public" >> + /> >> + >> + <browser:page >> for="Products.listen.interfaces.IHaveSubscribers" >> name="manage_membership" >> class=".manage_membership.ManageMembersView" >> Does anyone see how this might cause problems for anyone else if I >> check this in? (For instance, I know the opencore registration >> that does exactly this would need to be deleted to avoid >> conflicting registrations.) > > +1. in virtual hosting situations, the SMTP server would be able > to call http://yourpublicurl.com/send_listen_mail (rather than > http://###.##.##.###:PORT/send_listen_mail, as is currently required). > > -r > > > -- > Archive: http://www.openplans.org/projects/listen/lists/listen-dev/ > archive/2008/05/1211308585666 > To unsubscribe send an email with subject unsubscribe to listen- > dev@.... Please contact listen-dev- > manager@... for questions. > > > !DSPAM:4017,48331aa625868992556831! >
-