We have multiple logbooks. Each user is admin user for his/her own logbook. 

I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user. 

[logbook1]
Admin user = user1
Login user = user1, user2
Allow Config = user1
List Menu commands = Admin, Config

user1 click on Admin, it opens config file, when user1 click on save, user1 is brought to Config page, which has select user list on top, Change password, Remove user, New user buttons on bottom. Is there a way that admin user has access to config file, but no access to user info at all (not even presented to them).  Is there a way after user1 click save, page doesn't go to that config page?

I could put 
Deny Change password =
Deny Remove user
Deny New user

so when user1 click on those buttons, user1 will get command not allowed. However I would rather have user1 not even see that page. 

> > I upgraded my system, including the version of Firefox.
> > [...]
> > Sorry this is a bit rambling, but its very hard to describe!
> 
> A picture can say more than thousand words.
> Can you reproduce this with a simple configuration?
> If yes, can you attach the configuration, the *a.log files,
> a description of what firefox version you're using and please:
> some screenshots of "before" and "after"?
> 
> Thanks!
> Andreas
That's odd, I cannot reproduce the problem today - except on the topic [logbook] it already exists on.
Yet nothing has changed.  
I've looked for hidden files, hidden control codes in the *a.log files...  this one had better be put on the
back burner until I can find a way to reproduce it (!).

I was wondering if anyone out there has had any success with importing XML data into ELOG. Using the XML schema which I derive from the EXPORT data from ELOG into XML format or creating the file from scratch, I either blowup the system and have to restart elogd or it doesn't work and says, XML file doesn't contain ELOG_LIST element (which I create and it still doesn't work).

Basically, I am trying to take spreadsheet data, convert it into XML and upload it as a logbook so I don't have to perform lots of data entry. I also tried .CSV but have had no luck. 

Any thoughts or ideas? 

What happens if you just export as .CSV and then import that file again. Does that work?

If not, can you post your .CSV file here and I will have a look.

Stefan 

I'm running elog 2.9.2 on a Red Hat 6.3 server. This installation has been running for some time on a Solaris server, and was recently moved to the RHEL server.

When a user tries to upload a .bmp attachment, the upload never completes, eventually timing out with a proxy error. At that point, the elogd process stops responding to requests and needs to be restarted. Nothing is in the log file other than a "Listening" message when elogd starts up. Png and pdf attachments seem to work fine. I was able to convert an image from .bmp to .png and upload, but that's not practical for my user.

ImageMagick 6.5.4-7 is installed on the server. Everything else seems to be working normally.

Is this a known problem, or have I missed something that needs to be installed on the RHEL server?

When I saw this problem come in, I was reminded of problems I have of elog crashing.  So I tried attaching a .bmp file to an entry.  In my case it did not crash, but it did not run ImageMagick either - it just gave a link as it it were a zip or tar file - that is to say no .png image had been generated and shown.   As I've never attached a .bmp file before, I don't know whether elog allows for them to be processed and a thumbnail made, a quick look in the documentation didn't enlighten me, but then I didn't look for that long either.  (I'm running 2.9.2 svn 2475, under Slackware 13 which is a version post some image processing issues I reported to Stefan - might that explain why in my case?). 

I have found that sometimes elog will crash, but effectively after it has done the action - so if it crashes when asked to move files from one logbook to another, you find the entries have been moved.  In my case, I believe the crashes are due to memory issues, nothing I can state for certain.

It would possibly help Stefan and Andreas if you can tell whether the .bmp file appears in the relivent logbook directory (usually a subdirectory of ....../logbooks) - it will have been renamed as yymmdd_hhmmss_{filename}.bmp - except, of course, the date and time will be showing not these symbols - and if the entry with which you have tried to attach this .bmp file been written - using a text viewer on the file yymmdda.log (obviously the day will be today, i.e. the one just updated as you tried the entry.   I have come across orphan attachment files in directories in my time, possibly from when elog crashed part way through an action.

(If I am stating the obvious, apologies, I don't know your level of experience with elog or linux, so trying to cover all possible levels)

 Thanks for the info, David.

I do not see any *.bmp files in the logbook directory when this happens. The hang happens when the "Upload" button is hit, so there is no logbook entry yet either.