[BUG] Using old jauth.db with jcommunity upgrade

[jlstanus]

Hello,

I'm testing 3.2pre with my existing projects under LWC 3.1 and 3.2 before jcommunity upgrade.

As mentionned in issues docker-lizmap, we cannot use the lizmap_var directory created with an old version of LWC.

If we have hundrerd users in jauth.db, we need a tool to (auto-) convert the old to the new.

So, how to export from old and import in the new.

JLS

[jlstanus]

This SQL has fixed the problem of old jauth.db with existing users.

I have simply added the new fields in jlx_user :

ALTER TABLE jlx_user ADD status INTEGER DEFAULT '';
ALTER TABLE jlx_user ADD keyactivate VARCHAR(50) DEFAULT '';
ALTER TABLE jlx_user ADD request_date datetime DEFAULT '';
ALTER TABLE jlx_user ADD create_date datetime DEFAULT '';
UPDATE jlx_user SET status = 1;
UPDATE jlx_user SET create_date = '2018-03-27';

I m not sure the 2 last lines are mandatory

Then, i replace (empty/blank) new version jauth.db by the old one edited with the above sql.

[rldhont]

@laurentj this issue still remains ?

[rldhont]

@jlstanus if you use a normal upgrade from 3.1 to 3.2, the database jauth.db will be updated.

[laurentj]

@jlstanus We cannot reproduce the issue. If it still remain, please provide a full list of steps to help us to reproduce the issue.

[jlstanus]

Now it's ok.

Thanks