parse a correctly the username in save_user_config when using Webserver authentication, posted by Christof Hanke on Wed May 6 15:13:11 2015 
|
Hi Stefan,
When we use Webserver authentication, we have the correct username already in the variable http_user. |
Re: parse a correctly the username in save_user_config when using Webserver authentication, posted by Stefan Ritt on Tue Jun 9 15:44:49 2015
|
Hi Christof,
thanks for the patch, I merged it into the current HEAD.
/Stefan |
Attribute not updated, posted by Francois Cloutier on Wed May 13 14:58:46 2015
|
Good day,
I'm populating 2 fields based on the Option set in a third one.
|
|
Re: Attribute not updated, posted by Francois Cloutier on Wed May 13 15:19:55 2015
|
I also tried with :
{1, 53} Preset #Parution = 1
{2, 54} Preset #Parution = 2
|
|
Re: Attribute not updated, posted by Andreas Luedeke on Thu May 14 02:02:45 2015
|
Hi Francois,
as far as I know there is a limit on the number of conditions you can use (See elog:67303).
I guess you did hit that limit.
|
|
Re: Attribute not updated, posted by Francois Cloutier on Thu May 14 02:27:58 2015
|
> Hi Francois,
> as far as I know there is a limit on the number of conditions you can use (See elog:67303).
> I guess you did hit that limit.
|
Re: Attribute not updated, posted by Andreas Luedeke on Thu May 14 04:59:03 2015
|
> Seriously, I really hope It could make it... Could you try it on your side ?
|
|
Re: Attribute not updated, posted by Francois Cloutier on Thu May 14 05:08:06 2015
|
>
> > Seriously, I really hope It could make it... Could you try it on your side ?
>
|
|
Re: Attribute not updated, posted by Midas User on Tue Jun 9 15:28:53 2015
|
> I saw in the doc that an attribute cant be bigger than 100 char. but I couldn't figure the maximum size for options... I'm wondering if the issue comes
from the browser not refreshing correctly or if its elog..
|
edit somebody else's draft, posted by Konstantin Olchanski on Wed May 20 01:54:55 2015
|
this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
methinks I should only be offered to edit draft messages that I own or I can edit. K.O. |
|
Re: edit somebody else's draft, posted by David Pilgram on Wed May 20 22:12:49 2015
|
> this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
I find it odd that I can see someone elses draft, but never one that I am in the middle of composing (using a
|
|
Re: edit somebody else's draft, posted by Stefan Ritt on Fri May 22 13:50:31 2015
|
> > this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> > methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
> I find it odd that I can see someone elses draft, but never one that I am in the middle of composing (using a
|
|
Re: edit somebody else's draft, posted by Midas User on Tue Jun 9 15:22:03 2015
|
> this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
> methinks I should only be offered to edit draft messages that I own or I can edit. K.O.
|
RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Kamen Nikolov on Fri May 8 00:18:12 2015
|
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 |
|
Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Kamen Nikolov on Tue May 26 22:03:05 2015
|
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 |
|
Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Andreas Luedeke on Wed May 27 10:50:41 2015
|
Hi Kamen,
I've just tried it for V3.1.0 (6ab0fd5) and the described behaviour is unchanged.
It is even worse if you
don't specify the "RSS Title": datetime attributes are just displayed as seconds of the epoch then.
I think this is a feature
of ELOG at the moment.
You'll either need to dig into the code yourself or wait for Stefan to fix it.
I |
|
Re: RSS Feed Not Providing Time Stamps For datetime Attributes, posted by Stefan Ritt on Tue Jun 9 13:22:25 2015
|
I fixed the problem in the current GIT version.
/Stefan
Kamen |
|
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: |
|
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 |
|
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?) |
|
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 |
|
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. |
|
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
|
|
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 |
|
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 |
|
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 |
|
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 |
|
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: " |
|
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 |
|
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. |
|
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, |
|
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/ |
|
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, |