| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67938
|
Wed May 27 08:41:05 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.0 | Re: Fixed text | Hi Neal,
you can preload words into one attribute field, but one field is either editable or not, you cannot protect single words in a field.
But the ELOG way to solve this would be to have multiple attributes: you would get one entry field for each attribute.
Just look at this logbook: it has the attributes Icon, Author, Author Email, Category, OS, ELOG Version and Subject.
You can change the content of each attribute (except of "Author", that field is made here to be not editable), but as a normal user you cannot change the names in front of the fields.
Did you've set up the demo logbook and played around with it? Because your question suggests to me that you don't figured out yet what ELOG does. (Or as a direct answer: no, it does not make sense to me ;-) )
But I'm sure you'll figure it out: ELOG is best learned by trial and error.
Kind Regards
Andreas
| Neal Grafton wrote: |
|
Sorry I call this field that you write in the subject field, a little confusing.
So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)
Neal
| Andreas Luedeke wrote: |
|
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
| Neal Grafton wrote: |
|
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
|
|
67937
|
Tue May 26 22:03:05 2015 |
| Kamen Nikolov | kanikolov@gmail.com | Question | Windows | V2.9.0-239 | Re: RSS Feed Not Providing Time Stamps For datetime Attributes | Can anyone help? Do I need to do something different or could this possibly be a bug that is fixed in a newer version?
Thanks,
Kamen
| Kamen Nikolov wrote: |
|
Hello,
I am using the RSS feed feature of Elog (V2.9.0-2396). I have a couple of attributes of type "datetime" (Start Time and Stop Time). I don't have a "Time Format" statement, so just using the default format. I am passing the Start Time and Stop Time attributes to the RSS Title with $Start Time and $Stop Time, but when looking at the RSS title in IE11 browser, I only see the date and not the time. Is there any way I can see the time as well?
Additional info:
I'm also passing the creation time of the Elog with $entry time and this is displaying correctly (both date and time).
Please let me know if I am doing something incorrectly?
Thanks
|
|
|
67936
|
Tue May 26 12:34:44 2015 |
| Neal Grafton | nealgrafton@stfc.ac.uk | Question | Windows | 3.1.0 | Re: Fixed text | Sorry I call this field that you write in the subject field, a little confusing.
So is there anyway to fix the indicated words in place in this typing space so you can enter the text you want next to them but be unable to delete them. (does this make sense?)
Neal
| Andreas Luedeke wrote: |
|
Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
| Neal Grafton wrote: |
|
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
|
67935
|
Tue May 26 11:26:12 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.0 | Re: Fixed text | Dear Neal,
I don't understand your example. There is no such thing as a "subject field". You can define an attribute called "subject", like in this logbook.
But I would guess that you want to have five attributes "Time Off", "Reason", etc. that cannot be altered after an entry has been created? That's easy.
Or do you want to protect entries with specific content not to be deleted? That is not easy.
Please explain in more detail what you want to achieve, and I'll be happy to help.
Cheers, Andreas
| Neal Grafton wrote: |
|
I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail:
|
|
|
67934
|
Tue May 26 10:38:36 2015 |
 | Neal Grafton | nealgrafton@stfc.ac.uk | Question | Windows | 3.1.0 | Fixed text | I'd like to fix text or table in the subject field that can't be deleted or moved.
Can that be done in config? Example -
Time Off:
Reason:
Update By:
Estimated On time:
Detail: |
|
67933
|
Sat May 23 02:53:31 2015 |
| Konstantin Olchanski | olchansk@triumf.ca | Bug report | Linux | All | 3.1.0 | Re: elogd moves elog entries | >
> "News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"
>
> And for version 3.0.0 it states:
> - Create one logbook subdirectory pear year
>
The text should read:
the first time you run the new elogd against old elog data,
all existing entries will be moved into by-year subdirectories
and the old elogd will not work anymore.
K.O. |
|
67932
|
Sat May 23 02:49:22 2015 |
| Konstantin Olchanski | olchansk@triumf.ca | Bug report | Linux | 3.1.0 | Re: elogd complains about unknown cookies | > > elogd is spewing these messages about unknown cookies:
> >
> > Received unknown cookie "is_returning"
> > Received unknown cookie "__utma"
> > Received unknown cookie "__utmz"
> > Received unknown cookie "SSESSee3cc9c70bedf9a840203765bf409d7b"
> > Received unknown cookie "SESSee3cc9c70bedf9a840203765bf409d7b"
> > Received unknown cookie "MidasWikiUserID"
> > Received unknown cookie "MidasWikiUserName"
> > Received unknown cookie "MidasWiki_session"
> >
> > K.O.
>
> Delete your cookies ;-)
>
No, go. The MidasWikiUserName cookie will log me out of the MidasWiki, etc.
But why are MidasWiki cookies sent to the elog? Ah, yes, they all run from the same https://midas.triumf.ca.
This explains why elog complains about unexpected cookies - elogd does not expect to receive
mediawiki cookies - it does not expect to share the https:// connection with somebody else.
This is good to know for the future. (I.e. if mediawiki is confused by elogd cookies).
K.O. |
|
67931
|
Fri May 22 13:59:41 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 3.1.0 | Re: elogd complains about unknown cookies | > elogd is spewing these messages about unknown cookies:
>
> Received unknown cookie "is_returning"
> Received unknown cookie "__utma"
> Received unknown cookie "__utmz"
> Received unknown cookie "SSESSee3cc9c70bedf9a840203765bf409d7b"
> Received unknown cookie "SESSee3cc9c70bedf9a840203765bf409d7b"
> Received unknown cookie "MidasWikiUserID"
> Received unknown cookie "MidasWikiUserName"
> Received unknown cookie "MidasWiki_session"
>
> K.O.
Delete your cookies ;-)
Elog just logs all unknown cookies for trouble shooting. This should go under verbose output. I changed that just now.
Stefan |
|