Hi,

 

Some of our users were confused when our OpenMeetings Administrator
created their accounts (yes, that is me),  and they received an email
saying "OpenMeetings SignUp". They were confused because they actually
never "signed up" for OpenMeetings, instead someone else (the CO2CRC
Adminstirator) created their account on their behalf.

 

I would like to propose the following changes to the English text as
suggested below.  Please review and let me know if this would cause any
issues where else the text is used.  Please also let me know if you
believe the suggested text changes are an improvement or not.

 

506, "registering_mail_text_head", "OpenMeetings SignUp" changed to
"OpenMeetings Account Details".

 

507, "registering_mail_text_head2", "Your user data", changed to "Your
account details".

 

518, "register_mail_subject",  "OpenMeetings SignUp" changed to "Your
OpenMeetings account details".

 

I have tested the account creation by using "Not a member?" at the
"Login" screen, and the 'automatically generated account details email'
uses this same text that is sent when the Administrator creates an
account.  While the wording no longer mentions "sign up", I personally
do not have an issue with this, and it is a lot easier that altering the
code to include text for both ways of signing up.  Your comments on my
suggestions, please.

 

Thanks,

 

George Kirkham

 

IT Manager

Cooperative Research Centre For Greenhouse Gas Technologies (CO2CRC) 

NFF House, 14 - 16 Brisbane Avenue, Barton, ACT, 2600, Australia

T: (02) 6120 1600

F: (02) 6273 7181

E: [email protected], 

W: www.co2crc.com.au

 

 

From: George Kirkham [mailto:[email protected]] 
Sent: Saturday, 12 May 2012 8:40 PM
To: [email protected]
Subject: RE: exclusive audio in Build #68

 

Thanks Sebastian.  I will install and test.

 

 

George Kirkham

 

 

 

From: [email protected] [mailto:[email protected]] 
Sent: Saturday, 12 May 2012 7:55 PM
To: [email protected]
Subject: Re: exclusive audio in Build #68

 

Hallo Geroge,

1) + 2) should be solved with 
https://svn.apache.org/viewvc?view=revision&revision=1337492

Sebastian

Reply via email to