Fixed text, posted by Neal Grafton on Tue May 26 10:38:36 2015
|
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: |
Re: Fixed text, posted by Andreas Luedeke on Tue May 26 11:26:12 2015
|
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:
|
|
Re: Fixed text, posted by Neal Grafton on Tue May 26 12:34:44 2015
|
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:
|
|
|
Re: Fixed text, posted by Andreas Luedeke on Wed May 27 08:41:05 2015
|
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:
|
|
|
|
Re: Fixed text, posted by Neal Grafton on Wed May 27 08:51:23 2015
|
Andreas
We are still playing around with ideas, just thought I'd ask, didn't think it was possible.
We are ok with setting attributes but this is new to us as yet so may have more questions later.
Looking to produce, initially a shift running log and then many other logs for ISIS accelerator departments here at Rutherford Lab.
Thanks for the advice.
Andreas Luedeke wrote: |
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:
|
|
|
|
|
Side effects of draft messages (was Fixed text), posted by Andreas Luedeke on Wed May 27 08:54:27 2015
|
Hi Stefan,
I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.
I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).
It feels wrong if I watch people while they making an entry ;-)
Anyway, it is just an idea.
Cheers
Andreas
Neal Grafton wrote: |
Thanks Andreas
We are still playing around with ideas, just thought I'd ask, didn't think it was possible.
We are ok with setting attributes but this is new to us as yet so may have more questions later.
Andreas Luedeke wrote: |
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:
|
|
|
|
|
|
Side effects of draft messages (was Fixed text), posted by Stefan Ritt on Tue Jun 9 13:01:50 2015
|
I changed it such that drafts are not shown at all in ELOG. The only way you realize them is if you hit "new", and you will be prompted if there is any pending draft.
Andreas Luedeke wrote: |
Hi Stefan,
I got an answer to a forum entry before I actually finished writing my post! It is obviously possible to reply to a draft message.
I think it would be excellent if draft messages would only be shown to their authors (except maybe in case of an anonymous author).
It feels wrong if I watch people while they making an entry ;-)
Anyway, it is just an idea.
Cheers
Andreas
Neal Grafton wrote: |
Thanks Andreas
We are still playing around with ideas, just thought I'd ask, didn't think it was possible.
We are ok with setting attributes but this is new to us as yet so may have more questions later.
Andreas Luedeke wrote: |
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:
|
|
|
|
|
|
|
LDAP docs, posted by Stephen G on Thu Jun 4 00:08:56 2015
|
Could someone point me to the LDAP configuration docs, I searched to no avail. I'm sure there is some big red ldap config button it, but I just can't find it. |
Re: LDAP docs, posted by David Wallis on Thu Jun 4 16:25:42 2015
|
This is what I've been able to figure out, in terms of the elogd.cfg file:
LDAP server = server.domain:389
LDAP userbase = ou=people,o=domain.com,dc=domain,dc=com
LDAP login attribute = uid
LDAP register = 0
Stephen G wrote: |
Could someone point me to the LDAP configuration docs, I searched to no avail. I'm sure there is some big red ldap config button it, but I just can't find it.
|
|
Re: LDAP docs, posted by Stephen G on Thu Jun 4 19:36:31 2015
|
Thank you, I am looking to do LDAPS over 636 where would the certificate go (Does it go in the SSL folder?).
David Wallis wrote: |
This is what I've been able to figure out, in terms of the elogd.cfg file:
LDAP server = server.domain:389
LDAP userbase = ou=people,o=domain.com,dc=domain,dc=com
LDAP login attribute = uid
LDAP register = 0
Stephen G wrote: |
Could someone point me to the LDAP configuration docs, I searched to no avail. I'm sure there is some big red ldap config button it, but I just can't find it.
|
|
|
Re: LDAP docs, posted by Stefan Ritt on Tue Jun 9 12:40:44 2015
|
I do not officially support LDAP, since I don't have any server to test it. So it comes as a third party's contibution from https://github.com/vykozlov/elog-ldap.
To my knowlede LDAPS has not been implemented. You could post an issue the the github repository to ask the original author.
/Stefan
Stephen G wrote: |
Thank you, I am looking to do LDAPS over 636 where would the certificate go (Does it go in the SSL folder?).
David Wallis wrote: |
This is what I've been able to figure out, in terms of the elogd.cfg file:
LDAP server = server.domain:389
LDAP userbase = ou=people,o=domain.com,dc=domain,dc=com
LDAP login attribute = uid
LDAP register = 0
Stephen G wrote: |
Could someone point me to the LDAP configuration docs, I searched to no avail. I'm sure there is some big red ldap config button it, but I just can't find it.
|
|
|
|
Emails generated by Elog, posted by David Pilgram on Fri Jun 5 12:28:21 2015
|
I am one who received an email every time there is a new entry in this forum.
I have just noticed that since May 20, every email contains the message "An old ELOG entry has been updated: "
whereas before that date, the vast majority say "A new ELOG entry has been submitted: "
Is this something to do with the saving of draft messages?
Talking of which, I see my draft of this message shows up in the forum before I have submitted it. |
Re: Emails generated by Elog, posted by Stefan Ritt on Fri Jun 5 12:34:32 2015
|
I acknowledge these two bugs and will fix them soon.
David Pilgram wrote: |
I am one who received an email every time there is a new entry in this forum.
I have just noticed that since May 20, every email contains the message "An old ELOG entry has been updated: "
whereas before that date, the vast majority say "A new ELOG entry has been submitted: "
Is this something to do with the saving of draft messages?
Talking of which, I see my draft of this message shows up in the forum before I have submitted it.
|
|
Re: Emails generated by Elog, posted by Stefan Ritt on Tue Jun 9 12:11:19 2015
|
I fixed both issues in the current GIT version. Please double check it.
Stefan Ritt wrote: |
I acknowledge these two bugs and will fix them soon.
David Pilgram wrote: |
I am one who received an email every time there is a new entry in this forum.
I have just noticed that since May 20, every email contains the message "An old ELOG entry has been updated: "
whereas before that date, the vast majority say "A new ELOG entry has been submitted: "
Is this something to do with the saving of draft messages?
Talking of which, I see my draft of this message shows up in the forum before I have submitted it.
|
|
|
Different way CSS files are handled, posted by Stefan Ritt on Fri Jun 5 14:24:34 2015
|
Hi,
I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.
In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:
elog.css:
td {
color:black;
font-size:12px;
}
Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:
td {
font-size:18px;
}
This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.
The modification is committed to GIT and will be contained in the next release of elog.
/Stefan |
Re: Different way CSS files are handled, posted by Andreas Luedeke on Fri Jun 5 19:01:05 2015
|
Hi Stefan,
there is a little problem with the Makefile (on SL5 and SL6): the following line:
@$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/
/usr/bin/install: omitting directory `themes/default/icons'
make: *** [install] Error 1
When I go back to the old Makefile construct:
@$(INSTALL) -m 0644 themes/default/icons/* $(ELOGDIR)/themes/default/icons/
@for file in `find themes/default -type f` ;\
do \
if [ ! -f $(ELOGDIR)/themes/default/`basename $$file` ]; then \
$(INSTALL) -m 0644 $$file $(ELOGDIR)/themes/default/`basename $$file` ; \
fi; \
done
then it seems to work again.
Cheers
Andreas
Stefan Ritt wrote: |
Hi,
I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.
In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:
elog.css:
td {
color:black;
font-size:12px;
}
Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:
td {
font-size:18px;
}
This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.
The modification is committed to GIT and will be contained in the next release of elog.
/Stefan
|
|
Re: Different way CSS files are handled, posted by Stefan Ritt on Tue Jun 9 09:39:14 2015
|
Ok, fixed again.
Andreas Luedeke wrote: |
Hi Stefan,
there is a little problem with the Makefile (on SL5 and SL6): the following line:
@$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/
/usr/bin/install: omitting directory `themes/default/icons'
make: *** [install] Error 1
When I go back to the old Makefile construct:
@$(INSTALL) -m 0644 themes/default/icons/* $(ELOGDIR)/themes/default/icons/
@for file in `find themes/default -type f` ;\
do \
if [ ! -f $(ELOGDIR)/themes/default/`basename $$file` ]; then \
$(INSTALL) -m 0644 $$file $(ELOGDIR)/themes/default/`basename $$file` ; \
fi; \
done
then it seems to work again.
Cheers
Andreas
Stefan Ritt wrote: |
Hi,
I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.
In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:
elog.css:
td {
color:black;
font-size:12px;
}
Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:
td {
font-size:18px;
}
This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.
The modification is committed to GIT and will be contained in the next release of elog.
/Stefan
|
|
|
Auto save feature not working on 3.1.0, posted by David Wallis on Fri Jun 5 23:10:27 2015
|
Auto-saving does not seem to be working. In the config file, I have the following:
Save drafts = 1
Autosave = 10
but I never see the "auto saving" message or get any other indication that the feature is working.
Am I missing something? |
option transfer, posted by Neal Grafton on Fri Jun 5 11:52:43 2015
|
Can the chosen text in a dropdown menu be automatically transfered (copied) to this Text box? |
Re: option transfer, posted by Stefan Ritt on Fri Jun 5 12:01:01 2015
|
No.
Neal Grafton wrote: |
Can the chosen text in a dropdown menu be automatically transfered (copied) to this Text box?
|
|
Re: option transfer, posted by Neal Grafton on Fri Jun 5 13:06:22 2015
|
OK Thanks
I was trying to save the operator repeatedly typing in standard messages.
Stefan Ritt wrote: |
No.
Neal Grafton wrote: |
Can the chosen text in a dropdown menu be automatically transfered (copied) to this Text box?
|
|
|
Re: option transfer, posted by Stefan Ritt on Fri Jun 5 13:19:43 2015
|
There are browser extensions for that like "Autofill Forms" for Firefox. You can even link text templates to a single key.
Neal Grafton wrote: |
OK Thanks
I was trying to save the operator repeatedly typing in standard messages.
Stefan Ritt wrote: |
No.
Neal Grafton wrote: |
Can the chosen text in a dropdown menu be automatically transfered (copied) to this Text box?
|
|
|
|
Re: option transfer, posted by Andreas Luedeke on Fri Jun 5 19:35:34 2015
|
Why would you transfer the message to the text box?
You can have a "Message" attribute, which is an option list.
If the first option "Custom" is chosen, then you get an additional field "Custom Message".
We have an attribute "Entry type", there we could add the type "Message", if the attribute should not exist for other types of entries.
As an alternative you can have bookmarks in your browser, where the title field is preset already in the URL. In this Forum you can preset the Subject field by:
https://midas.psi.ch/elogs/Forum/?cmd=New&ignore=1&pSubject=test:please+ignore
Cheers
Andreas
Neal Grafton wrote: |
OK Thanks
I was trying to save the operator repeatedly typing in standard messages.
Stefan Ritt wrote: |
No.
Neal Grafton wrote: |
Can the chosen text in a dropdown menu be automatically transfered (copied) to this Text box?
|
|
|
|
ELOG Version field in elogs/Forum, posted by Andreas Luedeke on Fri May 29 09:38:40 2015
|
Hi Stefan,
could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
number?
That would be 13 characters.
Cheers
Andreas |
Re: ELOG Version field in elogs/Forum, posted by Stefan Ritt on Fri Jun 5 10:18:38 2015
|
> Hi Stefan,
> could we change the format of the "ELOG Version" field in this logbook, that one can enter the full git revision
> number?
> That would be 13 characters.
>
> Cheers
> Andreas
Ok, done.
/Stefan |
Duplicate: LDAP docs, posted by Stephen G on Thu Jun 4 00:10:32 2015
|
This is a duplicate, made by mistake.
Could someone point me to the LDAP configuration docs, I searched to no avail. I'm sure there is some big red ldap config button it, but I just can't find it. |
|