[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.2.7 upgrade problems

Hi David;

I believe I have found the problem with the session timeouts.

try adding a backslash (\) in front of the @ sign in line 87 of the LedgerSMB/Session/DB.pm

I will be doing my own testing before I commit this change.

Best Wishes,
Chris Travers

On 7/16/07, Chris Travers <..hidden..> wrote:

On 7/16/07, David Bandel <..hidden..> wrote:
On 7/16/07, Chris Travers <..hidden..> wrote:
> On 7/16/07, David Bandel < ..hidden.. > wrote:
> > Chris and crew,
> >
> > Upgraded from 1.2.5 (with some of my own hot-fixes) to 1.2.7.
> What sort of hot fixes?   Were these re-applied?

one I remember, in Form.pm, I changed one occurrence of customer_id to
{vc}_id because there's no customer_id in the vendor tables, only

Perusing the code, looks like you fixed it.

If I remember any more, I'll check them against your code.

There were two major hotfixes for 1.2.5-- that one and a patch to Locale.pm, both of which made it into 1.2.6.

> > 1.  I get asked at _every_ link selection to login (session expired)
> > Used the admin interface to up the time from 3600 to 86400 because the
> > preferences interface wouldn't save the value.  Still no go, though.
> Are your usernames in the form of Username@company by any chance?

yep.  And we fixed this once (partially) by adding back the @ in the
session.pm code in about 5 places (you had indicated to me 2 places
initially IINM).

Are there any other special characters in the login names?  Puncuation characters or the like?

I think we fixed it in quite a number of places.  I will check again, however.

> > 2.  AR links error out because I don't have a date that LedgerSMB
> > likes in the close books up to field (should be blank, but keeps
> > coming up 0 which is causing the error -- and my date type - dd/mm/yy,
> > closing books to 31/12/2006, is not liked either.
> try:  2006-12-31.  Or if you want it to be blank (for the time being) try
> the following query in psql:
> update defaults set value = null where setting_key = 'closed_to';

OK, the NULL seems to work, but the setting_key is 'closedto', at
least in my db.

Ok.  Thanks.

> The setting it to 0 is a different bug however that has not come up in our
> tests.  Filing that so we don't forget to fix it.

Best Wishes,
Chris Travers