> > I just installed v.2.6.1 coming from the previous 2.6.0 (on Win2000)
> > When I access the "configuration" function from a logbook, in the cfg page I only see two buttons in the header
> > (save or cancel); in the previous version I saw more buttons there ("global config", "create new logbook" and so
> > on), so here I'm unable to access global configuration or logbook management (except for current logbook options).
> 
> I tried to reproduce your problem, but could not. In my windows installation it looks fine. You only see the
> (save and cancel) buttons only if you go to "Change [global]", otherwise you see the "Change [global]", "Delete
> this logbook" etc. buttons. Have you tried with the default elogd.cfg which comes from the distribution?

Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both with the
existing cfg file and with the new cfg.
Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.
Regards
Giorgio

> Here I am again... I built and installed v2.6.1 also on a different system, this time on linux; i tried both
with the
> existing cfg file and with the new cfg.
> Choosing "configuration", I still only see the current logbook configuration file section with "Save" and "cancel"
> buttons, no access to global config whatsoever; the same as I saw on windows version. I tried version 2.6.1-1622.

I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
attached (elog:1627/2). So it's a mystery why it is different in your case...

> I tried again, using the configuration file from the distribution (elog:1627/1). Hitting "config", I see the picture
> attached (elog:1627/2). So it's a mystery why it is different in your case...

Indeed... I peeked into the code, and I got the feeling it could be a matter of incorrect user setup (though I have no
users/authorizations defined at all) or maybe browser cookies. A thin trail, but I'll try some debug directly on the
code and, should I come up with something, I'll surely notice you.
Thanks for your support!

> or maybe browser cookies. 

That rings a bell. If you change user permissions (like password file/no password file/rename logbooks) you might be
fooled by old cookies. Just delete all cookies in your browser and try again.

> > or maybe browser cookies. 
> 
> That rings a bell. If you change user permissions (like password file/no password file/rename logbooks) you might be
> fooled by old cookies. Just delete all cookies in your browser and try again.

Hi,
here I am at it again. Since my first posts, I tried to install the latest version of elog out-of-the-box on one pair of
PCs from scratch (fresh elog install on new, just-installed PCs, OS WinXP Pro and Win2000), but with no results. No
trace of the global configuration menu or the buttons to reach it.
Neither taking a look at the code has helped, I could not figure out exactly where the button bar was generated.
Didn't anybody other point out a similar behaviour? Do you have any suggestion for any tests to carry out?
Thanks
GiorgioCC

Hi,
after a long time, I thought I could try to investigate the code some further,
and maybe I found some hint.
The page where I expected the options to show was (probably) the one generated by this function:

void show_admin_page(LOGBOOK * lbs, char *top_group)

Inside, it, the buttons are generated by following code snippets:

(elogd.c:10443)
if (is_admin_user_global(getparam("unm"))) {
   sprintf(str, loc("Change %s"), "[global]");
   rsprintf("<input type=submit name=cmd value=\"%s\">\n", str);
}
(elogd.c:10461)
  if (is_admin_user("global", getparam("unm"))) {
     rsprintf("<input type=submit name=cmd value=\"%s\">\n", loc("Delete this logbook"));
     rsprintf("<input type=submit name=cmd value=\"%s\">\n", loc("Rename this logbook"));
     rsprintf("<input type=submit name=cmd value=\"%s\">\n", loc("Create new logbook"));
}

The functions called to validate the user are following:

(elogd.c:21298)
BOOL is_admin_user(char *logbook, char *user):
//...
   if (user == NULL)
      return FALSE;

(elogd.c:21324)

BOOL is_admin_user_global(char *user)
{
//...
   if (user == NULL)
      return FALSE;

Since I assume that I'm probably in the "userless" case (no users are defined in the configuration,
and no usernames are set when launching elog either), I would understand that this causes the options for
global config editing etc etc not to be shown on the admin page.

In my opinion (and given that my interpretation of the code flow isn't wrong), the "null"
user should be indeed considered admin, at least as long as no user management is defined whatsoever.
(If I got it right, if user==NULL, but a password file exists, user management is applied,
thus we're in the case of anonymous user which is correctly not admin).

Again, I might be wrong, but I would be curious to hear an opinion from you about this issue.
Thanks again for your attention.
GiorgioCC

You haven't found it. Just look here:

http://midas.psi.ch/elog/config.html#access

You need Password file and Login user. 

I added your vote to the wishlist

https://midas.psi.ch/elog/wishlist.html