Re: insert screenshots directly to elog?, posted by Yoshio Imai on Fri Feb 5 14:51:23 2010
|
Since elog is only the web server providing (comfortable) access to the logbook database, it relies on the web browser (possibly enhanced by script code) for facilities to attach pictures and other files to entries. So unless your browser has such an extension or someone writes some sort of script that can do it, the only way is to use an external capturing program, save the picture and upload it in the usual way. Cf. also entry 66004.
|
|
Re: Single Button Entry, posted by Yoshio Imai on Thu Feb 18 18:50:57 2010
|
| Geoff Ellis wrote: |
|
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this?
|
You could write a script/program that calls the ELOG client with the necessary attributes to submit the entry (see the user's guide). |
|
Re: Log Thread Close Automatically, posted by Yoshio Imai on Mon Feb 22 11:15:48 2010
|
| tom wrote: |
|
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages.
|
Did you consider using the "Restrict edit time" option? It should provide the necessary functionality, as long as you don't want to lock the entry at a fixed absolute time, but really only x hours after creation (also, as you talked about closing the "thread" automatically, there is no option to prevent replies after a certain amount of time).
See the administrator's guide. |
inline-code, posted by Yoshio Imai on Tue Jun 8 15:48:06 2010
|
Hi, Stefan!
Sometimes, it is annoying that the [code] -Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag [ilcode] (in-line code) which translates to <code> instead of <pre> .
Cheers
Yoshio |
|
Re: elog password , attributes and quoting username and password, posted by Yoshio Imai on Thu Nov 11 17:51:49 2010
|
| Arno Teunisse wrote: |
|
Please Notice that I've put quotes around : -u "username password" ( the documentation shows that this is not necessary) . But now it failes to see a required attribute.
|
Have you tried without the quotes? They may not be allowed! |
|
Re: elog password , attributes and quoting username and password, posted by Yoshio Imai on Fri Nov 12 11:48:54 2010
|
| Arno Teunisse wrote: | | It seems that the -m option for elog.exe is a required commandline option. |
You are right; I didn't see that part was missing. On the other hand, I obviously didn't see a few other things in your post, either ...  |
|
Re: Don't see login page - Self register = 1, posted by Yoshio Imai on Thu Nov 25 14:15:31 2010
|
Hi!
| Christoph Kukulies wrote: | I cannot get the login screen. I'm connecting to a logbook (and I can do this without logging in).
Shouldn't I get a screen to login/register? |
| Christoph Kukulies wrote: | | Guest menu commands = List, Find, Login, Help |
I might be wrong, but since you have defined "Guest menu commands", you should indeed be able to read the logbooks without logging on, only write access should be prevented. Do you get the login window when you explicitly click onto the "Login" link?
Also, I noticed that your user lists are space-separated, although as far as I know they should be comma-separated.
I hope this helps!
Yoshio |
|
Re: Don't see login page - Self register = 1, posted by Yoshio Imai on Fri Nov 26 11:42:50 2010
|
| Christoph Kukulies wrote: | | I only need to know how I get an admin passwd and user into the passwd file. |
You do this the same way as a regular user: use the self registration feature to create a user, and then declare this user to be the admin in your config file.
Yoshio |