> > 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.