Re: [Zope-dev] Confirmation email message after adding a new user

2013-03-14 Thread Gauthier Bastien

  
  
Hi,
  
  you should ask your question on the Plone-users list.
  
  You can subscribe here : https://plone.org/support/lists
  
  Have a nice day,
  
  

  

   Gauthier
  Bastien


   
 Zoning industriel, 34
  5190 Mornimont
  Tl: 0032(65)32 96 70
  Fax: 0032(65)32 96 79
  prenom@imio.be
  
   
La mutualisation
  informatique
au
  service des pouvoirs locaux

  

  
  Le 14/03/13 10:04, Murat Bilal a crit:

Hi,
  
  
  I want to change the confirmation email message after adding
a new user in a plone site.
  
  
  From where i can edit this confirmation email message.
  
  
  Thanks
  
  
  Murat
  
  
  
  ___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )



  

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Status of github migration

2013-01-31 Thread Gauthier Bastien

  
  
Hi everybody,
  
  I made what necessary for z3c.soap to comply with the zope project
  policy (used zope.repositorypolicy) and incindentally to work with
  Zope 2.13.19, what is the process now so it is migrated to Github?
  
  Thank you and have a nice day,
  
  

  

  

  
  
Gauthier Bastien
Support IMIO - CommunesPlone
rue de la Vieille Sambre 34
5190 Mornimont
Tl: +32(0)71 780979
  


  
Disclaimer


Les informations contenues dans ce courrier lectronique
(annexes incluses) sont confidentielles et rserves 
l'usage exclusif des destinataires repris ci-dessus. Si
vous n'tes pas le destinataire, soyez inform par la
prsente que vous ne pouvez ni divulguer, ni reproduire,
ni faire usage de ces informations pour vous-mme ou
toute tierce personne. Si vous avez reu ce courrier
lectronique par erreur, vous tes pri d'en avertir
immdiatement l'expditeur et d'effacer le message
e-mail de votre ordinateur.


De informatie in deze e-mail, bijlagen inbegrepen, is
vertrouwelijk en is als dus danig voorbehouden voor
exclusief gebruik door de hierboven vermelde
bestemmeling(en). Indien u niet de bestemmeling bent,
willen wij u erop wijzen dat u deze informatie niet mag
aanwenden voor eigen gebruik noch verspreiden aan
derden. Indien u deze e-mail per ongeluk hebt ontvangen,
gelieve de afzender onmiddellijk te verwittigen en deze
e-mail van uw computer te verwijderen.


The information contained in this e-mail and the annexed
documents is confidential and exclusively available to
the here above mentioned addressee(s).Should you not be
the addressee, please be informed that you may neither
disclose nor reproduce this e-mail, nor may the
information contained in this e-mail and its eventually
annexed documents be used by yourself or by a third
party. If you erroneously received this e-mail, could
you kindly and immediately inform the addresser and
delete the message on your computer.
  

  

  
  Le 11/01/13 16:42, Jim Fulton a crit:


  On Fri, Jan 11, 2013 at 10:34 AM, Tres Seaver tsea...@palladion.com wrote:

  
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/10/2013 06:10 PM, Matthew Wilkes wrote:



  Tres Seaver wrote:

  
What is needed is not scripts, but eyeballs:  we need people who
know the various packages and*care*  about getting them migrated to
github to step up.  Softwward which doesn't have a champion willing
to do the work should stay behind on SVN.

  
  
The community as a whole cares about having them all migrated to
github. I'm sure this will happen the next time there's a sprint, just
like lots of them got migrated (and subsequently deleted) at the zope4
sprint in San Francisco a few years back.



The communite as-a-whole demonstrably does *not* care about many of the
projects on svn.zope.org.  E.g.:

 https://mail.zope.org/pipermail/zope-tests/2013-January/070977.html



  We need man-hours, sure, but not champions. Being blocked on working
on the code because you're the first one to care about a package and
subsequently have to learn how to do the migration is a crazy way of
doing things.



The foundation agreed to support moving projects to github, but that
isn't a blank check.  For instance, if there is substantial interest in
having the projects pulled in by the current Plone buildout moved, make a
list of them, and recruit the folks to step up and help with the
migration for them.  The effort requires includes doing the conversion,
checking the results *by hand*, landing the repository, and fixing
anything that breaks once you do (including stuff that breaks in projects
you otherwise don't care about).

Any project that can't find somebody willing to do that work (that is
what I meant by a "champion") is better off staying on SVN:  we don't do
ourselves favors by carrying all the unmaintained baggage of fifteen
years worth of development forward, just for "purity" / completeness /
whatever.

  
  
+1

BTW (speaking of cruft), as someone who used/abused svn.zope.org as a
generic open-source hosting service (when I should have

Re: [Zope-dev] Small fix in Products.ZCTextIndex, how to go further?

2012-11-21 Thread Gauthier Bastien

  
  
Hi,
  
  does the current version of
  Products.ZCTextIndex.ZCTextIndex.ZCTextIndex.index_object method
  seems ok about keeping optimization?
  
  If so, what is the process to release a new version because we
  really need this in our projects and in Plone...  And as it fixes
  a bug, I think everybody using it needs it ;-)
  
  How to process?
  
  Thank you very much and have a nice end of day,
  
  

  

  

  
  
Gauthier Bastien
Support IMIO - CommunesPlone
rue de la Vieille Sambre 34
5190 Mornimont
Tél: +32(0)71 780979
  


  
Disclaimer


Les informations contenues dans ce courrier électronique
(annexes incluses) sont confidentielles et réservées à
l'usage exclusif des destinataires repris ci-dessus. Si
vous n'êtes pas le destinataire, soyez informé par la
présente que vous ne pouvez ni divulguer, ni reproduire,
ni faire usage de ces informations pour vous-même ou
toute tierce personne. Si vous avez reçu ce courrier
électronique par erreur, vous êtes prié d'en avertir
immédiatement l'expéditeur et d'effacer le message
e-mail de votre ordinateur.


De informatie in deze e-mail, bijlagen inbegrepen, is
vertrouwelijk en is als dus danig voorbehouden voor
exclusief gebruik door de hierboven vermelde
bestemmeling(en). Indien u niet de bestemmeling bent,
willen wij u erop wijzen dat u deze informatie niet mag
aanwenden voor eigen gebruik noch verspreiden aan
derden. Indien u deze e-mail per ongeluk hebt ontvangen,
gelieve de afzender onmiddellijk te verwittigen en deze
e-mail van uw computer te verwijderen.


The information contained in this e-mail and the annexed
documents is confidential and exclusively available to
the here above mentioned addressee(s).Should you not be
the addressee, please be informed that you may neither
disclose nor reproduce this e-mail, nor may the
information contained in this e-mail and its eventually
annexed documents be used by yourself or by a third
party. If you erroneously received this e-mail, could
you kindly and immediately inform the addresser and
delete the message on your computer.
  

  

  
  Le 14/11/12 16:26, Hanno Schlichting a écrit :

Hi.
  
  The change looks ok. But I think you broke an optimization. IIRC
  the code compares the old and new values for the index, and skips
  the indexing step if they are the same. The typical
  item.reindexObject() call sents data for all indexes, even if just
  one or two them have changed. The optimization made sure to skip
  any extra work, if there wasn't really any change for the text
  index. Without that check, you end up updating and writing a bunch
  of internal data structures in the text index every time. Those
  lead to slower write performance and more conflict errors.
  
  Could you have another look, and see if you can preserve the
  optimization?
  
  Thanks,
  Hanno
  

On Wed, Nov 14, 2012 at 4:16 PM,
  Gauthier Bastien gauth...@imio.be wrote:
  
 Hi everybody,
  
  I made a small change in the current Products.ZCTextIndex
  product, the change can be saw here :
  
  http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/ZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689
  
  and I added a test here :
  
  http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/tests/testZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689
  
  This fixes ticket : https://dev.plone.org/ticket/13310 :
  while reindexing, if the new content is empty, the index
  is not reindexed and the last indexed value is kept.
  
  I just wonder if it was the way to go, and if it was and
  if a reviewer can confirm that changes are OK, what to do
  to release a new version because this is a huge bug for
  us...
  
  Thank you and have a nice end of day

[Zope-dev] Small fix in Products.ZCTextIndex, how to go further?

2012-11-14 Thread Gauthier Bastien

  
  
Hi everybody,

I made a small change in the current Products.ZCTextIndex product,
the change can be saw here :

http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/ZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689

and I added a test here :

http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/tests/testZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689

This fixes ticket : https://dev.plone.org/ticket/13310 : while
reindexing, if the new content is empty, the index is not reindexed
and the last indexed value is kept.

I just wonder if it was the way to go, and if it was and if a
reviewer can confirm that changes are OK, what to do to release a
new version because this is a huge bug for us...

Thank you and have a nice end of day,

-- 
  

  

  


  Gauthier Bastien
Support IMIO - CommunesPlone
rue de la Vieille Sambre 34
5190 Mornimont
Tl: +32(0)71 780979

  
  

  Disclaimer
  
  
  Les informations contenues dans ce courrier lectronique
  (annexes incluses) sont confidentielles et rserves 
  l'usage exclusif des destinataires repris ci-dessus. Si
  vous n'tes pas le destinataire, soyez inform par la
  prsente que vous ne pouvez ni divulguer, ni reproduire,
  ni faire usage de ces informations pour vous-mme ou toute
  tierce personne. Si vous avez reu ce courrier
  lectronique par erreur, vous tes pri d'en avertir
  immdiatement l'expditeur et d'effacer le message e-mail
  de votre ordinateur.
  
  
  De informatie in deze e-mail, bijlagen inbegrepen, is
  vertrouwelijk en is als dus danig voorbehouden voor
  exclusief gebruik door de hierboven vermelde
  bestemmeling(en). Indien u niet de bestemmeling bent,
  willen wij u erop wijzen dat u deze informatie niet mag
  aanwenden voor eigen gebruik noch verspreiden aan derden.
  Indien u deze e-mail per ongeluk hebt ontvangen, gelieve
  de afzender onmiddellijk te verwittigen en deze e-mail van
  uw computer te verwijderen.
  
  
  The information contained in this e-mail and the annexed
  documents is confidential and exclusively available to the
  here above mentioned addressee(s).Should you not be the
  addressee, please be informed that you may neither
  disclose nor reproduce this e-mail, nor may the
  information contained in this e-mail and its eventually
  annexed documents be used by yourself or by a third party.
  If you erroneously received this e-mail, could you kindly
  and immediately inform the addresser and delete the
  message on your computer.

  

  

  

___
Zope-Dev maillist  -  Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Small fix in Products.ZCTextIndex, how to go further?

2012-11-14 Thread Gauthier Bastien

  
  
Hi Hanno,
  
  I did not know if checking the current index value could be faster
  or slower than indexing anyway.
  
  I think that checking the current index length could do what we
  need :
  
  Keeping the current code and changing this :
  
  
  --- if all_texts:
+++ if all_texts or self.index.length():
    return self.index.index_doc(documentId, all_texts)
  
  
  This way, it we have all_texts or if the index already contains
  something, we reindex...
  
  Would this keep the optimization?
  
  I adapted here and every tests passed...
  
  

  

  

  
  
Gauthier Bastien
Support IMIO - CommunesPlone
rue de la Vieille Sambre 34
5190 Mornimont
Tél: +32(0)71 780979
  


  
Disclaimer


Les informations contenues dans ce courrier électronique
(annexes incluses) sont confidentielles et réservées à
l'usage exclusif des destinataires repris ci-dessus. Si
vous n'êtes pas le destinataire, soyez informé par la
présente que vous ne pouvez ni divulguer, ni reproduire,
ni faire usage de ces informations pour vous-même ou
toute tierce personne. Si vous avez reçu ce courrier
électronique par erreur, vous êtes prié d'en avertir
immédiatement l'expéditeur et d'effacer le message
e-mail de votre ordinateur.


De informatie in deze e-mail, bijlagen inbegrepen, is
vertrouwelijk en is als dus danig voorbehouden voor
exclusief gebruik door de hierboven vermelde
bestemmeling(en). Indien u niet de bestemmeling bent,
willen wij u erop wijzen dat u deze informatie niet mag
aanwenden voor eigen gebruik noch verspreiden aan
derden. Indien u deze e-mail per ongeluk hebt ontvangen,
gelieve de afzender onmiddellijk te verwittigen en deze
e-mail van uw computer te verwijderen.


The information contained in this e-mail and the annexed
documents is confidential and exclusively available to
the here above mentioned addressee(s).Should you not be
the addressee, please be informed that you may neither
disclose nor reproduce this e-mail, nor may the
information contained in this e-mail and its eventually
annexed documents be used by yourself or by a third
party. If you erroneously received this e-mail, could
you kindly and immediately inform the addresser and
delete the message on your computer.
  

  

  
  Le 14/11/12 16:26, Hanno Schlichting a écrit :

Hi.
  
  The change looks ok. But I think you broke an optimization. IIRC
  the code compares the old and new values for the index, and skips
  the indexing step if they are the same. The typical
  item.reindexObject() call sents data for all indexes, even if just
  one or two them have changed. The optimization made sure to skip
  any extra work, if there wasn't really any change for the text
  index. Without that check, you end up updating and writing a bunch
  of internal data structures in the text index every time. Those
  lead to slower write performance and more conflict errors.
  
  Could you have another look, and see if you can preserve the
  optimization?
  
  Thanks,
  Hanno
  

On Wed, Nov 14, 2012 at 4:16 PM,
  Gauthier Bastien gauth...@imio.be wrote:
  
 Hi everybody,
  
  I made a small change in the current Products.ZCTextIndex
  product, the change can be saw here :
  
  http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/ZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689
  
  and I added a test here :
  
  http://svn.zope.org/Products.ZCTextIndex/trunk/src/Products/ZCTextIndex/tests/testZCTextIndex.py?rev=128273sortby=logr2=128273r1=113689
  
  This fixes ticket : https://dev.plone.org/ticket/13310 :
  while reindexing, if the new content is empty, the index
  is not reindexed and the last indexed value is kept.
  
  I just wonder if it was the way to go, and if it was and
  if a reviewer can confirm that changes are OK, what to do
  to release a new