Re: Applying cell style or some sort of subst in list view only, posted by Andreas Luedeke on Thu Feb 4 15:07:07 2016
|
> Good day,
>
> I have an attribute that is 25 chars. it can be empty until someone edit it to fill the information.
> The default view for that logbook is List.
>
> Is it possible to display that attribute in list view but not the entire 25 chars ?
> What I mean is that if the field is empty, show it as empty but if it has some information, show something like "X" in List view.
>
> I tried playing with Styles and Cell Styles but I couldn't figure it out...
> Cell Style seams to require specific values "" to apply the style properties. I can't figure how to apply cell style "if field is not empty" :)
>
> Thanks for your help :)
If your server would run on Linux, then the configuration below would just do what you've asked for:
Attributes = X
List change X = $shell(if [ -z "$X" ] ;then echo "";else echo "X";fi)
But since shell scripting is operating system dependent, you'll need to figure out yourself how to do it in Windows.
Cheers
Andreas |
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Andreas Luedeke on Mon Feb 8 15:07:05 2016
|
You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.
Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")
Cheers, Andreas
| Tapasi Ghosh wrote: |
|
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 16:19:11 2016
|
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/
ls -ltr
drwxrwxrwx 6 tapasi admin 204 Jan 7 18:26 demo
| Andreas Luedeke wrote: |
|
You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.
Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")
Cheers, Andreas
| Tapasi Ghosh wrote: |
|
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Andreas Luedeke on Mon Feb 8 16:27:45 2016
|
The process elogd runs as the user "nobody". This user obviously cannot write to /usr/local/elog/logbooks/demo.
But apparently you've created the wrong directory anyway: you've listed /usr/local/elog/demo, but ELOG looks for /usr/local/elog/logbooks/demo.
Cheers, Andreas
| Tapasi Ghosh wrote: |
|
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/
ls -ltr
drwxrwxrwx 6 tapasi admin 204 Jan 7 18:26 demo
| Andreas Luedeke wrote: |
|
You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.
Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")
Cheers, Andreas
| Tapasi Ghosh wrote: |
|
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
|
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Tapasi Ghosh on Mon Feb 8 17:40:27 2016
|
Sorry, it was my mistake while copying from terminal to the email . There is no "demo" directory under /usr/local/lib.
Tapasis-MacBook-Pro:elog tapasi$ cd /usr/local/elog/logbooks/demo
Tapasis-MacBook-Pro:demo tapasi$ ls -ltr
total 0
drwxr-xr-x 3 tapasi admin 102 Sep 22 11:00 2001
drwxr-xr-x 55 503 admin 1870 Dec 17 13:21 2015
drwxr-xr-x 2 tapasi admin 68 Jan 7 14:54 2016
So, how can I change the user from "nobody" to my name, so that elogd runs in my user name ?
Thanks
| Andreas Luedeke wrote: |
|
The process elogd runs as the user "nobody". This user obviously cannot write to /usr/local/elog/logbooks/demo.
But apparently you've created the wrong directory anyway: you've listed /usr/local/elog/demo, but ELOG looks for /usr/local/elog/logbooks/demo.
Cheers, Andreas
| Tapasi Ghosh wrote: |
|
Thanks for your reply.
I am the user and it also has the write access
cd /usr/local/elog/
ls -ltr
drwxrwxrwx 6 tapasi admin 204 Jan 7 18:26 demo
| Andreas Luedeke wrote: |
|
You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.
Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")
Cheers, Andreas
| Tapasi Ghosh wrote: |
|
Dear All,
I could not submit a new enetry to my logbook whenever restarting my laptop. I am a new user to elog.
Attached is the screenshot of the error message and also there is "nobody" while I grep elog.
----------------------
>>
Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$ ps aux | grep elog
tapasi 560 0.4 0.0 2432772 644 s002 S+ 9:50AM 0:00.01 grep elog
nobody 76 0.0 0.4 2481308 18440 ?? Ss 9:48AM 0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg
--------------------------
Any suggesstion will be very much appreciated.
Thanks in advance,
Tapasi
|
|
|
|
|
|
Re: New entry cannot be written to directory "/usr/local/elog/logbooks/demo/", posted by Stefan Ritt on Mon Feb 8 19:29:47 2016
|
Use
usr = <user anme>
in elogd.cfg as written in the documentation.
Stefan
| Tapasi Ghosh wrote: |
|
So, how can I change the user from "nobody" to my name, so that elogd runs in my user name ?
|
|
|
Re: size of atributes in summary mode, posted by Diego on Wed Feb 10 23:44:38 2016
|
I answer myself... Modify the value of width=100% in the class .listtitle2 in the .css file.
| Diego wrote: |
|
Good night,
I would be grateful if someone could indicate me, how could I increase the size of the block where the text of the atribute are in the summary mode.I would like, for example, increase the size of the "subject" you can see on the picture.
Thank you so much!!!
|
|
|
Re: Find empty attributes, posted by Stefan Ritt on Wed Feb 17 08:18:05 2016
|
Unfortunately not possible.
Stefan
| Arno Teunisse wrote: |
|
Want to use the find function from ELOG to search for empty fields ( Attributes that are not defined )
How to do that ?
Could not find it in the Forum.
Greetings Arno Teunisse
|
|