openmeetings-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Solodovnik <solomax...@gmail.com>
Subject Re: 307 OpenMeetings RC2: Period Invitation Gives Invalid Invitation Code
Date Sun, 27 Sep 2015 09:05:13 GMT
OK, I'll create new RC3, and will propose to make "short" vote period for
it (let's say today and tomorrow)

On Sun, Sep 27, 2015 at 2:43 PM, Alvaro <zurcamos@gmail.com> wrote:

>
> ...if is possible, please re-release 3.0.7. This version
> is very good.
>
> Alvaro
>
>
> ..............
>
> El dom, 27-09-2015 a las 13:46 +0600, Maxim Solodovnik escribió:
> > Here is the issue:
> https://issues.apache.org/jira/browse/OPENMEETINGS-1260
> > The fix is trivial, shoukd we consider this issue as showstopper and
> > re-release 3.0.7 with the fix? or maybe it might wait until 3.0.8?
> >
> > On Sun, Sep 27, 2015 at 12:11 PM, Susheel Jalali <
> > Susheel.Jalali@coscendcommunications.com> wrote:
> >
> > > Dear Maxim,
> > >
> > > When we send a invitation from the popup in conference room for today,
> the
> > > user receives the  invitation to be valid for exactly one month ago
> same
> > > time.
> > >
> > > If we create and send an invitation for Sep 27, it is being shown in
> the
> > > Error popup as Aug 27, and when we create and send for Oct 27, it is
> being
> > > accepted as valid for Sep 27, and invitee is able to join the Room
> today.
> > >
> > > It seems either the Java.util.Calendar is returning a date decreased
> by 1
> > > month, or more likely the invitation hash created is encoded with
> exactly
> > > one month subtraction.
> > >
> > > --
> > >
> > > Regards,
> > >
> > > Susheel Jalali
> > >
> > >
> > > Coscend Communications Solutions
> > >
> > > __
> > >
> > > Web site:www.CoscendCommunications.com <
> > > http://www.coscendcommunications.com/>
> > >
> > > ------------------------------------------------------------------
> > >
> > > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail
> > > Messages from Coscend Communications Solutions' posted at:
> > > http://www.CoscendCommunications.com/Terms_and_Conditions.html <
> > > http://www.coscendcommunications.com/Terms_and_Conditions.html>
> > >
> > >
> > > From    Maxim Solodovnik <solomax...@gmail.com>
> > > Subject    Re: 307 OpenMeetings RC2: Period Invitation Gives Invalid
> > > Invitation Code
> > > Date    Sun, 27 Sep 2015 00:05:09 GMT
> > >
> > > Actually 3.0.7 was just released
> > > Will announce tomorrow
> > > Please describe steps to reproduce, since everything seems to work as
> > > expected
> > >
> > > WBR, Maxim
> > > (from mobile, sorry for the typos)
> > > On Sep 26, 2015 21:51, "Susheel Jalali" <
> > > Susheel.Jalali@coscendcommunications.com> wrote:
> > >
> > > > Dear Maxim and Fellow OpenMeetings Developers,
> > > >
> > > > We downloaded OpenMeetings src, compiled and tested period
> invitation.
> > > > Even when the invitation link is used within the valid scheduled
> time, OM
> > > > server incorrectly gives the error:
> > > >    ‘Your invitation code is not valid, the code is only valid during
> this
> > > > specific date and time’.
> > > >
> > > > Attached is the screenshot.  Endless and One-time invitation are
> working
> > > > fine.
> > > >
> > > > Do we have a problem in our installation on three servers (CentOS
> 6.5 /
> > > > Java 7, CentOS 7 / Java 7)?
> > > >
> > > > Or,
> > > >
> > > > Are we missing something in InvitationService.java?
> > > >
> > > > ·         3.0.6 was using import java.util.Calendar; TimezoneUtil
> > > >
> > > > ·         3.0.7 uses import java.util.Date; CalendarHelper
> > > >
> > > > P.S.:  We are sending this to developer group so that if there is an
> > > error
> > > > in code, it is rectified before releasing to the user group.
> > > >
> > > > Thank you.
> > > >
> > > > Sincerely,
> > > >
> > > > ---
> > > >
> > > > Susheel Jalali
> > > >
> > > > Coscend Communications Solutions
> > > >
> > > > *Susheel.Jalali@Coscend.com <Susheel.Jalali@Coscend.com>*
> > > > Web site: <http://www.coscend.com/>www.Coscend.com
> > >
> > >
> >
> >
>
>
>


-- 
WBR
Maxim aka solomax

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message