| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67298
|
Wed Jul 4 14:18:21 2012 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.8.1-2350 | Re: move a type of entries to another logbook |
| Ze Li wrote: |
|
[...] I have logbook A and logbook B. Is it possible to move one type of entries in logbook A to logbook B? If yes, may I know how you do it? Thank you.[...]
|
-
You can add the "Move to = B" command in logbook A.
-
Then you add "select" in "List Menu commands = ..., select, ...".
-
Now you "Find" all entries of the type you want (for convenience choose "Display 9999 entries per page").
-
You press "toggle all" and then "Move to B"
|
|
67307
|
Fri Aug 10 11:47:49 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.0-2411 | Re: Authentication problem with wget and links (text browser) |
| cowden wrote: |
|
Hello,
I'm not able to authenticate to a logbook using my text based browser links, so I've started investigating with wget hoping solving the problem one will lead to a solution for the other. I've seen some examples on how to use wget to parse logbook entries in this forum, but my attempts keep returning the login page. Any advice would be helpful and appreciated. Here are a couple of the command line arguments I've tried:
wget --save-cookies cookie.txt --keep-session-cookies -d "http://hostname/LOGBOOK?unamee=YYY&upassword=XXX" -O elog.txt
wget --save-cookies cookie.txt --keep-session-cookies -d --post-data="redit=&uname=YYY&upassword=XXX&remember=1" -e robots=off "http://hostname/LOGBOOK" -O elog.txt
After these executions, my cookies.txt file remains empty. Running subsequent command with "--load-cookies=cookies.txt" still points me to the login page.
Many Thanks,
Chris
|
I've just checked that 'wget --no-check-certificate --save-cookies cookie.txt --keep-session-cookies -d "https://elog-gfa.psi.ch/SLS?uname=uuu&upassword=ppp" -O elog.txt'
created a file cookie.txt. The file contains three lines of data if uname and upassword are a valid login, and it is empty (beside of three comment lines) if they are not a valid login (wrong user or wrong password).
Could it be related to the set-up of your particular logbook? |
|
67334
|
Wed Sep 12 10:50:40 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9 | Re: Type <attribute> = Date - Issue |
| Garret Delaronde wrote: |
|
I haven't found anything in the forums about this. Apologies if its a duplicate.
I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work.
Currently looking to do some updates to one of the instances with the Date Type setting.
We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.
Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).
However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.
Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?
Syntax manual didn't help much for this issue.
|
The problem is, that the existing entries have a string content for this specific attribute.
An attribute with a "date" type content should contain a integer number, which represents the seconds of the epoch (starting with zero on 1-Jan-1970 at 00:00:00).
What you need to do is writing a script that reads all *a.log files in the logbook directory and converts lines of the type:
<attribute>: <text>
to lines like
<attribute>: $(date -d "<text>" +%s)
Unfortunately elog does not provide you with such a tool.
But since you have to write it now anyway now, you could submit your code to this forum 
Andreas |
|
67338
|
Mon Sep 17 09:16:38 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 2.9.2 | Re: HTML editor |
| Josef Uher wrote: |
|
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum. |
|
67341
|
Tue Sep 18 10:05:27 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | 2.9.2-2473 | Re: Mysterious Emboldened lines in threaded (collapsed) mode | > 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 |
|
67356
|
Thu Oct 4 11:35:12 2012 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.1 | Re: Importing XML |
| David Chastain wrote: |
|
[...] 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?
|
I've successfully imported a large amount of entries from old non-ELOG logbooks via XML.
The only problem that I did run into was the date format: ELOG is very restrictive on the imported format; it has to be either "MM/DD/YY(YY) (HH:MM:SS)" or "DD.MM.YY(YY) (HH:MM:SS)".
When you export entries ELOG honours the "Date format" that you've specified in your elogd.cfg, therefore you cannot import the exported file until you reformat the date in the file.
Andreas |
|
67360
|
Mon Oct 29 07:52:07 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | Windows | latest | Re: Comment avoir elog en français II |
| Philippe Rousselot wrote: |
|
Bonjour,
tout est dans le titre.
Merci
For those who speak strange languages, I asked how to get a french version of elog.
By the way, this is my second mail because I forgot to give an icon to the first mail, and when I hit Back to do so, my text was erased. Bug or normal obnoxious attitude of my browser ?
Thanks in advance
Philippe
|
ELOG comes "internationalised": you just need to set your desired language in the configuration files.
Language = french
in the configuration file elogd.cfg does the trick.
If you are capable to read the English language (which I suppose ), then I would recommend reading the manual, e.g. https://midas.psi.ch/elog/config.html#global  ⇄
Detect language » English
PS: I happened to have the same problem (text erased after "back") when I had javascript disabled in the browser. If you have it enabled, you'll get a popup window that tells you what mandatory fields are missing in your post. Then you'll not need to use the back button. |
|
67364
|
Mon Oct 29 17:27:12 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Windows | latest | Re: Comment avoir elog en français II [solved almost] |
| David Pilgram wrote: |
|
May I make a suggestion here? Something I do for other reasons. I run two separate elog daemons, each with their own configuration files. In this case you could have one configuration file tout en française, and the other in English. This gets around the language setting being in the Global section of the configuration file elog.cfg
Of course this needs a little planning, for example a small script/batch file to start up each daemon with the correct config file. - so on my linux system, I start one with
/usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd0.cfg -d /home/logbooks
and the other with
/usr/local/sbin/elogd -p 8081 -c /home/logbooks/elogd1.cfg -d /home/logbooks
The disadvantage is that you cannot click between French and English by the tabs along the top of the elog page, you'd have to switch between browser windows.
Hope this helps.
David.
|
Does this work nice and stable for you? I've tried at the beginning to run two server on one host, one in German and the other in English.
I experienced occasional server crashes (every few days) and assumed that they were related to two mirrors running on the same host.
A mirror server just for a second language was not of big importance to me, therefore I did shut down the mirror server.
And the server stopped crashing then. Was that just coincidence?
I recognised that you are not running a mirror, you let both logbook processes access the same data. Is that save?
Did you ever see data corruption from two processes modifying the same data? Or is one of the ELOG servers not used much?
Thanks for sharing your experience!
Andreas
⇄
Detect language » English
|
|