Re: [ledger-smb:bugs] #1165 after conversion to 1.4 previous 1.3.39 users only get menu "new window" and "logout" menu option

On Mon, Jun 2, 2014 at 3:20 PM, Erik Huelsmann <..hidden..> wrote:

Hi Chris,

As the ticket quoted below shows - to me - the current hidden "role_prefix" feature isn't transparent to people. Looks people expect to be able to copy a database and have it "just work".

Would it be an idea to reverse the scheme? Meaning: always add the role_prefix in setup.pl and allow an option in setup.pl when copying a database to "detach" it from the original (where the role prefix is deleted, the menu-acl table being rewritten and the correct roles are being generated)? I would expect that to be more intuitive than the current scheme.

That seems sane to me.

Regards,

Erik.

---------- Forwarded message ----------
From: mvb88 <..hidden..>
Date: Mon, Jun 2, 2014 at 9:15 PM
Subject: [ledger-smb:bugs] #1165 after conversion to 1.4 previous 1.3.39 users only get menu "new window" and "logout" menu option
To: Ticket 1165 <..hidden..>

[bugs:#1165] after conversion to 1.4 previous 1.3.39 users only get menu "new window" and "logout" menu option

Status: open
Group: 1.4
Created: Mon Jun 02, 2014 07:15 PM UTC by mvb88
Last Updated: Mon Jun 02, 2014 07:15 PM UTC
Owner: nobody

I upgraded from 1.3.38 to 1.3.39. Then I copied the DB to a new name (db14) in setup.pl of 1.3.39. This db14 was then opened with setup.pl using latest 1.4.5b, then I rebuild the DB so it matches with 1.4.

previous users have only see menu "new window" and "logout" menu option when logging on to db14.

As a workaround I added a new user via setup.pl (1.4) and gave that "full permissions" when I log on as this user to db14 then I cannot see the menu "system/Admin users" to manage permissions of others, it does have all the other menu items.

When I re-log on to setup.pl to edit the newly created user permissions via that way then this newly created user does not show and I can only create a new user. Is this intended behaviour?

To me this seems unwanted behaviour in the migration, I have not tested this behaviour on a fresh DB created with 1.4

Question on the side: How to make sure that either old users become usable or how to give a newly created user really full permissions in order to repair the old user accounts?

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/ledger-smb/bugs/1165/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.

Best Wishes,

Chris Travers

Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.

http://www.efficito.com/learn_more