Hi all It seems that I lost the superuser privileges during the upgrade from 3.0rc1 to 3.0rc2. Is there a way to set those privileges (within the staff interface or somewhere else)? I tried to do so using the user in koha-conf.xml but even that one seemes to have lost them. Greetings Beda
Beda, I'm not sure, but the first question & answer in this FAQ: http://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/App... help you ... --- Nicole C. Engard Open Source Evangelist, LibLime (888) Koha ILS (564-2457) ext. 714 nce@liblime.com AIM/Y!/Skype: nengard http://liblime.com http://blogs.liblime.com/open-sesame/ On Thu, Jul 24, 2008 at 3:23 AM, Beda Szukics <beda@muri-gries.ch> wrote:
Hi all
It seems that I lost the superuser privileges during the upgrade from 3.0rc1 to 3.0rc2.
Is there a way to set those privileges (within the staff interface or somewhere else)?
I tried to do so using the user in koha-conf.xml but even that one seemes to have lost them.
Greetings Beda _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Nicole Engard schrieb:
Beda,
I'm not sure, but the first question & answer in this FAQ: http://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/App... might help you ...
I do have a user named "koha" and I can log in. But this user hasn't the privileges to set privileges for other users. The final par to my koha-conf.xml: <!-- ADDITIONAL KOHA CONFIGURATION DIRECTIVE --> <!-- db_scheme should follow the DBD driver name --> <!-- port info: mysql:3306 Pg:5432 (5433 on Debian) --> <config> <db_scheme>mysql</db_scheme> <database>Schulbibliothek</database> <hostname>localhost</hostname> <port>3306</port> <user>koha</user> <pass>[my password]</pass> and so on That seems to be o.k.? Greetings Beda
There are some things that your are NOT supposed to be able to do as the superuser (in your case, "koha") by design. The superuser doesn't have assignable privileges, because they are not a real user. I.E., they do not appear in the borrowers table at all, because their account is required to *create* the borrowers table. --joe On Thu, Jul 24, 2008 at 8:38 AM, Beda Szukics <beda@muri-gries.ch> wrote:
Nicole Engard schrieb:
Beda,
I'm not sure, but the first question & answer in this FAQ:
http://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/App...
might help you ...
I do have a user named "koha" and I can log in. But this user hasn't the privileges to set privileges for other users.
The final par to my koha-conf.xml:
<!-- ADDITIONAL KOHA CONFIGURATION DIRECTIVE --> <!-- db_scheme should follow the DBD driver name --> <!-- port info: mysql:3306 Pg:5432 (5433 on Debian) --> <config> <db_scheme>mysql</db_scheme> <database>Schulbibliothek</database> <hostname>localhost</hostname> <port>3306</port> <user>koha</user> <pass>[my password]</pass>
and so on
That seems to be o.k.?
Greetings Beda _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Joe Atzberger schrieb:
There are some things that your are NOT supposed to be able to do as the superuser (in your case, "koha") by design. The superuser doesn't have assignable privileges, because they are not a real user. I.E., they do not appear in the borrowers table at all, because their account is required to *create* the borrowers table. I am confused now. What's the superuser for it not to create new users and assign them the privileges they need to work properly?
In my actual installation of koha (wich I updated to 3.0RC1) there are (only) two users right now: koha and beda (the one I created during the installation process of 3.0beta2). Both do not have the ability to set privileges for others. So I think I am blocked and cant go further. I had made two parallel installations of koha (beta2). The one I'm working with now I updated to RC1 (3.00.00.094), the other one is still beta2 (3.00.00.067). There I am still able to set the privileges. I think there must have been some mistake I did during the update process. But how correct it? Beda
Beda Szukics schrieb:
Joe Atzberger schrieb:
There are some things that your are NOT supposed to be able to do as the superuser (in your case, "koha") by design. The superuser doesn't have assignable privileges, because they are not a real user. I.E., they do not appear in the borrowers table at all, because their account is required to *create* the borrowers table.
I am confused now. What's the superuser for it not to create new users and assign them the privileges they need to work properly?
I'm even more confused now: My problems have to do with the fact that I'm using koha intranet in _german_ First thing I tried was to enter the address of the privileges manually: http://[my.server]/cgi-bin/koha/members/member-flags.pl?member=2. There I could see the checkboxes and select them, but the changes couldn't be saved. I changed the intranet-language to english and I had to change yui-path from http://yui.yahooapis.com/2.3.1/build to /intranet-tmpl/prog/en/lib/yui/ in Home->Administration->System Preferences->Staff Client (othervise the checkboxes would not appear). Strange ... Any ideas. (I would like to understand the program :-(( Beda
participants (3)
-
Beda Szukics -
Joe Atzberger -
Nicole Engard